i18n(ja): standardize SQL statement H1 headings to English and fix unnatural translations#23148
Open
yahonda wants to merge 24 commits into
Open
i18n(ja): standardize SQL statement H1 headings to English and fix unnatural translations#23148yahonda wants to merge 24 commits into
yahonda wants to merge 24 commits into
Conversation
ti-chi-bot
Bot
added
the
area/develop
|
[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 |
ti-chi-bot
Bot
added
missing-translation-status
ti-chi-bot
Bot
added
the
do-not-merge/work-in-progress
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Code Review
This pull request updates Japanese terminology across several documentation files, changing "文字通りの値" to "リテラル値" (literal values) and "生きる時間" to "存続時間" (TTL). The review feedback suggests adding a grammatical particle between adjacent markdown links in the release notes to improve readability, and replacing the non-standard term "消去" with the standard SQL keyword "DELETE" for technical accuracy.
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.
Replace Japanese-translated H1 headings in all 140 sql-statement
reference pages with the canonical English SQL syntax names, matching
the release-8.5 EN source format exactly (including backtick-wrapping
for keywords like `CALIBRATE RESOURCE`).
The anchor IDs ({#add-column}, etc.) are preserved.
- JSONタイプ/ベクトルタイプ → JSON型/ベクトル型 - 文字セットと照合 → 文字セットと照合順序 (TOC, basic-features, etc.) - 生きる時が来た → 存続時間（TTL） (system-variables.md x9) - 見えない/目に見えないインデックス → 非表示インデックス (6 files) - 複合PRIMARY KEY → 複合主キー - stray 表示 removal in release-8.0.0.md
yahonda
changed the title
ti-chi-bot
Bot
added
size/XL
Align with the official PingCAP Japanese documentation (https://docs.pingcap.com/ja/tidb/stable/sql-statement-alter-index/) which uses 不可視インデックス for 'invisible index'.
ti-chi-bot
Bot
added
size/XXL
yahonda
force-pushed
the
i18n-ja-fix-unnatural-translations
branch
from
c1c9b45 to
fa15bfb
Compare
yahonda
force-pushed
the
i18n-ja-fix-unnatural-translations
branch
from
5dcddac to
45d7366
Compare
ti-chi-bot
Bot
added
size/XL
yahonda
force-pushed
the
i18n-ja-fix-unnatural-translations
branch
from
4d7f850 to
b77027f
Compare
i18n(ja): 非表示/目に見えない→不可視 in release-8.0.0 (clean)
i18n(ja): 非表示 → 不可視 in index management best practices i18n(ja): 非表示 → 不可視 in index-management-best-practices.md i18n(ja): 非表示→不可視 in invisible index verb contexts (8 occurrences)
yahonda
force-pushed
the
i18n-ja-fix-unnatural-translations
branch
from
b77027f to
0ec8e83
Compare
yahonda
added a commit
to yahonda/docs
that referenced
this pull request
Jun 26, 2026
Reverted files that had overlapping 非表示→不可視 changes: - releases/release-5.0.0-rc.md - releases/release-8.0.0.md - sql-statement-alter-index.md - sql-statement-create-index.md - best-practices/index-management-best-practices.md Preserved unique PR pingcap#23145 changes (タイプ→型) in system-variables.md
yahonda
force-pushed
the
i18n-ja-fix-unnatural-translations
branch
from
fd71755 to
d5dab89
Compare
- MODIFY COLUMN → 再編成データ (for #reorg-data-change anchor) - CREATE INDEX → 複数値インデックスを作成する (for #create-multi-valued-indexes) - ALTER USER → ユーザーにバインドされているリソースグループを変更する - Remove stray CREATE word in resource-control-ru-groups.md
ti-chi-bot
Bot
removed
the
do-not-merge/work-in-progress
The link text was `VEC_COSINE_DISTANCE()()` instead of `VEC_COSINE_DISTANCE()`.
ti-chi-bot
Bot
removed
the
missing-translation-status
qiancai
approved these changes
Jun 29, 2026
[LGTM Timeline notifier]Timeline:
|
Collaborator
|
@yahonda Would you please resolve conflicts in this PR? Thanks. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is changed, added or deleted? (Required)
Fix unnatural Japanese translations, standardize terminology, and clean up broken link formats across the i18n-ja docs. Changes are organized by category below.
1. Time to Live translations
Three related literal/unnatural translations of "Time to Live" are fixed:
生きる時間 → 存続時間 (4 files): "Time to Live" was literally translated as "生きる時間" (living time). Changed to "存続時間" (lifetime/duration), which is the standard term used in the time-to-live.md page itself.
Affected: basic-features.md, TOC.md, tidb-cloud/releases/release-notes-2024.md, develop/dev-guide-delete-data.md
生きる時が来た → 存続時間（TTL） (4 occurrences in system-variables.md): A different broken phrasing where "時が来た" (time has come) was used in TTL link text. Replaced with the canonical Japanese name "存続時間（TTL）".
2. リテラル値 (Literal values)
文字通りの値 → リテラル値 (5 files): "Literal values" was translated as "文字通りの値" (literal/word-for-word value). Changed to "リテラル値", which is the standard programming term (カタカナ) used in the literal-values.md page summary itself.
Affected: TOC.md, TOC-tidb-cloud.md, TOC-tidb-cloud-starter.md, TOC-tidb-cloud-premium.md, TOC-tidb-cloud-essential.md
3. Collation (照合) terminology
4. SQL type name consistency
5. Invisible index terminology (非表示 → 不可視)
The MySQL term "invisible index" is being standardized to use 不可視 (invisible) rather than 非表示 (hidden) for accuracy. "Invisible" is the established MySQL term, and the EN source uses "invisible".
6. Expression index translation
7. SQL statement H1 headings to English
Many SQL statement page titles were translated into Japanese (e.g., "テーブルを作成" for
CREATE TABLE). Standardized to use the English statement name (e.g.,CREATE TABLE), matching the EN source and the toc.md file paths. ~80 files updated.Affected: all
sql-statements/sql-statement-*.mdfiles plustoc.md.8. Section heading consistency
9. SQL statement terminology
DROPor other operations.10. Other prose cleanups
文characters that were left over from broken edits.11. Broken link formats
VEC_COSINE_DISTANCE()()→VEC_COSINE_DISTANCE()(ai/integrations/vector-search-auto-embedding-overview.md): The link text had an extra pair of parentheses from a botched edit.表示 ユーザーの作成→[ユーザーの作成を表示](sql-statement-show-create-user.md): Fixed a link that was missing the surrounding brackets.[グローバル|セッション]バインディング →[[グローバル|セッション]バインディングの作成](create-binding.md and others): Added the missing outer brackets to make the bracketed-group section name a proper link.Which TiDB version(s) do your changes apply to? (Required)
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?