Option's doc should be translated.

[songofacandy@…]

Option's doc should be i18n target.

[Christian Boos]

Not for 0.12.2, and not all.

But the "user-oriented" ones (query:keywords~=userpreferences), yes.

[Jun Omae]

I worked the issue, ​https://github.com/jun66j5/trac/compare/t9666-i18n-option-doc.

New trac.dist.extract_python method can extract messages from doc keyword argument of Option family and ConfigSection. [[TracIni]] macro shows translated documentation of each option.

[Christian Boos]

Wow, lots of work in perspective for translators ;-)

For this reason, I wouldn't put the messages by default in the "messages" domain, but in a separate "tracini". That way, it's easy for translators to decide if they want to support this or not (this is not "end-user" facing text, only "admin-user").

Also, though it's easy to see that extract_python initially comes from Babel, maybe just add a note explaining what it does differently ("""Patched extract_python from Babel to support keyword argument mapping. with a brief overview of what this is about).

Other than those few remarks, looks great! If you want this for 0.13, please do so.

[Jun Omae]

Ok. I agreed the separating catalog. I will create extract_messages_tracini, init_catalog_tracini, compile_catalog_tracini and update_catalog_tracini commands of setup.py.

[Jun Omae]

Committed in [10598]. The translators can do options' documents in each tracini.po!