W3C home > Mailing lists > Public > public-i18n-core@w3.org > April to June 2011

Re: [css3-text] New Working Draft

From: Mark Davis ☕ <mark@macchiato.com>
Date: Fri, 15 Apr 2011 18:00:17 -0700
Message-ID: <BANLkTi=dTA3h8QeAV0kB-Q0PP8w7tuFYdQ@mail.gmail.com>
To: fantasai <fantasai.lists@inkedblade.net>
Cc: WWW International <www-international@w3.org>, "public-i18n-core@w3.org" <public-i18n-core@w3.org>, indic <public-i18n-indic@w3.org>, CJK discussion <public-i18n-cjk@w3.org>, Unicode <unicode@unicode.org>
1. Many of the references to Unicode specifications are outdated, both links
and names. For example,

[UAX24]
Mark Davis. Script
Names.<http://www.unicode.org/unicode/reports/tr24/tr24-7.html> 28
March 2005. Unicode Standard Annex #24. URL:
http://www.unicode.org/unicode/reports/tr24/tr24-7.html

<http://www.unicode.org/unicode/reports/tr24/tr24-7.html>Should use at least
the current name *Unicode Script Property* and link:
http://www.unicode.org/reports/tr24/tr24-15.html. Or even better is to use
the unversioned link http://www.unicode.org/reports/tr24/.


2. There is a problem with any general categorization of scripts, because
the categorization tends to vary according to the purpose. You'd be far
better off, rather than having the categorization that you list, using
labels that are directly associated with the function that you intend.

For example, if the purpose is to define the scripts affected by
text-justify, for example, it would be better remove Section 1.1, and
retarget your  Appendix E: Categorization of Scripts by having something
like:

Appendix E: Scripts and Justification

The style values for text-justify affect the following scripts:

inter-ideograph
Bopomofo, Han, Hangul, Hiragana, Katakana, Yi...

inter-cluster
Khmer, Lao, Myanmar, Thai...



FYI, http://www.macchiato.com/unicode/utc/script-metadata

Mark

*— Il meglio è l’inimico del bene —*


On Wed, Apr 13, 2011 at 19:36, fantasai <fantasai.lists@inkedblade.net>wrote:

> Yesterday the W3C published an updated copy of the CSS Text Level 3
> specification as a Working Draft. This defines many typographic
> features that will soon make their way into a Web browser near you!
>  http://www.w3.org/TR/css3-text/
>
> This module covers, among other things,
>  * White space processing
>  * Line breaking
>  * Justification
>  * Text decoration
>
> The latest revision in particular attempts to classify the scripts
> in Unicode according to their typographic behavior. Unfortunately
> while I am familiar with more scripts than the average person, I am
> unfamiliar with most of them. Any suggestions for corrections and
> additions would be thus much appreciated.
>  http://www.w3.org/TR/css3-text/#script-categorization
>
> The module is derived from some early CSS Internationalization drafts,
> and one of its primary goals is to provide key features needed to
> correctly typeset languages from around the world. We welcome your
> comments and questions on the draft. Input from the Indic, Southeast
> Asian, and Arabic script communities so far has been noticeably missing
> and would be especially appreciated.
>
> The best way to send feedback is to post to the archived mailing list
> www-style@w3.org: http://lists.w3.org/Archives/Public/www-style/
> with '[css3-text]' and a summary of your comment in the subject line.
>
> For those of you who want to follow the latest-latest modifications,
> the unofficial editor's draft is here:
>  http://dev.w3.org/csswg/css3-text/
>
> Thanks~
>
> ~fantasai
> Invited Expert, W3C CSS Working Group
>
>
>
Received on Saturday, 16 April 2011 01:04:59 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 16 April 2011 01:05:00 GMT