[gs-bugs] [Bug 691316] { /ISOLatin2Encoding findencoding } fails

bugzilla-daemon at ghostscript.com bugzilla-daemon at ghostscript.com
Wed May 19 13:24:11 UTC 2010


--- Comment #12 from Hin-Tak Leung <hintak at ghostscript.com> 2010-05-19 13:24:10 UTC ---
(In reply to comment #11)
> Thanks for your help, I would rather put it into a site directory and not into
> a product directory so that it does not get lost.  Is there a place where
> Ghostscript looks for locally supplied resources?
> I mean, ~/.fonts/Resource/Encoding for testing and
> /usr/share/ghostscript/Resource/Encoding for a system-wide setting (I obtained
> these values with -dDEBUG).

The search path somewhat site/installation-specific - but you could find out
from the output of "gs -h" what is appropriate for your site. e.g. on fedora,
this is what is shown: 

Search path:
   . : /usr/share/ghostscript/8.71/Resource/Init :
   /usr/share/ghostscript/8.71/lib :
   /usr/share/ghostscript/8.71/Resource/Font :
   /usr/share/ghostscript/fonts : /usr/share/fonts/default/ghostscript :
   /usr/share/fonts/default/Type1 : /usr/share/fonts/default/amspsfnt/pfb :
   /usr/share/fonts/default/cmpsfont/pfb : /usr/share/fonts :
   /usr/share/ghostscript/conf.d : /etc/ghostscript : /etc/ghostscript/8.71

so any of them should work - e.g. putting the file in /etc/ghostscript would be
appropriate for a Fedora Linux system. For testing, the current directory (.)
would work, I think. You can find out what is appropriate for your installation
by running "gs -h".

Configure bugmail: http://bugs.ghostscript.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

More information about the gs-bugs mailing list