i18n(ja): fix markdownlint conformance (MD030/046/037/022/032/039/034/012) to match release-8.5 - #23592
Conversation
|
test seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
|
Important Review skippedToo many files! This PR contains 1382 files, which is 1232 over the limit of 150. To get a review, reduce the PR to 150 files or fewer by splitting it into smaller PRs or changing its base branch. Upgrade to a paid plan to raise the limit. Usage-priced reviews support at most 300 files. ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1382)
You can disable this status message by setting the 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 |
|
[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 |
…) matching release-8.5
What is changed, added or deleted? (Required)
Normalized Markdown list-marker spacing across the Japanese (
i18n-ja-release-8.5) documentation to conform to MD030 (list-marker-space, one space after list markers), matching the formatting already used in the English source (release-8.5).The Japanese corpus had accumulated
-(three spaces after an unordered marker) and1.(two spaces after an ordered marker) list formatting, while the English source consistently uses one space.markdownlintreports 53,805 MD030 violations in the current Japanese branch. This PR fixes all of them.Additionally, converted indented code blocks to fenced code blocks to conform to MD046 (
code-block-style), matching the English source structure. The Japanese corpus had 281 indented code blocks (across 33 files) that the English source renders as fenced blocks. This PR converts all of them, including nested blocks inside lists and block quotes, so their structure matchesrelease-8.5.Finally, fixed the remaining markdownlint rules where the Japanese corpus deviated from the English source's conformance: MD037 (
no-space-in-emphasis, escaped\*multiplication signs), MD022/MD032 (blank lines around headings and lists), MD039 (space inside link text), MD034 (escaped|in table link), and MD012 (duplicate blank line).Verification performed:
markdownlint -c .markdownlint.yamlbefore and after: MD030 violations drop from 53,805 to 0; MD046 violations drop from 281 to 0; MD037 drops from 35 to 0; MD022/MD032, MD039, MD034, and the extra MD012 are all resolved.release-8.5English source: all aligned list markers, fenced code blocks, emphasis escapes, and link formatting in the Japanese files now match the English formatting exactly.markdownlintresults fori18n-ja-release-8.5matchrelease-8.5exactly: the only remaining violations are the shared.github/template files (MD012, MD041, MD007), identical to the English source.Affected: 1,381
.mdfiles, 53,805 lines (MD030); 33.mdfiles, 281 blocks (MD046); 10.mdfiles (MD037/022/032/039/034/012).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?