- From: Chris Lilley <chris@w3.org>
- Date: Thu, 24 Aug 2006 12:24:21 +0200
- To: Ian Hickson <ian@hixie.ch>
- Cc: www-style@w3.org
On Thursday, August 24, 2006, 12:17:37 PM, Ian wrote: IH> On Thu, 24 Aug 2006, Chris Lilley wrote: >> >> You miss the point entirely. I am not talking of whether the syntax >> would cause a syntax error in CSS (nothing does as far as I can see). >> >> The point is that CSS1 has a nice model where the fonts available is not >> an opaque blob but has separate descriptors for things like the family, >> the style, the weight, and so on. its then possible to change one >> property and match to a different font. IH> *shrug*. That would be an acceptable loss, IMHO, if it was true. IH> But it isn't; Sure it is - it changes the meaning of font-family and discards all the other descriptors. IH> I believe the idea howcome suggested would allow for IH> multiple TTF files to be included in the .zip file, such that the other IH> font properties would select the right font from the zip file. Which can be done already, simply by using font-src. IH> (Also, you said it would be backwards incompatible. This has nothing to do IH> with backwards compatibility.) Again, sure it does. -- Chris Lilley mailto:chris@w3.org Interaction Domain Leader Co-Chair, W3C SVG Working Group W3C Graphics Activity Lead Co-Chair, W3C Hypertext CG
Received on Thursday, 24 August 2006 10:24:35 UTC