-
Notifications
You must be signed in to change notification settings - Fork 98
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
Xelatex issues with FontAwesome on macOS #32
Comments
Yes, that would be me. I have not yet had time to find a solution to it and had to ask @rougier to recompile his paper himself so that I could publish it. I guess it should work fine on Linux as well, but for some reason it just doesn't on my system. I would be more than happy if we could come up with a "global" solution to the problem. |
I think the font is only used for having the GitHub logo. Maybe we can use a regular pdf instead such that the font would not be necessary. |
Just for the record, I experienced similar problems in GNU/Linux Ubuntu which creates this error:
Then, by following the recommendations at 🔗,
after Then the makefile works well! |
Oh nice. Can you make a PR for the template ? |
Another alternative is by using the package of |
Thanks. We changed the template a few months ago and we do not use the awesome package anymore. |
Compiling the article with the template provided by ReScience can lead to a confusing issue for users of macOS using MacTex, as I just experienced. It is well described here by someone else that stumbled into this one month ago: https://tex.stackexchange.com/questions/369068/how-can-i-use-the-fontawesome-package-with-xelatex
I solved this by opening the otf file located in
/usr/local/texlive/2017/texmf-dist/fonts/opentype/public/fontawesome/FontAwesome.otf
with Font Book, and installing it as a regular font.We may want to include something about that in the
README.md
(possibly along with includingFontAwesome.otf
directly in the repo to make it easier) or solve the problem in some other way.The text was updated successfully, but these errors were encountered: