Re: CSS3 @font-face / EOT Fonts - new compromise proposal

> To clarify, the kind of automatic translation I'm looking for is a
> rule like "if a file is requested with the (wlog) .eot extension, and
> that file doesn't exist, but there's a file with the same name but a
> .otf extension in the same directory, automatically convert the OTF
> file (likely caching it unless conversion is very cheap) and serve
> that".  Then we could just add an extra line to our CSS files for each
> font, to give the dummy EOT location to IE, and otherwise forget that
> there's any difference between the browsers at all.  And those who for
> whatever reason prefer EOT could do the reverse -- as long as the
> fonts' licenses permit that transformation.

Just one caveat here, you'll only be able to serve .ttf fonts via EOT to IE this way, it won't load .otf files in an EOT wrapper.

Received on Friday, 14 November 2008 01:45:19 UTC