i18n(ja): fix same-file/same-glossary terminology self-contradictions - #23583
Merged
qiancai merged 5 commits intoAug 20, 2026
Merged
Conversation
A batch of small, independently-verified fixes where a single file
(or a term's own canonical glossary entry) used two different
Japanese renderings for the identical concept within a few lines of
each other, found during a 2026-08-07 corpus-wide notation sweep and
re-verified fresh against EN before fixing:
- pessimistic-transaction.md: heading "## 行動" (conduct/deportment,
wrong register) -> "## 動作" (system behavior), matching every
other occurrence in the same file including the very next sentence
("...同様に動作します"). Heading "## 隔離レベル" -> "## 分離レベル",
matching this file's own body text 2 lines below and the canonical
target page transaction-isolation-levels.md's own H1.
- statistics.md: unified 上位N件 -> トップN in a table (2 cells x2
rows), matching the file's own heading "### トップN" and 5 other
body occurrences describing the identical Top-N statistics feature.
- choose-index.md: heading "選定" -> "選択", matching its own sibling
heading 2 lines above and its own child heading, both "選択", for
the identical EN word "selection".
- tidb-lightning/monitor-tidb-lightning.md: a Grafana metric label
"SST摂取" (false-friend, "ingest" as in eating) -> "SST取り込み",
matching the description column of the same table row.
- tiup-component-cluster.md and tiup-component-dm.md (same defect in
both files): 4 command-list entries each mistranslated the command
name against their own inline description on the same line -
[輸入]->[インポート], [画面]->[表示], [始める]->[起動する],
[破壊する]->[破棄する] - matching every sibling entry's already-
correct translated-noun style and their own inline descriptions.
- ai/concepts/vector-search-overview.md: H1 "ベクトルサーチ" (katakana
transliteration) -> "ベクトル検索", matching all 19 other
occurrences in the same file's own body.
- ai/integrations/vector-search-integrate-with-langchain.md:
"[ジュピターノートブック]" (phonetic transliteration) ->
"[Jupyter Notebook]", matching the same file's other 4 references
to this proper noun, which correctly keep it in English.
- system-variables.md: 6 occurrences of デコリレーション (an isolated
katakana coinage used nowhere else in the corpus) -> 非相関化,
matching the linked target page correlated-subquery-optimization.md
(17 corpus occurrences), which independently translates the exact
same EN sentence pattern about this variable using 非相関化.
- tidb-cloud/tidb-cloud-glossary.md, architecture-concepts.md,
tidb-cloud-billing.md, tidb-x-architecture.md: unified all 8
occurrences of 要求容量単位(RCU) - including two glossary entries
that contradicted their own body text one line below - to
リクエストキャパシティユニット(RCU), the corpus-dominant form (11+
files) used everywhere else including PR pingcap#23430's earlier RCU
unification, which had missed this exact phrasing. Also fixed one
additional spacing variant "リクエスト キャパシティー ユニット".
- table-filter.md: "各テーブルフィルタルール" (no long-vowel mark) ->
"各テーブルフィルタールール", matching the file's own H1 and 5 other
body occurrences using テーブルフィルター/テーブルフィルタール.
- ticdc/ticdc-glossary.md: heading "### 捕獲" (capture as in
seizing/catching prey) -> "### キャプチャ", matching the very next
sentence in the same glossary entry ("複数のキャプチャによって...")
and 182 other corpus occurrences of this TiCDC component name.
Not fixed in this batch (flagged for a separate, more careful pass):
grafana-pd-dashboard.md's "ホットライト" heading turned out to
correctly mirror its own sibling "ホットリード" heading's established
phonetic-transliteration convention, not a defect; ticdc-classic-
architecture.md's オーナー/所有者 mixing needs case-by-case rewording
of several compound forms (オーナーノード, オーナーキャプチャ, etc.)
rather than a blind substitution.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
ti-chi-bot
Bot
added
the
missing-translation-status
|
test seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
|
[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 |
ti-chi-bot
Bot
added
the
size/M
|
Warning Review limit reached
Next review available in: 29 minutes Limit details: You’ve used all 4 included reviews currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?Wait for the limit to reset, then comment An organization admin can change what happens after included review limits in Billing. How do review limits work?CodeRabbit enforces per-developer PR review limits within each organization. For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (12)
Included review availability: Your plan provides up to 4 included reviews per hour; 1 remains after this review. 📝 WalkthroughWalkthrough日本語ドキュメントの用語、見出し、前提条件、ラベルを修正しました。AI、SQL、TiDB Cloud、TiDB Lightning、TiUP のページを更新しています。リンク、アンカー、動作、説明内容は変更していません。 ChangesJapanese terminology updates
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to The PR changes Japanese documentation terminology and wording, while the existing list-marker style is consistent with repository conventions; no actionable merge-blocking risk remains after normal checks and review. Suggested labels: Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 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 |
…t lists Follow-up to 63a0d2f, expanding scope per user request. The 4 tiup files with a "## コマンドリスト {#command-list}" section (and tiup-reference.md's sibling "## コンポーネントリスト {#component-list}") all link to sibling pages whose own title is the literal, untranslated CLI invocation (e.g. `title: tiup cluster import`) - matching EN's own link text, which is always the bare subcommand/component name, never a translated word. This file's established convention of translating most of these names into Japanese (テンプレート, リスト, 展開する, etc.) actually diverged from what the linked target pages themselves are titled. Reverted every list-item link text (matched by URL) to the literal English name from EN, keeping each item's already-correct Japanese description after the colon unchanged: - tiup-component-cluster.md: 26 items (supersedes the narrower 4-item fix in 63a0d2f, which is now moot - the whole list uses English) - tiup-component-dm.md: 21 items (same) - tiup-command-mirror.md: 10 items (genkey/sign/init/set/grant/ publish/modify/rotate/clone/merge - previously katakana/verb-form mistranslations like ゲンキー, サイン, 回転する) - tiup-reference.md: 11 command-list items + 1 component-list item (クラスタ -> cluster) Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
ti-chi-bot
Bot
added
size/L
…orials
All 8 files share the same "## Prerequisites" boilerplate
("このチュートリアルを完了するには、以下が必要です。" followed by a
bullet checklist), but the bullets themselves used 3 different,
inconsistent verb forms for the identical "X installed." requirement:
a dropped が particle on the Python line ("...downloads/)インストール
されています。" - missing が entirely), a past-tense narration
("...がインストールされました。", reads as reporting a completed
event rather than stating a requirement) on the Jupyter Notebook/Git
lines, and a present-state form ("...がインストールされています。")
on quickstart-via-sql.md's MySQL CLI line.
Unified all of them to "...がインストールされていること。" - the
standard Japanese convention for an enumerated prerequisite/
requirement list, matching how each bullet item completes the
preceding "以下が必要です" (you need the following) sentence.
Also fixed a sibling miss: vector-search-integrate-with-llamaindex.md
still had "ジュピターノートブック" (phonetic transliteration) instead
of "Jupyter Notebook" - the exact defect already fixed in the sibling
vector-search-integrate-with-langchain.md file in a previous commit
on this PR, but missed there.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
EN uses the plain lowercase common noun "candidate plan" throughout (5 occurrences across both files) - never capitalized, not a proper term. JA had kept it as capitalized English "Candidate プラン" (9 occurrences total), which additionally self-contradicted this exact variable's own first sentence in system-variables.md, which already correctly says 候補プラン (matching the corpus's only other instance, in release-8.5.7.md). Unified all 9 occurrences across both files to 候補プラン. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Found while sweeping the corpus for other stray "Candidate" occurrences after fixing system-variables.md/correlated-subquery- optimization.md. EN: "Release Candidate (RC)". 3 sites in this file: 2 sentences had リリース + English "Candidate" glued together (リリースCandidate), and the section heading had an even worse double-translation combining both the Japanese and English words (### リリース候補Candidate). Unified all 3 to リリース候補, the only sensible reading once the stray "Candidate" is removed - no other corpus precedent exists for this term, so this is a fresh but straightforward translation, not a notation-convention pick. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
qiancai
added
translation/no-need
qiancai
approved these changes
Aug 20, 2026
[LGTM Timeline notifier]Timeline:
|
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.
What is changed, added or deleted? (Required)
A batch of small, independently-verified fixes where a single file (or a term's own canonical glossary entry) used two different Japanese renderings for the identical concept within a few lines of each other. Found during a 2026-08-07 corpus-wide notation sweep and re-verified fresh against EN before fixing (15 files, 15 sites):
pessimistic-transaction.md: heading "行動" (wrong register) → "動作" (system behavior); heading "隔離レベル" → "分離レベル", matching the file's own body and the canonical target page.statistics.md: unified 上位N件 → トップN in a table, matching the file's own heading and 5 other body occurrences.choose-index.md: heading "選定" → "選択", matching its own sibling and child headings.tidb-lightning/monitor-tidb-lightning.md: "SST摂取" (false-friend) → "SST取り込み", matching the same row's description column.tiup-component-cluster.md/tiup-component-dm.md: 4 command-list entries each mistranslated the command name against their own inline description — [輸入]→[インポート], [画面]→[表示], [始める]→[起動する], [破壊する]→[破棄する].ai/concepts/vector-search-overview.md: H1 "ベクトルサーチ" → "ベクトル検索", matching the file's own 19 other occurrences.ai/integrations/vector-search-integrate-with-langchain.md: "[ジュピターノートブック]" → "[Jupyter Notebook]", matching the file's other references.system-variables.md: 6 occurrences of デコリレーション (isolated coinage) → 非相関化, matching the linked target page.tidb-cloud/tidb-cloud-glossary.md+ 3 other files: unified 8 occurrences of 要求容量単位(RCU) → リクエストキャパシティユニット(RCU), including two glossary entries that contradicted their own body text one line below.table-filter.md: "テーブルフィルタルール" → "テーブルフィルタールール", matching the file's own H1.ticdc/ticdc-glossary.md: heading "捕獲" → "キャプチャ", matching the very next sentence in the same glossary entry.Not fixed in this batch (flagged for a separate, more careful pass):
grafana-pd-dashboard.md's "ホットライト" heading turned out to correctly mirror its own sibling "ホットリード" heading's established convention, not a defect;ticdc-classic-architecture.md's オーナー/所有者 mixing needs case-by-case rewording of several compound forms rather than a blind substitution.All fixes verified against EN source; line counts preserved in every file.
Which TiDB version(s) do your changes apply to? (Required)
What is the related PR or file link(s)?
AI agent involvement
Do your changes match any of the following descriptions?
Summary by CodeRabbit