Talk:Pootle

From SME Server
Jump to navigation Jump to search

Preliminary

The Goal is to manage SME translations with Pootle hosted on contribs.org. The current method excellent as it is makes it hard to find missing strings and to easily replace them.

Test pootle site: http://www.unixlan.com.ar:8888

Once we have everything worked out how to interact with pootle and the formmagick stuff then I'll get something up on contribs.org that everyone can use. It would be really nice if we could automate the extraction/import of files that need to be translated into pootle but first things first.

Slords 18:23, 24 January 2008 (MST)

xml2po

we are using http://linux.die.net/man/1/xml2po to convert the xml lexicons to .po files and back

You can download from http://mirror.contribs.org/smeserver/contribs/nhall/sme7/contribs/pootle/rpm/gnome-doc-utils-0.12.0-1.noarch.rpm

To create .po and export xml files, we have written a few shell scripts and added a translation file smetrans.py

we'll release these later for contribs authors


bugs

Bugs related to Pootle based translations are linked here

revision control using CVS/SVN

Today I had a quick look at the pootle pages and found a wiki as well, which has some valuable information like for instance revision control using CVS/SVN: http://translate.sourceforge.net/wiki/pootle/version_control - Cactus 03:26, 25 January 2008 (MST)

A few links for future implementation:

http://subversion.tigris.org/tools_contrib.html#po_update_sh
http://subversion.tigris.org/tools_contrib.html#verify_po_py
http://subversion.tigris.org/tools_contrib.html#svnmerge_py
http://subversion.tigris.org/tools_contrib.html#svnmerge_sh

Translation Workflow

Draft suggestions ...

.po files

  • gettext strings are in various files in cvs
we use xgettext to creates .po files from the original files to by extracting gettext strings [1]
we load these into pootle as .pot template files and update other languages from these
  • .po files have been converted to UTF-8, they will be converted back to ISO-8859-1 when patching SME
  • changes to original files, ie changed gettext strings, have to be tracked as usual in the bug tracker
these are imported into the templates and other languages by above method
  • at some point we diff updated po files against cvs po files, the patch is checked and applied.

FormMagick files

  • these are XML files with a <base> and <trans> pair of strings
we create .po files from the english versions [2]
we load these into pootle as .pot template files and update other languages from these
  • changes to original files, have to be tracked as usual in the bug tracker
new <base> strings only have to be added (or removed) to the cvs xml file for english
  • at some point we apply the new translation back to the xml file [2]

then diff against cvs, make patch, check and apply

[1] smeserver-locale smefetchpo (added)
[2] smeserver-locale smefetchxml, smexml* smereload (to be added)

Pootle Usage

Test pootle site: http://www.unixlan.com.ar:8888

Future wiki howto at Translations

move the pootle usage section there, and revise the whole page

untranslated words

click "Show Editing Functions" and finally at "Quick Translate" for each file or whole language.

Also you can see the suggestions clicking at "Review Suggestions".

checks

click "show checks" to see a list of syntax errors

acronyms  6 strings (2%) failed
brackets 17 strings (6%) failed
doublequoting 4 strings (1%) failed
doublespacing 1 string (0%) failed
endpunc 11 strings (3%) failed
endwhitespace 4 strings (1%) failed
numbers 2 strings (0%) failed
puncspacing 2 strings (0%) failed
sentencecount 2 strings (0%) failed
simplecaps 16 strings (5%) failed
startcaps 6 strings (2%) failed
unchanged 7 strings (2%) failed
untranslated 53 strings (19%) failed

click on one of the links offered and fix them

See http://translate.sourceforge.net/wiki/guide/pofilter_examples and http://translate.sourceforge.net/wiki/guide/translation/commonerrors

Merging new strings

Add, remove or modify strings in the template/*.pot file then click 'update from template'.

New strings are added
modified strings use existing data and made fuzzy (i think)
deleted strings are moved to the bottom of the file and commented out with #~