On Wed, 2007-05-16 at 23:29 +0200, Andreas Ahlenstorf wrote: > Hi, > > I've some models where the strings returned by __str__() are unicode > strings
For a start, you can *never* return anything other than a bytestring from the __str__ method. You may think you're trying to return unicode, but Python will always force it to have type "str". So even attempting to return unicode form __str__ is a bug in your code. > and contain non-ascii characters, especially umlauts. With a > recent Django version, this causes UnicodeEncodeErrors all over the > place. Could anybody give me a hint on what I have to do to work > around this issues except using ascii characters only? See http://code.djangoproject.com/wiki/UnicodeBranch . For many cases, that branch is usable at the moment, although you can see from the "todo" section that there is still a little work to do. Try it out. Report bugs (prefix any bug ticket titles with "unicode:" so that they show up in searches). See the "Porting Applications" section for changes you'll need to make to your code (and I'd like to hear reports -- via Trac -- of anything I've omitted there). The one big case where it won't behave correctly is if you have a site where the content can be in multiple languages that are decided at request time (some things won't be translated correctly). It's a known problem, obviously, and will be fixed before the branch 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 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 -~----------~----~----~----~------~----~------~--~---
