Altair SLC and Altair Analytics Workbench have certain features available for the convenience of some of our international customers.
Please comment below if your preferred language support is not yet available, to help us plan for future internationalisation.
DOCUMENTATION
Our documentation is in English but it is also available in French (except for the SAS language reference). The Workbench User Guide is also available in Spanish and Italian.
WORKBENCH USER INTERFACE
The Workbench user interface is available in English, French, Italian, Spanish and Japanese. It is the language settings of your operating system user interface (Windows, Mac, or Linux) that determines the language used by the Workbench user interface.
During the installation of the Workbench MSI you should select an optional language pack if you require one. (If you are not sure whether this was selected at install time then look in the \eclipse\configuration\ of the Workbench installation for the hidden folder .langpacksinstallfiles which will contain any optional language packs that were installed.)
The locale settings of your operating system are also used by Workbench to determine the conventions for display of numbers, etc.
The command line “workbench -nl <lang>” allows you to override the operating system language. (You can modify the workbench.ini file to put the -nl <lang> option on the command line option permanently.)
Workbench facilitates the reading, writing, and editing of SAS language source files in any major character encoding, including Latin1 (ISO 8859-1), Latin9, Kanji, Shift JIS, Unicode / UTF variations, ASCII and EBCDIC.
We recommend the use of UTF-8 encoding to encompass a broad range of the world’s character sets. However we also recognise that Japanese customers typically use ShiftJIS encoding with Microsoft Office applications so for these customers we recommend to use ShiftJIS in Workbench and Altair SLC, for compatibility.
See also the ENCODING-en.txt file in the “doc” folder/directory within your Workbench installation files.
ALTAIR SLC Character Encoding
Altair SLC sessions each have a session encoding and built-in transcoding capability so that strings of characters from databases, input files, source code, etc can be converted to the session encoding – and if required can be converted to alternative encodings when saving or outputting strings.
The LOCALE and ENCODING system options can be defined for each Altair SLC session (see “Processing Engine LOCALE and ENCODING settings” help topic). The default is ENGLISH_UNITEDSTATES.
The ENCODING system option must be set in the .CFG config files that are parsed when Altair SLC starts up as it cannot be set using an ‘options’ language step.
Finally, note that truetype fonts are used by SLC when writing to PDF and other ODS destinations, so your fonts - including any language-specific fonts you use - need to be installed in the operating system of the SLC server machine.
