The RIP's model of the file system
This page applies to Harlequin v13.1r0 and later; and to Harlequin MultiRIP but not Harlequin Core
The RIP uses an abstract, PostScript language model of the file system. See the Harlequin MultiRIP Extensions Manual for details.
File and directory names given in the next section are given in PostScript language form, but files and directories may differ on your platform. When the RIP is installed to use short filenames, it is not possible to map names from this PostScript language file system model onto the underlying file system. The names are mangled to produce an acceptable name following the 8.3 naming convention. An unacceptable name is one such as:
SW/Config/Page Setup
The name might become:
SW\CONFIG\PGESETUP
Most of the time, this name mangling will go unnoticed, with the RIP taking care of translations. The plugin, however, cannot access the code which converts the PostScript language (abstract) filenames to platformâspecific filenames, and must use the platformâspecific version. This works without difficulty for direct access to a file from the plugin. Care must be taken, however, if the plugin writes a file, and then passes the filename to the RIP, because then the filename differences must be observed. (For example, this might happen when the plugin writes some PostScript language code into a file for interpretation by the RIP.)