Am Sonntag, den 10.05.2020, 14:30 +0200 schrieb David Kastrup: > For a while, I've been getting the warning > > **** WARNING: The .setpdfwrite operator has been deprecated and will be > removed entirely > in the next release of Ghostscript. The functionality of this > operator has > been reduced to increasing the size of the VM threshold. If you > believe you > have a real need for this then you should replace your call to > .setpdfwrite > with: > > 3000000 setvmthreshold > > on documentation builds. There are comparatively few places where > .setpdfwrite is in our sources, but it's not clear to me just when > .setpdfwrite became unnecessary(?). So I have no idea if just removing > it won't cause trouble with earlier versions of Ghostscript still in use > with LilyPond (not least of all because we may be using them in GUB). > > Any ideas?
Last time I looked at this, I seem to remember that the warning came from Documentation/pictures. I just crawled the GS repo for a bit and the last change in functionality for .setpdfwrite is from 2003: http://git.ghostscript.com/?p=ghostpdl.git;a=commit;h=d4ad1763efd31a1ed3e7f9be134e8c211097cc09 So _probably_ we can do the replacement, though it might make sense to see if we really need the larger VM threshold - and whether an even larger value provides some performance benefit. Jonas
signature.asc
Description: This is a digitally signed message part