desktop-packages team mailing list archive

[Till Kamppeter <1438494@xxxxxxxxxxxxxxxxxx>]

Chris, thank you for the info.

I would be very grateful for further help. Which font mapping file do I
have to remove/move out into a separate package? Which font mappings (in
which files?) do I have to remove altogether? When packaging Ghostscript
in the many years up to now I did nearly no changes in included font
mappings or fonts as it usually worked, so I do not have much experience
in modifying font mappings.

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

Title:
  ghostscript fails to correctly substitute cidf fonts

Status in ghostscript package in Ubuntu:
  New

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/ghostscript/+bug/1438494/+subscriptions