i18n(ja): unify configuration file/parameter terminology - #23828
Closed
yahonda wants to merge 7 commits into
Closed
Conversation
ti-chi-bot
Bot
added
the
area/develop
|
Important Review skippedToo many files! This PR contains 265 files, which is 115 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: Advanced Run ID: 📒 Files selected for processing (265)
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 |
|
[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
yahonda
marked this pull request as draft
September 11, 2026 01:24
ti-chi-bot
Bot
added
the
do-not-merge/work-in-progress
yahonda
changed the title
Unifies the 3-way (4-way for "parameter", counting the long-vowel variant) split rendering of "configuration file" and "configuration parameter", consistent with the already-decided configuration item/ parameter/option compound direction (PR pingcap#23596). 512 occurrences/227 files, line-count-symmetric diff. Heading anchors (English-derived) unchanged, only visible text updated. Out of scope, left untouched: the standalone "configuration item" form and other smaller compounds, and configuration-word usages in unrelated senses. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
yahonda
force-pushed
the
fix-config-3rd-form
branch
from
September 11, 2026 01:25
a1b8066 to
6c79299
Compare
Expands the previous commit's scope to the rest of the corpus: item, flag, option, guide, method, and other small compounds, plus bare standalone use in headings, TOC labels, and prose. 193 occurrences/83 files. Two sites handled as manual exceptions rather than a straight substitution: - tidb-upgrade-migration-guide.md: a checklist bullet's label was itself the compound term, which would have produced a duplicated word if substituted literally; shortened to match sibling bullets' label style instead. - tidb-cloud/csv-config-for-import-data.md: kept this file's own already-established term instead, since its H1/summary/title all independently agree on it and substituting here would have left the file self-contradictory rather than more consistent. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
The Resource Manager page's Configuration/Estimate Capacity/Metrics section names are literal TiDB Dashboard UI labels (verified against pingcap/tidb-dashboard's own en.yaml translation file), not generic prose to translate. The previous commit in this branch had converted this file's Configuration bullet from a katakana rendering to Japanese, which was the wrong direction for a UI-literal label; Estimate Capacity and Metrics had similar pre-existing issues unrelated to this branch. Fixes both headings, the section-list bullets, one internal cross-reference link, and the frontmatter summary that names all three sections. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…data-migration.md "Required value" and "Why" were rendered as a literal compound noun and a bare interrogative word, respectively, neither of which reads naturally as a table header in Japanese. Changed to the standard forms used elsewhere in the corpus for this kind of column. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
- deploy-monitoring-services.md: the previous commit had converted
this file's Configuration reference from katakana to Japanese, but
it names a literal Grafana UI sidebar section ("Configuration"),
verified against the EN source's own bolded literal English.
- dynamic-config.md: the dynamic TiKV config item table's first row
showed the literal config key `log.level` translated into Japanese
prose ("ログレベル"), unlike every other row in the same table
(and the equivalent PD table elsewhere in this file), which
correctly show the literal backtick-quoted key name.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
"Application" here means the deployment use case/scenario (column values are OLTP, HTAP, TiCDC replication, etc.), but was translated as the "applied skill/theory" sense of the word, which reads oddly next to values like "OLTP" and "HTAP". Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…ed form The bulk configuration-term substitution in an earlier commit correctly converted the prefix but left one katakana synonym for "item" untouched, missing that the corpus's established rendering uses a different (kanji) word for "item" per the existing PR pingcap#23596 precedent. 4 sites/3 files. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
yahonda
force-pushed
the
fix-config-3rd-form
branch
from
September 11, 2026 02:29
2ba9d51 to
36f805c
Compare
yahonda
marked this pull request as ready for review
September 11, 2026 02:32
ti-chi-bot
Bot
removed
the
do-not-merge/work-in-progress
This was referenced Sep 11, 2026
Member
Author
|
Splitting this PR into two smaller PRs to stay under CodeRabbit's 150-file review limit (this PR grew to 265 files across 7 review-driven follow-up commits, 115 over the limit):
Both are byte-identical to this PR's final content for their respective file subsets. Closing in favor of the two split PRs. |
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
1 participant
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.
First-time contributors' checklist
What is changed, added or deleted? (Required)
Unifies the multi-way split rendering of "configuration" (file, parameter, item, flag, option, and other compounds, plus standalone/bare use) across the corpus, consistent with the already-decided direction for configuration item/parameter/option compounds (PR #23596).
First commit — file/parameter axis:
コンフィグレーションファイル→設定ファイル(166 occurrences)構成ファイル→設定ファイル(343 occurrences)コンフィグレーションパラメータ→設定パラメータ(37 occurrences)設定パラメーター(long-vowel variant) →設定パラメータ(settled independently: corpus-wideパラメータvsパラメーターis 2315 vs 133, ~95% no long vowel)Second commit — everything else (item/flag/option/guide/method/other compounds, plus bare standalone use in headings, TOC labels, and prose):
512 + 193 = 705 occurrences / ~300 files total, all line-count-symmetric diffs. Heading anchors (English-derived, e.g.
{#configuration}) are unchanged — only the visible text was updated.Two sites were handled as manual exceptions rather than a straight substitution:
tidb-upgrade-migration-guide.md: a checklist bullet's label was itself the compound term, which would have produced a duplicated word if substituted literally; shortened to match sibling bullets' label style instead.tidb-cloud/csv-config-for-import-data.md: kept this file's own already-established term instead, since its H1/summary/title all independently agree on it and substituting here would have left the file self-contradictory rather than more consistent.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?