Difference between revisions of "Live GIS Translate"
Jump to navigation
Jump to search
Line 7: | Line 7: | ||
svn co https://svn.osgeo.org/osgeo/livedvd/promo/en/presentations/OSGeoLive4_0Taster | svn co https://svn.osgeo.org/osgeo/livedvd/promo/en/presentations/OSGeoLive4_0Taster | ||
# Before committing files, you need commit access, described here: http://wiki.osgeo.org/wiki/Live_GIS_Disc#Subversion | # Before committing files, you need commit access, described here: http://wiki.osgeo.org/wiki/Live_GIS_Disc#Subversion | ||
− | # Add your name to the list of translators, so that we can credit you in releases: doc/translators. | + | # Add your name to the list of translators, so that we can credit you in releases: doc/translators.csv |
# use the English files from the directory /en as templates: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/en/ | # use the English files from the directory /en as templates: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/en/ | ||
# create a directory for your language in the directory /doc - like /doc/de or /doc/it | # create a directory for your language in the directory /doc - like /doc/de or /doc/it |
Revision as of 13:24, 23 September 2010
This page describes how to translate documentation for the OSGeo-Live DVD.
Translations
This is how it works:
- 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
- Before committing files, you need commit access, described here: http://wiki.osgeo.org/wiki/Live_GIS_Disc#Subversion
- Add your name to the list of translators, so that we can credit you in releases: doc/translators.csv
- use the English files from the directory /en as templates: https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/doc/en/
- create a directory for your language in the directory /doc - like /doc/de or /doc/it
- translate the files from /doc/en and copy them to your language directory (keep the directory structure like it is in en)
- 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
- 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.