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
>
> I've gladly granted you with the necessary permissions @ transifex so
> that you can move faster on this direction . If you need any other
> kind of help and/or infrastructure please post of your progress via
> [email protected] . Since long time ago we've been wanting o
> contribute an Spanish (... maybe Russian) translation as well , but
> had no time to spend on the initial scaffolding needed.
>
> I'm quite sure that others will follow , see downloads geo map [2]_ ;)
>
>>>> But I would like to add a feature for internationalization (like
>>>> Django):
>>>>
>>>> https://docs.djangoproject.com/en/1.5/topics/i18n/translation/#how-django-discovers-language-preference
>>>>
>
> AFAICT language selection based on header + prefs + admin exists in
> core , at least in 1.0 . I do not recall the status of i18n feature in
> 0.12
>
>>>> How should I proceed:
>>>> 1) Send a patch to Trac and wait for Trac integration and hope that
>>>> Apache Bloodhound will import it
>>>> 2) Send a patch to Trac and Apache Bloodhound, but what happens if
>>>> both have different comments or if one accept it and not the other ?
>>>> 3) Send a patch only to Apache Bloodhound
>>>>
>
> You'll definitely have to send a patch for Bloodhound considering (at
> least) the steps (1)-(6) above . IMO the aspects related to improving
> Trac's i18n subsystem are better submitted as a patch to trac-dev that
> we'll incorporate in forthcoming upgrades of our vendor branch .
>
> [...]
>
>> I will give a shot this week at Apache Bloodhound to see what can be
>> done there.
>
> cool !
>
> [...]
>
> .. [1] http://transifex.com/projects/p/bloodhound
>
> .. [2] http://goo.gl/#analytics/goo.gl/EMHMvQ/all_time
>
> --
> Regards,
>
> Olemis - @olemislc
>
--
Regards,
Olemis - @olemislc
Apache™ Bloodhound contributor
http://issues.apache.org/bloodhound
http://blood-hound.net
Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/
Featured article:
