On Feb 25, 5:57 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> This means that almost certainly you don't, in fact, have correct UTF-8
> data in your tables. Some ISO-8859-1 codepoints seem to have slipped in.
> You should write a script to run through the data and make sure it
> really is all UTF-8 (and re-encode that stuff that isn't).
>
> Somebody posted here a couple of weeks ago pointing out they had arrived
> in the same situation because their data was created by a PHP app (which
> doesn't seem to do the encoding correctly).
But all my data was generated by django. At first I was using django
0.96, which I suppose handle
unicode differently, but I tried exporting the DB, converting it to
utf-8, and reimporting it without success.
Also, I find strange that this work perfectly using the development
webserver, and when I start using fastcgi,
unicode errors come up, what could cause this?
By the way, the "latin1" settings created several other problems for
me, I add to change the default python encoding to
utf-8 to fix some of them, and using unicode(str) fixed others, but
there's some problems I couldn't fix yet.
I will test with a fresh project soon, to see I have the same
problems.
Thank for your help,
Jean-Pascal
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
