Source strings

43 Strings
100%
Browse Translate
1,446 Words
100%
9,255 Characters
100%
This translation is being used as source strings within this component.

Strings status

Strings Words Characters
43 1,446 9,255
All strings Browse Translate Zen
43 1,446 9,255
Read-only strings Browse Translate Zen

Summary

Project website www.boost.org
Instructions for translators

Please translate the Boost.Beast documentation. Maintain technical accuracy and follow exact formatting conventions.
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses monolingual files.
  • The translation base language can not be edited.
Source code repository git@github.com:CppDigest/beast.git
Repository branch local-zh_Hans
Last commit in Weblate Added translation using Weblate (Chinese (Simplified Han script)) 2d625eb
User avatar admin authored 05/25/2026
Weblate repository https://boost-weblate.cloud/git/boost-beast-documentation-zh_Hans/doc-qbk-version-qbk/
File mask doc/qbk/08_design/1_http_message_*.qbk
Monolingual base language file doc/qbk/08_design/1_http_message.qbk
Translation file Download doc/qbk/08_design/1_http_message.qbk
Last change May 25, 2026, 5:29 p.m.
Last change made by None
Language English
Language code en
Text direction Left to right
Case sensitivity Case-sensitive
Number of speakers 1,728,473,503
Number of plurals 2
Plural type One/other
Plurals Singular 1
Plural 0, 2, 3, 4, 5, 6, 7, 8, 9, 10, …
Plural formula n != 1
05/29/2026

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 43 1,446 9,255
Translated 100% 43 100% 1,446 100% 9,255
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 43 100% 1,446 100% 9,255
Failing checks 0% 0 0% 0 0% 0
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 45 changes
JunJulAugSepOctNovDecJanFebMarAprMay

Quick numbers

1,446
Hosted words
43
Hosted strings
100%
Translated
1
Contributors
and previous 30 days

Trends of last 30 days

+100%
Hosted words
—
+100%
Hosted strings
—
+100%
Translated
—
+100%
Contributors
—
User avatar admin

Resource updated
Parsing of the “doc/qbk/08_design/1_http_message.qbk” file was enforced. 05/25/2026
User avatar admin

Resource updated
File “doc/qbk/08_design/1_http_message.qbk” was added. 05/25/2026
User avatar admin

String added in the repository
In conclusion, this representation for the message container is well thought out, provides comprehensive flexibility, and avoids the necessity of defining additional traits classes. User declarations of functions that accept headers or messages as parameters are easy to write in a variety of ways to accomplish different results, without forcing cumbersome SFINAE declarations everywhere.
In conclusion, this representation for the message container is well thought out, provides comprehensive flexibility, and avoids the necessity of defining additional traits classes. User declarations of functions that accept headers or messages as parameters are easy to write in a variety of ways to accomplish different results, without forcing cumbersome SFINAE declarations everywhere.
05/25/2026
User avatar admin

String added in the repository
This container is also capable of representing complete HTTP/2 messages. Not because it was explicitly designed for, but because the IETF wanted to preserve message compatibility with HTTP/1. Aside from version specific fields such as Connection, the contents of HTTP/1 and HTTP/2 messages are identical even though their serialized representation is considerably different. The message model presented in this library is ready for HTTP/2.
This container is also capable of representing complete HTTP/2 messages. Not because it was explicitly designed for, but because the IETF wanted to preserve message compatibility with HTTP/1. Aside from version specific fields such as Connection, the contents of HTTP/1 and HTTP/2 messages are identical even though their serialized representation is considerably different. The message model presented in this library is ready for HTTP/2.
05/25/2026
User avatar admin

String added in the repository
response<file_body> res; ```
response<file_body> res; ```
05/25/2026
User avatar admin

String added in the repository
This allows concise specification for the common cases, while allowing for maximum customization for edge cases: ``` request<string_body> req;
This allows concise specification for the common cases, while allowing for maximum customization for edge cases: ``` request<string_body> req;
05/25/2026
User avatar admin

String added in the repository
/// An HTTP response template<class Body, class Fields = fields> using response = message<false, Body, Fields>; ```
/// An HTTP response template<class Body, class Fields = fields> using response = message<false, Body, Fields>; ```
05/25/2026
User avatar admin

String added in the repository
/// An HTTP request template<class Body, class Fields = fields> using request = message<true, Body, Fields>;
/// An HTTP request template<class Body, class Fields = fields> using request = message<true, Body, Fields>;
05/25/2026
User avatar admin

String added in the repository
/// An HTTP message template<bool isRequest, class Body, class Fields = fields> struct message;
/// An HTTP message template<bool isRequest, class Body, class Fields = fields> struct message;
05/25/2026
User avatar admin

String added in the repository
``` /// An HTTP header template<bool isRequest, class Body, class Fields = fields> struct header;
``` /// An HTTP header template<bool isRequest, class Body, class Fields = fields> struct header;
05/25/2026
Browse all translation changes