Michael Radziej wrote:
> gettext('blablabla %s blablalba') % \
> "utf8 bytestring with funny ää chars"
>
> If gettext returned unicode, python would decode the utf8 encoded
> bytestring, again using ASCII as default encoding -> exception galore ;-)
I believe we should teach people to start usi
Hi
Malcolm Tredinnick wrote:
> What I don't think is the right answer is to suddenly start making
> gettext() behave as if it were ugettext() -- using the wrong name for
> something will lead to confusion for people who use Django as a tool,
> not as a lifestyle choice.
Certainly. Think about th
Hey Michael,
On Tue, 2007-04-17 at 10:31 +0200, Michael Radziej wrote:
> Hi Malcom and you all,
>
> On Tue, Apr 10, Malcolm Tredinnick wrote:
>
> > What I'd really like from you guys (Michael, Ivan, Gábor -- and anybody
> > else who wants to play along) is to see how the code fits in with your
Hi Malcom and you all,
On Tue, Apr 10, Malcolm Tredinnick wrote:
> What I'd really like from you guys (Michael, Ivan, Gábor -- and anybody
> else who wants to play along) is to see how the code fits in with your
> existing workflow.
How do the translation functions gettext() (_()) etc. fit in?
Gábor Farkas wrote:
> i'd like to know about Request objects... how "early" do you plan to
> switch to unicode?
>
> will request.GET/POST already contain unicode-keys + unicode-values?
>
> what about request.META?
>
>
> i would personally like to have GET/POST already contain unicode data.
>
Malcolm Tredinnick wrote:
>
> What I'd really like from you guys (Michael, Ivan, Gábor -- and anybody
> else who wants to play along) is to see how the code fits in with your
> existing workflow. What are the bits that are still hard for you? What
> are the problems that aren't solved? I'm thinki
On Tue, 2007-04-10 at 12:13 +0200, Michael Radziej wrote:
> Hi Malcolm,
>
> Malcolm Tredinnick wrote:
> > It's a much tougher requirement on the developer. They have to change
> > every piece of their code. Instead, we can accept UTF-8 bytestrings or
> > unicode strings and large amounts of code
Hi Malcolm,
Malcolm Tredinnick wrote:
> It's a much tougher requirement on the developer. They have to change
> every piece of their code. Instead, we can accept UTF-8 bytestrings or
> unicode strings and large amounts of code will work unchanged.
>
> There aren't actually that many places where
On Tue, 2007-04-10 at 19:53 +1000, Malcolm Tredinnick wrote:
> On Tue, 2007-04-10 at 10:02 +0200, Gábor Farkas wrote:
> > hi,
> >
> > i've been reading http://code.djangoproject.com/wiki/StringEncoding,
> >
> > and the idea seems to be, that for "Passing Strings Between Django and
> > the Devel
Malcolm Tredinnick wrote:
> On Tue, 2007-04-10 at 10:02 +0200, Gábor Farkas wrote:
>> hi,
>>
>> i've been reading http://code.djangoproject.com/wiki/StringEncoding,
>>
>> and the idea seems to be, that for "Passing Strings Between Django and
>> the Developer's Code",
>>
>> django will/should acce
On Tue, 2007-04-10 at 10:02 +0200, Gábor Farkas wrote:
> hi,
>
> i've been reading http://code.djangoproject.com/wiki/StringEncoding,
>
> and the idea seems to be, that for "Passing Strings Between Django and
> the Developer's Code",
>
> django will/should accept both utf-8 encoded byte-string
hi,
i've been reading http://code.djangoproject.com/wiki/StringEncoding,
and the idea seems to be, that for "Passing Strings Between Django and
the Developer's Code",
django will/should accept both utf-8 encoded byte-strings, and
unicode-strings.
wouldn't it be simpler to only accept unicode
12 matches
Mail list logo
