i18n(ja): fix partial negations rendered as full negations#23311
i18n(ja): fix partial negations rendered as full negations#23311yahonda wants to merge 1 commit into
Conversation
|
Skipping CI for Draft Pull Request. |
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Machine translation rendered several English partial negations ("not fully",
"not all", "not totally") as unqualified Japanese negations, which invert the
meaning. For example:
EN: TiDB does not support all MySQL character sets.
JA: TiDBはMySQLのすべての文字セットをサポートしていません。 (reads: supports none)
-> TiDBはMySQLのすべての文字セットをサポートしているわけではありません。
Scope the negation with は (完全には) or 〜わけではありません, changing as few
characters as possible. 16 lines across 15 files. Each was checked against the
English source on release-8.5.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
cd0ec48 to
0b141b3
Compare
What is changed, added or deleted? (Required)
Machine translation rendered several English partial negations as unqualified Japanese negations, which inverts the meaning.
The fix scopes the negation with
は(完全には) or〜わけではありません, changing as few characters as possible.17 lines across 14 files. Each was verified against the English source on
release-8.5— only lines whose English is unambiguously a partial negation ("not fully", "not all", "not totally", "cannot cover all") were changed.How they were found: swept the ja branch for
完全に〜ない/常に〜ない/すべて〜ない, then cross-checked every hit against the English original. 79 candidates were examined; 62 turned out to be genuine full negations in English and were left untouched.The remaining
完全に正確ではありませんinai/reference/vector-search-index.mdis fixed in #23274 instead, since that line is already edited there.Which TiDB version(s) do your changes apply to? (Required)
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?
Note on scope
A few of the lines in this PR also carry a fix that belongs to one of the sibling ja PRs. Where a later sweep found damage on a line this PR already edits, the fix was applied here rather than duplicated into another PR — otherwise the two PRs would conflict. So a small number of lines go beyond the scope stated above, for example:
Here the stray
1(a translation-tool placeholder) and the word order were repaired alongside this PR's particle insertion.All fifteen ja PRs were verified to merge cleanly in any order (105 pairwise merges, 0 conflicts).