Editing operations in MBCS applications should operate on characters, not bytes.
MBCS应用程序里的编辑作业应该在字元上操作，而不是在位元组上。
For database design, you have to consider that the column sizes have to be defined in bytes, not in characters.
对于数据库设计，必须考虑到列大小是按照字节数定义的，而不是按照字符数。
Because the concept of "lines" isn't relevant for binary files (logical data constructs are not generally terminated by newlines), you must always specify the number of bytes that you wish to read in.
由于“行”的概念与二进制文件无关(逻辑数据结构通常都不是由新行终止)，因此您必须指定需要读入的字节数。
Each byte in the entire file is taken by no more than one section at a time, but there can be orphan bytes that are not covered by a section.
整个文件中的每个字节每次只能由一个区段使用，不过可以存在不被任何区段所包含的孤立字节。
Networks tend to consider data not in large chunks, nor in tiny bytes, but in packets.
网络不习惯于用较大的数据块或较小的字节来表示数据，而习惯于以包为单位。
The server may or may not return the number of bytes requested but identifies the number of bytes returned (along with the data) within the READ RPC reply.
服务器可能返回或不返回所请求字节的数量，但是会指出在READRPC回复中所返回(随着数据)字节的数量。
In combination with the data types that use UTF-8 encoding, functions like SUBSTR and LENGTH still work with bytes and not with characters.
在与使用UTF - 8编码的数据类型结合使用时，SUBSTR和LENGTH等函数仍然处理字节而不是字符。
For example, you can store an image or machine language command sequence within a blob, with the maximum size typically not exceeding 65,536 bytes.
例如，可以在一个blob中存储一幅图像或者一个机器语言命令序列，最大大小通常不超过65,536字节。
PHP USES so-called binary strings - in PHP, a string is not a string of Unicode characters, but rather a sequence of bytes.
PHP使用所谓的二进制字符串—在php中，一个字符串并不是一个Unicode字符的字符串，而是一个字节序列。
Problem: The created file is of 85 bytes because the Xserver is not running during the conversion.
问题：由于 Xserver在转换期间未运行，创建的文件为 85字节。
Because error.txt is not zero bytes in length, we read in the content of that file and assign it to the summary property.
由于error . txt的大小不为0，因此我们将读取该文件的内容并将它分配给summary属性。
While not necessarily a server performance tip (since you might see CPU utilization go up), using gzip compression can decrease the number of bytes sent by your server.
虽然使用gzip并不一定是服务器性能技巧（因为您可能会看到CPU使用率的提高），但是使用 gzip压缩可以减少服务器发送的字节数量。
First, the request and reply each may not exceed 1,920 bytes of information per transaction.
首先，在每个事务中，请求和应答均不能包含超过1,920字节的信息。
Functions are free to use the 288 bytes that are physically below the stack pointer for functions that do not call other functions.
函数可以自由使用288字节的内存，对于不调用其他函数的函数来说，这段内存物理上在堆栈指针之下。
If the file does not end with a delimiter, the file is processed as if a delimiter followed the final bytes of the file.
如果文件没有以分隔符结尾，则对文件的处理方式就像文件的最后一个字节后面跟着一个分隔符一样。
Here, reading the bytes is not enough to extract the necessary information; it returns a buffer if the string is read.
此处，读取字节还不足以提取必要的信息，如果要读取字符串，则要返回一个缓冲区。
Note that it's not completely random. The first two bytes are, by convention, the TLS version (03 01).
需要指出的是这并非全是随机数，按约定，最前面的两个字节是TLS版本(03 01)。
The most common example of this restriction can be seen in WML that's used for WAP pages, where each deck of pages should not exceed approximately 1500 bytes.
有个最常见的例子可以说明这一限制，即，wap页面中使用的WML。在WML中，每一张页面都不能超过约1500字节。
However, dealing directly with bytes isn't nearly as manageable when you're not just transferring bytes from a source (like a static VXML file) to an output stream.
但如果从源(例如一个静态VXML文件)传输到输出流的不仅仅是字节，那么直接处理字节的方式几乎无法管理控制。
Because it's not possible to determine the number of bytes to be accessed from a memory location, a method is needed to find out the amount of memory addressed.
因为不可能决定从一个内存位置开始访问的字节数，所以需要用一个方法计算访问的内存量。
The first block that is now parsed has an empty field for this first section; subsequent ones are likely to have one or more bytes listing tag indexes that have not yet been closed.
第一个被解析的块有这个第一节的空白字段；后续块可能有一个或多个字节列出尚未关闭的标记的索引。
Finally, for bytes, the preferred slot is not at the beginning of the register, but three bytes to the right.
最后，对于字节数，首选槽并不在寄存器的开始，却在右侧的3个字节。
It returns the number of bytes that were not clearable or zero if the operation was successful.
它将返回不可清除的字节数，如果操作成功，则返回0。
Note that no matter what number you specify, fread will not read more than 8,192 bytes (8 KB).
不管指定多少字节，fread都不会读取超过8,192个字节(8KB)。
The application should be able to process meaningfully any stream of bytes you send it that it does not reject as DE jure invalid.
应用程序应能够处理所发送的任何有意义的字节流，而不会因权利上(de jure)无效而拒绝。
If the initializer is a bytes literal, you need not specify the encoding type: Remember, bytes literals are not strings. But like strings, you can concatenate bytes.
如果初始化器是一个bytesliteral，则无须指定编码类型：请记住，bytesliteral并不是字符串。
The performance is not about number of parameters (or just a little) but about number of bytes send. The more data you send, the more it's costly to transfer/parse.
参数的性能不是数量（或一点点）而是发送的字节数。你发送更多的数据，更昂贵的传输/解析。
Otherwise, if the full-text unique key size exceeds the maximum size allowed (900 bytes), full-text population will not be able to proceed.
否则，如果全文唯一键的大小超过所允许的最大值(900个字节)，全文填充将无法继续进行。
Not an issue with dynamic translation, you know that a chunk of bytes is code because the machine is trying to execute it.
与动态翻译不是一个问题，你知道一块的字节代码，因为这台机器是试图执行它。
Not an issue with dynamic translation, you know that a chunk of bytes is code because the machine is trying to execute it.
与动态翻译不是一个问题，你知道一块的字节代码，因为这台机器是试图执行它。
应用推荐