Restrictive embeddable permission in OTF and TTF variants

[pvoborni]

Hello,

In both variants the embeddable permissions are set to "printable"(fstype=0004) instead of "installable"(fstype=0000). This causes a bug when the font is served to Internet Explorer 9+:
CSS3114: @font-face failed OpenType embedding permission check.
Permission must be Installable.

I assume this is caused by default settings of used font authoring tool. It can be also fixed by tool like https://github.com/hisdeedsaredust/ttembed during build process.

Note: IE9+ behavior is reproduced only when neither woff nor eot variants are served to IE. There are valid use cases for doing so. I'm mentioning it because it would be great to fix the issue and not close it with statement: 'there is a workaround' which is the default solution (serving everything).

Obviously this is a duplicate of #374 which was incorrectly closed by thinking it was a duplicate of #438

[WebReflection]

does this work on IE9 Mobile too ? ( I can test that for you if you have a page with the modified version )

[pvoborni]

I'm not sure.

Here's a test page: http://pvoborni.fedorapeople.org/fa-test/

[tagliala]

@vopet just to know... is there any reason to prefer ttf over woff/eot?

[pvoborni]

Packaging policy in Fedora + serving fonts to web apps without usage of external services like CDNs.

[tagliala]

temporarily added to 4.0.4

@vopet can you please check if bootstrap's default glyphicons has this permission?

[tagliala]

the ttf file is here: https://github.com/twbs/bootstrap/blob/master/fonts/glyphicons-halflings-regular.ttf

[pvoborni]

It has the same settings as FA:

$ ttembed -n glyphicons-halflings-regular.ttf 
fstype=0004 glyphicons-halflings-regular.ttf

[tagliala]

I think this should be done in docs/troubleshooting

What is the command line to change from 0004 to 0000 ?

[pvoborni]

$ ttembed ./*.?tf

Note: you might be forced to compile ttembed yourself.

[WebReflection]

I can confirm this will not fix IE9 Mobile problem with fonts.

About compiling, nothing more than clone the repo and gcc ttemed.c -o ttembed plus chmod +x teemed it does not need much and it compiles in seconds ;)

[thegregorator]

I ran into this same issue and wanted to include ttembed in my build process, but didn't want to deal with compiling it, so I wrote a node module for ttembed.

Just FYI in case it would be more convenient for this project.

[tagliala]

@thegregorator do you mind to edit the troubleshooting guide explaining this issue and needed steps to fix it?

TIA

[thegregorator]

Sure thing, I'll report back once I get a chance to make the edit.

[thegregorator]

@tagliala Edit made: https://github.com/FortAwesome/Font-Awesome/wiki/Troubleshooting#get-ttfotf-fonts-working-in-ie9

[lizzzzard]

This also effects embedding the font in Powerpoint.
Do I understand correctly that the fix requires me to compile the font file myself? You might want to fix the font offered for download on the hompage too... or is there a reason for the license setting?

[tagliala]

@lizzzzard there is no particular reason for this.

The actual settings are good to serve fontawesome as a webfont.

I need to ask Dave about this one, at the moment you should fix permissions by yourself.

I don't know if ttembed is the only way of doing that, maybe fontforge could help

[davegandy]

We’ll fix this right up for the next version. I’m always looking to make Font Awesome more open and easier to use. Thanks for bringing this up!

[lizzzzard]

@davegandy Thanks, nice to hear. I fixed it with ttembed here, even though it took a while until I had my windows machine ready to compile ttembed... the npm module didn't work since one of its dependencies was broken.

[davegandy]

These should now be addressed in the 4.1.0-wip branch. I've removed all restrictions on the font, and it should allow installable mode.

[lizzzzard]

The new font is installable now, but for me, embedding still doesn't work. What I did:

• have new fontawesome.otf installed
• have a word or powerpoint document with fontawesome text in it
• tell word or powerpoint to embed fonts: file/options/save/embed fonts
• uninstall fontawesome by deleting from c/windows/fonts folder
• reopen word or powerpoint file. icons are not visible, rectangles are shown instead. font setting is shown as fontawesome, though.
• tried rebooting, just in case. This is windows, we're talking about. Didn't help.

This did work with the ttembed fix.

[tagliala]

Reopening

@lizzzzard could you please check permissions before and after ttembed fix?

Please post there results

[davegandy]

Okay, I should have really gotten it this time. Please let me know if it's not working, and we'll re-open. Addressed in 4.4.1-wip branch.

[tbinggeli]

I'm still seeing this problem in IE11. I've got the latest and greatest font-awesome link. Can someone please help me out?

[tagliala]

Please check your group policy #8472

[tbinggeli]

I have checked my group policy. I've changed it, but no icons show up still.

[tagliala]

I'm going to reopen here because permissions on .ttf file are still 0004. I suppose font-squirrel is ignoring .otf's permission and replacing it with 0004

$ ./ttembed -n FontAwesome.otf 
$ ./ttembed -n fontawesome-webfont.ttf 
fstype=0004 fontawesome-webfont.ttf
$ ./ttembed fontawesome-webfont.ttf
$ ./ttembed -n fontawesome-webfont.ttf

[tagliala]

@tbinggeli please give a try to this branch

https://github.com/FortAwesome/Font-Awesome/tree/installable-permission-on-ttf

you should host it on your server

[davegandy]

Adding this to the release checklist until we can automate the fix. Going into 4.5.1.

[davegandy]

Can't get the node module to install for some reason. Anyone have a mac binary for ttembed?

[tagliala]

Anyone have a mac binary for ttembed?

I have it compiled by myself. please check your email

[davegandy]

Okay, I ran:

$ ttembed fontawesome-webfont.ttf

and it returned nothing, but changed the file. Can anyone validate that this worked as it should?

[davegandy]

(Best I can verify with Fontographer, it looks like the permissions on the ttf now match the otf. I'll re-open if necessary for a fix.)

[tagliala]

@davegandy I cannot check this because I'm not running into this issue. If ttembed returns nothing, it should be fine

[tagliala]

@tbinggeli please give a try to the 4.6.0-wip branch

[tbinggeli]

How do I point to the 4.6.0-wip branch? I'm pointing at
right now.

On Mon, Apr 11, 2016 at 11:49 AM, Geremia Taglialatela <
notifications@github.com> wrote:

@tbinggeli https://github.com/tbinggeli please give a try to the
4.6.0-wip branch

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#2517 (comment)

[tbinggeli]

Nevermind, I found it and copied it over. It did not resolve the issue.

CSS3111: @font-face encountered unknown error.
fontawesome-webfont.eot
CSS3111: @font-face encountered unknown error.
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
CSS3111: @font-face encountered unknown error.
fontawesome-webfont.woff
CSS3111: @font-face encountered unknown error.
DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff
CSS3111: @font-face encountered unknown error.
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
CSS3111: @font-face encountered unknown error.
fontawesome-webfont.ttf

On Tue, Apr 12, 2016 at 4:55 PM, Travis Binggeli tbinggeli@gmail.com
wrote:

How do I point to the 4.6.0-wip branch? I'm pointing at
right now.

On Mon, Apr 11, 2016 at 11:49 AM, Geremia Taglialatela <
notifications@github.com> wrote:

@tbinggeli https://github.com/tbinggeli please give a try to the
4.6.0-wip branch

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#2517 (comment)

[tagliala]

we went from "the permission must be embeddable" to

CSS3111: @font-face encountered unknown error.
fontawesome-webfont.ttf

Is there any chanche that a proxy is messing up with font files? could you please download the ttf on the machine experiencing the bug and check the md5 hash?

[Elfayer]

Or just convert your file to .woff : https://cloudconvert.com/