On Thu, 2012-03-08 at 19:25 +0100, newsgroups.mail2@stefanbaur.de wrote:
Am 08.03.2012 18:07, schrieb John A. Sullivan III:
<snip> I do not know much about ghostscript but do we know what this change does and what the real problem was? Was it the PDFSETTINGS=/printer or the DoNumCopies? What does the change really do?
A half hour of Internet research didn't turn up much: -dPDFSETTINGS=/screen (screen-view-only quality, 72 dpi images) -dPDFSETTINGS=/ebook (low quality, 150 dpi images) -dPDFSETTINGS=/printer (high quality, 300 dpi images) -dPDFSETTINGS=/prepress (high quality, color preserving, 300 dpi imgs) -dPDFSETTINGS=/default (almost identical to /screen)
I do not know what color preserving means. <snip>
It's been a while since I worked in printing support and had to deal with PostScript/PDF/ghostscript stuff, but I'd wager a guess that /prepress is for professional printing, and "color preserving" in that context probably means that ghostscript should not attempt to apply a color profile when processing the file, as professional printing equipment usually has its own methods of color calibration.
Does that sound like it makes sense? ;-)
<snip> Yes, that's what I was guessing more or less and why I was a little concerned about the patch despite my ignorance. I'm guessing the magic is removing DoNumCopies but that seems quite counter-intuitive. I'm wondering if there is a bug in gs for Windows or whatever is generating the file and making this change is accommodating a bug at who knows what expense.
If I recall correctly, we did have some problems printing from Windows TS and I believe it had to do with the file being processed through ps2pdf or some other utility twice. We solved it by making the X2Go printers in TS raw printers and that seemed to work (except in the odd case where the application directly queries the printer for its capabilities). Thanks - John