User Help > Managing Source Files as Members > Character Encoding
 
Character Encoding
Integrity Lifecycle Manager automatically decodes UTF-8 revision contents based on the presence of a byte order mark (BOM) in the file.
Integrity Lifecycle Manager supports UTF-8 encoded files in the following views:
• Annotated Revision
• Visual Difference
• Visual Merge
You can change the character encoding used in each view through a Character Encoding drop-down list on the toolbar. To make the list visible in the GUI, select View > Character Encoding. The list is always visible in the Web interface.
* 
When check in operations are performed on the same member from different locales, ensure that either UTF-8 character encoding is used, or the characters used are standard ASCII. Otherwise, there may be unexpected results when opening the files in an editor or compiler configured for a different locale.
Integrity Lifecycle Manager supports the following encoding/decoding character sets:
Region
Character Set
Unicode
Unicode (UTF-8)
Western Character Sets
English (US-ASCII)
Western (Windows-1252)
Western (ISO-8859-1)
Western (ISO-8859-15)
Western (IBM-437)
Western (IBM-850)
Western (IBM-858)
French-Canadian (IBM-863)
Japanese Character Sets
Japanese (EUC_JP)
Japanese (ISO_2022_JP)
Japanese (ISO_2022_JP_2)
Japanese (Shift_JIS)
Japanese (x-euc-jp-linux)
Japanese (x-eucJP-Open)
Japanese (x-windows-iso2022jp)
You can set character encoding preferences for each view and command through your client preferences. These preferences are used if the character set cannot be determined through the file’s BOM, or if no character set is specified in the command line. By default, the character set in the preferences matches the default character set provided by the client’s operating system locale.
* 
The encoding settings do not apply to third party merge or differencing tools.