Skip to content

i18n(ja): fix noun-smashed translation of a TiCDC release-note bullet - #23650

Closed
yahonda wants to merge 1 commit into
pingcap:i18n-ja-release-8.5from
yahonda:fix-support-placement-rules-wording
Closed

i18n(ja): fix noun-smashed translation of a TiCDC release-note bullet#23650
yahonda wants to merge 1 commit into
pingcap:i18n-ja-release-8.5from
yahonda:fix-support-placement-rules-wording

Conversation

@yahonda

@yahonda yahonda commented Aug 28, 2026

Copy link
Copy Markdown
Member

What is changed, added or deleted? (Required)

releases/release-6.0.0-dmr.md: EN "Support placement rules" (a verb-initial release-note bullet) had been word-for-word reordered into a bare noun compound with no particle, reading as a smashed-together "Support-Placement-Rule" noun rather than a sentence. Reworded to the noun-ending form used by sibling bullets in the same list.

1 file changed, 1 site.

Note: a broader corpus-wide sweep found ~50 similar "Support X" release-note bullets across ~30 files (mostly older release notes, release-1.0 through release-7.x) with the same word-order issue — this PR fixes only the single site the user flagged; the rest are tracked separately for a future dedicated sweep since each needs individual EN verification.

Which TiDB version(s) do your changes apply to? (Required)

  • i18n-ja-release-8.5 (TiDB Japanese documentation for TiDB 8.5 versions)

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

  • This PR is translated from:
  • Other reference 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

EN 'Support placement rules' had been word-for-word reordered into a bare noun compound (support + placement-rule stuck together with no particle), rather than translated as a clause. Reworded to match the noun-ending style used by sibling bullets in the same list.
@ti-chi-bot

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

coderabbitai Bot commented Aug 28, 2026

Copy link
Copy Markdown

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

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 commented Aug 28, 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 icemap 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 missing-translation-status This PR does not have translation status info. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Aug 28, 2026
yahonda added a commit to yahonda/docs that referenced this pull request Aug 28, 2026
Corpus-wide sweep of release-note bullets translated from EN's verb-initial 'Support X' pattern. JA had consistently reordered these into a bare noun compound with no particle (a prefix-glued 'サポートX'), rather than a proper clause. Reworded each site to match its own list's established local convention (mostly 'Xをサポート', a few 'Xのサポート' where local siblings already used that noun-ending form). Also fixed a handful of related mid-sentence 'Support X to do Y' scrambles found in passing in the same files. Excludes releases/release-6.0.0-dmr.md (already fixed in pingcap#23650) and 2 confirmed false positives (a genuine 'support ticket'/'support entries' noun usage, not this verb pattern).
yahonda added a commit to yahonda/docs that referenced this pull request Aug 28, 2026
Corpus-wide sweep of release-note bullets translated from EN's verb-initial 'Support X' pattern. JA had consistently reordered these into a bare noun compound with no particle (a prefix-glued 'サポートX'), rather than a proper clause. Reworded each site to match its own list's established local convention (mostly 'Xをサポート', a few 'Xのサポート' where local siblings already used that noun-ending form). Also fixed a handful of related mid-sentence 'Support X to do Y' scrambles found in passing in the same files. Excludes releases/release-6.0.0-dmr.md (already fixed in pingcap#23650) and 2 confirmed false positives (a genuine 'support ticket'/'support entries' noun usage, not this verb pattern).
yahonda added a commit to yahonda/docs that referenced this pull request Aug 28, 2026
Corpus-wide sweep of release-note bullets translated from EN's verb-initial 'Support X' pattern. JA had consistently reordered these into a bare noun compound with no particle (a prefix-glued 'サポートX'), rather than a proper clause. Reworded each site to match its own list's established local convention (mostly 'Xをサポート', a few 'Xのサポート' where local siblings already used that noun-ending form). Also fixed a handful of related mid-sentence 'Support X to do Y' scrambles found in passing in the same files. Excludes releases/release-6.0.0-dmr.md (already fixed in pingcap#23650) and 2 confirmed false positives (a genuine 'support ticket'/'support entries' noun usage, not this verb pattern).
yahonda added a commit to yahonda/docs that referenced this pull request Aug 28, 2026
Corpus-wide sweep of release-note bullets translated from EN's verb-initial 'Support X' pattern. JA had consistently reordered these into a bare noun compound with no particle (a prefix-glued 'サポートX'), rather than a proper clause. Reworded each site to match its own list's established local convention (mostly 'Xをサポート', a few 'Xのサポート' where local siblings already used that noun-ending form). Also fixed a handful of related mid-sentence 'Support X to do Y' scrambles found in passing in the same files. Excludes releases/release-6.0.0-dmr.md (already fixed in pingcap#23650) and 2 confirmed false positives (a genuine 'support ticket'/'support entries' noun usage, not this verb pattern).
@yahonda

yahonda commented Aug 28, 2026

Copy link
Copy Markdown
Member Author

Consolidated into #23651, which covers the same defect class (noun-smashed "Support X" release-note bullets) across the whole corpus, including this file's site.

@yahonda yahonda closed this Aug 28, 2026
yahonda added a commit to yahonda/docs that referenced this pull request Aug 28, 2026
Corpus-wide sweep of release-note bullets translated from EN's verb-initial 'Support X' pattern. JA had consistently reordered these into a bare noun compound with no particle (a prefix-glued 'サポートX'), rather than a proper clause. Reworded each site to match its own list's established local convention (mostly 'Xをサポート', a few 'Xのサポート' where local siblings already used that noun-ending form). Also fixed a handful of related mid-sentence 'Support X to do Y' scrambles found in passing in the same files. Excludes releases/release-6.0.0-dmr.md (already fixed in pingcap#23650) and 2 confirmed false positives (a genuine 'support ticket'/'support entries' noun usage, not this verb pattern).
@yahonda
yahonda deleted the fix-support-placement-rules-wording branch August 28, 2026 06:14
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. missing-translation-status This PR does not have translation status info. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant