Skip to content

i18n(ja): comprehensive Japanese language fluency fixes for release notes#23254

Draft
yahonda wants to merge 9 commits into
pingcap:i18n-ja-release-8.5from
yahonda:fix-ja-pr-link-placement
Draft

i18n(ja): comprehensive Japanese language fluency fixes for release notes#23254
yahonda wants to merge 9 commits into
pingcap:i18n-ja-release-8.5from
yahonda:fix-ja-pr-link-placement

Conversation

@yahonda

@yahonda yahonda commented Jul 13, 2026

Copy link
Copy Markdown
Member

What is changed, added or deleted? (Required)

Comprehensive Japanese-language fluency fixes across all release notes (v2.0 to v8.5) and related documentation. The branch history has been reorganized into 9 commits grouped by kind of change (all changes are 1-for-1 line replacements — no functional or content changes):

  1. Terminology standardization — プッシュダウン, PointGet / Batch PointGet, tombstone, ラーナー (learner), 非厳密モード, exchange partition, prepared plan cache, multi-valued index (多値インデックス), TiDB Cloud Branching, WHERE句, 数値型, 事前分割されるリージョン, etc. (121 files)
  2. 列目 and stray removal for column references (66 files)
  3. GitHub issue/PR links and @mentions moved to the end of the sentence in release notes; dangling katakana username transliterations removed (145 files)
  4. Extraneous particles/words removed (がで, で, に) (31 files)
  5. Missing particles added (を / が / の) and particle usage fixed (12 files)
  6. Word order and sentence structure fixes (5 files)
  7. Verb forms, conjugations, and panic spacing — panic→がpanicする/をpanicさせる, imperative してください→する, プッシュダウンられ→プッシュダウンされ/できない, and missing space between product names and panic (e.g. TiKVpanicTiKV panic; the dpanic log level is preserved)
  8. Number and notation formatting — 3.20, issue hash format, DDL binlog spacing (3 files)
  9. Miscellaneous fluency and mistranslation fixes — typos, an untranslated line, wording (23 files)

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

  • master (the latest development version)
  • v8.5 (TiDB 8.5 versions)
  • v8.4 (TiDB 8.4 versions)
  • v8.3 (TiDB 8.3 versions)
  • v8.2 (TiDB 8.2 versions)
  • v8.1 (TiDB 8.1 versions)
  • v7.5 (TiDB 7.5 versions)
  • v7.1 (TiDB 7.1 versions)
  • v6.5 (TiDB 6.5 versions)
  • v6.1 (TiDB 6.1 versions)
  • v5.4 (TiDB 5.4 versions)
  • v5.3 (TiDB 5.3 versions)

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

  • This PR is translated from: N/A (Japanese-only fluency fixes)
  • Other reference link(s):

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

@ti-chi-bot

ti-chi-bot Bot commented Jul 13, 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 csuzhangxc 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 missing-translation-status This PR does not have translation status info. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Jul 13, 2026
@yahonda yahonda marked this pull request as draft July 13, 2026 05:55
@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 Jul 13, 2026

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Code Review

This pull request contains a series of updates to various release notes (v2.0.x, v2.1.x, v3.0.x, v4.0.x, v5.0.x). The changes primarily involve fixing grammatical issues, improving phrasing for clarity, and ensuring consistent formatting of issue references. The review comments provided were actionable and identified specific language improvements, such as correcting missing quantifiers and fixing awkward phrasing in the Japanese release notes. All comments were valid and have been incorporated into the summary.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

Comment thread releases/release-2.1.11.md Outdated
Comment thread releases/release-2.1.14.md Outdated
Comment thread releases/release-2.1.17.md Outdated
Comment thread releases/release-2.1.17.md Outdated
Comment thread releases/release-3.0.0-beta.1.md Outdated
@yahonda yahonda force-pushed the fix-ja-pr-link-placement branch 6 times, most recently from 22efde3 to a875484 Compare July 14, 2026 07:04
@yahonda yahonda changed the title i18n(ja): move PR links and author mentions to end of sentence in release notes i18n(ja): comprehensive Japanese language fluency fixes for release notes Jul 14, 2026
@yahonda yahonda marked this pull request as ready for review July 14, 2026 07:09
@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 Jul 14, 2026
@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 Jul 14, 2026
@ti-chi-bot ti-chi-bot Bot added the needs-1-more-lgtm Indicates a PR needs 1 more LGTM. label Jul 14, 2026
@ti-chi-bot

ti-chi-bot Bot commented Jul 14, 2026

Copy link
Copy Markdown

[LGTM Timeline notifier]

Timeline:

  • 2026-07-14 09:08:46.151149873 +0000 UTC m=+704712.187244929: ☑️ agreed by qiancai.

@qiancai

qiancai commented Jul 14, 2026

Copy link
Copy Markdown
Collaborator

@yahonda Would you please resolve conflicts in this PR? Thanks.

@yahonda yahonda force-pushed the fix-ja-pr-link-placement branch 2 times, most recently from 2d02870 to e3121a4 Compare July 15, 2026 01:27
@ti-chi-bot ti-chi-bot Bot added the area/develop This PR relates to the area of TiDB App development. label Jul 15, 2026
@yahonda yahonda force-pushed the fix-ja-pr-link-placement branch 2 times, most recently from 4e43b04 to 902af20 Compare July 15, 2026 01:47
@yahonda yahonda marked this pull request as draft July 15, 2026 01:56
@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 Jul 15, 2026
@yahonda yahonda force-pushed the fix-ja-pr-link-placement branch from 902af20 to 064a4b5 Compare July 15, 2026 02:02
…, 非厳密モード, exchange partition, WHERE句, operator names, etc.)

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
yahonda and others added 8 commits July 15, 2026 11:47
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…; convert katakana-transliterated usernames to @mentions

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…erative, プッシュダウンられ, TiKV panic)

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…binlog)

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@yahonda yahonda force-pushed the fix-ja-pr-link-placement branch from 064a4b5 to 347f8b5 Compare July 15, 2026 02:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/develop This PR relates to the area of TiDB App development. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. needs-1-more-lgtm Indicates a PR needs 1 more LGTM. size/XXL Denotes a PR that changes 1000+ 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