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 11 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/context_*.adoc
Monolingual base language file doc/pages/conversion/context.adoc
3 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 64 1,380 10,850
Source 32 690 5,425
Translated 100% 64 100% 1,380 100% 10,850
Needs editing 0% 0 0% 0 0% 0
Read-only 50% 32 50% 690 50% 5,425
Failing checks 17% 11 4% 56 9% 1,028
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 150 changes 0 changes 1 change
FebMarAprMayJunJulAugSepOctNovDecJan

Quick numbers

1,380
Hosted words
64
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
For this you will have to use a different overload of `tag_invoke`. This time it has to be a function template, and it should have two parameters for contexts. The first parameter is the specific context that disambiguates that particular overload. The second parameter is the full context passed to <<ref_value_to>> or <<ref_value_from>>.
为此，您必须使用另一个`tag_invoke`重载。这次，它必须是一个函数模板，并且应包含两个上下文参数。第一个参数是用于区分该特定重载的具体上下文；第二个参数是传递给&lt; <<ref_value_to>&gt;或&lt;> 或<<ref_value_from>&gt;>的完整上下文。</ref_value_from></ref_value_to>
a month ago
User avatar user01

Translation changed
Consider this example. As was discussed in a previous section, <<ref_is_map_like>> requires that your key type satisfies <<ref_is_string_like>>. Now, let's say your keys are not string-like, but they do convert to <<ref_string>>. You can make such maps to also convert to objects using a context. But if you want to also use another context for values, you need a way to pass the full combined context to map elements. So, you want the following test to succeed.
考虑以下示例。如前一节所述，&lt;<<ref_is_map_like>&gt;>要求键类型满足&lt;<<ref_is_string_like>&gt;>。现在，假设您的键不是类字符串类型，但它们确实可以转换为&lt;<<ref_string>&gt;>。您可以通过上下文使此类映射也转换为对象。但如果您想同时为值使用另一个上下文，则需要一种方式将完整的组合上下文传递给映射元素。因此，您希望以下测试能够成功。</ref_string></ref_is_string_like></ref_is_map_like>
a month ago
User avatar user01

Translation changed
Often it is needed to use several conversion contexts together. For example, consider a log of remote users identified by IP addresses accessing a system. We can represent it as `std::vector<std::pair<std::chrono::system_clock::time_point, ip_address>>`. We want to serialize both ``ip_address``es and ``time_point``s as strings, but for this we need both `as_string` and `as_iso_8601` contexts. To combine several contexts just use {std_tuple}. Conversion functions will select the first element of the tuple for which a `tag_invoke` overload exists and will call that overload. As usual, `tag_invoke` overloads that don't use contexts and library-provided generic conversions are also supported. Thus, here's our example:
通常需要同时使用多个转换上下文。例如，考虑一个记录远程用户（通过 IP 地址标识）访问系统的日志，我们可以将其表示为 `std::vector<std::pair<std::chrono::system_clock::time_point, ip_address="">&gt;>>`。我们希望将``ip_address``和``time_point``都序列化为字符串，但这需要同时使用`as_string`和`as_iso_8601`两个上下文。要组合多个上下文，只需使用{std_tuple}。转换函数会从元组中选择第一个存在对应 `tag_invoke` 重载的元素，并调用该重载。与往常一样，不使用上下文的`tag_invoke`重载和库提供的通用转换也受支持。因此，我们的示例如下：</std::pair<std::chrono::system_clock::time_point,>
a month ago
User avatar user01

Translation changed
These `tag_invoke` overloads take an extra `as_string` parameter, which disambiguates this specific representation of `ip_address` from all other potential representations. In order to take advantage of them one needs to pass an `as_string` object to <<ref_value_from>> or <<ref_value_to>> as the last argument:
这些`tag_invoke`重载接受一个额外的`as_string`参数，用于将`ip_address`的这种特定表示形式与其他所有可能的表示形式区分开来。要使用这些重载，需要将`as_string`对象作为最后一个参数传递给&lt; <<ref_value_from>&gt; 或 &lt;<ref_value_to>&gt;：</ref_value_to></ref_value_from>> 或 <<ref_value_to>>：
a month ago
User avatar user01

Translation changed
Let's implement conversion from `user_ns::ip_address` to a JSON string:
让我们来实现从`user_ns::ip_address`到JSON字符串的转换：
a month ago
User avatar None

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

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

Component unlocked
Component unlocked a month ago
Browse all component changes