Re: Non-unicode strings.

2006-09-20 Thread gabor
Malcolm Tredinnick wrote: > > Although I have not used non-ISO-8859-1 storage much at all, I know that > there are some people around who have been using it for a while now > quite successfully, so almost all of the problems are easily solvable > with current Django code. One day I hope to find t

Re: Non-unicode strings.

2006-09-19 Thread Malcolm Tredinnick
On Tue, 2006-09-19 at 18:33 +, Pupeno wrote: > On Tuesday 19 September 2006 02:58, Malcolm Tredinnick wrote: > > That's true. We aren't using unicode universally at the moment. There is > > work in progress to fix this, but it has no completion date at the > > moment. > > So, I can't store Un

Re: Non-unicode strings.

2006-09-19 Thread Pupeno
On Tuesday 19 September 2006 02:58, Malcolm Tredinnick wrote: > That's true. We aren't using unicode universally at the moment. There is > work in progress to fix this, but it has no completion date at the > moment. So, I can't store Unicode strings on PostgreSQL and expect it to work under any c

Re: Non-unicode strings.

2006-09-18 Thread Malcolm Tredinnick
On Tue, 2006-09-19 at 02:27 +, Pupeno wrote: > Hello, > I am using Django 0.95 and SimpleTAL for templating. SimpleTAL expects all > the > strings, it seems, to be unicode (something sane from my point of view). It > seems that some data from PostgreSQL extracted using Django classes is not

Non-unicode strings.

2006-09-18 Thread Pupeno
Hello, I am using Django 0.95 and SimpleTAL for templating. SimpleTAL expects all the strings, it seems, to be unicode (something sane from my point of view). It seems that some data from PostgreSQL extracted using Django classes is not in Unicode and triggers this error: Request Method: GET