Skip to content

i18n(ja): unify the Japanese term for 'request' (190 files) - #23774

Closed
yahonda wants to merge 13 commits into
pingcap:i18n-ja-release-8.5from
yahonda:fix-yokyu-to-request-corpus-sweep
Closed

yahonda wants to merge 13 commits into
pingcap:i18n-ja-release-8.5from
yahonda:fix-yokyu-to-request-corpus-sweep

Conversation

@yahonda

@yahonda yahonda commented Sep 8, 2026

Copy link
Copy Markdown
Member

What is changed, added, or deleted? (Required)

Corpus-wide term-unification sweep: converts 要求 (yōkyū) to リクエスト (katakana "request") wherever the English source literally says "request" (noun or verb) — the established dominant form corpus-wide (リクエスト 1630 occurrences vs 要求 683 before this PR).

Every occurrence was individually checked against upstream/release-8.5 before converting. 要求 was intentionally LEFT UNCHANGED (36 remaining occurrences, across 25 files) wherever the EN source says something other than "request":

  • "require"/"requirement" (e.g. system-variables.md, tidb-cloud/tidb-cloud-faq.md)
  • "demand" (e.g. tune-tikv-memory-performance.md, tidb-troubleshooting-map.md)
  • other verbs like "asks" (e.g. tiup/tiup-cluster.md)

Net result: 647 occurrences converted across 190 files (要求 683→36, リクエスト 1630→2277).

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

  • master (the latest development version)
  • v9.0 (TiDB 9.0 versions)
  • v8.5 (TiDB 8.5 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)?

  • Related code change PR links (if applicable):
  • 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

@ti-chi-bot

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

coderabbitai Bot commented Sep 8, 2026

Copy link
Copy Markdown

Important

Review skipped

Too many files!

This PR contains 192 files, which is 42 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.

This review couldn't start because sufficient usage credits or metered capacity aren't available. Add credits or update usage-based reviews in the billing tab, then retry.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Advanced

Run ID: 1a7eb812-e46b-432a-bcac-89a3fbaefe18

📥 Commits

Reviewing files that changed from the base of the PR and between 7ec44ef and cfb2dd9.

📒 Files selected for processing (192)
  • alert-rules.md
  • auto-increment.md
  • best-practices/best-practices-on-public-cloud.md
  • best-practices/ddl-introduction.md
  • best-practices/high-concurrency-best-practices.md
  • best-practices/index-management-best-practices.md
  • best-practices/pd-scheduling-best-practices.md
  • best-practices/three-dc-local-read.md
  • best-practices/three-nodes-hybrid-deployment.md
  • br/backup-and-restore-use-cases.md
  • br/br-checkpoint-backup.md
  • br/br-log-architecture.md
  • br/br-snapshot-architecture.md
  • check-before-deployment.md
  • command-line-flags-for-tidb-configuration.md
  • configure-load-base-split.md
  • coprocessor-cache.md
  • dashboard/dashboard-diagnostics-report.md
  • dashboard/dashboard-diagnostics-usage.md
  • dashboard/dashboard-metrics-relation.md
  • dashboard/dashboard-monitoring.md
  • dashboard/dashboard-ops-deploy.md
  • develop/dev-guide-connection-parameters.md
  • develop/dev-guide-get-data-from-single-table.md
  • develop/dev-guide-use-follower-read.md
  • develop/java-app-best-practices.md
  • dm/dm-error-handling.md
  • dm/dm-generate-self-signed-certificates.md
  • dm/dm-open-api.md
  • dm/feature-shard-merge-pessimistic.md
  • dm/manually-handling-sharding-ddl-locks.md
  • dr-solution-introduction.md
  • dynamic-config.md
  • error-codes.md
  • explain-partitions.md
  • faq/deploy-and-maintain-faq.md
  • follower-read.md
  • generate-self-signed-certificates.md
  • global-indexes.md
  • glossary.md
  • grafana-overview-dashboard.md
  • grafana-performance-overview-dashboard.md
  • grafana-resource-control-dashboard.md
  • grafana-tidb-dashboard.md
  • grafana-tikv-dashboard.md
  • identify-expensive-queries.md
  • identify-slow-queries.md
  • information-schema/information-schema-cluster-log.md
  • information-schema/information-schema-inspection-result.md
  • information-schema/information-schema-metrics-summary.md
  • information-schema/information-schema-processlist.md
  • latency-breakdown.md
  • metrics-schema.md
  • multi-data-centers-in-one-city-deployment.md
  • optimistic-transaction.md
  • optimizer-hints.md
  • pd-configuration-file.md
  • pd-control.md
  • performance-tuning-methods.md
  • performance-tuning-overview.md
  • performance-tuning-practices.md
  • pessimistic-transaction.md
  • privilege-management.md
  • releases/release-2.1-ga.md
  • releases/release-2.1-rc.1.md
  • releases/release-2.1-rc.3.md
  • releases/release-2.1.18.md
  • releases/release-2.1.3.md
  • releases/release-3.0-beta.md
  • releases/release-3.0-ga.md
  • releases/release-3.1.0-beta.2.md
  • releases/release-3.1.0-ga.md
  • releases/release-3.1.0-rc.md
  • releases/release-3.1.1.md
  • releases/release-4.0-ga.md
  • releases/release-4.0.0-rc.1.md
  • releases/release-4.0.0-rc.2.md
  • releases/release-4.0.11.md
  • releases/release-4.0.15.md
  • releases/release-4.0.2.md
  • releases/release-4.0.7.md
  • releases/release-5.0.0-rc.md
  • releases/release-5.0.6.md
  • releases/release-5.1.0.md
  • releases/release-5.1.1.md
  • releases/release-5.1.2.md
  • releases/release-5.1.4.md
  • releases/release-5.1.5.md
  • releases/release-5.2.0.md
  • releases/release-5.2.2.md
  • releases/release-5.2.4.md
  • releases/release-5.3.0.md
  • releases/release-5.3.3.md
  • releases/release-5.4.0.md
  • releases/release-5.4.3.md
  • releases/release-6.0.0-dmr.md
  • releases/release-6.1.1.md
  • releases/release-6.1.2.md
  • releases/release-6.2.0.md
  • releases/release-6.3.0.md
  • releases/release-6.4.0.md
  • releases/release-6.5.0.md
  • releases/release-6.5.10.md
  • releases/release-6.5.11.md
  • releases/release-6.5.5.md
  • releases/release-6.5.6.md
  • releases/release-6.6.0.md
  • releases/release-7.0.0.md
  • releases/release-7.1.0.md
  • releases/release-7.1.2.md
  • releases/release-7.1.5.md
  • releases/release-7.1.6.md
  • releases/release-7.2.0.md
  • releases/release-7.4.0.md
  • releases/release-7.5.0.md
  • releases/release-7.5.2.md
  • releases/release-7.5.3.md
  • releases/release-7.5.4.md
  • releases/release-7.5.7.md
  • releases/release-7.6.0.md
  • releases/release-8.0.0.md
  • releases/release-8.1.0.md
  • releases/release-8.1.1.md
  • releases/release-8.1.2.md
  • releases/release-8.2.0.md
  • releases/release-8.3.0.md
  • releases/release-8.4.0.md
  • releases/release-8.5.0.md
  • releases/release-8.5.4.md
  • releases/release-8.5.6.md
  • smooth-upgrade-tidb.md
  • sql-statements/sql-statement-explain-analyze.md
  • sql-statements/sql-statement-lock-tables-and-unlock-tables.md
  • sql-statements/sql-statement-split-region.md
  • stale-read.md
  • statement-summary-tables.md
  • system-variables.md
  • ticdc/monitor-ticdc.md
  • ticdc/ticdc-architecture.md
  • ticdc/ticdc-faq.md
  • ticdc/ticdc-overview.md
  • ticdc/ticdc-server-config.md
  • ticdc/ticdc-sink-to-kafka.md
  • ticdc/ticdc-split-update-behavior.md
  • tidb-cloud/architecture-concepts.md
  • tidb-cloud/changefeed-sink-to-apache-kafka.md
  • tidb-cloud/changefeed-sink-to-apache-pulsar.md
  • tidb-cloud/data-service-api-key.md
  • tidb-cloud/import-csv-files.md
  • tidb-cloud/import-parquet-files.md
  • tidb-cloud/import-sample-data.md
  • tidb-cloud/migrate-from-mysql-using-data-migration.md
  • tidb-cloud/migrate-incremental-data-from-mysql-using-data-migration.md
  • tidb-cloud/monitor-datadog-integration.md
  • tidb-cloud/monitor-new-relic-integration.md
  • tidb-cloud/optimize-resource-allocation.md
  • tidb-cloud/plan-replayer.md
  • tidb-cloud/releases/release-notes-2023.md
  • tidb-cloud/releases/tidb-cloud-release-notes.md
  • tidb-cloud/serverless-high-availability.md
  • tidb-cloud/serverless-private-link-connection.md
  • tidb-cloud/set-up-sink-private-endpoint.md
  • tidb-cloud/set-up-vpc-peering-connections.md
  • tidb-cloud/tidb-cloud-auditing.md
  • tidb-cloud/tidb-cloud-glossary.md
  • tidb-cloud/tidb-cloud-tune-performance-overview.md
  • tidb-cloud/v8.5-performance-highlights.md
  • tidb-configuration-file.md
  • tidb-lightning/tidb-lightning-configuration.md
  • tidb-performance-tuning-config.md
  • tidb-resource-control-ru-groups.md
  • tidb-troubleshooting-map.md
  • tiflash-performance-tuning-methods.md
  • tiflash/maintain-tiflash.md
  • tiflash/monitor-tiflash.md
  • tiflash/tiflash-configuration.md
  • tiflash/tiflash-mintso-scheduler.md
  • tiflash/tiflash-overview.md
  • tiflash/tiflash-pipeline-model.md
  • tiflash/tiflash-results-materialization.md
  • tikv-configuration-file.md
  • tikv-control.md
  • tikv-in-memory-engine.md
  • tiproxy/tiproxy-configuration.md
  • tiproxy/tiproxy-load-balance.md
  • tiup/tiup-component-cluster-tls.md
  • tiup/tiup-mirror-reference.md
  • troubleshoot-hot-spot-issues.md
  • troubleshoot-lock-conflicts.md
  • troubleshoot-write-conflicts.md
  • tune-region-performance.md
  • tune-tikv-thread-performance.md

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


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 Sep 8, 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 hfxsd 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/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. area/develop This PR relates to the area of TiDB App development. labels Sep 8, 2026
@yahonda yahonda changed the title i18n(ja): unify yokyu to request katakana where EN source says request i18n(ja): unify the Japanese term for 'request' (190 files) Sep 8, 2026
yahonda and others added 7 commits September 8, 2026 16:39
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…oted request kinds

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@yahonda
yahonda force-pushed the fix-yokyu-to-request-corpus-sweep branch from 303d3eb to 9a47477 Compare September 8, 2026 07:40
yahonda and others added 6 commits September 8, 2026 16:43
…dentifiers

Fixes 5 sites where a stray 目 (or 件目/13件目) was mistakenly attached to a
backtick-quoted identifier, matching the established spurious-ordinal MT
artifact class (see memory ja-spurious-banme-artifact): handle column
mistranslated as handle-eye in 2 old release notes, a stray 目 inserted
after tso_wait in performance-tuning-methods.md, and a TiCDC UPDATE/DELETE/
INSERT split-event backport notice garbled with spurious 目/件目/a stray
'13' in release-7.1.6.md and release-7.5.2.md (release-6.5.10.md already
had the correct rendering of the identical paragraph, used as the
reference to fix the other two against).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
EN "highly concurrent" was mistranslated as 高度な同時 ("advanced
simultaneous") in 2 sites; the identical EN phrase is correctly rendered
elsewhere in the corpus as 同時実行性の高い (e.g. release-7.1.6.md and
release-7.5.3.md's copies of the same TiKV OOM release-note bullet), used
here as the reference to fix release-8.2.0.md's copy and
best-practices/high-concurrency-best-practices.md's intro sentence.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
sql-statements/sql-statement-explain-analyze.md: restored the missing は
particle after `Batch_Point_Get` and reworded the noun+suru construction
for 'read data' to the plain verb form for natural phrasing.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…oring doc

ticdc/monitor-ticdc.md documents the literal panel/metric names shown on
the actual TiCDC Grafana dashboards (both the new-architecture and
classic-architecture monitoring boards). Nearly every bullet label across
all 9 sections had been translated into Japanese, breaking the reader's
ability to match a label against what they see in Grafana -- the same
defect class documented for the grafana-*-dashboard.md files in PR pingcap#23763
(see memory ja-grafana-panel-names-english). Restored all metric/panel
labels to literal English (matching the live Grafana panel/section names)
while keeping the Japanese description text after each label unchanged.
Also fixed 2 section headings and the panel-name references in prose that
had drifted from their own anchor's English name (e.g. 概要/サーバー
panel-name mentions not matching the Summary/Server heading english form).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…pace

dynamic-config.md: aligned the TiFlash max_threads sentence with the
established wording already used for the identical content in
release-6.1.0.md (config item, not bare configuration), and removed 2
stray U+200B zero-width-space characters embedded mid-word (matching the
known legacy MT artifact class).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…peer mistranslation

- follower-read.md: restored a Grafana breadcrumb link (TiDB > KV Request >
  Read Req Traffic panel) to literal English, matching the panel-name
  defect class from PR pingcap#23763.
- grafana-performance-overview-dashboard.md: restored all panel/metric
  labels across every section (Performance Overview, TiFlash, CDC) to
  literal English while keeping descriptions in Japanese; also fixed
  several scrambled/garbled sentences found in the same pass (QPS, avg by
  type, kv request by type bullets) and a duplicated Raft/Raft typo.
- grafana-resource-control-dashboard.md: same treatment across all 3
  metric sections.
- glossary.md: fixed a same-file self-contradiction where the Region/Peer
  section heading and its inbound link used 仲間 (an informal, wrong
  register for 'peer') while the section's own body text already
  correctly used the established term ピア for the identical concept.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@yahonda
yahonda marked this pull request as ready for review September 9, 2026 00:30
@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 Sep 9, 2026
@yahonda

yahonda commented Sep 9, 2026

Copy link
Copy Markdown
Member Author

Split into #23783 (part A, 99 files) and #23784 (part B, 98 files) to stay under CodeRabbit's 150-file review limit (this PR had 197 files). Both halves are already fully reviewed (see this PR's own review history for the 6-batch verification pass) -- closing this one in favor of the two split PRs.

@yahonda yahonda closed this Sep 9, 2026
yahonda added a commit to yahonda/docs that referenced this pull request Sep 9, 2026
…shboard from this PR

Both files fully overlapped with PR pingcap#23783/pingcap#23784 (the split halves of
the 要求-to-リクエスト sweep, one of which had already fully restored
grafana-performance-overview-dashboard.md's panel names). Since this
branch was built from a pre-pingcap#23774 baseline, keeping these files here
would revert that already-merged-in-spirit work and create a same-line
merge conflict with pingcap#23783. The genuine new fixes from this PR (Raft
apply/ready jargon, and the panel-name restoration for
dashboard-monitoring.md that hadn't been done anywhere else) have been
reapplied directly onto PR pingcap#23783's branch instead, so nothing is lost
-- just moved to avoid duplicating/conflicting with already-in-flight
work.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
yahonda added a commit to yahonda/docs that referenced this pull request Sep 10, 2026
Split from PR pingcap#23774 into two halves to stay under CodeRabbit's
150-file review limit (originally 197 files). See PR pingcap#23774 for the
full context and review history -- both halves together are this
same corpus-wide term-unification plus the incidental mistranslation
fixes found while reviewing it.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
yahonda added a commit to yahonda/docs that referenced this pull request Sep 10, 2026
Split from PR pingcap#23774 into two halves to stay under CodeRabbit's
150-file review limit (originally 197 files). See PR pingcap#23774 for the
full context and review history -- both halves together are this
same corpus-wide term-unification plus the incidental mistranslation
fixes found while reviewing it.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/develop This PR relates to the area of TiDB App development. missing-translation-status This PR does not have translation status info. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant