C++ Logo


Advanced search

Re: [SG16] P1885: Naming text encodings: Curation and provenance of aliases

From: Jens Maurer <Jens.Maurer_at_[hidden]>
Date: Wed, 8 Sep 2021 18:50:44 +0200
On 08/09/2021 18.08, Hubert Tong via SG16 wrote:
> As it is, I think it is worthwhile to revisit whether the generality of the implementation-defined behaviour is advisable. It seems that, as the paper evolved, at least one implementation-injected alias was meant to be the "preferred name" on the system returned or recognized by various APIs (e.g., iconv_open). Even that is problematic: There is a tendency in converter applications to treat a de facto "reigning" extension as being what is meant when the non-extended standard is requested. In highly architected environments, the csShiftJIS and csWindows31J "problem" that is present in ICU would manifest as there being only one API-recognized "preferred name". The present design intent of P1885 in having non-overlapping sets of aliases is in conflict with the desire to associate the "preferred name" as an alias in such situations.

You seem to be saying that the preferred name for both csShiftJIS and
csWindows31J is supposed to be "Shift-JIS" (or so), but an alias is
supposed to be globally unique under P1885.


Received on 2021-09-08 11:50:56