2. Boost Json Translation (zh_Hans)
3. Doc / Pages / Io / Parsing (adoc)
4. Search

Filters

• Untranslated strings • state:empty
• Unfinished strings • state:<translated
• Translated strings • state:>=translated
• Strings marked for edit • state:needs-editing
• Strings with suggestions • has:suggestion
• Strings with variants • has:variant
• Strings with screenshots • has:screenshot
• Strings with labels • has:label
• Strings with context • has:context
• Unfinished strings without suggestions • state:<translated AND NOT has:suggestion
• Strings with comments • has:comment
• Strings with any failing checks • has:check
• Approved strings • state:approved
• Strings waiting for review • state:translated

state:>=translated

Position and priority

• Position and priority
• Position
• Priority
• Labels
• Source string
• Target string
• String age
• Last updated
• Number of words
• Number of comments
• Number of failing checks
• Key
• String location
• Component and priority

	Translation	Source string	Target string
	Boost Json Translation (zh_Hans)/Doc / Pages / Io / Parsing (adoc) — English	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:	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:
	Boost Json Translation (zh_Hans)/Doc / Pages / Io / Parsing (adoc) — Chinese (Simplified Han script)	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文本从标准输入逐行解析。此处使用错误码替代异常。函数&lt;<ref_stream_parser_finish>&gt;用于指示输入结束：</ref_stream_parser_finish>
	Boost Json Translation (zh_Hans)/Doc / Pages / Io / Parsing (adoc) — English	This example will break, if comments are enabled, because of	This example will break, if comments are enabled, because of
	Boost Json Translation (zh_Hans)/Doc / Pages / Io / Parsing (adoc) — Chinese (Simplified Han script)	This example will break, if comments are enabled, because of	如果启用了注释，此示例将失效，原因
	Boost Json Translation (zh_Hans)/Doc / Pages / Io / Parsing (adoc) — English	`std::getline` use (see the warning in <<non_standard_json>> section).	`std::getline` use (see the warning in <<non_standard_json>> section).
	Boost Json Translation (zh_Hans)/Doc / Pages / Io / Parsing (adoc) — Chinese (Simplified Han script)	`std::getline` use (see the warning in <<non_standard_json>> section).	在于使用了 `std::getline`（参见 &lt;<non_standard_json>&gt; 章节中的警告）。</non_standard_json>
	Boost Json Translation (zh_Hans)/Doc / Pages / Io / Parsing (adoc) — English	We can complicate the example further by extracting _several_ JSON values from the sequence of lines.	We can complicate the example further by extracting _several_ JSON values from the sequence of lines.
	Boost Json Translation (zh_Hans)/Doc / Pages / Io / Parsing (adoc) — Chinese (Simplified Han script)	We can complicate the example further by extracting _several_ JSON values from the sequence of lines.	我们可以通过从行序列中提取_多个_JSON值来进一步复杂化此示例。
	Boost Json Translation (zh_Hans)/Doc / Pages / Io / Parsing (adoc) — English	Controlling Memory	Controlling Memory
	Boost Json Translation (zh_Hans)/Doc / Pages / Io / Parsing (adoc) — Chinese (Simplified Han script)	Controlling Memory	控制内存
	Boost Json Translation (zh_Hans)/Doc / Pages / Io / Parsing (adoc) — English	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:	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:
	Boost Json Translation (zh_Hans)/Doc / Pages / Io / Parsing (adoc) — Chinese (Simplified Han script)	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:	在默认构造之后，或在无参调用 &lt;<ref_stream_parser_reset>&gt; 之后，成功解析操作所生成的 &lt;<ref_value>&gt; 将使用默认内存资源。若要使用不同的内存资源，可调用 `reset`并传入目标资源。以下示例使用了 &lt;<ref_monotonic_resource>&gt;，该资源针对解析进行了优化，但不适合后续修改</ref_monotonic_resource></ref_value></ref_stream_parser_reset>
	Boost Json Translation (zh_Hans)/Doc / Pages / Io / Parsing (adoc) — English	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:	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:
	Boost Json Translation (zh_Hans)/Doc / Pages / Io / Parsing (adoc) — Chinese (Simplified Han script)	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 的临时缓冲区，并在需要时回退到默认内存资源：
	Boost Json Translation (zh_Hans)/Doc / Pages / Io / Parsing (adoc) — English	Avoiding Dynamic Allocations	Avoiding Dynamic Allocations
	Boost Json Translation (zh_Hans)/Doc / Pages / Io / Parsing (adoc) — Chinese (Simplified Han script)	Avoiding Dynamic Allocations	避免动态分配
	Boost Json Translation (zh_Hans)/Doc / Pages / Io / Parsing (adoc) — English	Through careful specification of buffers and memory resources, it is possible to eliminate all dynamic allocation completely when parsing JSON, for the case where the entire JSON text is available in a single character buffer, as shown here:	Through careful specification of buffers and memory resources, it is possible to eliminate all dynamic allocation completely when parsing JSON, for the case where the entire JSON text is available in a single character buffer, as shown here:
	Boost Json Translation (zh_Hans)/Doc / Pages / Io / Parsing (adoc) — Chinese (Simplified Han script)	Through careful specification of buffers and memory resources, it is possible to eliminate all dynamic allocation completely when parsing JSON, for the case where the entire JSON text is available in a single character buffer, as shown here:	通过精心指定缓冲区和内存资源，可以在解析 JSON 时完全消除所有动态内存分配，前提是整个JSON文本在单个字符缓冲区中可用，如下所示：
	Boost Json Translation (zh_Hans)/Doc / Pages / Io / Parsing (adoc) — English	Custom Parsers	Custom Parsers
	Boost Json Translation (zh_Hans)/Doc / Pages / Io / Parsing (adoc) — Chinese (Simplified Han script)	Custom Parsers	自定义解析器
	Boost Json Translation (zh_Hans)/Doc / Pages / Io / Parsing (adoc) — English	Users who wish to implement custom parsing strategies may create their own handler to use with an instance of <<ref_basic_parser>>. The handler implements the function signatures required by SAX event interface. In <<examples_validate>> example we define the "null" parser, which throws out the parsed results, to use in the implementation of a function that determines if a JSON text is valid.	Users who wish to implement custom parsing strategies may create their own handler to use with an instance of <<ref_basic_parser>>. The handler implements the function signatures required by SAX event interface. In <<examples_validate>> example we define the "null" parser, which throws out the parsed results, to use in the implementation of a function that determines if a JSON text is valid.
	Boost Json Translation (zh_Hans)/Doc / Pages / Io / Parsing (adoc) — Chinese (Simplified Han script)	Users who wish to implement custom parsing strategies may create their own handler to use with an instance of <<ref_basic_parser>>. The handler implements the function signatures required by SAX event interface. In <<examples_validate>> example we define the "null" parser, which throws out the parsed results, to use in the implementation of a function that determines if a JSON text is valid.	希望实现自定义解析策略的用户可以创建自己的处理器（handler），并与 &lt;<ref_basic_parser>&gt; 实例配合使用。该处理器需实现 SAX 事件接口所要求的函数签名。在 &lt;<examples_validate>&gt; 示例中，我们定义了一个“空”解析器（null parser），它会丢弃所有解析结果，用于实现一个判断 JSON 文本是否有效的函数。</examples_validate></ref_basic_parser>

• 2 / 2
  / 2