Boost Json Translation (zh_Hans)/Doc / Pages / Comparison (adoc) — Chinese (Simplified Han script) @ Boost-Weblate: Value Type: https://github.com/Tencent/rapidjson/blob/bb5f966b9939d6cdfbac3462a0410e185099b3af/include/rapidjson/document.h#L608[`rapidjson::GenericValue`]

Zen

Translation

English

Chinese (Simplified Han script)

Needs editing

Skip

Key	English	Chinese (Simplified Han script)
	Comparison to nlohmann JSON	与nlohmann JSON的比较
	Value Type: https://github.com/nlohmann/json/blob/00cb98a3d170161711ab912ae6acefba31f29f75/include/nlohmann/json.hpp#L165[`nlohmann::basic_json`]	值类型：https://github.com/nlohmann/json/blob/00cb98a3d170161711ab912ae6acefba31f29f75/include/nlohmann/json.hpp#L165[`nlohmann::basic_json`]
	This library adopts a "kitchen sink" approach. It contains a wealth of features, even those with niche uses. Its weakness is that the many template parameters, while allowing for configurability, inhibit the best possible optimizations. The consequence is that the library performs poorly. The ability to configure every aspect of the value type has the paradoxical effect of making it less suitable as a vocabulary type.	该库采用了一种“大而全”（kitchen sink）的设计理念，包含大量功能，甚至涵盖一些使用场景非常小众的特性。其弱点在于：尽管众多模板参数提供了高度可配置性，却阻碍了编译器实现最优的性能优化。其结果是性能表现较差。这种对值类型各方面均可配置的能力，反而使其作为通用类型的适用性降低，形成了一种悖论效应。
	{icon_bad} `basic_json` is a class template. Libraries must agree on the	{icon_bad} `basic_json` 是一个类模板。各库必须在
	choices of template parameters to be interoperable.	模板参数的选择上达成一致，这样才能实现互操作。
	{icon_bad} Too much customization. We struggle to see a use case for making	{icon_bad} 过度定制化。我们很难想象
	`BooleanType` anything other than `bool`.	将 `BooleanType` 设置为 `bool` 之外的其他类型的使用场景。
	{icon_bad} Poor separation of concerns. The `basic_json` container	{icon_bad} 关注点分离不佳。`basic_json` 容器
	declaration needlessly conflates parsing and serialization APIs.	声明不必要地将解析和序列化API混杂在一起。
	{icon_bad} Limited allocator support. Only stateless allocators are allowed,	{icon_bad} 分配器支持有限。只允许无状态分配器，
	which rules out the most important type of allocator, a local arena-based implementation.	这排除了最重要的一类分配器，即基于本地内存池的实现。
:70	{icon_bad} No incremental parsing, no incremental serialization.	{icon_bad} 没有增量式解析，也没有增量式序列化。
	{icon_bad} Slow parsing and serialization performance.	{icon_bad} 解析和序列化性能较差。
	{icon_good} Full-featured, including JSON Pointer, CBOR, and others.	{icon_good} 功能全面，包含 JSON Pointer、CBOR 等特性。
	Comparison to RapidJSON	与RapidJSON的比较
	Value Type: https://github.com/Tencent/rapidjson/blob/bb5f966b9939d6cdfbac3462a0410e185099b3af/include/rapidjson/document.h#L608[`rapidjson::GenericValue`]	值类型：https://github.com/Tencent/rapidjson/blob/bb5f966b9939d6cdfbac3462a0410e185099b3af/include/rapidjson/document.h#L608[`rapidjson::GenericValue`]
	{icon_bad} The value type is not regular. Assignment is destructive,	{icon_bad} 值类型不满足“正规性”要求。赋值具有破坏性，
	performing `a = b` is equivalent to `a = std::move(b)`. No copy construction or copy assignment allowed.	执行 `a = b` 等同于 `a = std::move(b)`，且不允许复制构造和复制赋值。
	{icon_bad} Object types have no hash table or index to reduce the cost of	{icon_bad} 对象类型没有哈希表或索引用于降低查找成本。
	lookups.	(查找。)
	{icon_bad} Allocators have reference semantics. Problems with lifetime are	{icon_bad} 分配器采用引用语义，容易引发生命周期问题。
	easily encountered.	（容易引发。）
	{icon_bad} The interface of the array and object types are considerably	{icon_bad} 数组和对象类型的接口
	different from their standard library equivalents, and not idiomatic.	与标准库中的对应类型差异显著，且不符合惯用法。
:106	{icon_bad} No incremental parsing, no incremental serialization.	{icon_bad} 没有增量式解析，也没有增量式序列化。
	{icon_good} Parsing and serialization performance is better than most other	{icon_good} 解析和序列化性能优于大多数其他。
	libraries.	库。
	Comparison to SIMD JSON	与SIMD JSON的比较
	This is quite an interesting data structure, which is optimized to work well with the SIMD parser. It makes very good design choices for the intended use-case. However it is not well suited as a vocabulary type due to the necessary limitations.	这是一种相当有趣的数据结构，专为与 SIMD 解析器协同工作而优化。它在目标使用场景下做出了非常优秀的设计选择。然而，由于其必要的限制，它不太适合作为通用类型。
	{icon_bad} Sequential access only, via `ParsedJson::BasicIterator`	{icon_bad} 仅支持通过 `ParsedJson::BasicIterator` 进行顺序访问
	{icon_bad} Read-only, can only be populated by the provided SIMD JSON parser.	{icon_bad} 为只读类型，仅能通过所提供的 SIMD JSON 解析器进行填充。

	English	Chinese (Simplified Han script)	Actions
	= Comparison to Other Libraries	= 与其他库的比较
	Comparison to nlohmann JSON	与nlohmann JSON的比较
	Value Type: https://github.com/nlohmann/json/blob/00cb98a3d170161711ab912ae6acefba31f29f75/include/nlohmann/json.hpp#L165[`nlohmann::basic_json`]	值类型：https://github.com/nlohmann/json/blob/00cb98a3d170161711ab912ae6acefba31f29f75/include/nlohmann/json.hpp#L165[`nlohmann::basic_json`]
	This library adopts a "kitchen sink" approach. It contains a wealth of features, even those with niche uses. Its weakness is that the many template parameters, while allowing for configurability, inhibit the best possible optimizations. The consequence is that the library performs poorly. The ability to configure every aspect of the value type has the paradoxical effect of making it less suitable as a vocabulary type.	该库采用了一种“大而全”（kitchen sink）的设计理念，包含大量功能，甚至涵盖一些使用场景非常小众的特性。其弱点在于：尽管众多模板参数提供了高度可配置性，却阻碍了编译器实现最优的性能优化。其结果是性能表现较差。这种对值类型各方面均可配置的能力，反而使其作为通用类型的适用性降低，形成了一种悖论效应。
	{icon_bad} `basic_json` is a class template. Libraries must agree on the	{icon_bad} `basic_json` 是一个类模板。各库必须在
	choices of template parameters to be interoperable.	模板参数的选择上达成一致，这样才能实现互操作。
	{icon_bad} Too much customization. We struggle to see a use case for making	{icon_bad} 过度定制化。我们很难想象
	`BooleanType` anything other than `bool`.	将 `BooleanType` 设置为 `bool` 之外的其他类型的使用场景。
	{icon_bad} Poor separation of concerns. The `basic_json` container	{icon_bad} 关注点分离不佳。`basic_json` 容器
	{icon_bad} Limited allocator support. Only stateless allocators are allowed,	{icon_bad} 分配器支持有限。只允许无状态分配器，
	which rules out the most important type of allocator, a local arena-based implementation.	这排除了最重要的一类分配器，即基于本地内存池的实现。
	{icon_bad} Slow parsing and serialization performance.	{icon_bad} 解析和序列化性能较差。
	{icon_good} Full-featured, including JSON Pointer, CBOR, and others.	{icon_good} 功能全面，包含 JSON Pointer、CBOR 等特性。
	Comparison to RapidJSON	与RapidJSON的比较
	Value Type: https://github.com/Tencent/rapidjson/blob/bb5f966b9939d6cdfbac3462a0410e185099b3af/include/rapidjson/document.h#L608[`rapidjson::GenericValue`]	值类型：https://github.com/Tencent/rapidjson/blob/bb5f966b9939d6cdfbac3462a0410e185099b3af/include/rapidjson/document.h#L608[`rapidjson::GenericValue`]
	{icon_bad} Object types have no hash table or index to reduce the cost of	{icon_bad} 对象类型没有哈希表或索引用于降低查找成本。
	lookups.	(查找。)
	{icon_bad} Allocators have reference semantics. Problems with lifetime are	{icon_bad} 分配器采用引用语义，容易引发生命周期问题。
	easily encountered.	（容易引发。）
	different from their standard library equivalents, and not idiomatic.	与标准库中的对应类型差异显著，且不符合惯用法。
	{icon_good} Parsing and serialization performance is better than most other	{icon_good} 解析和序列化性能优于大多数其他。
	libraries.	库。
	Comparison to SIMD JSON	与SIMD JSON的比较
	This is quite an interesting data structure, which is optimized to work well with the SIMD parser. It makes very good design choices for the intended use-case. However it is not well suited as a vocabulary type due to the necessary limitations.	这是一种相当有趣的数据结构，专为与 SIMD 解析器协同工作而优化。它在目标使用场景下做出了非常优秀的设计选择。然而，由于其必要的限制，它不太适合作为通用类型。
	{icon_bad} Sequential access only, via `ParsedJson::BasicIterator`	{icon_bad} 仅支持通过 `ParsedJson::BasicIterator` 进行顺序访问
	{icon_bad} Read-only, can only be populated by the provided SIMD JSON parser.	{icon_bad} 为只读类型，仅能通过所提供的 SIMD JSON 解析器进行填充。
	declaration needlessly conflates parsing and serialization APIs.	声明不必要地将解析和序列化API混杂在一起。
	{icon_bad} The value type is not regular. Assignment is destructive,	{icon_bad} 值类型不满足“正规性”要求。赋值具有破坏性，
	performing `a = b` is equivalent to `a = std::move(b)`. No copy construction or copy assignment allowed.	执行 `a = b` 等同于 `a = std::move(b)`，且不允许复制构造和复制赋值。
	{icon_bad} The interface of the array and object types are considerably	{icon_bad} 数组和对象类型的接口

Loading…

admin

Translation uploaded

English

Chinese (Simplified Han script) 12 characters editedCurrent translationState: Translated

06/05/2026

admin

String added in the repository

English

Chinese (Simplified Han script) 155 characters editedPrevious translationState: Needs editing (Needs rewriting)

06/05/2026

Browse all string changes

Glossary

English	Chinese (Simplified Han script)
No related strings found in the glossary.

String information

Flags

safe-html, strict-same

Unit identifier

43048

Source string location

:78

String age

06/05/2026

Last updated

06/06/2026

Source string age

06/05/2026

Translation file AsciiDoc file

doc/pages/comparison_zh_Hans.adoc, string 19

Shortcut	Action
`?`	Open available keyboard shortcuts.
`Alt` + `Home`	Navigate to the first translation in the current search.
`Alt` + `End`	Navigate to the last translation in the current search.
`Alt` + `PageUp` or `Ctrl` + `↑` or `Alt` + `↑` or `Cmd` + `↑` or	Navigate to the previous translation in the current search.
`Alt` + `PageDown` or `Ctrl` + `↓` or `Alt` + `↓` or `Cmd` + `↓` or	Navigate to the next translation in the current search.
`Ctrl` + `Enter` or `Cmd` + `Enter`	Submit current form; this works the same as pressing Save and continue while editing translation.
`Ctrl` + `Shift` + `Enter` or `Cmd` + `Shift` +`Enter`	Unmark translation as Needing edit and submit it.
`Alt` + `Enter` or `Option` + `Enter`	Submit the string as a suggestion; this works the same as pressing Suggest while editing translation.
`Ctrl` + `E` or `Cmd` + `E`	Focus on translation editor.
`Ctrl` + `U` or `Cmd` + `U`	Focus on comment editor.
`Ctrl` + `M` or `Cmd` + `M`	Shows Automatic suggestions tab.
`Ctrl` + `1` to `Ctrl` + `9` or `Cmd` + `1` to `Cmd` + `9`	Copies placeable of a given number from source string.
`Ctrl` + `M` followed by `1` to `9` or `Cmd` + `M` followed by `1` to `9`	Copy the machine translation of a given number to current translation.
`Ctrl` + `I` followed by `1` to `9` or `Cmd` + `I` followed by `1` to `9`	Ignore one item in the list of failing checks.
`Ctrl` + `J` or `Cmd` + `J`	Shows the Nearby strings tab.
`Ctrl` + `S` or `Cmd` + `S`	Focus on search field.
`Ctrl` + `O` or `Cmd` + `O`	Copy the source string.
`Ctrl` + `Y` or `Cmd` + `Y`	Toggle the Needs editing checkbox.
`→`	Browse the next translation string.
`←`	Browse the previous translation string.

Translation

Glossary

String information

Flags

Details

Unit identifier

Source string location

String age

Last updated

Source string age

Translation file AsciiDoc file