Overview

The Helix Core Server can be run in Unicode mode to convert certain elements from their unicode representation on the server, to the particular character set used on clients and triggers that communicate with the server. The following elements are converted:

• File names or directory names that contain Unicode characters

• Helix Server identifiers (for example, user names) and specifications (for example, changelist descriptions or jobs) that contain Unicode characters

  If you need to manage textual files that contain Unicode characters, but do not need the features listed above, you do not need to run your server in Unicode mode. For such installations, assign the Helix Server utf16 file type to textual files that contain Unicode characters.

• unicode files and metadata. These are converted to the character set configured on the user’s machine.

  The Helix Server also verifies that the unicode files and metadata contain valid UTF-8 characters.

Normally, setting the server in Unicode mode should automatically configure the appropriate rendering for each client, independently of the platform where it runs. However, there are some cases in which you might also have to configure the client. The following subsections describe how you set up the server and the client if needed, and offer some troubleshooting tips.

In addition to affecting the client, Unicode settings also affect trigger scripts that communicate with the server. You should check your trigger’s use of the elements noted above (file names, Helix Server identifiers, etc.) and make sure that these are consistent with the character set used by the server.