[issue25416] Add encoding aliases from the (HTML5) Encoding Standard

Marc-Andre Lemburg added the comment: Please note that we can only add aliases if the encodings are indeed the same. Given that WhatWG has made changes to several standard encodings, this is especially important, since our codecs are mostly based on what the Unicode consortium defines as

[issue25416] Add encoding aliases from the (HTML5) Encoding Standard

Felipe Rodrigues added the comment: Ezio, I have issued a simple PR that adds just the two aliases cited in the issue's initial message. I would like to implement tests but as I wrote in the PR's message, I'm not really sure how to proceed with that. bpo-18624 is really related to this

[issue25416] Add encoding aliases from the (HTML5) Encoding Standard

Change by STINNER Victor : -- nosy: -vstinner ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue25416] Add encoding aliases from the (HTML5) Encoding Standard

Ezio Melotti added the comment: Adding those aliases sounds good to me. I think it would be good to add some tests first (possibly as a separate issue/pr), even though I'm not sure what would be the best way to test the aliases. Testing if the list is complete/correct should be done

[issue25416] Add encoding aliases from the (HTML5) Encoding Standard

Change by Felipe Rodrigues : -- keywords: +patch pull_requests: +9549 stage: needs patch -> patch review ___ Python tracker ___ ___

[issue25416] Add encoding aliases from the (HTML5) Encoding Standard

Changes by Serhiy Storchaka : -- components: +Unicode nosy: +ezio.melotti, haypo, lemburg, loewis stage: -> needs patch versions: +Python 3.6 ___ Python tracker