FGCOM/jansson
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

conformance: remove U+0000 restriction for object keys

Browse Source 
Signed-off-by: Maxim Zhukov <mussitantesmortem@gmail.com>
This commit is contained in:
Maxim Zhukov 2020-08-06 18:02:57 +03:00
parent ca6775dee4
commit 16a3899a9e
1 changed files with 1 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
doc/conformance.rst
View File

@ -22,8 +22,7 @@ JSON strings are mapped to C-style null-terminated character arrays,
and UTF-8 encoding is used internally. and UTF-8 encoding is used internally.
All Unicode codepoints U+0000 through U+10FFFF are allowed in string All Unicode codepoints U+0000 through U+10FFFF are allowed in string
values. However, U+0000 is not allowed in object keys because of API values. However, U+0000 is allowed in object keys only for length-aware functions.
restrictions.
Unicode normalization or any other transformation is never performed Unicode normalization or any other transformation is never performed
on any strings (string values or object keys). When checking for on any strings (string values or object keys). When checking for