When you install SAS 9.1.3 Foundation, you can choose to load localized
components (translations for various languages), the scope of which
varies from platform to platform, and from language to language.

Installing localized components (with user interface, system messages,
and documentation in the local language) must be distinguished from
setting the LOCALE= system option. The LOCALE= option does not invoke a
localized version but reflects the local conventions and culture for a
particular geographical region. However, when you install SAS 9.1.3
Foundation and you choose to load language translations, the
installation automatically sets the LOCALE= system option to the default
value for the language installed.

On Windows, language-specific configuration files are created for each
language installed (including English). If you select a language other
than English as default, a !SASROOT\nls\en directory may not be created,
however. In this case, you must create it and the corresponding
subdirectories manually and do the necessary configurations yourself.

An additional configuration file that is language-independent is
!SASROOT\sasv9.cfg. This master configuration file in !SASROOT is used
by all languages in addition to the language-specific files in
!SASROOT\nls\<lang>. It contains a link pointing to the configuration
file you have chosen as "default"; for example, -CONFIG "C:\Program
Files\SAS\SAS 9.1\nls\en\SASV9.CFG". You can modify these configuration
files to fit your needs.

The LOCALE option is set in the system configuration file for each
language installed. For example, on Windows !SASROOT\nls\fr\sasv9.cfg
sets LOCALE to French_France by default. If you want to change the
default locale setting for SAS, you can set the LOCALE system option to
the appropriate language in your system configuration file.

On UNIX ssytems, SAS is invoked by Bourne Shell scripts located in the
!SASROOT/bin directory. A SAS invocation script is created for each
language installed. The invocation scripts are named using the language
codes of the installed language. For example, sas_en invokes the English
version of SAS 9.1.3 Foundation. See the language codes table the
Installation Instructions for SAS 9.1.3 Foundation for UNIX Environments
for a list of all valid language codes.

If more than one language is chosen for installation, you will be asked
to choose a "default" language. SAS Setup uses this information to
create a symbolic link, !SASROOT/sas, to reference the appropriate
invocation script in !SASROOT/bin. For example, in an English
installation, !SASROOT/sas would be a symbolic link pointing to the
!SASROOT/bin/sas_en invocation script. SAS 9.1.3 Foundation creates a
separate configuration file for each language installed (including
English). These language-specific configuration files are called
!SASROOT/nls/<lang>/sasv9.cfg for each respective language. An
additional configuration file that is language-independent is
!SASROOT/sasv9.cfg. This master configuration file in !SASROOT is used
by all languages in addition to the language-specific files in
!SASROOT/nls/<lang>/.

You can modify these configuration files to fit your needs.  On z/OS,
SAS is distributed in encoding support groupings that usually support a
single encoding and a group of related locales. SAS system files
containing material translated into local languages are distributed
matching these specific encoding support groupings. SAS system
installation media VOLSERs and certain installed SAS system filenames
contain a two-character code that identifies the encoding(s) and
locale(s) supported. See the "Language, Encodings and Installation
Codes" table in the Installation Instructions for SAS 9.1.3 Foundation
for z/OS" for a list of all valid codes. For CLISTs, the naming
conventions are CLSTyyzz and CLSTzz, where yy=language code, and
zz=encoding. For example, the encoding for French is WA. There will be
two CLISTs: CLSTFRWA and CLSTWA, where CLSTFRWA contains translated
material in WA encoding, and CLSTWA is in English with the WA encoding.
Some installations only have the CLSTzz CLISTs.

On Windows and UNIX, you can add additional languages to an existing
installation by simply running the install and choosing to update an
existing installation. Then just choose the products you want to add
including any localizations. This is not possible on z/OS and it would
not make any sense there, since z/OS media is distributed in encoding
support groupings, which usually support a single encoding or a group of
related locales only.

If a service pack was installed for one language, it does not have to be
reinstalled for all the others.

Windows regional settings and UNIX locales are independent of the SAS
locales and localized components. However, it is recommended to use a
Windows regional setting or UNIX locale appropriate to the localized SAS
System image. You may experience unexpected results (for example, fonts
not being available and characters not being displayed correctly) if the
regional setting and the localized SAS System image are not consistent.

If multiple SAS localizations have been installed on the system, you may
need to change the setting for each localized SAS System image before
invocation. For information on how to change or to use these locale
settings, refer to the appropriate system documentation.

Operating System and Release Information