i18n(ja): fix execution-plan-related notation and spacing - #23808
Conversation
ti-chi-bot
Bot
added
area/develop
|
[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/S
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
📝 WalkthroughWalkthroughThis documentation-only change corrects Japanese execution plan terminology and wording in backup documentation, developer guides, release notes, and SQL statement documentation. It does not change functionality. ChangesJapanese documentation corrections
Estimated code review effort: 1 (Trivial) | ~2 minutes Severity of issue fixed: Low Suggested reviewers: Merge Risk: 🔵 Low · up to This documentation update standardizes execution-plan terminology, but one revised release-note sentence remains grammatically incomplete and should add 🚥 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 |
yahonda
changed the title
0bcd0df to
61f2253
Compare
yahonda
changed the title
qiancai
added
translation/no-need
Fix a corpus-wide MT spacing artifact where a half-width space was inserted between execution-plan (実行計画) and the word it modifies (binding, phase, level, digest), verified against release-8.5 line by line. Term-choice questions (e.g. execution-plan vs execution-plan katakana form for "binding") are left untouched -- this is a pure spacing fix, not a notation-unification sweep.
…subqueries.md EN: "TiDB will try to [Decorrelate of Correlated Subquery] to improve the query efficiency at the execution plan level." The JA rendering dropped the object particle after クエリ効率 and attached 向上させる directly to the link with no connective, reading as a run-on fragment.
Unify 実行計画バインディング to 実行プランバインディング where both render the same EN phrase "execution plan binding(s)" for the same referent -- confirmed as a same-file self-contradiction in br-snapshot-manual.md (heading said 実行プランバインディング, body said 実行計画バインディング). Bare "plan binding" (プランバインディ ング, without 実行) is left untouched, since it correctly mirrors EN's own separate, more casual "plan binding" wording (e.g. the "Fast Plan Binding" feature name), the same pattern as the earlier plan-cache fix.
ed6933e to
01bd612
Compare
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Advanced
Run ID: 3464a10f-d6c8-46b0-b2ba-133885985788
📒 Files selected for processing (7)
br/br-snapshot-manual.mdreleases/release-3.0-ga.mdreleases/release-6.5.12.mdreleases/release-7.5.5.mdreleases/release-8.1.0.mdreleases/release-8.1.2.mdsql-statements/sql-statement-create-binding.md
Included review availability: Your plan provides up to 4 included reviews per hour; 2 remain after this review.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
[LGTM Timeline notifier]Timeline:
|
2 participants
What is changed, added or deleted? (Required)
Two related fixes to the "execution plan" family of compound terms:
Fixes a corpus-wide MT spacing artifact: a half-width space was inserted between 実行計画 and the word it modifies — 実行計画 バインディング/フェーズ/レベル/ダイジェスト — across 8 files/9 sites. Each site was verified line-by-line against
release-8.5(EN: "execution plan binding(s)/phase/level/digest").Unifies 実行計画バインディング to 実行プランバインディング — both render the identical EN phrase "execution plan binding(s)" for the same referent (confirmed as a same-file self-contradiction in
br-snapshot-manual.md: heading said 実行プランバインディング, body said 実行計画バインディング). Bare "plan binding" (プランバインディング, without 実行) is intentionally left untouched — it correctly mirrors EN's own separate, more casual "plan binding" wording (e.g. the "Fast Plan Binding" feature name), the same EN-driven-variance pattern as the earlier execution-plan-cache fix in i18n(ja): unify execution plan cache notation #23807.Also fixes a dropped particle and scrambled clause found while reviewing
develop/dev-guide-use-subqueries.md.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