add support for root strings

[GoogleCodeExporter]

I've been told that when licensed, some fonts include requirements that
root strings have to be set.

I should add support for root strings so that ttf2eot users can abide by
these terms.

(Note that root strings provide no security, and are trivially
removed/modified/etc)

Original issue reported on code.google.com by taviso on 3 Jun 2009 at 9:09

[GoogleCodeExporter]

Root string support is useful, but for some projects using opensource fonts, it 
is
also useful to be able to not have a root string.

Original comment by [email protected] on 17 Jul 2009 at 4:57

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

Without a root string, the eot file will not render in IE.  See Issue # 10

Original comment by [email protected] on 23 Jul 2009 at 4:56

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

At the risk of merely posting a "me too", I was wondering if any progress has 
been made on this? Would there be 
any benefit to having access to some commercial fonts that are failing to 
convert, for testing purposes? I have 
some fonts that aren't converting successfully (specifically, don't render in 
IE) and which I have semi-urgent 
need to be able to convert. (Yes, I could use FontSquirrel, or EOTFast, or 
whatnot, but I need to be able to do this 
on-demand, rather than via a manual process.) I think I can wrangle permission 
to send one or two of these 
fonts to someone who's working this bug.

Original comment by rbowen%[email protected] on 26 Feb 2010 at 3:28

• Added labels: ****
• Removed labels: ****