Comment 3 for bug 1438494

Apologies, Till, for the delayed reply - I *thought* replying on a bug also subscribed me to it, but clearly not! (I have subscribed now).

There is a bit of guess work here, as I don't fully understand the file locations.

We are mainly concerned with the cidfmap file. Now, there is a set of cidfmap files in "/etc/ghostscript/cidfmap.d/" and those (it appears) are used by the "/usr/sbin/update-gsfontmap" script (poor name, as it adds to the confusion that Fonts and CIDFonts are the same thing!), to update the *actual* cidfmap which is in "/var/lib/ghostscript/fonts/cidfmap". It is not at all clear to me how the "update-gsfontmap" script gets run - possibly only as a package post-install step?

The files in "/etc/ghostscript/cidfmap.d/" are as follows (file name + TTF font(s) referenced):

90gs-cjk-resource-cns1.conf - ukai.ttc, uming.ttc
90gs-cjk-resource-gb1.conf - ukai.ttc, uming.ttc
90gs-cjk-resource-japan1.conf - fonts-japanese-mincho.ttf, fonts-japanese-gothic.ttf
90gs-cjk-resource-japan2.conf - ttf-japanese-mincho.ttf, ttf-japanese-gothic.ttf
90gs-cjk-resource-korea1.conf - NanumMyeongjo.ttf, NanumBarunGothic.ttf, NanumBarunGothicBold.ttf, NanumGothic.ttf

NOTE: there is some inconsistency (possibly bitrot) there with "fonts-japanese-*.ttf" used in one file and "ttf-japanese-*.ttf" used in another - clearly the same font, but likely different "generations" of name.

My two alternate solutions are that the Ghostscript package should be augmented to include the fonts listed above (with the names and paths updated to reflect the current directory tree etc) as dependencies, thus they always get installed with Ghostscript.

*Or* to split off (I *think*) the files in "/etc/ghostscript/cidfmap.d/" into something like a "ghostscript-cjk-cidfonts" package, which has those fonts listed above as dependencies (again with names and paths revised for a modern system).