Date: Wed, 28 Oct 2026 16:48:33 +0100
On 10/28/26 15:12, Tiago Freire via SG16 wrote:
>> That's presumably why the proposed APIs are called whatwg_encode and whatwg_decode, not universal_encode or generic_encode
>
> [...] Because what I want is generic transcoding,
I understand that WhatWG specifies the encoding and decoding of certain encodings
in detail.
You appear to be wanting more than the WhatWG encodings.
WG21 is not in the business of specifying character encodings, so we'd need
to refer to another standard for the details of each encoding.
Please name a particular encoding that isn't covered by WhatWG, and point
to the location of its specification. No, the IANA list is not that.
"IANA" is "Internet Assigned Numbers Authority", essentially a maintainer
of enums and numeric values to ensure those numeric values are unique.
Having a name such as "UTF-8" and a number doesn't provide a specification
of the encoding; we need a specification for that. For example, in the
case of UTF-8, Unicode provides that specification.
Jens
>> That's presumably why the proposed APIs are called whatwg_encode and whatwg_decode, not universal_encode or generic_encode
>
> [...] Because what I want is generic transcoding,
I understand that WhatWG specifies the encoding and decoding of certain encodings
in detail.
You appear to be wanting more than the WhatWG encodings.
WG21 is not in the business of specifying character encodings, so we'd need
to refer to another standard for the details of each encoding.
Please name a particular encoding that isn't covered by WhatWG, and point
to the location of its specification. No, the IANA list is not that.
"IANA" is "Internet Assigned Numbers Authority", essentially a maintainer
of enums and numeric values to ensure those numeric values are unique.
Having a name such as "UTF-8" and a number doesn't provide a specification
of the encoding; we need a specification for that. For example, in the
case of UTF-8, Unicode provides that specification.
Jens
Received on 2026-10-28 15:48:44
