W3C home > Mailing lists > Public > www-style@w3.org > August 2004

Re: [CSS21] Font-family syntax

From: Justin Wood <jw6057@bacon.qcc.mass.edu>
Date: Fri, 20 Aug 2004 03:09:36 -0400
Message-ID: <4125A3B0.1010200@bacon.qcc.mass.edu>
To: Etan Wexler <ewexler@stickdog.com>, W3C Style List <www-style@w3.org>

Etan Wexler wrote:

>
> Justin Wood wrote to <mailto:www-style@w3.org> on 17 August 2004 in 
> "Re: [CSS21] Font-family syntax" 
> (<mid:4121C2EE.1060608@bacon.qcc.mass.edu>):
>
>> Etan Wexler wrote:
>>
>>> There are many syntactic constructs which, though allowed by the 
>>> prose description of 'font-family', are forbidden by the Appendix G 
>>> grammar ...
>>
>>
>> Does not a quoted string solve all these issues?
>
>
> No.
>
> Using <string> lexical types makes things convenient for style-sheet 
> authors and for authoring tools. The issue remains outstanding for 
> implementors of CSS parsers and for the specification's editors. 
> Nothing about strings tells people whether the following is a valid 
> style sheet.
>
>     example { font-family: Trouble: A (Very) Troublesome Type Family & 
> Interesting Prospect. ; }
>
Though it can be said where that method is NOT to be written based on 
grammar/prose  it CAN be written legally syntacticly correct via quotes, 
which makes the issue moot, in my humble opinion.

example { font-family: "Trouble: A (Very) Troublesome Type Family & 
Interesting Prospect."; }

where your example would be skipped do to parsing errors.

~Justin Wood
Received on Friday, 20 August 2004 07:10:49 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:32 GMT