On Mon, 2007-05-21 at 06:07 -0700, sandro dentella wrote: > well, ok. It's the utf-8 encoded version of u'F\xf2' I imagine. But > why if I change DEFAULT_CHARSET > to ' latin-1' it does not get encoded in 'latin-1'? is the db > encoding winning over DEFAUL_ENCODING?
I don't know how many times we have to say this, but non-ASCII encoding is not supported on trunk at the moment. It might work in some places by accident, but if things break, you get to keep both pieces. That is why the UnicodeBranch (see the wiki page of that name) is in development. That branch is very close to fully complete at the moment. Look for an official call for testers in the next day or so. Note that on the unicode branch, you will only be able to use unicode strings and UTF-8 bytestrings internally. The internal encoding used by Django is in no way relating to DEFAULT_CHARSET, since that setting controls the *output* encoding and is not under the control of the code writer (it's under the control of whoever uses your code). A more complete explanation is given in the introduction of the StringEncoding wiki page, which is now close to a statement or reality, rather than just a wishlist (I still need to update it a little bit once unicode devfelopment is finished). Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
