i18n(ja): unify the Japanese rendering of "execution plan" - #23408
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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. Comment |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
9b24f94 to
bc45fbe
Compare
|
@yahonda, could you please resolve conflicts in this PR? Thanks. |
bc45fbe to
6d9dd97
Compare
|
Rebased. |
|
@yahonda, sorry to bother you again. It looks like there are new conflicts in this PR. Could you please take a look? Thanks! |
eea8ba4 to
04b6d2f
Compare
|
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.
04b6d2f to
21afd40
Compare
[LGTM Timeline notifier]Timeline:
|
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)
What is the related PR or file link(s)?