Re: My solution of webfonts problem

Dave Crossland wrote:
>  Right clicking the viewport of most UA have "save page as" actions
>  that allow you to install the page in the system, including all the
>  images, stylesheets, javascripts and so on.
>
>  If I do this with a page containing @font-face webfonts, I expect the
>  fonts for that page to be copied with them.
>
>  The "save image as" action of the most UAs allows me to save a copy
>  of an image on its own. Why not the same for a font?

I’m a bit curious what any of the above has to do with what Nikodem was 
saying. Still, I’ll address the points anyway.

Dave Crossland wrote:
>  Right clicking the viewport of most UA have "save page as" actions
>  that allow you to install the page in the system, including all the
>  images, stylesheets, javascripts and so on.
>
>  If I do this with a page containing @font-face webfonts, I expect the
>  fonts for that page to be copied with them.

I would expect this to happen as well if by “install the page in the 
system” you mean that the document and certain linked files should be 
saved to a user’s hard drive for later off‐site access; I would also 
expect that font files would be saved like any other file and not 
installed as an available font on the user’s OS.

Dave Crossland wrote:
>  The "save image as" action of the most UAs allows me to save a copy
>  of an image on its own. Why not the same for a font?

I could imagine a user being able to right‐click text that utilized a 
particular font and being offered a “Save font as…” option and I don’t 
see any reason to prevent it. However, I don’t think that such 
functionality is particularly necessary or has anything to do with CSS; 
I don’t see such convenient options for Flash video, ECMAScript 
documents, or CSS style sheets either (without extensions anyway) and 
all such features seem like they should be left up to UA vendors.

Received on Sunday, 20 April 2008 01:08:36 UTC