Cisco Cisco Computer Telephony Integration Option 9.0 Developer's Guide
CTI OS Internationalization Toolkit
11 of 35
2.3 Comments
Comments must begin with a semi-colon, and must use the standard C++ comment syntax:
either the /* … */ multiline syntax or // syntax, refer to Figure 4.
either the /* … */ multiline syntax or // syntax, refer to Figure 4.
; // this is valid
; /* this is also valid */
// this is NOT valid (no semi-colon)
// this is NOT valid (no semi-colon)
; this is NOT valid (no // for alternative syntax)
Figure 4. Comments
2.4 LanguageNames
The message file must contain only one LanguageNames entry, for example:
LanguageNames=(english=0x0409:ENU_UnitedStates)
If you use the message file provided in the Toolkit, you will find several
predefined
LanguageNames entries listed in the form of comments. To select a language, remove the
comment symbol where appropriate.
comment symbol where appropriate.
Key points:
The text in the LanguageNames line is critical and should not be changed under any
circumstances.
The values and language names match the values reported by the Microsoft Windows
operating system. For a complete list refer to “Language Identifiers and Locale” in the
MSDN Library CD or online.
MSDN Library CD or online.
Changing any value will prevent the Toolkit from loading the correct message files.
The language name for the selected language is the first term in the line. The remainder of
the statement contains the language binary code, the language designator code, and the
country code. The language name is used in the message definitions that follow.
country code. The language name is used in the message definitions that follow.
Cisco Systems, Inc.