GRASS messages translation

GRASS messages translation project

Many users prefer to use software in their mother tongue which is mostly no English. This requires that all GRASS software messages have to be translated to languages other than English. The GRASS Development Team is seeking translators. Please subscribe to the dedicated mailing list at

    GRASS translations mailing list
    http://lists.osgeo.org/mailman/listinfo/grass-translations

Translation related issues may be discussed there. This is an opportunity for non-programmers to contribute as messages can be easily translated. No programming skills required!

• Join the team

Wanted languages

Simple Chinese, Swahili, Hindi, Greek, Tamil, Russian, Telugu, Português, ... Please join us!

How to change the language

• see Testing different languages below.

How to create new translations

• For terminology, please refer to the GRASS Translation Glossary.

Files

In GRASS, we have 4 types of .po files per language (see in the source code the directory locale/po/):

• grasslibs_LANG.po: messages from libraries
• grassmods_LANG.po: messages from commands ("modules")
• grasstcl_LANG.po: messages from Tcl/Tk graphical user interface (GRASS 6)
• grasswxpy_LANG.po: messages from wxgrass/wxPython graphical user interface

where "LANG" in the above file names is a two character code which indicates the language. It is based on the Alpha-2 code of ISO 639-1 (right column). Example: grasswxpy_pl.po for Polish.

Continuing an existing translation

The file(s) are there but partially outdated? Read on.

First announce on the GRASS translations mailing list that you plan to continue the translation of a certain lanuage. Why? Because sometimes people silently translate already and we need these efforts to be coordinated to avoid doing it twice...

Then get these four .po files for your language and start. If a file is missing, just ask on the list to get it generated or see next section. To get these .po files (the files are in the directory locale/po/):

• either download current .po files directly from SVN (click on file name to download),
• or download source code package from SVN,
• or download the recent source code snapshot,
• or ask on the GRASS translations mailing list for these files.

Then edit the files with a .po file editor (poEDIT or kbabel or..., see below). Take care to maintain layout and special characters. And submit often - if you wait for weeks, the messages may already be outdated and your time wasted. Just keep in touch on the GRASS translations mailing list!

Starting a new translation

The language you want isn't yet there? Read on.

Briefly, the steps to create new messages files are (if you find this too complicated, ask on the GRASS translations mailing list to get these files done for you!):

1. Get the latest source code development version from either the SVN repository or as SVN snapshot (see Download).
2. run: './configure --with-nls [... other parameters]' to configure the GRASS source code
3. run: 'cd locale' to change into the translation directory
4. run: 'make pot' to create grass*.pot template files (to extract original messages)
5. run: copy these file from templates/ into po/; rename them to contain the two characters language code (see Alpha-2 code of ISO 639-1) and to .po extension; update the file headers either manually or with your .po editing software

 (Example: Polish language):
	        mv ./templates/grasslibs.pot ./po/grasslibs_pl.po
	        mv ./templates/grassmods.pot ./po/grassmods_pl.po
	        mv ./templates/grasstcl.pot ./po/grasstcl_pl.po
	        mv ./templates/grasswxpy.pot ./po/grasswxpy_pl.po

Now translate the messages in these po/*.po files (using kbabel or other editor, see below)

From time to time messages need to be updated from the originals. This is usually done by the GRASS translation manager.

Software to translate: .po file editors

• kbabel: KBabel is a set of tools for editing and managing gettext PO files (should come with your Linux distibution)
• poEdit: poEdit is cross-platform gettext catalogs (.po files) editor (works also under MS-Windows)
• Web based solution Transifex

Kbabel - rough, automated translation from existing .po files

To load existing .po files (eg from older GRASS versions or KDE translator center, http://i18n.kde.org/teams/) into Kbabel, use

     KBABEL -> SETTINGS -> CONFIGURE DIRECTORY -> PO AUXILIARY, load .po file

Then KBABEL -> TOOLS -> ROUGH TRANSLATION and some work might be done for you by kbabel...

Testing different languages

Testing different languages requires that the respective language environment and, if needed, fonts are installed. Check what languages are currently installed on your system with:

 locale -a

To change to a certain language environment (locale), do the following steps (here, example for Unix style environment):

  1. Define/check language settings:
    echo $LANG
    echo $LANGUAGE
    echo $LC_MESSAGES
 
  2. Change it (example for to Japanese):
   a) bash shell:
        export LANG=ja_JP.UTF-8
        export LANGUAGE=ja_JP.UTF-8
        export LC_MESSAGES=ja_JP.UTF-8
 
 
   b) (t)csh shell:
        setenv LANG ja_JP.UTF-8
        setenv LANGUAGE ja_JP.UTF-8
        setenv LC_MESSAGES ja_JP.UTF-8

Now launch GRASS in this terminal. If you launch it from an icon, you have to change the LOCALE in the computer setup program instead.

Other common languages useful for testing are de_DE for German, fr_FR for French, or "C" for none (effectively en_US, which for GRASS is the base language).

Creating startup scripts for different languages

GRASS in English language, save as "grass64eng" (executable flag set, store in path):

     #!/bin/sh
     export LANG=en_US
     export LANGUAGE=en_US
     export LC_MESSAGES=en_US
     exec grass64 "$@"

GRASS in Japanese language, save as "grass64ja" (executable flag set, store in path):

     #!/bin/sh
     export LANG=ja_JA.UTF-8
     export LANGUAGE=ja_JA.UTF-8
     export LC_MESSAGES=ja_JA.UTF-8
     grass64 "$@"

Coordination among translators

If several translators work on the same language files, obviously some coordination is needed. Please announce work via the "translations" mailing list at http://lists.osgeo.org/mailman/listinfo/grass-translations

Also the translation manager is listening there to the upload the changed files into the GRASS source code repository.