Difference between revisions of "User:Radenko/translate"

From GRASS-Wiki
Jump to: navigation, search
(0,1)
 
(ново)
Line 1: Line 1:
__TOC__
+
== 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!
  
GRASS ГИС пројект се развија под условима [http://www.gnu.org/copyleft/gpl.html ГНУ Опште јавне дозволе] [http://grass.ibiblio.org/devel/index.php јавно] од [http://grass.ibiblio.org/community/index.php добровољаца] из [http://mapserver.gdf-hannover.de/grassusers/map.phtml цјелог свијета].
+
* Join the [[GRASS_Translation_Team#Members_of_Translation_Team|team]]
  
GRASS се разликује од многих других ГИС програмских пакета кориштених међу пословним корисницима у томе што развијен и дијељен од корисника, корисницима; углавноим на добровољној основи, јавно, и дјељен је бесплатно.
+
=== Wanted languages ===
Нагласак је стављен на међуфункционалност и неограничен приступ подацима као и на прилагодивост и брзину развоја програма (обоје, додавање могућности и уклањање грешака).
 
  
* [[Gis_Concepts#How_the_Open_Source_software_development_model_works|Како функционише модел развоја Слободног софтвера]]
+
Simple Chinese, Swahili, Hindi, Greek, Tamil, Russian, Telugu, Português, ... Please join us!
  
* [http://en.wikipedia.org/wiki/Gpl Дискусија на википедији о ГНУ-у]
+
== How to change the language ==
  
=== GRASS Заједница и Развојни тим ===
+
* see [[GRASS_messages_translation#Testing_different_languages|Testing different languages]] below.
  
* [http://grass.ibiblio.org/community/index.php Заједница]
+
== How to create new translations ==
* [http://grass.ibiblio.org/community/team.php Развојни тим]
 
* [[GRASS_Translation_Team|Тим за превод]]
 
* [[PSC|GRASS комитет за вођење пројеката]]
 
  
=== Корисници-мапа ===
+
* For terminology, please refer to the [[GRASS Translation Glossary]].
* [http://mapserver.gdf-hannover.de/grassusers/map.phtml?winwidth=890&winheight=630&language=1&mapwidth=600&mapheight=400 Корисници GRASS-а у свијету]
 
* Опис нове [[GRASS-ове мапе корисника]]
 
  
=== ''Open Source Geospatial Foundation'' (ОСГео) ===
+
=== Files ===
* The new [http://www.osgeo.org/ Open Source Geospatial Foundation] (OSGeo.org) was established in Chicago. GRASS was proposed as founding project.
+
In GRASS, we have 4 types of .po files per language (see in the source code the directory locale/po/):
* [[Potential tasks and responsibilities]] (earlier proposal)
 
* [[GRASS Project Steering Commitee]] for the OSGeo Foundation
 
* [[GRASS Project Incubation]] at the OSGeo Foundation
 
* http://grass.osgeo.org/
 
  
=== Other Free GIS projects ===
+
* <tt>grasslibs_LANG.po</tt>: messages from libraries
 +
* <tt>grassmods_LANG.po</tt>: messages from commands ("modules")
 +
* <tt>grasstcl_LANG.po</tt>: messages from Tcl/Tk graphical user interface (GRASS 6)
 +
* <tt>grasswxpy_LANG.po</tt>: messages from wxgrass/wxPython graphical user interface
  
* [http://freegis.org FreeGIS.org]
+
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 [http://www.loc.gov/standards/iso639-2/php/English_list.php ISO 639-1] (right column). Example: <tt>grasswxpy_pl.po</tt> for Polish.
* [http://pkg-grass.alioth.debian.org/cgi-bin/wiki.pl The DebianGIS Project]
 
  
 +
=== Continuing an existing translation ===
  
== Getting Help ==
+
The file(s) are there but partially outdated? Read on.
  
=== Mailing lists ===
+
First '''announce''' on the [http://lists.osgeo.org/mailman/listinfo/grass-translations 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...
  
* The primary point of contact for GRASS user help and development coordination is on the [http://grass.ibiblio.org/community/support.php mailing lists]. The answers to many questions you may have will probably already have been addressed and will be waiting for you in the [http://grass.ibiblio.org/searchgrass.php mailing list archives].
+
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/):
  
* Because the mailing lists are so critical to the project's success, and support comes entirely from time-strapped volunteers and colleagues, we request some [[mailing list etiquette]] be followed.
+
* either [http://trac.osgeo.org/grass/browser/grass/trunk/locale/po download current .po files] directly from SVN (click on file name, then at page bottom click on 'Original Format' to get out the real file),
 +
* or [http://trac.osgeo.org/grass/wiki/DownloadSource#GRASS6.4 download source code package] from SVN,
 +
* or download the recent [http://grass.osgeo.org/grass64/source/snapshot/ source code snapshot],
 +
* or ask on the [http://lists.osgeo.org/mailman/listinfo/grass-translations GRASS translations mailing list] for these files.
  
=== IRC communication ===
+
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 [http://lists.osgeo.org/mailman/listinfo/grass-translations GRASS translations mailing list]!
  
IRC is live Internet Relay Chat. The GRASS project maintains a "chatroom" and if you are lucky there may be someone logged on who can give you a quick answer.
+
=== Starting a new translation ===
  
* [[How to participate in IRC communication]] (#grass, #osgeo, #gdal, #qgis, #mapserver and other channels)
+
The language you want isn't yet there? Read on.
  
=== Documentation ===
+
Briefly, the steps to create new messages files are (if you find this too complicated, ask on the [http://lists.osgeo.org/mailman/listinfo/grass-translations GRASS translations mailing list] to get these files done for you!):
  
* You've already discovered the wiki. Go forth and explore!
+
# Get the latest source code development version from either the SVN repository or as SVN snapshot (see [http://grass.osgeo.org/download/index.php Download]).
 +
# run: './configure --with-nls [... other parameters]' to configure the GRASS source code
 +
# run: 'cd locale' to change into the translation directory
 +
# run: 'make pot' to create grass*.pot template files (to extract original messages)
 +
# run: copy these file from templates/ into po/; rename them to contain the two characters language code (see Alpha-2 code of [http://www.loc.gov/standards/iso639-2/php/English_list.php 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)
  
== Community resources ==
+
From time to time messages need to be updated from the originals. This is usually done by the GRASS translation manager.
  
=== GRASS education (Free GIS education) ===
+
== Software to translate: .po file editors ==
  
The GRASS education (Free GIS education) wiki site offers a start to collect links, text documents and small images. Furthermore it provides a discussion platform to develop and collect approaches, techniques, exercises and course structures for people giving GRASS and/or other Free GIS courses.
+
* [http://kbabel.kde.org/ kbabel]: KBabel is a set of tools for editing and managing gettext PO files (should come with your Linux distibution)
 +
* [http://www.poedit.net/download.php poEdit]: poEdit is cross-platform gettext catalogs (.po files) editor (works also under MS-Windows)
 +
* [http://wiki.osgeo.org/wiki/Software_Translation_Portal Web based] solutions (not used yet for the GRASS project)
  
* [[GRASS_Education_(Free_GIS_education) | GRASS education (Free GIS education)]]
+
'''Kbabel - rough, automated translation from existing .po files'''
  
=== Promoting GRASS GIS ===
+
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
  
* [[GRASS promotion team]]
+
Then KBABEL -> TOOLS -> ROUGH TRANSLATION and some work might be done for you by kbabel...
* [[Promotional material]]
 
* [[GRASS migration hints]]
 
* [[GRASS Propaganda]]
 
  
=== Conferences ===
+
== Testing different languages ==
* [http://www.foss4g2007.org FOSS4G2007 - Free and Open Source Software for Geospatial 2007] Victoria, Canada September 24-27, 2007
 
* [http://www.foss4g2006.org/ FOSS4G2006 - Open Source Geospatial Communities Joint Conference] 12-15 September 2006 in Lausanne, Switzerland with GRASS workshops...
 
* [[GRASS related workshops and presentations]]
 
  
=== GRASS Add-on modules ===
+
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
  
* [[GRASS AddOns]] software contributed by the community.
+
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_ALL
 +
 
 +
  2. Change it (example for to Japanese):
 +
    a) bash shell:
 +
        export LANG=ja_JP
 +
        export LANGUAGE=ja_JP
 +
        export LC_ALL=ja_JP
 +
 
 +
    b) (t)csh shell:
 +
        setenv LANG ja_JP
 +
        setenv LANGUAGE ja_JP
 +
        setenv LC_ALL ja_JP
  
 +
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 <tt>de_DE</tt> for German, <tt>fr_FR</tt> for French, or "C" for none (effectively <tt>en_US</tt>, which for GRASS is the base language).
  
[[Category: Community]]
+
<!-- == See also == -->
 +
 
 +
 
 +
[[Category: Development]]
 +
[[Category: Documentation]]
 +
[[Category: FAQ]]

Revision as of 14:30, 26 August 2009

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!

Wanted languages

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

How to change the language

How to create new translations

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/):

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 solutions (not used yet for the GRASS project)

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_ALL
 
  2. Change it (example for to Japanese):
   a) bash shell:
        export LANG=ja_JP
        export LANGUAGE=ja_JP
        export LC_ALL=ja_JP
 
   b) (t)csh shell:
        setenv LANG ja_JP
        setenv LANGUAGE ja_JP
        setenv LC_ALL ja_JP

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).