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

[Rob Sayre <[e-mail]>]

On Sat, Sep 23, 2023 at 9:54 AM Carsten Bormann <[e-mail]> wrote:

> On 2023-09-23, at 18:51, Tim Bray <[e-mail]> wrote:
> >
> > I can’t see any reason to discuss string processing in programming
> languages. The IETF is concerned with the bytes that flow across the
> network. Our job is to document what to transmit and what to receive.
>

I think this stance is correct. The example MDN thing I sent was all in JS,
but you could send that JSON message over the network in well-formed UTF-8.
The ECMA JS WG, TC-39, altered their JSON.stringify API to produce this
type of message: <https://github.com/tc39/proposal-well-formed-stringify> .
It even mentions I-JSON in the "Discussion" section.


> (And, by the way, more modern programming languages tend to ensure strings
> are always valid, so such a discussion would be specific to the ones that
> don’t do that.)
>

Well, sort of. The ones that do that usually have other string types (OS
strings, C strings, byte strings) that don't enforce well-formedness, since
these are necessary to interact with other programs. But things like Swift
and Rust are pretty nice if you can stick to their basic string types.

thanks,
Rob