Re: Ghostscript/GhostPDL 9.28 Release Candidate 1

On 21/08/2019 11:08, Akira Kakuto wrote:
> Dear Chris,
> 
>> So, are you setting an environment variable, or a registry key, or a
>> commend line parameter, so Ghostscript can find it's initialisation
>> files?
> 
> Sorry for late report. I changed psi/nsisinst.nsi a little:
> 
> see WriteRegStr in an attached nsisinst.nsi.diff.

Bingo! It all makes sense now!

> PS:
> Added bad things:
> 
> I find that font files are also unreadable in -dSAFER:
> 
> gswin32 colorcir.ps
> fails with
> Can't find (or can't open) font file
> C:\usr\gs\gs9.28\Resource/Font/NimbusRoman-Regular
> ...
> 
> gswin32 -dSAFER -dOLDSAFER colorcir.ps
> is fine.

I worked on the assumption you were setting the path *somehow*, and in
debugging it, I noticed a problem with directory separators, which I fixed:

http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=ec0b35fed3de

I'm 90% sure that's the source of the problem you're seeing (especially
looking at the path for the font file above). This also explains why I
didn't see this in my testing, as I use Linux, where the OS and
Postcript directory separators are consistent with each other.

Fingers crossed, the new code will work for you with that change.

And thanks for taking the time test this stuff, and help track down the
problems.

Chris