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

svn co https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/ svn co https://svn.osgeo.org/osgeo/livedvd/promo/en/presentations/OSGeoLive4_0Taster
 * check out the doc-directory from svn:

Only if you want to compile with sphinx in your locale environment, you need to get check out all trunk-directory from svn: svn co https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/


 * Credit yourself
 * As a first test to see subversion is working, add your name to the list of translators.


 * 1) edit translators.csv
 * 2) please add your Language, i18n code, Name, Country, Email, and Osgeo_id to the list,
 * 3) separated by comma.
 * 4)  - Order alphabetically by language (2 letter code), then by first name
 * 5)  - remove punctuation from email addresses to stop harvesting for junk mail

This is so that we can credit you in releases and other translators can find you: doc/translators.csv

= Status Sheet =


 * Documents ready to translate are marked "Final" in our Project Status Spreadsheet.
 * Check the Translation Status to find files that need translation, or need updating. Note that the hyperlink for each translated doc will take you to a page showing the differences in the English doc since last translation. (This document is updated hourly by extracting document version from subversion).

= Nightly documentation builds =
 * http://adhoc.osgeo.osuosl.org/livedvd/
 * Latest documentation build can be found in the docs/ dir.
 * Please have a look at and squash any problems which show up in the error log, which can be found in the logs/ dir.

= Translations =

This is how it works:


 * Find documents that have a "Final" status in our Project Status sheet and which are not translated or outdated in the Translation Status.
 * If this is a new translated document, use subversion to copy the English version of the document to new language directory. (This retains our subversion history, while svn add does not)

svn copy doc/en/ .rst doc/lang/ .rst


 * add your name as translator of the document: add :Translator: Your_name at the top of document near :Reviewer: or Author
 * translate the document and then commit back to subversion

svn commit -m "Translated docX.rst to Italian" docX.rst


 * Once complete change status="complete"

Adding new languages
Make sure you edit the list in:
 * doc/Makefile
 * doc/themes/overview/page.html
 * doc/index.template
 * bin/lang_stats.sh

Setup the dir structure: LCODE=pt cd doc/ mkdir $LCODE cd $LCODE mkdir overview/ quickstart/ standards/ cd .. svn add $LCODE svn commit $LCODE

Remember that when `doc/Makefile` changes the hash needs to be updated; contact Hamish.

Glossary
At this page you can find a glossary of OSGeo-Live documentation related terms, please fell free to add new terms.

Use OmegaT for the translations
sudo apt-get install omegat
 * there is a nice tool to generate the translations http://www.omegat.org/ (here you find a good documentation)
 * To install the tool on a Ubuntu or Debian system (such as the live disc) run:
 * add the ending rst to be supported by OmegaT
 * configure: Options &rarr; file filter &rarr; textfiles &rarr; add &rarr; 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 &rarr; 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.