0.12 and i18n, what's the status?
Christian Boos
As someone recently updated the Trac french translation, I thought I
could have a look at this.
But that reminded me that the last time I've played with the i18n stuff,
there were still lots of open points.
That was *6* months ago, and there's been no progress since, which is a
bit unfortunate as the i18n was supposed to be /the/ feature of 0.12.
Note that I'm not talking about the translation updates, they have been
going well AFAICT. I'm talking about the necessary ground work for being
able to have decent translations in place everywhere, and that's far
from being over.
Most important items:
- #7497: I18N/L10N support for plugins
- #6353: Translation Interfaces for javascript
In particular, #7497 has a patch but mentions (in
http://trac.edgewall.org/ticket/7497#comment:6) the need for two
upstream patches. The Babel one has been applied (for 0.9.4) but not the
Genshi one (#G129).
There are other points as well (probably not an exhaustive list):
- translation support for the workflow states
- more generally, translation for the labels obtained from trac.ini
- refactoring the code in various places in order to get more
meaningful extracted strings (I have a patch for the contextual
navigation, for example)
So the question is, does someone have any plans to get that ball rolling
again?
-- Christian
Jonas Borgström
Agreed, Trac's I18N support still needs work but I'm willing do what I
can to help.
I've just attached a patch for #6353. It's still just a prototype and
I've not yet figured out the best way to keep down the size of the
catalog exported to javascript. One option is to extract javascript
strings into a separate domain, but I'm not sure how to get babel to
extract strings into more than one domain.
/ Jonas