Unfortunately, not all charsets will support all unicode characters, so really, the fact that DEFAULT_CHARSET configurable is mostly a moot point for me. For example, latin1 won't let me encode asian characters.
I honestly can't think of a good reason to do anything other than UTF8 unless you've got some weird requirement to do otherwise. vic On 12/12/06, favo <[EMAIL PROTECTED]> wrote: > > I think you'd better enforce de/encoding to settings.DEFAULT_CHARSET in > the middleware. not hardcode utf8. > > > > > -- "Never attribute to malice that which can be adequately explained by stupidity." - Hanlon's Razor --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
