What Docs changes are you proposing?
JSON is a very successful data format, but its string type is very simple. A value such as a title and name often needs more than Unicode characters. Consumers may need to know the language of the text and its direction, e.g., when displaying right-to-left scripts such as Arabic or Hebrew. Without that metadata, applications fall back to guessing, and guessing often fails.
The W3C Internationalization Working Group has a document on this topic: Strings on the Web: Language and Direction Metadata, which is a practical guide for specifications and formats that exchange strings. I'd like to write a blog post about this.
(See also json-schema-org/json-schema-spec#1710 )
Code of Conduct
What Docs changes are you proposing?
JSON is a very successful data format, but its string type is very simple. A value such as a title and name often needs more than Unicode characters. Consumers may need to know the language of the text and its direction, e.g., when displaying right-to-left scripts such as Arabic or Hebrew. Without that metadata, applications fall back to guessing, and guessing often fails.
The W3C Internationalization Working Group has a document on this topic: Strings on the Web: Language and Direction Metadata, which is a practical guide for specifications and formats that exchange strings. I'd like to write a blog post about this.
(See also json-schema-org/json-schema-spec#1710 )
Code of Conduct