But JSON doesn’t generally require special encoding for unicode characters.
Technically, JSON is UTF-8 encoded, but that’s true of NestedText too so that can’t be what they mean.
Also, of JSON it says:
> in JSON 32 is an integer, 32.0 is the real version of 32...
But JSON doesn’t distinguish integer from real. It only has number.
On the format itself, I wonder if it needs some testing and hardening. The definition seems ambiguous, but maybe just needs a formal grammar. Just from reading it, tab handling seems like an issue. I think you could have documents that look right but have invisible issues due to tabs. E.g., it sounds like tab can be a character in a dictionary key name, which looks like indentation.
> Unicode characters without encoding them
But JSON doesn’t generally require special encoding for unicode characters.
Technically, JSON is UTF-8 encoded, but that’s true of NestedText too so that can’t be what they mean.
Also, of JSON it says:
> in JSON 32 is an integer, 32.0 is the real version of 32...
But JSON doesn’t distinguish integer from real. It only has number.
On the format itself, I wonder if it needs some testing and hardening. The definition seems ambiguous, but maybe just needs a formal grammar. Just from reading it, tab handling seems like an issue. I think you could have documents that look right but have invisible issues due to tabs. E.g., it sounds like tab can be a character in a dictionary key name, which looks like indentation.