- From: Chris Lilley <Chris.Lilley@sophia.inria.fr>
- Date: Wed, 30 Jul 1997 14:53:12 +0200 (MET)
- To: "David Perrell" <davidp@earthlink.net>, "Chris Lilley" <Chris.Lilley@sophia.inria.fr>, "Style" <www-style@w3.org>
On Jul 29, 3:32pm, David Perrell wrote:
> Chris Lilley wrote:
> > Lets suppose I have an unusual font which has the family name of
> > 'bold Palatino'.
> How is the problem of missing quotes exacerbated by the relative
> position of the commas? Is
>
> H2 { bold Palatino, serif }
>
> any less ambiguous?
No, you are quite right. Assuming you meant
H2 { font: bold Palatino, serif }
> The size declaration is optional, so in the font
> shorthand/property, missing quotes is a firm no-no.
Correct. I think that also means that any unusual fonts called normal,
small-caps, bold, 700 etc should also be quoted even if they have no
spaces.
That should probably go on the erratta list for CSS1.
> This is a simple solution useful in simple situations, syntactically no
> less intuitive than the shorthand, yet functionally a superset. Or,
> more simply, all gain, no pain.
Some pain from the fact that the individual decalrations and the
shorthand are no longer equivalent, and some pain for those who
dynamically modify stylesheets using scripts.
--
Chris Lilley, W3C [ http://www.w3.org/ ]
Graphics and Fonts Guy The World Wide Web Consortium
http://www.w3.org/people/chris/ INRIA, Projet W3C
chris@w3.org 2004 Rt des Lucioles / BP 93
+33 (0)4 93 65 79 87 06902 Sophia Antipolis Cedex, France
Received on Wednesday, 30 July 1997 08:59:11 UTC