Kristian, I had a similar problem when I needed to send some ASCII emails. I have a snippet at does a translation of unicode characters to close ASCII approximations if it is helpful:
http://www.djangosnippets.org/snippets/588/ Corey On Feb 5, 2008, at 3:48 PM, Kristian Øllegaard wrote: > Hi again > > Ok - my bad. > > Thanks a lot > > Regards > Kristian > > On Feb 5, 2008 9:29 PM, Jacob Kaplan-Moss > <[EMAIL PROTECTED]> wrote: > > On 2/5/08, Kristian Øllegaard <[EMAIL PROTECTED]> wrote: > > Is there an obvious thing i did wrong? Have you heard about this > error > > before? > > This is because of the changes in Unicode handling after 0.96; read > more here: > http://code.djangoproject.com/wiki/UnicodeBranch#PortingApplicationsTheQuickChecklist > > In general, if you've upgraded from 0.96 you *need* to read the > backwards-incompatible changes list: > http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges. When > we release new versions, that list becomes the release notes, but if > you're running off a trunk checkout you need to be aware of the > changes. > > Jacob > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
