Difference between revisions of "Interface translation"

Revision as of 23:24, 16 July 2016

Go back to the main Translation information page.

Main translation file

Get the PO file for your language

Download the PO file for your language from here. See here to get information about how to deal with PO files.

If a PO file for your language does not yet exist, then you will have to get an empty template file to start a new translation. You may also need to use the updated template file (mentioned below) to bring the PO file up to date with new strings introduced in the UI. The most straightforward way to obtain the ‘inkscape.pot’ template is to download it from here.

When you are done with your translation, submit your work.

Using Bazaar

Alternatively, you can checkout the full Bazaar project repository and generate the project template. Information on how to get the source tree can be found here. Then, you have to follow some steps in order to generate the template:

./autogen.sh
./configure
Enter the ‘po’ directory: cd po
Generate the current PO template: intltool-update --pot

To make an absolutely up-to-date translation (in case the PO file in bzr is not up-to-date enough):

Update your local copy of Inkscape in the usual way: bzr pull
Merge your existing translations into the new POT file (inkscape.pot):
msgmerge your_latest_PO_file inkscape.pot > new_PO_file

If you want to update all PO files in po/, cd there and run: make update-po

Windows installer

Get the file according to your language here. If there is not such a file, copy the ‘English.nsh’ file and rename it to ‘YourLanguage.nsh’.
Translate the strings in the file.
Change header information in ‘YourLanguage.nsh’ (language name, local ID, windows code page and authors list) to proper values.
Optionally, test your translation as described below.
Submit your work (specify whether you tested it or not).

Testing the translation

This part is optional but recommended.

Install NSIS.
Run the make -f Makefile.mingw dist command after successful compilation of Inkscape. This command prepares binary of Inkscape for installer creation.
Add the filename of your file to the ‘inkscape.nsi’ file (in the parent folder) in the ; Localization section (with other languages).
Right-click on the ‘inkscape.nsi’ file and choose ‘Compile NSIS Script’. The installer compilation will start.
When the installer is finished, run it to test your translations for the installer and the uninstaller.

Default template

To translate the default template:

Modify the ‘default.svg’ file and save it as ‘default.xx.svg’ where ‘xx’ is the ISO code of your language. You will find the current template here.
Modify your PO translation to use your localized default template. Look up for a ‘default.svg’ string and translate it accordingly to the file name of the localized template.
To test your template, save it as well as the compiled PO file (.mo) to the proper location for your system and restart Inkscape. New documents should now be based on your localized template (this is valid if your system is properly set to your locale).
Submit your work.

To translate the default template, you can use Inkscape as well as any UTF-8 encoding capable text editor.

@@ Line 3: / Line 3: @@
 == Main translation file ==
-See [[Translation information#PO translation files|here]] to get information about how to deal with PO files.
+=== Get the PO file for your language ===
-=== Get the PO file for your language ===
+Download the PO file for your language from [http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/files/head:/po/ here]. See [[Translation information#PO translation files|here]] to get information about how to deal with PO files.
-Download the .po file for your language from [http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/files/head:/po/ here].
+If a PO file for your language does not yet exist, then you will have to get an empty template file to start a new translation. You may also need to use the updated template file (mentioned below) to bring the PO file up to date with new strings introduced in the UI. The most straightforward way to obtain the ‘inkscape.pot’ template is to download it from [http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/annotate/head:/po/inkscape.pot here].
-If a .po file for your language does not yet exist, then you will have to get an empty template file to start a new translation.
+When you are done with your translation, [[Translation information#Submit finished work|submit your work]].
-You may also need to use the updated template file (mentioned blow) to bring the .po file up to date with new strings introduced in the UI.
-The most straightforward way to obtain the inkscape.pot template is to download it from [http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/annotate/head:/po/inkscape.pot here].
+=== Using Bazaar ===
 Alternatively, you can checkout the full Bazaar project repository and generate the project template. Information on how to get the source tree can be found [https://inkscape.org/develop/inkscape-bzr/ here]. Then, you have to follow some steps in order to generate the template:
@@ Line 26: / Line 25: @@
 # Merge your existing translations into the new POT file (inkscape.pot):<br/> <code>msgmerge your_latest_PO_file inkscape.pot > new_PO_file</code>
-If you want to update ALL .po files in po/, cd there and run:
+If you want to update '''all''' PO files in po/, cd there and run: <code>make update-po</code>
-<pre>
-make update-po
-</pre>
-Now that you have an empty PO template, you can start translating the messages.
-=== Locale Testing ===
-Before reporting that a locale doesn't work in Inkscape, you need to make sure that your system has that locale correctly set up. To do this, you need to generally find a way to run ‘locale-gen’ (under Debian/Ubuntu this is via <code>dpkg-reconfigure locales</code>). If you set both the LANG and LANGUAGE variables and check a regular tool, you should see the correct language for both the libc error (first line) and the tool error (second line):
-<pre>
-LANG=es_MX LANGUAGE=es_MX ls -z
-ls: opción inválida -- z
-Pruebe `ls --help' para más información.
-</pre>
-If it reports the regular C messages, your locale has not been correctly configured, and you'll need to find the right way to run ‘locale-gen’ for your distribution:
-<pre>
-LANG=es_ES LANGUAGE=es_MX ls -z
-ls: invalid option -- z
-Try `ls --help' for more information.
-</pre>
-=== Submit finished work ===
-Upload your work via the [https://bugs.launchpad.net/inkscape/ Launchpad bug tracker]. Report a new bug and attach your translated file to it. Don't forget to compress your file before uploading it.
-Additionally, you may send a message to Inkscape's translators mailing list.
 == 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 is not such a file, copy the ‘English.nsh’ file and rename it to ‘YourLanguage.nsh’.
-# Translate strings in the file.
+# Translate the strings in the file.
-# Change header information in ‘YourLanguage.nsh’ file (language name, [https://msdn.microsoft.com/en-us/goglobal/bb895996.aspx local ID], [https://msdn.microsoft.com/en-us/goglobal/bb964654 windows code page] and authors list) to proper values.
+# Change header information in ‘YourLanguage.nsh’ (language name, [https://msdn.microsoft.com/en-us/goglobal/bb895996.aspx local ID], [https://msdn.microsoft.com/en-us/goglobal/bb964654 windows code page] and authors list) to proper values.
+# Optionally, test your translation as described below.
+# [[Translation information#Submit finished work|Submit your work]] (specify whether you tested it or not).
 === Testing the translation ===
@@ Line 71: / Line 43: @@
 # Right-click on the ‘inkscape.nsi’ file and choose ‘Compile NSIS Script’. The installer compilation will start.
 # When the installer is finished, run it to test your translations for the installer and the uninstaller.
-# If the translation is tested successfully, submit it to the [https://bugs.launchpad.net/inkscape/ Launchpad bug tracker] and mark as ‘Translation’.
-If you submit your translation but haven't tested it yet, enter this information to the patch information. You will be contacted about its correctness.
 == Default template ==
@@ Line 80: / Line 49: @@
 * Modify the ‘default.svg’ file and save it as ‘default.xx.svg’ where ‘xx’ is the ISO code of your language. You will find the current template [http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/files/head:/share/templates/ here].
 * Modify your PO translation to use your localized default template. Look up for a ‘default.svg’ string and translate it accordingly to the file name of the localized template.
-* To test it, save it as well as the compiled PO file (.mo) to the proper location and restart Inkscape. New documents should now be based on your localized template (this is valid if your system is properly set to your locale).
+* To test your template, save it as well as the compiled PO file (.mo) to the proper location for your system and restart Inkscape. New documents should now be based on your localized template (this is valid if your system is properly set to your locale).
-* Upload your ‘default.xx.svg’ file to the bug tracker.
+* [[Translation information#Submit finished work|Submit your work]].
 To translate the default template, you can use Inkscape as well as any UTF-8 encoding capable text editor.
 [[Category:Translation]]