Skip to content

i18n(ja): standardize prepared plan cache and prepared statement terminology#23249

Merged
qiancai merged 5 commits into
pingcap:i18n-ja-release-8.5from
yahonda:fix-ja-prepared-plan-cache
Jul 14, 2026
Merged

i18n(ja): standardize prepared plan cache and prepared statement terminology#23249
qiancai merged 5 commits into
pingcap:i18n-ja-release-8.5from
yahonda:fix-ja-prepared-plan-cache

Conversation

@yahonda

@yahonda yahonda commented Jul 13, 2026

Copy link
Copy Markdown
Member

What is changed, added or deleted? (Required)

Standardize Japanese translations of "Prepared Plan Cache" and "Prepared Statement" terminology across ~33 files:

  • 準備済みプランキャッシュ / 準備されたプランキャッシュ / プラン準備キャッシュ → プリペアドプランキャッシュ
  • 準備済み実行プランキャッシュ / 準備された実行プランキャッシュ → プリペアドプランキャッシュ
  • 準備されていないプランキャッシュ / 未準備SQLプランキャッシュ / 未準備実行プランキャッシュ → 非プリペアドプランキャッシュ
  • 準備済みステートメント / 準備されたステートメント / 準備ステートメント → プリペアドステートメント
  • 非準備済みステートメント / 未準備ステートメント → 非プリペアドステートメント
  • プランキャッシュの準備 / 実行プランキャッシュを準備する → プリペアドプランキャッシュ
  • 準備済みですか? → Is Prepared? (UI label, original English)

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)?

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

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 do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. area/develop This PR relates to the area of TiDB App development. labels Jul 13, 2026
@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 overvenus 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/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Jul 13, 2026
gemini-code-assist[bot]
gemini-code-assist Bot reviewed Jul 13, 2026
View reviewed changes

@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 standardizes terminology across various Japanese documentation files, replacing outdated or inconsistent terms with "プリペアドプランキャッシュ" (Prepared Plan Cache), "非プリペアドプランキャッシュ" (Non-Prepared Plan Cache), and "プリペアドステートメント" (Prepared Statement). The review comments provide valuable feedback to ensure grammatical correctness, natural Japanese phrasing, and terminology consistency across all updated files.

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 develop/dev-guide-prepared-statement.md Outdated
Comment thread releases/release-7.1.0.md Outdated
Comment thread releases/release-7.1.0.md Outdated
Comment thread releases/release-7.1.0.md Outdated
Comment thread releases/release-7.1.0.md Outdated
Comment thread releases/release-7.4.0.md Outdated
Comment thread tidb-cloud/tidb-cloud-sql-tuning-overview.md Outdated
Comment thread system-variables.md
Comment thread performance-tuning-methods.md Outdated
@yahonda yahonda force-pushed the fix-ja-prepared-plan-cache branch 2 times, most recently from eaa0b54 to f7ad32b Compare July 13, 2026 02:04
yahonda added 3 commits July 13, 2026 11:05
@yahonda
i18n(ja): standardize prepared plan cache terminology
1a75ab9 
- 準備済みプランキャッシュ/準備されたプランキャッシュ/プラン準備キャッシュ → プリペアドプランキャッシュ
- 準備済み実行プランキャッシュ/準備された実行プランキャッシュ → プリペアドプランキャッシュ
- 準備されていないプランキャッシュ/未準備プランキャッシュ → 非プリペアドプランキャッシュ
- プランキャッシュの準備/実行プランキャッシュを準備する → プリペアドプランキャッシュ
@yahonda
i18n(ja): standardize prepared statement terminology
2d32de6 
- 準備済みステートメント/準備されたステートメント/準備ステートメント → プリペアドステートメント
- 非準備済みステートメント/未準備ステートメント → 非プリペアドステートメント
- 準備されたステートメントプランキャッシュ → プリペアドステートメントプランキャッシュ
@yahonda
i18n(ja): use original English for config params and UI labels
cf84851 
- キャッシュ準備ステートメント → cachePrepStmts
- 準備済みですか?/プランはキャッシュからですか?/プランはバインディングからですか? → Is Prepared?/Is Plan from Cache?/Is Plan from Binding?
@yahonda yahonda force-pushed the fix-ja-prepared-plan-cache branch from f7ad32b to cf84851 Compare July 13, 2026 02:07
@yahonda yahonda marked this pull request as ready for review July 13, 2026 02:13
@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 13, 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:10:38.430975067 +0000 UTC m=+704824.467070124: ☑️ agreed by qiancai.

@qiancai qiancai merged commit 60a30e1 into pingcap:i18n-ja-release-8.5 Jul 14, 2026
3 of 8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@qiancai qiancai qiancai approved these changes
+1 more reviewer
@gemini-code-assist gemini-code-assist[bot] gemini-code-assist[bot] left review comments
Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

area/develop This PR relates to the area of TiDB App development. needs-1-more-lgtm Indicates a PR needs 1 more LGTM. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. translation/no-need No need to translate this PR.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@yahonda @qiancai