Re: bug? /Font resourceforall generates undefinedresource error

On 09/10/15 08:31, Ken Sharp wrote:
> At 22:41 08/10/2015 -0700, Perry Hutchison wrote:
>
>> BTW the cidfmap file shown below is exactly as packaged/installed:
>> the 4 lines that would map Munhwa fonts to themselves are commented
>> out in the package as distributed.
>
> I suggest you take this up with the packager, they have clearly modified
> the cidfmap file, and arguably done so incorrectly, since it has left
> Ghostscript referencing fonts which don't apparently exist.
>
> You might also suggest they upgrade to a more recent version at the same
> time.

As far as I can tell, Ken is absolutely correct.

The error you see is only triggered if there is mapping in your cidfmap 
that references an non-existent font file. Basically, the Ghostscript 
package for your distribution is (subtly) broken, and should either not 
include those mappings, or should have the relevant packages containing 
those font files are dependencies for the Ghostscript package.

Recent releases (IIRC, 9.16 onwards) validate the cidfmap records as 
they are read, and drop ones that attempt to map to non-existent files, 
so the error does not occur.

Nevertheless, that still leaves the Ghostscript package, I would 
suggest, badly configured, and it would be preferable to have it 
correctly configured in the first place.

Chris