On Sat, 2007-11-03 at 14:51 +0000, omat wrote: > I have experimented both with the subject and the message. They both > expose the same problem when the name contains non-ascii chars. > > As a hack, I started using the slug field instead of the name field > both in the message template and the subject and it works fine, but > the problem is still there.
When debugging change *one* thing at a time, not multiple things! Since the error is in the template rendering, only change that. This is why I wanted to see the traceback, so we could see what was really causing the problem. You said it was the subject line, but it turns out not to be the case. So leave the subject line along and focus your attention on the template code. It's only going to make things more confusing for you (and us) if you keep tweaking portions that are unrelated to the problem without first proving they are actually relevant. malcolm -- Why can't you be a non-conformist like everyone else? http://www.pointy-stick.com/blog/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
