Tim Bray <tbray@xxxxxxxxxxxxxx> writes: > 4627 has been obsoleted by the current operative specification of JSON, > RFC8259 (disclosure: editor), from which: Well, ugh. I have to take it all back. Uh, is there a coherent explanation why RFC 8259 allows non-character code points? Or specifically why it allows surrogate code points? "net-yet-assigned" code points I can see as plausibly allowing, but surrogate code points will never be assigned characters. Dale -- last-call mailing list -- last-call@xxxxxxxx To unsubscribe send an email to last-call-leave@xxxxxxxx
