Re: [w3ctag/design-reviews] Serialization of natural language in data formats such as JSON [I18N] (#178)

> Solution 1: New Data Type
> Create a new data type whose serialization optionally includes language and direction. Examples:
> 
> myLocalizedString: "Hello World!"@en^ltr
> myLocalizedString_fr: "Bonjour monde !"@fr
> myLocalizedString_ar: "مرحبا بالعالم!"@ar-EG^rtl
> myLocalizedString_und: "שלום עולם!"^rtl
> myLanguageNeutralString: "978-0-123-4567-X" // no language or direction for this non-natural-language string

There are quite a few parser implementations out in the wild already for this approach to be feasible - and since parsers which do not support this feature will not function against data with these tags present, this does not seem like a way forward.

We did briefly touch on http://unicode.org/faq/languagetagging.html during the call, in case that would be an option.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/178#issuecomment-306535246