This page applies to Harlequin v13.1r0 and later; both Harlequin Core and Harlequin MultiRIP
The value of OutputFile
in an Outputs
dictionary must be one of:
A string
| Specifying the full file name to export the contours to. The file name must be formatted in PostScript language encoding, for example (%C%/temp/outputfile.export)
. To suppress file name mapping, we recommend using a slash immediately after the device name.
|
A procedure (PostScript) or procedure string (JSON)
| A procedure that takes no operands and which returns a single string, as described for string
above.
|
An array of strings and names
| Values within the array are concatenated in order to create the file name to export to. Names may be selected from the following:
/JobName
the job name
/JobPath
from Harlequin v12.0r2. The volume and directory path from which the job file is being read.
/Date
the date and time on which the job is processed.
/YY
two-digit year
/YYYY
four-digit year
/MM
two-digit numeric month
/MMM
three-character month name (in English)
/DD
two-digit day
/hh
two-digit hour
/mm
two-digit minute
/ss
two digit second
/Contour
the value of ID from the current Intercepts dictionary
/Exten
the normal file extension for the exported file format. Includes the leading period (“.”).
/Page
The page number within a multi-page file.
/PP, /PPP, /PPPP
the page number padded to 2, 3, or 4 digits with leading zeros.
For example:
[ (%C%/Export/) /JobName (-) /Contour (-) /PP /Extens ]
In a JSON configuration the names above must be encoded as strings where the first character is “<
“ and the last is “>
”, for example:
[ (%C%/Export/), “<JobName>”, (-), “<Contour>”, (-), “<PP>”, “<Extens>” ]
|
