Skip to main content
Skip table of contents

(v13) Using "%%Title:" for Jobname

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

Some input channels do not provide a sensible file name for input jobs. In such cases, when no other job name is set by the job (in the user parameters or statusdict), all the files in the output controller have the same name.

In this case, it is possible to force the RIP to use the value of the %%Title: comment in the job as the job name. This feature is initially disabled, but you can  enable it for a particular input channel by adding its Channel Class to the UseTitleForJobName dictionary in statusdict, thus:

statusdict /UseTitleForJobName get /SocketInput true put

In this example, replace SocketInput with the name of the desired input channel class. The value of the key in the dictionary (true in the example) is ignored.

When a job is subsequently processed, and the input channel class is present as a key in the UseTitleForJobName dictionary, the value of the %%Title: comment (if present) is set as the value for the jobname key in statusdict. (As a side effect this also sets the JobName user parameter.)

The UseTitleForJobName dictionary is initially empty, but gets populated with Global Graphics' default list of channel classes which are to benefit from this behavior by the file SW/Sys/ExtraStart/UseTitleForJobName.

OEMs can add further channel classes in a startup file, such as HqnOEM, for application to all jobs, or in a page feature for individual jobs.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.