[dvipdfmx] "mktexpk" is not disabled for fonts loaded by relative path
Akira Kakuto
kakuto at w32tex.org
Thu Oct 8 08:38:23 CEST 2020
On 2020/10/08 6:04, Karl Berry wrote:
> It doesn't surprise me. What did you see?
% test.tex (cmr10.tfm in the current dir)
\nopagenumbers
\font\x=./cmr10
\x x
\bye
[A]
(1)
pdftex:
Proceeds as usual by using cmr10.pfb in the system.
(2)
dvipdfmx:
Proceeds as usual by using cmr10.pfb in the system.
(3)
dvips:
dvips: Font ./cmr10 not found; characters will be left blank.
[B]
Delete cmr10.600pk if it exists.
Delete cmr10.pfb and delete a line in pdftex.map:
cmr10 CMR10 <cmr10.pfb
(1)
MKTEXPK=1 pdftex test
call mktexpk automatically
(2)
MKTEXPK=1 dvipdfmx test
call mktexpk automatically
(3)
MKTEXPK=1 dvips test
dvips: Font ./cmr10 not found; characters will be left blank.
If cmr10.600pk exists,
dvips: Font ./cmr10 not found; using cmr10
and uses cmr10.600pk in both cases of
MKTEXPK=0 dvips test
MKTEXPK=1 dvips test
dvipdfmx and pdftex seem to behave similarly.
Thanks,
Akira
More information about the dvipdfmx
mailing list.