msgid "" msgstr "" "Project-Id-Version: English (Boost Json Translation (zh_Hans))\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2026-06-06 13:34+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: English \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" #: :10 #, read-only, safe-html, strict-same msgid "" "= Conversion Customization Guidelines With so many options, it can be hard " "to choose the best way to customise conversion for your type. In this " "section, we will discuss those options and suggest which to choose when." msgstr "" "= Conversion Customization Guidelines With so many options, it can be hard " "to choose the best way to customise conversion for your type. In this " "section, we will discuss those options and suggest which to choose when." #: :15 #, read-only, safe-html, strict-same msgid "" "The first advice is to use one of the library-provided conversions, rather " "then providing a custom one, unless the resulting format is undesirable. If " "the library deduces the wrong conversion category, you can opt out by " "specialising the relevant trait to inherit from `std::false_type`." msgstr "" "The first advice is to use one of the library-provided conversions, rather " "then providing a custom one, unless the resulting format is undesirable. If " "the library deduces the wrong conversion category, you can opt out by " "specialising the relevant trait to inherit from `std::false_type`." #: :20 #, read-only, safe-html, strict-same msgid "" "If library-provided conversions are suitable for you, you have the option to " "use direct conversions. This also puts the requirement of being default " "constructible on many of your types." msgstr "" "If library-provided conversions are suitable for you, you have the option to " "use direct conversions. This also puts the requirement of being default " "constructible on many of your types." #: :24 #, read-only, safe-html, strict-same msgid "" "The next thing to consider is whether your conversions are intended for " "internal use, or whether your users are not members of your team. If your " "users are external, then they will ultimately determine the conditions in " "which these conversions will be used. Conversely, for internal libraries and " "applications, you have the full control of usage conditions." msgstr "" "The next thing to consider is whether your conversions are intended for " "internal use, or whether your users are not members of your team. If your " "users are external, then they will ultimately determine the conditions in " "which these conversions will be used. Conversely, for internal libraries and " "applications, you have the full control of usage conditions." #: :30 #, read-only, safe-html, strict-same msgid "" "If your users are external, they and not you decide whether throwing " "exceptions is acceptable. So, in this case it is better to use non-throwing " "`tag_invoke` overloads. In addition, for customising conversion of composite " "types, always use `tag_invoke` overload with 2 context parameters. This will " "allow correct context propagation to elements of composites. This will also " "allow propagation of exceptions from conversion of elements." msgstr "" "If your users are external, they and not you decide whether throwing " "exceptions is acceptable. So, in this case it is better to use non-throwing " "`tag_invoke` overloads. In addition, for customising conversion of composite " "types, always use `tag_invoke` overload with 2 context parameters. This will " "allow correct context propagation to elements of composites. This will also " "allow propagation of exceptions from conversion of elements." #: :37 #, read-only, safe-html, strict-same msgid "" "Finally, it is worth mentioning that due to the ability to provide " "conversions to JSON containers without a binary dependency on the library, " "you don't have to push such dependency on your users. This is particularly " "relevant for libraries for which interoperation with Boost.JSON is only " "ancillary." msgstr "" "Finally, it is worth mentioning that due to the ability to provide " "conversions to JSON containers without a binary dependency on the library, " "you don't have to push such dependency on your users. This is particularly " "relevant for libraries for which interoperation with Boost.JSON is only " "ancillary."