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

RE: Web Fonts

From: Paul Nelson (ATC) <paulnel@winse.microsoft.com>
Date: Thu, 24 Aug 2006 04:49:57 -0700
Message-ID: <49C257E2C13F584790B2E302E021B6F90ECD19A2@winse-msg-01.segroup.winse.corp.microsoft.com>
To: Håkon Wium Lie <howcome@opera.com>, "Anne van Kesteren" <annevk@opera.com>
CC: <www-style@w3.org>

Each font in the .ZIP should be treated as it is named. All font data should be represented as it is named in the font. Otherwise we are making new fonts and likely to end up with all sorts of metrics issues etc.
 
Given the fact that a page author could put anything in a .ZIP, along with any number of fonts of different families, the UA should never assume what is/is not in the .ZIP.
 
My guess is that even if some browsers choose to push ahead with this type of mechanism, there will be some who view this as too large of a security and/or legal risk to pursue.
 
Paul

________________________________

From: www-style-request@w3.org on behalf of Håkon Wium Lie
Sent: Thu 8/24/2006 7:12 PM
To: Anne van Kesteren
Cc: www-style@w3.org
Subject: Re: Web Fonts




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 12:07:20 GMT

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