The W3C wisely explains, "In other situations, such as for APIs, UTF-16 or UTF-32 may be more appropriate.
W3C明智地解释说，“其他情况下，如对于API，UTF-16或UTF-32可能更合适。
In XSLT 1.0, implementations can put a BOM for UTF-8 documents, and would likely do so for UTF-16 and UTF-32.
在XSLT 1.0中，实现可以在utf - 8文档中加上BOM,UTF - 16和UTF - 32可能也是如此。
Also, CODEUNITS32 specifies that Unicode UTF-32 is used to understand the character boundaries of multi-byte characters.
同样，CODEUNITS32指定使用UnicodeUTF - 32来理解多字节字符的字符边界。
Unicode defines character encodings in three distinct sizes-utf-8, UTF-16, and utf-32-while the traditional character type is 8 bits.
Unicode用三种不同的大小定义字符编码—utf -8、UTF - 16和UTF - 32—而传统的字符类型是8位的。
When supplementary characters are involved, a supplementary is counted as two UTF-16 code units using CODEUNITS16, or one UTF-32 code unit using CODEUNITS32.
使用增补字符时，对于一个增补字符，使用CODEUNITS16 计算是两个UTF-16代码单元，而使用CODEUNITS32 计算则是一个 UTF-32 代码单元。
There are others (UTF-16 and UTF-32, for example) defined by the Unicode consortium, but UTF-8 is the best supported encoding for international character sets.
Unicode协会还规定了其他一些编码方式（如UTF-16,UTF-32），但 UTF-8是国际字符集支持得最好的一种。
Applications that require random access to specific indexes within a document may operate more quickly when using a fixed-width encoding such as UCS2 or UTF-32.
需要随机访问文档特定位置的应用程序使用ucs2或utf - 32这类固定宽度的编码可能操作起来更快。
And unlike UTF-16 and UTF-32, it is backwards-compatible with ASCII, meaning UTF-8 is increasingly becoming the default encoding system fore-mail and websites.
不像的UTF - 16和UTF - 32，它是向后兼容的ASCII，这意味着使用UTF - 8是日益成为默认的编码系统的电子邮件和网站。
And unlike UTF-16 and UTF-32, it is backwards-compatible with ASCII, meaning UTF-8 is increasingly becoming the default encoding system fore-mail and websites.
不像的UTF - 16和UTF - 32，它是向后兼容的ASCII，这意味着使用UTF - 8是日益成为默认的编码系统的电子邮件和网站。
应用推荐