Difference between revisions of "Interface translation"

From Inkscape Wiki
Jump to navigation Jump to search
(Update for move to gitlab)
(7 intermediate revisions by 2 users not shown)
Line 3: Line 3:
== Main translation file ==
== Main translation file ==


See [[Translation information#PO translation files|here]] to get information about how to deal with PO 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.


=== Get the PO file for your language ===
When you are done with your translation and enjoyed testing it, [[Translation information#Submit finished work|submit your work]].


Download the .po file for your language from [http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/files/head:/po/ here].
=== Test ===


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.
# 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.
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.
# 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’.
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].
# Backup this .mo and put your compiled .mo instead. Then start Inkscape and you'll see your strings!
 
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:
 
# <code>./autogen.sh</code>
# <code>./configure</code>
# Enter the ‘po’ directory: <code>cd po</code>
# Generate the current PO template: <code>intltool-update --pot</code>
 
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: <code>bzr pull</code>
# 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:
<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 ==
== 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’.
# 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).
# 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/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.
# Save the file. (Translation files should always use Unicode, encoded as UTF8!).
# 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 ===
=== Test ===


This part is optional but recommended.
# [[Compiling Inkscape|Compile Inkscape]] (you'll probably want to [[Compiling Inkscape on Windows|Compile Inkscape on Windows]]) and run <code>make install</code> to create the binary distribution directory of Inkscape.
# Install [http://nsis.sourceforge.net/Main_Page NSIS].
# Install [http://nsis.sourceforge.net/Main_Page NSIS].
# Run the <code>make -f Makefile.mingw dist</code> 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 <code>; Localization</code> section (with other languages).
# Right-click on the ‘inkscape.nsi’ file and choose ‘Compile NSIS Script’. The installer compilation will start.
# 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.
# When the installer is ready, 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 ==
== Default template ==


To translate the 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 [http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/files/head:/share/templates/ here].
* 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 [https://gitlab.com/inkscape/inkscape/tree/master/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.
* 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.
To translate the default template, you can use Inkscape as well as any UTF-8 encoding capable text editor.


[[Category:Translation]]
[[Category:Translation]]

Revision as of 19:12, 9 June 2017

Go back to the main Translation information page.

Main translation file

Download the PO file for your language (or the .pot template). See here to get information about how to deal with PO files.

When you are done with your translation and enjoyed testing it, submit your work.

Test

  1. 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.
  2. Compile your PO file to .mo. Some translation tools (e.g. Poedit) have an option for that.
  3. Find the .mo of your installation of Inkscape for your locale. It should be in a folder named ‘locale’.
  4. Backup this .mo and put your compiled .mo instead. Then start Inkscape and you'll see your strings!

Windows installer

  1. Get the file according to your language here. If there's no such file, copy the ‘English.nsh’ file and rename it to ‘YourLanguage.nsh’ (make sure someone updates the file _language_lists.nsh in this case).
  2. Translate the strings in the file.
  3. Change/update header information in ‘YourLanguage.nsh’ (language name, locale ID and authors list) to proper values.
  4. Save the file. (Translation files should always use Unicode, encoded as UTF8!).
  5. Optionally, test your translation as described below.
  6. Submit your work (specify whether you tested it or not).

Test

  1. Compile Inkscape (you'll probably want to Compile Inkscape on Windows) and run make install to create the binary distribution directory of Inkscape.
  2. Install NSIS.
  3. Right-click on the ‘inkscape.nsi’ file and choose ‘Compile NSIS Script’. The installer compilation will start.
  4. When the installer is ready, 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.

Retrieved from "https://wiki.inkscape.org/wiki/index.php?title=Interface_translation&oldid=105386"