You might also use the solution provided by Cajus
>
>
> Regards,
> Romeo
>
> -Ursprüngliche Nachricht-
> Von: Cajus Pollmeier [mailto:pollme...@gonicus.de]
> Gesendet: Dienstag, 14. April 2015 14:37
> An: qooxdoo Development
> Betreff: Re: [qooxdoo-devel] Work a
d by Cajus
Regards,
Romeo
-Ursprüngliche Nachricht-
Von: Cajus Pollmeier [mailto:pollme...@gonicus.de]
Gesendet: Dienstag, 14. April 2015 14:37
An: qooxdoo Development
Betreff: Re: [qooxdoo-devel] Work around translation key discovery of
generator.py
I'm not sure if I underst
I'm not sure if I understand the problem correctly. Here's what we do in
an application with the need for dynamic localization:
We're loading i18n messages from a backend and feed them into the
current translation using the "addTranslation" method of
qx.locale.Manager.
The code hasn't been update
Dear all,
In a number of cases we have stumbled upon a shortcoming of the
translation framework. It is my understanding that generator.py scans
class files for tr*() and marktr() calls in order to extract relevant
translation message ids. It then looks up these ids in the .po files to
compile
