The update-gsfontmap is indeed run in a post-install script, in the one of the ghostscript package. It should get run on every change in the directories /etc/ghostscript/cidfmap.d/ and /etc/ghostscript/fontmap.d/ as other packages than ghostscript, for example font packages, could drop files here. Indeed the files in /etc/ghostscript/cidfmap.d/ come from the poppler-data package. I could not determine which package(s) hold the actal fonts though.
-- 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 -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
