W3C home > Mailing lists > Public > www-style@w3.org > January 2012

Re: [CSS21] 3 editorial modifications in § 15.5 Small-caps: the 'font-variant' property

From: Anton Prowse <prowse@moonhenge.net>
Date: Mon, 02 Jan 2012 12:55:12 +0100
Message-ID: <4F019B20.9070800@moonhenge.net>
To: www-style@gtalbot.org, Public W3C style mailing list <www-style@w3.org>
CC: Chris Lilley <chris@w3.org>
On 13/10/2011 16:45, "Gérard Talbot" wrote:
> Le Mer 12 octobre 2011 11:39, Chris Lilley a écrit :
>> On Tuesday, October 11, 2011, 2:42:46 AM, Gérard wrote:
>>
>> GT>  "
>> GT>  It is acceptable (but not required) in CSS 2.1 if the small-caps font
>> is a
>> GT>  created by taking a normal font and replacing the lower case letters
>> by
>> GT>  scaled uppercase characters.
>> GT>  "
>> GT>  section 15.5 Small-caps: the 'font-variant' property
>> GT>  http://www.w3.org/TR/CSS21/fonts.html#small-caps
>>
>> GT>  I propose to
>>
>> (two good changes, omitted)
>>
>> GT>  3- change "letters" to "characters": I don't see why the sentence
>> GT>  unexpectedly mentions letters and then characters.
>>
>> Both letters and characters are incorrect here. Firstly, one can't scale a
>> character but one can scale a glyph. Secondly, it could be misread as an
>> actual substitution of characters (which would show up in the DOM).

[...]

> Section 15.2
> http://www.w3.org/TR/CSS21/fonts.html#algorithm
> also needs a bit of tuning:
>
> "
> where all lowercase letters are replaced by upper case letters.
> "
>
> which, I think, should be replaced with
>
> "
> where all lowercase characters are replaced by uppercase characters.
> "
>
> There are some characters which are not considered letters but which can
> be uppercased.

Gérard, I've tracked this in 
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15383

Cheers,
Anton Prowse
http://dev.moonhenge.net
Received on Monday, 2 January 2012 11:58:19 GMT

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