i18n(ja): restore lost code fences (batch 7, 25 files) - #23534
Conversation
Final batch of the 110-file high-confidence queue derived 2026-08-14.
Same defect as batches 1-6: the MT pipeline dropped triple-backtick
fence markers around code/config/log examples during translation,
leaving bare (sometimes mis-indented) content while the EN source
keeps the fence. Restored fences with EN's exact per-line indentation
for every affected block across the 25 files.
Also fixed one collateral defect found during the mandatory 3-layer
verification (fence-count + block-content indentation + blockquote-
aware positional check): two-data-centers-in-one-city-deployment.md
had a stray extra blank line between the end of a JSON block and its
closing fence, inflating that block's line count by one versus EN.
Left alone (out of scope, not fence defects): 2 untranslated EN
sentences in user-account-management.md, a missing {{< copyable >}}
shortcode line in two-data-centers-in-one-city-deployment.md, and a
missing {{< copyable >}} note in use-tidb-to-read-tiflash.md — all
pre-existing translation gaps unrelated to fence structure.
|
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 |
[LGTM Timeline notifier]Timeline:
|
What is changed, added or deleted? (Required)
Final batch (7 of 7) of the lost-code-fences sweep. The ja-translation MT pipeline dropped triple-backtick fence markers around code/config/log examples during translation in these 25 files, leaving bare (sometimes mis-indented) content while the EN source keeps the fence and syntax highlighting. This restores the fences with EN's exact per-line indentation for every affected block.
Also fixes one collateral defect found during the mandatory 3-layer verification (fence-count + block-content indentation + blockquote-aware positional check):
two-data-centers-in-one-city-deployment.mdhad a stray extra blank line between the end of a JSON block and its closing fence.Left alone (out of scope, pre-existing, not fence defects): 2 untranslated EN sentences in
user-account-management.md, and missing{{< copyable >}}shortcode lines intwo-data-centers-in-one-city-deployment.mdanduse-tidb-to-read-tiflash.md.This completes the 110-file high-confidence queue derived 2026-08-14 (batches 4-7). See prior batches: #23529, #23530, #23531.
Which TiDB version(s) do your changes apply to? (Required)
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?