(v13) Plugin Mappings files

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

On PCs, where PostScript language filenames are outside the structure permitted by the platform, it is necessary to provide name mappings.

Mappings are provided for the RIP by the mappings file FILEMAP.PS in the SW directory. Plugin directories containing files accessible from the PostScript language must also provide a mapping file when necessary.

The name of the plugin's mappings file must be that of the plugin executable with .map appended, or, on Windows the stem of the executable file name with .map appended.

The RIP can only be installed in long filename mode, but may still require access to networked disks using short filenames.

Mappings provided by the plugin mappings file are merged with those of the main mappings file when the plugin is first loaded. The .map file is then renamed to .mXp . For this reason, it is important not to copy a “used” plugin directory from one SW directory to another. Always start with a fresh copy.

Warning: If you do not start with a fresh plugin directory, the main mappings file will be badly damaged, probably meaning that you will have to install the RIP again from scratch.

When the .map file is processed:

• On a long‐file‐name‐installed RIP, for the unusual cases where even a long name is not representable on the filing system, all mappings are copied from the .map file to the main mapping file. If this results in a conflict with a mapping already present, a new platform‐dependent name is invented, and the file in the plugin hierarchy renamed accordingly. Any files with a short name in the plugin hierarchy are renamed to their long name.

In this way it is possible to provide a short name encoded distribution directory with a single mappings file which is appropriate for both long and short filename installations, and which can be distributed on media which only support short filenames, such as ISO CD‐ROMs. If a plugin will only ever be used on a long‐filename system and can be distributed on long‐filename media, no .map file is required.

Note: If necessary, a plugin can determine whether the system is running with long or short filenames by looking at the deviceDefinition flag d_longfilenames .

The names Setups , Setup , Profiles , Targets , Target , and Misc , as well as the name of the device type, will all require mapping (at least for upper/lower case) when a .map file is needed. Do not assume that mappings for these names already exist.

The .map file is a text file structured just like FILEMAP.PS . For example:

    /Mappings [
      (Misc) (MISC)
      (Profiles) (PROFILES) (Setup) (SETUP)
      (Setups) (SETUPS) (Targets) (TARGETS) (Target) (TARGET)
      (My Special Device Type) (SPECDT)
    ]

The first name in each pair is the name by which the file or directory is to be known in PostScript language code, and the second is the name by which it is known on the native filing system.