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

[Tim Bray <[e-mail]>]

On Oct 1, 2023 at 9:34:44 AM, Carsten Bormann <[e-mail]> wrote:

>
>
> See
> https://www.ietf.org/archive/id/draft-bormann-dispatch-modern-network-unicode-03.html#name-normalization
>

I think everyone who’s been following this discussion has now read
modern-network-unicode draft. It’s interesting! I would be mildly in favor
of spinning up a WG to consider it.  But only mildly because I spent many
years in the publishing-technology world, and discussion of line-end
semantics and normalization forms tend to have an infinite tendency to
rat-hole. So it would be a long difficult march.  You’d need strong
co-chairs with infinite patience.

Unpaired surrogate code points and their escaped form need to be covered,
> since the standard behavior of billions of web browsers is to smuggle them
> in well-formed UTF-8 via escape sequences. [2]
>
> But this is about JavaScript (and its half-broken character model), not
> about Unicode.
>

Yeah, but it’s part of the reason why it’s worthwhile to warn people to be
explicit about character repertoires.

>
>