Hello Richard,
On 2/1/2010 3:14 AM, Richard Liao wrote:
Hi all,
Since Trac 0.12dev's i18n support for plugins have been implemented
for more than one year, I think it should be stable now.
I'm trying to migrate some plugins to apply i18n, according to
http://trac.edgewall.org/ticket/7497#comment:12
I'm glad you were able to make your way without much documentation about
this ...
I should have added some notes about plugin translations in the TracL10N
page...
What I have done:
1. Apply i18n changes to setup.cfg, setup.py, all .py files and templates.
2. Extract messages from .py files and template using "python
setup.py extract_messages"
3. Translate local language files
4. Make .mo file using "python setup.py compile_catalog -f"
Everything works perfectly except for Genshi templates. I have added
xmlns:i18n="http://genshi.edgewall.org/i18n"; in html tag, and template
messages can be extracted to .po files.
Lack of plugin domain in template seems the problem, but I can't find
where to add it.
You could try this:
http://genshi.edgewall.org/wiki/ApiDocs/genshi.filters.i18n#genshi.filters.i18n:DomainDirective
Any suggestions are appreciate.
Hope this works, and when I'm done with the doc, I'll keep you posted so
that you could have a look and proof read or enhance it.
-- Christian
--
You received this message because you are subscribed to the Google Groups "Trac
Development" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/trac-dev?hl=en.
