W3C home > Mailing lists > Public > www-style@w3.org > October 2008

RE: CSS3 @font-face / EOT Fonts

From: Alex Mogilevsky <alexmog@microsoft.com>
Date: Mon, 20 Oct 2008 04:35:06 -0700
To: "robert@ocallahan.org" <robert@ocallahan.org>
CC: "www-style@w3.org" <www-style@w3.org>, "bert@w3.org" <bert@w3.org>
Message-ID: <7C2F64B551D8664AAD94A28DAC37D020670924CBAD@NA-EXMSG-C103.redmond.corp.microsoft.com>
There is a way to programmatically load font resources from files, including the web. It does involve code though, and at that point I am not sure if it is possible to control where a resource is coming from and what is done with it. If there is interest in learning more about what how installing fonts from code works I’ll refer to somebody in Silverlight.

It seems the point of the argument is “Silverlight argument” is that Microsoft is against declarative linking to bare TTF files, while it has a product that implements exactly that. The answer is that Microsoft had a product that had functionality that we consider wrong. Microsoft has admitted it was a mistake and removed the feature.

It seems that the proper order of actions to make further progress here should be


a)      Define what is the right way to do (and not to do)

b)      Review existing implementations (if any) for compliance with the new standard/rules

c)       Change non-compliant implementations if necessary

It is possible that participants of this discussion find that they have implementations that don’t comply with standards being developed. IMO it must not be an obstacle to creating a solution that works and then following it.

Alex

From: rocallahan@gmail.com [mailto:rocallahan@gmail.com] On Behalf Of Robert O'Callahan
Sent: Monday, October 20, 2008 12:09 PM
To: Alex Mogilevsky
Cc: www-style@w3.org; bert@w3.org
Subject: Re: CSS3 @font-face / EOT Fonts

On Mon, Oct 20, 2008 at 10:33 PM, Alex Mogilevsky <alexmog@microsoft.com<mailto:alexmog@microsoft.com>> wrote:

Silverlight 2 is in fact different, it has removed support for loading bare TTF files from markup.

OK, but it can still load and use bare font files via the WebClient and FontSource APIs, if this documentation is accurate.
http://msdn.microsoft.com/en-us/library/cc189021%28VS.95%29.aspx (Search for references to fonts and FontSource)

Is there some degree of syntactic inconvenience that makes serving of bare TTF files acceptable?

Rob
--
"He was pierced for our transgressions, he was crushed for our iniquities; the punishment that brought us peace was upon him, and by his wounds we are healed. We all, like sheep, have gone astray, each of us has turned to his own way; and the LORD has laid on him the iniquity of us all." [Isaiah 53:5-6]
Received on Monday, 20 October 2008 11:35:57 GMT

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