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 7 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/custom_*.adoc
Monolingual base language file doc/pages/conversion/custom.adoc
2 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 46 914 7,036
Source 23 457 3,518
Translated 100% 46 100% 914 100% 7,036
Needs editing 0% 0 0% 0 0% 0
Read-only 50% 23 50% 457 50% 3,518
Failing checks 15% 7 2% 25 6% 487
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 126 changes 0 changes 1 change
FebMarAprMayJunJulAugSepOctNovDecJan

Quick numbers

914
Hosted words
46
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
``` T tag_invoke( const value_to_tag< T >&, const value& ); ```
``` T tag_invoke( const value_to_tag&lt; T &gt;&amp;< T >&, const value&amp; ); ```
a month ago
User avatar user01

Translation changed
While overloads of `tag_invoke` called by <<ref_value_to>> take the form:
而由&lt; <<ref_value_to>&gt;> 调用的`tag_invoke`重载采用以下形式：</ref_value_to>
a month ago
User avatar user01

Translation changed
``` void tag_invoke( const value_from_tag&, value&, T ); ```
``` void tag_invoke( const value_from_tag&amp;, value&amp;, T ); ```
a month ago
User avatar user01

Translation changed
Overloads of `tag_invoke` called by <<ref_value_from>> take the form:
由 &lt;<<ref_value_from>&gt;> 调用的 tag_invoke 重载具有如下形式：</ref_value_from>
a month ago
User avatar user01

Translation changed
embed the user-defined type into the arguments list (e.g. by using a tag type template such as `value_to_tag<T>`) so that its http://eel.is/c++draft/basic.lookup.argdep#2[associated namespaces and entities] are examined when name lookup is performed.
2. 将用户定义的类型嵌入到参数列表中（例如，通过使用像`value_to_tag<t>`这样的标签类型模板），以便在执行名称查找时检查其http://eel.is/c++draft/basic.lookup.argdep#2[关联的命名空间和实体]。</t>
a month ago
User avatar user01

Translation changed
It exposes both a sequence API and a tuple API. But converting from <<ref_value>> to `user_ns::ip_address` would not be able to use implementation for sequences, since those are constructed empty and then populated one element at a time, while `ip_address` has a fixed size of 4. The tuple conversion would fit, though. The only problem is that <<ref_is_tuple_like>> has a lower priority than <<ref_is_sequence_like>>. In order to circumvent this, the user only needs to specialize <<ref_is_sequence_like>> to not match `ip_address`.
它同时暴露了序列（sequence）API 和元组（tuple）API。然而，从 &lt;<<ref_value>&gt;> 转换到 user_ns::ip_address 时无法使用序列的实现，因为序列类型的转换会先构造一个空对象，再逐个填充元素，而 ip_address 的大小固定为 4。相比之下，元组转换是合适的。唯一的问题在于 &lt;<<ref_is_tuple_like>&gt;> 的优先级低于 &lt;<<ref_is_sequence_like>&gt;>。为绕过此问题，用户只需特化 &lt;<<ref_is_sequence_like>&gt;>，使其对 ip_address 不匹配即可。</ref_is_sequence_like></ref_is_sequence_like></ref_is_tuple_like></ref_value>
a month ago
User avatar user01

Translation changed
Previously a number of conversion type traits, like <<ref_is_tuple_like>> or <<ref_is_sequence_like>>, were introduced. The library tries the traits one after another and uses the implementation that corresponds to the first matching trait. In some cases, though, a type would match a trait with a higher priority, but the user intends for it to belong to a lower priority category. If this happens the user can specialize the trait that's not supposed to match for that type to be an equivalent of `std::false_type`.
之前已经介绍了一些转换类型特征，例如&lt; <<ref_is_tuple_like>&gt; 或 &lt;> 或 <<ref_is_sequence_like>&gt;>。库会依次尝试这些特征，并使用与第一个匹配特征对应的实现。然而，在某些情况下，某个类型可能会匹配到优先级更高的特征，而用户实际希望将其归入优先级更低的类别。如果发生这种情况，用户可以针对该类型特化那个不应匹配的特征，使其等同于`std::false_type`。</ref_is_sequence_like></ref_is_tuple_like>
a month ago
User avatar user01

Translation changed
Boost.JSON uses two mechanisms to customize conversion between <<ref_value>> and user types. One mechanism involves specializing type traits. The other one is more powerful and requires defining overloads of `tag_invoke`. Both mechanisms will be further explained in this section.
Boost.JSON 提供了两种机制用于自定义 &lt;<<ref_value>&gt;> 与用户类型之间的转换。一种机制涉及特化类型特征（type traits）。另一种机制更强大，需要定义`tag_invoke`的重载。本节将进一步解释这两种机制。</ref_value>
a month ago
Browse all component changes