- From: Levantovsky, Vladimir <Vladimir.Levantovsky@MonotypeImaging.com>
- Date: Tue, 23 Jun 2009 16:07:38 -0400
- To: "Aryeh Gregor" <Simetrical+w3c@gmail.com>, "Sylvain Galineau" <sylvaing@microsoft.com>
- Cc: "CSS 3 W3C Group" <www-style@w3.org>
On Tuesday, June 23, 2009 2:19 PM Aryeh Gregor wrote: > > Services like Typekit attempt to make OTF/TTF "safe" enough for > foundries to accept without browser-side changes, by means of > client-side scripting and possibly other things (sneaky hacks in the > font files? clever server-side scripts?). Likewise, techniques such > as John Daggett outlined could provide most of the "safety" that font > foundries want in the near future without explicit browser support. > Do you feel confident that these efforts will fail, or that they'd be > significantly technically inferior to what a new font format could do? I don't think there is a universal @font-face/raw font support at this time. So, I am sorry, I simply do not understand why we are trying so hard to make site owners/authors go to the great length by means of client-side scripting and sneaky hacks (that are tricky and may not work) to support raw fonts when there is simple solution that requires minimal efforts on both browser side and from web authors - compress a font before you put it on a server and decompress it in a browser before you pass it on to OS for rendering.
Received on Tuesday, 23 June 2009 20:08:50 UTC