2. Boost Json Translation (zh_Hans)
3. English
4. Zen

59 :137
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Supported JSON Text 19/10000 · 19
59 :90
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<parse_twitter_json,*twitter.json*>> 37/10000 · 37
59 :95
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — https://en.cppreference.com/w/cpp/language/types[`double`] 58/10000 · 58
59 :147
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — :leveloffset: -1 16/10000 · 16
59 :194
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — When using a memory resource in this fashion, including the case where a storage pointer or container is constructed from a {ref_polymorphic_allocator}, the caller must ensure that the lifetime of the resource is extended until it is no longer referenced by any variables; otherwise, undefined behavior is possible. 315/10000 · 315
59 :249
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 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: 241/10000 · 241
60 :139
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The library expects input text to be encoded using UTF-8, which is a requirement put on all JSON exchanged between systems by the https://datatracker.ietf.org/doc/html/rfc8259#section-8.1[RFC]. Similarly, the text generated by the library is valid UTF-8. 254/10000 · 254
60 :90
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 617KB 5/10000 · 5
60 :95
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<ref_value_emplace_double>> 28/10000 · 28
60 :200
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Shared ownership is achieved using the function <<ref_make_shared_resource>>, which creates a new, reference-counted memory resource using a dynamic memory allocation and returns it as a <<ref_storage_ptr>>: 207/10000 · 207
60 :259
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Custom Parsers 14/10000 · 14
61 :144
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The RFC does not allow byte order marks (BOM) to appear in JSON text, so the library considers BOM syntax errors. 113/10000 · 113
:90 :90
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — An export of data from Twitter's API. 37/10000 · 37
61 :95
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<ref_value_is_double>> 23/10000 · 23
61 :209
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — When a storage pointer is constructed this way, the lifetime of the referenced memory resource is extended until all variables which reference it are destroyed. 160/10000 · 160
61 :260
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — 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. 394/10000 · 394
62 :147
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The library supports several popular JSON extensions. These have to be explicitly enabled. 90/10000 · 90
62 :90
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<parse_twitterescaped_json,*twitterescaped.json*>> 51/10000 · 51
62 :95
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — <<ref_value_if_double>> 23/10000 · 23
62 :213
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — User-Defined Resource 21/10000 · 21