Xerox Paris, a document system Support & Software User Guide
Device Specific Features in Paris
The Paris Spooler Technical Manual
219
How these features are referred to in the output stream
It is important to note that the type of feature (XJT, JobComment, JobCode or
Page) refers to the position of the feature in the output stream, not the contents.
Page) refers to the position of the feature in the output stream, not the contents.
For example, it is possible to insert any comment into the output stream using the
JobCode or Page feature hooks, or to add valid PostScript code to the JobTicket or
Comment portions of the output stream using the XJT or JobComment hooks. It is
the user’s responsibility to ensure the device will accept the code inserted by any
hook as valid. Paris does not read or validate the feature code at all.
JobCode or Page feature hooks, or to add valid PostScript code to the JobTicket or
Comment portions of the output stream using the XJT or JobComment hooks. It is
the user’s responsibility to ensure the device will accept the code inserted by any
hook as valid. Paris does not read or validate the feature code at all.
What else you should know about using Features
•
If a job asks for a feature that the current XPD file does not support, then
nothing happens (this is not considered an error, and printing will continue).
nothing happens (this is not considered an error, and printing will continue).
•
If two printers implement the same feature (i.e., binding) but use different code
to achieve this, then the XPD files for each printer should have the same feature
name defined, but with different code.
to achieve this, then the XPD files for each printer should have the same feature
name defined, but with different code.
If one printer requires the activation to be in the Job Ticket, and another requires it
in the Job Preamble, then each printer XPD should be given two features, one of
which is a ‘null’ code. The Job is then created calling for both features.
in the Job Preamble, then each printer XPD should be given two features, one of
which is a ‘null’ code. The Job is then created calling for both features.
For example
:
Printer 1:
XPDFeature_JobComment Binding1: “%%Requirements: binding true”
XPDFeature_JobCode Binding2: “”
Printer 2:
XPDFeature JobComment Binding1: “”
XPDFeature_JobCode Binding2: “binding true setpagedevice”
The job would call for both ‘Binding1’ and ‘Binding2’, and would then print
correctly on both printers.
Printer 2:
XPDFeature JobComment Binding1: “”
XPDFeature_JobCode Binding2: “binding true setpagedevice”
The job would call for both ‘Binding1’ and ‘Binding2’, and would then print
correctly on both printers.