Skip to content

i18n(ja): unify the Japanese rendering of "execution plan" - #23408

Merged
qiancai merged 2 commits into
pingcap:i18n-ja-release-8.5from
yahonda:i18n-ja-execution-plan-term
Aug 5, 2026
Merged

i18n(ja): unify the Japanese rendering of "execution plan"#23408
qiancai merged 2 commits into
pingcap:i18n-ja-release-8.5from
yahonda:i18n-ja-execution-plan-term

Conversation

@yahonda

@yahonda yahonda commented Aug 3, 2026

Copy link
Copy Markdown
Member

What is changed, added or deleted? (Required)

Standardizes the Japanese rendering of "execution plan" to 実行計画 (the established Japanese database term, matching the Oracle / PostgreSQL / SQL Server Japanese documentation) instead of the transliteration 実行プラン, which was the previous majority but not the conventional term.

Changed

  • 実行プラン実行計画 (execution plan)
  • クエリ実行プランクエリ実行計画 (query execution plan — still an execution plan; only the プラン/計画 spelling is unified, "query" is preserved)

Deliberately NOT changed

  • クエリプラン (query plan): kept as-is. The English source distinguishes "query plan" (the optimizer's intermediate plan structure) from the final "execution plan" — e.g. sql-optimization-concepts.md: "TiDB obtains a query plan structure … and then obtains a final execution plan". Merging them would conflate two different concepts.
  • 実行プランキャッシュ / 実行プランバインディング (plan cache / plan binding): excluded. These are separate terms with their own dominant standalone forms (プランキャッシュ, プランバインディング); unifying them here would create a new inconsistency. Left to their own future sweeps.

Section {#...} anchors are English-derived and unchanged, so all inbound links keep resolving.

Scope: 190 files (includes releases/, since this is pure term unification and unrelated to sentence structure).

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

  • master (the latest development version)
  • v8.5 (TiDB 8.5 versions)

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

@coderabbitai

coderabbitai Bot commented Aug 3, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 9e4b224b-4de5-469a-bae1-1b00942cb41e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

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 area/develop This PR relates to the area of TiDB App development. label Aug 3, 2026
@ti-chi-bot

ti-chi-bot Bot commented Aug 3, 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 missing-translation-status This PR does not have translation status info. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Aug 3, 2026
@yahonda yahonda changed the title i18n(ja): unify the term for "execution plan" to 実行計画 i18n(ja): unify the Japanese rendering of "execution plan" Aug 3, 2026
@yahonda
yahonda force-pushed the i18n-ja-execution-plan-term branch from 9b24f94 to bc45fbe Compare August 3, 2026 02:28
@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 Aug 3, 2026
@qiancai

qiancai commented Aug 3, 2026

Copy link
Copy Markdown
Collaborator

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

@yahonda
yahonda force-pushed the i18n-ja-execution-plan-term branch from bc45fbe to 6d9dd97 Compare August 4, 2026 00:48
@yahonda

yahonda commented Aug 4, 2026

Copy link
Copy Markdown
Member Author

Rebased.

@qiancai

qiancai commented Aug 4, 2026

Copy link
Copy Markdown
Collaborator

@yahonda, sorry to bother you again. It looks like there are new conflicts in this PR. Could you please take a look? Thanks!

@yahonda
yahonda force-pushed the i18n-ja-execution-plan-term branch 2 times, most recently from eea8ba4 to 04b6d2f Compare August 4, 2026 03:00
@yahonda

yahonda commented Aug 4, 2026

Copy link
Copy Markdown
Member Author

Rebased.

Standardize the Japanese rendering of "execution plan" to 実行計画 (the
established Japanese database term, matching Oracle/PostgreSQL/SQL Server JP
docs) instead of the transliteration 実行プラン.

- 実行プラン -> 実行計画 (execution plan)
- クエリ実行プラン -> クエリ実行計画 (query execution plan; still an execution
  plan, only the プラン/計画 spelling is unified)

Deliberately NOT changed:
- クエリプラン (query plan): kept as-is. The English source distinguishes
  "query plan" (the optimizer's intermediate plan structure) from the final
  "execution plan" (e.g. sql-optimization-concepts.md), so merging them would
  conflate two different concepts.
- 実行プランキャッシュ / 実行プランバインディング (plan cache / plan binding):
  excluded. These are separate terms with their own dominant standalone forms
  (プランキャッシュ, プランバインディング); unifying them here would create a
  new inconsistency. Left to their own future sweeps.
@yahonda
yahonda force-pushed the i18n-ja-execution-plan-term branch from 04b6d2f to 21afd40 Compare August 4, 2026 06:35
@ti-chi-bot ti-chi-bot Bot added the needs-1-more-lgtm Indicates a PR needs 1 more LGTM. label Aug 5, 2026
@ti-chi-bot

ti-chi-bot Bot commented Aug 5, 2026

Copy link
Copy Markdown

[LGTM Timeline notifier]

Timeline:

  • 2026-08-05 12:20:19.224448556 +0000 UTC m=+2617005.260543622: ☑️ agreed by qiancai.

@qiancai
qiancai merged commit b028115 into pingcap:i18n-ja-release-8.5 Aug 5, 2026
2 of 6 checks passed
@yahonda
yahonda deleted the i18n-ja-execution-plan-term branch August 6, 2026 00:30
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. 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