[dvipdfmx] "mktexpk" is not disabled for fonts loaded by relative path
Akira Kakuto
kakuto at w32tex.org
Tue Oct 20 02:11:45 CEST 2020
On 2020/10/20 8:26, Shunsaku Hirata wrote:
> For dvips convention, the part “only look for pk font”
> does not sound reasonable to me as dvipdfmx
> behavior.
I'll explain by experiments:
cmr10.tfm and cmr10.pfb in the current dirctory.
%
% test.tex
\nopagenumbers
\font\x=./cmr10\x x
\bye
If cmr10.600pk exists,
This is dvips(k) 2020.1 Copyright 2020 Radical Eye Software (www.radicaleye.com)
' TeX output 2020.10.20:0845' -> test.ps
dvips: Font ./cmr10 not found; using cmr10
and cmr10.600pk is used.
If cmr10.600pk does not exist,
This is dvips(k) 2020.1 Copyright 2020 Radical Eye Software (www.radicaleye.com)
' TeX output 2020.10.20:0845' -> test.ps
dvips: Font ./cmr10 not found; characters will be left blank.
and cmr10.pfb is not used even if it is in the current dirctory.
Even if I try
% test.map
./cmr10 CMR10 <./cmr10.pfb
dvips -u+test.map test.dvi
cmr10.pfb is not used.
Best,
Akira
More information about the dvipdfmx
mailing list.