[i18n-activity] base direction considerations (#685)

aphillips has just created a new issue for https://github.com/w3c/i18n-activity:

== base direction considerations ==
(general)
https://cdn.staticaly.com/gh/w3c/wot-thing-description/TD-TAG-review/index.html?env=dev

As discussed in the [teleconference](https://www.w3.org/2019/04/18-i18n-minutes.html), no reference is made to support for bidirectional text values. The I18N WG has recently published a document ([string-meta](https://www.w3.org/TR/string-meta)) and has had a number of issues open against other WGs as well as TAG regarding the problem of identifying and conveying the base direction of text in data formats, such as those based on JSON-LD, schema.org, RDF, and so forth.

We do not have a general purpose solution to offer currently. Because your spec is only "notionally" conformant to some of the aforementioned standards, you might be free to adopt some of the suggested designs (notably the `Localizable` pattern) in our draft. However, that's probably not a good idea, given that standardization work in this area in the (hopefully near term) future might go in a different direction and leave your implementers orphaned. In any case, this is an important problem. We would suggest:

* include a health warning describing the problem (probably by referring to string-meta)
* suggest that producers generate bidi controls or markers as appropriate to try to ensure proper display
* suggest that consumers apply bidi isolation (which they should do anyway) and employ first-strong heuristics in the absence of base direction metadata

---
**WHEN CREATING A NEW ISSUE DO SO ABOVE THIS PARAGRAPH, REPLACING THE PROMPTS, BUT LEAVE THIS PARAGRAPH INTACT AS WELL AS THE TEXT BELOW IT** When this issue is raised in the github/bugzilla/mail of the WG that owns the spec, use the text above this para as the basis for that comment. Then edit this issue to remove this paragraph and ALL THE TEXT ABOVE IT. Replace the text 'link_to_issue_raised' below with a link to the place you raised the issue, but leave the remaining text below this para unaltered.

**This is a tracker issue.** Only discuss things here if they are i18n WG internal meta-discussions about the issue. **Contribute to the actual discussion at the following link:**


ยง link_to_issue_raised



Please view or discuss this issue at https://github.com/w3c/i18n-activity/issues/685 using your GitHub account

Received on Friday, 19 April 2019 21:25:17 UTC