Translate UpNext to as many languages possible

[dagwieers]

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

[sagatxxx]

how can i help to spanish translate?

[dagwieers]

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

[dagwieers]

Existing languages

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

• French (fr_fr): 17 fatal errors -- @zecakeh :heavy_check_mark:
• Croatian (hr_hr): 18 fatal errors -- @arvvoid :heavy_check_mark:
• Hungarian (hu_hu): 1 fatal error -- @frodo19 :heavy_check_mark:
• Japanese (ja_jp): syntax error -- @Thunderbird2086
• Korean (ko_kr): 3 fatal errors -- @Thunderbird2086

[dagwieers]

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:

• Czech (cs_cz): @angelblue05 @svetlemodry :heavy_check_mark:
• Danish (da_dk): @coz2001
• Greek (el_gr): @Twilight0 :heavy_check_mark:
• Spanish (es_es): @sagatxxx @roliverosc :heavy_check_mark:
• Finnish (fi_fi): @Lam4hound
• Hebrew (he_il): @Eng2Heb
• Lithuanian (lt_lt): @egidijusm
• Latvian (lv_lv): @marcisbe
• Brazilian (pt_br): @mediabrasiltv :heavy_check_mark:
• Portuguese (pt_pt): @beatwiz
• Russian (ru_ru): @vlmaksime :heavy_check_mark:
• Slovak (sk_sk): @matejmosko :heavy_check_mark:
• Swedish (sv_se): @emilsvennesson @Sopor :heavy_check_mark:

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

[mediabrasiltv]

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

Wanilton

[Twilight0]

Cheers, have fun: https://github.com/im85288/service.upnext/pull/157

[sagatxxx]

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

[dagwieers]

@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)

• Start from resources/language/resource.language.es_es/strings.po
• Then copy your strings.po content (we don't need the other files)
• At the bottom give a commit-message
• Then follow the instructions

Alternatively, I can do it for you.

[sagatxxx]

@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)

• Start from resources/language/resource.language.es_es/strings.po
• Then copy your strings.po content (we don't need the other files)
• At the bottom give a commit-message
• Then follow the instructions

Alternatively, I can do it for you.

I think it's done, i'm a little newbie

[dagwieers]

I think it's done, i'm a little newbie

There is no pull request in this project. But I noticed you made a pull request in your own project. https://github.com/sagatxxx/service.upnext/pull/1

I made a PR for you: https://github.com/im85288/service.upnext/pull/158 But somehow you managed to place it in the wrong directory. Let's communicate in the new PR.

[sagatxxx]

@dagwieers Within my ignorance I think I have renamed the folder, now I am lost on how to continue, I need to study the operation of github urgently

[im85288]

Don’t worry about it, it has now been included and will go into the next release. Thanks for your contribution

[sagatxxx]

ohh..., fine!! thanks

[matejmosko]

Slovak done.

Thanks for your work

[dagwieers]

@matejmosko Found it in your GitHub fork and made a PR from it #163 :+1:

[dagwieers]

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! :+1:

[dagwieers]

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]

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]

We now have a special request for translating Up Next in the Add-ons project at: https://github.com/add-ons/translations/issues/4

[olavinto]

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]

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.