The string was longer than the limit of 16380 single-byte characters.
字串长度超过 16380单一位元组字元的限制。
Prior to adjacent strings being concatenated, a string cannot be longer than 16380 single-byte characters.
在相邻字串进行串连之前，字串长度不可超过16380单一位元组字元。
Also, CODEUNITS32 specifies that Unicode UTF-32 is used to understand the character boundaries of multi-byte characters.
同样，CODEUNITS32指定使用UnicodeUTF - 32来理解多字节字符的字符边界。
Recognizing the character as a single, unit as opposed to a sequence of bytes, is a requirement in the case of string manipulations involving multi-byte characters.
将字符看作一个单元而不是一个字节序列，这是进行多字节字符的字符串操作的必要条件。
In Figure 6, shows a search for the character after the third byte, which would have been the second occurrence of the character "a" if all were single byte characters.
在图6中，搜索第三个字节后的字符，如果所有的字符都是单字节字符的话应该搜索到第二次出现的“a”字符。
It may also be necessary to build the libiconv library to support a specific code page or apply a patch when complex multi-byte characters are used, such as those in Japanese.
使用复杂的多字节字符时，比如日语中的那些字符，可能需要构建libiconv库来支持特定代码页，或者是需要应用补丁。
These characters each have a single byte of display and multiple bytes of internal storage.
每个这些字符都有一个显示字节，以及多个字节的内部存储。
Some UTF-8 characters are normally represented in one byte, others in two, others in three, and so on, and programs are supposed to always generate the shortest possible representation.
有一些UTF - 8字符由一个字节来表示，一些用两个字节来表示，还有一些用三个字节来表示，甚至更多，而程序被假定总是生成最短的可能的表示。
But if byte semantics is used, and characters are encoded using UTF-8, then the length of the string is 6 bytes.
但是如果使用字节语义并使用UTF - 8对字符进行编码，则该字符串的长度为6字节。
The counting of string length using a byte is referred to as byte semantics in this article, and the counting of string length using the number of characters is referred to as character semantics.
本文中将使用字节计算字符串长度的方法称作字节语义，而使用字符数计算字符串长度的方法称作字符语义。
Row 2 has only English characters containing 10 letters (logical characters) that contain 1 byte each.
行2只有英文字符，包含10个字母(逻辑字符)，每个字符包含1字节。
Encode the hashed byte array into hex characters.
将哈希后的字节数组编码成十六进制字符。
If you use a nullable VARCHAR column and only ASCII characters (UTF-8 format 1 byte per character) involved, the maximum character length that can be indexed is 1021 characters.
如果使用可空的varchar列并只涉及ASCII字符(在utf - 8格式中每字符1字节)，那么可以建立索引的最大字符长度是1021个字符。
In hexadecimal notation, it takes merely two characters to represent a byte.
在16进制记法里，仅仅用两个字符就能表示一个字节。
For documents that contain Unicode characters beyond the ASCII range, the parser must read and convert multiple byte sequences for each character.
对于包含ASCII以外的Unicode字符的文档，解析器必须为每个字符读取和转换多字节序列。
The characters numbered 0 to 0x7f (127) encode to themselves as a single byte, and larger character values are encoded into 2 to 6 bytes.
从0到0x7f(127)的字符把自身编码成单字节，而将值更大的字符编码成2到6个字节。
UTF-8 encodes ASCII characters with only 1 byte.
UTF - 8只用1字节对ASCII字符进行编码。
The first phase translates the sequence of characters from byte order (how the characters are stored in memory) to the proper written order (as it would appear on paper).
第一个阶段是将字符序列从字节顺序(字符在内存中如何存储)转换成正确的手写顺序(字符如何在纸面上显示)。
This means the default font setting in the system cannot display the characters for double-byte languages.
这意味着系统中的默认字体设置不能显示双字节语言的字符。
English is not a multi-byte character set, so it cannot contain partial characters.
英语不是多字节字符集，因此不能包含部分字符。
Row 1 has a multi-byte UTF character containing 3 logical characters containing 3 bytes each (superscript denotes the storage of a single letter).
行1有一个包含3个逻辑字符的多字节ut f字符，其中每个字符包含3个字节(上标表示一个字母的存储)。
In the Windows operating system, Microsoft provides the Arial Unicode MS font, which enables the display of characters in most languages including double-byte languages.
在Windows操作系统中，Microsoft提供了ArialUnicodeMS字体，支持多数语言中的字符显示，其中包括双字节语言。
Multi-byte support is enabled, by default, to allow you enter Japanese characters into the description and label fields of your Rhapsody model.
默认条件下，多字节的支持也包含在内，允许您在Rhapsody模型的描述以及标签区域中输入日语字符。
In other words, POSIX locales are potentially able to deal with 2 - and 3-byte Japanese and Chinese characters.
换句话说，POSIXlocale有可能可以处理2字节或者3字节的日文或中文字符。
Prior to DB2 UDB V8.2, a Unicode database could only be defined with the collating sequence IDENTITY, which means that the characters are compared by their byte encoding.
在DB 2UDBV8.2之前，Unicode数据库只能定义为排序次序identity，这意味着按照字节编码对字符进行比较。
Prior to DB2 UDB V8.2, a Unicode database could only be defined with the collating sequence IDENTITY, which means that the characters are compared by their byte encoding.
在DB 2UDBV8.2之前，Unicode数据库只能定义为排序次序identity，这意味着按照字节编码对字符进行比较。
应用推荐