First, unlike UTF-16, UTF-8 has no endianness issues.
首先，与utf - 16相比，UTF - 8没有endianness问题。
The input file should be encoded in UTF-8 or UTF-16 format.
应该将输入文件编码为utf - 8或UTF - 16格式。
UTF-16BE: 16-bit UCS Transformation format, big-endian byte order.
UTF - 16 BE：16位UCS转换格式，大尾数法字节顺序。
UTF-16LE: 16-bit UCS Transformation format, little-endian byte order.
UTF - 16le：16位UCS转换格式，小尾数法字节顺序。
UTF-16:16-bit UCS Transformation format, byte order identified by marker.
UTF - 16：16位UCS转换格式，用标记(marker)识别的字节顺序。
Other Unicode formats such as UTF-16 tend to contain numerous zero bytes.
其他unicode格式如utf - 16往往包含很多零字节。
Numeric inputs are converted according to the UTF-16 encoding for characters.
根据字符的UTF - 16编码来转换数字输入。
The DOMString type is explicitly specified to consist of wide UTF-16 characters.
DOMString 类型被显式指定包括宽UTF-16 字符。
The character is specified as one or two UTF-16 code units in hexadecimal notation.
这个字符指定为十六进制形式的一个或两个UTF - 16编码单元。
Even documents that use the default UTF-8 and UTF-16 encodings should have such a declaration.
即使采用默认utf - 8和utf - 16编码的文档也应该有这样的声明。
UTF-8 was chosen as the default format for character data columns, with UTF-16 for graphic data columns.
UTF - 8被选择为字符数据列的默认格式，其中U TF - 16用于图形数据列。
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可能也是如此。
But even when you're encoding CJK XML in UTF-8, the actual size gain compared to UTF-16 probably isn't so large.
但即使用utf - 8编码CJKXML，实际的大小可能也比utf - 16小。
Xerces-C + + USES this larger character representation to exchange text as UTF-16 as opposed to UTF-8 or ISO-8859.
Xerces - C+ +使用更大的字符表示UTF - 16而不是UTF - 8或者ISO - 8859交换文本。
UTF-8 can also be browsed or read by almost all text-processing tools, many of which would have problems with UTF-16.
几乎所有的文本处理工具也可以浏览或者读取UTF-8，其中许多工具在处理 UTF-16 时出现问题。
However, if you use UTF-16, the size of the original document roughly doubles and the document takes longer to parse.
然而，如果使用UTF - 16的话，原始文档的大小便要加倍，这样的文档解析起来要花更多的时间。
In that case, it is recommended to use MemBufFormatTarget instead, for receiving an encoded string other than UTF-16.
在这种情况下，要接收非utf - 16编码的字符串，建议您使用MemBufFor matTarget。
In addition, there is another encoding scheme called UTF-16 that can also be used to represent supplementary characters.
另外，还有一种称为utf - 16的编码方案，它也可以用来表示补充字符。
Google doesn't even allow alternate encodings of Unicode such as UTF-16, much less non-Unicode encodings like ISO-8859-1.
Google甚至不允许其他Unicode编码(如utf - 16)，更不用说iso- 8859 - 1这样的非unicode编码了。
This method completely ignores all the encoding information available, and the returned string is always encoded in UTF-16.
这个方法完全忽略所有可用的编码信息，所返回的字符串总是用utf - 16编码的。
A number of different encoding schemes are used for this purpose: UTF-8, UTF-16, ISO-8859-1, Cp1252, SJIS, and many others.
很多编码方案可实现此目的：utf - 8、UTF - 16、ISO- 8859 -1、Cp 1252和SJIS等。
UTF-8 is less likely than UTF-16 or other Unicode encodings to cause problems for systems that are unaware of Unicode and XML.
与UTF-16或其他Unicode编码相比，对于不支持 Unicode和XML的系统，UTF-8更不容易造成问题。
This paper presents a "Fake UTF-16" coding algorithm, so that all XML parsers can handle GB code in an easy and universal fashion.
本文提出伪UTF 16编解码算法，为XML中文数据的解析提供了简单、通用的方法。
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位的。
All three of these may or may not be preceded by a Unicode byte order mark in either UTF-8, big-endian UTF-16, or little-endian UTF-16.
所有这三行之前都可能有Unicode字节序标记，如utf - 8、big -endianUTF - 16或little -endian UTF - 16。
The UTF-16 encoding alleviates some of this penalty because each character is specified using two bytes, assuming no surrogate characters.
因为每个字符都规定使用两个字节，同时假设没有代替的字符，所以 UTF-16编码在一定程度上减轻了这种性能损失。
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是国际字符集支持得最好的一种。
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是国际字符集支持得最好的一种。
应用推荐