PostScript new document command in duplex mode
We are printing several duplex documents to one single ps-file, and we have used the showpage command to indicate that a new document is to be printed. However, due to the duplex setting the first page of the new document might end up on the back of the last page of the previous document, if the number of pages previous document is odd.
Are there any standard way to handle this, or is the only (and ugly) solution that we count the number of pages in each document, and if the number of pages is odd then we add a blank page at the end?
Are there any standard way to handle this, or is the only (and ugly) solution that we count the number of pages in each document, and if the number of pages is odd then we add a blank page at the end?
it's your approach that is flawed, not PS
>We are printing several duplex documents to one single ps-file
PS is not supposed to manage such details. This is due to UNIX phylosophy: each program does one thing and does it well. To add features, add programs in the middle like rings in a chain that take output of a ring, elaborate, and send its own output to the next one.
If you want to use PS to do everything, yes, there's no other solution except adding a blank pages on odd documents to make them even.
>We are printing several duplex documents to one single ps-file
PS is not supposed to manage such details. This is due to UNIX phylosophy: each program does one thing and does it well. To add features, add programs in the middle like rings in a chain that take output of a ring, elaborate, and send its own output to the next one.
If you want to use PS to do everything, yes, there's no other solution except adding a blank pages on odd documents to make them even.
Are you printing directly from the application to the printer?
Or is there a printing system in between?
In the last case that should handle the task of handling the output correctly...
Also a printer should reset when receiving the ^D that separates two print jobs,
if there is no End of Job sign then everything is received as a single large job with indeed running together of pages.
The ^D should be inserted by a Printing system, if you drive the printer DIRECTLY from you application then that needs to behave like a printing system.
Or is there a printing system in between?
In the last case that should handle the task of handling the output correctly...
Also a printer should reset when receiving the ^D that separates two print jobs,
if there is no End of Job sign then everything is received as a single large job with indeed running together of pages.
The ^D should be inserted by a Printing system, if you drive the printer DIRECTLY from you application then that needs to behave like a printing system.
>Also a printer should reset when receiving the ^D that separates two print jobs,
I belive the printing job is only one... they append everything in a single PS file and then send it to the printer. That's why they get this glitch
I belive the printing job is only one... they append everything in a single PS file and then send it to the printer. That's why they get this glitch
ASKER
Thanks.
@noci: The application generates the PS file, and I expected the application to handle this correctly - which it does not, and that was why I asked here, as I could get nowhere with the support from the applications support team.
I will check our PS files to see if there are any End of Job signs included, but I assume not, I would expect that was included when the PS file was added to the print queue.
@ai ja nai: thanks. The philosophy of having everything in one print file is from the application vendor, but they have only recently started to run on linux, previously they only supported MS, but I would expect that it did not make a difference how PS files were handled by the printer. Am I wrong on this?
Thanks for the help so far!
@noci: The application generates the PS file, and I expected the application to handle this correctly - which it does not, and that was why I asked here, as I could get nowhere with the support from the applications support team.
I will check our PS files to see if there are any End of Job signs included, but I assume not, I would expect that was included when the PS file was added to the print queue.
@ai ja nai: thanks. The philosophy of having everything in one print file is from the application vendor, but they have only recently started to run on linux, previously they only supported MS, but I would expect that it did not make a difference how PS files were handled by the printer. Am I wrong on this?
Thanks for the help so far!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for the input - I see that there is quite a bit to be discussed with the application provider (which is why I rated the answers as "Good" - let me know if this is unfair, and I will change it :-) - I feel that Excellent is when there is a ready-to-implement solution).
ASKER