[tex-live] TL2017's dvipdfmx prints warnings

jack tljack at forallx.net
Sat Jan 20 17:08:49 CET 2018


On Sat, January 20, 2018 9:16 am, Bob Tennent wrote:
>> |Ever since TeXLive 2017 came out, dvipdfmx is throwing weird warning
>> |messages when I use garamond as the font, when the exact same document
>> |involves no such warnings in prior years of TeXLive.
>> |
>> |Consider the following tiny sample, which we can call "demo.tex"
>> |
>> |\documentclass{article}
>> |\usepackage[mdugm]{mathdesign}
>> |\begin{document}
>> |[foo]
>> |\end{document}
>> |
>> |If I run `latex demo.tex`, followed by `dvipdfmx demo`, I do get a pdf
>> |created but the following messages get shown:
>> |
>> |  atemplate-2 -> atemplate-2.pdf
>> |  [1]
>> |  xdvipdfmx:warning: Glyph width mismatch for TFM and font (md-gmr8t)
>> |  xdvipdfmx:warning: TFM: 375.402 vs. Type1 font: 374
>> |  xdvipdfmx:warning: Glyph width mismatch for TFM and font (md-gmr8t)
>> |  xdvipdfmx:warning: TFM: 375.402 vs. Type1 font: 374
>> |
>> |These never appeared prior to TeXLive 2017, even with the exact same
>> |sample document and even though I have the garamond fonts installed in
>> the |same location.  (Namely, I have a symlink in
>> |$TL2017/texmf-local/fonts/type1 called "urw" that points to a folder in
>> my |$HOME.  This has worked flawlessly for years.) I have this problem
>> on |multiple machines.
>> |
>> |I'm not a TeX expert, but I don't see why there would suddenly be a
>> |mismatch between metrics and what the font says.  Those garamond fonts
>> |have not changed in years as far as I know.  I got them from the
>> |"garamond" package on CTAN, which hasn't changed in years.  I seem to
>> |recall the directions in there told me that all I need are: ugmm8a.pfb,
>>  |ugmmi8a.pfb, ugmr8a.pfb, and ugmri8a.pfb.  That is indeed what is in
>> the |dir that my symlink points to.
>>
>
> Your MWE uses
>
>
> \usepackage[mdugm]{mathdesign}
>
>
> which provides its own versions of the garamond fonts. So it looks to me
> like there's an issue with the mathdesign package.

According to its manual (and also the top of mathdesign.sty), the
mathdesign package hasn't changed since 2013.  And yet these warnings
didn't appear until TL2017.  So there is something about TL2017 in
particular that is either causing a bug or revealing a latent one.

-Jack


More information about the tex-live mailing list