Re: [encoding] Consider making the DOM name the canonical name (#32)

> potential future uses, but those should probably not exist since there's utf-8.

Indeed.

> (Note that it's not 100% IANA casing

Good point. Not only `GB18030` vs. `gb18030` but also `ibm866` vs. `IBM866`. Now I really wonder where WebKit got its casing from. Did they copy Gecko after all but failed to copy `gbk`?

Anyway, I still think the concept _name_ should directly be what's currently the DOM _compatibility name_.

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/encoding/issues/32#issuecomment-174419657

Received on Monday, 25 January 2016 06:57:32 UTC