RE: .screenfonts

>There is no simple way to integrate the different design sizes of a  
typeface with the browsers' text scaling functionality.


I've done some work in this area and yes, Page Zoom has spawned some
substantial problems that have not as yet been addressed. However, I don't
see how they can be addressed within the kind of spec we are discussing
here: a web-specific font file format which, on the inside, will still be a
TTF or OTF file that works in the same way as one installed in the OS.
The problem you're describing CAN and SHOULD be addressed, however,
somewhere within the specs for CSS or the Event model. It's a problem that
sort of falls between the cracks because it involves user selected settings
in the browser's Page Zoom or Text Zoom features and there is, as yet, no
standard for that as there is for, say, the display of Alternate Style
Sheets within the browser chrome.
Personally, I've gotten a handle on it quite nicely in IE using a JavaScript
middle-ware layer connecting the Text Size and Zoom menus to IE's event
model, creating the equivalent of a window.textsize and window.zoom property
as well as window.ontextsizechange and window.onzoom events. ZoomPerfect is
the name of the product and I should have it finished up sometime around the
release of Windows 7. Along with a whitepaper detailing how I think the
specs should deal with Text Zoom versus Page Zoom going forward and why it's
necessary in order for browsers to become fully capable E-Readers. 
Cameron Moll recently wrote a post related to this you might want to check


Richard Fink

-----Original Message-----
From: [] On Behalf Of
Gustavo Ferreira
Sent: Friday, July 17, 2009 6:35 AM
To: Tal Leming; Erik van Blokland
Cc: www-font
Subject: .screenfonts

Hello Tal & Erik,

I have a question & some ideas to extend your current .webfont  
proposal to embrace size-specific, screen-optimized typeface designs.

#--- The question

Would it be possible to include support for size-specific designs in  
the .webfonts proposal?

#--- Context ( executive summary )

1. I have been working on screen typefaces with 'optical  
scaling' (different designs for different sizes).

2. Most (if not all) browsers have an integrated text scaling  
functionality [Ctrl+/Ctrl-].

3. There is no simple way to integrate the different design sizes of a  
typeface with the browsers' text scaling functionality.

4. I think the notion of size-specific designs is essential to (high- 
quality text screen-) typography and should be part of the technical  
typographic infra-structure of the web.

#--- Context ( long version )

I predict a near future in which the ability to use any font on web  
pages will bring us internet text typography of /inferior/ quality  
than what we have today; PostScript typefaces designed for print will  
not display as well in text sizes on the screen as Verdana & Co,  
specially on Windows.

There is currently no standard cross-plattform technology to control  
the display of fonts on screens. The only way to have some kind of  
control on the display of type on screens is by working directly on  
the pixel grid, either with bitmaps or outlines 'grid-fitted by design'.

This size-specific design approach demands the individual fonts to be  
used in the specific sizes they were designed for. This approach,  
which has been in the heart of type design practice for centuries, is  
not possible with current type technology architecture.

(I am aware that OpenType has a mechanism for dealing with optical  
sizes, but this is not yet widely supported and I haven't heard of any  
plans to do so in the near future.)

#--- My idea

I find it highly desirable to have some sort of standard mechanism to  
deal with different design sizes of a same typeface.

The different design sizes could be made available as individual font  
files (format is irrelevant), zipped into a "fontdata" resource.

"fontinfo.xml" would contain a flag to indicate that this typeface  
comes with size-specific fonts. It would also list a range of sizes  
(in pixels) and the corresponding font files to be used for each pixel  

Finally, browsers would recognize the flag from the font resource and  
match the [Ctrl+/Ctrl-] text scaling steps to the available fonts  
inside the font resource.

And that's it. Things would continue to work exactly the same way for  
scalable outline fonts, but we would have a cross-plattform way to  
address the representation of typefaces under different low-resolution  

#--- The End

Thanks for reading all this.

I'm curious about any comments you and others might have.

Best regards,

Received on Friday, 17 July 2009 14:11:11 UTC