Bug 83401 - Blank space where every 'fi' ligature should be
Summary: Blank space where every 'fi' ligature should be
Status: RESOLVED MOVED
Alias: None
Product: poppler
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: poppler-bugs
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-02 14:24 UTC by Zack Weinberg
Modified: 2018-08-21 10:52 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
test case (5.68 KB, application/pdf)
2014-09-02 14:24 UTC, Zack Weinberg
Details

Description Zack Weinberg 2014-09-02 14:24:40 UTC
Created attachment 105613 [details]
test case

The attached PDF is a single page extracted from the 1999 C standard.  Evince 3.12.2 renders it correctly *except* that every single 'fi' ligature has turned into a blank space.  Since the document makes heavy use of terms like 'identifier', 'specifier', 'qualifier', 'definition', and so on, this bug is, although minor, exceedingly irritating. ;-)  IIRC this also affects 'fl', 'ffi', and other common ligatures, but 'fi' is the only one on this page.  Copy and paste is not affected.

Older versions of Evince/Poppler rendered this document correctly; I do not know exactly when it broke.  Ghostscript 9.06 does render it correctly.  It is probably relevant that *none* of the fonts used are embedded (they are all from the mandatory 17).
Comment 1 Thomas Freitag 2016-03-16 14:14:35 UTC
Seems to be fixed again in actual version
Comment 2 GitLab Migration User 2018-08-21 10:52:14 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/poppler/poppler/issues/400.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.