Re: [css3-text] clarifying text-transform:capitalize

On 03/01/2012 06:14 AM, Jonathan Kew wrote:
> I put a small test-case at, which applies the ‘capitalize’ transform to two lines of text:
> A.   (this) “is” [a] –short– -test- «for» *the* _css_ ¿capitalize? ¡transform!
>       ⓐⓑⓒ (ⓓⓔⓕ) —ⓖⓗⓘ— ⓙkl
> ...
> The second line of the test uses Unicode circled letters, which are not actually in the "Letter or Number general categories", and so ought to be untouched by ‘capitalize’ according to the current CSS3 Text definition. However, both Gecko and Webkit _do_ capitalize them just like normal letters - including the Gecko failure when preceded by a dash. So they're aiming for something like B2a, modulo the varying punctuation treatment.
> ...
> What I'd like to confirm - hence this message - is:
> (a) that we're happy with the CSS3 Text definition here, as far as it goes, in particular recognizing that it means certain word-initial punctuation characters will be treated differently by ‘first-letter’ and ‘capitalize’; and

I guess your question here is really
   - Should the letter after an underscore, hyphen, or em-dash be capitalized?

A key question is what happens to a hyphenated word, should "well-intended" become
"Well-Intended" or "Well-intended"?

Otherwise I'm leaning towards the IE9 behavior, too. :) Filed as

> (b) that the circled letters, being categorized as Symbols rather than Letters, should _not_ be affected by ‘capitalize’ (i.e. the expected result is B2b).

I think if we're case-shifting such symbols as all, we should case-shift them
and treat them as first-letters for capitalize. But you bring up a good point.
Maybe we shouldn't be case-shifting Symbols.

Filed as


Received on Saturday, 21 April 2012 02:56:56 UTC