From: Philippe Verdy (verdy_p@wanadoo.fr)
Date: Sat Oct 23 2004 - 11:19:24 CST
From: "fantasai" <fantasai.lists@inkedblade.net>
> Comments on CSS (but not how-to questions) should be directed to
> the www-style mailing list at w3.org, not unicode:
> http://lists.w3.org/Archives/Public/www-style/
OK for the "numeric" versus "capitalize|uppercase|lowercase" remark, which
is related to form validation and has probably nothing to do within the
Unicode list. But the general discussion of the behavior of BiDi with
vertical scripts, or horizontal scripts rendered vertically (or even in
Boustrophedon) is still something that the Bidi algorithm in Unicode is not
solving completely. There are bidirectional properties that are inherent to
scripts and their characters, and that are in the direct focus of Unicode
standardization.
Although this was discussed in relation with CSS3, this is still a big issue
of Unicode because it's not a problem specific to CSS as it directly affects
any rendering of plain text.
The CSS3 article was very interesting to read because it really speaks about
problems that exist today with scripts already in Unicode, and for which the
BiDi properties do not seem enough to effectively write a generic renderer
for all of them (including the interation of Latin/Greek/Cyrillic with
Han/Hiragana/Katakana, or the special interaction of Hiragana/Katakana in
Han text.)
I bet that if the proposed CSS3 model works, it will demonstrate which
properties need to be added by Unicode in its standard, for use in other
non-CSS based applications. May be this will require now BiDi controls and a
more complex algorithm to handle them. For now, the only "safe" way to do
that is to base the augmented properties on the "script" property of
characters (but still with ambiguity problems for general purpose characters
like punctuation and spacing).
This archive was generated by hypermail 2.1.5 : Sat Oct 23 2004 - 11:26:57 CST