Language Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
English 0 0 0 0 0 0 0
Chinese (Simplified Han script) 100% 0 0 0 0 3 0 0
Please sign in to see the alerts.

Summary

Project website www.boost.org
Instructions for translators

Please translate the Boost.json documentation. Maintain technical accuracy and follow AsciiDoc formatting conventions.
Project maintainers1 User avatar user01
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:AuraMindNest/json.git
Repository branch develop
Last commit in Weblate Translated using Weblate (Chinese (Simplified Han script)) 3c2eea2
User avatar user01 authored a month ago
Weblate repository https://boost-weblate.cloud/git/boost-json-documentation/doc-library-detail/
File mask doc/pages/conversion/nothrow_*.adoc
Monolingual base language file doc/pages/conversion/nothrow.adoc
4 weeks ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 22 526 3,916
Source 11 263 1,958
Translated 100% 22 100% 526 100% 3,916
Needs editing 0% 0 0% 0 0% 0
Read-only 50% 11 50% 263 50% 1,958
Failing checks 13% 3 2% 14 5% 228
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 77 changes 0 changes 1 change
FebMarAprMayJunJulAugSepOctNovDecJan

Quick numbers

526
Hosted words
22
Hosted strings
100%
Translated
2
Contributors
0
Components
2
Languages
2
Translations
0
Screenshots
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+100%
—
Contributors
+100%
User avatar None

Alert triggered
Repository has changes. a month ago
User avatar user01

Changes committed
Changes committed a month ago
User avatar user01

Translation changed
The opposite is also true: if there's a `tag_invoke` overload intended for <<ref_try_value_to>>, but not for <<ref_value_to>>, then calling <<ref_value_to>> will invoke the non-throwing overload, then construct a {ref_system_error} from the {ref_error_code} and throw it. Due to these fallbacks, it is recommended that users provide the overload from this section, rather then the other one, if they ever intend to use <<ref_try_value_to>>.
反之亦然：如果存在适用于 &lt;<<ref_try_value_to>&gt;> 的 tag_invoke 重载，但没有适用于 &lt;<<ref_value_to>&gt;> 的重载，那么调用 &lt;<<ref_value_to>&gt;> 时会转而调用不抛异常的重载，随后根据返回的 {ref_error_code} 构造一个 {ref_system_error} 并抛出。由于存在上述回退机制，建议用户在计划使用 &lt;<<ref_try_value_to>&gt;> 时，优先提供本节所述的不抛异常重载，而非抛异常的重载。</ref_try_value_to></ref_value_to></ref_value_to></ref_try_value_to>
a month ago
User avatar user01

Translation changed
If <<ref_try_value_to>> is used with a type, for which there's no `tag_invoke` overload of the form described in this section, but there is one of the form intended for <<ref_value_to>>, then the library still tries to perform the conversion. It uses the throwing overload, and attempts to convert any thrown exception into an {ref_error_code}. Note, though, that such approach will likely be slower then a dedicated overload.
如果对某个类型使用 &lt;<<ref_try_value_to>&gt;>，而该类型没有本节所述形式的 `tag_invoke` 重载，但存在适用于 &lt;<<ref_value_to>&gt;> 的重载，那么库仍会尝试执行转换：它会调用抛异常的重载，并试图将抛出的任何异常转换为 {ref_error_code}。但请注意，这种方式的性能很可能不如专门提供的不抛异常重载。</ref_value_to></ref_try_value_to>
a month ago
User avatar user01

Translation changed
The overload lets us use `ip_address` with <<ref_try_value_to>>.
该重载使我们能够将 `ip_address` 与 &lt;<<ref_try_value_to>&gt;> 一起使用。</ref_try_value_to>
a month ago
User avatar user01

Translation changed
For the class `ip_address` from the section <<custom_conversions>> this overload may look like this:
对于 &lt;<<custom_conversions>&gt;> 节中所述的 `ip_address` 类，该重载可能如下所示：</custom_conversions>
a month ago
User avatar user01

Translation changed
``` result_for<T, value>::type tag_invoke( const try_value_to_tag< T >&, const value& ); ```
``` result_for<tT, value="">::type tag_invoke( const try_value_to_tag&lt; T &gt;&amp;< T >&, const value&amp; ); ```</t,>
a month ago
User avatar user01

Translation changed
The library provides non-throwing conversions for all the categories of types it supports with <<ref_value_to>>. If a user wants to use it with custom types, an overload of `tag_invoke` of this form needs to be provided:
该库为 &lt;<<ref_value_to>&gt;> 所支持的所有类型类别均提供了不抛异常的转换。如果用户希望将其用于自定义类型，则需要提供如下形式的 `tag_invoke` 重载：</ref_value_to>
a month ago
User avatar user01

Translation changed
There's no non-throwing equivalent for <<ref_value_from>>. This is simply because we haven't yet encountered a situation where <<ref_value_from>> needed to communicate an error to the caller.
对于 &lt;<<ref_value_from>&gt>; 没有对应的不抛异常版本。这仅仅是因为我们尚未遇到需要 &lt;<<ref_value_from>&gt;> 向调用者报告错误的情况。</ref_value_from></ref_value_from>
a month ago
User avatar user01

Translation changed
For the case where throwing exceptions is undesirable, Boost.JSON also provides a non-throwing version of <<ref_value_to>>, the function template <<ref_try_value_to>>. It returns {ref_result}, a specialised variant that either holds a value or an {ref_error_code}.
对于不希望抛出异常的场景，Boost.JSON 还提供了 &lt;<<ref_value_to>&gt;> 的不抛异常版本，即函数模板 &lt;<<ref_try_value_to>&gt;>。它返回 {ref_result}，这是一个特化的变体类型，要么持有转换得到的值，要么持有 {ref_error_code}。</ref_try_value_to></ref_value_to>
a month ago
Browse all component changes