Search results for query: *

If the PostScript files do not re-define "setpagedevice" themselves, you can re-define "setpagedevice" in the prologue.ps file: /ORIGsetpagedevice /setpagedevice load def % Save the original /setpagedevice { dup % Get copy of dictionary ...<code to inspect dictionary and run commands based...

In the procedure "r", "ra" and "s" are called. You might want to check the operand stack after the "ra" procedure has executed. There might not be the correct number and/or order of objects on the stack for the "s" procedure. Thanks Scott Prouty

Are you printing from your application through a printer driver? If so, then there should be settings in the printer driver to set the desired page size. Is your application generating PostScript code without using a printer driver? If it is, then the line you mentioned is correct...

There are two main ways jogging/offsetting is implemented on a printer, if it supports jogging/offsetting at all. One way is to jog/offset at the end of every job. This kind of jogging/offsetting can often be achieved by a setting on the printer, without any commands needed in the job. This...

PostScript code for finishing options are specific each particular printer model. So while the /Jog 3 - /Jog 0 works on the Xerox DocuSP, it may not on other printers, i.e. the HP 9000. Unfortunately I do not have access to the HP 9000 PostScript documentation, so I can not say what its...

These would need to go at the top of the page where the jogging/offsetting is to occur. I just happen to have an example file I created a while ago to test jogging/offsetting on Xerox DocuSP printers: %!PS-Adobe %%Requirements: jog simplex % 2001-11-15 SJP % File to test Xerox DocuSP printer...

Read about the "put" command in the PostScript Language Reference Manual... Thanks Scott Prouty

DSC stands for Document Structuring Comments. A PostScript interpreter ignores these comments. The comments are only for pre-processing applictions that might do things like split the pages, do n-up processing, etc. A PostScript device does not read DSC to activate finish operations. The...

On most interpreters, the following should work... At the start of the page to invoke duplexing, use this command: <</Duplex true>> setpagedevice At the start of the page where duplexing is to be stopped, use this command: <</Duplex false>> setpagedevice Be aware that your existing files...

I agree that answering the original question is the way to go. That is what I was attempting to do. However, as I said, of the two level 3 interpreters available to me (Adobe Distiller 6.0 and a Xerox DP75), both run your code in the original post with no errors. The syntax, structure, etc...

Remember that both the code I posted and the code in the original post ran fine through Adobe Distiller without any erorrs producing a valid PDF. So Adobe Distiller at least does not agree with the other interpreters that are getting an error. Just for kicks, I tried the original code on two...

I just ran your origianl code posted above through Adobe Distiller 6.0 and it ran fine with no errors. Are you sure the interpreter you are testing with is Level 3? As for the ASCIIHexDecode terminator ">", note that that is just a termination sequence for the filter, as if you had done...

The code does look like it should work. However, the error seems to indicate a problem with ASCCIIHexDecode. Try terminating the hex data with a ">" without the quotes. This should then satisfy that filter's EOD condition. Also note that because ASCIIHexDecode filter already has a defined...

This depends on how the a particular printer handles the "setpagedevice" command, but issuing the following commands at the start of the appropriate pages can work: To start a duplex set: <</Duplex true>> setpagedevice To start a simplex set: <</Duplex false>> setpagedevice