I have the following document:

This is a test. 1 $1$.

I believe the fonts are installed correctly because this works perfectly with pdflatex and lualatex, but it fails when I use xelatex. On Windows with texlive 2013, I get the following:

This is XeTeX, Version 3.1415926-2.5-0.9999.3 (TeX Live 2013/W32TeX)
 restricted \write18 enabled.
entering extended mode
LaTeX2e <2011/06/27>
Babel <3.9g> and hyphenation patterns for 78 languages loaded.
Document Class: article 2007/10/19 v1.4h Standard LaTeX document class
(c:/texlive/2013/texmf-dist/tex/latex/mathdesign/mdpgd/t1mdpgd.fd))) (./tmp.aux
) (c:/texlive/2013/texmf-dist/tex/latex/mathdesign/mdacmr.fd)
(c:/texlive/2013/texmf-dist/tex/latex/mathdesign/mdpgd/mdbmdpgd.fd) [1]
(./tmp.aux) )kpathsea:make_tex: Invalid fontname `<AGaramondPro-Regular.otf', co
ntains '<'

** WARNING ** Could not locate a virtual/physical font for TFM "mdwgdr8t".
** WARNING ** >> This font is mapped to a physical font "<AGaramondPro-Regular.o
** WARNING ** >> Please check if kpathsea library can find this font: <AGaramond
** ERROR ** Cannot proceed without .vf or "physical" font for PDF output...

Output file removed.

Error 1 (driver return code) generating output;
file tmp.pdf may not be valid.
Transcript written on tmp.log.
  • Welcome to TeX SE. Please check if kpathsea library can find this font: <AGaramond Pro-Regular.otf. What does kpathsea say? Normally for text XeTeX will use system fonts but I think with your set up it is looking for TeX-installed fonts. Have you tried loading fontspec?
    – cfr
    Jun 4, 2014 at 0:24
  • @cfr: kpsewhich finds "AGaramondPro-Regular.otf", but it does not find "<AGaramondPro-Regular.otf", of course. I don't know why the "<" appears here.
    – ipswitch
    Jun 4, 2014 at 3:50
  • In mathdesign the fonts are not used through the normal "fontspec" way but tfm-files are loaded. The actual fonts are found with the help of map-file entries. In texlive xetex (xdvipdfmx) uses pdftex.map. This map use the syntax ` <<AGaramondPro-Regular.otf` (pdftex need it as it can load otf only fully) but obviously xdvipdfmx gets confused by the two <<. You could put corrected map entries in a mygaramond.map, save it in fonts/map and then add f mygaramond.map to your dvipdfmx.cfg. Jun 4, 2014 at 8:47
  • Thanks @UlrikeFischer! Some progress has been made, but I'm not quite there. I made mygaramond.map with lines like this: mdwgdr8t AGaramondPro-Regular " AutoEnc_csqf633h5kovjwhnfrdbqmo3bg ReEncodeFont " <[a_csqf63.enc <AGaramondPro-Regular.otf (changing the << to <), added f mygaramond.map to dvipdfmx.cfg, ran mktexlsr and updmap. Now I get a new error after it apparently runs mktexpk and then mktexmf AGaramondPro-Regular.mf. I get mktexmf: empty or non-existent rootfile! Cannot find AGaramondPro-Regular.mf. I try ps2pk-->gsftopk-->ttf2pk-->hbf2gf. Cannot find AGaramondPro-Regular.tfm.
    – ipswitch
    Jun 4, 2014 at 15:58
  • I don't have the actual otf so I couldn't run a complete test. Also I copied the map entries for mygaramond.map from the map of miktex. It uses the syntax mdwgdr7m a_rxz3ga AGaramondPro-Regular Jun 4, 2014 at 16:06


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.