On Tue, Jun 23, 2009 at 10:55 AM, Levantovsky, Vladimir < Vladimir.Levantovsky@monotypeimaging.com> wrote: > On Monday, June 22, 2009 5:49 PM Jonathan Kew wrote: > > Either way, the customer has to use a > > tool that readies the font for web-server deployment. Such a font- > > renaming tool would be easy to create, using any of several existing > > (free) font-processing toolkits -- allowing this technique to be > > widely deployed in a fraction of the time it will take to implement > > any other option that involves significant modifications to browser > > code. > > > > ... and still leaving the raw font data out in the open, without a > license, eating the bandwidth that a site owner is paying for, and > having to support EOT for IE in addition to raw data? A tool that changes the family name in the font file and a tool that converts TTF to EOT and back again are basically equivalent as far as a font user is concerned. It makes no sense to say that one of those activities is "automated" and the other is "manual", or that one leaves the "raw font data out in the open" and one does not. Rob -- "He was pierced for our transgressions, he was crushed for our iniquities; the punishment that brought us peace was upon him, and by his wounds we are healed. We all, like sheep, have gone astray, each of us has turned to his own way; and the LORD has laid on him the iniquity of us all." [Isaiah 53:5-6]
Received on Tuesday, 23 June 2009 00:04:22 UTC