Since one of the last updates, unfortunately, every ModernCV based tex-file fails with the following errors:
kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+57/600 --dpi 657 FontAwesome--fontawesometwo
mktexpk: don't know how to create bitmap font for FontAwesome--fontawesometwo. mktexpk: perhaps FontAwesome--fontawesometwo is missing from the map file.
kpathsea: Appending font creation commands to missfont.log.
Welcome to the forums.
A couple of thoughts: FontAwesome will only work with XeTeX, not with LaTeX; have you installed the otf version of FontAwesome?
Hey, thanks!
The packages I’ve installed are:
I’ve got the same problem on all openSUSE boxes since the last update (worked fine before). The same is working on my gentoo machine.
There’s a “FontAwesome.otf” in both texlive-fontawesome-fonts and fontawesome-fonts. Is this what you meant?
There is a note:
The package offers access to the large number of web-related icons provided by the included font. The package requires the package, fontspec, running under XeTeX or LuaTeX.
on the fontawesome package.
Did you get these packages from openSUSE or elsewhere? If you got them from openSUSE, you should have had the relevant packages installed. But you then need to ensure that you call XeTeX or LuaTeX rather than TeX to compile the code.
All packages are installed from the openSUSE repository.
The note is:
The package requires the package, fontspec, **if** run with XeTeX or LuaTeX.
So doesn’t this only indicate, that you need “fontspec” if used with XeTex / LuaTex, but fontawesome overall should work just fine with other Latex compilers?
I didn’t know switching between XeTex / LuaTex / … was so simple (I am using TexStudio).
Using XeTex failed with:
xdvipdfmx:fatal: Cannot proceed without the font: /usr/share/fonts/truetype/fontawesome-webfont.woff Output file removed.
However, LuaTex did the job.
Thanks!
Glad you got it to work finally. No LaTeX only works with specific TeX fonts; XeTeX was developed in part to allow people to use non-TeX specific fonts. For example, I do some work for an organisation which has an in-house font policy - so I have to use XeTeX for all their documents.
seijikun, I am able to reproduce your problem when using xelatex. I suspect the problem is with the openSUSE distribution of Font Awesome, because the problem occurs only when the fonts are installed via the RPM package in the M17N repository. If you install Font Awesome manually using kfontinst, then there is no problem. (I can also confirm that lualatex works in either case, but I think that’s just because it’s more aggressive at finding fonts.)
I have raised an issue on the Novell Bugzilla; feel free to comment and/or vote there: https://bugzilla.novell.com/show_bug.cgi?id=994667