Skip to content

i18n(ja): unify MySQL-compatibility term translation - #23437

Merged
qiancai merged 1 commit into
pingcap:i18n-ja-release-8.5from
yahonda:i18n-ja-mysql-compat-term
Aug 5, 2026
Merged

i18n(ja): unify MySQL-compatibility term translation#23437
qiancai merged 1 commit into
pingcap:i18n-ja-release-8.5from
yahonda:i18n-ja-mysql-compat-term

Conversation

@yahonda

@yahonda yahonda commented Aug 5, 2026

Copy link
Copy Markdown
Member

What is changed, added or deleted? (Required)

Unifies the ja translation of "MySQL compatibility"/"MySQL Compatibility" to MySQLとの互換性, which was previously split roughly 50/50 with MySQLの互換性 (143 vs 142 occurrences before this PR).

  • MySQLとの互換性 matches the H1 heading of mysql-compatibility.md (# MySQLとの互換性 {#mysql-compatibility}) and reads more naturally as "compatibility with MySQL".
  • 141 files changed, 143 lines updated — mostly the ## MySQL...の互換性 {#mysql-compatibility} section heading repeated across sql-statements/*.md, plus inline link text [MySQLの互換性](...) and a few prose sentences.
  • All {#mysql-compatibility} heading anchors are unchanged (English-derived).
  • Guardrail: verified via exact count math (143 old + 142 old = 285 new MySQLとの互換性, 0 remaining MySQLの互換性) and per-file line-count-unchanged check across all 141 files.

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

  • v8.5 (LTS)
  • v8.1 (LTS)
  • v7.5 (LTS)
  • v7.1 (LTS)
  • v6.5 (LTS)
  • v6.1 (LTS)

Do your changes match any of the following descriptions?

  • Delete files
  • Change aliases
  • Add redirect rules
  • Change the framework or the code logic of the repository

@ti-chi-bot

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

coderabbitai Bot commented Aug 5, 2026 •
edited
Loading

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: b60e2643-b0ba-4fc6-a576-5fe0b6b7ac80

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 5, 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 tangenta 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. area/develop This PR relates to the area of TiDB App development. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Aug 5, 2026
@yahonda
i18n(ja): unify MySQL-compatibility term translation
d2d0346 
MySQLの互換性 (143 occurrences) and MySQLとの互換性 (142 occurrences) were
split roughly 50/50 for the same English term "MySQL compatibility"/"MySQL
Compatibility". Unified to MySQLとの互換性, matching the H1 heading of
mysql-compatibility.md and the grammatically-preferred "compatibility with
MySQL" reading. Headings keep their {#mysql-compatibility} anchor unchanged.
@yahonda
yahonda force-pushed the i18n-ja-mysql-compat-term branch from 37683d8 to d2d0346 Compare August 5, 2026 05:22
@yahonda yahonda changed the title i18n(ja): unify MySQL-compatibility term to MySQLとの互換性 i18n(ja): unify MySQL-compatibility term translation Aug 5, 2026
@yahonda
yahonda marked this pull request as ready for review August 5, 2026 06:11
@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 5, 2026
This was referenced Aug 5, 2026
Merged
Merged
yahonda added a commit to yahonda/docs that referenced this pull request Aug 5, 2026
@yahonda
i18n(ja): restore dropped particles after code spans in two SQL/TiCDC…
f2bcd55 
… docs

- sql-statement-start-transaction.md: the START TRANSACTION compatibility
  bullet was missing は after every `START TRANSACTION` code span (3
  places), producing a run-on, ungrammatical sentence. Restored particles to
  match the English source's three clauses (TiDB behavior / MySQL behavior /
  the WITH CONSISTENT SNAPSHOT equivalence).
- Fixed the same missing-は defect in the adjacent START TRANSACTION READ
  ONLY bullet.
- ticdc-faq.md: "詳細は[MySQLの互換性](...)ご覧ください" was missing the を
  particle before the verb. Restored to "...をご覧ください", and also applied
  MySQLの互換性 -> MySQLとの互換性 here (matching pingcap#23437's term unification,
  to avoid a needless cross-PR conflict on this line).
- ticdc-faq.md: reordered "TiDBのデフォルト値`explicit_defaults_for_timestamp`
  がMySQLと異なる" (awkward: reads as "TiDB's default value
  explicit_defaults_for_timestamp") to "TiDBの`explicit_defaults_for_timestamp`
  のデフォルト値がMySQLと異なる", matching the English's modifier order:
  "the default value of `explicit_defaults_for_timestamp` in TiDB".
@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 5, 2026
@ti-chi-bot ti-chi-bot Bot added the needs-1-more-lgtm Indicates a PR needs 1 more LGTM. label Aug 5, 2026
@ti-chi-bot

ti-chi-bot Bot commented Aug 5, 2026

Copy link
Copy Markdown

[LGTM Timeline notifier]

Timeline:

  • 2026-08-05 12:26:31.172469202 +0000 UTC m=+2617377.208564258: ☑️ agreed by qiancai.

@qiancai
qiancai merged commit dc73077 into pingcap:i18n-ja-release-8.5 Aug 5, 2026
4 of 9 checks passed
yahonda added a commit to yahonda/docs that referenced this pull request Aug 6, 2026
@yahonda
i18n(ja): restore dropped particles after code spans in two SQL/TiCDC…
276c450 
… docs

- sql-statement-start-transaction.md: the START TRANSACTION compatibility
  bullet was missing は after every `START TRANSACTION` code span (3
  places), producing a run-on, ungrammatical sentence. Restored particles to
  match the English source's three clauses (TiDB behavior / MySQL behavior /
  the WITH CONSISTENT SNAPSHOT equivalence).
- Fixed the same missing-は defect in the adjacent START TRANSACTION READ
  ONLY bullet.
- ticdc-faq.md: "詳細は[MySQLの互換性](...)ご覧ください" was missing the を
  particle before the verb. Restored to "...をご覧ください", and also applied
  MySQLの互換性 -> MySQLとの互換性 here (matching pingcap#23437's term unification,
  to avoid a needless cross-PR conflict on this line).
- ticdc-faq.md: reordered "TiDBのデフォルト値`explicit_defaults_for_timestamp`
  がMySQLと異なる" (awkward: reads as "TiDB's default value
  explicit_defaults_for_timestamp") to "TiDBの`explicit_defaults_for_timestamp`
  のデフォルト値がMySQLと異なる", matching the English's modifier order:
  "the default value of `explicit_defaults_for_timestamp` in TiDB".
@yahonda
yahonda deleted the i18n-ja-mysql-compat-term branch August 6, 2026 00:30
yahonda added a commit to yahonda/docs that referenced this pull request Aug 6, 2026
@yahonda
i18n(ja): restore dropped particles after code spans in two SQL/TiCDC…
0100ce1 
… docs

- sql-statement-start-transaction.md: the START TRANSACTION compatibility
  bullet was missing は after every `START TRANSACTION` code span (3
  places), producing a run-on, ungrammatical sentence. Restored particles to
  match the English source's three clauses (TiDB behavior / MySQL behavior /
  the WITH CONSISTENT SNAPSHOT equivalence).
- Fixed the same missing-は defect in the adjacent START TRANSACTION READ
  ONLY bullet.
- ticdc-faq.md: "詳細は[MySQLの互換性](...)ご覧ください" was missing the を
  particle before the verb. Restored to "...をご覧ください", and also applied
  MySQLの互換性 -> MySQLとの互換性 here (matching pingcap#23437's term unification,
  to avoid a needless cross-PR conflict on this line).
- ticdc-faq.md: reordered "TiDBのデフォルト値`explicit_defaults_for_timestamp`
  がMySQLと異なる" (awkward: reads as "TiDB's default value
  explicit_defaults_for_timestamp") to "TiDBの`explicit_defaults_for_timestamp`
  のデフォルト値がMySQLと異なる", matching the English's modifier order:
  "the default value of `explicit_defaults_for_timestamp` in TiDB".
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@qiancai qiancai qiancai approved these changes

Assignees

No one assigned

Labels

area/develop This PR relates to the area of TiDB App development. needs-1-more-lgtm Indicates a PR needs 1 more LGTM. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. translation/no-need No need to translate this PR.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@yahonda @qiancai