#694: Translations scaffolding
------------------------+----------------------
Reporter: olemis | Owner: olemis
Type: task | Status: assigned
Priority: minor | Milestone:
Component: trac core | Version: 0.7.0
Resolution: | Keywords: i18n
------------------------+----------------------
Comment (by SaintGermain):
Ok then I see your point with the user-defined translation catalog.
But it becomes quite complex for this patch.
Forcing the translation make only sense if the user is able to give its
own user catalog, so I'd prefer to keep this code for later.
As of now the 'Tickets' mainnav label is an anomaly because it is only by
chance (because we use the same label as the default one) that it is
translated (it's not a bug it's a feature ! ;-) ).
So I'd propose to keep things as they are and plan the complete user-
defined label translation for another patch instead of implementing only
half the solution.
If translation consistency is important in the mainnav, we can remove the
browser.label and tickets.label from the generated base.ini (and replace
'Browse Source' by 'Source' in the code if you think it is a better
label).
Would that be acceptable ?
Thanks,
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/694#comment:74>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
