(v13) Making decisions based on preview quality in OPI
This page applies to Harlequin v13.1r0 and later; both Harlequin Core and Harlequin MultiRIP.
OPI version 2.0 introduces the ability for a sending application to include information saying whether the embedded image data should be regarded as proxy data or not. This is encoded in the
%%IncludedImageQuality
comment, which takes the values 1.0 to 3.0. Harlequin has extended this concept by adding the value of 0.0.
The values have these meanings:
| No low-resolution preview data is included in the job file. The Harlequin RIP automatically sets the value of |
| The preview data is known to be low resolution or sub-sampled. It is unlikely that it would be acceptable to use this data for final output. |
| The sending application does not know whether the preview image data is acceptable for final output. |
| The preview data is actually high-resolution data and no OPI substitution is required. |
The in-RIP OPI in the Harlequin RIP also applies this concept to OPI version 1.3 comments. IncludedImageQuality is set to either 0.0 or 2.0 depending upon whether any preview image data is included in the job file.
The configuration items OPIreplaceFiles, OPIreportFiles, and OPIerrorAction have array values where the elements of the array are named actions for each of the values of IncludedImageQuality. That is, the array can be considered as:
[ action_for_0.0 action_for_1.0 action_for_2.0 action_for_3.0 ]
There is compatibility with older code. When using HqnOPIconfigure, or passing configuration data in a call to HqnOPIimage, it is still possible to supply values for these items as single names. Each single name value is expanded to an array holding four copies of the same value.