Skip to content

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

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

i18n(ja): comprehensive Japanese language fluency fixes for release notes#23254
yahonda wants to merge 4 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 fixes across all release notes (v2.0 to v8.5) and documentation files. Categories of fixes:

  1. Extraneous がで patterns: Removed extraneous で after が (~60 occurrences across 32 files)
  2. Particle fixes: Fixed double particles (がに, をに, はで, がと, がの, etc.) and added missing particles (てにをは)
  3. GitHub mention cleanup: Moved inline GitHub @mentions and issue/PR references to end of sentences. Replaced katakana-transcribed GitHub usernames with proper @mention format (e.g., ヤンケオ→@ YangKeao)
  4. Terminology standardization:
    • ポイント取得/ポイントゲット/ポイント獲得→PointGet
    • バッチPointGet/バッチポイント取得→Batch PointGet
    • カルテシアン→直積/直積結合
    • 動的トリミング→動的プルーニング
    • 非厳密な→非厳密モード
    • トゥームストーン→tombstone
    • 概要ログ→一般ログ
    • S3storage→S3ストレージ
    • 学習ノード→ラーナーノード
    • 節→句 (SQL clauses)
    • 領域→リージョン (TiKV regions)
    • 種類→型 (data types)
  5. Verb fixes: Panic→がpanicする/をpanicさせる, fixed imperative forms (してください→する)
  6. Word order and sentence structure: Fixed various unnatural word orders and broken sentence structures
  7. Release-8.5.x review fixes: Fixed code span transpositions, missing predicates, and terminology errors based on English original verification

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
- Pump
- 利用可能なbinlogスペースを制限するための`stop-write-at-available-space`設定項目を追加します[#659](https://github.com/pingcap/tidb-binlog/pull/659)
- LevelDB L0ファイルの数が[#648](https://github.com/pingcap/tidb-binlog/pull/648)の場合にガベージコレクターが動作しないことがある問題を修正しました。
- LevelDB L0ファイルの数がの場合にガベージコレクターが動作しないことがある問題を修正しました。 [#648](https://github.com/pingcap/tidb-binlog/pull/648)

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.

high

「LevelDB L0ファイルの数が場合に」という表現は、形容詞(多い)が抜けており、日本語として不自然です。元の英文リリースノート("when the number of LevelDB L0 files is large")に合わせて「数が多い場合に」に修正することをお勧めします。

Suggested change
- LevelDB L0ファイルの数がの場合にガベージコレクターが動作しないことがある問題を修正しました。 [#648](https://github.com/pingcap/tidb-binlog/pull/648)
- LevelDB L0ファイルの数が多い場合にガベージコレクターが動作しないことがある問題を修正しました。 [#648](https://github.com/pingcap/tidb-binlog/pull/648)

Comment thread releases/release-2.1.17.md Outdated
Comment thread releases/release-2.1.17.md Outdated
- ノード[#5277](https://github.com/tikv/tikv/pull/5277)再起動によって発生するジッターを軽減するために起動プロセスを最適化します。
- 場合によってはロック解決プロセスを最適化して、トランザクション[#5339](https://github.com/tikv/tikv/pull/5339)ロック解決を高速化します。
- ノード再起動によって発生するジッターを軽減するために起動プロセスを最適化します。 [#5277](https://github.com/tikv/tikv/pull/5277)
- 場合によってはロック解決プロセスを最適化して、トランザクションロック解決を高速化します。 [#5339](https://github.com/tikv/tikv/pull/5339)

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.

low

「トランザクションロック解決」という表現は、助詞の「の」が抜けており、日本語として少し不自然です。「トランザクションのロック解決」に修正することをお勧めします。

Suggested change
- 場合によってはロック解決プロセスを最適化して、トランザクションロック解決を高速化します[#5339](https://github.com/tikv/tikv/pull/5339)
- 場合によってはロック解決プロセスを最適化して、トランザクションのロック解決を高速化します[#5339](https://github.com/tikv/tikv/pull/5339)

Comment thread releases/release-3.0.0-beta.1.md Outdated
@yahonda yahonda force-pushed the fix-ja-pr-link-placement branch 5 times, most recently from b3da95a to 22efde3 Compare July 14, 2026 07:01
yahonda added 2 commits July 14, 2026 16:03
- Remove extraneous がで patterns (~60 occurrences)
- Fix double particles (がに, をに, はで, がと, がの, etc.)
- Add missing particles (てにをは)
- Fix word order, sentence structure, and missing objects
- Standardize terminology (非厳密モード, プルーニング, 直積, 直積結合)
- Fix 節→句 for SQL clauses, 領域→リージョン, 種類→型
- Move inline GitHub @mentions and issue refs to end
- Replace katakana GitHub handles with proper @mentions
- Fix TiKV/TiDB/PD panic→がpanicする/をpanicさせる
- Fix PDLeader→PD Leader spacing, 概要ログ→一般ログ
- Fix 学習者→ラーナー, Redactログ→ログの秘匿化
- Fix non-past tense (修正する→修正しました)
- Apply review fixes for release-8.5.x lines
- PointGet/Batch PointGet terminology (latency-breakdown.md, glossary.md)
- カルテシアン→直積 (explain-subqueries.md, dashboard-diagnostics-usage.md)
- トゥームストーン→tombstone (tikv-configuration-file.md, tikv-control.md, etc.)
- Remove 目 from column references (multiple doc files)
@yahonda yahonda force-pushed the fix-ja-pr-link-placement branch 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.

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/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