i18n(ja): unify the Japanese term for deploy/deployment (190 files) - #23647
Open
yahonda wants to merge 4 commits into
Open
i18n(ja): unify the Japanese term for deploy/deployment (190 files)#23647yahonda wants to merge 4 commits into
yahonda wants to merge 4 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
|
Important Review skippedToo many files! This PR contains 193 files, which is 43 over the limit of 150. To get a review, reduce the PR to 150 files or fewer by splitting it into smaller PRs or changing its base branch. Upgrade to a paid plan to raise the limit. This review couldn't start because sufficient usage credits or metered capacity aren't available. Add credits or update usage-based reviews in the billing tab, then retry. ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (193)
You can disable this status message by setting the 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 |
Corpus-wide sweep unifying the Japanese rendering of EN deploy/deployment to a single katakana term, while leaving untouched occurrences that correspond to a different English word (expand, roll out, extract, evolve) or the already-unified deployment-topology term.
yahonda
force-pushed
the
fix-ja-deployment-terminology
branch
from
August 28, 2026 02:50
963bac7 to
a87a073
Compare
yahonda
changed the title
Consolidates PR pingcap#23644 (now closed): unifies 展開トポロジー/デプロイメントトポロジー to 展開トポロジ (no long vowel mark), matching the target pages' own H1 titles. 6 files, 2 of which required combining with this PR's own deploy/deployment wording changes on the same lines.
6 tasks
yahonda
force-pushed
the
fix-ja-deployment-terminology
branch
from
August 28, 2026 05:46
e582460 to
116de0f
Compare
- serverless-private-link-connection-to-self-hosted-kafka-in-alicloud.md: unify デプロイ情報 to デプロイメント情報, matching 4 near-identical sibling pages using the same EN sentence.
- production-deployment-using-tiup.md: fix a pre-existing garbled MT artifact (stray デプロイ」のデプロイを fragment) that the mechanical 展開→デプロイ swap left in place, now doubly confusing since it read デプロイ twice back to back.
- hardware-and-software-requirements.md: fix a pre-existing mistranslation where EN's capability ("can be deployed") was stated as a completed fact (デプロイされています instead of デプロイできます).
yahonda
force-pushed
the
fix-ja-deployment-terminology
branch
from
August 28, 2026 05:54
116de0f to
73472b9
Compare
yahonda
marked this pull request as ready for review
August 28, 2026 05:56
ti-chi-bot
Bot
removed
the
do-not-merge/work-in-progress
qiancai
added
translation/no-need
…ja-deployment-terminology # Conflicts: # TOC.md # three-data-centers-in-two-cities-deployment.md # tidb-cloud/serverless-high-availability.md # two-data-centers-in-one-city-deployment.md
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)
Corpus-wide sweep unifying the Japanese rendering of EN "deploy"/"deployment" to a single katakana term, while leaving untouched occurrences that correspond to a different English word (expand, roll out, extract, evolve). Also includes the "deployment topology" term unification (展開トポロジー/デプロイメントトポロジー → 展開トポロジ, no long vowel mark, matching the target pages' own H1 titles), consolidated from #23644 (now closed).
196 files changed, 331 sites converted total.
Which TiDB version(s) do your changes apply to? (Required)
What is the related PR or file link(s)?
AI agent involvement
Do your changes match any of the following descriptions?