1.3. Internationalization

Intel Trace Analyzer's target audience is pretty small compared to, say a word processor and the same installation on a parallel computer will often be used in diverse communities. The GUI is as agnostic as possible when it comes to internationalization (or i18n for short).

There is only an English version of the software and the documentation. Also, the number formats in the GUI (refer to Section 2.2 and Section 5.13) and in exported text files always use a decimal point and when separating three digit groups a space character is used instead of a comma or point.

The problem of non-ASCII characters in path and filenames is a little more complicated. Intel Trace Analyzer uses UTF-8 encoding internally and in its configuration file to be able to deal with file and path names that contain characters from most of all the languages of the world.

Since Windows* uses the same encoding (UTF-16) in file and path names regardless of your language and region settings you do not need to configure anything to make the Intel Trace Analyzer work in your environment. As soon as the file names appear correctly in the directory listings they will be usable in the Intel Trace Analyzer.

On Linux* systems you will have to set the encoding part in your locale settings correctly to be able to open your tracefiles. If you use plain ASCII in your path names then you are already done. On a recent Linux* system chances are high that everything is setup correctly out of the box.

Valid locale settings look like en_US.latin-1 (for an U.S. American), de_DE.UTF-8 (for a German), fr_CA.iso88591 (for a Canadian speaking french) and ja_JP.ujis (for a Japanese). The command locale will help to list all available locales and encodings on your system. For the Trace Analyzer only the encoding part of the locale setting is relevant. All file names and path names given on the command line and read from the file system are expected to be encoded in the encoding given by the locale settings. Beware: having for example UTF-8 encoded directory names and storing trace files there with ISO-8859-1 encoded filenames can lead to inaccessible files.

The Intel Trace Analyzer supports the following encodings (but use the encoding names as given by locale -m):

Summary: to make your life simple when moving trace files between different systems and sharing them among people it is recommended that you use pure ASCII characters in path and file names as much as possible. When using non-ASCII characters in path names seems unavoidable then use UTF-8 encoding on Linux* since it is space efficient, can express nearly all languages, is supported on most systems and it is identical to 7bit ASCII encoding for codes 0 to 127.