[tex-live] Class moderncv and XeLateX: xdvipdfmx:fatal
Dr. Werner Fink
werner at suse.de
Tue Jul 31 11:03:30 CEST 2018
On Mon, Jul 30, 2018 at 11:27:05AM +0200, Dr. Werner Fink wrote:
> I've a bug report that the template.tex of the LaTeX class moderncv
> for typesetting modern curriculums vitae, cause an error
> xdvipdfmx:fatal: pdf_ref_obj(): passed invalid object.
> Output file removed.
> (see the transcript file for additional information)
> and testing this I see in template.log
> Here is how much of TeX's memory you used:
> 22724 strings out of 492979
> 423028 string characters out of 6141751
> 560602 words of memory out of 5000000
> 26518 multiletter control sequences out of 15000+600000
> 544859 words of font info for 61 fonts, out of 8000000 for 9000
> 1348 hyphenation exceptions out of 8191
> 57i,21n,65p,10361b,467s stack positions out of 5000i,500n,10000p,200000b,80000s
> Error 256 (driver return code) generating output;
> file template.pdf may not be valid.
> ... if the line
> is change to
> it works out. The only main difference seems to be
> diff -up moderncvstyleclassic.sty moderncvstylecasual.sty
> % symbols
> which leads to loading fronts from the sub package fontawesome but
> for the wrong engine? Or moderncviconsawesome.sty seems to use hard
> coded symbols which are not given for XeLaTex here. This because
> all symbols are found in fontawesomesymbols-generic.tex.
Seems that the Type1 font of fontawesome does mask the opentype version.
After telling fontconfig to ignore Type1 it works.
"Having a smoking section in a restaurant is like having
a peeing section in a swimming pool." -- Edward Burr
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 880 bytes
Desc: not available
More information about the tex-live