[tex-k] [dvipdfmx] dvipdfm[x] problem with dashed horizontal lines

Bob Tennent rdtennent at gmail.com
Tue Jun 1 16:44:42 CEST 2021

 >|Actually it is possible to have an option to recover the
 >|old behavior (use TFM data for font dictionary's Width
 >|entry which might be different from that of embedded font
 >|file), however, by doing so it results in dvipdfmx to
 >|generate PDF files which are not compliant to the PDF

Takanori Uchiyama, the developer of the type1 musixtex-fonts
has emerged and has regenerated the fonts to correct all the
inconsistent glyph widths. They're currently being tested.

 >|> I've been told that it is "wrong" for dvipdfmx to use
 >|> tfm widths rather than pfb widths, and maybe that's
 >|> true if the pfbs are going to be used, but in my
 >|> opinion it is a *bug* to use pfbs that the user has
 >|> explicitly chosen not to use.
 >|> Please fix this.
 >|Dvipdfmx does not provide a way to explicitly specify
 >|which font format to use. But you may use a pk font
 >|by explicitly specifying the file name including the
 >|extension. For example,
 >|    \special{pdf:mapline musixspx none musixspx.600pk}

This approach would require some 79 specials! dvipdfmx
certainly uses the pk format if it can't find type1 files.
I wasn't asking for an option or a clumsy way to specify
the format. I was asking that dvipdfmx *automatically*
refrain from using type1 fonts that the user has explicitly

Bob T.

More information about the tex-k mailing list.