Difference between revisions of "Interface translation"

Latest revision as of 18:43, 6 June 2023

Go back to the main Translation information page.

Main translation files

1. Coordinate

As there may be other persons also currently working on the translation to your language, as a first step, please let your colleagues on the translators mailing list know that you'd like to start working on your language's translation, and coordinate your efforts (e.g. divide the work, set up a review system, … ). You can also check the mailing list archives to see whether there may be others who have started working on it recently. You can also ask for help finding previous translators for your language in the chat, to join their team.

2. Get the file

Get the most up-to-date translation files from GitLab's automatic builds:

For the main development branch: https://gitlab.com/inkscape/inkscape/-/jobs/artifacts/master/download?job=translations

For release branches: https://gitlab.com/inkscape/inkscape/-/jobs/artifacts/<branch name>/download?job=translations

The name of the release branch is usually something like '1.0.x' or '1.1.x'. You can ask on the mailing list or in the chat which branch is the current translation target.

In some cases, this will give a 'Page not found' error. In that case, visit the main Inkscape repository page on GitLab, select the correct branch at the top, then on the right side, click on the download icon and select to download the 'translations' artifact.

Unzip the downloaded file and select the po file for your language from it.

3. Translate

Translate the file for your language from the archive above with your favorite translation software.

Tip: if you encounter a case where, in the English text, the order of formatting arguments (numbers or text snippets that will be inserted into the string when the program runs) is different from the order in your language, and the arguments are not numbered in the original string, you can try this.

4. Test

Make sure you have the release of Inkscape you are translating installed. If you're translating the coming release, pick a pre-release and compile it.
Compile your PO file to .mo. Some translation tools (e.g. Poedit) have an option for that.
Find and replace your language's .mo file. It is a file named ‘locale/your_language/LC_MESSAGES/inkscape.mo’, in the directory listed under Edit > Preferences > System > Inkscape Data in Inkscape.
Note: This will not work with the snap, .dmg, AppImage or flatpak version of Inkscape, but only with a version that has been properly installed on your system and with extracted binary archives (zip files for Windows) or self-compiled versions. In some cases, you may need administrator privileges to edit files in said directory.
Rename the original inkscape.mo file to inkscape.mo.bak and save your compiled .mo file into its place as inkscape.mo instead
Then start Inkscape and you'll see your strings!

5. Get a GitLab account

If you don't have an account yet, now is the time to create one

6. Exchange the file on GitLab

For Inkscape 1.3.x, visit https://gitlab.com/inkscape/inkscape/-/blob/1.3.x/po/<your_locale>.po

For the main development branch, go to https://gitlab.com/inkscape/inkscape/-/blob/master/po/<your_locale>.po

Click on the "Replace" button and upload your translated file.

Enter your commit message below (something like "Update <your_locale>"). Choose a name for your branch. Do not use the same name as the target branch, but something like 'es_translations_for_1.3'.

7. Make a merge request

Click on the "Create merge request" button.

In the form, check 'Allow commits from members who can merge to the target branch' and also 'squash commits'.

Submit the merge request.

@@ Line 1: / Line 1: @@
 Go back to the main [[Translation information]] page.
-== Main translation file ==
+== Main translation files ==
-[https://gitlab.com/inkscape/inkscape/tree/master/po Download] the PO file for your language (or the .pot template). See [[Translation information#PO translation files|here]] to get information about how to deal with PO files.
+=== 1. Coordinate ===
-When you are done with your translation and enjoyed testing it, [[Translation information#Submit finished work|submit your work]].
+As there may be other persons also currently working on the translation to your language, as a first step, please let your colleagues on the translators mailing list know that you'd like to start working on your language's translation, and coordinate your efforts (e.g. divide the work, set up a review system, … ). You can also check the mailing list archives to see whether there may be others who have started working on it recently. You can also ask for help finding previous translators for your language in the chat, to join their team.
-=== Test ===
+=== 2. Get the file ===
+Get the most up-to-date translation files from GitLab's automatic builds:
+For the main development branch:
+https://gitlab.com/inkscape/inkscape/-/jobs/artifacts/master/download?job=translations
+For release branches:
+https://gitlab.com/inkscape/inkscape/-/jobs/artifacts/<branch name>/download?job=translations
+The name of the release branch is usually something like '1.0.x' or '1.1.x'. You can ask on the mailing list or in the chat which branch is the current translation target.
+In some cases, this will give a 'Page not found' error. In that case, visit the [https://gitlab.com/inkscape/inkscape/ main Inkscape repository page on GitLab], select the correct branch at the top, then on the right side, click on the download icon and select to download the 'translations' artifact.
+Unzip the downloaded file and select the po file for your language from it.
+=== 3. Translate ===
+Translate the file for your language from the archive above with your [https://wiki.inkscape.org/wiki/index.php/Translation_information#Tools_for_translators favorite translation software].
+Tip: if you encounter a case where, in the English text, the order of formatting arguments (numbers or text snippets that will be inserted into the string when the program runs) is different from the order in your language, and the arguments are not numbered in the original string, [https://gitlab.com/inkscape/inbox/-/issues/6544#note_996695887 you can try this].
+=== 4. Test ===
 # Make sure you have the release of Inkscape you are translating installed. If you're translating the coming release, pick a pre-release and compile it.
 # Compile your PO file to .mo. Some translation tools (e.g. Poedit) have an option for that.
-# Find the .mo of your installation of Inkscape for your locale. It should be in a folder named ‘locale’.
+# Find and replace your language's .mo file. It is a file named ‘locale/your_language/LC_MESSAGES/inkscape.mo’, in the directory listed under '''Edit > Preferences > System > Inkscape Data''' in Inkscape. <br>''Note: This will not work with the snap, .dmg, AppImage or flatpak version of Inkscape, but only with a version that has been properly installed on your system and with extracted binary archives (zip files for Windows) or self-compiled versions. In some cases, you may need administrator privileges to edit files in said directory.''
-## For Windows OS go to: '''INKSCAPE_DIR/share/local/your_language/LC_MESSAGES/inkscape.mo'''
+# Rename the original inkscape.mo file to inkscape.mo.bak and save your compiled .mo file into its place as inkscape.mo instead
-# Backup this .mo and put your compiled .mo instead. Then start Inkscape and you'll see your strings!
+# Then start Inkscape and you'll see your strings!
+=== 5. Get a GitLab account ===
+If you don't have an account yet, now is the time to [https://gitlab.com/users/sign_up create one]
+=== 6. Exchange the file on GitLab ===
+For Inkscape 1.3.x, visit
+<code><nowiki>https://gitlab.com/inkscape/inkscape/-/blob/1.3.x/po/<your_locale>.po</nowiki></code>
+For the main development branch, go to
+<code><nowiki>https://gitlab.com/inkscape/inkscape/-/blob/master/po/<your_locale>.po</nowiki></code>
+Click on the "Replace" button and upload your translated file.
+Enter your commit message below (something like "Update <your_locale>"). Choose a name for your branch. Do not use the same name as the target branch, but something like 'es_translations_for_1.3'.
+=== 7. Make a merge request ===
+Click on the "Create merge request" button.
+In the form, check 'Allow commits from members who can merge to the target branch' and also 'squash commits'.
+Submit the merge request.
+<!--
 == Windows installer ==
-# Get the file according to your language [http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/files/head:/packaging/win32/languages/ here]. If there's no such file, copy the ‘English.nsh’ file and rename it to ‘YourLanguage.nsh’ (make sure someone updates the file [http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/view/head:/packaging/win32/languages/_language_lists.nsh _language_lists.nsh] in this case).
+# Get the file according to your language [https://gitlab.com/inkscape/inkscape/tree/master/packaging/win32/languages here]. If there's no such file, copy the ‘English.nsh’ file and rename it to ‘YourLanguage.nsh’ (make sure someone updates the file [https://gitlab.com/inkscape/inkscape/blob/master/packaging/win32/languages/_language_lists.nsh _language_lists.nsh] in this case).
 # Translate the strings in the file.
 # Change/update header information in ‘YourLanguage.nsh’ (language name, [https://msdn.microsoft.com/en-us/goglobal/bb895996.aspx locale ID] and authors list) to proper values.
@@ Line 40: / Line 87: @@
 To translate the default template, you can use Inkscape as well as any UTF-8 encoding capable text editor.
+-->
 [[Category:Translation]]