2. Boost Beast Translation (zh_Hans)
3. Chinese (Simplified Han script)
4. Zen

3 string ID 18
	Source string description type: section title
	English Clients
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — Clients 7/100 · 7 Needs editing (Needs rewriting)
3 string ID 174
	Source string description type: paragraph
	English __video__ contains video presentation content
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — __video__ contains video presentation content 45/450 · 45 Needs editing (Needs rewriting)
3 string ID 21
	Source string description type: table title
	English Stream Concepts
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — Stream Concepts 15/150 · 15 Needs editing (Needs rewriting)
16 string ID 16
	Source string description type: table title
	English Message Stream Operations
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — Message Stream Operations 25/250 · 25 Needs editing (Needs rewriting)
3 string ID 19
	Source string description type: paragraph
	English A request or response is an [@https://tools.ietf.org/html/rfc7230#section-3 HTTP message] (referred to hereafter as "message") having two parts: a header with structured metadata and an optional variable-length body holding arbitrary data. A serialized header is one or more text lines where each line ends in a carriage return followed by linefeed (`"\r\n"`). An empty line marks the end of the header. The first line in the header is called the ['start-line]. The contents of the start line contents are different for requests and responses.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — A request or response is an [@https://tools.ietf.org/html/rfc7230#section-3 HTTP message] (referred to hereafter as "message") having two parts: a header with structured metadata and an optional variable-length body holding arbitrary data. A serialized header is one or more text lines where each line ends in a carriage return followed by linefeed (`"\r\n"`). An empty line marks the end of the header. The first line in the header is called the ['start-line]. The contents of the start line contents are different for requests and responses. 543/5430 · 543 Needs editing (Needs rewriting)
3 string ID 16
	Source string description type: paragraph
	English A [@https://en.wikipedia.org/wiki/Computer_network ['network]] allows programs located anywhere to exchange information after opting-in to communications by establishing a [@https://en.wikipedia.org/wiki/Data_link ['connection]]. Data may be reliably transferred across a connection in both directions ([@https://en.wikipedia.org/wiki/Duplex_(telecommunications) ['full-duplex]]) with bytes arriving in the same order they were sent. These connections, along with the objects and types used to represent them, are collectively termed [link beast.concepts.streams ['streams]]. The computer or device attached to the network is called a [@https://en.wikipedia.org/wiki/Host_(network) ['host]], and the program on the other end of an established connection is called a [@https://en.wikipedia.org/wiki/Peer-to-peer ['peer]].
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — A [@https://en.wikipedia.org/wiki/Computer_network ['network]] allows programs located anywhere to exchange information after opting-in to communications by establishing a [@https://en.wikipedia.org/wiki/Data_link ['connection]]. Data may be reliably transferred across a connection in both directions ([@https://en.wikipedia.org/wiki/Duplex_(telecommunications) ['full-duplex]]) with bytes arriving in the same order they were sent. These connections, along with the objects and types used to represent them, are collectively termed [link beast.concepts.streams ['streams]]. The computer or device attached to the network is called a [@https://en.wikipedia.org/wiki/Host_(network) ['host]], and the program on the other end of an established connection is called a [@https://en.wikipedia.org/wiki/Peer-to-peer ['peer]]. 820/8200 · 820 Needs editing (Needs rewriting)
3 string ID 22
	Source string description type: paragraph
	English To obtain the serialized next buffer sequence, call [link beast.ref.boost__beast__http__serializer.next `serializer::next`]. Then, call [link beast.ref.boost__beast__http__serializer.consume `serializer::consume`] to indicate the number of bytes consumed. This updates the next set of buffers to be returned, if any. `serializer::next` takes an error code parameter and invokes a visitor argument with the error code and buffer of unspecified type. In C++14 this is easily expressed with a generic lambda. The function [link beast.ref.boost__beast__http__serializer.is_done `serializer::is_done`] will return `true` when all the buffers have been produced. This C++14 example prints the buffers to standard output:
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — To obtain the serialized next buffer sequence, call [link beast.ref.boost__beast__http__serializer.next `serializer::next`]. Then, call [link beast.ref.boost__beast__http__serializer.consume `serializer::consume`] to indicate the number of bytes consumed. This updates the next set of buffers to be returned, if any. `serializer::next` takes an error code parameter and invokes a visitor argument with the error code and buffer of unspecified type. In C++14 this is easily expressed with a generic lambda. The function [link beast.ref.boost__beast__http__serializer.is_done `serializer::is_done`] will return `true` when all the buffers have been produced. This C++14 example prints the buffers to standard output: 714/7140 · 714 Needs editing (Needs rewriting)
3 string ID 20
	Source string description type: paragraph
	English This library offers programmers simple and performant models of HTTP messages and their associated operations including synchronous, asynchronous, and buffer-oriented parsing and serialization of messages in the HTTP/1 wire format using __Asio__. Specifically, the library provides:
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — This library offers programmers simple and performant models of HTTP messages and their associated operations including synchronous, asynchronous, and buffer-oriented parsing and serialization of messages in the HTTP/1 wire format using __Asio__. Specifically, the library provides: 282/2820 · 282 Needs editing (Needs rewriting)
3 string ID 17
	Source string description type: table title
	English Message
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — Message 7/100 · 7 Needs editing (Needs rewriting)
3 string ID 16
	Source string description type: list
	English * Receive the header first and body later.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — * Receive the header first and body later. 42/420 · 42 Needs editing (Needs rewriting)
3 string ID 18
	Source string description type: list
	English * [issue 3066] Fixed typecast warnings in `inflate_with_eb`
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — * [issue 3066] Fixed typecast warnings in `inflate_with_eb` 59/590 · 59 Needs editing (Needs rewriting)
3 string ID 20
	Source string description type: paragraph
	English The interface to this concept is intended to permit the following implementation strategies:
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — The interface to this concept is intended to permit the following implementation strategies: 92/920 · 92 Needs editing (Needs rewriting)
3 string ID 16
	Source string description type: heading
	English Associated Types
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — Associated Types 16/160 · 16 Needs editing (Needs rewriting)
3 string ID 14
	Source string description type: heading
	English Associated Types
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — Associated Types 16/160 · 16 Needs editing (Needs rewriting)
3 string ID 16
	Source string description type: paragraph
	English The general strategy used by the author to evaluate external libraries is as follows:
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — The general strategy used by the author to evaluate external libraries is as follows: 85/850 · 85 Needs editing (Needs rewriting)
3 string ID 17
	Source string description type: heading
	English Associated Types
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — Associated Types 16/160 · 16 Needs editing (Needs rewriting)
3 string ID 20
	Source string description type: list
	English * A body that does not entirely fit in memory. * A body produced incrementally from coroutine output. * A body represented by zero or more buffers already in memory. * A body whose size is not known ahead of time. * Body data generated dynamically from other threads. * Body data computed algorithmically.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — * A body that does not entirely fit in memory. * A body produced incrementally from coroutine output. * A body represented by zero or more buffers already in memory. * A body whose size is not known ahead of time. * Body data generated dynamically from other threads. * Body data computed algorithmically. 305/3050 · 305 Needs editing (Needs rewriting)
3 string ID 18
	Source string description type: heading
	English Associated Types
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — Associated Types 16/160 · 16 Needs editing (Needs rewriting)
26 string ID 26
	Source string description type: heading
	English Parser Options
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — Parser Options 14/140 · 14 Needs editing (Needs rewriting)
3 string ID 18
	Source string description type: paragraph
	English Stream concepts are based on named requirements in networking:
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — Stream concepts are based on named requirements in networking: 62/620 · 62 Needs editing (Needs rewriting)