➜

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 Behdad.Esfahbod
Recipients Behdad.Esfahbod, MLModel, loewis, ronaldoussoren
Date 2015-04-23.18:33:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1429813994.71.0.0283048570533.issue10733@psf.upfronthosting.co.za>
In-reply-to
Content 
> Replacing all control characters by entities before trying to parse the Plist XML would likely be the best way forward. 

That wouldn't work.  Control characters are disallowed in XML's character set, so they are invalid even if input as entities.

Unfortunately this causes a lot of trouble for clients [0], because it means that XML cannot represent the full Unicode repertoire.  I'm curious about alternates.  Perhaps the expat module can be extended to allow recovering from this if the client chooses to...

[0] eg. https://github.com/behdad/fonttools/issues/249
History
Date User Action Args
2015-04-23 18:33:14Behdad.Esfahbodsetrecipients: + Behdad.Esfahbod, loewis, ronaldoussoren, MLModel
2015-04-23 18:33:14Behdad.Esfahbodsetmessageid: <1429813994.71.0.0283048570533.issue10733@psf.upfronthosting.co.za>
2015-04-23 18:33:14Behdad.Esfahbodlinkissue10733 messages
2015-04-23 18:33:14Behdad.Esfahbodcreate