- From: Adam Twardoch (List) <list.adam@twardoch.com>
- Date: Wed, 03 Mar 2010 05:03:09 +0100
- To: Andrew Cunningham <lang.support@gmail.com>
- CC: Chris Fynn <cfynn@gmx.net>, www-font@w3.org
Andrew Cunningham wrote: > On 3 March 2010 14:44, Adam Twardoch (List) <list.adam@twardoch.com> wrote: > >> none of these tools performs subsetting. They offer (rightly) just one >> core functionality: converting a .ttf to .eot (which means, "wrapping" a >> .ttf into an .eot "envelope"). >> > > although some of the web based tools do modify the .ttf before > generating the web fonts, thus breaking complex script rendering. I was referring to the three tools mentioned in the subject line (eotfast, ttf2eot, mkeot). AFAIK, they just offer the core functionality of converting the container format. Web-based conversion services often perform a number of different operations in a row. Similarly, when you upload a movie to YouTube, the service performs several different operations such as container conversion, demuxing, transcoding, muxing, and, again, container conversion). While those operations may appear as "one step" to the end-user, they're usually a chain of steps done consecutively. Especially in the opensource software world, often separate specialized tools or libraries exist for each of those steps, and they are being linked into chains of operations using scripts or GUI applications. BTW, the situation you mention clearly indicates that some things are better left to skilled professionals. :) A. -- Adam Twardoch | Language Typography Unicode Fonts OpenType | twardoch.com | silesian.com | fontlab.net Reporter: "So what will your trip to Ireland look like?" Lech Wałęsa: "I get into a car, then onto a plane, and then the other way around."
Received on Wednesday, 3 March 2010 04:03:46 UTC