Search for has:check @ Boost-Weblate

19 strings / 731 words

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.

Translation	Source string	Target string
Boost Beast Translation (zh_Hans)/Doc / Qbk / 05 Http Examples / Http Examples (qbk) — Chinese (Simplified Han script)	These examples in this section are working functions that may be found in the examples directory. They demonstrate the usage of the library for a variety of scenarios.	These examples in this section are working functions that may be found in the examples directory. They demonstrate the usage of the library for a variety of scenarios.
Boost Beast Translation (zh_Hans)/Doc / Qbk / 05 Http Examples / Http Examples (qbk) — Chinese (Simplified Han script)	Change Body Type __example__	Change Body Type __example__
Boost Beast Translation (zh_Hans)/Doc / Qbk / 05 Http Examples / Http Examples (qbk) — Chinese (Simplified Han script)	Sophisticated servers may wish to defer the choice of the Body template type until after the header is available. Then, a body type may be chosen depending on the header contents. For example, depending on the verb, target path, or target query parameters. To accomplish this, a parser is declared to read in the header only, using a trivial body type such as [link beast.ref.boost__beast__http__empty_body `empty_body`]. Then, a new parser is constructed from this existing parser where the body type is conditionally determined by information from the header or elsewhere.	Sophisticated servers may wish to defer the choice of the Body template type until after the header is available. Then, a body type may be chosen depending on the header contents. For example, depending on the verb, target path, or target query parameters. To accomplish this, a parser is declared to read in the header only, using a trivial body type such as [link beast.ref.boost__beast__http__empty_body `empty_body`]. Then, a new parser is constructed from this existing parser where the body type is conditionally determined by information from the header or elsewhere.
Boost Beast Translation (zh_Hans)/Doc / Qbk / 05 Http Examples / Http Examples (qbk) — Chinese (Simplified Han script)	This example illustrates how a server may make the commitment of a body type depending on the method verb:	This example illustrates how a server may make the commitment of a body type depending on the method verb:
Boost Beast Translation (zh_Hans)/Doc / Qbk / 05 Http Examples / Http Examples (qbk) — Chinese (Simplified Han script)	Expect 100-continue (Client) __example__	Expect 100-continue (Client) __example__
Boost Beast Translation (zh_Hans)/Doc / Qbk / 05 Http Examples / Http Examples (qbk) — Chinese (Simplified Han script)	The Expect field with the value "100-continue" in a request is special. It indicates that the after sending the message header, a client desires an immediate informational response before sending the message body, which presumably may be expensive to compute or large. This behavior is described in [@https://tools.ietf.org/html/rfc7231#section-5.1.1 rfc7231 section 5.1.1]. Invoking the 100-continue behavior is implemented easily in a client by constructing a __serializer__ to send the header first, then receiving the server response, and finally conditionally send the body using the same serializer instance. A synchronous, simplified version (no timeout) of this client action looks like this:	The Expect field with the value "100-continue" in a request is special. It indicates that the after sending the message header, a client desires an immediate informational response before sending the message body, which presumably may be expensive to compute or large. This behavior is described in [@https://tools.ietf.org/html/rfc7231#section-5.1.1 rfc7231 section 5.1.1]. Invoking the 100-continue behavior is implemented easily in a client by constructing a __serializer__ to send the header first, then receiving the server response, and finally conditionally send the body using the same serializer instance. A synchronous, simplified version (no timeout) of this client action looks like this:
Boost Beast Translation (zh_Hans)/Doc / Qbk / 05 Http Examples / Http Examples (qbk) — Chinese (Simplified Han script)	Expect 100-continue (Server) __example__	Expect 100-continue (Server) __example__
Boost Beast Translation (zh_Hans)/Doc / Qbk / 05 Http Examples / Http Examples (qbk) — Chinese (Simplified Han script)	The Expect field with the value "100-continue" in a request is special. It indicates that the after sending the message header, a client desires an immediate informational response before sending the message body, which presumably may be expensive to compute or large. This behavior is described in [@https://tools.ietf.org/html/rfc7231#section-5.1.1 rfc7231 section 5.1.1]. Handling the Expect field can be implemented easily in a server by constructing a __parser__ to read the header first, then send an informational HTTP response, and finally read the body using the same parser instance. A synchronous version of this server action looks like this:	The Expect field with the value "100-continue" in a request is special. It indicates that the after sending the message header, a client desires an immediate informational response before sending the message body, which presumably may be expensive to compute or large. This behavior is described in [@https://tools.ietf.org/html/rfc7231#section-5.1.1 rfc7231 section 5.1.1]. Handling the Expect field can be implemented easily in a server by constructing a __parser__ to read the header first, then send an informational HTTP response, and finally read the body using the same parser instance. A synchronous version of this server action looks like this:
Boost Beast Translation (zh_Hans)/Doc / Qbk / 05 Http Examples / Http Examples (qbk) — Chinese (Simplified Han script)	HEAD request (Client) __example__	HEAD request (Client) __example__
Boost Beast Translation (zh_Hans)/Doc / Qbk / 05 Http Examples / Http Examples (qbk) — Chinese (Simplified Han script)	The [@https://tools.ietf.org/html/rfc7231#section-4.3.2 HEAD request] method indicates to the server that the client wishes to receive the entire header that would be delivered if the method was GET, except that the body is omitted. When a client wishes to receive the response to a HEAD request, it is necessary to inform the parser not to expect a body. This is done by calling [link beast.ref.boost__beast__http__basic_parser.skip `basic_parser::skip`] with the value `true`, as shown in this example:	The [@https://tools.ietf.org/html/rfc7231#section-4.3.2 HEAD request] method indicates to the server that the client wishes to receive the entire header that would be delivered if the method was GET, except that the body is omitted. When a client wishes to receive the response to a HEAD request, it is necessary to inform the parser not to expect a body. This is done by calling [link beast.ref.boost__beast__http__basic_parser.skip `basic_parser::skip`] with the value `true`, as shown in this example:
Boost Beast Translation (zh_Hans)/Doc / Qbk / 05 Http Examples / Http Examples (qbk) — Chinese (Simplified Han script)	HEAD response (Server) __example__	HEAD response (Server) __example__
Boost Beast Translation (zh_Hans)/Doc / Qbk / 05 Http Examples / Http Examples (qbk) — Chinese (Simplified Han script)	When a server receives a [@https://tools.ietf.org/html/rfc7231#section-4.3.2 HEAD request], the response should contain the entire header that would be delivered if the method was GET, except that the body is omitted.	When a server receives a [@https://tools.ietf.org/html/rfc7231#section-4.3.2 HEAD request], the response should contain the entire header that would be delivered if the method was GET, except that the body is omitted.
Boost Beast Translation (zh_Hans)/Doc / Qbk / 05 Http Examples / Http Examples (qbk) — Chinese (Simplified Han script)	HTTP Relay __example__	HTTP Relay __example__
Boost Beast Translation (zh_Hans)/Doc / Qbk / 05 Http Examples / Http Examples (qbk) — Chinese (Simplified Han script)	An HTTP proxy acts as a relay between client and server. The proxy reads a request from the client and sends it to the server, possibly adjusting some of the headers and representation of the body along the way. Then, the proxy reads a response from the server and sends it back to the client, also with the possibility of changing the headers and body representation.	An HTTP proxy acts as a relay between client and server. The proxy reads a request from the client and sends it to the server, possibly adjusting some of the headers and representation of the body along the way. Then, the proxy reads a response from the server and sends it back to the client, also with the possibility of changing the headers and body representation.
Boost Beast Translation (zh_Hans)/Doc / Qbk / 05 Http Examples / Http Examples (qbk) — Chinese (Simplified Han script)	The example that follows implements a synchronous HTTP relay. It uses a fixed size buffer, to avoid reading in the entire body so that the upstream connection sees a header without unnecessary latency. This example brings together all of the concepts discussed so far, it uses both a __serializer__ and a __parser__ to achieve its goal:	The example that follows implements a synchronous HTTP relay. It uses a fixed size buffer, to avoid reading in the entire body so that the upstream connection sees a header without unnecessary latency. This example brings together all of the concepts discussed so far, it uses both a __serializer__ and a __parser__ to achieve its goal:
Boost Beast Translation (zh_Hans)/Doc / Qbk / 05 Http Examples / Http Examples (qbk) — Chinese (Simplified Han script)	Send Child Process Output __example__	Send Child Process Output __example__
Boost Beast Translation (zh_Hans)/Doc / Qbk / 05 Http Examples / Http Examples (qbk) — Chinese (Simplified Han script)	Sometimes it is necessary to send a message whose body is not conveniently described by a single container. For example, when implementing an HTTP relay function a robust implementation needs to present body buffers individually as they become available from the downstream host. These buffers should be fixed in size, otherwise creating the unnecessary and inefficient burden of reading the complete message body before forwarding it to the upstream host.	Sometimes it is necessary to send a message whose body is not conveniently described by a single container. For example, when implementing an HTTP relay function a robust implementation needs to present body buffers individually as they become available from the downstream host. These buffers should be fixed in size, otherwise creating the unnecessary and inefficient burden of reading the complete message body before forwarding it to the upstream host.
Boost Beast Translation (zh_Hans)/Doc / Qbk / 05 Http Examples / Http Examples (qbk) — Chinese (Simplified Han script)	To enable these use-cases, the body type __buffer_body__ is provided. This body uses a caller-provided pointer and size instead of an owned container. To use this body, instantiate an instance of the serializer and fill in the pointer and size fields before calling a stream write function.	To enable these use-cases, the body type __buffer_body__ is provided. This body uses a caller-provided pointer and size instead of an owned container. To use this body, instantiate an instance of the serializer and fill in the pointer and size fields before calling a stream write function.
Boost Beast Translation (zh_Hans)/Doc / Qbk / 05 Http Examples / Http Examples (qbk) — Chinese (Simplified Han script)	This example reads from a child process and sends the output back in an HTTP response. The output of the process is sent as it becomes available:	This example reads from a child process and sends the output back in an HTTP response. The output of the process is sent as it becomes available: