Skip to content

i18n(ja): restore lost code fences (batch 7, 25 files) - #23534

Merged
qiancai merged 1 commit into
pingcap:i18n-ja-release-8.5from
yahonda:i18n-ja-lost-code-fences-sweep-batch7
Aug 17, 2026
Merged

i18n(ja): restore lost code fences (batch 7, 25 files)#23534
qiancai merged 1 commit into
pingcap:i18n-ja-release-8.5from
yahonda:i18n-ja-lost-code-fences-sweep-batch7

Conversation

@yahonda

@yahonda yahonda commented Aug 17, 2026

Copy link
Copy Markdown
Member

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.md had 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 in two-data-centers-in-one-city-deployment.md and use-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)

  • master (the latest development version)
  • v8.5 (TiDB 8.5 versions)
  • v8.4 (TiDB 8.4 versions)
  • v8.3 (TiDB 8.3 versions)
  • v8.2 (TiDB 8.2 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)
  • v6.1 (TiDB 6.1 versions)
  • v5.4 (TiDB 5.4 versions)
  • v5.3 (TiDB 5.3 versions)

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

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

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

ti-chi-bot Bot commented Aug 17, 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 17, 2026
@ti-chi-bot

ti-chi-bot Bot commented Aug 17, 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

@ti-chi-bot ti-chi-bot Bot added the missing-translation-status This PR does not have translation status info. label Aug 17, 2026
@coderabbitai

coderabbitai Bot commented Aug 17, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

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: 995b1145-3615-4800-ba8f-7c0a4477e2cd

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 the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Aug 17, 2026
@yahonda
yahonda marked this pull request as ready for review August 17, 2026 00:39
@ti-chi-bot ti-chi-bot Bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 17, 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 17, 2026
@ti-chi-bot ti-chi-bot Bot added the needs-1-more-lgtm Indicates a PR needs 1 more LGTM. label Aug 17, 2026
@qiancai
qiancai merged commit b8c8611 into pingcap:i18n-ja-release-8.5 Aug 17, 2026
5 of 9 checks passed
@ti-chi-bot

ti-chi-bot Bot commented Aug 17, 2026

Copy link
Copy Markdown

[LGTM Timeline notifier]

Timeline:

  • 2026-08-17 09:58:36.818420046 +0000 UTC m=+3645302.854515112: ☑️ agreed by qiancai.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs-1-more-lgtm Indicates a PR needs 1 more LGTM. 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