desktop-packages team mailing list archive

[cliddell <1438494@xxxxxxxxxxxxxxxxxx>]

Two things:

1) I *really* don't understand why Ghostscript configuration file are
being installed by poppler. It would be worth finding out how (and even
if) poppler actually uses them, because I rather feel poppler and
Ghostscript configurations *should* be separate. For example, if I get
time, I'll probably be tweaking the capabilities of cidfmap at some
point, which could, potentially, break poppler's use of these files.

2) the question of whether poppler will fall back to some other
substitute CIDFont is moot since, if poppler *does* use those
configuration files, it won't (normally) find the font files they
reference anyway. So even if poppler does use them, splitting them off
into a separate package and fixing the dependencies will work better for
poppler, too.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to poppler-data in Ubuntu.
https://bugs.launchpad.net/bugs/1438494

Title:
  ghostscript fails to correctly substitute cidf fonts

Status in poppler-data package in Ubuntu:
  Triaged

Bug description:
  I reported this bug first with ghostscript
  (http://bugs.ghostscript.com/show_bug.cgi?id=695874), but it is
  apparently a packaging issue.

  The general issue is that when there is a CIDF font in a .pdf that is
  not embedded in the document, ghostscript will stop processing the
  file at that font (see the file attached to the ghostscript bug).  The
  packaging issue is that CIDF fonts that are not on the system are in
  the default Ubuntu cidfmap file.

  System info is:

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:    Ubuntu 14.10
  Release:        14.10
  Codename:       utopic

  $ ghostscript --version
  9.14

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler-data/+bug/1438494/+subscriptions