[i18n-activity] Abstract wording inexact

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

== Abstract wording inexact ==
CSS Writing Modes Level 4
https://www.w3.org/TR/2017/WD-css-writing-modes-4-20171207/

> CSS Writing Modes Level 4 defines CSS support for various international writing modes, such as left-to-right (e.g. Latin or Indic), right-to-left (e.g. Hebrew or Arabic), bidirectional (e.g. mixed Latin and Arabic) and vertical (e.g. Asian scripts).

The terms 'right-to-left', 'bidirectional', and 'vertical' are slightly abused here. While the spec understands the issues, a casual reader looking at the spec would have incorrect assumptions about RTL scripts reinforced and might have the impression that vertical writing is either the default for CJK or only a CJK artifact. While the abstract is trying to convey what the doc is about without being overly pedantic, perhaps a bit more would be useful here. I'd suggest something like:

> CSS Writing Modes Level 4 defines CSS support for various international writing modes, such as the vertical presentation of text (which is most common in Asian scripts) or support for horizontal presentation, including directional variation in bidirectional scripts (predominantly right-to-left text in scripts such as Arabic and Hebrew).

---
**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/521 using your GitHub account

Received on Thursday, 14 December 2017 18:45:03 UTC