I had the same problem (ticket 3630).
I solved that by passing my mySQL fields in UTF8, then by doing :
for i in data :
data[i] = data[i].decode("latin1","replace")
Then I created a form with these data and used its values to save them
in the DB. If you do that, you will see that if their is an error and
that the form is displayed again, you will have strange characters...
So I have kept the "data" object like it was before the decoding
(old_data = data.copy()), created an other form with these data un-
decoded, and this is the one I display in the template. 2 forms, yeah,
that sucks, but I have not found any other way.
Sorry, I don't speak a good english, just say it if you have not
understood.
Regards
Baptiste.
On 7 mar, 18:49, "Nuno Mariz" <[EMAIL PROTECTED]> wrote:
> Hi,
> Although seems that exists a patch for this problem, the newforms
> continues with the same problem.
> I have a field that the user fills with: João Ratão
> In the database shows: Jo? Rat
>
> This behavior happens only in the latest trunk, in the old an unicode
> exception was raised.
> In the Admin interface works fine(because uses the oldforms, I guess)
> In my settings.py I have: DEFAULT_CHARSET = 'utf-8'
>
> I'm doing something wrong?
>
> Thanks,
> Nuno Mariz
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
