Fri 13 May 2011 09:19:14 AM UTC, original submission:
Since using gs 9 my exported post-script files have been 2-3 times larger than normal and my pdf files have been 20 times larger than normal.
If I disable the use of gs to "condition" the eps files written by qt_image_to_eps then the resulting .ps file seems to not be conformant:
1. gv can only display page 1
2. evince can only display some page in the middle.
3. basic old gs can display all pages (althought of course it requires me to press enter after each page).
I guess this is why gs was being used to condition these .eps images.
I note that when ps2ps invoked on the non-conformant output ps file, it reduces it from 158MB to 9MB and causes it to work just fine in evince and so on.
Also, ps2pdf when invoked on the non-conformant output ps file produces a 2.5MB pdf file that also seems to work just fine.
Primary conclusions
1. The .eps written by qt_image_to_eps is not satisfactory.
2. The .eps written by gs is not satisfactory.
3. The .eps written by the imagemagick "convert" utility is satisfactory.
Secondary conclusions
1. ps2ps might be invoked to some advantage on the output .ps in all cases.
2. qt_image_to_eps might do well to copy the format produced by imagemagick or that produced by gs version 8 when processing the imagemagick format.
3. gs 9 tools should not be used to output intermediate post-script files
Actions - patch provided, tested on Ubuntu 11.04 - requires imagemagick to be present
1. In image_to_eps
a. Disable qt_image_to_eps
b. Disable gs_to_eps
Future actions:
1. Fix qt_image_to_eps to produce conformant eps files directly instead of using gs to sanitize
2. Maybe the gs eps2write target instead of the epswrite target when it exists (the ps2write target doesn't work).
3. Consider invoking ps2ps on the generated ps to condition and trim the resultant .ps file. This can reduce a .ps file from 167MB to 10MB
|