[Poppler-bugs] [Bug 34522] mapping problem with ligatures and accents

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=34522

--- Comment #11 from Adrian Johnson <ajohnson at redneon.com> 2011-02-22 13:46:33 PST ---
(In reply to comment #9)
> I was imprecise: How does the PCF specification mandate glyph access in SFNT
> fonts?

You can read all about it in Section 9.6.6 of the PDF Reference [1].

Character encoding is the worst part of the PDF standard, probably because it
is something the started with only supporting Type 1 fonts in PDF 1.0 and has
been extended in each revision to support additional font types while
maintaining backwards compatibility.

In the frsa.pdf file it is using text strings with 8-bit characters.
[A-Za-z0-9] are all encoded with the standard ASCII values. The character used
for the fi ligature is encoded as character 174. The font dictionary for the
font used by most of the text (including the fi ligature) specifies a Type 1
font named "Optima". The font dictionary overrides the font encoding in the
font with a custom encoding. In PDF, Type 1 font encodings are keyed by glyph
name. The dictionary maps character 174 to glyph name "/AE". Since this font is
not embedded in the PDF this is all the information the PDF viewer has to work
with.

[1]
http://www.adobe.com/content/dam/Adobe/en/devnet/pdf/pdfs/adobe_supplement_iso32000.pdf

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