Difference between revisions of "TestPage"

From Inkscape Wiki
Jump to navigation Jump to search
Line 71: Line 71:
 
If you've never translated a PO file before, you will find its syntax very simple. The PO format is a really simple format, which probably at least partly explains its success and widespread use. The format is basically a hash list consisting of msgid and msgstr pairs, with the msgid being the original English string and key, and the msgstr being the translated value of it. Below is an example of a message.
 
If you've never translated a PO file before, you will find its syntax very simple. The PO format is a really simple format, which probably at least partly explains its success and widespread use. The format is basically a hash list consisting of msgid and msgstr pairs, with the msgid being the original English string and key, and the msgstr being the translated value of it. Below is an example of a message.
  
<nowiki>
+
  &#35;: gedit/dialogs/gedit-plugin-program-location-dialog.c:78
<p>
+
  &#35;: gedit/dialogs/program-location-dialog.glade2.h:2
#: gedit/dialogs/gedit-plugin-program-location-dialog.c:78<br>
+
  msgid "Set program location..."
#: gedit/dialogs/program-location-dialog.glade2.h:2<br>
+
  msgstr "Ställ in programplats..."
msgid "Set program location..."<br>
 
msgstr "Ställ in programplats..."<br>
 
</p>
 
</nowiki>
 
  
 
In addition to the msgid and msgstr parts, a message usually also has lines starting with #: that tells what source files and what lines the string used as msgid was extracted from. These lines have no syntactic value. They are only there as a help for translators and developers to know where a message came from.  
 
In addition to the msgid and msgstr parts, a message usually also has lines starting with #: that tells what source files and what lines the string used as msgid was extracted from. These lines have no syntactic value. They are only there as a help for translators and developers to know where a message came from.  
Line 87: Line 83:
 
* A new string has been added to the source, and the string is very similar, but not identical, to the msgid of an already existing, translated message. Then the msgstr of that message will be automatically reused for the new message, but the new message will also at the same time be marked fuzzy so that the translator knows there is some difference that he or she needs to adapt the translation to match.
 
* A new string has been added to the source, and the string is very similar, but not identical, to the msgid of an already existing, translated message. Then the msgstr of that message will be automatically reused for the new message, but the new message will also at the same time be marked fuzzy so that the translator knows there is some difference that he or she needs to adapt the translation to match.
  
There is always one special message in each valid PO file: the PO file header. It is encoded with the msgid for the empty string ("") as the key, and the actual header values are in the msgstr part. This unfortunately means that if you mark an empty string for translation, you will get the entire PO file header back as the "translation". In almost all cases this is probably not what you want. Hence, do not mark empty strings for translation.  
+
There is always one special message in each valid PO file: the PO file header. It is encoded with the msgid for the empty string ("") as the key, and the actual header values are in the msgstr part. This unfortunately means that if you mark an empty string for translation, you will get the entire PO file header back as the "translation". In almost all cases this is probably not what you want. Hence, do not mark empty strings for translation.
  
 
== Get the PO file for your language ==
 
== Get the PO file for your language ==

Revision as of 11:08, 31 May 2006

Introduction

Community based, user oriented

The translations of the various documents focusing on Inkscape rely on the work of volunteers. Motivation for this work can range from the simple pleasure to contribute to take the opportunity of learning a lot about Inkscape and translation processes. It is very important not to forget that Inkscape is an open source, community based and user oriented software, which implies that software developpers/contributors are generaly users. It also implies that the translation efforts are also user oriented, with a strong focus on interface, user documentation and website.

Guidelines/workflow

  1. Contact to a local translation group, to get support and help on your language. Rather than working alone, you should work with an experienced translation team for your language. Thus you will benefit from their knowledge, as well as being able to communicate with them on your own mother tongue. Moreover, translation teams use to have style guidelines and a standarized vocabulary for technical terms that you should be aware of. There may be many communities working on translations for your own language, but a good start point is subscribing to your local GNOME translation team or KDE translation team.
  2. Subscribe to Inkscape translator mailing list. By subscribing on Inkscape's translator list you will be able to ask for help on some questions more related to Inkscape issues to other Inkscape translators, as well as the mantainers.
  3. Get files for your language. If you only want to translate the interface messages, you can get the files from Inkscape's svn repository web interface. Besides getting files from web interface, you can obtain the full repository; instructions on how to do this are found here. See section #Translatable_content for which files you have to modify to translate each part of Inkscape.
  4. Submit finished work to patch tracker. Finished translations must be sent to patch tracker and/or mailing list in order to be integrated into the trunk. You will need a Sourceforge.net account to commit patches to Inkscape's patch tracker. Before sending a file, remember to check that the file you are submitting doesn't have syntax errors that would break the building process.
  5. Send a mail on the translator mailing list. Your contribution will be reviewed/commited as soon as possible.

Best practices

Best case for a good translation : translate from English to your mother tongue.

Test the behavior of the interface before starting translation

Translatable content

Inkscape's translation effort covers many areas, from aplication UI itself to web pages and tutorials. This is a summary of all those areas, ordered by priority.

These tasks, rather than being for hackers only, can be achieved by most software enthusiasts, whether they have a technological background or just plain users. The main requirement is the wish to provide support for Inkscape on your language: the technology required for do that has been developed in a simple approach, and it involves mainly text files and applications used to verify its syntax. Supporting applications exists to make this tasks even easier.

User interface

PO files contain the strings for the Inkscape user interface (main software and extentions). A PO file is a text file which contains the original English message and its translation. That's why it is obviously the translation to start with.

See section #Interface_Translation for information on PO files.

Tutorials

As you know, Inkscape comes with some very nice SVG tutorials. By translating them, users will learn how to use the application, as well its tips and tricks.

See section #Tutorial_Translation for information on translating tutorials.

Windows installer

High value for users, even if the installation process of Inkscape is quite simple, translating the Windows installer helps a lot potential users feeling good with Inkscape.

Templates

Release notes

Translating release notes helps giving a lot of visibility to Inkscape

- give a general overview of the possibilities of the software to potential users

- can be used for local marketing (local Free Software/Linuw/Graphics oriented web sites, articles in fanzines, e-magazines and even magazines...)

News displayed on Inkscape web site

Web pages

English is generaly the exchange-tongue of developppers, and developper/user documentation is mainly written in English.

Translation efforts should be first oriented on user documentation.

See the main pages of Inkscape and of this wiki to get some exemple of the translations of websites.


Others

Templates (translation and localization) Text files found in the inkscape directory ...

Interface Translation

Introduction to PO file format

If you've never translated a PO file before, you will find its syntax very simple. The PO format is a really simple format, which probably at least partly explains its success and widespread use. The format is basically a hash list consisting of msgid and msgstr pairs, with the msgid being the original English string and key, and the msgstr being the translated value of it. Below is an example of a message.

  #: gedit/dialogs/gedit-plugin-program-location-dialog.c:78
  #: gedit/dialogs/program-location-dialog.glade2.h:2
  msgid "Set program location..."
  msgstr "Ställ in programplats..."

In addition to the msgid and msgstr parts, a message usually also has lines starting with #: that tells what source files and what lines the string used as msgid was extracted from. These lines have no syntactic value. They are only there as a help for translators and developers to know where a message came from.

A message in a PO file can be in one of essentially three different states. The message can be translated, fuzzy, or untranslated. A message counts as translated as soon as the msgstr part of it is non-empty. In a similar manner, an untranslated message is one where the msgstr is empty. The fuzzy state is special and essentially means that there is a translation in the msgstr part, but that this translation is most likely not entirely correct, and that it thus needs manual attention by a translator. A message can become fuzzy in one of two ways:

  • The original string that the msgid represents was changed in the source code. A typo in the string may have been fixed or the string altered in some other way. The translator needs to check that the msgstr is still valid and make changes if necessary.
  • A new string has been added to the source, and the string is very similar, but not identical, to the msgid of an already existing, translated message. Then the msgstr of that message will be automatically reused for the new message, but the new message will also at the same time be marked fuzzy so that the translator knows there is some difference that he or she needs to adapt the translation to match.

There is always one special message in each valid PO file: the PO file header. It is encoded with the msgid for the empty string ("") as the key, and the actual header values are in the msgstr part. This unfortunately means that if you mark an empty string for translation, you will get the entire PO file header back as the "translation". In almost all cases this is probably not what you want. Hence, do not mark empty strings for translation.

Get the PO file for your language

Download the .po file for your language from here:

   http://svn.sourceforge.net/viewcvs.py/inkscape/inkscape/trunk/po/

If a .po file for your language does not yet exist, then you will have to get a current copy of the working tree from SVN repository in order to generate a template. This empty template contains only English messages. Information on how to get a the source tree can be found here.

Create your own language file by copying the inkscape.pot file that gets generated when you run make in the codebase.

1. "./autogen.sh"
2. "./configure"
3. enter the "po" directory: "cd po"
4. generate the current PO template: "intltool-update --pot"

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

1. update your local copy of Inkscape in the usual way: "svn update"
2. merge your existing translations into the new POT file (inkscape.pot):
   "msgmerge your_latest_PO_file inkscape.pot > new_PO_file"

Then you just need to complete the translations in the PO file that was created in step 6.

If you want to update ALL .po files in po/, cd there and run:

make update-po

Tools for translators

You can edit PO files from any plain text editor, since they are simple text files. However, many useful tools have been developed to provide a simple experience translating PO files.

And last but not least, gettext utils.

Submit finished work

Upload your work via the SourceForge patch tracker:

   http://sourceforge.net/tracker/?func=add&group_id=93438&atid=604308

(Check the Upload checkbox and add your file or patch.)

Additionally, you may send a message to Inskcape's translators mailing list.

A few important things to remember

  • Some strings that can ambiguous or having several meanings according to different contexts may have a context prefix : "Context|Amibiguous string". In this case, simply translate "Ambiguous string", the "Context|" string is just a not to translate indication.
  • After translating a fuzzy string (one that is marked with a ", fuzzy" comment), please remove its "fuzzy" tag -- otherwise this translation will be discarded by the build process, meaning that this string will show up untranslated. KBabel can do this automatically (see KBabel settings).
  • Before publishing your work (after you have finished updating the PO file), please update the "PO-Revision-Date" and "Last-Translator" fields in the PO file header. KBabel can do this automatically.

Review

This is the start of a list of places to get translation reviews done. So far:

 http://www.linux.it/tp/

Verification

Before submitting your file in the patch tracker, please make sure it is valid:

  • Make sure the file is encoded in UTF-8
  • Make sure it is a valid po file and obtain some statistics about it: simply run "msgfmt --statistics -cv translationFile.po" from a command window
  • Make sure it is correctly formatted: run "check-markup translationFile.po" from a command window and verify it doesn't output any error message. "check-markup" perl script can be found in the /po directory of Inkscape svn trunk

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 "dpkg-reconfigure locales".) 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):

LANG=es_MX LANGUAGE=es_MX ls -z
ls: opción inválida -- z
Pruebe `ls --help' para más información.

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:

LANG=es_ES LANGUAGE=es_MX ls -z
ls: invalid option -- z
Try `ls --help' for more information.

Programmers

Please make sure you use dgettext for any pluralized strings.

Tutorial Translation

Inkscape tutorial sources are in DocBook format, with illustrations in SVG. If you want to translate one or more tutorials, first download the DocBook source here:

http://svn.sourceforge.net/viewcvs.cgi/inkscape/doc-docbook/trunk/

Each tutorial is in its own subdirectory. You need the *.xml file, for example basic/tutorial-basic.xml. Get it and simply replace all English text in it with the text in your language, preserving all XML markup. See README at that location for some notes on markup.

  • If there's already such a file in SVN, you can edit it instead :) If there's no xml file at the above location but there's a translation of this tutorial in SVG format (in share/tutorials in Inkscape distribution), you'll need to convert it to DocBook (and probably update). Conversion can be done simply by: select the text blocks of an SVG tutorial in Inkscape, Ctrl+C, and Ctrl+V in your text editor, then add the markup.
  • Save your file as <original name>.<language suffix>.xml, for example basic/tutorial-basic.es.xml for Spanish.
  • Do not use symbolic entities like &aacute; (they're not defined in XML without a DTD). Instead use either numeric entities such as &#225; or simply write your text in UTF-8.
  • Most illustrations don't need translations, so you leave the references to them from English XML intact. If however an illustration has some text that you want to translate, open the illustration file in Inkscape (e.g. basic/basic-f12.svg), edit it as needed, and save under a different name (e.g. basic/basic-f12-es.svg). Then change the filename reference in the XML source appropriately.
  • When finished, run xmllint on your file to make sure it's well-formed.
  • Send the file to Joshua Andler <scislac at users dot sf dot net>, and he'll convert it to SVG and HTML and upload it to SVN and the web site.
  • If after that you want to make any changes, download the file from the above location again, because it may have changed compared to the one you have.

Tools

Transforming XML into PO files

One can also use xml2po to get PO files out of the XML sources, and also transform the PO files back to XML. After you have a PO file, follow the instructions for editing those files below.

xml2po is available in gnome-doc-utils (http://ftp.gnome.org/pub/gnome/sources/gnome-doc-utils/).

Here are some command lines that were used to translate a German tutorial (the de-locale), please adapt accordingly until we nicely integrate this into our Makefiles.

## use this at the very beginning, when there is no translation at all:
xml2po --output=basic/tutorial-basic.pot basic/tutorial-basic.xml

## use this when there is a *.de.xml, but you want a de.po:
xml2po --output=basic/de.po --reuse=basic/tutorial-basic.de.xml basic/tutorial-basic.xml

## xml2po is not happy when this directory doesn't exist:
mkdir .tmp.basic

## use this when the tutorial-basic.xml has been updated and you
## want the new stuff in your de.po:
xml2po --update-translation=basic/de.po basic/tutorial-basic.xml

## use this to create a tutorial-basic.de.xml from your de.po (ScislaC
## will use this file to create the final tutorial SVG file)
xml2po --po-file=basic/de.po basic/tutorial-basic.xml > basic/tutorial-basic.de.xml

Keyboard and mouse translation

Wiki and web site

Status

Interface translation (po files)

The names and e-mail addresses of contributors and last translator can be found in the header of the po file (simply open it with your favorite text editor)

Total number of PO files: 38 Total number of strings to translate: 2142


Amharic: am.po

translated: 77 ( 3%)

fuzzy: 592 ( 27 %), untranslated: 1473 ( 68%)

Date of last update: 2003-02-01


Azerbaijani/Turkic: az.po

translated: 63 ( 2%)

fuzzy: 853 ( 39 %), untranslated: 1226 ( 57%)

Date of last update: 2001-12-04


Belarusian: be.po

translated: 158 ( 7%)

fuzzy: 945 ( 44 %), untranslated: 1039 ( 48%)

Date of last update: 2003-07-20


Catalan: ca.po

translated: 2039 ( 95%)

fuzzy: 24 ( 1 %), untranslated: 79 ( 3%)

Date of last update: 2006-05-08


Czech: cs.po

translated: 2096 ( 97%)

fuzzy: 18 ( 0 %), untranslated: 28 ( 1%)

Date of last update: 2006-05-22


Danish: da.po

translated: 100 ( 4%)

fuzzy: 980 ( 45 %), untranslated: 1062 ( 49%)

Date of last update: 2002-01-15


German: de.po

translated: 2116 ( 98%)

fuzzy: 6 ( 0 %), untranslated: 20 ( 0%)

Date of last update: 2006-05-23


Greek: el.po

translated: 44 ( 2%)

fuzzy: 998 ( 46 %), untranslated: 1100 ( 51%)

Date of last update: 2001-12-28


Spanish: es.po

translated: 2125 ( 99%)

fuzzy: 6 ( 0 %), untranslated: 11 ( 0%)

Date of last update: 2006-05-25


Spanish/Mexico: es_MX.po

translated: 337 ( 15%)

fuzzy: 930 ( 43 %), untranslated: 875 ( 40%)

Date of last update: 2004-04-05


Estonian: et.po

translated: 9 ( 0%)

fuzzy: 778 ( 36 %), untranslated: 1355 ( 63%)

Date of last update: 2000-04-08


Basque: eu.po

translated: 1548 ( 72%)

fuzzy: 340 ( 15 %), untranslated: 254 ( 11%)

Date of last update: 2006-03-16


French: fr.po

translated: 2126 ( 99%)

fuzzy: 6 ( 0 %), untranslated: 10 ( 0%)

Date of last update: 2006-05-27


Irish: ga.po

translated: 14 ( 0%)

fuzzy: 719 ( 33 %), untranslated: 1409 ( 65%)

Date of last update: 2000-08-24


Galician: gl.po

translated: 82 ( 3%)

fuzzy: 963 ( 44 %), untranslated: 1097 ( 51%)

Date of last update: 2001-11-10


Hungarian: hu.po

translated: 1564 ( 73%)

fuzzy: 327 ( 15 %), untranslated: 251 ( 11%)

Date of last update: 2006-05-29


Italian: it.po

translated: 2008 ( 93%)

fuzzy: 65 ( 3 %), untranslated: 69 ( 3%)

Date of last update: 2006-05-15


Japanese: ja.po

translated: 1294 ( 60%)

fuzzy: 423 ( 19 %), untranslated: 425 ( 19%)

Date of last update: 2005-11-16


Korean: ko.po

translated: 180 ( 8%)

fuzzy: 18 ( 0 %), untranslated: 1944 ( 90%)

Date of last update: 2006-04-10


Lithuanian: lt.po

translated: 1774 ( 82%)

fuzzy: 30 ( 1 %), untranslated: 338 ( 15%)

Date of last update: 2006-05-02


mk.po

translated: 0 ( 0%)

fuzzy: 606 ( 28 %), untranslated: 1536 ( 71%)

Date of last update: 2003-06-15


Norwegian/bokmål dialect: nb.po

translated: 144 ( 6%)

fuzzy: 916 ( 42 %), untranslated: 1082 ( 50%)

Date of last update: 2003-01-25


Dutch: nl.po

translated: 1484 ( 69%)

fuzzy: 387 ( 18 %), untranslated: 271 ( 12%)

Date of last update: 2005-11-07


Norwegian/Nynorsk: nn.po

translated: 1376 ( 64%)

fuzzy: 410 ( 19 %), untranslated: 356 ( 16%)

Date of last update: 2005-07-14


Punjabi: pa.po

translated: 912 ( 42%)

fuzzy: 349 ( 16 %), untranslated: 881 ( 41%)

Date of last update: 2005-09-11


Polish: pl.po

translated: 1503 ( 70%)

fuzzy: 374 ( 17 %), untranslated: 265 ( 12%)

Date of last update: 2005-10-29


Portuguese: pt.po

translated: 183 ( 8%)

fuzzy: 1004 ( 46 %), untranslated: 955 ( 44%)

Date of last update: 2003-07-28


Portuguese/Brazillian: pt_BR.po

translated: 1546 ( 72%)

fuzzy: 349 ( 16 %), untranslated: 247 ( 11%)

Date of last update: 2006-04-27


Russian: ru.po

translated: 1542 ( 71%)

fuzzy: 339 ( 15 %), untranslated: 261 ( 12%)

Date of last update: 2005-11-08


Slovak: sk.po

translated: 845 ( 39%)

fuzzy: 659 ( 30 %), untranslated: 638 ( 29%)

Date of last update: 2005-02-13


Slovenian: sl.po

translated: 2055 ( 95%)

fuzzy: 27 ( 1 %), untranslated: 60 ( 2%)

Date of last update: 2006-05-12


Serbian: sr.po

translated: 1359 ( 63%)

fuzzy: 414 ( 19 %), untranslated: 369 ( 17%)

Date of last update: 2005-07-08


Serbian/Latine: sr@Latn.po

translated: 1359 ( 63%)

fuzzy: 414 ( 19 %), untranslated: 369 ( 17%)

Date of last update: 2005-07-08


Swedish: sv.po

translated: 410 ( 19%)

fuzzy: 848 ( 39 %), untranslated: 884 ( 41%)

Date of last update: 2005-10-08


Turkish: tr.po

translated: 907 ( 42%)

fuzzy: 567 ( 26 %), untranslated: 668 ( 31%)

Date of last update: 2005-11-26


Ukrainian: uk.po

translated: 1518 ( 70%)

fuzzy: 371 ( 17 %), untranslated: 253 ( 11%)

Date of last update: 2005-10-21


Chinese/Simplified: zh_CN.po

translated: 2134 ( 99%)


fuzzy: 3 ( 0 %), untranslated: 5 ( 0%)

Date of last update: 2006-05-28


Chinese/Traditional: zh_TW.po

translated: 1550 ( 72 %)

fuzzy: 340 ( 15 %), untranslated: 252 ( 11%)

Date of last update: 2006-03-24

Tutorials

  • Basic: ca, de, en, es, fr, ja, nn, ru, sl
  • Shapes: ca, en, es, fr, ja, sl
  • Advanced: ca, en, es, fr, ja, sl
  • Tracing: ca, de, en, es, fr, sl
  • Calligraphy: ca, en, es, fr, sl
  • Elements of design: en, es, fr, sl
  • Tips and tricks: de, en, es, fr, sl


Keys (shortcuts)

Already available in svn :

  • en
  • fr
  • sl


Windows installer

Already available in svn :

  • czech.nsh
  • english.nsh
  • german.nsh
  • italian.nsh

Wiki translation

Website

News