Boost Beast Translation (zh_Hans) - English @ Boost-Weblate

Exit Zen

12 string ID 63
	Source string description type: paragraph

	English Here is our first attempt at declaring some message containers: 63/10000 · 63
12 string ID 49
	Source string description type: section title

	English Requirements 12/10000 · 12
12 string ID 21
	Source string description type: table cell

	English [link beast.ref.boost__beast__buffers_front `buffers_front`] 60/10000 · 60
12 string ID 78
	Source string description type: paragraph

	English The `tcp_stream` is designed as a replacement for [@boost:/doc/html/boost_asio/reference/ip__tcp/socket.html `net::ip::tcp::socket`]. Any program which currently uses a socket, can switch to a `tcp_stream` and achieve the features above (although some interfaces are different, see below). Networking now allows I/O objects to construct with any instance of __ExecutionContext__ or __Executor__ objects. Here we construct a stream which uses a particular I/O context to dispatch completion handlers: 499/10000 · 499
12 string ID 17
	Source string description type: table cell

	English [link beast.ref.boost__beast__file_posix `file_posix`] 54/10000 · 54
12 string ID 62
	Source string description type: paragraph

	English The following Boost.Asio methods can be used for loading a certificate or a certificate chain: 94/10000 · 94
12 string ID 44
	Source string description type: table cell

	English [link beast.ref.boost__beast__bind_handler `bind_handler`] 58/10000 · 58
12 string ID 68
	Source string description type: list

	English * For operations which complete immediately (i.e. without calling an 68/10000 · 68
12 string ID 53
	Source string description type: paragraph

	English This document refers to the three implementations above interchangeably and collectively as [*Networking] (or just ['networking]). The Boost.Asio and Asio flavors of Networking provide additional features not currently proposed for C++, but likely to appear in a future specification, such as: 293/10000 · 293
12 string ID 46
	Source string description type: table cell

	English [link beast.ref.boost__beast__buffered_read_stream `buffered_read_stream`] 74/10000 · 74
12 string ID 125
	Source string description type: paragraph

	English The __DynamicBuffer__ concept defines a resizable buffer sequence interface. Algorithms may be expressed in terms of dynamic buffers when the memory requirements are not known ahead of time, for example when reading an HTTP message from a stream. Beast provides a well-rounded collection of dynamic buffer types such as [link beast.ref.boost__beast__buffers_adaptor `buffers_adaptor`], [link beast.ref.boost__beast__flat_buffer `flat_buffer`], [link beast.ref.boost__beast__multi_buffer `multi_buffer`], and [link beast.ref.boost__beast__static_buffer `static_buffer`]. The following function reads data from a [link beast.ref.boost__beast__tcp_stream `tcp_stream`] into a dynamic buffer until it encountering a newline character, using [@boost:/doc/html/boost_asio/reference/buffers_iterator.html `net::buffers_iterator`] to treat the contents of the buffer as a range of characters: 884/10000 · 884
12 string ID 63
	Source string description type: paragraph

	English The following is an example that can read an HTTP response from such a server: 78/10000 · 78
12 string ID 21
	Source string description type: table cell

	English __AsyncReadStream__ 19/10000 · 19
12 string ID 73
	Source string description type: paragraph

	English Here we forward declare the composed operation type, and provide the definition of the initiation function object. They are placed in the `detail` namespace since they should not be public: 189/10000 · 189
12 string ID 25
	Source string description type: table cell

	English [path_link example/http/client/async-local/http_client_async_local.cpp http_client_async_local.cpp] 99/10000 · 99
12 string ID 75
	Source string description type: table cell

	English This response has a [@https://tools.ietf.org/html/rfc7231#section-6 200 status code] meaning the operation requested completed successfully. The obsolete reason phrase is "OK". It specifies HTTP version 1.1, and contains a body 13 octets in size with the text "Hello, world!". 276/10000 · 276
12 string ID 74
	Source string description type: paragraph

	English Interfaces for operating on HTTP messages are structured into several layers. The highest level provides ease of use, while lower levels provide progressively more control, options, and flexibility. At the lowest level customization points are provided, where user defined types can replace parts of the implementation. The layers are arranged thusly: 351/10000 · 351
12 string ID 51
	Source string description type: paragraph

	English The container offers value semantics including move and copy if supported by __Body__ and __Fields__. User defined template function parameters can accept any message, or can use partial specialization to accept just requests or responses. The default __fields__ is a provided associative container using the standard allocator and supporting modification and inspection of fields. As per __rfc7230__, a non-case-sensitive comparison is used for field names. User defined types for fields are possible. The `Body` type determines the type of the container used to represent the body as well as the algorithms for transferring buffers to and from the container. The library comes with a collection of common body types. As with fields, user defined body types are possible. 772/10000 · 772
12 string ID 29
	Source string description type: table code

	English /// An HTTP/1 parser for producing a message. template< bool isRequest, // `true` to parse an HTTP request class Body, // The Body type for the resulting message class Allocator = std::allocator<char>> // The type of allocator for the header class parser : public basic_parser<...>; 334/10000 · 334
12 string ID 47
	Source string description type: table cell

	English A buffer sequence representing the CRLF (`"\r\n"`) delimiter. This class is used when the caller desires to emit the chunk body in two or more individual stream operations. 172/10000 · 172

Shortcut	Action
`?`	Open available keyboard shortcuts.
`Alt` + `Home`	Navigate to the first translation in the current search.
`Alt` + `End`	Navigate to the last translation in the current search.
`Alt` + `PageUp` or `Ctrl` + `↑` or `Alt` + `↑` or `Cmd` + `↑` or	Navigate to the previous translation in the current search.
`Alt` + `PageDown` or `Ctrl` + `↓` or `Alt` + `↓` or `Cmd` + `↓` or	Navigate to the next translation in the current search.
`Ctrl` + `Enter` or `Cmd` + `Enter`	Submit current form; this works the same as pressing Save and continue while editing translation.
`Ctrl` + `Shift` + `Enter` or `Cmd` + `Shift` +`Enter`	Unmark translation as Needing edit and submit it.
`Alt` + `Enter` or `Option` + `Enter`	Submit the string as a suggestion; this works the same as pressing Suggest while editing translation.
`Ctrl` + `E` or `Cmd` + `E`	Focus on translation editor.
`Ctrl` + `U` or `Cmd` + `U`	Focus on comment editor.
`Ctrl` + `M` or `Cmd` + `M`	Shows Automatic suggestions tab.
`Ctrl` + `1` to `Ctrl` + `9` or `Cmd` + `1` to `Cmd` + `9`	Copies placeable of a given number from source string.
`Ctrl` + `M` followed by `1` to `9` or `Cmd` + `M` followed by `1` to `9`	Copy the machine translation of a given number to current translation.
`Ctrl` + `I` followed by `1` to `9` or `Cmd` + `I` followed by `1` to `9`	Ignore one item in the list of failing checks.
`Ctrl` + `J` or `Cmd` + `J`	Shows the Nearby strings tab.
`Ctrl` + `S` or `Cmd` + `S`	Focus on search field.
`Ctrl` + `O` or `Cmd` + `O`	Copy the source string.
`Ctrl` + `Y` or `Cmd` + `Y`	Toggle the Needs editing checkbox.
`→`	Browse the next translation string.
`←`	Browse the previous translation string.