i18n(ja): restore lost code fences (batch 3, 33 files) - #23511
Merged
qiancai merged 1 commit intoAug 13, 2026
Conversation
Restores triple-backtick code fences dropped by the original MT translation across DM guides, deployment/scale guides, and sql-statement pages, matching the English source's fence positions and indentation exactly.
|
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 |
|
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 |
ti-chi-bot
Bot
added
missing-translation-status
yahonda
marked this pull request as ready for review
August 13, 2026 01:06
ti-chi-bot
Bot
removed
the
do-not-merge/work-in-progress
12 tasks
yahonda
added a commit
to yahonda/docs
that referenced
this pull request
Aug 13, 2026
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).
qiancai
added
translation/no-need
qiancai
approved these changes
Aug 13, 2026
[LGTM Timeline notifier]Timeline:
|
yahonda
added a commit
to yahonda/docs
that referenced
this pull request
Aug 13, 2026
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).
This was referenced Aug 14, 2026
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)
Batch 3 of the corpus-wide lost-code-fences sweep (see #23505 and #23506 for batch 1/2 context): restores triple-backtick code fences that were dropped by the original MT translation, across DM guides, TiUP deployment/scaling guides, and
sql-statements/sql-statement-*.mdpages. 33 files, each verified against the English source for both fence count and per-line indentation (including list-nested and blockquote-nested fences).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?