Bugs item #4291, was opened at 2009-06-26 22:37
Status: Closed Priority: 3 Submitted By: The Thanh Han (hanthethanh) Assigned to: Nobody (None) Summary: \pdfgentounicode conflicts with cmap+\pdffontattr Category: None Group: None Resolution: Fixed
Initial Comment: from https://www.tug.org/pipermail/tex-live/2007-October/014986.html
I think there are unsolved issues. Now there are two methods for adding CMaps: (a) \pdffontattr, package cmap (b) \pdfgentounicode, glyphtounicode.tex
Both methods have its limitations, e.g. (b) only works for Type 1 fonts. Thus you could need both methods to cover all fonts, but the methods doesn't know each other, thus fonts can end up with two CMap tables.
---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2010-07-28 12:40 Message: Fixed in 1.40.11 ---------------------------------------------------------------------- Comment By: The Thanh Han (hanthethanh) Date: 2010-04-16 12:25 Message: a workaround for this problem is available in pdftex stable (1.40.11-beta). A primitive was introduced to disable the tounicode entry generated by \pdfgentounicode if needed. Minimal test file: ,--------, \pdfcompresslevel=0 \input glyphtounicode \pdfgentounicode=1 \font\f=cmb10 \pdfnobuiltintounicode\f Hello, \f world! \bye `--------` ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=493&aid=4291&group_id=106