#694: Translations scaffolding
------------------------+--------------------
Reporter: olemis | Owner: olemis
Type: task | Status: review
Priority: minor | Milestone:
Component: trac core | Version: 0.7.0
Resolution: | Keywords: i18n
------------------------+--------------------
Comment (by SaintGermain):
Hi !
In fact 'needinfo' is really what I had in mind, but I got mixed up and
the questions were on the mailing list instead of here.
So here are the questions :
A) Do you want one domain per plugin or one global 'bloodhound' domain
? The way it works, the translation files live in the plugin
directory, so I guess it doesn't really matter. Except if I didn't
understand how it works and we can have one global translation file
for all bloodhound plugin ?
C) As you said for 1), we would like to avoid duplicates translation
string with Trac. How can we do that in practice ?
How can the translation mechanism know in which translation file to
look for the translation ?
Should I mark the duplicated Trac strings for translation (with _("")) or
not ?
Thanks !
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/694#comment:9>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
