3.2 Character Sets and Encodable Strings

The Cloud Fax and Notifications API uses XML documents to transmit information. Within an XML document, a single character encoding applies - most commonly UTF-8. EasyLink systems permit some data - documents and certain fields - to contain data using a different character encoding. There are also some fields which may contain data which may be in a different character encoding, but for which the character set information is not recorded.

Character sets should be specified using ISO standard names, or names in the following list. Note that EasyLink support for character sets is evolving and may vary depending on the particular systems a customer uses - testing is recommended to verify support for any particular application.s use of any of these (including UTF-8).

• US-ASCII
• ISO-8859-1
• SHIFT-JIS
• EUC-JP
• EUC-KR
• US-ASCII
• ISO-8859-1
• ISO-8859-1
• BIG5
• GB2312
• KS_C_5601-1987
• UTF-8
• ISO-2022-JP
• ISO-2022-KR
• ISO-2022-CN
• ISO-8859-2
• ISO-8859-3
• ISO-8859-4
• ISO-8859-5
• ISO-8859-6
• ISO-8859-7
• ISO-8859-8
• ISO-8859-9
• ISO-8859-10
• ISO-8859-13
• ISO-8859-14
• ISO-8859-15
• windows-1252

3.2.1 Field Character Sets

EasyLink stores most account data as ISO-8859-1 data. In general, it should be assumed that data provided for account data should be IS0-8859-1, or convertible to that character set.

The EncodableStringType defined in the schema, which includes an attribute "b64charset", can be used, if necessary, to transmit information in other character sets. The value of the field must be supplied in base64-encoded form, and the b64charset attribute specifies the character set the data is actually in.

The value of the b64charset attribute must be a "standard name" (as described above) or value "binary". These values are not enforced by the schema, and testing is advised to confirm support for any particular application.