Well, don't keep us in suspense, Jens.

What *does* ISO 10646 define as the UTF-16 encoding scheme?

Best regards,

              Peter

> -----Original Message-----
> From: SG16 <sg16-bounces_at_[hidden]> On Behalf Of Jens Maurer via SG16
> Sent: 06 October 2021 12:20
> To: sg16_at_[hidden]
>
> On 06/10/2021 11.35, Corentin Jabot via SG16 wrote:
> >
> >
> >
> > On Wed, Oct 6, 2021 at 8:31 AM Hubert Tong via SG16 <sg16_at_[hidden]
> <mailto:sg16_at_[hidden]>> wrote:
> >
> > Concern for SG 16 to evaluate:
> > The recommended practice re: UTF-16 and UTF-32 is not consistent with
> getting the correct treatment out of interfaces that attempt to read the
> wide character data as a byte stream (e.g., iconv) when there are invalid
> characters in a position to be confused as reverse-from-native-endian BOMs.
> >
> >
> > UTF-16 is synonymous to either UTF-16BE/UTF-16LE depending on the
> platform.
> > The endianness is implied by the platform, not by text_encoding.
>
> That is not what ISO 10646 defines as the UTF-16 encoding scheme.