... Yup, it got here in Normalization Form C, using U+00C4 in both cases. But that's email for you, and perhaps that's Apple for you too. I'd stick with...
1616
John Cowan
johnwcowan
Mar 2, 2011 7:27 pm
... Actually, it doesn't mean anything, because the RFC only says that the keys of an object SHOULD (not MUST) be unique. In practice, people probably parse...
1615
John Cowan
johnwcowan
Mar 2, 2011 7:20 pm
... I don't think so. In particular, it is often helpful to allow keys named "$" or "#foo" or such. In any case, the normalization rule for JavaScript ...
1614
John Cowan
johnwcowan
Mar 2, 2011 6:45 pm
... Indeed they would, which is precisely why {foo: "bar"} is not conformant JSON any more than {if: "bar"} would be, although the first is conformant ...
1613
Dave Gamble
signalzerodb
Mar 2, 2011 6:43 pm
... I am aware of that :) It occurs to me that since the intention is that JSON text deserializes into an instanced object, which will in some cases be a ...
1612
Dave Gamble
signalzerodb
Mar 2, 2011 6:39 pm
To save people looking it up: ECMA-262, section 7.6: Two IdentifierName that are canonically equivalent according to the Unicode standard are not equal unless...
1611
John Cowan
johnwcowan
Mar 2, 2011 6:38 pm
... In JSON, unquoted keys are not permitted, so both keys and values are strings. -- Unless it was by accident that I had John Cowan offended...
1610
Dave Gamble
signalzerodb
Mar 2, 2011 6:29 pm
Better question: How does the ECMA/javascript spec limit variable names? This seems to be the same question, in practical terms. Dave. ... [Non-text portions...
1609
Dave Gamble
signalzerodb
Mar 2, 2011 6:21 pm
Would it be too much to specify that key names are to be ASCII top-bit-unset strings? i.e. in the definition of an object, designate that the "string" there is...
1608
mehdigholam@...
mehdigholam...
Mar 2, 2011 6:17 pm
Hello all, Huge optimizations again for fastJSON the .net implementations. http://www.codeproject.com/KB/IP/fastJSON.aspx Cheers,...
1607
johne_ganz
Mar 2, 2011 4:46 am
... The Foundation framework (specifically the NSString class) on Mac OS X and iPhone / iPad does. Not sure if 90+ million iPhones count for much, though. In...
1606
johne_ganz
Mar 2, 2011 3:58 am
... It is my opinion that the answer is "Yes". The standard must address some of the issues introduced by the use of Unicode (see below). Then there is the...
1605
Petri Lehtinen
akhern...
Feb 28, 2011 7:31 pm
Jansson 2.0 is finally out. This is a new major release that is (slightly) backwards incompatible with the older versions. Changes since v1.3 ... * Backwards...
1604
mehdigholam@...
mehdigholam...
Feb 27, 2011 7:47 am
Hello all, Huge speed optimizations in fastJSON v1.4 now officially the fastest JSON on the .net platform. http://www.codeproject.com/KB/IP/fastJSON.aspx...
1603
Douglas Crockford
douglascrock...
Feb 27, 2011 12:07 am
... No. ... Right....
1602
Tatu Saloranta
cowtowncoder
Feb 26, 2011 9:03 pm
... This sounds reasonable to me as well. -+ Tatu +-...
1601
Tatu Saloranta
cowtowncoder
Feb 26, 2011 8:59 pm
... Yes. ... Ok. But in this case, would JSON specification itself help a lot? I understand that this is problematic, in that different platforms can choose...
1600
John Cowan
johnwcowan
Feb 26, 2011 8:09 pm
... So you are now conceding that it's invalid JSON to send through unpaired surrogate code units, since they don't correspond to code points? We discussed...
1599
John Cowan
johnwcowan
Feb 26, 2011 8:08 pm
... You are over-interpreting the standard. Of course applications can delete characters: sed -s 's/t//' deletes all t's from the input. And that's all...
1598
John Cowan
johnwcowan
Feb 26, 2011 8:05 pm
... Normalization is non-trivial, and I doubt if any existing Unicode library imposes it on all strings at creation/modification time. Certainly ICU does not;...
1597
Douglas Crockford
douglascrock...
Feb 26, 2011 6:04 pm
... That's not quite right. JSON says nothing at all about number representations. All it knows is sequences of digits with the occasional decimal points. JSON...
1596
John Cowan
johnwcowan
Feb 26, 2011 5:04 pm
... I agree in part. JSON parsers MUST NOT normalize their inputs, for the reasons given upthread. But JSON generators SHOULD generate normalization form C,...
1595
John Cowan
johnwcowan
Feb 26, 2011 4:54 pm
... I think that limit is implied by the statement in the "Security considerations"; section that says that JSON is a subset of JavaScript, where numbers are...
1594
Mark Slater
markosslater
Feb 26, 2011 11:05 am
Regarding the handling of numbers, the RFC doesn't appear to make any mention of native representations of numbers - in fact, it only specifies what...
1593
johne_ganz
Feb 26, 2011 5:08 am
... This is my point. It happens both on the serialization side, but (at least in my opinion), it is much more likely to happen on the deserialization side. ...
1592
johne_ganz
Feb 26, 2011 4:01 am
... True. It would seem, at least to me, that this is one of those nuanced points that either a) Has not been given the proper consideration by Unicode...
1591
Douglas Crockford
douglascrock...
Feb 26, 2011 12:44 am
... I agree....
1590
David Graham
dgraham...
Feb 26, 2011 12:35 am
I had the normalization question while writing json-stream in Ruby as well. I decided the parser shouldn't do Unicode normalization for the following reasons: ...
1589
Tatu Saloranta
cowtowncoder
Feb 25, 2011 11:45 pm
On Fri, Feb 25, 2011 at 3:09 PM, johne_ganz <john.engelhart@...> wrote: ... This is true statement, although the more practical question seems to be what...
1588
Tatu Saloranta
cowtowncoder
Feb 25, 2011 11:25 pm
... Do you have an ACTUAL problem worth discussion, or is this from just purity standpoint? -+ Tatu +-...
