Talk:Pootle

Preliminary

The Goal is to integrate Pootle with CVS and an automatic converter between XML files and PO at contribs.org :)

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 (talk • contribs). 18:23, 24 January 2008 (MST)

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

When you comment on this page, please, add comments in the related section and delete dated text

Formagick

I have found a good tool (getpo) for convert HTML to PO and revert. The best is you can customize to handle xml tags. It has use TIDY lib.

Before use, you can enable centosplus repo and install "tidy".

Download getpo from http://i18n.linux.net.cn/download/gettext-autowork/getpo-031.tar.bz2

See these address:

http://mail.gnome.org/archives/gnome-i18n/2004-March/msg00070.html
http://tidy.sourceforge.net
http://www.w3.org/People/Raggett/tidy/
http://tidy.sourceforge.net/docs/quickref.html

I want to play with it to finally convert formmagick panels to PO correctly.

progress

Is this working manually yet Normando ?

Not yet because I need help from a python or perl specific programmer. Anyway I can playing with these converters.

--Normando Hall 08:21, 25 January 2008 (MST)

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)

progress

we'll look at this later, perhaps starting with contribs

Usage

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

Remarks

Now we have entered the data, it makes it clearer where there are missing translations, good work !

bugs

• there isn't a standard english base for translators to work off, french and german have the most complete set
• .po file names are inconsistent, some add .tmpl

questions

• Another item is charset utf8 or iso-8859-1

charset=iso-8859-1 is mostly being used in the files I've looked at why would we change it ? SN

• I added Slovinian and Indonesion, but I don't understand the setting 'Number of plurals' I used ONE

merging new strings

I have merged new strings into all 10 languages

A good way is to create a file with the change, called the same as the file you are merging into eg this update from sv userOverQuota.po

#: root/etc/e-smith/templates/usr/lib/e-smith-quota/userOverQuota.tmpl:22
msgid " no limit set"
msgstr ""

A not so good way is to clobber it with a complete file, I did this with server-console.po

The stings merge fine, it just overwrites the header info.

I created the new server-console.po by taking the most complete translation which was the fr version and stripping the fr translations

A few inconsistencies remain, individual translators will have to resolve them, eg

IT has extra strings

SV is missing a few

We should work out how 'update from template' works. Where are the templates kept ? they will be the EN versions