Skip to content

i18n(ja): fix dropped/duplicated particles in backported release-note bullets - #23708

Open
yahonda wants to merge 4 commits into
pingcap:i18n-ja-release-8.5from
yahonda:fix-ja-stats-log-particle
Open

i18n(ja): fix dropped/duplicated particles in backported release-note bullets#23708
yahonda wants to merge 4 commits into
pingcap:i18n-ja-release-8.5from
yahonda:fix-ja-stats-log-particle

Conversation

@yahonda

@yahonda yahonda commented Sep 2, 2026

Copy link
Copy Markdown
Member

What is changed, added or deleted? (Required)

Found while reading through release notes: several bullets (mostly backported bug-fix descriptions appearing identically across multiple release branches) had dropped or duplicated particles, or a particle choice that subtly misstated the relationship EN describes.

Fixed:

  • Missing する verb connecting "output the log" to "problem" in a stats-loading bullet, across 4 files (release-6.5.10.md, release-7.1.6.md, release-7.5.2.md, release-8.1.0.md)
  • Missing に particle after IndexLookup in release-7.4.0.md's cost-model bullet
  • Duplicated と/で particle in release-7.5.3.md's REMOVE PARTITIONING bullet (sibling release-8.2.0.md already had it correct)
  • の→における particle fix for the Longlong overflow-in-predicates bullet across 4 files (release-6.5.10.md, release-7.1.6.md, release-7.5.2.md, release-8.1.1.md), matching the already-correct sibling in release-8.2.0.md and the established corpus convention for "type error in X" bullets

Each fix was verified against the corresponding EN source in release-8.5, using the issue/PR number as an anchor and cross-checking sibling occurrences of the same backported bug across release branches.

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

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

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

  • This PR is translated from:
  • Other reference 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

Summary by CodeRabbit

  • Documentation
    • Corrected Japanese wording and grammar in release notes for TiDB versions 6.5.10, 7.1.6, 7.4.0, 7.5.2, 7.5.3, 8.1.0, and 8.1.1.
    • Clarified descriptions of existing bug fixes and improvements, including overflow handling, statistics loading, partitioning, and cost-model behavior.
    • No functional, logic, or product behavior changes were introduced.

@ti-chi-bot

ti-chi-bot Bot commented Sep 2, 2026

Copy link
Copy Markdown

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@ti-chi-bot ti-chi-bot Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Sep 2, 2026
@coderabbitai

coderabbitai Bot commented Sep 2, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

Next included review available in 53 minutes.

Check out review usage here.

View limit details

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.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Team

Run ID: b487ae1c-dbec-43c1-aea1-95e8f6c800cf

📥 Commits

Reviewing files that changed from the base of the PR and between a82e814 and 35f2126.

📒 Files selected for processing (7)
  • releases/release-6.5.10.md
  • releases/release-7.1.6.md
  • releases/release-7.4.0.md
  • releases/release-7.5.2.md
  • releases/release-7.5.3.md
  • releases/release-8.1.0.md
  • releases/release-8.1.1.md

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Team

Run ID: d3f34006-4ea5-4a12-894a-a85b6dbaffe7

📥 Commits

Reviewing files that changed from the base of the PR and between 23d5ab9 and cd024ad.

📒 Files selected for processing (7)
  • releases/release-6.5.10.md
  • releases/release-7.1.6.md
  • releases/release-7.4.0.md
  • releases/release-7.5.2.md
  • releases/release-7.5.3.md
  • releases/release-8.1.0.md
  • releases/release-8.1.1.md

Included review availability: Your plan provides up to 4 included reviews per hour; 1 remains after this review.


📝 Walkthrough

Walkthrough

The release notes contain Japanese wording corrections in ten entries across seven version documents. The changes affect grammar and phrasing only. No functional, structural, or public entity changes were made.

Changes

Release note corrections

Layer / File(s) Summary
Japanese wording updates
releases/release-6.5.10.md, releases/release-7.1.6.md, releases/release-7.4.0.md, releases/release-7.5.2.md, releases/release-7.5.3.md, releases/release-8.1.0.md, releases/release-8.1.1.md
Corrected Japanese expressions in Longlong overflow, statistics loading, IndexLookup, partitioning, and output-related release-note entries.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to cd024

This change only corrects wording in Japanese release notes and does not alter product behavior; no actionable merge-blocking risk remains beyond normal checks and review.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly summarizes the primary change: correcting dropped or duplicated Japanese particles in backported release-note bullets.
Description check ✅ Passed The description explains the changes, affected files, verification method, target documentation branch, and AI involvement. The selected version is stated as the repository-specific `i18n-ja-release-8…
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.
Full details: Description check

Explanation

The description explains the changes, affected files, verification method, target documentation branch, and AI involvement. The selected version is stated as the repository-specific i18n-ja-release-8.5 branch rather than one of the template checkboxes, but the affected scope is clear.

Full details: Docstring Coverage

Explanation

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 files. (7 skipped: 7 unsupported.)

✨ Finishing Touches 💡 1
🛠️ Fix failing CI checks 💡
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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.

@ti-chi-bot ti-chi-bot Bot added the missing-translation-status This PR does not have translation status info. label Sep 2, 2026
@ti-chi-bot

ti-chi-bot Bot commented Sep 2, 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 breezewish 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/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Sep 2, 2026
@yahonda
yahonda marked this pull request as ready for review September 2, 2026 08:02
@ti-chi-bot ti-chi-bot Bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Sep 2, 2026
@yahonda
yahonda force-pushed the fix-ja-stats-log-particle branch from cd024ad to 9deafab Compare September 3, 2026 02:08
@qiancai qiancai added translation/no-need No need to translate this PR. and removed missing-translation-status This PR does not have translation status info. labels Sep 3, 2026
@ti-chi-bot

ti-chi-bot Bot commented Sep 3, 2026

Copy link
Copy Markdown

[LGTM Timeline notifier]

Timeline:

  • 2026-09-03 03:38:04.672246993 +0000 UTC m=+1336919.843341099: ☑️ agreed by qiancai.

@ti-chi-bot ti-chi-bot Bot added the needs-1-more-lgtm Indicates a PR needs 1 more LGTM. label Sep 3, 2026
yahonda and others added 4 commits September 3, 2026 13:36
The bullet was missing the verb する connecting "log wo shutsuryoku"
(output the log) to "mondai" (problem), reading as a broken noun
compound instead of a relative clause. Same bug backported identically
to 4 release files.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
… release-7.4.0.md

EN: "when IndexLookup involves many table retrieval tasks". JA was
missing the ni-particle marking IndexLookup as the container/subject
of the clause.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
The bullet had a redundant "de" stacked right after "to" (jikkousuru
to de), an MT artifact; the sibling occurrence of the same bug in
release-8.2.0.md was already phrased correctly.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…convention

EN: "Fix the overflow issue of the Longlong type in predicates". The
possessive no-particle (predicate's Longlong type) subtly misstates
this as the predicate's own type rather than a type used within
predicates. Changed to niokeru, matching the sibling occurrence in
release-8.2.0.md and the established convention used elsewhere in the
corpus for "type error in X" bullets (e.g. release-4.0.11.md's
"function niokeru duration type inference" bullet).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@yahonda
yahonda force-pushed the fix-ja-stats-log-particle branch from 9deafab to 35f2126 Compare September 3, 2026 04:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs-1-more-lgtm Indicates a PR needs 1 more LGTM. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. translation/no-need No need to translate this PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants