#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 olemis):
Replying to [comment:21 olemis]:
> Replying to [comment:20 SaintGermain]:
>
[...]
>
> > However I could not create a bhdashboard.util.translation as there
were already a util.py or utils.py file inside each plugin.
> > So I created a translation.py file, which means we'll use:
> > {{{from bhdashboard.translation import _}}}
> >
>
> I'll take a look into this and suggest something in a while .
>
I've incorporated your patch into my patch queue in branch
[https://bitbucket.org/olemis/bloodhound-mq/commits/branch/t694_bh_i18n
t694_bh_i18n] just to track changes and see how it evolves with time . I
uploaded an (untested) [https://bitbucket.org/olemis/bloodhound-
mq/src/cef907a1137247b8ba7b39dcf8d1a5df295a7152/t694/t694_r1534486_bloodhound_i18n.diff?at=t694_bh_i18n
version] that :
- introduces `util`(s) packages
- moves previous `util(s).py` files into `__init__.py`
- moves `translation.py` into that folder
- updates dependent import statements
PS: The changes were introduced in changeset [https://bitbucket.org/olemis
/bloodhound-
mq/commits/8c5bf612eb8c4f6d05cf884383229a07f9448828?at=t694_bh_i18n
8c5bf61] , the next one merely moves the patch to a new location .
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/694#comment:25>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
