Date: Wed, 28 Oct 2026 16:55:48 +0000
Yes, I want more than WhatWG, and not just that.
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.
What are you talking about?
WhatWG isn't an authority on ANY of those encodings.
You know the iso-8859-XYZ is a standard setup by ISO. Utf-X is defined by the Unicode standard, the windows-Z also have supporting documents setup by Microsoft.
The IANA list has references to the specs of the encoding defined by their enumeration.
Why are we still having this discussion?
Please explain to me, and I would really like to know. How would the C++ standard and C++ developers benefit from being able to transcode windows_874, be able to only transcode from Utf-16 big endian and little endia, but not be able to transcode to and from NATIVE utf-16.
What are we doing?
________________________________
From: Jens Maurer <jens.maurer_at_[hidden]>
Sent: Wednesday, October 28, 2026 4:48:50 PM
To: sg16_at_[hidden] <sg16_at_[hidden]>; Jonathan Wakely <cxx_at_[hidden]>
Cc: Tiago Freire <tmiguelf_at_[hidden]>
Subject: Re: [isocpp-sg16] P4246R0 Transcoding Text Views and Ranges for WhatWG and iconv
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
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.
What are you talking about?
WhatWG isn't an authority on ANY of those encodings.
You know the iso-8859-XYZ is a standard setup by ISO. Utf-X is defined by the Unicode standard, the windows-Z also have supporting documents setup by Microsoft.
The IANA list has references to the specs of the encoding defined by their enumeration.
Why are we still having this discussion?
Please explain to me, and I would really like to know. How would the C++ standard and C++ developers benefit from being able to transcode windows_874, be able to only transcode from Utf-16 big endian and little endia, but not be able to transcode to and from NATIVE utf-16.
What are we doing?
________________________________
From: Jens Maurer <jens.maurer_at_[hidden]>
Sent: Wednesday, October 28, 2026 4:48:50 PM
To: sg16_at_[hidden] <sg16_at_[hidden]>; Jonathan Wakely <cxx_at_[hidden]>
Cc: Tiago Freire <tmiguelf_at_[hidden]>
Subject: Re: [isocpp-sg16] P4246R0 Transcoding Text Views and Ranges for WhatWG and iconv
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
Received on 2026-10-28 16:55:52
