On Wed, Feb 11, 2009 at 10:07:25PM +0100, Wouter Bolsterlee wrote:
> 2009-02-11 klockan 22:03 skrev Marcel Telka:
> > On Wed, Feb 11, 2009 at 09:37:20PM +0100, Wouter Bolsterlee wrote:
> > > There is one downside though: translators MUST NOT translate the keywords
> > Isn't this checked by the msgf
2009-02-11 klockan 22:03 skrev Marcel Telka:
> On Wed, Feb 11, 2009 at 09:37:20PM +0100, Wouter Bolsterlee wrote:
> > There is one downside though: translators MUST NOT translate the keywords
> Isn't this checked by the msgfmt command? If not, it should be, IMHO.
> Bug in gettext?
If I recall corr
2009-02-11 klockan 21:58 skrev Willie Walker:
> But, if the gnome-i18n team makes a decree that thou shalt always use
> format specifier reordering, [...]
Hi Willie,
No worries, if your current approach to this specific case works, by all
means leave it like it currently is. It's simpler after
On Wed, Feb 11, 2009 at 09:37:20PM +0100, Wouter Bolsterlee wrote:
> >>> 'the role is %(role)s and the level is %(level)d' % {'role': 'test',
> 'level': 3}
> 'the role is test and the level is 3'
>
> If translators decide the order has to be changed, this will result in
> something like this:
Hi Wouter:
From my experiences with the Q_ vs. C_ change, for example, I saw
translators being overly aggressive in their translations, translating
stuff the comments explicitly told them not to translate. Hence, I
definitely supported the change to C_ because it helped prevent this.
At the
Hi all,
The "format specifiers should be in a different order" problem is not new,
and not specific to Python. Let's look into this specific case once more:
2009-02-11 klockan 20:58 skrev Willie Walker:
> At the request of our Hungarian translator, we've changed a string in
> Orca. The old str
