i18n(ja): replace katakana product names with English equivalents#23107
i18n(ja): replace katakana product names with English equivalents#23107yahonda wants to merge 19 commits into
Conversation
|
Skipping CI for Draft Pull Request. |
ti-chi-bot
Bot
added
the
do-not-merge/work-in-progress
|
[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
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request unifies product name notations and terminology across various Japanese documentation files, updating terms like 'セルフマネージド' to 'Self-Managed', 'プレイグラウンド' to 'Playground', 'プレミアム' to 'Premium', and 'スターター' to 'Starter'. The review feedback points out several minor issues, including broken anchor links, grammatically incomplete or unnatural Japanese sentences, duplicate word typos (such as '本番本番', 'スタート', and 'TiUPTiUPグラウンド'), inconsistent capitalization of 'TiDB', missing backticks for command names, and a few remaining terminology inconsistencies that should be updated to match the PR's overall goal.
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.
yahonda
force-pushed
the
i18n-ja-fix-product-name-katakana
branch
from
d02fddd to
34bfcba
Compare
i18n(ja): replace レッドハットEnterpriseリナックス with Red Hat Enterprise Linux revert: keep エンタープライズデータ as katakana i18n(ja): fix TiDBEnterprise spacing and revert Enterprise data fix: TiDB エンタープライズ → TiDB Enterprise i18n(ja): fix Enterprise/エンタープライズ distinction and other fixes
yahonda
force-pushed
the
i18n-ja-fix-product-name-katakana
branch
from
6d7d123 to
0abc280
Compare
fix: ステートメントを支持する → サポートする fix: 行政ステートメント → 管理ステートメント fix: Security → セキュリティ in general noun context fix: address gemini-code-assist review comments fix: Self-ManagedAPI → Self-Managed API fix: セントOS → CentOS fix: remove 。 inside link brackets fix: Enterpriseユーザー → エンタープライズユーザー (general noun) fix: standardize storage type names fix: パフォーマンス/プラス → Performance/Plus in body text fix: remaining issues from final review
yahonda
force-pushed
the
i18n-ja-fix-product-name-katakana
branch
2 times, most recently
from
1a2a48b to
2336384
Compare
ti-chi-bot
Bot
removed
the
do-not-merge/work-in-progress
1 participant
What is changed, added or deleted? (Required)
Unified Japanese documentation terminology across 300 files by replacing katakana product/plan names with English equivalents and fixing various translation issues.
Product name notation fixes:
Enterprise/エンタープライズ distinction:
Terminology fixes:
Command/component names:
Punctuation and formatting fixes:
pessimistic-txn。max-retry-count→pessimistic-txn.max-retry-countWhich 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?