When Essbase Administration Server opens files, encoding is determined in one of the following ways:
For files that include an encoding indicator, the specified encoding is used.
For files that do not include an encoding indicator and that are opened from Essbase, the application encoding is used.
For rules and text files that do not include an encoding indicator and that are not opened from Essbase, Administration Services Console asks for the encoding. For outline files (.otl), the Essbase encoding is used.
When Essbase Administration Server saves files, text is encoded in one of the following ways:
For files saved to Essbase, the application encoding is used:
In UTF-8, if the application is a Unicode-mode application
In the encoding specified by the Essbase ESSLANG variable, if the application is a non-Unicode-mode application
For previously existing files that are saved to client locations, the previously existing encoding is used.
For new text files that are saved to client locations, Administration Services Console asks for the encoding. For outline files (.otl), the Essbase encoding is used.
Note: | Once the encoding is specified and the file is saved, the encoding cannot be changed, even if the file is saved to another name. |
“Managing File Encoding” in the Oracle Essbase Database Administrator's Guide