- From: Addison Phillips via GitHub <sysbot+gh@w3.org>
- Date: Thu, 25 May 2017 16:58:41 +0000
- To: public-i18n-archive@w3.org
aphillips has just created a new issue for https://github.com/w3c/i18n-activity: == Recommended Characters Sets considered harmful == 7.2 Recommended Character Sets https://www.w3.org/TR/ttml-imsc1.0.1/#recommended-character-sets > A Document Instance SHOULD be authored using characters selected from the sets specified in B. Recommended Character Sets. This text and the text in _Appendix B_ is intended to describe content restrictions that authors should observe when writing captions and subtitles in a TTML document. There are a number of problems with this: 1. Numerous important languages and their scripts, most notably the Chinese/Japanese/Korean scripts, but also, for example, the scripts of South Asia/India, the scripts of Southeast Asia, and so forth are completely omitted. These comprise large audiences who might well use TTML and IMSC, but who are excluded from consideration. 2. The reference materials that do exist have gaps in coverage or are uneven in the recommended glyph set supported by the fonts. For example, only `pt` and `es` include the currency symbols other than $ and Euro. Why this is the case is not clear. 3. Rendering systems generally use font fallback to provide coverage with high-enough quality for multiple scripts rather than using a single font or font collection. If the goal is to describe limited capacity devices, such as a (non-smart) TV which will have a single or small number of hardcoded fonts for captioning built in, it would be more useful to describe a few "profiles" for minimum glyph sets than trying to break it out by language. Even then, I'd be concerned that we're artificially promoting to implementers specific language support rather than providing useful guidance to authors. --- **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. Contribute to the actual discussion at the following link:** link_to_issue_raised Only discuss things here if they are i18n WG internal meta-discussions about the issue. Please view or discuss this issue at https://github.com/w3c/i18n-activity/issues/420 using your GitHub account
Received on Thursday, 25 May 2017 16:58:48 UTC