Boost Json Translation (zh_Hans)/Doc / Pages / Io / Parsing (adoc) — Chinese (Simplified Han script) @ Boost-Weblate: Sometimes a protocol may have a JSON text followed by …

Zen

Translation

English

Chinese (Simplified Han script)

Needs editing

Skip

	English	Chinese (Simplified Han script)	Actions
	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 周期的内存消耗是有上限的
	Jitter, unfairness, and latency is reduced	减少抖动、不公平性和延迟
	Less total memory is required to process the full input	处理完整输入所需的总内存更少
	To use the <<ref_stream_parser>>, declare an instance. Then call <<ref_stream_parser_write>> zero or more times with successive buffers representing the input JSON. When there are no more buffers, call <<ref_stream_parser_finish>>. The function <<ref_stream_parser_done>> returns `true` after a successful call to `write` or `finish` if parsing is complete.	要使用 <<ref_stream_parser>>，请先声明一个实例。然后对表示输入 JSON 的连续缓冲区零次或多次调用 <<ref_stream_parser_write>>。当没有更多缓冲区时，调用 <<ref_stream_parser_finish>>。在成功调用`write`或`finish`后，若解析已完成，函数 <<ref_stream_parser_done>> 将返回`true`。</ref_stream_parser_done></ref_stream_parser_finish></ref_stream_parser_write></ref_stream_parser>
	In the following example a JSON text is parsed from standard input a line at a time. Error codes are used instead. The function <<ref_stream_parser_finish>> is used to indicate the end of the input:	在以下示例中，JSON文本从标准输入逐行解析。此处使用错误码替代异常。函数<<ref_stream_parser_finish>>用于指示输入结束：</ref_stream_parser_finish>
	This example will break, if comments are enabled, because of	如果启用了注释，此示例将失效，原因
	`std::getline` use (see the warning in <<non_standard_json>> section).	在于使用了 `std::getline`（参见 <<non_standard_json>> 章节中的警告）。</non_standard_json>
	We can complicate the example further by extracting _several_ JSON values from the sequence of lines.	我们可以通过从行序列中提取_多个_JSON值来进一步复杂化此示例。
	Controlling Memory	控制内存
	After default construction, or after <<ref_stream_parser_reset>> is called with no arguments, the <<ref_value>> produced after a successful parse operation uses the default memory resource. To use a different memory resource, call `reset` with the resource to use. Here we use a <<ref_monotonic_resource>>, which is optimized for parsing but not subsequent modification:	在默认构造之后，或在无参调用 <<ref_stream_parser_reset>> 之后，成功解析操作所生成的 <<ref_value>> 将使用默认内存资源。若要使用不同的内存资源，可调用 `reset`并传入目标资源。以下示例使用了 <<ref_monotonic_resource>>，该资源针对解析进行了优化，但不适合后续修改</ref_monotonic_resource></ref_value></ref_stream_parser_reset>
	To achieve performance and memory efficiency, the parser uses a temporary storage area to hold intermediate results. This storage is reused when parsing more than one JSON text, reducing the total number of calls to allocate memory and thus improving performance. Upon construction, the memory resource used to perform allocations for this temporary storage area may be specified. Otherwise, the default memory resource is used. In addition to a memory resource, the parser can make use of a caller-owned buffer for temporary storage. This can help avoid dynamic allocations for small inputs. The following example uses a four kilobyte temporary buffer for the parser, and falls back to the default memory resource if needed:	为实现性能与内存效率，解析器使用一块临时存储区来保存中间结果。在解析多个 JSON 文本时，该存储区会被复用，从而减少内存分配的总次数，提升性能。构造解析器时，可指定用于此临时存储区分配的内存资源；若未指定，则使用默认内存资源。此外，解析器还可利用调用方提供的缓冲区作为临时存储，有助于避免对小型输入进行动态分配。以下示例为解析器提供了一个 4 KB 的临时缓冲区，并在需要时回退到默认内存资源：

	English	Chinese (Simplified Han script)	Actions
	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 周期的内存消耗是有上限的
	Less total memory is required to process the full input	处理完整输入所需的总内存更少
	To use the <<ref_stream_parser>>, declare an instance. Then call <<ref_stream_parser_write>> zero or more times with successive buffers representing the input JSON. When there are no more buffers, call <<ref_stream_parser_finish>>. The function <<ref_stream_parser_done>> returns `true` after a successful call to `write` or `finish` if parsing is complete.	要使用 <<ref_stream_parser>>，请先声明一个实例。然后对表示输入 JSON 的连续缓冲区零次或多次调用 <<ref_stream_parser_write>>。当没有更多缓冲区时，调用 <<ref_stream_parser_finish>>。在成功调用`write`或`finish`后，若解析已完成，函数 <<ref_stream_parser_done>> 将返回`true`。</ref_stream_parser_done></ref_stream_parser_finish></ref_stream_parser_write></ref_stream_parser>
	In the following example a JSON text is parsed from standard input a line at a time. Error codes are used instead. The function <<ref_stream_parser_finish>> is used to indicate the end of the input:	在以下示例中，JSON文本从标准输入逐行解析。此处使用错误码替代异常。函数<<ref_stream_parser_finish>>用于指示输入结束：</ref_stream_parser_finish>
	This example will break, if comments are enabled, because of	如果启用了注释，此示例将失效，原因
	`std::getline` use (see the warning in <<non_standard_json>> section).	在于使用了 `std::getline`（参见 <<non_standard_json>> 章节中的警告）。</non_standard_json>
	We can complicate the example further by extracting _several_ JSON values from the sequence of lines.	我们可以通过从行序列中提取_多个_JSON值来进一步复杂化此示例。
	Controlling Memory	控制内存
	After default construction, or after <<ref_stream_parser_reset>> is called with no arguments, the <<ref_value>> produced after a successful parse operation uses the default memory resource. To use a different memory resource, call `reset` with the resource to use. Here we use a <<ref_monotonic_resource>>, which is optimized for parsing but not subsequent modification:	在默认构造之后，或在无参调用 <<ref_stream_parser_reset>> 之后，成功解析操作所生成的 <<ref_value>> 将使用默认内存资源。若要使用不同的内存资源，可调用 `reset`并传入目标资源。以下示例使用了 <<ref_monotonic_resource>>，该资源针对解析进行了优化，但不适合后续修改</ref_monotonic_resource></ref_value></ref_stream_parser_reset>
	To achieve performance and memory efficiency, the parser uses a temporary storage area to hold intermediate results. This storage is reused when parsing more than one JSON text, reducing the total number of calls to allocate memory and thus improving performance. Upon construction, the memory resource used to perform allocations for this temporary storage area may be specified. Otherwise, the default memory resource is used. In addition to a memory resource, the parser can make use of a caller-owned buffer for temporary storage. This can help avoid dynamic allocations for small inputs. The following example uses a four kilobyte temporary buffer for the parser, and falls back to the default memory resource if needed:	为实现性能与内存效率，解析器使用一块临时存储区来保存中间结果。在解析多个 JSON 文本时，该存储区会被复用，从而减少内存分配的总次数，提升性能。构造解析器时，可指定用于此临时存储区分配的内存资源；若未指定，则使用默认内存资源。此外，解析器还可利用调用方提供的缓冲区作为临时存储，有助于避免对小型输入进行动态分配。以下示例为解析器提供了一个 4 KB 的临时缓冲区，并在需要时回退到默认内存资源：

Loading…

admin

Translation uploaded

English

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

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>

06/05/2026

admin

String added in the repository

English

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

06/05/2026

Browse all string changes

Things to check

Mismatched colon

Source and translation do not both end with a colon.

Reset

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

42853

Source string location

:162

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 42

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 colon

Mismatched full stop

Glossary

String information

Flags

Details

Unit identifier

Source string location

String age

Last updated

Source string age

Translation file AsciiDoc file