On 30-Aug-07, at 1:29 PM, Michael Radziej wrote:
>>
>> True, that's why I call this behaviour "buggy".
>
> Ah! I thought that you advocated for gettext instead of
> gettext_lazy in this
> specific situation.
well, i am using gettext until the bug is fixed - so far no problems
--
regards
On Thu, Aug 30, Jarek Zgoda wrote:
>
> Michael Radziej napisał(a):
>
> The next testing option is to try with non-lazy version.
> >>> that works! import gettext as _
> >> And that's a real bug, I think.
> >>
> >> Anyway, for future reference, keep in mind that lazily translated
> >>
Michael Radziej napisał(a):
The next testing option is to try with non-lazy version.
>>> that works! import gettext as _
>> And that's a real bug, I think.
>>
>> Anyway, for future reference, keep in mind that lazily translated
>> "strings" become real strings at access time. Before that
On Wed, Aug 29, Jarek Zgoda wrote:
>
> Kenneth Gonsalves napisał(a):
>
> >>> now, this doesnt work - when I remove the _(), then the choices
> >>> appear. How do I then mark them for translation?
> >>>
> >> Make sure to use gettext_lazy
> > i *am* using: from
Kenneth Gonsalves napisał(a):
>>> now, this doesnt work - when I remove the _(), then the choices
>>> appear. How do I then mark them for translation?
>>>
>> Make sure to use gettext_lazy
> i *am* using: from django.utils.translation import gettext_lazy
> as _
Ha!
On 29-Aug-07, at 2:53 PM, Jarek Zgoda wrote:
>> now, this doesnt work - when I remove the _(), then the choices
>> appear. How do I then mark them for translation?
>>
> Make sure to use gettext_lazy
i *am* using: from django.utils.translation import gettext_lazy
as _
On 29-Aug-07, at 2:51 PM, Michael Radziej wrote:
>> doesnt work - i just marked one string, the marked string didnt
>> appear, the other two did.
>
> Well, sorry, then I'm personally running out of ideas. But this
> looks really
> weird.
i filed a bug report
--
regards
kg
Kenneth Gonsalves napisał(a):
> now, this doesnt work - when I remove the _(), then the choices
> appear. How do I then mark them for translation?
>
Make sure to use gettext_lazy
>>> i *am* using: from django.utils.translation import gettext_lazy as _
>> Ha! How should we know?
On Wed, Aug 29, Kenneth Gonsalves wrote:
>
>
> On 29-Aug-07, at 2:24 PM, Michael Radziej wrote:
>
> now, this doesnt work - when I remove the _(), then the choices
> appear. How do I then mark them for translation?
>
> >>>
> >>> Make sure to use gettext_lazy
> >>
> >> i *am*
On 29-Aug-07, at 2:24 PM, Michael Radziej wrote:
now, this doesnt work - when I remove the _(), then the choices
appear. How do I then mark them for translation?
>>>
>>> Make sure to use gettext_lazy
>>
>> i *am* using: from django.utils.translation import gettext_lazy as _
>
>
On Wed, Aug 29, Kenneth Gonsalves wrote:
>
>
> On 28-Aug-07, at 9:55 PM, Chris Hoeppner wrote:
>
> >> when i upgraded to the latest svn head, I found that all the places
> >> in admin that had drop downs for choices were blank. I had always
> >> marked my choices for translation like so:
> >>
On 28-Aug-07, at 9:55 PM, Chris Hoeppner wrote:
>> when i upgraded to the latest svn head, I found that all the places
>> in admin that had drop downs for choices were blank. I had always
>> marked my choices for translation like so:
>>
>> article_type = (
>> ("NW", _("News")),
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kenneth Gonsalves escribió:
> hi,
>
> when i upgraded to the latest svn head, I found that all the places
> in admin that had drop downs for choices were blank. I had always
> marked my choices for translation like so:
>
> article_type = (
>
hi,
when i upgraded to the latest svn head, I found that all the places
in admin that had drop downs for choices were blank. I had always
marked my choices for translation like so:
article_type = (
("NW", _("News")),
("FT",_("Features")),
)
now, this doesnt work - when I remove the _(),
14 matches
Mail list logo
