W3C home > Mailing lists > Public > www-style@w3.org > October 2011

RE: [css3-text] comments on text-transform

From: Koji Ishii <kojiishi@gluesoft.co.jp>
Date: Tue, 4 Oct 2011 13:11:50 -0400
To: Florian Rivoal <florianr@opera.com>, "www-style@w3.org" <www-style@w3.org>
Message-ID: <A592E245B36A8949BDB0A302B375FB4E0CF697772F@MAILR001.mail.lan>
Assuming you guys know that the use case for the value is Ruby; I don't think people who wants to use ruby on the web is "very few".

The next question is how many percent of ruby usage would use this feature. I don't have the data, but if we learn from publishing, most published materials apply this rule to Ruby today. So, I think "very few" is too strong. The basic idea of the feature is small Kana in Ruby are too hard to read. It's even harder to read small letters on screen than when printed.

Regarding the "full-size-kana" or general @-rules; I'm more than happy to agree with @-rules if there were several use cases just like CSS3 Lists @counter-style does. I actually like the idea very much, and I heard some people like it too. But as far as I know, "full-size-kana" is the only use case for now. As long as there's only one use case, I think developing @-rules is too much feature.

If we find more use cases in future, we could migrate "full-size-kana" to @-rules as CSS3 Lists did from CSS2.


Regards,
Koji

-----Original Message-----
From: www-style-request@w3.org [mailto:www-style-request@w3.org] On Behalf Of Florian Rivoal
Sent: Wednesday, September 21, 2011 10:56 PM
To: www-style@w3.org
Subject: Re: [css3-text] comments on text-transform

On Tue, 13 Sep 2011 10:25:01 +0900, John Daggett <jdaggett@mozilla.com>
wrote:

> 4. Drop 'full-size-kana' and remove Appendix F While this 
> transformation might be useful to some, without a strong general use 
> case I think we shouldn't have very special use case values like this.  
> If it's really important, define it as a simple mechanism that allows 
> arbitrary text transforms:
> Example:
> @text-transform vowelcaps {
>   from: "aeiou";
>   to:   "AEIOU";
> }
> h4.articleheader { text-transform: custom(vowelcaps); }

I support with this proposal. Opera made a similar suggestion at the Kyoto F2F, also with the intent of having it replace very specialized values such as full-size-kana.

The very few people who actually want full-size-kana can then trivially redefine it themselves.

@text-transform full-size-kana {
   from: "ゃゅょぁぃぅぇぉっャュョァィゥェォッ";
   to:   "やゆよあいうえおつヤユヨアイウエオツ";
}

This simple yet very generic approach would address two classes of uses
cases:

1) use cases too rare to unanimously convince the WG (ex: full-size-kana,
mkhedruli-to-asomtavruli...)

2) uses cases that are hard or impossible to solve in the general case, but may be solvable in special narrower cases. The WG can't spec out the general case, but individual authors may be able to, depending on their situation. (example: accent removal)

  - Florian

Received on Tuesday, 4 October 2011 17:11:30 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:45 GMT