Limitations of pagebuffer redirection

This page applies to Harlequin v13.1r0 and later; and to Harlequin MultiRIP but not Harlequin Core.

There are some limitations in redirection.

There is no built-in handling (escaping) of special characters in a pagebuffer name, which is derived from the job name. The special characters that may cause problems are those with significance to the operating system on which the RIP is running. There is a problem characters may occur as single characters or as part of a character with a double-byte representation.

To be safe on all platforms, job names must not use the colon ( : ) character or any of:

TEXT

\ / * ? "
            < > |

To avoid problems, create a workflow where the supplied job names cannot cause problems. Alternatively, add code (at step 4 of the example page feature) to create a well-conditioned JobName, and from that the RIP can construct an acceptable pagebuffer name.

There must be one redirection device for each destination directory required within a single RIP session. (It is not possible to redefine the directory for a device while the RIP is running, but it is possible to change the RedirectDevice for %raster-rdwr%.)