Re: [Json] Proposal for strings/Unicode text

[Norbert Lindenberg <[e-mail]>]

On Jun 12, 2013, at 15:54 , Tim Bray wrote:

> On Wed, Jun 12, 2013 at 3:46 PM, Norbert Lindenberg <[e-mail]> wrote:
> The JSON RFC seems to use Unicode character names, in this case case "reverse solidus".
> 
> We’re not allowed to change JSON but we are allowed to improve the spec. The term “solidus” is obscure and off-putting.

If that's how you feel: Is there a proposal then to replace all occurrences of "solidus" and "reverse solidus" in the RFC? There are more, and the issue doesn't seem connected to the character vs. code point issue.
 
>> > 16-bit quantities (normally Unicode characters from the Basic Multingual Pane(U+0000 through U+FFFF) may be “escaped”, or represented as a six-character sequence: a backslash (U+005C REVERSE SOLIDUS), followed  by the lowercase letter u, followed by four hexadecimal digits that encode the character's code point.  The hexadecimal letters A though F can be upper or lower case.  So, for example, a string containing only a single backslash may be represented as "\u005C".
>> 
>> These escape sequences aren't about 16-bit quantities - they represent Unicode BMP code points.
>  
> They also represent surrogates.  Thus they combine fish and bicycles, and I think the only accurate way to describe what you can escape is “16-bit quantities”

Surrogate code points are BMP code points (see http://www.unicode.org/glossary) They are an awkward kind of code point and are best avoided, but I don't see what fish or bicycles have to do with them.

Also, as I explained before, in some environments there are no 16-bit quantities in either input or output.

Norbert