Live GIS Translate

This page describes how to translate documentation for the OSGeo-Live DVD.

Getting Started

Thanks for considering translating the OSGeo-Live documentation. To get started:

Introduce yourself.

Please join our email list at: http://lists.osgeo.org/mailman/listinfo/live-demo, and send an email introducing yourself and your wish to help out. If you wish to start translating to a new language, let us know so that we can create a new status worksheet for you.

Say "hello" to other translators from your region. There details are listed here: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/translators.csv

Get Subversion access

Before updating files, you need commit access to our Subversion repository, described here: http://wiki.osgeo.org/wiki/Live_GIS_Disc#Subversion

check out the doc-directory from svn

svn co https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/
svn co https://svn.osgeo.org/osgeo/livedvd/promo/en/presentations/OSGeoLive4_0Taster

Credit yourself

As a first test to see subversion is working, add your name to the list of translators. This is so that we can credit you in releases and other translators can find you: doc/translators.csv

Status Sheet

We track status of all translations in this google docs spreadsheet: https://spreadsheets.google.com/ccc?key=0AlRFyY1XenjJdFRDbjFyWHg1MlNTRm10QXk0UWEzWlE&hl=en_GB&authkey=CPTB6uIE#gid=7

It contains some excel wizardry to check reported status of English docs, and entered document versions to report on status of translations. This is where you should look to determine which file you should translate next, and also which you should update after translating a document.

Update status sheet version numbers

To update the version numbers of documents, someone should follow the following process:

svn co https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/bin/extract_doc_versions.sh
bin/extract_doc_versions.sh > list.csv
ooffice list.csv

Cut and paste the contents into the second row of the worksheet "svnlist" in https://spreadsheets.google.com/ccc?key=0AlRFyY1XenjJdFRDbjFyWHg1MlNTRm10QXk0UWEzWlE&hl=en_GB&authkey=CPTB6uIE#gid=7

Translations

This is how it works:

1. use the English files from the directory /en as templates: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/en/
2. create a directory for your language in the directory /doc - like /doc/de or /doc/it
3. translate the files from /doc/en and copy them to your language directory (keep the directory structure like it is in en)
   1. the plan is to translate the files in the language-root directory, then the files from standards-directory and from overview-directory and if there is still energy left the files from the quickstart-directory
4. Add your name to https://spreadsheets.google.com/ccc?key=0AlRFyY1XenjJdFRDbjFyWHg1MlNTRm10QXk0UWEzWlE&hl=en&authkey=CPTB6uIE#gid=0 (let's see how this helps)

Use OmegaT for the translations

• there is a nice tool to generate the translations http://www.omegat.org/ (here you find a good documentation)
• apt-get install omegat
• add the ending rst to be supported by OmegaT
  • configure: Options - file filter - textfiles - add - add *.rst

• Create a new project:
  • Select a folder where OmegaT can write its files
  • Select your destination language, point Source Files directory to doc/en, and Translated Files directory to doc/$your-language-code. The two middle options can stay where they are in subfolders of OmegaT project folder.
  • Translate something.
  • Write files: Project > Create Translated Documents will populate doc/$your-language into SVN tree. All .rst files contain both translated and untranslated strings.
  • svn commit

• Work on an already started translation:
  • TO BE DONE - is OmegaT able to handle contents under version control? Seems not, for me.