- From: r12a <ishida@w3.org>
- Date: Thu, 8 Feb 2018 11:47:23 +0000
- To: public-hlreq-admin@w3.org
hlreq folks, Over recent months at the W3C we've been formulating a new approach to lreq work. Here is a quick overview, but please read the following for more details prior to the meeting on Tuesday. https://github.com/w3c/i18n-discuss/wiki/Analysing-support-for-text-layout-on-the-Web https://github.com/w3c/typography/wiki/Setting-up-a-Gap-Analysis-Project We are now encouraging groups to develop a gap analysis document first, which aims 1. to describe issues for support in web browsers and ereaders for features of one or more languages, 2. to document them and 3. to use a broad classification to describe the severity of the issue. Once an issue is identified, requirements for the relevant feature would be added to the hlreq document. (The hlreq document can also describe the writing system more fully (ie. features not mentioned in the gap analysis), and that would be helpful, but the idea is that doing the gap analyis workk in parallel will provide a sense of movement and and practical applicability that wasn't so clear before.) The gap analysis results are summarised in a matrix at https://w3c.github.io/typography/gap-analysis/language-matrix.html You can see an example of a gap analysis document that i put together very quickly for Amharic & Tigriña at: https://w3c.github.io/elreq/gap-analysis/ I also developed one section in more in-depth for Japanese: see https://w3c.github.io/jlreq/gap-analysis/index.html#emphasis If it makes sense to you to go down this route, you can use a template i already added to the hlreq repo. You'll find it at: https://w3c.github.io/hlreq/gap-analysis/ Let's discuss further on Tuesday. cheers, ri
Received on Thursday, 8 February 2018 11:48:13 UTC