Translations update from Boost-Weblate#2
Merged
Conversation
Updated by "Cleanup translation files" add-on in Weblate. Translation: Boost Json Translation (zh_Hans)/Doc / Pages / Faq (adoc) Translate-URL: https://boost-weblate.cloud/projects/boost-json-documentation-zh_Hans/doc-pages-faq-adoc/
📝 WalkthroughWalkthroughThis PR adds comprehensive Simplified Chinese (zh_Hans) documentation for Boost.JSON, comprising 38 new AsciiDoc pages organized across library overview, DOM container reference, allocator management, value conversion system, and I/O operation modules. ChangesBoost.JSON Simplified Chinese Documentation Localization
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. Comment |
added 12 commits
May 11, 2026 21:26
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 17
🧹 Nitpick comments (1)
doc/pages/dom/numbers_zh_Hans.adoc (1)
1-63: ⚡ Quick winAll translation files are missing final newlines.
All 8 documentation files in this PR (array_zh_Hans.adoc, benchmarks_zh_Hans.adoc, reference_zh_Hans.adoc, guidelines_zh_Hans.adoc, custom_zh_Hans.adoc, init_lists_zh_Hans.adoc, overview_zh_Hans.adoc, and numbers_zh_Hans.adoc) are missing a final newline at the end of the file. While not critical, adding a final newline is a POSIX standard convention and improves git diff behavior.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@doc/pages/dom/numbers_zh_Hans.adoc` around lines 1 - 63, The file ending for the document with header "[`#dom_numbers`]" and title "= 数字" is missing a final newline; add a single trailing newline character at EOF to numbers_zh_Hans.adoc (and similarly for the other listed translation files: array_zh_Hans.adoc, benchmarks_zh_Hans.adoc, reference_zh_Hans.adoc, guidelines_zh_Hans.adoc, custom_zh_Hans.adoc, init_lists_zh_Hans.adoc, overview_zh_Hans.adoc) so each file terminates with a newline to satisfy POSIX convention and improve git diffs.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@doc/library-detail_zh_Hans.adoc`:
- Line 61: Replace the mixed-language phrase "Supports -fno-exceptions（可自动检测）"
with a fully Chinese sentence for consistency, e.g., "支持
-fno-exceptions（可自动检测）", ensuring the original meaning is preserved and
punctuation/parentheses remain Chinese-style; update the string in
doc/library-detail_zh_Hans.adoc where that exact text appears.
In `@doc/pages/benchmarks_zh_Hans.adoc`:
- Line 62: Replace the English sentence "Google Summer of Code 2018 data." with
a Simplified Chinese translation to match the rest of the document; e.g., change
that line to "Google 夏季编程大赛 2018 的数据。" so the string is fully translated in
doc/pages/benchmarks_zh_Hans.adoc (locate the exact text "Google Summer of Code
2018 data." to update).
In `@doc/pages/comparison_zh_Hans.adoc`:
- Line 89: The header "=== 与SIMD JSON的比较" is mis-nested under the RapidJSON
section; change its AsciiDoc level from "===" to "==" so "与SIMD JSON的比较" becomes
a top-level peer section like other library comparisons (update the line
containing the header text and verify sibling sections use the same "==" level
for TOC consistency).
- Line 17: Update the cramped inline link
"以及https://github.com/lemire/simdjson[SIMD JSON]" by inserting a space before
the URL and a space before the bracket so it reads "以及
https://github.com/lemire/simdjson [SIMD JSON]" to match readable spacing used
for the other links; edit the phrase containing
"以及https://github.com/lemire/simdjson[SIMD JSON]" accordingly.
In `@doc/pages/conversion/direct_zh_Hans.adoc`:
- Line 17: The AsciiDoc reference token is malformed: replace the accidental
HTML entity sequence "<<<ref_string_view>>" with the correct AsciiDoc
reference token "<<"ref_string_view">>" (i.e., use <<ref_string_view>> directly)
so the phrase reads consistent with the existing <<ref_parse_into>> reference
and correctly shows the overload accepting <<ref_string_view>> or
`std::istream`.
In `@doc/pages/conversion/forward_zh_Hans.adoc`:
- Line 20: Remove the stray closing XML-like tag artifact "</ref_value>" from
the sentence that mentions tag_invoke overloads (the line referring to
<<ref_value>> being forward-declared) so the documentation renders correctly;
locate the occurrence of "</ref_value>" in the forward_zh_Hans.adoc text and
delete it, ensuring the surrounding sentence still reads correctly and uses the
intended <<ref_value>> reference syntax.
In `@doc/pages/dom/nested_access_zh_Hans.adoc`:
- Line 12: The opening sentence currently repeats wording ("为了便于便捷地获取和修改
<<ref_value>> 对象中深层嵌套的元素"); edit that sentence to remove redundancy by replacing
it with a concise version such as "为了便于获取和修改 <<ref_value>> 对象中深层嵌套的元素，该库实现了
https://datatracker.ietf.org/doc/html/rfc6901[RFC 6901 (JSON Pointer)]:" so the
phrase is clearer and non-redundant.
In `@doc/pages/dom/overview_zh_Hans.adoc`:
- Around line 47-53: The localized overview doc
(doc/pages/dom/overview_zh_Hans.adoc) is including non-localized source files
via include::value.adoc[], include::string.adoc[], include::array.adoc[],
include::object.adoc[], include::numbers.adoc[], include::init_lists.adoc[],
include::nested_access.adoc[]; update these include targets to point to their
Simplified Chinese equivalents (e.g., value_zh_Hans.adoc, string_zh_Hans.adoc,
etc.) or use the project localization variable (for example
include::value.{locale}.adoc[] or include::value_{lang}.adoc[]) so the overview
pulls localized content consistently; ensure each referenced file
(value/string/array/object/numbers/init_lists/nested_access) exists in the
zh_Hans set and rename or add localized files if necessary.
In `@doc/pages/dom/string_zh_Hans.adoc`:
- Line 15: The line containing "可修改的字符序列通过 <<ref_string>> 类型的对象表示。</ref_string>"
has a stray closing tag "</ref_string>" that should be removed; update the text
for the <<ref_string>> reference to read "可修改的字符序列通过 <<ref_string>> 类型的对象表示。"
(remove the trailing "</ref_string>") so the reference renders correctly.
In `@doc/pages/dom/value_zh_Hans.adoc`:
- Line 56: Remove the stray HTML closing tag at the end of the sentence that
reads "下表列出了所有用于判断和访问 <<ref_value>> 内容的方法："; specifically delete the incorrect
"</ref_value>" token so the AsciiDoc cross-reference remains as "<<ref_value>>"
without any closing tag.
- Around line 165-167: Replace the incorrect reference token
`<<ref_value_get_int64>>` in the table row that describes `std::uint64_t` with
the proper uint64 kind reference (e.g. `<<ref_value_get_uint64>>`) so the link
targets the correct uint64 documentation; keep the displayed text
`std::uint64_t` and the description unchanged.
- Around line 173-175: The table row uses the wrong reference token
<<ref_value_get_double>> for the `bool` kind; replace that token with the
correct bool-kind reference (the same token used elsewhere for `bool`, e.g.
<<ref_kind_bool>> or the project's canonical bool ref) so the link target
matches the `bool` entry, keeping the existing URL and description intact.
- Around line 124-131: Replace the incorrect kind identifier
<<ref_value_get_double>> with the enum reference for kind::bool (use
<<ref_value_kind_bool>> or the existing project anchor that represents the
kind::bool enum) so the first cell in this table row correctly identifies the
kind as bool; update the token at the start of the row to the canonical
kind::bool reference (e.g., <<ref_value_kind_bool>>).
- Around line 106-113: Replace the incorrect kind reference
<<ref_value_get_int64>> with the uint64 kind reference <<ref_value_get_uint64>>
so the table row correctly identifies kind::uint64; update the document entry
that currently lists <<ref_value_get_int64>> to use <<ref_value_get_uint64>> and
ensure the surrounding references (<<ref_value_emplace_uint64>>,
<<ref_value_is_uint64>>, <<ref_value_if_uint64>>, <<ref_value_try_as_uint64>>,
<<ref_value_as_uint64>>, <<ref_value_get_uint64>>) remain unchanged.
- Around line 97-104: Replace the incorrect emplace reference in the "种类测试"
(Kind Test) table cell: locate the cell that currently uses
<<ref_value_emplace_int64>> and change it to the is_int64 reference
<<ref_value_if_int64>> so the Kind Test points to the correct function; confirm
only that tag is updated and table formatting remains intact.
In `@doc/pages/io/parsing_zh_Hans.adoc`:
- Around line 66-67: The "非标准JSON" section lacks the explicit anchor referenced
as <<non_standard_json>> later; add an AsciiDoc ID anchor by inserting
[`#non_standard_json`] immediately above the "== 非标准JSON" heading so the
cross-reference <<non_standard_json>> resolves correctly (update the section
heading "非标准JSON" to include the anchor reference).
In `@doc/pages/main_zh_Hans.adoc`:
- Around line 27-37: Replace the unsuffixed include directives in
main_zh_Hans.adoc (e.g. include::quick_look.adoc[],
include::dom/overview.adoc[], include::allocators/overview.adoc[],
include::io/overview.adoc[], include::conversion/overview.adoc[],
include::examples.adoc[], include::faq.adoc[], include::benchmarks.adoc[],
include::comparison.adoc[], include::reference.adoc[],
include::../../CHANGELOG.adoc[]) with their zh_Hans variants (e.g.
include::quick_look_zh_Hans.adoc[], include::dom/overview_zh_Hans.adoc[], etc.),
updating each include::...[] line to reference the corresponding _zh_Hans
suffixed file so the translated pages are assembled into main_zh_Hans.adoc.
---
Nitpick comments:
In `@doc/pages/dom/numbers_zh_Hans.adoc`:
- Around line 1-63: The file ending for the document with header
"[`#dom_numbers`]" and title "= 数字" is missing a final newline; add a single
trailing newline character at EOF to numbers_zh_Hans.adoc (and similarly for the
other listed translation files: array_zh_Hans.adoc, benchmarks_zh_Hans.adoc,
reference_zh_Hans.adoc, guidelines_zh_Hans.adoc, custom_zh_Hans.adoc,
init_lists_zh_Hans.adoc, overview_zh_Hans.adoc) so each file terminates with a
newline to satisfy POSIX convention and improve git diffs.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: a8c4f926-f1aa-4c0f-9066-87b5abc35ce4
📒 Files selected for processing (32)
doc/library-detail_zh_Hans.adocdoc/pages/allocators/background_zh_Hans.adocdoc/pages/allocators/overview_zh_Hans.adocdoc/pages/allocators/storage_ptr_zh_Hans.adocdoc/pages/allocators/uses_allocator_zh_Hans.adocdoc/pages/benchmarks_zh_Hans.adocdoc/pages/comparison_zh_Hans.adocdoc/pages/conversion/alloc_zh_Hans.adocdoc/pages/conversion/context_zh_Hans.adocdoc/pages/conversion/custom_zh_Hans.adocdoc/pages/conversion/direct_zh_Hans.adocdoc/pages/conversion/forward_zh_Hans.adocdoc/pages/conversion/guidelines_zh_Hans.adocdoc/pages/conversion/nothrow_zh_Hans.adocdoc/pages/conversion/overview_zh_Hans.adocdoc/pages/definitions_zh_Hans.adocdoc/pages/dom/array_zh_Hans.adocdoc/pages/dom/init_lists_zh_Hans.adocdoc/pages/dom/nested_access_zh_Hans.adocdoc/pages/dom/numbers_zh_Hans.adocdoc/pages/dom/object_zh_Hans.adocdoc/pages/dom/overview_zh_Hans.adocdoc/pages/dom/string_zh_Hans.adocdoc/pages/dom/value_zh_Hans.adocdoc/pages/examples_zh_Hans.adocdoc/pages/faq_zh_Hans.adocdoc/pages/io/overview_zh_Hans.adocdoc/pages/io/parsing_zh_Hans.adocdoc/pages/io/serializing_zh_Hans.adocdoc/pages/main_zh_Hans.adocdoc/pages/quick_look_zh_Hans.adocdoc/pages/reference_zh_Hans.adoc
|
|
||
| * 仅需 C++11 | ||
| * 可链接预构建的静态或动态 Boost 库，也可使用纯头文件方式（见下文）。 | ||
| * Supports -fno-exceptions（可自动检测） |
There was a problem hiding this comment.
统一该条目的中文表述。
Line 61 目前是中英混排（Supports -fno-exceptions（可自动检测）），与整页 zh_Hans 风格不一致，建议改为完整中文表达以提升可读性与一致性。
✏️ 建议修改
-* Supports -fno-exceptions（可自动检测）
+* 支持 `-fno-exceptions`（可自动检测）📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| * Supports -fno-exceptions（可自动检测） | |
| * 支持 `-fno-exceptions`（可自动检测） |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@doc/library-detail_zh_Hans.adoc` at line 61, Replace the mixed-language
phrase "Supports -fno-exceptions（可自动检测）" with a fully Chinese sentence for
consistency, e.g., "支持 -fno-exceptions（可自动检测）", ensuring the original meaning is
preserved and punctuation/parentheses remain Chinese-style; update the string in
doc/library-detail_zh_Hans.adoc where that exact text appears.
|
|
||
| | <<parse_gsoc_2018_json,*gsoc-2018.json*>> | ||
| | 3.25MB | ||
| | Google Summer of Code 2018 data. |
There was a problem hiding this comment.
Untranslated content in Chinese documentation.
Line 62 contains English text "Google Summer of Code 2018 data." in a Simplified Chinese documentation file. For consistency with the rest of the translation, this should be translated to Chinese.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@doc/pages/benchmarks_zh_Hans.adoc` at line 62, Replace the English sentence
"Google Summer of Code 2018 data." with a Simplified Chinese translation to
match the rest of the document; e.g., change that line to "Google 夏季编程大赛 2018
的数据。" so the string is fully translated in doc/pages/benchmarks_zh_Hans.adoc
(locate the exact text "Google Summer of Code 2018 data." to update).
| :icon_good: pass:q[[.green]##✔##] | ||
| :icon_bad: pass:q[[.red]##✘##] | ||
|
|
||
| C++ 中存在众多 JSON 库，但为了比较的目的，有三个在对比中尤为值得关注：https://rapidjson.org/[RapidJSON]、https://nlohmann.github.io/json/[JSON for Modern {cpp}]（本文中称为 nlohmann's JSON， 或简称 nlohmann）以及https://github.com/lemire/simdjson[SIMD JSON]。 |
There was a problem hiding this comment.
Fix inline link spacing/punctuation for readability.
Line 17 has cramped punctuation/spacing around “以及https://...”. This may render awkwardly in the final doc.
Suggested fix
-C++ 中存在众多 JSON 库，但为了比较的目的，有三个在对比中尤为值得关注：https://rapidjson.org/[RapidJSON]、https://nlohmann.github.io/json/[JSON for Modern {cpp}]（本文中称为 nlohmann's JSON， 或简称 nlohmann）以及https://github.com/lemire/simdjson[SIMD JSON]。
+C++ 中存在众多 JSON 库，但为了比较的目的，有三个在对比中尤为值得关注：https://rapidjson.org/[RapidJSON]、https://nlohmann.github.io/json/[JSON for Modern {cpp}]（本文中称为 nlohmann's JSON，或简称 nlohmann）以及 https://github.com/lemire/simdjson[SIMD JSON]。📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| C++ 中存在众多 JSON 库，但为了比较的目的，有三个在对比中尤为值得关注：https://rapidjson.org/[RapidJSON]、https://nlohmann.github.io/json/[JSON for Modern {cpp}]（本文中称为 nlohmann's JSON， 或简称 nlohmann）以及https://github.com/lemire/simdjson[SIMD JSON]。 | |
| C++ 中存在众多 JSON 库，但为了比较的目的，有三个在对比中尤为值得关注：https://rapidjson.org/[RapidJSON]、https://nlohmann.github.io/json/[JSON for Modern {cpp}]（本文中称为 nlohmann's JSON，或简称 nlohmann）以及 https://github.com/lemire/simdjson[SIMD JSON]。 |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@doc/pages/comparison_zh_Hans.adoc` at line 17, Update the cramped inline link
"以及https://github.com/lemire/simdjson[SIMD JSON]" by inserting a space before
the URL and a space before the bracket so it reads "以及
https://github.com/lemire/simdjson [SIMD JSON]" to match readable spacing used
for the other links; edit the phrase containing
"以及https://github.com/lemire/simdjson[SIMD JSON]" accordingly.
|
|
||
| * {icon_good} 解析和序列化性能优于大多数其他库。 | ||
|
|
||
| === 与SIMD JSON的比较 |
There was a problem hiding this comment.
Section level for SIMD JSON is likely mis-nested.
Line 89 uses ===, which nests “与SIMD JSON的比较” under “与RapidJSON的比较”. Given the page intro treats SIMD JSON as a peer library, this section should likely be == to keep TOC hierarchy consistent.
Suggested fix
-=== 与SIMD JSON的比较
+== 与SIMD JSON的比较📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| === 与SIMD JSON的比较 | |
| == 与SIMD JSON的比较 |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@doc/pages/comparison_zh_Hans.adoc` at line 89, The header "=== 与SIMD JSON的比较"
is mis-nested under the RapidJSON section; change its AsciiDoc level from "==="
to "==" so "与SIMD JSON的比较" becomes a top-level peer section like other library
comparisons (update the line containing the header text and verify sibling
sections use the same "==" level for TOC consistency).
|
|
||
| 尽管如此，如果你的类型是可默认构造的，并且不需要 <<ref_value_to>> 和 <<ref_value_from>> 所提供的自定义能力，那么使用直接转换可以获得显著的性能提升。 | ||
|
|
||
| 直接解析是由<<ref_parse_into>> 系列函数执行的。库提供了接受<<<ref_string_view>> 或`std::istream`的重载，并且可以通过抛出异常或设置错误码来报告错误。 |
There was a problem hiding this comment.
Fix malformed AsciiDoc reference token.
Line 17 contains <<<ref_string_view>>, which looks like an accidental HTML entity and may render incorrectly. Use the reference directly.
Suggested fix
-直接解析是由<<ref_parse_into>> 系列函数执行的。库提供了接受<<<ref_string_view>> 或`std::istream`的重载，并且可以通过抛出异常或设置错误码来报告错误。
+直接解析是由<<ref_parse_into>> 系列函数执行的。库提供了接受 <<ref_string_view>> 或 `std::istream` 的重载，并且可以通过抛出异常或设置错误码来报告错误。📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| 直接解析是由<<ref_parse_into>> 系列函数执行的。库提供了接受<<<ref_string_view>> 或`std::istream`的重载，并且可以通过抛出异常或设置错误码来报告错误。 | |
| 直接解析是由<<ref_parse_into>> 系列函数执行的。库提供了接受 <<ref_string_view>> 或 `std::istream` 的重载，并且可以通过抛出异常或设置错误码来报告错误。 |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@doc/pages/conversion/direct_zh_Hans.adoc` at line 17, The AsciiDoc reference
token is malformed: replace the accidental HTML entity sequence
"<<<ref_string_view>>" with the correct AsciiDoc reference token
"<<"ref_string_view">>" (i.e., use <<ref_string_view>> directly) so the phrase
reads consistent with the existing <<ref_parse_into>> reference and correctly
shows the overload accepting <<ref_string_view>> or `std::istream`.
Comment on lines
+124
to
+131
| |<<ref_value_get_double>> | ||
| |https://en.cppreference.com/w/cpp/language/types[`bool`] | ||
| |<<ref_value_emplace_bool>> | ||
| |<<ref_value_is_bool>> | ||
| |<<ref_value_if_bool>> | ||
| |<<ref_value_try_as_bool>> | ||
| |<<ref_value_as_bool>> | ||
| |<<ref_value_get_bool>> |
There was a problem hiding this comment.
Fix incorrect kind reference in table.
Line 124 incorrectly uses <<ref_value_get_double>> as the kind identifier. This should be the kind::bool enum value.
🔧 Proposed fix
-|<<ref_value_get_double>>
+|<<ref_kind,`kind::bool`>>
|https://en.cppreference.com/w/cpp/language/types[`bool`]🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@doc/pages/dom/value_zh_Hans.adoc` around lines 124 - 131, Replace the
incorrect kind identifier <<ref_value_get_double>> with the enum reference for
kind::bool (use <<ref_value_kind_bool>> or the existing project anchor that
represents the kind::bool enum) so the first cell in this table row correctly
identifies the kind as bool; update the token at the start of the row to the
canonical kind::bool reference (e.g., <<ref_value_kind_bool>>).
Comment on lines
+165
to
+167
| | <<ref_value_get_int64>> | ||
| | `std::uint64_t` | ||
| | 64位无符号整数。 |
There was a problem hiding this comment.
Fix incorrect kind reference in second table.
Line 165 uses <<ref_value_get_int64>> instead of the proper kind reference for uint64.
🔧 Proposed fix
-| <<ref_value_get_int64>>
+| <<ref_kind,`kind::uint64`>>
| `std::uint64_t`📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| | <<ref_value_get_int64>> | |
| | `std::uint64_t` | |
| | 64位无符号整数。 | |
| | <<ref_kind,`kind::uint64`>> | |
| | `std::uint64_t` | |
| | 64位无符号整数。 |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@doc/pages/dom/value_zh_Hans.adoc` around lines 165 - 167, Replace the
incorrect reference token `<<ref_value_get_int64>>` in the table row that
describes `std::uint64_t` with the proper uint64 kind reference (e.g.
`<<ref_value_get_uint64>>`) so the link targets the correct uint64
documentation; keep the displayed text `std::uint64_t` and the description
unchanged.
Comment on lines
+173
to
+175
| | <<ref_value_get_double>> | ||
| | https://en.cppreference.com/w/cpp/keyword/bool[`bool`] | ||
| | 一个`bool`，用于保存`true`或`false`。 |
There was a problem hiding this comment.
Fix incorrect kind reference in second table.
Line 173 uses <<ref_value_get_double>> instead of the proper kind reference for bool.
🔧 Proposed fix
-| <<ref_value_get_double>>
+| <<ref_kind,`kind::bool`>>
| https://en.cppreference.com/w/cpp/keyword/bool[`bool`]📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| | <<ref_value_get_double>> | |
| | https://en.cppreference.com/w/cpp/keyword/bool[`bool`] | |
| | 一个`bool`，用于保存`true`或`false`。 | |
| | <<ref_kind,`kind::bool`>> | |
| | https://en.cppreference.com/w/cpp/keyword/bool[`bool`] | |
| | 一个`bool`，用于保存`true`或`false`。 |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@doc/pages/dom/value_zh_Hans.adoc` around lines 173 - 175, The table row uses
the wrong reference token <<ref_value_get_double>> for the `bool` kind; replace
that token with the correct bool-kind reference (the same token used elsewhere
for `bool`, e.g. <<ref_kind_bool>> or the project's canonical bool ref) so the
link target matches the `bool` entry, keeping the existing URL and description
intact.
Comment on lines
+66
to
+67
| == 非标准JSON | ||
| 除非另有说明，本库中的解析器采用严格模式，仅识别有效的标准 JSON。通过填充一个 <<ref_parse_options>> 结构并按值传递它来配置解析器，以允许某些非标准扩展。默认情况下，所有扩展都被禁用： |
There was a problem hiding this comment.
Add missing section anchor for cross-reference.
The section "非标准JSON" is referenced later on line 143 as <<non_standard_json>>, but the section lacks an explicit anchor ID. AsciiDoc auto-generated anchors from Chinese text won't match the English reference name, causing a broken link.
🔧 Proposed fix
-== 非标准JSON
+[`#non_standard_json`]
+== 非标准JSON
除非另有说明,本库中的解析器采用严格模式,仅识别有效的标准 JSON。通过填充一个 <<ref_parse_options>> 结构并按值传递它来配置解析器,以允许某些非标准扩展。默认情况下,所有扩展都被禁用：📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| == 非标准JSON | |
| 除非另有说明，本库中的解析器采用严格模式，仅识别有效的标准 JSON。通过填充一个 <<ref_parse_options>> 结构并按值传递它来配置解析器，以允许某些非标准扩展。默认情况下，所有扩展都被禁用： | |
| [`#non_standard_json`] | |
| == 非标准JSON | |
| 除非另有说明，本库中的解析器采用严格模式，仅识别有效的标准 JSON。通过填充一个 <<ref_parse_options>> 结构并按值传递它来配置解析器，以允许某些非标准扩展。默认情况下，所有扩展都被禁用： |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@doc/pages/io/parsing_zh_Hans.adoc` around lines 66 - 67, The "非标准JSON"
section lacks the explicit anchor referenced as <<non_standard_json>> later; add
an AsciiDoc ID anchor by inserting [`#non_standard_json`] immediately above the
"== 非标准JSON" heading so the cross-reference <<non_standard_json>> resolves
correctly (update the section heading "非标准JSON" to include the anchor
reference).
Comment on lines
+27
to
+37
| include::quick_look.adoc[] | ||
| include::dom/overview.adoc[] | ||
| include::allocators/overview.adoc[] | ||
| include::io/overview.adoc[] | ||
| include::conversion/overview.adoc[] | ||
| include::examples.adoc[] | ||
| include::faq.adoc[] | ||
| include::benchmarks.adoc[] | ||
| include::comparison.adoc[] | ||
| include::reference.adoc[] | ||
| include::../../CHANGELOG.adoc[] |
There was a problem hiding this comment.
main_zh_Hans.adoc is assembling non-zh_Hans pages.
Lines 27–37 currently include unsuffixed files, which likely bypasses the translated pages introduced by this PR.
Proposed fix
-include::quick_look.adoc[]
-include::dom/overview.adoc[]
-include::allocators/overview.adoc[]
-include::io/overview.adoc[]
-include::conversion/overview.adoc[]
-include::examples.adoc[]
-include::faq.adoc[]
-include::benchmarks.adoc[]
-include::comparison.adoc[]
-include::reference.adoc[]
+include::quick_look_zh_Hans.adoc[]
+include::dom/overview_zh_Hans.adoc[]
+include::allocators/overview_zh_Hans.adoc[]
+include::io/overview_zh_Hans.adoc[]
+include::conversion/overview_zh_Hans.adoc[]
+include::examples_zh_Hans.adoc[]
+include::faq_zh_Hans.adoc[]
+include::benchmarks_zh_Hans.adoc[]
+include::comparison_zh_Hans.adoc[]
+include::reference_zh_Hans.adoc[]📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| include::quick_look.adoc[] | |
| include::dom/overview.adoc[] | |
| include::allocators/overview.adoc[] | |
| include::io/overview.adoc[] | |
| include::conversion/overview.adoc[] | |
| include::examples.adoc[] | |
| include::faq.adoc[] | |
| include::benchmarks.adoc[] | |
| include::comparison.adoc[] | |
| include::reference.adoc[] | |
| include::../../CHANGELOG.adoc[] | |
| include::quick_look_zh_Hans.adoc[] | |
| include::dom/overview_zh_Hans.adoc[] | |
| include::allocators/overview_zh_Hans.adoc[] | |
| include::io/overview_zh_Hans.adoc[] | |
| include::conversion/overview_zh_Hans.adoc[] | |
| include::examples_zh_Hans.adoc[] | |
| include::faq_zh_Hans.adoc[] | |
| include::benchmarks_zh_Hans.adoc[] | |
| include::comparison_zh_Hans.adoc[] | |
| include::reference_zh_Hans.adoc[] | |
| include::../../CHANGELOG.adoc[] |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@doc/pages/main_zh_Hans.adoc` around lines 27 - 37, Replace the unsuffixed
include directives in main_zh_Hans.adoc (e.g. include::quick_look.adoc[],
include::dom/overview.adoc[], include::allocators/overview.adoc[],
include::io/overview.adoc[], include::conversion/overview.adoc[],
include::examples.adoc[], include::faq.adoc[], include::benchmarks.adoc[],
include::comparison.adoc[], include::reference.adoc[],
include::../../CHANGELOG.adoc[]) with their zh_Hans variants (e.g.
include::quick_look_zh_Hans.adoc[], include::dom/overview_zh_Hans.adoc[], etc.),
updating each include::...[] line to reference the corresponding _zh_Hans
suffixed file so the translated pages are assembled into main_zh_Hans.adoc.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Translations update from Boost-Weblate for Boost Json Translation (zh_Hans)/Doc / Library Detail (adoc).
It also includes following components:
Boost Json Translation (zh_Hans)/Doc / Pages / Quick Look (adoc)
Boost Json Translation (zh_Hans)/Doc / Pages / Comparison (adoc)
Boost Json Translation (zh_Hans)/Doc / Pages / Main (adoc)
Boost Json Translation (zh_Hans)/Doc / Pages / Examples (adoc)
Boost Json Translation (zh_Hans)/Doc / Pages / Definitions (adoc)
Boost Json Translation (zh_Hans)/Doc / Pages / Reference (adoc)
Boost Json Translation (zh_Hans)/Doc / Pages / Faq (adoc)
Boost Json Translation (zh_Hans)/Doc / Pages / Io / Parsing (adoc)
Boost Json Translation (zh_Hans)/Doc / Pages / Dom / Value (adoc)
Boost Json Translation (zh_Hans)/Doc / Pages / Benchmarks (adoc)
Boost Json Translation (zh_Hans)/Doc / Pages / Dom / String (adoc)
Boost Json Translation (zh_Hans)/Doc / Pages / Io / Serializing (adoc)
Boost Json Translation (zh_Hans)/Doc / Pages / Io / Overview (adoc)
Boost Json Translation (zh_Hans)/Doc / Pages / Dom / Overview (adoc)
Current translation status:
Summary by CodeRabbit
Release Notes