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

Re: [css3-font] unquoted font family names with whitespace

From: Glenn Adams <glenn@skynav.com>
Date: Wed, 14 Mar 2012 05:52:58 -0600
Message-ID: <CACQ=j+cL3-QGOsw1zP3J8anr3A9zfO3THcaKc-X9k+U_z5MdRg@mail.gmail.com>
To: Simon Pieters <simonp@opera.com>
Cc: "www-style@w3.org" <www-style@w3.org>
On Wed, Mar 14, 2012 at 12:52 AM, Simon Pieters <simonp@opera.com> wrote:

> "To avoid mistakes in escaping, it is recommended to quote font family
> names that contain white space, digits, or punctuation characters other
> than hyphens:"
>
> http://dev.w3.org/csswg/css3-**fonts/#propdef-font-family<http://dev.w3.org/csswg/css3-fonts/#propdef-font-family>
> http://www.w3.org/TR/CSS21/**fonts.html#font-family-prop<http://www.w3.org/TR/CSS21/fonts.html#font-family-prop>
>
> What mistake in escaping can one do when a font family name contains
> whitespace? Whitespace doesn't need escaping (unless a font has something
> funny like a tab character or two subsequent spaces, but such fonts don't
> exist). Unquoted font family names with spaces work fine. Don't recommend
> quoting them.
>
> Unescaped unquoted font family names that start with a digit or contain
> punctuation characters other than hyphen will break *even if there is no
> whitespace*.
>
> Suggested wording:
>
> To avoid mistakes in escaping, it is recommended to quote font family
> names that contain words that start with digits or contains punctuation
> characters other than hyphens:
>
> body { font-family: "Amalgamate O (outlined)", serif }
>
> <BODY STYLE="font-family: '21st Century', fantasy">


This recommendation has been in effect for a long time now. I see no reason
to change it.
Received on Wednesday, 14 March 2012 11:53:52 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 22 May 2012 03:48:51 GMT