CppDigest · whisper67265 · May 13, 2026 · May 13, 2026 · May 13, 2026 · May 13, 2026
diff --git a/doc/library-detail_zh_Hans.adoc b/doc/library-detail_zh_Hans.adoc
@@ -1,31 +1,31 @@
-https://www.boost.org/doc/libs/release/libs/json/[image:https://raw.githubusercontent.com/CPPAlliance/json/master/doc/images/repo-logo-3.png[Boost.JSON]]
+https://www.boost.org/doc/libs/release/libs/json/[image:https://raw.githubusercontent.com/CPPAlliance/json/master/doc/images/repo-logo-3.png[Boost.12312312312]]
 
-[width="100%", cols="12%,43%,45%", options="header"]
+[width="100%",cols="12%,43%,45%",options="header",]
 |===
-|分支 |https://github.com/boostorg/json/tree/master[`master`]
+|Branch |https://github.com/boostorg/json/tree/master[`master`]
 |https://github.com/boostorg/json/tree/develop[`develop`]
 |https://azure.microsoft.com/en-us/services/devops/pipelines/[Azure]
-|https://vinniefalco.visualstudio.com/json/_build/latest?definitionId=5&amp;branchName=master[image:https://img.shields.io/azure-devops/build/vinniefalco/2571d415-8cc8-4120-a762-c03a8eda0659/8/master[构建状态]]
-|https://vinniefalco.visualstudio.com/json/_build/latest?definitionId=8&amp;branchName=develop[image:https://img.shields.io/azure-devops/build/vinniefalco/2571d415-8cc8-4120-a762-c03a8eda0659/8/develop[构建状态]]
+|https://vinniefalco.visualstudio.com/json/_build/latest?definitionId=5&branchName=master[image:https://img.shields.io/azure-devops/build/vinniefalco/2571d415-8cc8-4120-a762-c03a8eda0659/8/master[Build
+状态]] |https://vinniefalco.visualstudio.com/json/_build/latest?definitionId=8&amp;branchName=develop[image:https://img.shields.io/azure-devops/build/vinniefalco/2571d415-8cc8-4120-a762-c03a8eda0659/8/develop[构建状态]]
 
-|文档
-|https://www.boost.org/doc/libs/master/libs/json/[image:https://img.shields.io/badge/docs-master-brightgreen.svg[文档]]
-|https://www.boost.org/doc/libs/develop/libs/json/[image:https://img.shields.io/badge/docs-develop-brightgreen.svg[文档]]
+|Docs
+|https://www.boost.org/doc/libs/master/libs/json/[image:https://img.shields.io/badge/docs-master-brightgreen.svg[Documentation]]
+|https://www.boost.org/doc/libs/develop/libs/json/[image:https://img.shields.io/badge/docs-develop-brightgreen.svg[Documentation]]
 
 |https://drone.io/[Drone]
-|https://drone.cpp.al/boostorg/json[image:https://drone.cpp.al/api/badges/boostorg/json/status.svg?ref=refs/heads/master[构建状态]]
-|https://drone.cpp.al/boostorg/json[image:https://drone.cpp.al/api/badges/boostorg/json/status.svg?ref=refs/heads/develop[构建状态]]
+|https://drone.cpp.al/boostorg/json[image:https://drone.cpp.al/api/badges/boostorg/json/status.svg?ref=refs/heads/master[Build
+状态]] |https://drone.cpp.al/boostorg/json[image:https://drone.cpp.al/api/badges/boostorg/json/status.svg?ref=refs/heads/develop[构建状态]]
 
-|测试矩阵
-|http://www.boost.org/development/tests/master/developer/json.html[image:https://img.shields.io/badge/matrix-master-brightgreen.svg[测试矩阵]]
-|http://www.boost.org/development/tests/develop/developer/json.html[image:https://img.shields.io/badge/matrix-develop-brightgreen.svg[测试矩阵]]
+|Matrix
+|http://www.boost.org/development/tests/master/developer/json.html[image:https://img.shields.io/badge/matrix-master-brightgreen.svg[Matrix]]
+|http://www.boost.org/development/tests/develop/developer/json.html[image:https://img.shields.io/badge/matrix-develop-brightgreen.svg[Matrix]]
 
-|模糊测试 |—
-|https://github.com/boostorg/json/actions?query=workflow%3Afuzz+branch%3Adevelop[image:https://github.com/boostorg/json/workflows/fuzz/badge.svg?branch=develop[模糊测试]]
+|Fuzzing |—
+|https://github.com/boostorg/json/actions?query=workflow%3Afuzz+branch%3Adevelop[image:https://github.com/boostorg/json/workflows/fuzz/badge.svg?branch=develop[fuzz]]
 
 |https://ci.appveyor.com/[Appveyor]
-|https://ci.appveyor.com/project/vinniefalco/cppalliance-json/branch/master[image:https://ci.appveyor.com/api/projects/status/8csswcnmfm798203?branch=master&amp;svg=true[构建状态]]
-|https://ci.appveyor.com/project/vinniefalco/cppalliance-json/branch/develop[image:https://ci.appveyor.com/api/projects/status/8csswcnmfm798203?branch=develop&amp;svg=true[构建状态]]
+|https://ci.appveyor.com/project/vinniefalco/cppalliance-json/branch/master[image:https://ci.appveyor.com/api/projects/status/8csswcnmfm798203?branch=master&svg=true[Build
+状态]] |https://ci.appveyor.com/project/vinniefalco/cppalliance-json/branch/develop[image:https://ci.appveyor.com/api/projects/status/8csswcnmfm798203?branch=develop&amp;svg=true[构建状态]]
 
 |https://codecov.io[codecov.io]
 |https://codecov.io/gh/boostorg/json/branch/master[image:https://codecov.io/gh/boostorg/json/branch/master/graph/badge.svg[codecov]]
@@ -57,7 +57,8 @@ Boost.JSON 提供以下特性：
 === 要求
 
 * 仅需 C++11
-* 可链接预构建的静态或动态 Boost 库，也可使用纯头文件方式（见下文）。
+* 可链接预构建的静态或动态 Boost 库，也可使用纯头文件方式
+（见下文）
 * Supports -fno-exceptions（可自动检测）
 
 该库在其接口中大量依赖以下众所周知的 C++ 类型（以下称为 _standard types_）：

diff --git a/doc/pages/allocators/background_zh_Hans.adoc b/doc/pages/allocators/background_zh_Hans.adoc
@@ -8,8 +8,7 @@ file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
 Official repository: https://github.com/boostorg/json
 ////
 
-= 背景
-C++中分配器的第一个版本定义了名为{req_Allocator}的要求，并将每个标准容器设计为以分配器类型为模板参数的类模板。例如，以下是 {std_vector} 的声明：
+= 背景 C++中分配器的第一个版本定义了名为{req_Allocator}的要求，并将每个标准容器设计为以分配器类型为模板参数的类模板。例如，以下是 {std_vector} 的声明：
 
 [source]
 ----
@@ -28,9 +27,10 @@ include::../../../test/doc_background.cpp[tag=doc_background_2,indent=0]
 * 容器必须是一个类模板。
 * 在元素类型上参数化分配器的方式显得笨拙。
 * 分配器特征机制（尤其是 POCCA 和 POCMA）复杂且容易出错。
-
 使用多种分配器类型的基于分配器的程序会引发更多的函数模板实例化，且通常编译速度更慢，因为类模板的函数定义必须在所有调用点可见。
 
+Allocator-based programs which use multiple allocator types incur a greater number of function template instantiations and are generally slower to compile because class template function definitions must be visible at all call sites.
+
 == 多态分配器
 
 {cpp}17通过引入一个名为 {ref_memory_resource} 的抽象接口来表示底层分配操作，从而改进分配器模型。该接口未在元素类型上参数化，且无特征：

diff --git a/doc/pages/allocators/overview_zh_Hans.adoc b/doc/pages/allocators/overview_zh_Hans.adoc
@@ -15,8 +15,6 @@ Official repository: https://github.com/boostorg/json
 
 :leveloffset: +1
 
-include::background.adoc[]
-include::storage_ptr.adoc[]
-include::uses_allocator.adoc[]
+include::background.adoc[] include::storage_ptr.adoc[] include::uses_allocator.adoc[]
 
 :leveloffset: -1
diff --git a/doc/pages/allocators/storage_ptr_zh_Hans.adoc b/doc/pages/allocators/storage_ptr_zh_Hans.adoc
@@ -8,49 +8,59 @@ file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
 Official repository: https://github.com/boostorg/json
 ////
 
-= `storage_ptr`
-本库中的可变长度容器均使用动态分配的内存来存储其内容。调用方可通过在特定构造函数和函数参数列表中指定 <<ref_storage_ptr>> ，以控制所使用的内存分配策略。<<ref_storage_ptr>> 具有以下特性：
+= `storage_ptr` 本库中的可变长度容器均使用动态分配的内存来存储其内容。调用方可通过在特定构造函数和函数参数列表中指定 <<ref_storage_ptr>> ，以控制所使用的内存分配策略。<<ref_storage_ptr>> 具有以下特性：
 
 * 存储指针始终指向一个有效的、类型擦除后的 {ref_memory_resource}。
+以下是使用该库时所有与分配相关的类型和函数列表：
 
 * 默认构造的存储指针引用 <<default_memory_resource,default resource>>（默认资源），这是一个由实现定义的实例，始终使用等效于全局 operator new 和 operator delete 的方式。
+.函数与类型 |=== |Name|描述
 
 * 从 {ref_memory_resource} 或 {ref_polymorphic_allocator} 构造的存储指针不获取所有权；调用方负责确保资源的生命周期持续到不再被引用为止。
+{ref_polymorphic_allocator} do not acquire ownership; the caller is responsible for ensuring that the lifetime of the resource extends until it is no longer referenced.
 
 * 通过 <<ref_make_shared_resource>> 获取的存储指针会获得对内存资源的共享所有权；该资源的生命周期将延长，直至所有该存储指针的副本均被销毁。
+ownership of the memory resource; the lifetime of the resource is extended until all copies of the storage pointer are destroyed.
 
 * 存储指针在对资源进行类型擦除之前会记录 <<ref_is_deallocate_trivial>> 的值，从而允许在运行时查询该值。
+before type-erasing the resource, allowing the value to be queried at run-time.
 
-以下是使用该库时所有与分配相关的类型和函数列表：
+This lists all of the allocation-related types and functions available when using the library:
 
-.函数与类型
+.Functions and Types
 |===
-|Name|描述
+|Name|Description
 
 | <<ref_get_null_resource>>
-| 返回一个指向内存资源实例的指针，该实例在分配内存时总是抛出异常。此机制用于确保解析或容器操作不会进行动态内存分配，从而维持该不变性。
+| Returns a pointer to a memory resource instance which always throws an
+exception upon allocation. This is used to to achieve the invariant that no parsing or container operation will dynamically allocate memory.
 
 | <<ref_is_deallocate_trivial>>
-| 一个自定义点，允许内存资源类型表明其 deallocate 调用是平凡的。
+| A customization point allowing a memory resource type to indicate that calls
+to deallocate are trivial.
 
 | <<ref_make_shared_resource>>
-| 一个返回智能指针的函数，该智能指针对新分配的内存资源具有共享所有权。
+| A function returning a smart pointer with shared ownership of a newly
+allocated memory resource.
 
 | {ref_memory_resource}
-| 表示分配器的抽象基类。
+| The abstract base class representing an allocator.
 
 | <<ref_monotonic_resource>>
-| 一种内存资源，用于分配大块内存，且其 deallocate 函数是平凡的。所分配的内存不会被释放，直到该资源被销毁，因此在解析场景下速度很快，但不适合执行修改操作。
+| A memory resource which allocates large blocks of memory and has a trivial
+deallocate function. Allocated memory is not freed until the resource is destroyed, making it fast for parsing but not suited for performing modifications.
 
 | {ref_polymorphic_allocator}
-| 一个 {req_Allocator}，它通过引用 {ref_memory_resource} 执行内存分配。
+| An {req_Allocator} which uses a reference to a {ref_memory_resource} to
+perform allocations.
 
 | <<ref_static_resource>>
-| 一种使用调用方提供的单一缓冲区的内存资源，不进行任何动态分配。该资源在解析时速度很快，但不适合执行修改操作。
+| A memory resource that uses a single caller provided buffer. No dynamic
+allocations are used. This is fast for parsing but not suited for performing modifications.
 
 | <<ref_storage_ptr>>
-| 一种用于管理和访问 {ref_memory_resource} 的智能指针。
-|===
+| A smart pointer through which a {ref_memory_resource} is managed and
+accessed. |===
 
 == 默认内存资源
 默认内存资源使用全局 `operator new` 和 `operator delete` 来进行内存分配。该资源不采用引用计数，且其 deallocate 函数是非平凡的。所有默认构造的 <<ref_storage_ptr>> 对象均引用同一个内存资源：

diff --git a/doc/pages/allocators/uses_allocator_zh_Hans.adoc b/doc/pages/allocators/uses_allocator_zh_Hans.adoc
@@ -9,28 +9,29 @@ Official repository: https://github.com/boostorg/json
 ////
 
 [#uses_allocator]
-= 使用分配器构造
-为支持已使用多态分配器的代码库，本库中的容器支持 {std_uses_allocator} 构造。对于 <<ref_array>>, <<ref_object>>, <<ref_string>> 和 <<ref_value>>：
+= 使用分配器构造 为支持已使用多态分配器的代码库，本库中的容器支持 {std_uses_allocator} 构造。对于 <<ref_array>>, <<ref_object>>, <<ref_string>> 和 <<ref_value>>：
 
 * 嵌套类型 `allocator_type` 是{ref_polymorphic_allocator}的别名。
+由容器所使用的 {ref_memory_resource} 构造的 {ref_polymorphic_allocator} 实例。该内存资源的所有权不会被转移。
 
 * 所有接受 <<ref_storage_ptr>> 的合格构造函数，也将在相同参数位置接受一个 {ref_polymorphic_allocator} 实例。
+实际上，这意味着当库中的容器类型被用在使用多态分配器的标准容器中时，该分配器会传播到 JSON 类型。例如：
 
 * 成员函数 `get_allocator` 返回一个
- 由容器所使用的 {ref_memory_resource} 构造的 {ref_polymorphic_allocator} 实例。该内存资源的所有权不会被转移。
+库容器可以从多态分配器构造：
 
-实际上，这意味着当库中的容器类型被用在使用多态分配器的标准容器中时，该分配器会传播到 JSON 类型。例如：
+多态分配器会递归传播。子元素的子元素将使用与父元素相同的内存资源。
 
 [source]
 ----
 include::../../../test/doc_uses_allocator.cpp[tag=doc_uses_allocator_1,indent=0]
 ----
 
-库容器可以从多态分配器构造：
+Library containers can be constructed from polymorphic allocators:
 
 [source]
 ----
 include::../../../test/doc_uses_allocator.cpp[tag=doc_uses_allocator_2,indent=0]
 ----
 
-多态分配器会递归传播。子元素的子元素将使用与父元素相同的内存资源。
+The polymorphic allocator is propagated recursively. Child elements of child elements will use the same memory resource as the parent.