Re: Bug#351525: dvipdfmx: how to properly implement map files support for dvipdfmx
"A Lee" <alee@debian.org> wrote:
> If updmap-sys is used to for such fonts, it MUST NOT modify the map file of
> dvipdfm because dvipdfmx also read it.
Therefore it would make things much easier if upstream (i.e. the TeXlive
people and Thomas Esser) would decide to drop the unmaintained dvipdfm
completely and use dvipdfmx instead.
> As far as i know dvips and ps2pk
> does not support truetype font. If it is true, updmap-sys must not modify
> their map files, either.
I don't understand this - it of course does modify, or rather create,
map files for dvips and ps2pk. It just doesn't include information how
to create slanted versions etc., and it must not change this behavior.
I guess you simply can't use these fonts with dvips - or is there an
other trick?
> Furthermore, some fonts like Adobe's OTFs included
> in acroread are supported by only dvipdfmx. In this case, updmap-sys must
> not touch fontmap files for all the other programs.
>
> I think using updmap-sys for dvipdfmx is not a good idea.
I don't understand why you think that. The whole point of updmap is
that there should be one central place for font configuration
(updmap.cfg, in Debian a generated file), and one program that knows
about the syntax of the map files for all TeX-related programs, and
created the correct map file for each. AFAIK, it currently includes the
all fonts in all generated map files, but it already drops some
information about a particular font if it is not needed and/or
understood by the target program.
Why not simply extend this behavior to not include lines for fonts that
have this "how-to-generate-slanted" feature, or instead to keep only the
information for the base font?
Regards, Frank
--
Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX)
Reply to: