* Frank Ch. Eigler:
>> > Yes, and yet we have had the bidi situation recently where UTF-8 raw
>> > codes could visually confuse a human reader whereas escaped \u
>> > wouldn't. If we forbid \u unilaterally, we literally become
>> > incompatible with JSON (RFC8259 7. String. "Any character
Hi -
> JSON has been targeted at the Windows/Java UTF-16 world, there is always
> going to be a mismatch if you try to represent it in UTF-8 or anything
> that doesn't have surrogate pairs.
The JSON RFC8259 8.1 mandates UTF-8 encoding for situations like ours.
> > Yes, and yet we have had the b
