Date: Wed, 4 Jun 2025 08:26:05 +0200
On 03.06.25 18:52, Corentin Jabot wrote:
> I don't see the value of the added [uaxid.def.rfmt], otherwise LGTM
>
> On Sat, May 31, 2025 at 11:02 PM Steve Downey via SG16 <sg16_at_[hidden] <mailto:sg16_at_[hidden]>> wrote:
>
> Paper for minimally changing Annex E to reflect UAX 31 as of Unicode 15.1 for C++26.
>
> Remove R1a Restricted format characters
[uaxid.def.rfmt] needs to go entirely. There is no point in keeping a sort-of change history here.
> Remove descriptions of how the standard does not conform with list from 15.1, just state we don't.
The previous version of the paper appeared to do the minimum necessary to reflect
Unicode 16 and kept all the detailed "we don't conform" statements in. Now, the ask
was to rebase on 15.1. What is the rationale for changing the approach towards the
"we don't conform" utterances for such a rather trivial rebase?
Jens
> I don't see the value of the added [uaxid.def.rfmt], otherwise LGTM
>
> On Sat, May 31, 2025 at 11:02 PM Steve Downey via SG16 <sg16_at_[hidden] <mailto:sg16_at_[hidden]>> wrote:
>
> Paper for minimally changing Annex E to reflect UAX 31 as of Unicode 15.1 for C++26.
>
> Remove R1a Restricted format characters
[uaxid.def.rfmt] needs to go entirely. There is no point in keeping a sort-of change history here.
> Remove descriptions of how the standard does not conform with list from 15.1, just state we don't.
The previous version of the paper appeared to do the minimum necessary to reflect
Unicode 16 and kept all the detailed "we don't conform" statements in. Now, the ask
was to rebase on 15.1. What is the rationale for changing the approach towards the
"we don't conform" utterances for such a rather trivial rebase?
Jens
Received on 2025-06-04 06:26:13