The Analytic Services Unicode File Utility is a standalone program that enables
you to add encoding identifiers to files used with Unicode-mode applications.
Encoding identifiers are markers that identify the text encoding used in the
file. Located in the arborpath\bin
directory, this utility is called
essutf8.exe
(in Windows) or ESSUTF8
(in UNIX). You can use this utility to make
the following changes to text files, outline files, and rules files:
.otl
) and rules files (.rul
)The Analytic Services Unicode File Utility works with text files and binary files that you can edit and change. This utility does not support user-defined characters (UDC) such as can be found in Japanese, Korean, Chinese, and Taiwanese host code pages.
Applicable text files include:
.csc
).rep
).alt
)Applicable binary files include:
.otl
).rul
)Using the Analytic Services Unicode File Utility to insert locale indicators in outline files and rules files is relevant when outline files and rules files were created by earlier releases of Analytic Services or its clients (prior to Release 7.0) or when rules files are initially created on a client. For a more detailed description of encoding and locale indicators, see the "Enabling Multi-Language Applications Through Unicode" part in the Database Administrator's Guide.
Note: Text files for non-Unicode-mode applications cannot be encoded in UTF-8. They must be encoded according to a locale definition common to the client and Analytic Server.
See the "Enabling Multi-language Applications through Unicode" part of Volume III of the Database Administrator's Guide for additional information about encoding formats, the UTF-8 signature, and locale indicators.
This topic contains the following subtopics:
Different types of encoding indicators are used, depending on the type of file and its encoding:
While you are migrating various client and server sites to a Unicode-enabled release with Unicode-mode applications, Analytic Services provides you the flexibility to use non-Unicode-encoded files. For Unicode-mode applications, using UTF-8-encoded text files is recommended. Using UTF-8 encoding is simpler; you do not need to keep track of different locales.
The following list includes examples of situations when you would use the Analytic Services Unicode File Utility.
For a more detailed description of encoding and locale indicators, see the Database Administrator's Guide.
©2004 Hyperion
Solutions Corporation. All Rights Reserved. http://www.hyperion.com |