[art] Re: draft-bray-unichars-09 review

[Rob Sayre <[e-mail]>]

On Fri, Oct 4, 2024 at 7:22 AM Orie Steele <[e-mail]>
wrote:

> Hi,
>
> This is not yet my AD evaluation, if you think I missed something obvious
> here, please let me know so I can address it when this document moves to AD
> Evaluation.
>

I think everything in these comments are topics on which reasonable people
can disagree.

I will pick one.


### Where is UTF-16 used?
>
> ```
> 178   A surrogate which occurs in text encoded in any transformation format
> 179   other than UTF-16 has no meaning and may cause malfunction in
> 180   software that encounters it.  In particular, it is impossible to
> 181   represent a surrogate in well-formed UTF-8.
> ```
>
> Some guidance here on where to expect UTF-16 could help explain where to
> expect surrogates.
>

It's not possible to describe in an IETF standard, because these are not
sent over the network. Except in JSON, in an undesirable way, occasionally.

Maybe it would be better to say something like "Operating systems have many
error-prone implementations of UTF-16, and these leak into UTF-8 protocols.
It is unfortunate."

thanks,
Rob