[dvipdfmx] "mktexpk" is not disabled for fonts loaded by relative path

[Karl Berry]

    Where can I find a document mentioning the correct behavior?

There is no official specification for this feature (or hardly any
others) in kpathsea/tex-k/whatever. I just tried to implement what was
useful. I tried to document the things that users might care about, but
didn't try to write up "everything", and surely missed plenty of unusual
cases, like this one.

    I tested pdftex and observed different behavior than tex+dvips.

It doesn't surprise me. What did you see?

      \font\x=./cmr10 \x e \bye
    with only "cmr10.tfm" copied to the current directory, dvips
    fails to map "./cmr10" to cmr10.pfb, not invoking mktexpk,
    and finally falls back to a pk font version of cmr10.

Seems ok to me.

    I expected only the font name "cmr10" is used as a key for
    looking up fontmaps and it is mapped to cmr10.pfb according
    to the default fontmap file.

The idea is that the user presumably used "./cmr10" ("find it in the
current directory only") for a reason. Therefore it does not seem right
to look it up in the system fontmap file. --best, karl.