Skip to content

i18n(ja): unify optimistic/pessimistic mode terminology - #23463

Open
yahonda wants to merge 1 commit into
pingcap:i18n-ja-release-8.5from
yahonda:i18n-ja-optimistic-pessimistic-mode-term
Open

i18n(ja): unify optimistic/pessimistic mode terminology#23463
yahonda wants to merge 1 commit into
pingcap:i18n-ja-release-8.5from
yahonda:i18n-ja-optimistic-pessimistic-mode-term

Conversation

@yahonda

@yahonda yahonda commented Aug 7, 2026

Copy link
Copy Markdown
Member

What is changed, added or deleted? (Required)

DM's shard-merge feature has an "optimistic mode" and a "pessimistic mode." The Japanese rendering was split three ways: 楽観的モード/悲観的モード (the -teki adjectival form, 39/27 occurrences, dominant), 楽観モード/悲観モード (a bare noun-compound form, 4/3), and オプティミスティックモード (an English-derived katakana form, 2, optimistic side only).

Unified everything to the -teki form (楽観的モード/悲観的モード) across 5 files: TOC.md, dm/dm-best-practices.md, dm/dm-ddl-compatible.md, dm/feature-shard-merge.md, and dm/feature-shard-merge-optimistic.md's own H1 heading.

The H1 fix is notable: feature-shard-merge-optimistic.md's H1 used the katakana form (オプティミスティックモード) while its own summary: frontmatter and body text both already used the -teki form (楽観的モード) — an internal inconsistency within the same file — and its pessimistic sibling page's H1 already correctly used the -teki form (悲観的モード). The anchor ({#merge-and-migrate-data-from-sharded-tables-in-optimistic-mode}) is unchanged, as it's an explicit English-derived tag.

45 occurrences of 楽観的モード and 30 of 悲観的モード after (up from 39/27), 0 remaining of the other two forms.

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)

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

N/A

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

DM's shard-merge "optimistic mode" / "pessimistic mode" was rendered
three ways: the -teki adjectival form (39/27 occurrences, dominant and
used in both pages' own summary/body text), a bare noun-compound form
(4/3), and an English-derived katakana form (2, optimistic side only).
Unified to the -teki form across 5 files: TOC.md, dm/dm-best-practices.md,
dm/dm-ddl-compatible.md, dm/feature-shard-merge.md, and
dm/feature-shard-merge-optimistic.md's own H1 heading, which was itself
inconsistent with its own summary and body text (both already used the
-teki form) and with its pessimistic sibling page's H1 (which already
used the -teki form). Anchor unchanged (EN-derived {#...} tag).
@ti-chi-bot

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

coderabbitai Bot commented Aug 7, 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: 7edc7e08-16c5-4d4f-afbe-51ceb853c255

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 commented Aug 7, 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 oreoxmt 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/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Aug 7, 2026
@yahonda
yahonda marked this pull request as ready for review August 7, 2026 04:35
@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 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

missing-translation-status This PR does not have translation status info. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant