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 UTC
This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:13 UTC