Translations: Difference between revisions

From Official Kodi Wiki
Jump to navigation Jump to search
>Mad-max
(Created page with "== General == In the development cycle from Eden (V12) to Frodo (V12) the translation system has been revised. The former strings.xml file has been superseeded by the appropria...")
 
m (Updated for v20)
 
(92 intermediate revisions by 11 users not shown)
Line 1: Line 1:
== General ==
{{mininav|[[Development]] {{l2|[[Language portal]]}} {{l2|[[Add-on development]]}} }}
In the development cycle from Eden (V12) to Frodo (V12) the translation system has been revised.


The former strings.xml file has been superseeded by the appropriate strings.po files.
{{see also|Add-on development}}
Due to that the way how translations are handled has been changed, too.


== Transifex ==
= History =
The whole translation system has been moved to [http://www.transifex.net Transifex].
In the development cycle from Eden (V11) to Frodo (V12) the translation system has been revised.<br/>
So if you want to help translating XBMC into your native language, first thing you need to do is to sign up at Transifex.
The former strings.xml file has been superseeded by the appropriate GNU gettext strings.po files.
<br/><br/>
[https://kodi.tv/article/switching-translations-to-weblate/ In 2021 Kodi switched translation platform to Weblate.]


= Weblate =
The whole translation system has been moved to [https://kodi.weblate.cloud/ Weblate].<br/><br/>
Addon developers should read this page for information on how to translate add-ons: [[Translating_add-ons|Translating your add-on]]
<br/><br/>
If you want to help translating Kodi into your native language, first thing you need to do is to [https://kodi.weblate.cloud/accounts/register/ sign up at Weblate].<br/> 
You can create a new account or use an existing Google, Facebook or Github account.<br/>
Please visit [https://forum.kodi.tv/showthread.php?tid=363132 this forum post] to let us know which language you would like to translate.<br/> 
Once added to a langage team, you can start translating immediately.
<br/><br/>
== Profile ==
In the top right, you can find your profile settings:
<br/><br/>
[[File:Weblate_profile_settings.png|300px|Weblate profile settings]]
<br/><br/>
In the '''Language tab''' you can select the interface language, the language you can translate to and your secondary languages:
<br/><br/>
[[File:Weblate language settings new.png|900px|Weblate language settings]]
<br/><br/>
In the '''Notifications tab''' you can select your watched projects.<br/>
Those projects can be selected in the top Projects menu.<br/>
''We recommend selecting all projects to have easy access to all components.''
<br/><br/>
[[File:Weblate watched.png|900px|Weblate watched projects settings]] 


Next Step would be to check the current project for XBMC. Currently it is this one:


[https://www.transifex.net/projects/p/XBMC-Main-Frodo/ XBMC Main Translation Project (Frodo)]
Now you are ready to translate components:
<br/><br/>
[[File:Weblate.png|900px|Weblate main screen]]
<br/> 
<br/>


== Translating Kodi and other components ==
''Note: Please do not download files, modify them and upload again! Always translate components and strings inside Weblate!''
<br/><br/>
Ok, let's get to work!
<br/><br/>
Search that part of the project that needs updating.<br/>
You can see the percentage of the translations, untranslated strings / words / characters:
<br/><br/>
[[File:Weblate components.png|900px|Components at Weblate]]
<br/><br/>
You might note that there is some untranslated strings in "Kodi core/kodi main".<br/>
So we click either on the pencil to the left or on the language label to translate it:
<br/><br/>
[[File:Weblate component hl close.png|700px|Translate buttons highlighted]]
<br/><br/>
The next screen will show you all information on the chosen language.<br/><br/>
We recommend to take care of most alerts: BBcode markup, mismatched \n, mismatching line breaks, XML markup, starting spaces, trailing spaces, double space, unchanged translations.<br/>
Keeping alerts might break the file and ultimately lead to Kodi crashing.<br/>
Alerts can be cleared when selecting the string with the alert.<br/><br/>
[[File:Weblate translate1.png|900px|Translate window inside Weblate]]
<br/><br/>
If you want to translate the component, '''"Not translated strings"''' is where to go.<br/>
<br/>
Clicking any item in the previous image will take you here:
<br/><br/>
[[File:Weblate translate.png|900px]]
<br/><br/>
* <span style="color:#00e235">'''SOURCE STRING COMMENT:'''</span> The developers can create useful comments for the string, e.g. what it exactly does or where it can be found in the GUI.
* <span style="color:red">'''GLOSSARY:'''</span> View the glossary entries matching your current string. You can also add new glossary entries.
* <span style="color:#de00ff">'''NBS:'''</span> "No-break space" is a character used if you can't translate the source string into your native language. It's useful for languages that don't have certain words. It will not take up any character space and will not use the source string.
* <span style="color:#00b4ff">'''REVIEW STATE:'''</span> Reviewers/coordinators can approve strings or mark them for editing.
* <span style="color:orange">'''AUTOMATIC SUGGESTIONS:'''</span> Matching strings and translations from other components will be listed here. This is great for keeping consistency. We recommend keeping this tab open when translating.
<br/>
[[File:Weblate translate colors.png|1000px|Colors explaining Weblate translate window]]
<br/><br/>
'''Other languages tab''' is great for looking at the current string translated into other languages. Works well for closely related languages.
<br/><br/>
[[File:Weblate other languages.png|900px|Other languages tab at Weblate]]
<br/><br/>
'''Comments tab''': Here you can make comments on the current string for other translators, reviewers and developers to read.<br/>
You can also make source string comments or suggestions for changes to the string.
<br/><br/>
[[File:Weblate comments2.png|900px|Comments for strings]]
<br/><br/>


On that page you should see the available languages that can be translated:
= Useful hints =
 
This part shows some additional information for developers and translators to make things more easy. So it's worth taking a look.
 
[[File:Lang_overview.png]]
 
 
Check your native language and request to join the translation team. In this example I choose Greek:
 
 
[[File:Join.png]]
 
The appropriate coordinator of your language will approve or deny your request.
 
By approval you can start translating immediately.
 
Currently this project is for core XBMC only! So no third party addons or stuff like that!
 
This will follow later on. So stay tuned in the [http://forum.xbmc.org/forumdisplay.php?fid=90 appropriate forums section for translations]
 
== Translating XBMC ==
''Note: Please do not download files, modify them and upload again! Always use the "Translate Now" Button!''
 
Ok, let's get to work!


Search that part of the project that needs updating. You can see the percentage of the translations to the right:


[[File:Select_ressource.png]]
== Details & Comments ==
The developers can set special marks in the strings.po file to give a useful comment on that string. e.g. what it exactly does or where it can be found in the GUI.
<br/><br/>
[[File:Weblate comments.png|900px|Comments in a string]]


You might note that there is something missing in "visualisation milkdrop". So we click on it to translate it.


The red marked area is button mentioned before. Always use this one!
In the source file it looks like this:
<syntaxhighlight lang="xml" enclose="div">
#. play GUI sounds
#: xbmc/settings/GUISettings.cpp
msgctxt "#34122"
msgid "Always"
msgstr ""
</syntaxhighlight>


[[File:Translate_now.png]]


Check the missing strings on the right side. After you completed them hit the "Save and Exit" button down on the left.
With #. we can add a helper comment or context to help translators understand the meaning or usage of string.


[[File:Translating_string.png]]
with #: we can specify where the string is used. Sometimes this could also be a useful info.


== Addons ==
= Contact and support =
Currently this part is under construction as there will be another project for 3rd party addons later on.
If you have problems with Weblate your first person to contact should be the coordinator of your language!


== Contact ==
If you have more general questions you might [https://forum.kodi.tv/forumdisplay.php?fid=90 head over to the forums and post your question in the translations section].<br/>
If you have problems with Transifex your first person to contact should be the coordinator of your language!
Gade and others can help you there.<br/><br/>
Or you can join the [https://forum.kodi.tv/showthread.php?tid=370465 official channel at Slack for all language and translation related discussions.]


If you have more general questions you might head over to the forums and post your question in the translation are there.
= Sync time schedule =
Alanwww1 and others can help you there.
For Kodi language add-ons, new versions are released every time a Weblate pull request is merged.<br/>
It depends how many translations are done for a specific language, but usually new versions are released once a month.


{{updated|20}}
{{top}}


[[Category:Development|*]]
[[Category:Development|T]]
[[Category:Languages]]

Latest revision as of 18:58, 8 February 2023

Home icon grey.png   ▶ Development
▶ Language portal
▶ Add-on development		 ▶ Translations
See also: Add-on development

History

In the development cycle from Eden (V11) to Frodo (V12) the translation system has been revised.
The former strings.xml file has been superseeded by the appropriate GNU gettext strings.po files.

In 2021 Kodi switched translation platform to Weblate.

Weblate

The whole translation system has been moved to Weblate.

Addon developers should read this page for information on how to translate add-ons: Translating your add-on

If you want to help translating Kodi into your native language, first thing you need to do is to sign up at Weblate.
You can create a new account or use an existing Google, Facebook or Github account.
Please visit this forum post to let us know which language you would like to translate.
Once added to a langage team, you can start translating immediately.

Profile

In the top right, you can find your profile settings:

Weblate profile settings

In the Language tab you can select the interface language, the language you can translate to and your secondary languages:

Weblate language settings

In the Notifications tab you can select your watched projects.
Those projects can be selected in the top Projects menu.
We recommend selecting all projects to have easy access to all components.

Weblate watched projects settings


Now you are ready to translate components:

Weblate main screen

Translating Kodi and other components

Note: Please do not download files, modify them and upload again! Always translate components and strings inside Weblate!

Ok, let's get to work!

Search that part of the project that needs updating.
You can see the percentage of the translations, untranslated strings / words / characters:

Components at Weblate

You might note that there is some untranslated strings in "Kodi core/kodi main".
So we click either on the pencil to the left or on the language label to translate it:

Translate buttons highlighted

The next screen will show you all information on the chosen language.

We recommend to take care of most alerts: BBcode markup, mismatched \n, mismatching line breaks, XML markup, starting spaces, trailing spaces, double space, unchanged translations.
Keeping alerts might break the file and ultimately lead to Kodi crashing.
Alerts can be cleared when selecting the string with the alert.

Translate window inside Weblate

If you want to translate the component, "Not translated strings" is where to go.

Clicking any item in the previous image will take you here:

Weblate translate.png

  • SOURCE STRING COMMENT: The developers can create useful comments for the string, e.g. what it exactly does or where it can be found in the GUI.
  • GLOSSARY: View the glossary entries matching your current string. You can also add new glossary entries.
  • NBS: "No-break space" is a character used if you can't translate the source string into your native language. It's useful for languages that don't have certain words. It will not take up any character space and will not use the source string.
  • REVIEW STATE: Reviewers/coordinators can approve strings or mark them for editing.
  • AUTOMATIC SUGGESTIONS: Matching strings and translations from other components will be listed here. This is great for keeping consistency. We recommend keeping this tab open when translating.


Colors explaining Weblate translate window

Other languages tab is great for looking at the current string translated into other languages. Works well for closely related languages.

Other languages tab at Weblate

Comments tab: Here you can make comments on the current string for other translators, reviewers and developers to read.
You can also make source string comments or suggestions for changes to the string.

Comments for strings

Useful hints

This part shows some additional information for developers and translators to make things more easy. So it's worth taking a look.


Details & Comments

The developers can set special marks in the strings.po file to give a useful comment on that string. e.g. what it exactly does or where it can be found in the GUI.

Comments in a string


In the source file it looks like this: 

#. play GUI sounds
#: xbmc/settings/GUISettings.cpp
msgctxt "#34122"
msgid "Always"
msgstr ""


With #. we can add a helper comment or context to help translators understand the meaning or usage of string.

with #: we can specify where the string is used. Sometimes this could also be a useful info.

Contact and support

If you have problems with Weblate your first person to contact should be the coordinator of your language!

If you have more general questions you might head over to the forums and post your question in the translations section.
Gade and others can help you there.

Or you can join the official channel at Slack for all language and translation related discussions.

Sync time schedule

For Kodi language add-ons, new versions are released every time a Weblate pull request is merged.
It depends how many translations are done for a specific language, but usually new versions are released once a month.

Return to top
Retrieved from "https://kodi.wiki/index.php?title=Translations&oldid=244196"