-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
! fontspec error: "font-not-found" #181
Comments
Just using \usepackage{fontspec} is not going to be enough in case you want to use custom fonts. |
I had the same problem with font awesome and installing font in the system was enough. |
Installing the font system wide is a hack. I think I've fixed it though. You just have to delete line 12 from
This works because the font family is defined properly in |
You cannot just change a copyrighted file.
Also, installing a font system wide is not a hack.
Am 06.02.2018 03:25 schrieb "Chris Barrick" <[email protected]>:
… Installing the font system wide is a hack. I think I've fixed it though.
You just have to delete line 12 from fontawesome.sty. I.e. delete this:
% Define shortcut to load the Font Awesome font.
\newfontfamily{\FA}{FontAwesome}
This works because the font family is defined *properly* in awesome-cv.cls
already.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#181 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AH4EjpX8RTFAuVWLkTX-HBkrrBy9pB3eks5tR7gCgaJpZM4RMf8T>
.
|
Check the font directory in the source files. If the style files are in the "examples" folder, fontdir should be ../fonts/ in the main .tex file as well as |
same issue |
@cbarrick , Still get the error after remove line 12 in my case. |
My issue has been removed by moving the |
I had the same problem, and this worked for me. |
The \FA font family is declared both in fontawesome.sty (without a path) and in awesome-cv.cls (with a path). This confuses xelatex and produces a font-not-found error if Font Awesome is not installed globally. It is fixed by only using the declaration with a path. This closes posquit0#181 and posquit0#221.
That alongside commenting out l.14-16, helped getting the FA icons to show up.
|
The \FA font family is declared both in fontawesome.sty (without a path) and in awesome-cv.cls (with a path). This confuses xelatex and produces a font-not-found error if Font Awesome is not installed globally. It is fixed by only using the declaration with a path. This closes posquit0#181 and posquit0#221.
@johannesbottcher Isn't it licensed under CC-BY-SA? I don't see the problem in modifying the file, or am I missing something? |
This way works for me too!! Amazing! |
All the seemingly used fonts are not found, though I've installed them. One example error is:
I use Windows 10, MiKTeX.
The text was updated successfully, but these errors were encountered: