Boost Json Translation (zh_Hans)/Doc / Pages / Conversion / Direct (adoc) — Chinese (Simplified Han script) @ Boost-Weblate: Direct serialization doesn't require any special components and works with …

Zen

Translation

English

Chinese (Simplified Han script)

Needs editing

Skip

	English	Chinese (Simplified Han script)	Actions
	= Direct Conversion For large inputs parsing into the library's containers followed by conversion via <<ref_value_to>> (or vice versa <<ref_value_from>> followed by serialization from a <<ref_value>>) might be prohibitively expensive. For these cases the library provides components that allow parsing directly into and serializing directly from user-provided objects.	= 直接转换对于大型输入，先解析到库的容器中，再通过 <<ref_value_to>> 进行转换（或反之，先通过 <<ref_value_from>> 转换，再从 <<ref_value>> 序列化）可能代价过高。针对这类场景，库提供了可直接将数据解析到用户提供的对象中、或直接从用户提供的对象进行序列化的组件。</ref_value></ref_value_from></ref_value_to>
	The drawback of this approach is that fully custom type representations are not supported, only the library-provided conversions are. Also all objects that should be populated by parsing have to be default constructible types. This includes not only the top-level object, but e.g. elements of containers, members of described `struct`s, and alternatives of variants.	这种方法的缺点在于，不支持完全自定义的类型表示，仅支持库提供的转换。此外，所有需通过解析进行填充的对象都必须是可默认构造的类型——这不仅包括顶层对象，也包括容器的元素、所描述`struct`的成员以及变体类型的备选项。
	That being said, if your types are default-constructible and you don't need the customisability allowed by <<ref_value_to>> and <<ref_value_from>>, then you can get a significant performance boost with direct conversions.	尽管如此，如果你的类型是可默认构造的，并且不需要 <<ref_value_to>> 和 <<ref_value_from>> 所提供的自定义能力，那么使用直接转换可以获得显著的性能提升。</ref_value_from></ref_value_to>
	Direct parsing is performed by the <<ref_parse_into>> family of functions. The library provides overloads that take either <<ref_string_view>> or `std::istream`, and can report errors either via throwing exceptions or setting an error code.	直接解析是由<<ref_parse_into>> 系列函数执行的。库提供了接受<<<ref_string_view>> 或`std::istream`的重载，并且可以通过抛出异常或设置错误码来报告错误。</ref_string_view></ref_parse_into>
	If you need to combine incremental parsing with direct parsing, you can resort to <<ref_parser_for>>. `parser_for<T>` is an instantiation of <<ref_basic_parser>> that parses into an object of type `T`, and is what <<ref_parse_into>> uses under the hood.	如果需要将增量解析与直接解析结合使用，可以借助 <<ref_parser_for>>。`parser_for<t>`是<<ref_basic_parser>> 的一个实例化，用于将数据解析到类型为`T`的对象中，并且是<<ref_parse_into>>在底层所使用的。</ref_parse_into></ref_basic_parser></t></ref_parser_for>
	Direct serialization doesn't require any special components and works with the regular <<ref_serializer>> and <<ref_serialize>>.	直接序列化不需要任何特殊组件，可直接使用常规的 <<ref_serializer>> 和<<ref_serialize>>。</ref_serialize></ref_serializer>

	English	Chinese (Simplified Han script)	Actions
	That being said, if your types are default-constructible and you don't need the customisability allowed by <<ref_value_to>> and <<ref_value_from>>, then you can get a significant performance boost with direct conversions.	尽管如此，如果你的类型是可默认构造的，并且不需要 <<ref_value_to>> 和 <<ref_value_from>> 所提供的自定义能力，那么使用直接转换可以获得显著的性能提升。</ref_value_from></ref_value_to>
	Direct parsing is performed by the <<ref_parse_into>> family of functions. The library provides overloads that take either <<ref_string_view>> or `std::istream`, and can report errors either via throwing exceptions or setting an error code.	直接解析是由<<ref_parse_into>> 系列函数执行的。库提供了接受<<<ref_string_view>> 或`std::istream`的重载，并且可以通过抛出异常或设置错误码来报告错误。</ref_string_view></ref_parse_into>
	The drawback of this approach is that fully custom type representations are not supported, only the library-provided conversions are. Also all objects that should be populated by parsing have to be default constructible types. This includes not only the top-level object, but e.g. elements of containers, members of described `struct`s, and alternatives of variants.	这种方法的缺点在于，不支持完全自定义的类型表示，仅支持库提供的转换。此外，所有需通过解析进行填充的对象都必须是可默认构造的类型——这不仅包括顶层对象，也包括容器的元素、所描述`struct`的成员以及变体类型的备选项。
	= Direct Conversion For large inputs parsing into the library's containers followed by conversion via <<ref_value_to>> (or vice versa <<ref_value_from>> followed by serialization from a <<ref_value>>) might be prohibitively expensive. For these cases the library provides components that allow parsing directly into and serializing directly from user-provided objects.	= 直接转换对于大型输入，先解析到库的容器中，再通过 <<ref_value_to>> 进行转换（或反之，先通过 <<ref_value_from>> 转换，再从 <<ref_value>> 序列化）可能代价过高。针对这类场景，库提供了可直接将数据解析到用户提供的对象中、或直接从用户提供的对象进行序列化的组件。</ref_value></ref_value_from></ref_value_to>
	If you need to combine incremental parsing with direct parsing, you can resort to <<ref_parser_for>>. `parser_for<T>` is an instantiation of <<ref_basic_parser>> that parses into an object of type `T`, and is what <<ref_parse_into>> uses under the hood.	如果需要将增量解析与直接解析结合使用，可以借助 <<ref_parser_for>>。`parser_for<t>`是<<ref_basic_parser>> 的一个实例化，用于将数据解析到类型为`T`的对象中，并且是<<ref_parse_into>>在底层所使用的。</ref_parse_into></ref_basic_parser></t></ref_parser_for>
	Direct serialization doesn't require any special components and works with the regular <<ref_serializer>> and <<ref_serialize>>.	直接序列化不需要任何特殊组件，可直接使用常规的 <<ref_serializer>> 和<<ref_serialize>>。</ref_serialize></ref_serializer>

Loading…

admin

Translation uploaded

English

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

06/05/2026

admin

String added in the repository

English

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

06/05/2026

Browse all string changes

Things to check

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

42520

Source string location

:42

String age

06/05/2026

Last updated

06/06/2026

Source string age

06/05/2026

Translation file AsciiDoc file

doc/pages/conversion/direct_zh_Hans.adoc, string 6

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 full stop

Glossary

String information

Flags

Details

Unit identifier

Source string location

String age

Last updated

Source string age

Translation file AsciiDoc file