[NTG-pdftex] [pdftex-Bugs][2092] Ligatures and special characters in included pdf disappear in typesetted document

pdftex-bugs at sarovar.org pdftex-bugs at sarovar.org
Thu Sep 18 14:06:50 CEST 2008

Bugs item #2092, was opened at 2008-09-18 10:36
Status: Open
Priority: 3
Submitted By: Jan Michael (jan)
Assigned to: Nobody (None)
Summary: Ligatures and special characters in included pdf disappear in typesetted document 
>Resolution: Accepted
Group: None
Category: PDF inclusion

Initial Comment:
Dear Readers,

as the subject already states, my documents created with pdflatex are loosing their ligatures and other special characters from included pdf documents which were typesetted by other applications (Word, Excel, Omnigraffle ...).

(a) Situation

This is how the behaviour can be reproduced and how it happens in my case:

(1) Import Latin Modern fonts as otf into system wide font location
(2) Create a document with Latin Modern Roman font and use ff, fi, fl ligatures
(3) Save Document as PDF (in OS X it's just "Save as PDF ...") - the pdf still shows the ligatures
(4) Include the created pdf into a *.tex document with \includegraphics
(5) Typeset the document with pdflatex
(6) Ligatures from included pdf document disappear while inline ligature are typeset as usual.

(b) Minimal Example

ligaturen.pdf can be downloaded from <https://dl.getdropbox.com/u/73200/ligaturen.pdf>

(c) Problem Analysis
This is what the the German tex usenet group de.comp.text.tex has already figured out:

- problem can be reproduced with MiKTeX 2.6 and TexLive 2008 (Windows)
- names of ligature glyphs in included pdf (f_i, f_l, f_f) differ from names used by pdftex (fi, fl, ff)
- font from included pdf is replaced by pdftex -> glyphs f_i, ... won't be found anymore
- behaviour can be suppressed by using \pdfmapfile{}
- behaviour can be suppressed by removing or renaming related fonts in pdftex.map
- behaviour can be suppressed by typesetting the pdf with xe(la)tex before including it in pdf(la)tex document. XeTeX redeclares the font in ligaturen.pdf from JTSEMF+LMRoman10-Regular to ASKXQL+LMRoman10-Regular-Identity-H.

The related thread, in German language, can be found here:

Right now I use the workaround with XeTeX to get my documents right. What do you think?




p.s. Please see pdf(la)tex version information below:
(from TexLive 2007 shipped with MacTeX 2007 package on MacBook
C2D running OS X 10.5.5)

$ pdflatex -v
pdfTeX 3.141592-1.40.3-2.2 (Web2C 7.5.6)
kpathsea version 3.5.6
Copyright 2007 Peter Breitenlohner (eTeX)/Han The Thanh (pdfTeX).
Kpathsea is copyright 2007 Karl Berry and Olaf Weber.
There is NO warranty.  Redistribution of this software is
covered by the terms of both the pdfTeX copyright and
the Lesser GNU General Public License.
For more information about these matters, see the file
named COPYING and the pdfTeX source.
Primary author of pdfTeX: Peter Breitenlohner (eTeX)/Han The Thanh (pdfTeX).
Kpathsea written by Karl Berry, Olaf Weber, and others.

Compiled with libpng 1.2.15; using libpng 1.2.15
Compiled with zlib 1.2.3; using zlib 1.2.3
Compiled with xpdf version 3.01


>Comment By: The Thanh Han (hanthethanh)
Date: 2008-09-18 12:06

yes this is an unfortunate situation: both the font from included pdf and the font on disk use the same name (LMRoman10-Regular), but they differ. Workarounds have been also mentioned; in short they fall into  2 methods:

- disable font subsetting globally, or
- change the font name in included pdf to something else, hence pdftex will not think this is the same font as the one on disk

none is perfect, and also it's not clear how pdftex should handle such cases. Needs more thinking...


You can respond by visiting: 

More information about the ntg-pdftex mailing list