RE: [css3-webfonts] Downloaded fonts should not...

The inclusion of EOT as a part of CSS was rejected at the November 2007 meetings in Boston. A new working group will be created to standardize the EOT file format.

Permanently installing on a remote system is:
1. A security issue. I could put a style sheet that would fill your device's hard drive so you could not put anything else on the device. Sorry for the end user.
2. A licensing issue. A font may or may not be allowed to be installed permanently. It all depends upon the EULA. The safest thing for UAs to do is to temporarily install the font for use with the page using a memory only install.

I will as for the CSS3 document to be edited.

Paul

-----Original Message-----
From: d.crossland@gmail.com [mailto:d.crossland@gmail.com] On Behalf Of Dave Crossland
Sent: Friday, April 11, 2008 8:48 AM
To: Paul Nelson (ATC)
Cc: www-style@w3.org
Subject: Re: [css3-webfonts] Downloaded fonts should not...

Hi Paul!

On 10/04/2008, Paul Nelson (ATC) <paulnel@winse.microsoft.com> wrote:
>
> >  "Downloaded fonts should not be made available to other applications."
> >  - http://www.w3.org/TR/2002/WD-css3-webfonts-20020802/

> >
> >  Could someone explain what this means in a technical way for a browser
> >  developer implementing css3-webfonts?
>
>  Please have a look at the Microsoft/Monotype EOT and submission to W3C at:
>  http://www.w3.org/Submission/2008/01/

>  http://www.w3.org/Submission/2008/SUBM-EOT-20080305/


I'm confused. Is this submission intended as a part of CSS3?

It contradicts CSS3 as it says "Fonts ... may be embedded and
permanently installed on the remote system by [User Agents]."

--
Regards,
Dave

Received on Friday, 11 April 2008 00:54:51 UTC