Skip to content

i18n(ja): fix translation defects in the v6.5.x and v6.6.0 release notes - #24158

Open
yahonda wants to merge 3 commits into
pingcap:i18n-ja-release-8.5from
yahonda:fix-ja-releases-65-66
Open

yahonda wants to merge 3 commits into
pingcap:i18n-ja-release-8.5from
yahonda:fix-ja-releases-65-66

Conversation

@yahonda

@yahonda yahonda commented Oct 6, 2026 •

Copy link
Copy Markdown
Member

What is changed, added or deleted? (Required)

Fixes translation defects in the Japanese release notes for v6.5.0 to v6.6.0 (14 files). This is the second half of round 5 of the releases/ review; v6.0.0-DMR to v6.4.0 are in a separate PR. I checked each item against its EN bullet (release-8.5) and against resources/terms-en-ja.md.

Meaning fixes

  • 6.6.0:
    • L496: almost the whole bullet was missing. It is restored from EN.
    • L341: "to replace on-duplicate" was dropped, so all three items read as new.
    • L508: two duplicated "fix" clauses are merged, in the EN order.
    • Swapped identifiers in L56 (LIMIT parameters) and L308 (TTL_JOB_INTERVAL/tidb_ttl_job_run_interval).
    • Scrambled L151, L296, L300, and L348.
  • 6.5.0:
    • L272: "bidirectional" was dropped.
    • L344/L347: the enum value MEDIUM was translated.
    • TiKV-BR had a stray space.
  • 6.5.6 L108 and 6.5.x: the OOM cause; "store messages" was read as "save"; the Sort spill condition; "the Leader fails to transfer".
  • 6.5.4 L142: fsp of DATETIME/TIMESTAMP/TIME.
  • A broken handle: [5kb] → @[5kbpers] (6.6.0).
  • Wrong-domain words:
    • 拘束 → バインド.
    • 条項 → 句.
    • 感度調整 → 秘匿化.
    • 2人のDDL所有者 → 2つのDDL Owner.
    • 本番 → 生成.
    • 回転 → スピン.
    • 管理者チェックサム → ADMIN CHECKSUM.

Glossary and literals

  • Glossary terms:
    • Stale Read → ステイル読み取り.
    • Capitalized Learner and Leader stay in English (lowercase "learner" is ラーナー).
    • privileges → 権限.
    • online unsafe recovery → オンラインアンセーフリカバリ.
    • Region → リージョン.
  • These stay in English: Resolved TS, Scatter Region, safe-ts, meta-kv, crossbeam-channel, a Grafana metric name, and @[hi-rustin] (as in EN).

Particles and Markdown

  • Restores particles dropped after links or backticks (about 60 sites); removes stray particles and full stops, and backticks inside issue-link text.

Not changed: the order and spacing of handles.

Which TiDB version(s) do your changes apply to? (Required)

Tips for choosing the affected version(s):

By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.

For details, see tips for choosing the affected versions.

  • i18n-ja-release-8.5 (TiDB Japanese documentation for TiDB 8.5 versions)

What is the related PR or file link(s)?

AI agent involvement

  • The changes in this PR were primarily made by an AI agent on behalf of the PR author.

Do your changes match any of the following descriptions?

  • Delete files
  • Change aliases
  • Need modification after applied to another branch
  • Might cause conflicts after applied to another branch

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Documentation
    • Updated Japanese release notes for TiDB versions 6.5.0–6.6.0, correcting wording, terminology, formatting, links, and table headings across feature, compatibility, improvement, and bug-fix descriptions.
    • Added or updated documented bug-fix entries for versions 6.5.9 and 6.5.10, covering issues across TiDB, TiKV, PD, TiFlash, BR, and TiCDC.
    • Clarified selected configuration, compatibility, and issue conditions, including statistics initialization, TiFlash logging defaults, and failures involving PD leader changes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ti-chi-bot ti-chi-bot Bot added the missing-translation-status This PR does not have translation status info. label Oct 6, 2026
@ti-chi-bot

ti-chi-bot Bot commented Oct 6, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign hfxsd for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ti-chi-bot ti-chi-bot Bot added the size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. label Oct 6, 2026
@coderabbitai

coderabbitai Bot commented Oct 6, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

📝 Walkthrough

Walkthrough

Japanese release notes for TiDB 6.5.0–6.5.12 and 6.6.0 receive wording, terminology, and formatting revisions. Some issue descriptions are clarified, and 6.5.9 adds or updates improvement and bug-fix entries. The diff changes documentation, not implementation behavior.

Changes

Japanese release notes

Layer / File(s) Summary
6.5.0–6.5.8 release-note revisions
releases/release-6.5.0.md–releases/release-6.5.8.md
Feature, compatibility, improvement, and bug-fix descriptions receive wording and terminology corrections. Some issue conditions and descriptions are clarified.
6.5.9–6.5.12 issue-note revisions
releases/release-6.5.9.md–releases/release-6.5.12.md
The 6.5.9 notes add or update improvement and bug-fix entries. The 6.5.10–6.5.12 notes clarify or revise existing issue descriptions and terminology.
6.6.0 release-note revisions
releases/release-6.6.0.md
Feature, compatibility, configuration, improvement, and bug-fix descriptions receive wording corrections. The notes clarify parameterized LIMIT forms and physical-import checksum handling.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Other

Merge Risk: 🔵 Low · up to 0be79

The release notes have no runtime impact, but these wording, link, and version errors should be corrected before publication.

Architecture Summary

Architecture risk: 🔵 Low · up to 0be79

The change affects 1 system.

Changed systems: releases

Architecture concerns
No architecture-level concerns identified.

Review details

Systems and components

  • observed — releases (service) was modified; 14 changed files map to changed impact.

Before / after behavior

  • observed — Modified behavior in releases/release-6.5.0.md: Corrects wording in the feature overview and index-acceleration description, including the link text for adding index acceleration.
  • observed — Modified behavior in releases/release-6.5.0.md: Clarifies that INSERT INTO specifies the TiDB destination table for TiFlash query results.
  • observed — Modified behavior in releases/release-6.5.0.md: Corrects the linked description of index-merge documentation.
  • observed — Modified behavior in releases/release-6.5.0.md: Corrects the formatting of the AUTO_ID_CACHE value in the MySQL-compatible AUTO_INCREMENT description.
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Title check ✅ Passed The title clearly summarizes the main change: correcting translation defects in the Japanese v6.5.x and v6.6.0 release notes.
Description check ✅ Passed The description explains the translation corrections, identifies the affected release-note files and version branch, and includes related references and AI-agent involvement. It is mostly complete aga…
✨ Finishing Touches 💡 1
🛠️ Fix failing CI checks 💡
  • Commit to this branch
  • Create a new PR
🧪 Generate unit tests (beta)
  • Create a new PR
  • Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3


ℹ️ Review info
⚙️ Run configuration
  • Configuration used: Repository: pingcap/docs/.coderabbit.yaml
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: 786194a9-2fc1-4308-a410-c58d598202f8
📥 Commits

Reviewing files that changed from the base of the PR and between a4dfec7 and 0be7993.

📒 Files selected for processing (14)
  • releases/release-6.5.0.md
  • releases/release-6.5.1.md
  • releases/release-6.5.10.md
  • releases/release-6.5.11.md
  • releases/release-6.5.12.md
  • releases/release-6.5.2.md
  • releases/release-6.5.3.md
  • releases/release-6.5.4.md
  • releases/release-6.5.5.md
  • releases/release-6.5.6.md
  • releases/release-6.5.7.md
  • releases/release-6.5.8.md
  • releases/release-6.5.9.md
  • releases/release-6.6.0.md

Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 1 remain after this review.

Comment thread releases/release-6.5.0.md
Comment thread releases/release-6.5.6.md
Comment thread releases/release-6.6.0.md Outdated
yahonda and others added 2 commits October 6, 2026 15:49
…notes

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

missing-translation-status This PR does not have translation status info. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant