Translations
The team does not control or manage the translations, we just periodically pull those from for languages that are 75% complete to include them into the current development stream.
-
Run the script
update-loc.cmd
that you will find at the repository root folder. -
As a result, you should see two changed files:
English.xlf
andEnglish.Plugins.xlf
(optional)⚠️ If you have the Plugin Manager installed, do not commit the following addition because the AppVeyor build would fail:<file datatype="plaintext" original="Plugin" source-language="en"> <body> <trans-unit id="Description.Text"> <source>Plugin Manager</source> <target /> </trans-unit> </body> </file>
(On AppVeyor, we run the translations before we import the Plugin Manager, thus no entry for it would be added.)
-
Create a PR
-
Open your favourite command line and run the following command:
PS> .\build.cmd -loc
-
As a result, you should see two changed files:
English.xlf
andEnglish.Plugins.xlf
(optional)⚠️ If you have the Plugin Manager installed, do not commit the following addition because the AppVeyor build would fail:<file datatype="plaintext" original="Plugin" source-language="en"> <body> <trans-unit id="Description.Text"> <source>Plugin Manager</source> <target /> </trans-unit> </body> </file>
(On AppVeyor, we run the translations before we import the Plugin Manager, thus no entry for it would be added.)
-
Create a PR
The translations are managed by a community at .
Note: To help you, you could have a look at the git .po translation file of your languages as a reference on how some git notions are translated. Some languages has even a lexicon at the top of the file for git main notions.