This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ezio.melotti
Recipients Brian.Jones, eric.araujo, eric.smith, ezio.melotti, hp.dekoning, loewis
Date 2011-07-21.05:22:23
SpamBayes Score 0.00046417097
Marked as misclassified No
Message-id <1311225744.01.0.0402121579674.issue11113@psf.upfronthosting.co.za>
In-reply-to
Content
Having them in different mappings would be good, but I expect that for most real world application a single mappings that includes them all is the way to go.  If I'm parsing a supposedly HTML page that contains an &apos; I'd rather have it converted even if it's not an HTML entity.
If the set of entities supported by HTML5 is a superset of the HTML4 and XHTML ones, than we might just use that (I haven't checked though).
History
Date User Action Args
2011-07-21 05:22:24ezio.melottisetrecipients: + ezio.melotti, loewis, eric.smith, eric.araujo, Brian.Jones, hp.dekoning
2011-07-21 05:22:24ezio.melottisetmessageid: <1311225744.01.0.0402121579674.issue11113@psf.upfronthosting.co.za>
2011-07-21 05:22:23ezio.melottilinkissue11113 messages
2011-07-21 05:22:23ezio.melotticreate