<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><blockquote type="cite"><div>Well, IE did this in like 1996 so its not really true they decided to do something different; </div></blockquote><div><br></div><div>Yeah, I remember that this is an old thing. But now there <i>is</i> a standard.<div><br></div><div>But:</div><div></div><div><br></div><blockquote type="cite"><div>2009/7/1 ricardo lafuente <<a href="mailto:bollecs@sollec.org">bollecs@sollec.org</a>>:<br><blockquote type="cite">would it be too difficult/impractical to have this run on a font submitted<br></blockquote><blockquote type="cite">to the OFLB and generate the .eot on demand?<br></blockquote><br>That's the plan; actually, the ideal plan would be to have a mod_eot<br>Apache module so that when it saw IE coming, it did a cached<br>conversion on the fly so web designers don't have to think about it.</div></blockquote><div><br></div><div>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?</div><div><br></div><div>-J</div><div><br></div><div><div><div>On Jul 1, 2009, at 11:13 AM, Dave Crossland wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>2009/7/1 Joshua A.C. Newman <<a href="mailto:joshua@joshuanewmandesign.com">joshua@joshuanewmandesign.com</a>>:<br><blockquote type="cite">Oh, I'm not blaming Google or the engineer at all. I think it's cool someone<br></blockquote><blockquote type="cite">picked up the project. It's the fact that we have to do any of it that<br></blockquote><blockquote type="cite">chafes. There's a standard. Microsoft has decided instead to do something<br></blockquote><blockquote type="cite">that is more difficult,<br></blockquote><br>Well, IE did this in like 1996 so its not really true they decided to<br>do something different; back then Netscape had its own font DRM system<br>(from Bitstream, also a USA patent holder for web fonts...) and plain<br>TTF/OTF fonts were never considered.<br><br>Reading <a href="mailto:www-font@w3.org">www-font@w3.org</a> archives from ~15 years ago was very<br>interesting for me. ;-)<br></div></blockquote></div><br><div> <span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Gill Sans'; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div style="text-align: right; "><a href="http://joshuanewmandesign.com/"><font class="Apple-style-span" color="#FF5903">Joshua Newman Design</font></a></div><div style="text-align: right; ">401.225.7222</div></div></div></span> </div><br></div></div></body></html>