Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
Boost Json Documentation / Doc / Library Detail (adoc) 0% 71 645 6,767 70
Boost Json Documentation / Doc / Pages / Allocators / Background (adoc) 0% 23 499 3,458 23
Boost Json Documentation / Doc / Pages / Allocators / Overview (adoc) 0% 5 49 380 5
Boost Json Documentation / Doc / Pages / Allocators / Storage Ptr (adoc) 0% 63 983 6,995 63
Boost Json Documentation / Doc / Pages / Allocators / Uses Allocator (adoc) 0% 10 138 1,059 10
Boost Json Documentation / Doc / Pages / Benchmarks (adoc) 0% 126 635 6,820 126
Boost Json Documentation / Doc / Pages / Comparison (adoc) 0% 35 375 2,989 35
Boost Json Documentation / Doc / Pages / Conversion / Alloc (adoc) 0% 7 171 1,266 7
Boost Json Documentation / Doc / Pages / Conversion / Context (adoc) 0% 21 681 4,674 21
Boost Json Documentation / Doc / Pages / Conversion / Custom (adoc) 0% 19 453 3,155 19
Boost Json Documentation / Doc / Pages / Conversion / Direct (adoc) 0% 6 217 1,576 6
Boost Json Documentation / Doc / Pages / Conversion / Forward (adoc) 0% 5 136 957 5
Boost Json Documentation / Doc / Pages / Conversion / Guidelines (adoc) 0% 6 278 1,780 6
Boost Json Documentation / Doc / Pages / Conversion / Nothrow (adoc) 0% 8 262 1,825 8
Boost Json Documentation / Doc / Pages / Conversion / Overview (adoc) 0% 59 549 4,143 4 55
Boost Json Documentation / Doc / Pages / Definitions (adoc) 0% 3 66 3,959 3
Boost Json Documentation / Doc / Pages / Dom / Array (adoc) 0% 8 175 1,243 8
Boost Json Documentation / Doc / Pages / Dom / Init Lists (adoc) 0% 11 226 1,507 11
Boost Json Documentation / Doc / Pages / Dom / Nested Access (adoc) 0% 5 90 719 5
Boost Json Documentation / Doc / Pages / Dom / Numbers (adoc) 0% 12 324 2,141 12
Boost Json Documentation / Doc / Pages / Dom / Object (adoc) 0% 16 296 2,049 16
Boost Json Documentation / Doc / Pages / Dom / Overview (adoc) 0% 17 144 1,085 17
Boost Json Documentation / Doc / Pages / Dom / String (adoc) 0% 30 411 2,965 30
Boost Json Documentation / Doc / Pages / Dom / Value (adoc) 0% 115 676 6,586 115
Boost Json Documentation / Doc / Pages / Examples (adoc) 0% 5 7 54 5
Boost Json Documentation / Doc / Pages / Faq (adoc) 25% 6 156 986 8
Boost Json Documentation / Doc / Pages / Io / Overview (adoc) 0% 4 37 303 4
Boost Json Documentation / Doc / Pages / Io / Parsing (adoc) 0% 61 1,191 8,148 61
Boost Json Documentation / Doc / Pages / Io / Serializing (adoc) 0% 17 244 1,779 17
Boost Json Documentation / Doc / Pages / Main (adoc) 0% 6 43 609 6
Boost Json Documentation / Doc / Pages / Quick Look (adoc) 0% 31 865 5,512 31
Boost Json Documentation / Doc / Pages / Reference (adoc) 0% 12 145 1,627 12
Glossary Boost Json Translation (zh_Hans)

Summary

Project website www.boost.org
Instructions for translators

Please translate the Boost.Json documentation. Maintain technical accuracy and follow exact formatting conventions.
Project maintainers1 User avatar william
Language Chinese (Simplified Han script)
Language code zh_Hans
Text direction Left to right
Case sensitivity Case-insensitive
Number of speakers 1,286,444,445
04/19/2026

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 825 11,222 89,559
Translated 1% 2 1% 55 1% 443
Needs editing 99% 819 99% 11,141 99% 88,955
Read-only 0% 0 0% 0 0% 0
Failing checks 99% 820 99% 11,195 99% 89,397
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 1% 4 1% 26 1% 161
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 0 changes
AprMayJunJulAugSepOctNovDecJanFebMar

Quick numbers

11,222
Hosted words
825
Hosted strings
1%
Translated
1
Contributors
and previous 30 days

Trends of last 30 days

+100%
Hosted words
—
+100%
Hosted strings
—
+1%
Translated
—
+100%
Contributors
—
User avatar william

Resource updated
File “doc/pages/allocators/background_zh_Hans.adoc” was added. 04/19/2026
User avatar william

String added in the repository
Boost.JSON solves this problem by introducing a new smart pointer called <<ref_storage_ptr>> which builds upon {cpp}17's memory allocation interfaces, accomplishing the goals above. As a result, libraries which use this type compose more easily and enjoy faster compilation, as member functions for containers which use the type can be defined out-of-line.
Boost.JSON solves this problem by introducing a new smart pointer called <<ref_storage_ptr>> which builds upon {cpp}17's memory allocation interfaces, accomplishing the goals above. As a result, libraries which use this type compose more easily and enjoy faster compilation, as member functions for containers which use the type can be defined out-of-line.
04/19/2026
User avatar william

String added in the repository
`T` interoperates with code already using `std::pmr`
`T` interoperates with code already using `std::pmr`
04/19/2026
User avatar william

String added in the repository
`T` supports both reference semantics or shared ownership
`T` supports both reference semantics or shared ownership
04/19/2026
User avatar william

String added in the repository
`T` references a {ref_memory_resource}
`T` references a {ref_memory_resource}
04/19/2026
User avatar william

String added in the repository
`T` is not a class template
`T` is not a class template
04/19/2026
User avatar william

String added in the repository
We would like an allocator model using a single type `T` with the following properties:
We would like an allocator model using a single type `T` with the following properties:
04/19/2026
User avatar william

String added in the repository
Problem Statement
Problem Statement
04/19/2026
User avatar william

String added in the repository
Workarounds for this problem are worse than the problem itself. The library could return a pair with the vector and `std::unique_ptr<std::pmr::memory_resource>` which the caller must manage. Or the library could change its function signatures to accept a {ref_memory_resource}``*`` provided by the caller, where the library also makes public the desired memory resources (`my_resource` above).
Workarounds for this problem are worse than the problem itself. The library could return a pair with the vector and `std::unique_ptr<std::pmr::memory_resource>` which the caller must manage. Or the library could change its function signatures to accept a {ref_memory_resource}``*`` provided by the caller, where the library also makes public the desired memory resources (`my_resource` above).
04/19/2026
User avatar william

String added in the repository
This can be worked around by declaring the container to use a custom allocator (perhaps using a `std::shared_ptr< std::pmr::memory_resource >` as a data member). This hinders library composition; every library now exports unique, incompatible container types. A raw memory resource pointer is also easy to misuse:
This can be worked around by declaring the container to use a custom allocator (perhaps using a `std::shared_ptr< std::pmr::memory_resource >` as a data member). This hinders library composition; every library now exports unique, incompatible container types. A raw memory resource pointer is also easy to misuse:
04/19/2026
Browse all changes for this language