i18n(ja): restore lost code fences (batch 2, 37 files) - #23506
Conversation
Continues the corpus-wide fence-restoration sweep (see PR pingcap#23505, batch 1). Same method: fence markers restored to match English exactly, including per-line indentation correction. Verified via the fence-count + positional (blockquote-aware) indentation check across all 37 files -- no remaining mismatches. 4 files from this batch's original scope (dm/dm-manage-schema.md, dm/handle-failed-ddl-statements.md, dm/manually-handling-sharding-ddl-locks.md, privilege-management.md) were still incomplete when this batch was interrupted and are reverted to their original state, to be redone cleanly in a future batch rather than committing partial/inconsistent edits. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
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 skippedDraft detected. 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 |
What is changed, added or deleted? (Required)
Second batch of a corpus-wide sweep fixing a structural MT regression (batch 1: #23505): many config/log/command/output examples in Japanese translations lost their triple-backtick code fences entirely, degrading to plain (sometimes still-indented) text with no syntax highlighting or copy-button UI. The example content itself was untouched — only the fence markers were missing.
This PR (37 files) restores the fences to match the English source exactly:
or taggedyaml/sql/shell/```json) added back at the correct position and indentation.Verified mechanically for every file in this PR: (1) the count of ``` occurrences matches the English source exactly, and (2) for every matched code block, per-line leading-whitespace matches the English source exactly, including code fences nested inside blockquotes.
Disjoint file set from #23505 (batch 1) — the two PRs can be reviewed/merged independently. A further batch of the remaining ~179 candidate files will follow separately.
Which TiDB version(s) do your changes apply to? (Required)
Tips for choosing the affected version(s):
By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.
For details, see tips for choosing the affected versions.
What is the related PR or file link(s)?
AI agent involvement
Do your changes match any of the following descriptions?