i18n(ja): unify configuration item/parameter/option terminology - #23596
Open
yahonda wants to merge 1 commit into
Open
i18n(ja): unify configuration item/parameter/option terminology#23596yahonda wants to merge 1 commit into
yahonda wants to merge 1 commit into
Conversation
|
Important Review skippedToo many files! This PR contains 197 files, which is 47 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 (197)
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 |
ti-chi-bot
Bot
added
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
the
size/XXL
yahonda
added a commit
to yahonda/docs
that referenced
this pull request
Aug 25, 2026
…notes - release-2.0.9.md: 構成→設定 for "configuration" (matches the pingcap#23596 direction decision) - release-2.1-rc.1.md: 3 missing を/の particles, plus fixed scrambled word order in the Scope-check bullet
yahonda
added a commit
to yahonda/docs
that referenced
this pull request
Aug 25, 2026
- release-6.5.10.md/7.1.6.md/7.5.2.md: rewrote a heavily garbled paragraph (spurious ordinal 目/件目 counters, a fabricated "13件目", dangling してください with no governing verb) to match the English source's TiCDC UPDATE-split-behavior description (pingcap#10918) - ticdc/ticdc-split-update-behavior.md: removed a stray つ inserted after every `DELETE`と`INSERT` mention (6 sites) - release-7.1.0.md, release-7.1.3.md: removed spurious unclosed full- width parentheses not present in the English source - release-7.5.4.md: fixed a garbled trailing clause ("in some cases") that had become a dangling 場合） with an unmatched parenthesis - release-6.5.12.md/7.5.5.md/8.1.2.md: fixed duplicated の (負のの→負の) - release-8.1.1.md: misleading imperative 変更してください→変更します (describes a change TiDB itself made, not a user instruction) - release-6.5.3.md: a literal BR error-message string ("resolve lock timeout") had been translated into Japanese, misrepresenting what actually appears in the tool's output; restored to the literal string - release-6.5.11.md/7.1.6.md/7.5.3.md: 構成項目→設定項目 for the same referent repeated two sentences later as 設定項目 (matches the pingcap#23596 direction; these release-note files were missed by that sweep)
qiancai
added
translation/no-need
yahonda
force-pushed
the
fix-config-item-term-unification
branch
2 times, most recently
from
August 26, 2026 01:56
317b882 to
9c3cb66
Compare
Rebased onto i18n-ja-release-8.5 after pingcap#23602 merged the markdownlint conformance fixes. Also escaped a literal multiplication asterisk formula in statement-summary-tables.md that was already failing MD037 in the pre-rebase branch (same class of issue as pingcap#23605's cost-model.md fix), matching how the English source escapes it.
yahonda
force-pushed
the
fix-config-item-term-unification
branch
from
August 27, 2026 04:33
9c3cb66 to
5afb637
Compare
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)
The English source consistently uses "configuration item" (954 occurrences), "configuration parameter" (84), and "configuration option" (25). The Japanese translation had split each into two competing renderings of "configuration" — 構成 vs 設定 — with no dominant form and no semantic distinction between the two.
Unifies to 設定, matching the already-fully-consistent rendering of "system variable" (システム変数, 1334 occurrences, no competing form):
442 occurrences changed across 193 files. Verified 0 remaining occurrences of the old forms, and that this only touches these three exact compound terms — bare 構成 used in unrelated senses (e.g. cluster/architecture "構成", as in クラスター構成) is untouched.
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?