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

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
9 :77
	English The requirement for an initializer list to be interpreted as an <<ref_object>> or <<ref_array>> when initializing such an entity only applies to the outermost initializer list; subsequent nested elements will follow the usual ambiguity resolution rules.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — 当初始化一个 &lt;<ref_object>&gt; 或 &lt;<ref_array>&gt; 时，要求初始化列表被解释为对应类型的规则仅适用于最外层的初始化列表；后续嵌套的元素将遵循常规的歧义解析规则。</ref_array></ref_object> 129/2530 · 253 Needs editing
:36 :36
	English Custom behavior.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — 自定义行为。 6/160 · 16 Needs editing
10 :13
	English https://www.boost.org/doc/libs/develop/libs/json/[image:https://img.shields.io/badge/docs-develop-brightgreen.svg[Documentation]]
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — https://www.boost.org/doc/libs/develop/libs/json/[image:https://img.shields.io/badge/docs-develop-brightgreen.svg[文档]] 118/1290 · 129 Needs editing
10 :32
	English <<ref_string>>
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — &lt;<ref_string>&gt;</ref_string> 33/140 · 14 Needs editing
10 :27
	English small buffer optimisation is guaranteed, which avoids allocating memory for
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — 保证采用小缓冲区优化，从而避免为短字符串分配内存。 25/750 · 75 Needs editing
10 :80
	English is negative and its value is less than `INT64_MIN`, or
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — 为负数且其值小于`INT64_MIN`，或 21/540 · 54 Needs editing
10 :73
	English One particular use case that is enabled by contexts is adaptor libraries that define JSON conversion logic for types from a different library.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — 上下文支持的一个特定用例是适配器库，这些库为来自不同库的类型定义JSON转换逻辑。 41/1420 · 142 Needs editing
10 :58
	English embed the user-defined type into the arguments list (e.g. by using a tag type
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — 将用户自定义类型嵌入到参数列表中（例如，通过使用 24/770 · 77 Needs editing