On Dec 30, 8:38 pm, "Adrian Holovaty" <[EMAIL PROTECTED]> wrote:
You shouldn't have to hack around the library like that; it's intended
to handle encoding issues for you. Could you create a ticket (or just
respond here) with the offending data, the offending code and the full
traceback? That way, we'll fix the library so you don't have to hack
around it.
Odd. I created a new project and an application, threw in a couple of
models and forms, changed LANGUAGE_CODE .. and it simply worked. I've
had loads of trouble with the two previous test-applications that I
built. I did, however, svn the framework since then, but I cannot
confirm if anything has changed that could affect my problems. I will
post again if I manage to reproduce the problem.
Now all I do to get some localization going is encode all varchar/text
fields of models before saving (model.field =
model.field.encode('utf-8')), otherwise MySQL truncates the data after
the first non-ascii character (utf-8 database).
Is there a cleaner solution to that too perhaps? :)
---
Gustaf
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
