[tex-live] Bug in xdvipdfmx (was (x)dvipdfmx and fully embededfonts in pdftex.map

Ulrike Fischer news3 at nililand.de
Thu Jun 5 15:03:25 CEST 2014

Am Thu, 5 Jun 2014 21:23:09 +0900 schrieb Akira Kakuto:

> Related:
> psfonts.map contains lines such as
> md-grbb7m GFSBodoni-Bold " AutoEnc_2rwgawua6ejo6lcmev7rxg6fvb ReEncodeFont " <[a_2rwgaw.enc <<GFSBodoniBold.otf
> AFAIK dvips cannot download open type fonts.
> Thus the lines like above may not be intended
> to use by dvips.

No. The fonts will not work with dvips. But as long as one doesn't
try to use the fonts such map entries don't do much harm. (The same
is naturally true for the AGaramond entries: As long as xdvipdfmx
doesn't try to use them ...)

> There is LCDF type tools to help in such cases.

Yes, but it is naturally more work. Also it is not quite clear to me
if it is always allowed to convert the fonts to other font types.
And imho LCDF only works with postscript flavour open type and not
with true type. 

> IMHO latex+dvipdfmx supports native open type fonts
> in map files. 

Yes, when the map-entries are correct (no <<) then they work fine
with latex+dvipdfmx. But xdvipdfmx simply doesn't look for them. 
(That's a pity as you can reencode fonts in such map-entries). 

> Can other cases use open type fonts in map files directly?

pdflatex + lualatex can do it. (But at least pdflatex only if the
fonts are embedded completly with <<). 

Ulrike Fischer 

More information about the tex-live mailing list