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.
<https://bugs.ghostscript.com/show_bug.cgi?id=699397>
I don't like using .locksafe as opposed to -DSAFER and -DDELAYSAFER (?)
command line options because Ghostscript has a history of fscking around
with any commands not in the PostScript standard. For example, the
current Ghostscript man page states:
When running with -dNOSAFER it is possible to perform a
"save" followed by ".setsafe", execute a file or procedure
in SAFER mode, and then use "restore" to return to NOSAFER
mode. In order to prevent the save object from being
restored by the foreign file or procedure, the ".runandhide"
operator should be used to hide the save object from the
restricted procedure.
I read this part of the documentation as "If you don't use 'save' prior
to .setsafe / .locksafe everything is fine" ....
and in spite of this documentation, Ghostscript has just removed the
.runandhide operator without notice, keeping this documentation.
Well, in gs master this part of the documentation has been updated.
Knut
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
