Skip to content
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

Closed
ooker777 opened this issue Dec 26, 2017 · 13 comments · Fixed by hlgirard/Awesome-CV#3
Closed

! fontspec error: "font-not-found" #181

ooker777 opened this issue Dec 26, 2017 · 13 comments · Fixed by hlgirard/Awesome-CV#3

Comments

@ooker777
Copy link

All the seemingly used fonts are not found, though I've installed them. One example error is:

! fontspec error: "font-not-found"
! 
! The font "Roboto-Thin" cannot be found.
! 
! See the fontspec documentation for further information.
! 
! For immediate help type H <return>.

I use Windows 10, MiKTeX.

@ivanbistrovic
Copy link

Just using \usepackage{fontspec} is not going to be enough in case you want to use custom fonts.
If you use the example Latex templates provided within this project you don't have to use fontspec.

@bkolada
Copy link

bkolada commented Jan 30, 2018

I had the same problem with font awesome and installing font in the system was enough.

@cbarrick
Copy link

cbarrick commented Feb 6, 2018

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.

@johannesbottcher
Copy link
Contributor

johannesbottcher commented Feb 6, 2018 via email

@niranjantdesai
Copy link

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 awesome-cv.cls.

@77QingLiu
Copy link

same issue

@77QingLiu
Copy link

@cbarrick , Still get the error after remove line 12 in my case.

@77QingLiu
Copy link

My issue has been removed by moving the fonts folder under the examples folder. I think this should solve your problem too.

@inmybrain
Copy link

I had the same problem, and this worked for me.

cbarrick added a commit to cbarrick/CV that referenced this issue Jan 30, 2019
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.
@cbarrick
Copy link

I've got an updated PR with the fix in #262, but I'm not sure @posquit0 is interested in reviewing new PRs...

@Berkmann18
Copy link

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.

That alongside commenting out l.14-16, helped getting the FA icons to show up.

\newcommand*{\faicon}[1]{{
\FA\csname faicon@#1\endcsname
}}

woneill pushed a commit to woneill/resume that referenced this issue Mar 8, 2020
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.
fox0430 added a commit to fox0430/Awesome-CV that referenced this issue Sep 6, 2020
@abuck2
Copy link

abuck2 commented Sep 29, 2020

@johannesbottcher Isn't it licensed under CC-BY-SA? I don't see the problem in modifying the file, or am I missing something?

@Daisy1111
Copy link

My issue has been removed by moving the fonts folder under the examples folder. I think this should solve your problem too.

This way works for me too!! Amazing!

@OJFord OJFord closed this as completed Feb 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet