i18n(ja): fix mistranslated function-name headings and misc defects - #23512
i18n(ja): fix mistranslated function-name headings and misc defects#23512yahonda wants to merge 1 commit into
Conversation
|
Skipping CI for Draft Pull Request. |
|
[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 |
|
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 |
Found via a deeper content-level indentation check (comparing every line inside every fenced block against the English source, not just the fence markers themselves) run while reviewing this PR: - pd-control.md: 8 closing/opening brace lines inside JSON example blocks ended up mis-indented by this batch's own fix pass (some were already correctly indented before this batch touched the file and got de-indented in the process; others were left with a stale leading indent on just the first line of a block). All now match the English source's indentation exactly. - performance-tuning-methods.md: fix one missing を particle (`close`呼び出します -> `close`を呼び出します) found in the same file while re-checking it. Verified via an exhaustive fenced-block content diff against the English source across all 37 files in this PR: 0 remaining mismatches. Also verified no merge conflicts against the other open i18n-ja-release-8.5 PRs (pingcap#23509, pingcap#23511, pingcap#23512).
Found via user spot-checks across the current i18n-ja-release-8.5
branch; fixed every confirmed defect and swept the corpus for
recurrences of each pattern.
- Restore literal English SQL function names in headings that had
been mistranslated as Japanese prose (SLEEP() -> 寝る(), VALUES() ->
値(), CASE -> 場合, IF() -> もし(), and 15 more across
miscellaneous-functions.md, information-functions.md, and
control-flow-functions.md). Verified corpus-wide via an anchor-based
heading comparison against the English source: 0 remaining
instances of this pattern after the fix.
- Fix 3 missing が particles after code-span identifiers
(string-functions.md x2, partitioned-table.md) and one misplaced を
particle (encryption-at-rest.md's --s3.sse argument).
- Fix a meaning-inverting heading/sentence in partitioned-table.md
("partitioned table" -> "partitioned table" instead of "partitioned
table" -> "non-partitioned table").
- Unify "rotate the master key" heading to ローテーションする, matching
the ローテーション term used in the very next sentence and dominant
throughout the rest of the corpus (回転させる was a self-contradicting
outlier).
- Restore 4 more lost code fences in pd-control.md that a previous
batch (pingcap#23506) missed, and fix newly-discovered lost fences in
performance-tuning-methods.md (3), performance-tuning-overview.md
(1, plus translating its formula to match the rest of the file),
pipelined-dml.md (1), and performance-schema-session-connect-attrs.md
(2) -- none of which were in the original corpus-wide sweep list,
suggesting daily syncs keep reintroducing this defect in newly
translated content.
- Unify 5 inconsistent renderings of the "Queries Using Plan Cache
OPS" Grafana panel name in performance-tuning-methods.md to the one
form the sync bot itself already left correctly in English.
Verified no merge conflicts against all other open i18n-ja-release-8.5
PRs (pingcap#23506, pingcap#23509, pingcap#23511).
29b2d3d to
0b25849
Compare
What is changed, added or deleted? (Required)
Found via user spot-checks across the current
i18n-ja-release-8.5branch. Each flagged item was verified against the English source before fixing, and every confirmed defect pattern was then swept corpus-wide for recurrences.SLEEP()→ 寝る(),VALUES()→ 値(),CASE→ 場合,IF()→ もし(), and 15 more acrossfunctions-and-operators/miscellaneous-functions.md,functions-and-operators/information-functions.md, andfunctions-and-operators/control-flow-functions.md). Verified corpus-wide via an anchor-based heading comparison against the English source — 0 remaining instances of this pattern after the fix.string-functions.mdx2,partitioned-table.md) and one misplaced を particle (encryption-at-rest.md's--s3.sseargument description).partitioned-table.md("partitioned table" → "partitioned table" instead of the correct "partitioned table" → "non-partitioned table").pd-control.mdthat a previous batch (i18n(ja): restore lost code fences (batch 2, 37 files) #23506) missed, and fix newly-discovered lost fences inperformance-tuning-methods.md(3),performance-tuning-overview.md(1, plus translating its formula to match the rest of the file),pipelined-dml.md(1), andperformance-schema/performance-schema-session-connect-attrs.md(2) — none of which were in the original corpus-wide sweep list from i18n(ja): restore lost code fences (batch 1, 135 files) #23505/i18n(ja): restore lost code fences (batch 2, 37 files) #23506/i18n(ja): restore lost code fences (batch 3, 33 files) #23511, suggesting daily syncs keep reintroducing this defect in newly translated content.performance-tuning-methods.mdto the one form the sync bot itself already left correctly in English.Verified no merge conflicts against all other open
i18n-ja-release-8.5PRs (#23506, #23509, #23511).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?