-
Okay, I was fairly clearly on drugs when I wrote the first patch. New version fixes problems and is a lot better tested. You can now pass bytestrings (Python str objects) or Unicode strings to Markdown.convert(), with or without BOMs.
Further testing has revealed problems with utf-16 BOM handling. The issue is that unicode(codecs.BOM_UTF16_LE, 'utf-16') is u'' -- the BOM is swallowed in the...
2007-10-22 11:47:06 UTC in Python Markdown
-
A problem in version 1.6b:
When you are attempting to remove any BOM from the start of the text, you need to handle the fact that the input text might not be ASCII, even though it's a bytestring. Python will treat a bytestring as ASCII when you call things like text.startswith() in the normal default encoding setup, but it could be, e.g., a UTF-8 encoded bytestring.
Attached patch fixes...
2007-10-21 23:25:30 UTC in Python Markdown
-
The setup.py shipped with feedparser-3.1 still has the
version number set to 3.0. This is a little annoying
when building rpms.
2004-07-03 07:52:52 UTC in Universal Feed Parser
-
Logged In: YES
user_id=65682
This has been fixed for a long time. Although you do not
mention the version you are reporting again, I have to
assume it is 0.3.12. Please upgrade to 0.3.14.
2004-02-04 22:16:15 UTC in ScrollKeeper
-
malcolmt committed patchset 730 of module scrollkeeper to the ScrollKeeper CVS repository, changing 1 files.
2003-12-22 21:33:01 UTC in ScrollKeeper
-
malcolmt committed patchset 729 of module scrollkeeper to the ScrollKeeper CVS repository, changing 1 files.
2003-12-22 21:32:07 UTC in ScrollKeeper
-
malcolmt committed patchset 728 of module scrollkeeper to the ScrollKeeper CVS repository, changing 1 files.
2003-12-22 21:30:16 UTC in ScrollKeeper
-
Logged In: YES
user_id=65682
Sorry about that mistake. Thanks for patch. Applied in CVS.
2003-12-12 01:53:55 UTC in ScrollKeeper
-
malcolmt committed patchset 726 of module scrollkeeper to the ScrollKeeper CVS repository, changing 2 files.
2003-12-12 01:53:16 UTC in ScrollKeeper
-
Logged In: YES
user_id=65682
I have released scrollkeeper-0.3.14 which fixes this
problem. The only small trap remaining is that you need to
make sure you have the XML::Parser perl module installed.
However, from the above error message, that seems to be the
case, since I suspect you would not have got that far if
perl -e "require XML::Parser" failed.
2003-12-06 14:12:26 UTC in ScrollKeeper
