Source strings

61 Strings
100%
Browse Translate
1,191 Words
100%
8,148 Characters
100%
This translation is being used as source strings within this component.

Strings status

Strings Words Characters
61 1,191 8,148
All strings Browse Translate Zen
61 1,191 8,148
Read-only strings Browse Translate Zen
1 36 234
Strings with any failing checks Browse Translate Zen
1 36 234
Failing check: Unpluralised Browse Translate Zen

Summary

Project website www.boost.org
Instructions for translators

Please translate the Boost.Json documentation. Maintain technical accuracy and follow exact formatting conventions.
Project maintainers1 User avatar william
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses monolingual files.
  • The translation base language can not be edited.
Source code repository git@github.com:CppDigest/json.git
Repository branch local-zh_Hans
Last commit in Weblate Added translation using Weblate (Chinese (Simplified Han script)) fc1da24
User avatar william authored 04/19/2026
Weblate repository https://boost-weblate.cloud/git/boost-json-documentation-zh_Hans/boost-json-documentation-doc-library-detail-adoc/
File mask doc/pages/io/parsing_*.adoc
Monolingual base language file doc/pages/io/parsing.adoc
Translation file Download doc/pages/io/parsing.adoc
Last change April 19, 2026, 9:21 a.m.
Last change made by None
Language English
Language code en
Text direction Left to right
Case sensitivity Case-sensitive
Number of speakers 1,728,473,503
Number of plurals 2
Plural type One/other
Plurals Singular 1
Plural 0, 2, 3, 4, 5, 6, 7, 8, 9, 10, …
Plural formula n != 1
04/19/2026

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 61 1,191 8,148
Translated 100% 61 100% 1,191 100% 8,148
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 61 100% 1,191 100% 8,148
Failing checks 1% 1 3% 36 2% 234
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
AprMayJunJulAugSepOctNovDecJanFebMar

Quick numbers

0
Hosted words
0
Hosted strings
0%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
—
—
Hosted strings
—
—
Translated
—
—
Contributors
—
User avatar william

Resource updated
Parsing of the “doc/pages/io/parsing.adoc” file was enforced. 04/19/2026
User avatar william

Resource updated
File “doc/pages/io/parsing.adoc” was added. 04/19/2026
User avatar william

String added in the repository
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.
04/19/2026
User avatar william

String added in the repository
Custom Parsers
Custom Parsers
04/19/2026
User avatar william

String added in the repository
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:
04/19/2026
User avatar william

String added in the repository
Avoiding Dynamic Allocations
Avoiding Dynamic Allocations
04/19/2026
User avatar william

String added in the repository
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:
04/19/2026
User avatar william

String added in the repository
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:
04/19/2026
User avatar william

String added in the repository
Controlling Memory
Controlling Memory
04/19/2026
User avatar william

String added in the repository
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.
04/19/2026
Browse all translation changes