From: Kent J. <ke...@td...> - 2007-10-30 22:05:12
|
Yuri Takhteyev wrote: > I want to stick with a simple rule: if it's a string, then > its unicode. > > So, I think we should offer the following functions: > > 1. unicode text -> unicode html Hmm...one problem with this (and Waylan's suggestion of making the encoding parameter to markdown() do something useful) is that until 1.6b, markdown() did in fact work perfectly well with encoded text and it was not at all clear that this was not the intended usage. When 1.6b came out I just commented out the call to removeBOM(), complained to the list, and continued on my way. I use markdown from Django with the markdown support included with Django; presumably many other people are also. For example: http://www.freewisdom.org/projects/python-markdown/Django which is based on this post by Waylan: http://achinghead.com/archive/70/django-blog-and-markdown/ which is pretty close to the current form of the Django markdown filter. Kent |