attachment
Hi,<br><br>Mike, Smith, and others interested in specs for best practice use<br>of Unicode in various scripts - an interesting note from W3C I18N<br>mailing list.<br><br>Cheers,<br>- Ira<br><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div style="display:inline"></div><div style="display:inline"></div><div style="display:inline"></div><div></div><div></div><div></div><div></div></div></div></div>
<br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Richard Ishida</b> <span dir="ltr"><<a href="mailto:ishida@w3.org">ishida@w3.org</a>></span><br>Date: Thu, May 14, 2015 at 11:39 AM<br>Subject: Supporting CSS for typographic information<br>To: www International <<a href="mailto:www-international@w3.org">www-international@w3.org</a>>, "fantasai (<a href="mailto:fantasai@inkedblade.net">fantasai@inkedblade.net</a>)" <<a href="mailto:fantasai@inkedblade.net">fantasai@inkedblade.net</a>>, Koji Ishii <<a href="mailto:kojiishi@gluesoft.co.jp">kojiishi@gluesoft.co.jp</a>>, Ivan Herman <<a href="mailto:ivan@w3.org">ivan@w3.org</a>>, Dave Cramer <<a href="mailto:dave.cramer@hbgusa.com">dave.cramer@hbgusa.com</a>><br><br><br>CSS WG (fantasai) asked whether the i18n WG could document information about justification and other typographic info related to non-Latin scripts so that CSS specs can point to it for the benefit of implementers, rather than try to boil the typographic ocean in the CSS spec.<br>
<br>
I chatted with her, and agreed that the CSS spec could point to <a href="https://www.w3.org/International/wiki/Typography" target="_blank">https://www.w3.org/International/wiki/Typography</a>, from which we point to information we know about, including:<br>
<br>
1. requirements generated by W3C groups<br>
2. spec references<br>
3. tests<br>
4. external pages<br>
<br>
(That page is already providing support for work on digital publications. Note, btw, that i shortened the URL for the page.)<br>
<br>
Furthermore, I believe it would be advantageous to convert information in external references to W3C documents for reasons including the following:<br>
<br>
1. we could ensure that the information is available on a long-term basis<br>
2. we can put the information out for review and adapt as needed<br>
<br>
We are already doing this for some scripts, with our layout requirements task forces, ie. Chinese, Japanese, Indic, Korean, and hopefully soon Mongolian and Tibetan.<br>
<br>
I recommend that any information we develop in-house be grouped into documents by script (eg. Tibetan, Korean, Ethiopic, etc) rather than by feature (eg. justification, emphasis, page layout, etc.). Partly this is useful because it fits with our current approach vis a vis layout requirements, and partly because features such as justification are often interconnected with other features, such as line-breaking, hyphenation, line-start indentation, etc, etc. and so it makes sense to describe all the features together.<br>
<br>
Bringing the information into W3C documents involves some extra work for the WG. Ideally the documentation would be created by experts working in task forces. We already have people working on Chinese, Korean, Indic, etc, and we should encourage participation from others. For example, we heard this week from someone who is interested in writing up information about Ethiopic. I also have some contacts who expressed interest in working on Arabic-script information.<br>
<br>
One major benefit of doing this work is that it directly affects the usability of the Web in cultures around the world, and supports in a practical way our 'Web for All' philosophy. Another is that it involves in the W3C people from countries and cultures around the world that have typically not been well engaged by us in the past, as well as effectively promoting awareness and relevance of the W3C around the world.<br>
<br>
Comments?<span class="HOEnZb"><font color="#888888"><br>
<br>
ri<br>
</font></span><br>
<br>
<br>
PS: if anyone reading this knows of authoritative and useful information about typographic requirements for a given script, please send me a link, so that i can consider adding to the wiki page above.<br>
<br>
<br>
</div><br>