The customer reports that if the two attached PostScript files are printed using this command line: gsprint.exe -ghostscript gswin32c.exe -printer -noquery -mono each is printed with the incorrect orientation. I've tried converting the files to TIFF using Ghostscript and the output appears to be correct (i.e. it matches what is printed if I send the files to PostScript laser printer). I've also attached two PDF files, which are scans from the customer of the output printed via gsprint.
Created attachment 7176 [details] landscape.ps
Created attachment 7177 [details] portrait_print_job_printer_output.pdf
Created attachment 7178 [details] landscape_print_job_printer_output.pdf
It works correctly if the Windows printer is set to use A3 paper and portrait orientation. If the Windows printer set set to use A4, or landscape, or rotated landscape, then it will print incorrectly. When using GSPRINT, you can't set the page size from the command line. You can tell it to use portrait orientation with the "-portrait" command line optoin, which overrides the "Portrait, Landscape, Rotated Landscape" setting in the printer "printing preferences" (defaults).
Assigning to me to discuss with customer.
If I remember correctly, gsprint can print to a windows printer queue by name? That could work around the papersize issue by having multiple queues per physical printer. It has been almost 10 years since I last configured/used gsprint so my memory could be fuzzy. Of course this idea is not new: unix print queues have been that way - different queues for different options for the same physical printer - in the early days. It is only when cups came along that it becomes possible/routine to set options per queue.
(In reply to comment #7) > If I remember correctly, gsprint can print to a windows printer queue by > name? You can specify the printer by name, yes. I believe if you don't specify a printer it uses whichever printer is currently set as the default. > That could work around the papersize issue by having multiple queues > per physical printer. It has been almost 10 years since I last > configured/used gsprint so my memory could be fuzzy. That is possible, the default settings for each 'printer' would have to be different, which could be difficult in the case of printers with a lot of options, but its certainly possible.
Has there been any progress with this bug?
With the current version of GSPrint the only solution is to set up multiple printers with the default setup set correclty, and send teh job to that virtual printer. We will be releasing a new version of GSView/GSPrint in future and any issues will be addressed in that or subsequent releases.