Well, IE did this in like 1996 so its not really true they decided
to do something different;
Yeah, I remember that this is an old thing. But now there is a standard.
But:
2009/7/1 ricardo lafuente <boll...@sollec.org>:
would it be too difficult/impractical to have this run on a font
submitted
to the OFLB and generate the .eot on demand?
That's the plan; actually, the ideal plan would be to have a mod_eot
Apache module so that when it saw IE coming, it did a cached
conversion on the fly so web designers don't have to think about it.
That's the hot hotness. But doesn't that only work for linking to
those fonts? Would it work to generate EOTs for download as well?
-J
On Jul 1, 2009, at 11:13 AM, Dave Crossland wrote:
2009/7/1 Joshua A.C. Newman <jos...@joshuanewmandesign.com>:
Oh, I'm not blaming Google or the engineer at all. I think it's
cool someone
picked up the project. It's the fact that we have to do any of it
that
chafes. There's a standard. Microsoft has decided instead to do
something
that is more difficult,
Well, IE did this in like 1996 so its not really true they decided to
do something different; back then Netscape had its own font DRM system
(from Bitstream, also a USA patent holder for web fonts...) and plain
TTF/OTF fonts were never considered.
Reading www-f...@w3.org archives from ~15 years ago was very
interesting for me. ;-)
Joshua Newman Design
401.225.7222
