You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 17, 2023. It is now read-only.
I started seeing "Failed to convert WOFF 2.0 font" errors a few builds ago in Chrome. I replaced the files with fresh font awesome 4.5 files and the errors are gone.
I think it relates to this issue: http://stackoverflow.com/a/33792610/5727571
Here's a quote:
"In my situation, Git was treating the file as a text file, and messing with its "line endings". This was corrupting the file.
I started seeing "Failed to convert WOFF 2.0 font" errors a few builds ago in Chrome. I replaced the files with fresh font awesome 4.5 files and the errors are gone.
I think it relates to this issue: http://stackoverflow.com/a/33792610/5727571
Here's a quote:
"In my situation, Git was treating the file as a text file, and messing with its "line endings". This was corrupting the file.
Adjusting the .gitconfig to recognize *.woff files as binary, then removing the file, and adding a new copy from https://github.com/FortAwesome/Font-Awesome/raw/v4.2.0/fonts/fontawesome-webfont.woff solved the issue for me."
The text was updated successfully, but these errors were encountered: