> Congratulation! Thank you!
> > The plugin works with multiple repositories. Language is translated if Babel > > is installed. > > I seriously doubt this would work with current code. Did you test it? > Browsing the repo I failed to find a message catalog as well as the bare > minimum of configuration for generation/updating one. Importing a single > translation function is not enough. Consider reading the almost finished > i18n/l10n guide for Trac plugins: > http://trac.edgewall.org/wiki/CookBook/PluginL10N Ah, but the trick was to only use existing strings used by the core of Trac 0.12 ;) I am the translator for the Swedish locale... So, yes it works! BUT, you are nevertheless correct, there is one string (I think) that goes untranslated, but this is not part of the normal use case (or should not be very frequent at least). But that string is also the same as in Trac core (tracopts/commit_updater, I don't know why that string is not part of messages.pot). The important strings that I've added -- the header of the new section and a couple of other lingual expressions, that are frequent and will show up with existing page content -- are all existing in messages.pot and thus translated. > > I'd like to assist to get i18n support working and up to date. > Afterwards I'd love to add the message catalog to the Trac l10n project > http://trac-hacks.org/wiki/TracPluginTranslation > for help with coordination and collection of translations via Transifex. > Just the way Trac does it, but most helpful for a translator, who can > get plugin message catalogs from a single place now. I agree, I've seen that work has started with finding work methods for translating plugins. I avoided this subject by careful selection of the very few strings. Once that work has made progress, I will adapt this plugin, of course. > > Sincerely > > Steffen Hoffmann Thanks for the feedback! -- Mikael -- 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.
