> Because nobody uses it for web pages (https://w3techs.com/technologies/overview/character_encoding) and email,
Yet!
> and because no encoding/decoding is needed to convert UTF-32 data to scalar values. So the entire encoding spec is unnecessary for UTF-32, it's a no-op.
I disagree. I don’t do web. I want to transcode to and from UTF-32, and it deserves to be a proper citizen with an enum to match if everybody else has one. If you are arguing that we only should use this for web, then that is fine, but then I would argue that Chromium already exists and it doesn’t need to added into the standard.
Let’s not forget what the WhatWG is. Which is a group of browser vendors deciding that the way their browsers work should the way everybody else’s browser should work, regardless of what other innovations the technology would allow. And I am not particularly comfortable endorsing what essentially amounts to corporate induced barnacles disguised as an “open web standard” into other standards that have absolutely nothing to do with the web other than “it can be used to make web apps”.
> Which IANA standard are you talking about?
The IANA standard for character set identification numbers. https://www.iana.org/assignments/character-sets
If there is going to be an enum identifying the different encodings there is not a single doubt in my mind that that should be the IANA’s one and not WhatWG.
And if that ever was up to an open vote I would have no doubt which one would have majority support. Or do you doubt this?
And yes, if we did that then the “WhatWG” implementation wouldn’t work. Which is another reason not to do it.
People may have other opinions on this, but for me this is a hard NO. No way!