Richard Fink writes: support for the "open" standard actually leads to higher costs for all concerned [..] the OTF must be pre-processed and obfuscated [and this] inflicts considerable inconvenience and additional cost. As much or more than using WEFT to create an EOT file [..] Fat or lite. Using WEFT, authors had to scan their HTML pages to create EOT files. This was highly inconvenient and proably the major reason why nobody used it. You're saying that the solutions in development will be even more inconvenient? -h&kon Håkon Wium Lie CTO °þe®ª howcome@opera.com http://people.opera.com/howcomeReceived on Saturday, 18 July 2009 09:06:11 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 11 June 2011 00:14:02 GMT