2007/4/6, Gabor Farkas <[EMAIL PROTECTED]>:
>
> Ivan Sagalaev wrote:
> but, even if it not, i think full django-unification is worth ANY cost.
I agree completly with you. just look at
http://code.djangoproject.com/ticket/3924 and similar tickets.
The actual mix is a nightmare for non english user
Ivan Sagalaev wrote:
> Malcolm Tredinnick wrote:
>> I applaud Adrian's attempts to be unicode-aware from the get go, but
>> it's also cost a bit of sleep lately trying to debug things. Having
>> spent most of my free time over the last three days looking at this
>> exact set of problems, I'm begin
Malcolm Tredinnick wrote:
> Do you use git or cogito? I can put my repository up if you want to play
> along at home over the weekend. I guess I could also make it subversion
> accessible, although that will take more than the three minutes a git
> repository would (still, git -> subversion isn't
Adrian Holovaty wrote:
> I'm 100% for that. Let's do it. If you think a branch would be better
> for this, we can make that happen, too.
Yes, that would be handy. Malcolm asked about 'git' and 'cogito' which,
I assume, has something to do with automated patch control but I never
seen that :-).
On 4/6/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> I applaud Adrian's attempts to be unicode-aware from the get go, but
> it's also cost a bit of sleep lately trying to debug things. Having
> spent most of my free time over the last three days looking at this
> exact set of problems, I'm b
Hey Ivan,
On Fri, 2007-04-06 at 18:07 +0400, Ivan Sagalaev wrote:
> Malcolm Tredinnick wrote:
> > I applaud Adrian's attempts to be unicode-aware from the get go, but
> > it's also cost a bit of sleep lately trying to debug things. Having
> > spent most of my free time over the last three days lo
Malcolm Tredinnick wrote:
> I applaud Adrian's attempts to be unicode-aware from the get go, but
> it's also cost a bit of sleep lately trying to debug things. Having
> spent most of my free time over the last three days looking at this
> exact set of problems, I'm beginning to think we should jus
On Fri, 2007-04-06 at 15:04 +0200, Michael Radziej wrote:
> Hi,
>
> in the course of triaging a few tickets ... how is newforms expected to
> deal with model attributes, like in {{{ aModel.field=value }}}? Should
> it use unicode strings or UTF-8 encoded bytestrings?
>
> I see that it currently
Hi,
in the course of triaging a few tickets ... how is newforms expected to
deal with model attributes, like in {{{ aModel.field=value }}}? Should
it use unicode strings or UTF-8 encoded bytestrings?
I see that it currently uses unicode strings, but these then cause havoc
in other parts of Djan
