The ScopeSET Support and Community Portal
View all tags
Tags:    No tags associated yet.

Unicode Support in OpenAmeos

Starting with 10.2, OpenAmeos supports Unicode. This has some ramifications which need to be considered.

Unicode can be used with Microsoft Jet, SQLite and Sybase as the repository server. For Sybase ASE 12.5 and 15 an additional character set needs to be added to the server. A brief description how to do this can be found at Add Unicode Character Set to Sybase ASE.

There are three new ToolInfo variables to define the encoding used for non UNICODE applications like Note Description editors and RTF Viewers.

  • note_desc_editor_encoding, encoding used for the node description editors
  • rtf_encoding, encoding, used for RTF viewers
  • nonunicode_encoding, a combination of the above two 

When rtf_encoding or nonunicode_encoding are set, characters in RTF are converted with the specified code page. As a result, Unicode characters (like €) used in symbol names are printed correctly in RTF. If the TI variable is not set, Unicode characters (>127) are printed as Unicode escapes (\u1028? for example).

ToolInfo note_desc_editor_encoding is needed to define the encoding if non Unicode editors like notepad are used for note descriptions. As soon as the editor for note descriptions will store the edited text in Unicode, please make sure that neither note_desc_editor_encoding nor nonunicode_encoding are set.

The default value is


This is the German character set and does the proper encoding for notepad as the description editor and MS Word as the RTF viewer.

Below a list of possible values for these variables:

cp437 United States IBM
cp819 Windows 3.1 (United States and Western Europe)
cp850 IBM multilingual
cp852 Eastern European
cp860 Portuguese
cp862 Hebrew
cp863 French Canadian
cp864 Arabic
cp865 Norwegian
cp866 Soviet Union
cp932 Japanese
cp1250 Windows 3.1 (Eastern European)
cp1251 Windows 3.1 (Cyrillic)
cp1252 German

A complete list can be found at Supported Conversion Encodings