W3C home > Mailing lists > Public > www-font@w3.org > July to September 2009

Re: .webfont Proposal

From: Erik van Blokland <erik@letterror.com>
Date: Thu, 9 Jul 2009 09:10:02 +0200
Cc: "Tab Atkins Jr." <jackalmage@gmail.com>, Tal Leming <tal@typesupply.com>, www-font <www-font@w3.org>
Message-Id: <90207544-2E07-48B4-BD5D-E5FD9FA6B6B1@letterror.com>
To: John Daggett <jdaggett@mozilla.com>

On Jul 8, 2009, at 11:57 PM, John Daggett wrote:

>> Note, though, that the proposal says that mismatches still allow the
>> font to be used, but suggest that UAs may offer an unobtrusive alert
>> about the mismatch.
>
> Ah, so this is root strings with "warn on load" rather than "refuse
> display on load".

Yes.

> No quite sure the user is the one who needs warning.

I can think of several scenarios in which such warnings are important  
to the user.

> The maintenance headaches and need for web infrastructure changes are
> still there.

Handling maintenance headaches is what foundries do. However  
complicated or easy, IMO these things are part of the relationship  
between the foundry and the font licensee. With all the relevant data  
in XML rather than the font binary, this can easily be automated. I  
think this can also be an issue where foundries can compete with each  
other on ease of use.

Which web infrastructure changes do you think are needed?

In reply to your earlier post, I agree the local file:// urls should  
not be part of the list. It implies one has access to the file anyway.  
I suggest in this case the browser should load the font and not ping  
the user.

Erik
Received on Thursday, 9 July 2009 07:10:44 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 11 June 2011 00:14:02 GMT