(i.e. RSS/ATOM, web services and the
like).
--
Julian 'Julik' Tarkhanov
please send all personal mail to [EMAIL PROTECTED]
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
T
On Jan 27, 2007, at 6:44 PM, ak wrote:
> And another thing I still don't understand is: let's pretend I use
> MySQL 4.0 with national charset and my templates are in the same
> charset too. How would work:
It should not work.
--
Julian 'Julik' Tarkhanov
please send all personal m
On Jan 27, 2007, at 6:44 PM, ak wrote:
> 1. newforms are with unicode inside
> 2. ORM is with str inside
3. welcome to the world of pain
--
Julian 'Julik' Tarkhanov
please send all personal mail to
me at julik.nl
--~--~-~--~~~---~--~~
You re
d to stay liberal
in 952 - primarily because
it's still unknown how Django authors want to approach this.
--
Julian 'Julik' Tarkhanov
please send all personal mail to
me at julik.nl
--~--~-~--~~~---~--~~
You received this message because you are subscribed to t
On Jan 26, 2007, at 2:25 PM, Gábor Farkas wrote:
>
> Julian 'Julik' Tarkhanov wrote:
>>
>>
>> Python's unicode is actually UTF-16
>
> on linux it's usually utf-32, and on windows it's usually (always?)
> utf-16.
sorry I forgot that - it's been a year at le
every database driver has to be scrutinized
for whether it returns unicode strings proper.
I know, it seems so nice to be liberal and allow people to choose
their encoding but just too many situations prove that to be the
Wrong Choice.
--
Julian 'Julik' Tarkhanov
please send all persona
On 7-jul-2006, at 17:50, Bill de hÓra wrote:
> This is my point. Cut what exactly? "No good" for what exactly? We
> could file patches to see what sticks, but it might be better to
> figure
> what's wanted first, instead of playing fetch me a rock.
This is handled by Unicode standard and is
On 2-jun-2006, at 22:14, Carlo C8E Miron wrote:
>
> On 6/2/06, Julian 'Julik' Tarkhanov <[EMAIL PROTECTED]>
> wrote:
>>
>> I would advise all respected Django contributors to follow the path
>> mentioned here:
>>
>> http://blade.nagaokau
On 2-jun-2006, at 22:14, Carlo C8E Miron wrote:
>
> On 6/2/06, Julian 'Julik' Tarkhanov <[EMAIL PROTECTED]>
> wrote:
>>
>> I would advise all respected Django contributors to follow the path
>> mentioned here:
>>
>> http://blade.nagaokau
--
Julian 'Julik' Tarkhanov
please send all personal mail to
me at julik.nl
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develope
http://code.djangoproject.com/ticket/952
On 22-mrt-2006, at 6:54, ak wrote:
>
> Thanks, posted: http://code.djangoproject.com/ticket/1528
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
I file a much broader patch for thus about a few months ago. Check
out the tickets.
On 22-mrt-2006, at 6:54, ak wrote:
>
> Thanks, posted: http://code.djangoproject.com/ticket/1528
--~--~-~--~~~---~--~~
You received this message because you are subscribed to
12 matches
Mail list logo
