Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Translate UpNext to as many languages possible #112

Closed
dagwieers opened this issue Dec 3, 2019 · 21 comments
Closed

Translate UpNext to as many languages possible #112

dagwieers opened this issue Dec 3, 2019 · 21 comments
Assignees
Labels
release Related to release management translations Related to translations
Milestone

Comments

@dagwieers
Copy link
Collaborator

dagwieers commented Dec 3, 2019

With the upcoming v1.1.0 release including new settings and a new developer mode, it is time to look at the languages supported by the add-ons using UpNext, and reach out to their translators to translate UpNext and related add-ons to their language.

The first goals is to prepare v1.1.0 and make changes that may influence translation files.
(e.g. restructure strings, add needed functionality, etc.) Then we can ask new and existing translators to help out with this task.

I prepared a list of languages supported by Netflix, inputstreamhelper and inputstream.adaptive, which is available in the Wiki:
https://github.com/im85288/service.upnext/wiki/Translations

@dagwieers dagwieers added question Further information is requested translations Related to translations labels Dec 25, 2019
@dagwieers dagwieers added this to the v1.1.0 milestone Dec 25, 2019
@dagwieers dagwieers self-assigned this Dec 25, 2019
@sagatxxx
Copy link

sagatxxx commented Jan 4, 2020

how can i help to spanish translate?

@dagwieers
Copy link
Collaborator Author

@sagatxxx Create a translated .po file for the Spanish (es_es) language based on the English (en_gb) version.

@dagwieers
Copy link
Collaborator Author

dagwieers commented Jan 13, 2020

Existing languages

We have the following issues for existing languages (run make language in the master branch):

@dagwieers
Copy link
Collaborator Author

dagwieers commented Jan 13, 2020

New languages

We would like to offer translations for every language that is supported by related/consuming add-ons (like Netflix) for the best experience by users:

We plan to release by Wednesday, but any translations we get after Wednesday will go into the next release. Thanks in advance!

@dagwieers dagwieers added the release Related to release management label Jan 13, 2020
@mediabrasiltv
Copy link
Contributor

@dagwieers, translation pt-br done, opened PR.
Regards,

Wanilton

im85288 added a commit that referenced this issue Jan 14, 2020
@dagwieers dagwieers removed the question Further information is requested label Jan 14, 2020
@Twilight0
Copy link
Contributor

Cheers, have fun: #157

@sagatxxx
Copy link

sagatxxx commented Jan 14, 2020

spanish.zip
@dagwieers Done spanish translation, how can I upload it?

@dagwieers
Copy link
Collaborator Author

dagwieers commented Jan 14, 2020

@sagatxxx The best option is to fork (on GitHub) and clone our repository, then make a branch, add the file to your branch, make a commit and push it to your GitHub fork. Then make a pull request from this branch. (Steep learning curve)

But you can also make the changes in GitHub by adding the file in the correct place, and the GitHub web-interface will help you make the PR. (Anyone can do this)

Alternatively, I can do it for you.

@sagatxxx

This comment has been minimized.

@dagwieers

This comment has been minimized.

@sagatxxx

This comment has been minimized.

@im85288

This comment has been minimized.

@sagatxxx

This comment has been minimized.

@matejmosko
Copy link
Contributor

matejmosko commented Jan 14, 2020 via email

@dagwieers dagwieers pinned this issue Jan 14, 2020
@dagwieers
Copy link
Collaborator Author

@matejmosko Found it in your GitHub fork and made a PR from it #163 👍

@dagwieers
Copy link
Collaborator Author

If you were considering to translate Up Next, we are going to delay releasing v1.1.0 to Thursday evening, probably 18:00 CEST. This should give you one extra day to contribute your translations!
Any translations we get after that cut-off point will go into the next release.

Thanks to all translators we already have 9 new languages in the upcoming release. More than we could have hoped for! 👍

@ghost ghost mentioned this issue Jan 16, 2020
@dagwieers
Copy link
Collaborator Author

Thanks everyone ! We released version v1.1.0 so I am going to close this issue.
For the next release we will call out to translators again (for incomplete languages).
But feel free to send your translations as soon as you find the time.

@dagwieers
Copy link
Collaborator Author

dagwieers commented Mar 15, 2020

We have created translator-teams in the @kodi-addons organization at: https://github.com/orgs/add-ons/teams/translators

This will help us translate Kodi add-ons to more languages in the future using less effort.
If you are willing to help out, join a language team!

@dagwieers
Copy link
Collaborator Author

We now have a special request for translating Up Next in the Add-ons project at: add-ons/translations#4

@olavinto
Copy link
Contributor

I just have to ask: Why isn't the Kodi Weblate utilized for by many addons for translations? It is so much more accessible to translators and would offer string by string management, glossaries and TMs which would help with terminology and consistency a lot. Doing it via GitHub by simply editing files directly seems super time consuming, not to mention making it completely inaccessible to many potential translators.

I do a lot of Finnish translating and proofreading especially at Crowdin and Weblate and there are many addons (like this one) that I use and have used for years and would happily translate. But doing it without any real translation workflow support features seems super counterproductive to me, and can easily lead to a situation where terminology in a single Kodi instance is all over the place if consistency isn't manually checked against the current Kodi translation.

@MoojMidge
Copy link
Collaborator

The effort to translate this addon predates the Kodi migration to Weblate by at least 1.5 years (probably more actually).

Utilising Weblate requires some administrative work and changes in the addon workflow process, so while it seems like a good idea, it needs a bit of effort to achieve and at the moment there is no one to do this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release Related to release management translations Related to translations
Projects
None yet
Development

No branches or pull requests

8 participants