[cairo-bugs] [Bug 19487] New: Not all the relevant documents are followed when make a ToUnicode map for PDF

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Jan 9 13:53:42 PST 2009


           Summary: Not all the relevant documents are followed when make a
                    ToUnicode map for PDF
           Product: cairo
           Version: 1.8.6
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: pdf backend
        AssignedTo: ajohnson at redneon.com
        ReportedBy: chemoelectric at chemoelectric.org
         QAContact: cairo-bugs at cairographics.org

Cairo should follow the standard glyph-name rules from
http://www.adobe.com/devnet/opentype/archives/glyph.html when generating
ToUnicode maps. Otherwise PDF readers cannot handle alternate glyphs and
ligatures in OpenType fonts.

This is very important for PDF e-books, because otherwise "Find" or "Search"
doesn't work with ligatures, small caps, lining or oldstyle figures, etc.

(One might also, optionally, wish to map older glyph names similarly to their
newer equivalents, such as treating "Asmall" the same as "a.sc".)

Note that, although there are a few ligatures that do have their own code
points (ff, fi, fl, etc.) in newer OpenType fonts (I think including all from
Adobe) these often aren't used, and instead ligatures f_f, f_i, f_l, etc., are
treated like any other ligatures.

Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

More information about the cairo-bugs mailing list