[Python-ideas] Support WHATWG versions of legacy encodings

Rob Speer rspeer at luminoso.com
Tue Jan 9 22:56:12 EST 2018

One other thing I've noticed that's related to the WHATWG encoding list: in
Python, the encoding name "windows-874" seems to be missing. The _encoding_
is there, as "cp874", but "windows-874" doesn't work as an alias for it the
way that "windows-1252" works as an alias for "cp1252". That alias should
be added, right?

On Tue, 9 Jan 2018 at 21:46 Nick Coghlan <ncoghlan at gmail.com> wrote:

> On 10 January 2018 at 09:56, Rob Speer <rspeer at luminoso.com> wrote:
> > Oh that's interesting. So it seems to be Python that's the exception
> here.
> >
> > Would we really be able to add entries to character mappings that haven't
> > changed since Python 2.0?
> Changing things that used to cause an exception into operations that
> produce a useful result is generally OK - it's going the other way
> (dubious output -> exception) that's always problematic.
> So as long as the Windows specialists give it a +1, updating the
> existing codecs to match the MultiByteToWideChar behaviour seems like
> a better option to me than offering multiple versions of the codecs
> (and that could then be done as a tracker enhancement request along
> the lines of "Make the windows-* text encodings match
> MultiByteToWideChar").
> Cheers,
> Nick.
> --
> Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-ideas/attachments/20180110/e7ebd3a0/attachment.html>

More information about the Python-ideas mailing list