On Mon, 2007-10-22 at 06:02 -0700, koenb wrote: > Alexander, > > A few weeks ago I came across the same issue (I filed ticket #5663). > > The good thing is, making your own replacement filter to bypass the > problem is easy. > > On the other hand, Malcolm closed the ticket today as wontfix, stating > it is a bug in markdown. > Though that may be true, I do not understand why the markdown filter > in SVN is converting text to bytestrings first if the markdown module > understands unicode (or maybe it didn't before ?).
That's exactly it: it is only in the recent 1.6b release that Markdown started understanding Unicode at all and there's no way that Django's going to ask everybody to do a forced upgrade just because a third-party package has done something that appears to be an error. Regards, Malcolm -- Monday is an awful way to spend 1/7th of your life. 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 -~----------~----~----~----~------~----~------~--~---
