Philip Rinn <ri...@inventati.org> writes: > Hi David, hi Russell, > > I think it is a problem of the input file - this might be linked to the > Ghostscript version used - see: > > > philip@debian:~$ epstool --test-eps input.eps > "gs" -dNOEPS -dNOPAUSE -dBATCH -dNODISPLAY "/tmp/gsview8BugKU" > GPL Ghostscript 9.26 (2018-11-20) > Copyright (C) 2018 Artifex Software, Inc. All rights reserved. > This software comes with NO WARRANTY: see the file PUBLIC for details. > EPSWARN FAIL: EPS file must not use /statusdict > EPSWARN WARNING: EPS file should be careful using /setmatrix > EPSWARN WARNING: EPS file should be careful using /setmatrix > > EPSWARN FAIL > > "gs" -dNOPAUSE -dBATCH -sDEVICE=bbox -c "<</PageSize [9400 9400] > /PageOffset > [3000 3000]>> setpagedevice" -f "/tmp/gsviewo4EEll" > GPL Ghostscript 9.26 (2018-11-20) > Copyright (C) 2018 Artifex Software, Inc. All rights reserved. > This software comes with NO WARRANTY: see the file PUBLIC for details. > %%BoundingBox: 589 3541 3172 3721 > %%HiResBoundingBox: 589.805982 3541.013892 3171.982263 3720.131886
The EPS is produced by dvips -E. At a guess this hasn't changed recently (although I did not verify). So if I understand correctly Ghostscript got fussier and stopped accepting the output from dvips -E? d
