[dvipdfmx] [tex-k] dvipdfm[x] problem with dashed horizontal lines
Bob Tennent
rdtennent at gmail.com
Tue Jun 1 04:02:52 CEST 2021
>|I'm trying to force dvipdfmx to use bitmapped musixtex
>|fonts (to avoid "Intolerable difference in glyph width"
>|issues). I've disabled musix.map and the musixtex fonts
>|do not appear in pdftex.map. Then dvipdfmx -v output
>|includes
>|
>| <musixspx at 19.93pt(TFM:musixspx)
>| pdf_font>> Simple font "musixspx" enc_id=<builtin,-1>
>| font_id=<musixspx,1>.
>|
>|yet the type1 versions are still appearing in the pdf.
>|How do I force dvipdfmx to ignore the type1 fonts and use
>|glyph widths from the tfm files (and presumably embed
>|type3 bitmapped fonts)?
I've figured out how to do this: uninstall the system-wide
musixtex-fonts package, install a personal musixtex-fonts
package and *remove the type1 fonts*. Then dvipdfmx is
forced to use glyph widths from the tfm and the problematic
horizontal dashed lines are gone.
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.
Bob T.
More information about the dvipdfmx
mailing list.