Re: gs -dNOSAFER / windows

Am 01.06.2018 um 17:43 schrieb David Kastrup: Comments? Objections? Yes to not putting stuff like the file reading permissions on the command line. As ghostscript has problems with -dEPSCrop and .locksafe in eps files and ps files that include those eps files, I filed a bugreport.

Re: gs -dNOSAFER / windows

Knut Petersen writes: > Am 30.05.2018 um 13:34 schrieb Knut Petersen: >> Am 30.05.2018 um 11:49 schrieb David Kastrup: >>>     -dSAFER, that is broken on windows. >>> >>> >>> So the question is: has that apparent group read permission problem (?) >>> been fixed in the last 13 years? >>> >>> Unles

Re: gs -dNOSAFER / windows

Am 30.05.2018 um 13:34 schrieb Knut Petersen: Am 30.05.2018 um 11:49 schrieb David Kastrup:     -dSAFER, that is broken on windows. So the question is: has that apparent group read permission problem (?) been fixed in the last 13 years? Unless somebody has a clue, I lean towards just trying t

Re: gs -dNOSAFER / windows

Am 30.05.2018 um 11:49 schrieb David Kastrup: -dSAFER, that is broken on windows. So the question is: has that apparent group read permission problem (?) been fixed in the last 13 years? Unless somebody has a clue, I lean towards just trying this out and waiting for problem reports. At le

Re: gs -dNOSAFER / windows

Knut Petersen writes: > Hi everybody! > > Could someone please explain why we use ghostscript in  -dNOSAFER > mode if the windows platform is used? > >(define-public (postscript->pdf paper-width paper-height >     base-name tmp-name is-eps) >   (let* ((pdf-

gs -dNOSAFER / windows

Hi everybody! Could someone please explain why we use ghostscript in  -dNOSAFER mode if the windows platform is used? (define-public (postscript->pdf paper-width paper-height     base-name tmp-name is-eps)   (let* ((pdf-name (string-append base-name ".pdf")