You can clone with
No one assigned
In some cases, fontello generates broken EOT files. That can be checked in IE8 (IE9 fallback to TTF). Original fonts are ok. So, problem is in merger/fontforge.
Tons of thanks to @LouisStAmour for solution: #73 (comment) .
IE has a bug importing EOT files where it requires that FamilyName begins FullName. Here, FamilyName is set to "fontello" while FullName is set to "whatever_you_call_it" when IE expects "fontello whatever_you_call_it" as the full name.
i think we're having similar issues, the last ~6 or so glyphs never seem to work
That seems to be another issue, not EOT-related. Please, provide config file & description, wich glyphs are broken. Reproduceable samle will greately help to fix bug.
sure I'll try and get something, I've done about 6 builds so far and it seems to happen to all of them
Маке shure, that your issue is not encoding-related #70 (problem with codes > 0x1XXXX)
I was only able to get my font to work in IE8 by explicitly setting the name (at fontello.com) to "fontello" because IE has a bug importing EOT files where it requires that FamilyName begins FullName. Here, FamilyName is set to "fontello" while FullName is set to "whatever_you_call_it" when IE expects "fontello whatever_you_call_it" as the full name. (The family name has to be included.)
I've had great success then, when "fontello" is both the full name and family name in the exported .eot file, regardless of what you call it in your CSS. The eot file doesn't work in IE9 either, but it falls back to woff instead.
I never had to adjust the code range to get it working in IE. In fact, it even fixed a bug I was seeing in IE related to unicode character ranges.
EOT fix for IE6-8. Related to #73
@LouisStAmour Awesome! Rolled quick-fix, please, try now.
I still see some minor issues in IE7 with Unicode 6.1 chars on fontello site. But your advice helped to fix EOT problem in general.