Re: [I18ndir] [art] New Version Notification for draft-bray-unichars-06.txt

[Rob Sayre <[e-mail]>]

On Fri, Oct 6, 2023 at 6:14 PM Carsten Bormann <[e-mail]> wrote:

> +1
>
> For all intents and purposes, “Unicode character” should be understood
> (and, possibly, defined for use in a document) as “Unicode scalar value”.
> There are very few protocols that need finer detail about their repertoire.
> Obviously, the 1d and 2d subsets (see modern-network-unicode) make a lot
> of sense for 1d and 2d applications.
>
> That is really all that most of the people who need to design
> Unicode-based protocols need to know.
> Adding some knowledge about normalization may sometimes be useful (see
> Appendix C).
>

Oh, but this line doesn't work as a uniform approach. There are many
reasons for that, and we can't change them! Really. We are powerless.

What we can do is specify a way to send Unicode that does work. This draft
does do that. It is right.

But, let's imagine trying to punish people that send stuff like unpaired
surrogate code points. What are you going to do? Put them in jail?

The best way to go is to describe the right way, and this draft is pretty
good.

thanks,
Rob