- From: Chris Lilley <chris@w3.org>
- Date: Sun, 8 Aug 2004 00:03:17 +0200
- To: Etan Wexler <ewexler@stickdog.com>
- Cc: www-style@w3.org
On Saturday, August 7, 2004, 7:54:21 PM, Etan wrote: EW> Bert Bos wrote to <mailto:www-style@w3.org> on 6 August 2004 in "Re: EW> [css3-text] Capital spacing" EW> (<mid:16659.42505.884013.479149@lanalana.inria.fr>): >> I think you have to explain a bit more. If the text contains a word >> like "valley" and 'text-transform' turns it into "VALLEY", it seems to >> me quite obvious that the kerning between the V and the A should be >> whatever the font says it should be for V and A, not what it says for >> v and a. It would look rather ugly otherwise. EW> You have my agreement on your example. But my question is, should the EW> spacing between the "V" and "A" (and the other upper-cased letters) use EW> the default glyph-widths table or the all-caps-spacing glyph-widths EW> table? (Refer to the OpenType registration of the capital spacing EW> feature EW> <http://partners.adobe.com/asn/tech/type/opentype/appendices/ EW> features_ae.jsp#cpsp>.) The latter, as it is known to be all caps. This is a case where the correct answers fall out obviously as soon as the different layers of bytes, characters, and glyphs are separated out cleanly. text-transform alters the glyphs that particular characters produce. Fonts are collections of glyphs. -- Chris Lilley mailto:chris@w3.org Chair, W3C SVG Working Group Member, W3C Technical Architecture Group
Received on Saturday, 7 August 2004 22:03:17 UTC