Date: Fri, 23 May 2025 10:11:34 +0200
Hello!
This paper updates Annex E onto Unicode 16.
However, the actual core issue we're trying to resolve
(and to which the paper is lacking a reference) is
CWG2843 Undated reference to Unicode makes C++ a moving target
https://cplusplus.github.io/CWG/issues/2843.html
which says
"More drafting to rebase Annex E on Unicode 15.1 is needed."
Note the difference between 15.1 and 16.
I have no clue whether the paper would apply to 15.1, too, or not.
Also, the wording changes remove [uaxid.def.rfmt], but contain
an "insert" of "UAX31-" into the heading of the removed section.
That seems like a stray "UAX31-" would remain after the edits.
That feels wrong.
Also, this paper adds the prefix "UAX31-" to most headings, but
omits an edit to the heading of [uaxid.def.stable].
That feels inconsistent.
Could we please have an updated paper prior to the upcoming SG16
discussion?
Jens
This paper updates Annex E onto Unicode 16.
However, the actual core issue we're trying to resolve
(and to which the paper is lacking a reference) is
CWG2843 Undated reference to Unicode makes C++ a moving target
https://cplusplus.github.io/CWG/issues/2843.html
which says
"More drafting to rebase Annex E on Unicode 15.1 is needed."
Note the difference between 15.1 and 16.
I have no clue whether the paper would apply to 15.1, too, or not.
Also, the wording changes remove [uaxid.def.rfmt], but contain
an "insert" of "UAX31-" into the heading of the removed section.
That seems like a stray "UAX31-" would remain after the edits.
That feels wrong.
Also, this paper adds the prefix "UAX31-" to most headings, but
omits an edit to the heading of [uaxid.def.stable].
That feels inconsistent.
Could we please have an updated paper prior to the upcoming SG16
discussion?
Jens
Received on 2025-05-23 08:11:44