<div dir="ltr">2018-07-31 12:38 GMT+02:00 Ulrike Fischer <span dir="ltr"><<a href="mailto:news3@nililand.de" target="_blank">news3@nililand.de</a>></span>:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-"><br>
> Seems that the Type1 font of fontawesome does mask the opentype version.<br>
> After telling fontconfig to ignore Type1 it works.<br>
<br>
</span>See also<br>
<a href="https://tex.stackexchange.com/questions/334078/xdvipdfmx-pdf-ref-obj-error-with-fontawesome" rel="noreferrer" target="_blank">https://tex.stackexchange.com/<wbr>questions/334078/xdvipdfmx-<wbr>pdf-ref-obj-error-with-<wbr>fontawesome</a><br>
<br>
Imho the best would be if moderncv would call the font by font name<br>
but by file name. <br></blockquote><div><br></div><div>Loading a fot via a file name is IMHO good for nonstandard fonts that are distributed with the document and copied to the working directory. You never know what is the directory sturcture on someone else's computer and where the font file is located.<br> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
--  <br>
Ulrike Fischer <br>
<a href="http://www.troubleshooting-tex.de/" rel="noreferrer" target="_blank">http://www.troubleshooting-<wbr>tex.de/</a><br>
<br>
</blockquote></div><br><br clear="all"><div><div class="gmail_signature">Zdeněk Wagner<br><a href="http://ttsm.icpf.cas.cz/team/wagner.shtml" target="_blank">http://ttsm.icpf.cas.cz/team/wagner.shtml</a><br><a href="http://icebearsoft.euweb.cz" target="_blank">http://icebearsoft.euweb.cz</a></div></div>
<br></div></div>