Skip to main content
Skip table of contents

How do I localize the LDK Tool?


This page applies to Harlequin v13.1r0 and later for Harlequin MultiRIP.

If you plan to use Harlequin Core and require a localized LDK Tool, please contact Harlequin Support.

The language of the LDK Tool can be changed, using a very similar method to a RIP localization, with a resources file (which should be placed in the same directory as ldktool.exe) and a messages file (which should be placed in the Messages subdirectory below the directory in which ldktool.exe is installed).

Contact Harlequin Support for the base Resources file to develop from if you need it.

By default an ENU messages file is provided for US English, and no resources file. The tool runs in English.

If multiple messages files are present (with associated resources files for all except ENU) the user can change language in the File menu. When the user changes the language of the LDK Tool, it quits with exit status 44 and must be restarted to use the new language. Under normal circumstance the LDK Tool quits with exit status 0.

Therefore, if the installer has run the LDK Tool so that the user can activate the RIP and then the user switches language, the developer of the installer should check its exit status and re-run the LDK Tool in the newly selected language if necessary.

If the ENU messages file is removed and messages and resources files are provided for only a single language, the LDK tool is forced to run in that language.

As an example, the LDK Tool can be forced to run in Japanese, with no selection needed by the user, by providing just \Messages\JPN and RESOURCE.JPN, and omitting \Messages\ENU. So, if there is only one language option available the LDK Tool uses it; you do not have to make any selections.

JavaScript errors detected

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

If this problem persists, please contact our support.