search

omacranger / fontawesome-subset

Creates subsets of FontAwesome fonts for optimized use on the web.
GNU General Public License v3.0
66 stars 15 forks source link

woff files not working in IE11 #1

Closed PPP01 closed 4 years ago

PPP01 commented 4 years ago

We noticed that woff files don't work in IE11. ttf2woff expects an array as parameter. The buffer leads to a broken woff file. the same applies to eot (untested)

omacranger commented 4 years ago

@PPP01 Can you give me a sample of your config options that you're using for fontawesome-subset? I have it building and displaying correctly in IE11 with the current implementation.

PPP01 commented 4 years ago

Hi, i use your example:

npm install --save-dev fontawesome-subset index.js : --> const fontawesomeSubset = require('fontawesome-subset'); fontawesomeSubset(['check','square','caret-up'], '../htdocs/fonttest/css/fonts/'); --<

node index.js

In IE11 this gives an error: CSS3112: Fehler bei der WOFF-Integritätsprüfung in "@font-face". fa-solid-900.woff Sorry for the german error, its like: WOFF integrity check error in "@font-face".

I added 2 zips with my html test: first with normal generated fonts, 2nd with my changes.

fonttest.zip fonttest-working.zip

omacranger commented 4 years ago

Thanks for providing those samples. Along with Duotone support I've added some fixes for woff and eot file generation on the development branch. If you're able to grab a copy from there and let me know if it works for you that would be great!

omacranger commented 4 years ago

Reference issue: #1

This has been resolved and published on NPM as version 1.1.0. Thanks.