2. Boost Json Translation (zh_Hans)
3. Chinese (Simplified Han script)
4. Zen

8 :25
	English <<ref_serialize>>
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — &lt;<ref_serialize>&gt;</ref_serialize> 39/170 · 17 Needs editing
8 :67
	English Similarly, an initializer list for an <<ref_object>> is always interpreted as an <<ref_object>>. In such cases, the initializer list must be a list of key-value pairs. For example, the following code will not compile because `1` is not convertible to a string:
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — 同样，用于 &lt;<ref_object>&gt; 的初始化列表始终会被解释为 &lt;<ref_object>&gt;。此时，初始化列表必须由键值对组成。例如，以下代码无法编译，因为` `1 无法转换为字符串：</ref_object></ref_object> 133/2600 · 260 Needs editing
8 :36
	English Custom conversion.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — 自定义行为。 6/180 · 18 Needs editing
9 :13
	English https://www.boost.org/doc/libs/master/libs/json/[image:https://img.shields.io/badge/docs-master-brightgreen.svg[Documentation]]
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — https://www.boost.org/doc/libs/master/libs/json/[image:https://img.shields.io/badge/docs-master-brightgreen.svg[文档]] 116/1270 · 127 Needs editing
9 :28
	English is a string and the mapped type is a JSON value. Search, insertion, and removal have average contant-time complexity. In addition, elements are stored contiguously in memory allowing cache-friendly iteration.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — 字符串，映射类型为 JSON 值。查找、插入和移除操作具有平均常数时间复杂度。此外，元素在内存中连续存储，支持缓存友好的迭代。 63/2080 · 208 Needs editing
9 :26
	English <<ref_storage_ptr>> is used instead of {req_Allocator}, and
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — 使用&lt;<ref_storage_ptr>&gt;代替{req_Allocator}，且</ref_storage_ptr> 64/590 · 59 Needs editing
9 :79
	English contains an exponent, or
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — 包含指数，或 6/240 · 24 Needs editing
9 :65
	English The new context is used in a similar fashion to `as_string` previously in this section.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — 这个新上下文的使用方式与本节前面介绍的`as_string`类似。 33/870 · 87 Needs editing
9 :56
	English customization point, and
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — 并且 2/240 · 24 Needs editing
9 :38
	English Initializer lists consisting of two-element key value pairs can be used to construct objects with initial contents. These constructors may allocate memory and throw:
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — 由两元素键值对组成的初始化列表可用于构造带有初始内容的对象。这些构造函数可能会分配内存并抛出异常： 49/1650 · 165 Needs editing
9 :34
	English **object**: A collection of name/value pairs, also known as an
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — **对象**：名称/值对的集合，也称为 19/620 · 62 Needs editing
9 :30
	English ownership of the memory resource; the lifetime of the resource is extended until all copies of the storage pointer are destroyed.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — 对内存资源的共享所有权；该资源的生命周期将延长，直至所有该存储指针的副本均被销毁。 41/1290 · 129 Needs editing
9 :42
	English Polymorphic Allocators
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — 多态分配器 5/220 · 22 Needs editing
9 :68
	English *Constants* + <<ref_array_kind>> + <<ref_condition>> + <<ref_error>> + <<ref_kind>> + <<ref_number_precision>> + <<ref_object_kind>> + <<ref_string_kind>>
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — *常量* + &lt;<ref_array_kind>&gt; + &lt;<ref_condition>&gt; + &lt;<ref_error>&gt; + &lt;<ref_kind>&gt; + &lt;<ref_number_precision>&gt; + &lt;<ref_object_kind>&gt; + &lt;<ref_string_kind>&gt;</ref_string_kind></ref_object_kind></ref_number_precision></ref_kind></ref_error></ref_condition></ref_array_kind> 304/1540 · 154 Needs editing
9 :36
	English Library containers can be constructed from polymorphic allocators:
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — 库容器可以从多态分配器构造： 14/660 · 66 Needs editing
9 :26
	English <<ref_parse>>
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — &lt;<ref_parse>&gt;</ref_parse> 31/130 · 13 Needs editing
9 :100
	English To permit custom memory allocation strategies, these containers all allow construction with a <<ref_storage_ptr>> which is a smart pointer to a {ref_memory_resource}. The constructor signatures have the same ordering as their `std` equivalents which use {req_Allocator} parameters. Once a container is constructed its memory resource can never change. Here we create an array without performing any dynamic allocations:
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — 为支持自定义内存分配策略，这些容器均允许通过一个 &lt;<ref_storage_ptr>&gt;（指向 {ref_memory_resource} 的智能指针）进行构造。其构造函数签名的参数顺序与使用 {req_Allocator} 参数的标准库等价类型一致。容器一旦构造完成，其内存资源便不可更改。以下代码创建了一个未执行任何动态分配的数组：</ref_storage_ptr> 192/4190 · 419 Needs editing
9 :34
	English resource>>, which uses the standard C++ allocator, and is designed for general use including mutation of the document after it is parsed. The <<ref_stream_parser>> object is reused between trials, allowing temporary memory allocated by the implementation to persist and improve performance.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — resource&gt;&gt;, which uses the standard C++ allocator, and is designed for general use including mutation of the document after it is parsed. The &lt;<ref_stream_parser>&gt; object is reused between trials, allowing temporary memory allocated by the implementation to persist and improve performance.</ref_stream_parser> 322/2900 · 290 Needs editing
9 :60
	English {icon_bad} Too much customization. We struggle to see a use case for making
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — {icon_bad} 过度定制化。我们很难想象 23/750 · 75 Needs editing
9 :25
	English Return a {std_string} representing a serialized <<ref_value>>, <<ref_array>>,
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — 返回一个 {std_string}，表示序列化后的 &lt;<ref_value>&gt;、&lt;<ref_array>&gt;、</ref_array></ref_value> 90/770 · 77 Needs editing