- From: Håkon Wium Lie <howcome@opera.com>
- Date: Thu, 24 Aug 2006 13:12:57 +0200
- To: "Anne van Kesteren" <annevk@opera.com>
- Cc: www-style@w3.org
Also sprach Anne van Kesteren:
> Perhaps
>
> h1 { font-family: Headline url(...), serif }
>
> would be better. Putting the name of the font and the font resource
> together instead of separating them by a comma.
That could work. In any case, the "Headline" font should be use if
it's pre-installed on the system.
Another issue appears here:
h1 { font-family: url(font.zip), Headline, serif }
The zip file will -- most likely -- contain four ttf files from the
same family in which case the font family is unambigously specified.
So, listing the family name as a string is strictly not necessary.
However, if the zip file contains two or more families, it's not
unambigous any more. This is problematic.
Here are some options:
a) always require a font family name
b) use the first font family name that appears in the archive
c) make all fonts in the archive available for selection, proceed to
the next list value ("Headline" in the above example) and follow
normal rules from that point on.
-h&kon
Håkon Wium Lie CTO °þe®ª
howcome@opera.com http://people.opera.com/howcome
Received on Thursday, 24 August 2006 11:13:18 UTC