i18n(ja): unify generated column terminology - #23461
Conversation
|
Skipping CI for Draft Pull Request. |
ti-chi-bot
Bot
added
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
63c8eb4 to
e3badf3
Compare
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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 |
e3badf3 to
8e5035f
Compare
The English term "generated column(s)" was rendered three different ways
in Japanese: one form (85 occurrences), a longer descriptive form (82,
~50/50 split with the first), and a katakana form (7, outliers). The
compound terms for virtual/stored generated columns already locked in the
first (shorter) form, so unify everything to that, including the
generated-columns.md H1/H2 headings (anchors unchanged, they are explicit
{#...} tags derived from English). 58 files changed, 174 occurrences of the
target form after (up from 85), 0 remaining of the other two forms.
Also fixes defects surfaced while touching these lines:
- develop/dev-guide-create-table.md: the term's own noun repeated
immediately after itself ("generated-column column-clause") where the
English says "generated column clauses" (one column, not two).
- develop/dev-guide-schema-design-overview.md and
tidb-cloud/database-schema-concepts.md (identical broken sentence in
both): a dropped word left "some " dangling with nothing after it, and
the two link targets in the next clause were concatenated with no
particle and no verb attached to the first one. Restored the missing
word and both particles to match the English two-sentence structure.
- releases/release-6.0.0-dmr.md and releases/release-8.5.0.md: the blanket
substitution broke grammar in two release notes that used the adverbial
form "virtually [passive-verb] column" -- after swapping the verb phrase
for the noun compound, the adverb was left modifying a bare noun with
nothing to attach to. Fixed by using the "virtual generated column"
compound noun instead of the adverb + noun construction.
- optimizer-fix-controls.md: restored a dropped particle before a verb
that follows a link (pre-existing, not introduced by the substitution).
- Unified a second, unrelated three-way split for "stored generated
column": generated-columns.md itself used a verbal/relative-clause form
in one section while using the noun-compound form (matching "virtual
generated column") elsewhere in the same document, and a bare form that
drops "generated" entirely in its opening paragraph, losing precision.
A sibling TiDB Cloud doc used yet another kanji spelling for "stored".
Unified all of these, plus two release notes and a TiCDC FAQ entry that
used the same verbal form, to the dominant noun-compound form -- now
internally consistent with "virtual generated column" throughout.
- ticdc/ticdc-open-protocol.md: translated a table's English column
headers (Bit/Value/Name) that were left untranslated next to an already-
translated header (Description) in the same row.
8e5035f to
4713b9b
Compare
ti-chi-bot
Bot
removed
the
do-not-merge/work-in-progress
1 participant
What is changed, added or deleted? (Required)
Unifies the Japanese rendering of the English term "generated column(s)," which was split three ways across the corpus: a short form (85 occurrences), a longer descriptive form (82, roughly a 50/50 split with the short form), and a katakana form (7, outliers). The compound terms for virtual/stored generated columns already used the short form exclusively, so this PR unifies everything to match.
Also updates
generated-columns.md's H1 and one H2 heading, which were themselves internally inconsistent. Anchors are explicit{#...}tags derived from the English source and are unchanged.58 files changed, 174 occurrences of the unified term afterward (up from 85), 0 remaining of the other two forms.
Additional defects fixed while touching these lines:
develop/dev-guide-create-table.md: a duplicated 列 ("generated-column column-clause" instead of "generated column clause").develop/dev-guide-schema-design-overview.mdandtidb-cloud/database-schema-concepts.md: a dropped word and two missing particles in an identical broken sentence in both files.releases/release-6.0.0-dmr.mdandreleases/release-8.5.0.md: the mechanical substitution broke grammar in two release notes using an adverb + passive-verb construction; fixed by using the established "virtual generated column" compound noun instead.optimizer-fix-controls.md: restored a pre-existing dropped particle before a verb following a link.generated-columns.mditself (internally inconsistent) plus two release notes and a TiCDC FAQ entry — unified to the noun-compound form, matching "virtual generated column."ticdc/ticdc-open-protocol.md: translated a table's English column headers (Bit/Value/Name) left untranslated next to an already-translated header (Description) in the same row.Which TiDB version(s) do your changes apply to? (Required)
What is the related PR or file link(s)?
N/A
AI agent involvement
Do your changes match any of the following descriptions?