Skip to content

i18n(ja): restore lost code fences (batch 2, 37 files) - #23506

Draft
yahonda wants to merge 1 commit into
pingcap:i18n-ja-release-8.5from
yahonda:i18n-ja-lost-code-fences-sweep-batch2
Draft

i18n(ja): restore lost code fences (batch 2, 37 files)#23506
yahonda wants to merge 1 commit into
pingcap:i18n-ja-release-8.5from
yahonda:i18n-ja-lost-code-fences-sweep-batch2

Conversation

@yahonda

@yahonda yahonda commented Aug 12, 2026

Copy link
Copy Markdown
Member

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:

  • Fence markers (plain or taggedyaml/sql/shell/```json) added back at the correct position and indentation.
  • Body content re-indented where it had accumulated stray leading whitespace from the old workaround (Markdown's "4-space indented code block" convention, used as a substitute once the real fence was lost) — every file's fence count and per-line indentation now matches the English source exactly.
  • No translated prose, headings, or any other content was touched.

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.

  • master (the latest development version)
  • v9.0 (TiDB 9.0 versions)
  • v8.5 (TiDB 8.5 versions)
  • v8.1 (TiDB 8.1 versions)
  • v7.5 (TiDB 7.5 versions)
  • v7.1 (TiDB 7.1 versions)
  • v6.5 (TiDB 6.5 versions)

What is the related PR or file link(s)?

AI agent involvement

  • The changes in this PR were primarily made by an AI agent on behalf of the PR author.

Do your changes match any of the following descriptions?

  • Delete files
  • Change aliases
  • Need modification after applied to another branch
  • Might cause conflicts after applied to another branch

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>
@ti-chi-bot

ti-chi-bot Bot commented Aug 12, 2026

Copy link
Copy Markdown

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@ti-chi-bot ti-chi-bot Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 12, 2026
@ti-chi-bot

ti-chi-bot Bot commented Aug 12, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign overvenus for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@coderabbitai

coderabbitai Bot commented Aug 12, 2026

Copy link
Copy Markdown

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: e6461b88-c274-463f-b411-0080d6844483

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@ti-chi-bot ti-chi-bot Bot added missing-translation-status This PR does not have translation status info. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Aug 12, 2026
@qiancai qiancai added translation/no-need No need to translate this PR. and removed missing-translation-status This PR does not have translation status info. labels Aug 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. translation/no-need No need to translate this PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants