Re: [I18ndir] [art] Just uploaded draft-bray-unichars-03

[Tim Bray <[e-mail]>]

On Sep 10, 2023 at 1:43:07 AM, Asmus Freytag <[e-mail]> wrote:

I sympathize with the desire not to bring in the entire formalism, so the
> following suggestion might suffice to limit the sense of "transformation
> format" that is intended here.
>
> Unicode describes a variety of "transformation formats", ways to *uniquely
> *encode *each **scalar value* into bytes of computer memory. A survey of
> transformation formats is beyond the scope of this document.
>
> If you like to avoid the term "scalar value" - it is synonymous to
> "non-surrogate code point".
>
The common perception of the meaning of “transformation format” is “UTF-8,
UTF-16, those kinds of things” which is essentially correct and I’m not
sure that it’s good investment of Unicode Consortium effort to try to fix
that. Furthermore, I am pretty sure that most people understand that \u2345
is a JSON-specific thing that is unrelated to transformation formats.

What I’m saying is that I think that the current text is unlikely to
mislead anyone, because the popular understanding of what it means is
pretty well correct. The -04 rev currently under construction calls out
escape sequences and makes it clear that “\uDEAD” is not a way to route
around code point repertoire restrictions.

Let’s revisit this after we’ve seen -04 and if enough people think that the
use of “transformation formats” is still misleading, I think Asmus’
suggestion is OK.


A./
>
>
>
> thanks,
> Rob
>
>
>
>