Translations to Esperanto [eo]

[diestel@…]

This ticket is for coordination of esperanto translations for Trac. The message.po file will soon be attached - I'm still testing the translations. But there are two small issues with localizing the workflow part:

• How to get an initial state other then "new"
• The small words "as" and "to" in the Actions should be translatable

(see attached screenshots)

[Remy Blank]

Replying to diestel@…:

• How to get an initial state other then "new"

This is non-trivial (as is the translation of workflows in general), and won't be fixed before 0.12 AFAIK.

• The small words "as" and "to" in the Actions should be translatable

I fixed those yesterday. Update to the latest trunk and update your .po and you should get them.

[Christian Boos]

Replying to rblank:

Replying to diestel@…:

• How to get an initial state other then "new"

This is non-trivial (as is the translation of workflows in general), and won't be fixed before 0.12 AFAIK.

Right, see also #5441.

[anonymous]

I attached the messages.po file for [eo] now.

[Christian Boos]

Nearly perfect :-)

$ make stats-eo
stats-eo: 1072 translated messages, 14 untranslated messages.

$ make check-eo
check-eo: OK

$ make compile-eo
python setup.py compile_catalog -l eo
running compile_catalog
error: trac/locale\eo\LC_MESSAGES\messages.po:5415: incompatible format for placeholder u'from': 'd' and 's' are not compatible
compiling catalog 'trac/locale\\eo\\LC_MESSAGES\\messages.po' to 'trac/locale\\eo\\LC_MESSAGES\\messages.mo'

File committed as [9516], with the above glitch fixed.

Please next time use Babel 0.9.5 instead of 1.0dev, as the former is the recommended version. I didn't do an update myself, as I noticed you were on step in advance for the extraction, and currently Babel has some trouble resurrecting obsolete messages (#Bl221).

Starting with 98% coverage is simply excellent, I'm tempted to give you right away the commit rights on that file, if you'd like to ;-)

[diestel@…]

Yes I think write permission for this file would be a good idea. From earlier experiences with translating in the KDE project I know that keeping translations up to date needs working one a regular base. Often just before a new release many messages are revised. So they introduced a message freeze two weeks before the code freeze in order to give translators a minimal chance to reach 100% of coverage.

[diestel@…]

Replying to rblank:

Replying to diestel@…:

• How to get an initial state other then "new"

This is non-trivial (as is the translation of workflows in general), and won't be fixed before 0.12 AFAIK.

For the actions I can set theire own name via trac.ini (e.g., leave.name=let it be) Why not do the same for the states like new.name=fresh? Internally using english state names is ok.

• The small words "as" and "to" in the Actions should be translatable

I fixed those yesterday. Update to the latest trunk and update your .po and you should get them.

In the first option "leave as new" the word "as" still is not translatable for me.

[Remy Blank]

The string for that is at line 2551 in messages.po​ for the Esperanto translation, and is currently empty. It seems to be working correctly in the French translation.

[diestel@…]

Replying to rblank:

The string for that is at line 2551 in messages.po​ for the Esperanto translation, and is currently empty. It seems to be working correctly in the French translation.

My fault! Now it works. Thank you!

[anonymous]

Line 4257 of messages.po contains "subtenaata", which should be "subtenata".

[anonymous]

Replying to anonymous:

Line 4257 of messages.po contains "subtenaata", which should be "subtenata".

fixed

[Ryan J Ollos]

Initial commit of [eo] translation in [9516], and much activity since then: log:/trunk/trac/locale/eo. Appears to have been first included in Trac 0.12: tags/trac-0.12/trac/locale/eo​.

[Ryan J Ollos]

I guess I misunderstood. We leave these translation tickets open indefinitely?