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

:38 :38
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — A stateful DOM parser object which may be used to efficiently parse a series 76/10000 · 76
17 :40
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — of JSON texts incrementally, returning each result as a <<ref_value>>. 70/10000 · 70
18 :42
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<ref_value_stack>> 19/10000 · 19
19 :42
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — A low level building block used for efficiently building a <<ref_value>>. The 77/10000 · 77
20 :44
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — parsers use this internally, and users may use it to adapt foreign parsers to produce this library's containers. |=== 117/10000 · 117
21 :48
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 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: 186/10000 · 186
22 :57
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Alternatively, an {ref_error_code} can be used: 47/10000 · 47
23 :64
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Even when using error codes, exceptions thrown from the underlying {ref_memory_resource} are still possible: 108/10000 · 108
24 :72
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 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. 332/10000 · 332
25 :83
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Non-Standard JSON 17/10000 · 17
26 :84
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 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: 289/10000 · 289
27 :94
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 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: 204/10000 · 204
28 :103
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 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. 234/10000 · 234
29 :113
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — When enabling comment support take extra care not to drop whitespace 68/10000 · 68
30 :114
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — when reading the input. For example, `std::getline` removes the endline characters from the string it produces. 111/10000 · 111
31 :117
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Full Precision Number Parsing 29/10000 · 29
32 :118
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 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. 334/10000 · 334
33 :129
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 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. 313/10000 · 313
34 :135
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Parser 6/10000 · 6
35 :136
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Instances of <<ref_parser>> and <<ref_stream_parser>> offer functionality beyond what is available when using the <<ref_parse>> free functions: 143/10000 · 143