➜

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 serhiy.storchaka
Recipients amaury.forgeotdarc, doerwalter, lemburg, ncoghlan, scoder, serhiy.storchaka, vstinner
Date 2017-03-25.13:39:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1490449148.32.0.380025573408.issue18059@psf.upfronthosting.co.za>
In-reply-to
Content 
Marc-Andre, there are at least two issues about supporting East Asian encodings (issue13612 and issue15877). I think this means that that encodings are used in XML in wild. Current support of encodings (8-bit + UTF-8 + UTF-16) is enough for my needs, but I never have deal with East Asian languages.

Currently the CodecInfo object has an optional flag _is_text_encoding. I think we can add more private attributes (flags and precomputed tables) for using with the expat parser. If they are not set (third-party encodings) the current autodetection code can be used as a fallback.
History
Date User Action Args
2017-03-25 13:39:08serhiy.storchakasetrecipients: + serhiy.storchaka, lemburg, doerwalter, amaury.forgeotdarc, ncoghlan, scoder, vstinner
2017-03-25 13:39:08serhiy.storchakasetmessageid: <1490449148.32.0.380025573408.issue18059@psf.upfronthosting.co.za>
2017-03-25 13:39:08serhiy.storchakalinkissue18059 messages
2017-03-25 13:39:08serhiy.storchakacreate