On 29/11/2021 12.23, Peter Brett wrote:
> As a quick follow-up, several of the points made in the new paper:
>
> P2491 Text encodings follow-up (Jens Maurer)
> https://wg21.link/p2491r0
>
> rest on the discrepancy in the specification of the UTF-16 encoding scheme between the Unicode Standard 14.0.0 and ISO 10646:2020. The project editor for ISO 10646 believes this to be a defect which will be brought into line with the Unicode Standard in the next revision of ISO 10646, which is currently being prepared.
>
> I hope that P2491 can be revised to mention this.

Does ISO 10646 have a defect tracking system that is publicly
visible, so that we can monitor the progress and have a bug-id
to refer to?

Beyond that, I believe the reference to "higher-level protocol"
in the proposed resolution is underspecified; I don't know what
a "higher-level protocol" is.

Beyond that, Note 3 in section 12 of ISO 10646:2020 (not Note 2 as
mentioned in the paper) suggests "0007 BELL", which is ambiguous
with U+1F514 BELL. This should use "ALERT" instead.

I hope that N5168 can be revised to fix these issues.

Jens



> Best regards,
>
> Peter
>
>> -----Original Message-----
>> From: SG16 <sg16-bounces_at_[hidden]> On Behalf Of Peter Brett via SG16
>> Sent: 29 November 2021 10:55
>> To: sg16_at_[hidden]
>> Cc: Peter Brett <pbrett_at_[hidden]>
>> Subject: [SG16] ISO10646 defect report
>>
>> EXTERNAL MAIL
>>
>>
>> Hi all,
>>
>> I've filed a defect report against ISO10646:2020. Please see the attached
>> paper.
>>
>> The project editor thinks that the defects can be resolved in the next
>> revision, which will be helpful.
>>
>> Best wishes,
>>
>> Peter