Why #icomoon and ?#iefix stuff in the templates?

[eush77]

The URL for SVG version of a font in src property of @font-face is appended with #icomoon suffix, but what if I have my own SVG font, not affiliated with Icomoon?

src: {{#fonts.eot}}url("{{{fonts.eot}}}?#iefix") format("embedded-opentype"),
     {{/fonts.eot}}{{#fonts.woff}}url("{{{fonts.woff}}}") format("woff"),
     {{/fonts.woff}}{{#fonts.ttf}}url("{{{fonts.ttf}}}") format("truetype"),
     {{/fonts.ttf}}{{#fonts.svg}}url("{{{fonts.svg}}}#icomoon") format("svg"){{/fonts.svg}};

IMO the module should not depend on any vendor extensions. If the filename is foo.svg#icomoon, then it should be assigned to fonts.svg as it is. (And what a strange name btw.)

The same holds true for ?#iefix.

This module can certainly be more useful be it a bit more generic.

[twolfson]

icomoon is referring to the SVG layer. Since this module is part of the fontsmith family and icomoon is the only engine that is the current case. We could abstract it now but with having other engines to cover it would be premature and potentially give us a worse interface.

iefx is to deal with a bug in Internet Explorer 6 - 8 with fontface. Here is an explanation from the Stack Overflow

http://stackoverflow.com/questions/14207425/css-font-face-iefix

I will leave this issue open until we address icomoon in the templates.

[eush77]

Thank you for the explanation. The problem is probably more involved than I thought.