The character data in
a transport file is created in either of two types of encodings:
-
the UTF-8 encoding of the SAS session
in which the transport file is created
-
the Windows encoding that is associated
with the locale of the SAS session in which the transport file is
created
These examples show
how SAS applies an encoding to a transport file:
Assignment of Encodings to Transport Files
Encoding Value of the
Transport File
|
Example of Applying
an Encoding in a SAS Invocation
|
|
|
|
A SAS session is invoked
using the UTF-8 encoding. The session encoding is applied to the transport
file.
|
|
|
A SAS session is invoked
using the default UNIX encoding, latin2, which is associated with
the Polish Poland locale.
|
For a complete list
of encodings that are associated with each locale, see
Locale Tables
in SAS National Language Support (NLS): Reference Guide.
In order for a transport
file to be imported successfully, the encodings of the source and
target SAS sessions must be compatible. Here is an example of compatible
source and target SAS sessions:
Compatible Encodings
|
|
|
|
UNIX SAS Session Encoding
|
|
|
Windows SAS Session
Encoding
|
|
|
|
|
|
The encodings of the
source and target SAS sessions are compatible because the Windows
default encoding for the es_MX locale is wlatin1 and the encoding
of the target SAS session is wlatin1.
However, if the encodings
of the source and target SAS sessions are incompatible, a transport
file cannot be successfully imported. Here is an example of incompatible
encodings:
Incompatible Encodings
|
|
|
|
UNIX SAS Session Encoding
|
|
|
|
cs_CZ (Czech Czechoslovakia)
|
|
|
|
|
The encodings of the
source and target SAS sessions are incompatible because the Windows
default encoding for the cs_CZ locale is wlatin2 and the encoding
of the target SAS session is open_ed-1141. A transport file cannot
be imported between these locales.
When importing transport
files, you will be alerted to compatibility problems via warnings
and error messages.