UTF-8 requires 8, 16, 24 or 32 bits (one to four bytes) to encode a Unicode character, UTF-16 requires either 16 or 32 bits to encode a character, and UTF-32 always requires 32 bits to encode a character. XML is, by default, encoded as UTF-8, and all XML processors must at least support UTF-8 (including US-ASCII by definition) and UTF-16.
TYPES OF TEXT ENCODING MAC OS X
One rare counter-example is the "strings" file used by Mac OS X (10.3 and later) applications for lookup of internationalized versions of messages which defaults to UTF-16, with "files encoded using UTF-8.
TYPES OF TEXT ENCODING WINDOWS
Therefore, even on most UTF-16 systems such as Windows and Java, UTF-16 text files are not common older 8-bit encodings such as ASCII or ISO-8859-1 are still used, forgoing Unicode support or UTF-8 is used for Unicode. Because they contain many zero bytes, the strings cannot be manipulated by normal null-terminated string handling for even simple operations such as copy. UTF-16 and UTF-32 are incompatible with ASCII files, and thus require Unicode-aware programs to display, print and manipulate them, even if the file is known to contain only characters in the ASCII subset. For instance, the C printf function can print a UTF-8 string, as it only looks for the ASCII '%' character to define a formatting string, and prints all other bytes unchanged, thus non-ASCII characters will be output unchanged. Legacy programs can generally handle UTF-8 encoded files, even if they contain non-ASCII characters. A UTF-8 file that contains only ASCII characters is identical to an ASCII file.
0 kommentar(er)
