W3C home > Mailing lists > Public > www-international@w3.org > January to March 2011

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

From: Xaxio Brandish <xaxiobrandish@gmail.com>
Date: Tue, 22 Feb 2011 08:54:10 -0800
Message-ID: <AANLkTi=QA0tMjUJwHoOTROs+OXnYoLyc_trOau6A2tWU@mail.gmail.com>
To: Christoph Päper <christoph.paeper@crissov.de>
Cc: W3C style mailing list <www-style@w3.org>, "'WWW International' (www-international@w3.org)" <www-international@w3.org>
Good morning,

For 5, perhaps "first character of every word" to cover non-English
graphemes as well?

--Xaxio
On Feb 22, 2011 2:08 AM, "Christoph Päper" <christoph.paeper@crissov.de>
wrote:
> Koji Ishii:
>
>> it looks like we're in the consensus for the following points:
>>
>> 1. The feature should rely on Unicode to define its scope
>> 2. The name of the value should stay unchanged
>> 3. The wording "language-specific rules *must* be used"[1] should be
weakened at least for this value as language-specific rules for this value
is more complicated than upper/lower. We'd like to allow UAs to implement
language-specific rules, but we might not be able to test and make them
interoperable.
>> 4. Use UAX#29 for word break
>> 5. Apply Titlecase_Mapping defined in Unicode[2] to the first letter of
every word
>
> ad 2. you could introduce a ‘titlecase’ value that should use
language-dependent rules, but may fallback to ‘capitalize’.
> ad 3. The current text is only about case pairs like ‹I›/‹i› that may vary
depending on language, it does not say anything about higher level rules,
i.e. grammatical ones.
>
> Btw.: I still think the new values ‘fullwidth’ and ‘large-kana’ need to be
revised.
>
>> A couple of concerns were left:
>>
>> A. I'd like to add:
>> 5.1. Except that numeric glyphs appear before the first letter of a word
>>
>> B. No existing implementations match to this spec.
>>
>> C. Unicode defines "first letter of a word is an uppercase letter and the
rest of the letters are lowercase". All current implementation leaves the
rest of the letters untouched. CSS 2.1 also defines "other characters are
unaffected"[1]. But I see doing this might result strange for "LJ" case.
>
> Lowercasing the rest is helpful for
>
> <abbr>AIDS</abbr>
>
> or, better yet,
>
> acronym {text-transform: capitalize;}
>
> but harmful for
>
> <h1>Scrooge McDuck richest duck ever</h1>
>
> as long as we don’t have and use
>
> <h1><name>Scrooge McDuck</name> richest duck ever</h1>
> name {text-transform: none;}
Received on Tuesday, 22 February 2011 17:14:39 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 22 February 2011 17:14:42 GMT