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

> The common case where you don't want language or direction information is for non-language-bearing fields (isbn).

Watch out though, apparently harmless data may not actually be so. The isbn field will only display correctly if it is _isolated_ when displayed in a RTL target context and treated as LTR inside that isolated area. For example, if i just drop the text into a field on a RTL page without any precautions, i get:

![screen shot 2017-07-17 at 18 11 08](https://user-images.githubusercontent.com/4839211/28280380-7a91fdcc-6b1b-11e7-8dc9-341d77ad51d3.png)

rather than what i really want, which is:

![screen shot 2017-07-17 at 18 11 19](https://user-images.githubusercontent.com/4839211/28280391-81235b68-6b1b-11e7-9ab8-2a073370593a.png)

However, if the value were a range, such as 100-300, the first arrangement would actually be what's wanted in Arabic (though not Hebrew, and i'm not sure about N'Ko), otherwise the range would appear to be decreasing instead of increasing.

So it may actually be useful to have some direction information for isbn numbers, MAC addresses, telephone numbers, etc.

-- 
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-315823318