On 10/15/13, Saint Germain <[email protected]> wrote:
> On 15 October 2013 16:34, Gary Martin <[email protected]> wrote:
Hi !
:)
>>> I am a newcomer to Trac and Apache Bloodhound and it seems that both
>>> projects are very interesting for me.
>>>
>>> I would like to know what is the best way to contribute ?
>>>
>>> For instance for translation, having discussed with rjollos, it seems
>>> better to translate Trac, as the translation will end up eventually in
>>> Apache Bloodhound.
>>>
There are a few messages in Apache™ Bloodhound that differ from Trac's
and still need to be translated . We attempted to start working on
Bloodhound translations a while ago . At the time we created the
translation project at Transifex [1]_ . Unfortunately we could not
follow since had to switch to do other tasks . That's why it's
actually empty (even if a dummy translations are included in there
aimed at probing transifex way of doing things ;)
With the increased popularity of Bloodhound we have received requests
for translating it into Persian, Vietnamese, and your personal request
for French (... which I've not replied because of the reasons
expressed above ... there are no real strings to translate so far) .
Nevertheless I incorporated you as a member of the French translation
group , but beware of the previous facts ;)
If you'll be spending some time in generating translations for French
there are a few previous steps :
1. Detect all strings selectable for translation , especially _('string')
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>
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
