|
|
Posted by Andy Dingley on 09/19/06 08:55
richard wrote:
> Never did it that way before. As fonts are seperated by commas, and many
> have two or more words for a name, it doesn't become a problem without the
> quotes.
You're still not getting the "standards" thing though.
Yes, unquoted font names work. It's still bad practice to not quote
them though, because the standard says they should be:
"Font names containing any such characters or whitespace should be
quoted:"
http://www.w3.org/TR/CSS21/fonts.html#font-family-prop
_If_ you quote them and it doesn't work, that's a browser problem. If
you don't quote them and it doesn't work, then that's your problem.
Take any sufficiently complex piece of work and you'll run into this
issue. Maybe not for font-family, maybe not today, but sooner or later
you get bitten by this stuff. It's the difference between IE and a web
browser. Start working around mis-use of the standards and before long
the whole thing is in pieces.
Incidentally, font family names for the generics nust _not_ be quoted,
and font family names for fonts with the same name as the generics must
be quoted. Quoting one of these names may stop it being recognised
correctly as a generic.
Navigation:
[Reply to this message]
|