Talk:Pootle

Preliminary

• http://bugs.contribs.org/show_bug.cgi?id=3782

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)

Formagick

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

I have packaged for a better installation. You can download from http://mirror.contribs.org/smeserver/contribs/nhall/sme7/contribs/pootle/rpm/gnome-doc-utils-0.12.0-1.noarch.rpm

Create .po and export xml files

we have written a few shell scripts and added a translation file, which are automating checking, we'll release later for contribs authors

bugs

• newxml needs to set: lang="fr"

sed script or look at

xml2po -l fr -p yum.po yum > yum.xml

-l --language=LANG Set language of the translation to LANG

• you can't have a <base> equal to a <trans>

http://bugs.contribs.org/show_bug.cgi?id=3863

Console

• http://bugs.contribs.org/show_bug.cgi?id=3833

update all .po files

Templates have been implemented with up to date strings,

now it's over to users to translate them

• http://bugs.contribs.org/show_bug.cgi?id=3834

.po file names are inconsistent, SV & FR add .tmpl.po to be FIXED in pootle: .tmpl.po is correct, other languages have been changed

• http://bugs.contribs.org/show_bug.cgi?id=3858

Use UTF-8 for console .po files

Pootle has problems with the current charset=iso-8859-1

we now use UTF-8

WONTFIX, we will script the conversion back to iso-8859-1

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

Remarks

Translation Workflow

Draft suggestions ...

.po files

• gettext strings are in various files in cvs, currently we think we have them all in pootle as .pot template files

we need to use xgettext to search a maintained list of files to extract current gettext strings

this may find missing, or modified strings or remove old strings saving on pointless translations

• existing translations have been placed in pootle and merged with the templates

this shows missing translations very nicely and is ready for user testing

• all .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, other languages are updated from templates

• at some point we diff against cvs po files, the patch is checked and applied.

FormMagick files

• these are XML files with a <base> and <trans> pair of strings, these can be converted to .po files with some work

• some rough scripts are being worked on above, there may be others on the net waiting to be found...

we need to clean up some inconsistencies in the english lexicons and they will be our .pot templates

we need to script the conversion of existing translations into .po files

• changes to original files, have to be tracked as usual in the bug tracker

the following is speculative ...

these are imported into the .pot templates, other languages are updated from templates

new <base> strings only have to be added to the cvs xml file for english

• at some point we script xml2po to apply the new translation back to the xml file,

then diff against cvs, make patch, check and apply

Pootle Usage

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

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 #~