On Thu, 2007-10-25 at 13:27 -0700, Alexander Tsamutali wrote:
> On Oct 22, 6:06 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
> wrote:
> > On Mon, 2007-10-22 at 06:02 -0700, koenb wrote:
> > ...
> > > On the other hand, Malcolm closed the ticket today as wontfix, stating
> > > it is a bug inmarkdown.
> > > Though that may be true, I do not understand why themarkdownfilter
> > > in SVN is converting text to bytestrings first if themarkdownmodule
> > > understands unicode (or maybe it didn't before ?).
> >
> > That's exactly it: it is only in the recent 1.6b release thatMarkdown
> > 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.
> 
> You think that Unicode support is an error or i'm missing something?
> This problem appeared because API changed in python-markdown and
> django should support both versions for some time (checking python-
> markdown version for ex.).

The error is that it *only* supports Unicode string input and not
bytestrings, despite the internals appearing to be prepared to process
bytestrings (for example, he tries to trim Byte Order Marks, which don't
even appear when you convert  UTF-16 byestring to Unicode). Up until
recently, handled non-ASCII bytestrings, so considering this and the
code changes, it looks like an oversight that remains undiscovered
because of some subtleties in the markdown test suite.

If the markdown bug isn't fixed and the new versions will only accept
non-ASCII data as unicode strings, we'll change Django to work around
that, but for the moment I'm hoping the problem will be fixed in the
right place.

Regards,
Malcolm

> 
> 
> > 
> 
-- 
On the other hand, you have different fingers. 
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 [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
-~----------~----~----~----~------~----~------~--~---

Reply via email to