W3C home > Mailing lists > Public > public-i18n-cjk@w3.org > October to December 2013

Re: [css3-writing-modes] Summary of Tr in UTR#50 and 'text-orientation' discussions

From: John Daggett <jdaggett@mozilla.com>
Date: Sat, 5 Oct 2013 20:00:03 -0700 (PDT)
To: Rossen Atanassov <Rossen.Atanassov@microsoft.com>
Cc: Koji Ishii <kojiishi@gluesoft.co.jp>, www-style@w3.org, "CJK discussion (public-i18n-cjk@w3.org)" <public-i18n-cjk@w3.org>
Message-ID: <684963032.1781953.1381028403126.JavaMail.zimbra@mozilla.com>

Rossen Atanassov wrote:

>> James Clark said, for the same reason as John's #3 and Sylvain, CSS
>> should only allow UTR#50-compliant impl and disallow tailoring.
>> My preference is to allow both UTR#50 and the tailoring in John's
>> #2. CSS already allows a lot of tailoring, such as Turkish
>> uppercasing or UAX#14 grapheme cluster. As a secondary preference,
>> if tailoring is really bad and that subtle consistency is critical,
>> I'd agree with James.
> How about take it out of CSS all together? Unicode already defines it
> all so why can't we leave it at that and remove these properties from CSS?

By this you mean omit 'text-orientation' altogether?  That's not
possible because authors need an explicit way to override the default.
For example, 'IBM' would by default be displayed sideways but in some
situations authors might prefer to see it displayed upright.  The same
is true for digits in dates such as 9月7日, the digits need to be
upright in vertical runs.  Hence the need for manual override values
such as 'upright'.


John Daggett
Received on Sunday, 6 October 2013 03:00:35 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 15:59:19 UTC