On 10/15/13, Olemis Lang <[email protected]> wrote: > On 10/15/13, Olemis Lang <[email protected]> wrote: > [...] >> >> 1. Detect all strings selectable for translation , especially >> _('string') > > In here I did not mention that sometimes the string included in Genshi > templates and/or _('source code') is exactly the same one you'll see > in Trac . IMO in that case available translations **should** be reused > (rather than creating a carbon copy in bh domain(s) ) ... and thereby > maybe more tricks and edits will be required . > >> 2. Create translation domain for Bloodhound plugins >> * or maybe one domain per plugin ? >> 3. Define i18n:domain in Genshi templates >> 4. Run Trac extraction commands >> 5. Prepare and compile the catalog >> 6. Ensure that translations will be actually loaded (e.g. domain match) >> 7. Upload files onto Transifex >> 8. Translate to <language> > > ... of course , I did not mention here that translation file had to be > downloaded and incorporated in i18n bh folder(s) , which in turn have > to be created , etc , etc , etc ... > >> 9. Ensure that translations will be actually loaded for <language> >> >> Maybe there are a few more gory details involved which will be clarified >> in >> >> http://trac-hacks.org/wiki/TracPluginTranslation >> http://trac.edgewall.org/wiki/CookBook/PluginL10N >> http://trac.edgewall.org/wiki/TracL10N >>
jftr , this ticket may be used to track the progress made on this feature , submitting patches , etc ... https://issues.apache.org/bloodhound/ticket/694 -- Regards, Olemis - @olemislc
