Boost Json Translation (zh_Hans)/Doc / Pages / Io / Parsing (adoc) — Chinese (Simplified Han script) @ Boost-Weblate: The default algorithm that the library uses to parse numbers …

Zen

Translation

English

Chinese (Simplified Han script)

Needs editing

Skip

	English	Chinese (Simplified Han script)	Actions
	of JSON texts incrementally, returning each result as a <<ref_value>>.	一系列JSON文本，并将每个结果作为<<ref_value>>返回</ref_value>
	<<ref_value_stack>>	<<ref_value_stack>></ref_value_stack>
	A low level building block used for efficiently building a <<ref_value>>. The	一种用于高效构建 <<ref_value>> 的低层构建块。</ref_value>
	parsers use this internally, and users may use it to adapt foreign parsers to produce this library's containers. \|===	解析器在内部使用它，用户也可以使用它来适配外部解析器以生成此库的容器。\|===
	The <<ref_parse>> function offers a simple interface for converting a serialized JSON text to a <<ref_value>> in a single function call. This overload uses exceptions to indicate errors:	<<ref_parse>> 函数提供了一个简单接口，用于在单个函数调用中将序列化的JSON文本转换为<<ref_value>>。此重载使用异常来指示错误：</ref_value></ref_parse>
	Alternatively, an {ref_error_code} can be used:	或者，可以使用{ref_error_code}：
	Even when using error codes, exceptions thrown from the underlying {ref_memory_resource} are still possible:	即使使用错误码，底层 {ref_memory_resource} 仍可能抛出异常：
	The <<ref_value>> returned in the preceding examples use the <<default_memory_resource,default memory resource>>. The following code uses a <<ref_monotonic_resource>>, which results in faster parsing. `jv` is marked `const` to prevent subsequent modification, because containers using a monotonic resource waste memory when mutated.	前述示例中返回的 <<ref_value>> 使用了 <<default_memory_resource,default memory="" resource="">>（默认内存资源）。以下代码使用了 <<ref_monotonic_resource>>，从而实现更快的解析。`jv` 被标记为 `const` 以防止后续修改，因为使用单调内存资源的容器在被修改时会浪费内存。</ref_monotonic_resource></default_memory_resource,default></ref_value>
	Non-Standard JSON	非标准JSON
	Unless otherwise specified, the parser in this library is strict. It recognizes only valid, standard JSON. The parser can be configured to allow certain non-standard extensions by filling in a <<ref_parse_options>> structure and passing it by value. By default all extensions are disabled:	除非另有说明，本库中的解析器采用严格模式，仅识别有效的标准 JSON。通过填充一个 <<ref_parse_options>> 结构并按值传递它来配置解析器，以允许某些非标准扩展。默认情况下，所有扩展都被禁用：</ref_parse_options>
	When building with {cpp}20 or later, the use of https://en.cppreference.com/w/cpp/language/aggregate_initialization#Designated_initializers[designated initializers] with <<ref_parse_options>> is possible:	当使用 {cpp}20 或更高版本构建时，可以对 <<ref_parse_options>> 使用 https://en.cppreference.com/w/cpp/language/aggregate_initialization#Designated_initializers[指定初始化器]：</ref_parse_options>
	When `allow_invalid_utf16` is enabled, the parser will not throw an error in the case of illegal leading, trailing, or half a surrogate. Instead, it will replace the invalid UTF-16 code point(s) with the Unicode replacement character.	启用 allow_invalid_utf16 后，解析器在遇到非法的前导代理、尾随代理或半个代理时不会抛出错误，而是将无效的 UTF-16 码点替换为 Unicode 替换字符。
	When enabling comment support take extra care not to drop whitespace	启用注释支持时，需格外注意不要丢失空白字符于
	when reading the input. For example, `std::getline` removes the endline characters from the string it produces.	读取输入时。例如，`std::getline`会从它生成的字符串中移除行尾字符
	Full Precision Number Parsing	全精度数字解析
	The default algorithm that the library uses to parse numbers is fast, but may result in slight precision loss. This may not be suitable for some applications, so there is an option to enable an alternative algorithm that doesn't have that flaw, but is somewhat slower. To do this, you also need to use <<ref_parse_options>> structure.	库默认使用的数字解析算法速度较快，但可能导致轻微的精度损失。这在某些应用中可能不可接受，因此可以选择启用一种没有此缺陷但速度稍慢的替代算法。为此，您还需要使用<<ref_parse_options>>结构体。</ref_parse_options>
	Note that full precision number parsing requires the algorithm to see the full number. This means, that when used with <<ref_stream_parser>>, additional memory allocations may be necessary to store the number parts which were so far accepted by the parser. The library does try its best to avoid such allocations.	请注意，全精度数字解析要求算法看到完整的数字。这意味着，当与<<ref_stream_parser>>一起使用时，可能需要额外的内存分配来存储解析器迄今为止接受的数字部分。该库尽力避免此类分配。</ref_stream_parser>
	Parser	解析器
	Instances of <<ref_parser>> and <<ref_stream_parser>> offer functionality beyond what is available when using the <<ref_parse>> free functions:	<<ref_parser>> 和 <<ref_stream_parser>> 的实例所提供的功能超出了使用 <<ref_parse>> 自由函数时可用的功能：</ref_parse></ref_stream_parser></ref_parser>
	More control over memory	对内存的更精细控制
	Streaming API, parse input JSON incrementally	流式 API，可增量解析输入的 JSON
	Improved performance when parsing multiple JSON texts	在解析多个JSON文本时性能更佳
	Ignore non-JSON content after the end of a JSON text	忽略JSON文本末尾之后的非JSON内容
	The parser implementation uses temporary storage space to accumulate values during parsing. When using the <<ref_parse>> free functions, this storage is allocated and freed in each call. However, by declaring an instance of <<ref_parser>> or <<ref_stream_parser>>, this temporary storage can be reused when parsing more than one JSON text, reducing the total number of dynamic memory allocations.	解析器实现使用临时存储空间在解析过程中累积值。使用 <<ref_parse>> 自由函数时，该存储在每次调用中都会被分配和释放。然而，通过声明一个 <<ref_parser>> 或 <<ref_stream_parser>> 实例，可在解析多个 JSON 文本时重用该临时存储，从而减少动态内存分配的总次数。</ref_stream_parser></ref_parser></ref_parse>
	To use the <<ref_parser>>, declare an instance. Then call <<ref_parser_write>> once with the buffer containing representing the input JSON. Finally, call <<ref_parser_release>> to take ownership of the resulting <<ref_value>> upon success. This example persists the parser instance in a class member to reuse across calls:	要使用 <<ref_parser>>，先声明一个实例。然后调用 <<ref_parser_write>> 一次，传入包含输入 JSON 的缓冲区。最后，在成功时调用 <<ref_parser_release>> 以获取生成的 <<ref_value>> 的所有权。以下示例将解析器实例作为类成员保存，以便在多次调用间复用：</ref_value></ref_parser_release></ref_parser_write></ref_parser>
	Sometimes a protocol may have a JSON text followed by data that is in a different format or specification. The JSON portion can still be parsed by using the function <<ref_parser_write_some>>. Upon success, the return value will indicate the number of characters consumed from the input, which will exclude the non-JSON characters:	有时，某个协议可能在 JSON 文本之后跟随采用不同格式或规范的数据。此时仍可使用函数 <<ref_parser_write_some>> 来解析 JSON 部分。成功时，其返回值将指示从输入中消耗的字符数，该数量不包括非 JSON 的字符：</ref_parser_write_some>
	The parser instance may be constructed with parse options which allow some non-standard JSON extensions to be recognized:	解析器实例可以使用解析选项构造，这些选项允许识别一些非标准JSON扩展：
	Streaming Parser	流式解析器
	The <<ref_stream_parser>> implements a https://en.wikipedia.org/wiki/Online_algorithm[__streaming algorithm__]; it allows incremental processing of large JSON inputs using one or more contiguous character buffers. The entire input JSON does not need to be loaded into memory at once. A network server can use the streaming interface to process incoming JSON in fixed-size amounts, providing these benefits:	<<ref_stream_parser>>实现了一种https://en.wikipedia.org/wiki/Online_algorithm[__流式算法__]；它允许使用一个或多个连续字符缓冲区增量处理大型JSON输入。整个输入JSON无需一次性加载到内存中。网络服务器可以使用流式接口以固定大小的量处理传入的JSON，从而提供以下优势：</ref_stream_parser>
	CPU consumption per I/O cycle is bounded	每个 I/O 周期的 CPU 消耗是有上限的
	Memory consumption per I/O cycle is bounded	每个 I/O 周期的内存消耗是有上限的

	English	Chinese (Simplified Han script)	Actions
	Alternatively, an {ref_error_code} can be used:	或者，可以使用{ref_error_code}：
	Jitter, unfairness, and latency is reduced	减少抖动、不公平性和延迟
	Avoiding Dynamic Allocations	避免动态分配
	= Parsing Parsing is the process where a serialized JSON text is validated and decomposed into elements. The library provides these functions and types to assist with parsing:	= 解析解析是将序列化的JSON文本验证并分解为元素的过程。该库提供以下函数和类型来辅助解析：
	A structure used to select which extensions are enabled during parsing.	一种结构，用于选择在解析期间启用哪些扩展。
	<<ref_parse>>	<<ref_parse>></ref_parse>
	Parse a string containing a complete serialized JSON text, and return	解析包含完整序列化 JSON 文本的字符串，并返回
	a <<ref_value>>.	一个 <>。
	<<ref_parser>>	<<ref_parser>></ref_parser>
	Unless otherwise specified, the parser in this library is strict. It recognizes only valid, standard JSON. The parser can be configured to allow certain non-standard extensions by filling in a <<ref_parse_options>> structure and passing it by value. By default all extensions are disabled:	除非另有说明，本库中的解析器采用严格模式，仅识别有效的标准 JSON。通过填充一个 <<ref_parse_options>> 结构并按值传递它来配置解析器，以允许某些非标准扩展。默认情况下，所有扩展都被禁用：</ref_parse_options>
	When building with {cpp}20 or later, the use of https://en.cppreference.com/w/cpp/language/aggregate_initialization#Designated_initializers[designated initializers] with <<ref_parse_options>> is possible:	当使用 {cpp}20 或更高版本构建时，可以对 <<ref_parse_options>> 使用 https://en.cppreference.com/w/cpp/language/aggregate_initialization#Designated_initializers[指定初始化器]：</ref_parse_options>
	When `allow_invalid_utf16` is enabled, the parser will not throw an error in the case of illegal leading, trailing, or half a surrogate. Instead, it will replace the invalid UTF-16 code point(s) with the Unicode replacement character.	启用 allow_invalid_utf16 后，解析器在遇到非法的前导代理、尾随代理或半个代理时不会抛出错误，而是将无效的 UTF-16 码点替换为 Unicode 替换字符。
	When enabling comment support take extra care not to drop whitespace	启用注释支持时，需格外注意不要丢失空白字符于
	when reading the input. For example, `std::getline` removes the endline characters from the string it produces.	读取输入时。例如，`std::getline`会从它生成的字符串中移除行尾字符
	Full Precision Number Parsing	全精度数字解析
	The default algorithm that the library uses to parse numbers is fast, but may result in slight precision loss. This may not be suitable for some applications, so there is an option to enable an alternative algorithm that doesn't have that flaw, but is somewhat slower. To do this, you also need to use <<ref_parse_options>> structure.	库默认使用的数字解析算法速度较快，但可能导致轻微的精度损失。这在某些应用中可能不可接受，因此可以选择启用一种没有此缺陷但速度稍慢的替代算法。为此，您还需要使用<<ref_parse_options>>结构体。</ref_parse_options>
	Note that full precision number parsing requires the algorithm to see the full number. This means, that when used with <<ref_stream_parser>>, additional memory allocations may be necessary to store the number parts which were so far accepted by the parser. The library does try its best to avoid such allocations.	请注意，全精度数字解析要求算法看到完整的数字。这意味着，当与<<ref_stream_parser>>一起使用时，可能需要额外的内存分配来存储解析器迄今为止接受的数字部分。该库尽力避免此类分配。</ref_stream_parser>
	Parser	解析器
	Instances of <<ref_parser>> and <<ref_stream_parser>> offer functionality beyond what is available when using the <<ref_parse>> free functions:	<<ref_parser>> 和 <<ref_stream_parser>> 的实例所提供的功能超出了使用 <<ref_parse>> 自由函数时可用的功能：</ref_parse></ref_stream_parser></ref_parser>
	More control over memory	对内存的更精细控制
	Streaming API, parse input JSON incrementally	流式 API，可增量解析输入的 JSON
	Improved performance when parsing multiple JSON texts	在解析多个JSON文本时性能更佳
	Ignore non-JSON content after the end of a JSON text	忽略JSON文本末尾之后的非JSON内容
	The parser implementation uses temporary storage space to accumulate values during parsing. When using the <<ref_parse>> free functions, this storage is allocated and freed in each call. However, by declaring an instance of <<ref_parser>> or <<ref_stream_parser>>, this temporary storage can be reused when parsing more than one JSON text, reducing the total number of dynamic memory allocations.	解析器实现使用临时存储空间在解析过程中累积值。使用 <<ref_parse>> 自由函数时，该存储在每次调用中都会被分配和释放。然而，通过声明一个 <<ref_parser>> 或 <<ref_stream_parser>> 实例，可在解析多个 JSON 文本时重用该临时存储，从而减少动态内存分配的总次数。</ref_stream_parser></ref_parser></ref_parse>
	To use the <<ref_parser>>, declare an instance. Then call <<ref_parser_write>> once with the buffer containing representing the input JSON. Finally, call <<ref_parser_release>> to take ownership of the resulting <<ref_value>> upon success. This example persists the parser instance in a class member to reuse across calls:	要使用 <<ref_parser>>，先声明一个实例。然后调用 <<ref_parser_write>> 一次，传入包含输入 JSON 的缓冲区。最后，在成功时调用 <<ref_parser_release>> 以获取生成的 <<ref_value>> 的所有权。以下示例将解析器实例作为类成员保存，以便在多次调用间复用：</ref_value></ref_parser_release></ref_parser_write></ref_parser>
	Sometimes a protocol may have a JSON text followed by data that is in a different format or specification. The JSON portion can still be parsed by using the function <<ref_parser_write_some>>. Upon success, the return value will indicate the number of characters consumed from the input, which will exclude the non-JSON characters:	有时，某个协议可能在 JSON 文本之后跟随采用不同格式或规范的数据。此时仍可使用函数 <<ref_parser_write_some>> 来解析 JSON 部分。成功时，其返回值将指示从输入中消耗的字符数，该数量不包括非 JSON 的字符：</ref_parser_write_some>
	The parser instance may be constructed with parse options which allow some non-standard JSON extensions to be recognized:	解析器实例可以使用解析选项构造，这些选项允许识别一些非标准JSON扩展：
	Streaming Parser	流式解析器
	The <<ref_stream_parser>> implements a https://en.wikipedia.org/wiki/Online_algorithm[__streaming algorithm__]; it allows incremental processing of large JSON inputs using one or more contiguous character buffers. The entire input JSON does not need to be loaded into memory at once. A network server can use the streaming interface to process incoming JSON in fixed-size amounts, providing these benefits:	<<ref_stream_parser>>实现了一种https://en.wikipedia.org/wiki/Online_algorithm[__流式算法__]；它允许使用一个或多个连续字符缓冲区增量处理大型JSON输入。整个输入JSON无需一次性加载到内存中。网络服务器可以使用流式接口以固定大小的量处理传入的JSON，从而提供以下优势：</ref_stream_parser>
	CPU consumption per I/O cycle is bounded	每个 I/O 周期的 CPU 消耗是有上限的

Loading…

admin

Translation uploaded

English

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

The default algorithm that the library uses to parse numbers is fast, but may result in slight precision loss. This may not be suitable for some applications, so there is an option to enable an alternative algorithm that doesn't have that flaw, but is somewhat slower. To do this, you also need to use <<库默认使用的数字解析算法速度较快，但可能导致轻微的精度损失。这在某些应用中可能不可接受，因此可以选择启用一种没有此缺陷但速度稍慢的替代算法。为此，您还需要使用<<ref_parse_options>>结构体。</ref_parse_options>~~> structure.~~

06/05/2026

admin

String added in the repository

English

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

06/05/2026

Browse all string changes

Things to check

Mismatched full stop

Source and translation do not both end with a full stop.

Reset

Glossary

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

String information

Flags

safe-html, strict-same

Unit identifier

42843

Source string location

:118

String age

06/05/2026

Last updated

06/06/2026

Source string age

06/05/2026

Translation file AsciiDoc file

doc/pages/io/parsing_zh_Hans.adoc, string 32

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

Things to check

Mismatched full stop

Glossary

String information

Flags

Details

Unit identifier

Source string location

String age

Last updated

Source string age

Translation file AsciiDoc file