Carsten Bormann writes:
> On 2. May 2025, at 12:04, Henry Thompson via Datatracker <noreply@xxxxxxxx> wrote:
>>
>> ["26bc4LT-ac6q2KI6cBW5es", "family_name", "M%xc3%xb6bius"] [2]
>
> The weird %x notation in the third element has nothing to do with
> JSON, which makes it difficult for me to understand the rest of what
> you are trying to say.
Apologies for the difficulty, but this is a very tricky area, in which
I think this spec. needs to be very careful to illustrate accurately
all of UNICODE characters,
* JSON strings (as type instances), components of JSON objects
* What RFC 8259 calls "JSON text", the kind of thing you might find
in a file or see rendered on screen
* UTF-8 encoded JSON text, i.e. byte sequences which when decoded
result in JSON text which, when parsed, yields JSON objects.
The problem you've encountered arises when one tries to illustrate
UTF-8 byte sequences in an unambiuous way in, for example, an IETF
RFC.
My recommendation is to follow RFC 8259's lead, and use e.g. "%xC3"
for that purpose.
Hope this helps,
ht
--
Henry S. Thompson, School of Informatics, University of Edinburgh
10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND
e-mail: ht@xxxxxxxxxxxx
URL: https://www.ltg.ed.ac.uk/~ht/
[mail from me _always_ has a .sig like this -- mail without it is forged spam]
--
last-call mailing list -- last-call@xxxxxxxx
To unsubscribe send an email to last-call-leave@xxxxxxxx
