W3C home > Mailing lists > Public > www-style@w3.org > September 2010

Re: [css3 fonts] font-specific features

From: Erik van Blokland <erik@letterror.com>
Date: Sat, 18 Sep 2010 18:35:03 +0200
Message-Id: <04CC9A3D-2F12-463B-9880-A7636431E71F@letterror.com>
To: www-style <www-style@w3.org>, www-font <www-font@w3.org>
On Sep 18, 2010, at 2:01 AM, John Hudson wrote:

> Since web authors may be working directly with the WOFF file, rather than with an unpacked, desktop installed version of the font, is there a benefit to having a 'Manual' link in the standard WOFF metadata in addition to in the font data? I can imagine that a manual for use of the font on the web might differ from or be more CSS-specific than a general font manual related to use in a range of environments. So perhaps a case can be made, as with the license info metadata, for WOFF-related documentation that differs from other documentation.

Great idea to have this kind of documentation available to the webdesigner!

But to me it seems this class of information is best provided by the foundry / library / font source. The information itself has no place in the stream from site to reader. 

It is only relevant to the site builder / publisher / webdesigner. I'm sure they can find a clearly labeled pdf in the collateral that comes with the .woff. If they can't, there's not much point in putting it in the metadata either.

A link to a "manual" would surely be more compact. But I would have the same concerns. The manual is not really relevant to the woff consumer. 

For a machine readable representation of the features (say for a web design app that wants to offer a palette of options) there is no better data than the wrapped font itself.

Erik
Received on Saturday, 18 September 2010 19:36:06 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:31 GMT