EOT files broken, when merged from several fonts #73

Closed
puzrin opened this Issue Jul 28, 2012 · 8 comments

Comments

Projects
None yet
5 participants
Owner

puzrin commented Jul 28, 2012

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.

Possible workarounds:

  1. Try to use SVG source instead of TTF
  2. Repack TTF with ttx http://www.letterror.com/code/ttx/index.html prior to run EOT convertor.
  3. Try to merge SVG manually
  4. Split sources to SVG images, and assemble fonts from scratch.

upd

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.

shkuropat was assigned Jul 28, 2012

tj commented Jul 28, 2012

i think we're having similar issues, the last ~6 or so glyphs never seem to work

Owner

puzrin commented Jul 28, 2012

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.

tj commented Jul 28, 2012

sure I'll try and get something, I've done about 6 builds so far and it seems to happen to all of them

Owner

puzrin commented Jul 28, 2012

Маке 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.

@puzrin puzrin added a commit that referenced this issue Aug 16, 2012

@puzrin puzrin EOT fix for IE6-8. Related to #73 ea75025
Owner

puzrin commented Aug 16, 2012

@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.

puzrin closed this Aug 18, 2012

Proteo commented Aug 24, 2014

Hi guys. I just spent three hours trying to fix a very weird issue: I was able to see the font properly in every single (supported) browser but IE9. Even IE8 was working allright. Tried the solution posted by LouisStAmour and others found on the net to no avail.

It seems that the problem lies in the .eot generated file after all, so I figured out a way to solve it: I uploaded the ttf file generated by Fontello to the FontSquirrel font converter service, and generated a new .eot file from there. Then replaced the Fontello generated .eot with FontSquirrel's one and voilà! it worked like magic.

If some of you decide to take the FontSquirrel route, make sure you enable the expert settings checkbox, then feed the "Unicode Ranges" option with the unicode values from your glyphs.

Best regards.

Owner

puzrin commented Aug 24, 2014

I think, you did wrong generalization. Font is generated from svg, and there are no difference on source.

Try to make minimalistic example, that does not work (for example 2 glyphs from different fonts). I think, that can be sonething glyph-specific.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment