msgid ""
msgstr ""
"Project-Id-Version: English (Boost Json Translation (zh_Hans))\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2026-06-06 15:34+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: English <https://insights.cppalliance.org/weblate/projects/"
"boost-json-documentation-zh_Hans/doc-pages-io-serializing-adoc/en/>\n"
"Language: en\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=n != 1;\n"
"X-Generator: Weblate 2026.5\n"

#: :11
#, read-only, safe-html, strict-same
msgid "= Serializing"
msgstr "= Serializing"

#: :13
#, read-only, safe-html, strict-same
msgid ""
"Serialization is the process where a JSON document represented in memory by "
"a <<ref_value>> is turned into a sequence of characters. The library "
"provides the following free functions and types for serialization:"
msgstr ""
"Serialization is the process where a JSON document represented in memory by "
"a <<ref_value>> is turned into a sequence of characters. The library "
"provides the following free functions and types for serialization:"

#: :18
#, read-only, safe-html, strict-same
msgid "Name"
msgstr "Name"

#: :18
#, read-only, safe-html, strict-same
msgid "Description"
msgstr "Description"

#: :18
#, read-only, safe-html, strict-same
msgid "<<ref_operator_lt_lt>>"
msgstr "<<ref_operator_lt_lt>>"

#: :18
#, read-only, safe-html, strict-same
msgid ""
"Serialize a <<ref_value>>, <<ref_array>>, <<ref_object>>, or <<ref_string>>"
msgstr ""
"Serialize a <<ref_value>>, <<ref_array>>, <<ref_object>>, or <<ref_string>>"

#: :23
#, read-only, safe-html, strict-same
msgid "to a {std_ostream}."
msgstr "to a {std_ostream}."

#: :25
#, read-only, safe-html, strict-same
msgid "<<ref_serialize>>"
msgstr "<<ref_serialize>>"

#: :25
#, read-only, safe-html, strict-same
msgid ""
"Return a {std_string} representing a serialized <<ref_value>>, <<ref_array>>,"
msgstr ""
"Return a {std_string} representing a serialized <<ref_value>>, <<ref_array>>,"

#: :27
#, read-only, safe-html, strict-same
msgid "<<ref_object>>, or <<ref_string>>."
msgstr "<<ref_object>>, or <<ref_string>>."

#: :29
#, read-only, safe-html, strict-same
msgid "<<ref_serializer>>"
msgstr "<<ref_serializer>>"

#: :29
#, read-only, safe-html, strict-same
msgid ""
"A stateful object which may be used to efficiently serialize one or more"
msgstr ""
"A stateful object which may be used to efficiently serialize one or more"

#: :31
#, read-only, safe-html, strict-same
msgid ""
"instances of <<ref_value>>, <<ref_array>>, <<ref_object>>, or <<ref_string>>"
". |==="
msgstr ""
"instances of <<ref_value>>, <<ref_array>>, <<ref_object>>, or <<ref_string>>"
". |==="

#: :34
#, read-only, safe-html, strict-same
msgid ""
"To facilitate debugging and ease of output, library container types may be "
"written to standard output streams using the stream operator:"
msgstr ""
"To facilitate debugging and ease of output, library container types may be "
"written to standard output streams using the stream operator:"

#: :42
#, read-only, safe-html, strict-same
msgid ""
"The <<ref_serialize>> function converts a <<ref_value>> into a {std_string}:"
msgstr ""
"The <<ref_serialize>> function converts a <<ref_value>> into a {std_string}:"

#: :49
#, read-only, safe-html, strict-same
msgid ""
"In situations where serializing a <<ref_value>> in its entirety is "
"inefficient or even impossible, <<ref_serializer>> can be used to serialize "
"a <<ref_value>> incrementally. This may be done for a variety of reasons, "
"such as to avoid buffering the entire output, or to ensure that a fixed "
"amount of work is performed in each cycle. Instances of <<ref_serializer>> "
"maintain an output state using internal dynamically allocated structures, "
"with an interface to retrieve successive buffers of the serialized output "
"into a caller provided buffer. Here is an example, demonstrating how "
"<<ref_operator_lt_lt>> may be implemented using a <<ref_serializer>>:"
msgstr ""
"In situations where serializing a <<ref_value>> in its entirety is "
"inefficient or even impossible, <<ref_serializer>> can be used to serialize "
"a <<ref_value>> incrementally. This may be done for a variety of reasons, "
"such as to avoid buffering the entire output, or to ensure that a fixed "
"amount of work is performed in each cycle. Instances of <<ref_serializer>> "
"maintain an output state using internal dynamically allocated structures, "
"with an interface to retrieve successive buffers of the serialized output "
"into a caller provided buffer. Here is an example, demonstrating how "
"<<ref_operator_lt_lt>> may be implemented using a <<ref_serializer>>:"

#: :64
#, read-only, safe-html, strict-same
msgid ""
"As with the parser, the serializer may be reused by calling "
"<<ref_serializer_reset>>. This sets up the object to serialize a new "
"instance and retains previously allocated memory. This can result in "
"performance improvements when multiple variables are serialized."
msgstr ""
"As with the parser, the serializer may be reused by calling "
"<<ref_serializer_reset>>. This sets up the object to serialize a new "
"instance and retains previously allocated memory. This can result in "
"performance improvements when multiple variables are serialized."