i18n(ja): join top 30 katakana compound word-pairs - #23577
Merged
qiancai merged 9 commits intoAug 25, 2026
Merged
Conversation
Corpus-wide scan found 1,908 distinct katakana-compound word pairs written with a stray internal space (inherited from the English source's word-boundary space during MT), affecting ~1,100+ files. For 332 pairs occurring 5+ times, direction is per-pair, not uniform - most (but not all) are majority no-space, i.e. spaced is the minority MT artifact. This PR fixes only the top 30 clearest no-space-majority pairs (joined-count exceeds spaced-count by >=1.3x and by >=15 occurrences, e.g. プライベートエンドポイント 406 vs 178, リソースグループ 301 vs 173, ログバックアップ 405 vs 87), 2,139 occurrences across 484 files. Deliberately excluded pairs with ambiguous or reversed direction (e.g. アクセス リスト 94 vs 87 - too close; インタラクティブ モード 5 vs 64, デバッグ モード 3 vs 55, ターゲット クラスター 14 vs 47, インポート ブロック 1 vs 30 - space is actually the majority for these, a separate fix in the opposite direction). Fix is deliberately narrow: only the 30 selected (word1, word2) pairs had their exact adjacent occurrence joined; other katakana compounds sharing a word (e.g. データ エクスポート タスク) were left untouched since they are not among the validated pairs. Verified 0 remaining spaced instances for all 30 pairs and 0 anomalies in line-count/ **-count/[-count/]-count across all 484 changed files. Remaining long tail (302 more no-space-majority pairs down to freq=5, 79 reversed-direction pairs, and an unvetted <5-freq tail of 1,611 pairs) is deferred to future sweeps - logged in memory. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
|
ti-chi-bot
Bot
added
area/develop
|
[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 |
|
Important Review skippedToo many files! This PR contains 873 files, which is 723 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 (873)
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 |
ti-chi-bot
Bot
added
the
size/XXL
Found via user review: lines already touched by the top-30 batch often had OTHER katakana-compound pairs still spaced right next to the fixed one (e.g. データ インポートタスク - インポートタスク was joined by the top-30 batch but データ+インポート wasn't), creating a visibly inconsistent mix on the same line. Rescanned every line changed by the previous commit for any remaining katakana-adjacent-space pair, computed each pair's corpus-wide joined-vs-spaced count, and joined every pair where the joined form is the clear majority (209 pairs, 1,435 occurrences, 446 files). Skipped 115 pairs where spaced is majority or the counts are too close to call (e.g. アクセス リスト 94 vs 87, ターゲット クラスター 47 vs 14 - space is actually majority for that one). Also fixed one single-occurrence case on semantic grounds (no corpus-frequency data either way): グローバルインデックス パターン -> グローバルインデックスパターン, matching EN "global index patterns" as one descriptive phrase. Verified 0 anomalies in line-count/**-count/[-count/]-count across all 446 changed files. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Member
Author
|
Follow-up commit ( Re-scanned every line the first commit touched for any remaining katakana-adjacent-space pair (324 distinct pairs found on those lines), computed each pair's full corpus-wide joined-vs-spaced count, and joined every pair where joined > spaced: 209 pairs qualified, 1,435 occurrences across 446 files. Skipped 115 pairs where spaced ties or wins (consistent with the reversed-pair list in the PR description, e.g. アクセス リスト 94 vs 87, ターゲット クラスター 47 vs 14). Also joined one single-occurrence case on semantic grounds (グローバルインデックス パターン → グローバルインデックスパターン, matching EN "global index patterns" as one phrase). Verified 0 anomalies in line-count/ |
Rescanned the full corpus after batches 1-2 for remaining katakana-compound word pairs with an internal space, lowering the frequency threshold to >=3 occurrences (from >=5) to extend coverage. Joined every pair where the joined form is the clear majority corpus-wide (joined > spaced): 249 pairs, 1,824 occurrences across 583 files, including common technical compounds such as ストレージエンジン, オプティマイザヒント, プルリクエスト, クエリログ, キャッシュテーブル, リーダーノード, フォロワーノード, データレプリケーション, and バッチサイズ. Skipped 196 pairs where spaced ties or wins, consistent with the previously-identified reversed/ambiguous set (アクセス リスト, インタラクティブ モード, パフォーマンス テスト, デバッグ モード, ターゲット クラスター, インポート ブロック, サービス ノード, etc.). Verified 0 remaining spaced instances for all 249 pairs and 0 anomalies in line-count/**-count/[-count/]-count across all 583 changed files. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
インタラクティブ モード -> インタラクティブモード, joining the remaining pre-existing spaced instances (this term's corpus majority was originally spaced, but per user preference, katakana compounds should generally stay unspaced). 64 occurrences across 10 files. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
yahonda
force-pushed
the
fix-katakana-compound-spacing-2026-08-20
branch
from
August 20, 2026 02:14
0207389 to
bfe938b
Compare
K 近傍 -> K近傍 (3 occurrences, 1 file). The established Japanese ML terminology for "K-nearest neighbor" is K近傍法/k近傍法 with no space between K and 近傍 (matching other standard terms like K平均法); the space was an MT artifact carried over from the English "K-Nearest" hyphen/space position. The file had both forms mixed 3-3. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
qiancai
added
translation/no-need
# Conflicts: # best-practices/saas-best-practices.md # br/backup-and-restore-storages.md # dashboard/dashboard-profiling.md # develop/dev-guide-create-secondary-indexes.md # develop/dev-guide-gui-datagrip.md # develop/dev-guide-gui-dbeaver.md # develop/dev-guide-gui-mysql-workbench.md # develop/dev-guide-gui-navicat.md # develop/dev-guide-gui-vscode-sqltools.md # develop/dev-guide-sample-application-aws-lambda.md # develop/dev-guide-sample-application-golang-gorm.md # develop/dev-guide-sample-application-golang-sql-driver.md # develop/dev-guide-sample-application-java-hibernate.md # develop/dev-guide-sample-application-java-jdbc.md # develop/dev-guide-sample-application-java-mybatis.md # develop/dev-guide-sample-application-java-spring-boot.md # develop/dev-guide-sample-application-nextjs.md # develop/dev-guide-sample-application-nodejs-mysql2.md # develop/dev-guide-sample-application-nodejs-mysqljs.md # develop/dev-guide-sample-application-nodejs-prisma.md # develop/dev-guide-sample-application-nodejs-sequelize.md # develop/dev-guide-sample-application-nodejs-typeorm.md # develop/dev-guide-sample-application-python-django.md # develop/dev-guide-sample-application-python-mysql-connector.md # develop/dev-guide-sample-application-python-mysqlclient.md # develop/dev-guide-sample-application-python-peewee.md # develop/dev-guide-sample-application-python-pymysql.md # develop/dev-guide-sample-application-python-sqlalchemy.md # develop/dev-guide-sample-application-ruby-mysql2.md # develop/dev-guide-sample-application-ruby-rails.md # dm/dm-webui-guide.md # sql-plan-management.md # system-variables.md # tidb-cloud/changefeed-sink-to-mysql.md # tidb-cloud/configure-external-storage-access.md # tidb-cloud/configure-sql-users.md # tidb-cloud/data-service-manage-data-app.md # tidb-cloud/data-service-manage-endpoint.md # tidb-cloud/integrate-tidbcloud-with-vercel.md # tidb-cloud/integrate-tidbcloud-with-zapier.md # tidb-cloud/migrate-from-mysql-using-aws-dms.md # tidb-cloud/migrate-from-mysql-using-data-migration.md # tidb-cloud/migrate-from-op-tidb.md # tidb-cloud/premium/migrate-from-op-tidb-premium.md # tidb-cloud/premium/set-up-sink-private-endpoint-premium.md # tidb-cloud/releases/release-notes-2022.md # tidb-cloud/releases/release-notes-2023.md # tidb-cloud/releases/release-notes-2024.md # tidb-cloud/releases/release-notes-2025.md # tidb-cloud/releases/tidb-cloud-release-notes.md # tidb-cloud/set-up-private-endpoint-connections-on-azure.md # tidb-cloud/set-up-sink-private-endpoint.md # tidb-cloud/setup-aws-self-hosted-kafka-private-link-service.md # tidb-cloud/tidb-cloud-budget.md # tidb-cloud/tidb-cloud-glossary.md # tidb-cloud/tidb-cloud-org-sso-authentication.md # tidb-cloud/tidb-node-group-management.md # tidb-cloud/tidb-x-architecture.md # tikv-configuration-file.md # tiup/tiup-component-dm.md
# Conflicts: # best-practices/saas-best-practices.md # dashboard/dashboard-profiling.md # develop/dev-guide-gui-datagrip.md # develop/dev-guide-gui-dbeaver.md # develop/dev-guide-gui-mysql-workbench.md # develop/dev-guide-gui-navicat.md # develop/dev-guide-gui-vscode-sqltools.md # develop/dev-guide-sample-application-aws-lambda.md # develop/dev-guide-sample-application-golang-gorm.md # develop/dev-guide-sample-application-golang-sql-driver.md # develop/dev-guide-sample-application-java-hibernate.md # develop/dev-guide-sample-application-java-jdbc.md # develop/dev-guide-sample-application-java-mybatis.md # develop/dev-guide-sample-application-java-spring-boot.md # develop/dev-guide-sample-application-nextjs.md # develop/dev-guide-sample-application-nodejs-mysql2.md # develop/dev-guide-sample-application-nodejs-mysqljs.md # develop/dev-guide-sample-application-nodejs-prisma.md # develop/dev-guide-sample-application-nodejs-sequelize.md # develop/dev-guide-sample-application-nodejs-typeorm.md # develop/dev-guide-sample-application-python-django.md # develop/dev-guide-sample-application-python-mysql-connector.md # develop/dev-guide-sample-application-python-mysqlclient.md # develop/dev-guide-sample-application-python-peewee.md # develop/dev-guide-sample-application-python-pymysql.md # develop/dev-guide-sample-application-python-sqlalchemy.md # develop/dev-guide-sample-application-ruby-mysql2.md # develop/dev-guide-sample-application-ruby-rails.md # dm/dm-webui-guide.md # tidb-cloud/backup-and-restore.md # tidb-cloud/changefeed-overview.md # tidb-cloud/changefeed-sink-to-apache-kafka.md # tidb-cloud/changefeed-sink-to-mysql.md # tidb-cloud/configure-external-storage-access.md # tidb-cloud/configure-sql-users.md # tidb-cloud/connect-via-standard-connection-serverless.md # tidb-cloud/connected-care-overview.md # tidb-cloud/data-service-api-key.md # tidb-cloud/data-service-manage-data-app.md # tidb-cloud/data-service-manage-endpoint.md # tidb-cloud/import-csv-files-serverless.md # tidb-cloud/import-csv-files.md # tidb-cloud/import-parquet-files-serverless.md # tidb-cloud/import-parquet-files.md # tidb-cloud/integrate-tidbcloud-with-vercel.md # tidb-cloud/integrate-tidbcloud-with-zapier.md # tidb-cloud/migrate-from-mysql-using-aws-dms.md # tidb-cloud/migrate-from-mysql-using-data-migration.md # tidb-cloud/migrate-from-op-tidb.md # tidb-cloud/migrate-incremental-data-from-mysql-using-data-migration.md # tidb-cloud/migrate-sql-shards.md # tidb-cloud/premium/connect-to-premium-via-aws-private-endpoint.md # tidb-cloud/premium/import-csv-files-premium.md # tidb-cloud/premium/migrate-from-op-tidb-premium.md # tidb-cloud/premium/set-up-sink-private-endpoint-premium.md # tidb-cloud/prometheus-grafana-integration.md # tidb-cloud/recovery-group-get-started.md # tidb-cloud/releases/release-notes-2022.md # tidb-cloud/releases/release-notes-2023.md # tidb-cloud/releases/release-notes-2024.md # tidb-cloud/releases/release-notes-2025.md # tidb-cloud/releases/tidb-cloud-release-notes.md # tidb-cloud/scale-tidb-cluster.md # tidb-cloud/serverless-export.md # tidb-cloud/serverless-private-link-connection-to-alicloud-rds.md # tidb-cloud/serverless-private-link-connection-to-amazon-msk.md # tidb-cloud/serverless-private-link-connection-to-aws-confluent.md # tidb-cloud/serverless-private-link-connection-to-self-hosted-kafka-in-alicloud.md # tidb-cloud/serverless-private-link-connection.md # tidb-cloud/set-up-private-endpoint-connections-on-azure.md # tidb-cloud/set-up-private-endpoint-connections-on-google-cloud.md # tidb-cloud/set-up-private-endpoint-connections-serverless.md # tidb-cloud/set-up-sink-private-endpoint.md # tidb-cloud/set-up-vpc-peering-connections.md # tidb-cloud/setup-aws-self-hosted-kafka-private-link-service.md # tidb-cloud/setup-azure-self-hosted-kafka-private-link-service.md # tidb-cloud/setup-self-hosted-kafka-private-service-connect.md # tidb-cloud/tidb-cloud-auditing.md # tidb-cloud/tidb-cloud-billing-ticdc-rcu.md # tidb-cloud/tidb-cloud-budget.md # tidb-cloud/tidb-cloud-connect-aws-dms.md # tidb-cloud/tidb-cloud-console-auditing.md # tidb-cloud/tidb-cloud-import-local-files.md # tidb-cloud/tidb-cloud-org-sso-authentication.md # tidb-cloud/tidb-cloud-poc.md # tidb-cloud/tidb-cloud-support.md # tidb-cloud/tidb-node-group-management.md # tidb-cloud/top-ru.md
yahonda
force-pushed
the
fix-katakana-compound-spacing-2026-08-20
branch
from
August 25, 2026 00:20
6f67677 to
d503411
Compare
Fixes same-file self-contradictions and remaining stray instances for 5 previously-established compound pairs (デバッグ モード, インポート ブロック, クラスタコマンド リスト, リソース コントローラー, リソース タイプ) plus 3 residual joined-form gaps for ナビゲーションペイン that survived earlier batches.
…tween katakana) Per user direction, this corpus's default for katakana compounds is to NOT insert a space between adjacent katakana words. Reverts the 5 add-space pairs from the previous commit (デバッグモード, インポートブロック, クラスタコマンドリスト, リソースタイプ, リソースコントローラークライアント) back to their one-word form; keeps the ナビゲーションペイン join fix, which already matched this direction.
qiancai
approved these changes
Aug 25, 2026
[LGTM Timeline notifier]Timeline:
|
yahonda
added a commit
to yahonda/docs
that referenced
this pull request
Aug 26, 2026
Rebased onto i18n-ja-release-8.5 after pingcap#23602 merged the markdownlint conformance fixes and after pingcap#23577's katakana compound-word joins. Re-verified and restored 8 katakana joins that had been silently reverted by the initial content-preserving merge on lines this branch also touched, using an independent scan comparing spaced-katakana runs in the result against upstream's already-joined form.
yahonda
added a commit
to yahonda/docs
that referenced
this pull request
Aug 26, 2026
Rebased onto i18n-ja-release-8.5 after pingcap#23602 merged the markdownlint conformance fixes and after pingcap#23577's katakana compound-word joins. Restored 4 katakana joins that had been silently reverted by the initial content-preserving merge on lines this branch also touched.
yahonda
added a commit
to yahonda/docs
that referenced
this pull request
Aug 26, 2026
Rebased onto i18n-ja-release-8.5 after pingcap#23602 merged the markdownlint conformance fixes and after pingcap#23577's katakana compound-word joins. Restored 291 katakana joins (converged over 2 passes) that had been silently reverted by the initial content-preserving merge on lines this branch also touched, verified via an independent scan comparing spaced-katakana runs in the result against upstream's joined form. Also fixed 2 pre-existing MD037 violations (literal multiplication asterisks misidentified as emphasis markers) found while verifying, matching how the English source escapes them.
yahonda
added a commit
to yahonda/docs
that referenced
this pull request
Aug 27, 2026
Rebase PR pingcap#23584 onto the advanced i18n-ja-release-8.5 base using the content-preserving line-merge method, and re-apply katakana compound-word joins (PR pingcap#23577) that were reverted where this branch also touched the same lines. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
yahonda
added a commit
to yahonda/docs
that referenced
this pull request
Aug 27, 2026
Rebased onto i18n-ja-release-8.5 after pingcap#23602 merged the markdownlint conformance fixes and after pingcap#23577's katakana compound-word joins. Re-verified and restored 8 katakana joins that had been silently reverted by the initial content-preserving merge on lines this branch also touched, using an independent scan comparing spaced-katakana runs in the result against upstream's already-joined form.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is changed, added or deleted? (Required)
Corpus-wide scan found 1,908 distinct katakana-compound word pairs written with a stray internal space (inherited from the English source's word-boundary space during MT), affecting 1,100+ files. For 332 pairs occurring 5+ times, direction is per-pair, not uniform — most (but not all) are majority no-space, i.e. the spaced form is the minority MT artifact.
This PR fixes only the top 30 clearest no-space-majority pairs (joined-count exceeds spaced-count by >=1.3x and by >=15 occurrences), 2,139 occurrences across 484 files:
プライベートエンドポイント(406 vs 178),リソースグループ(301 vs 173),レプリケーションタスク(311 vs 148),データソース(319 vs 140),データアプリ(305 vs 104),システムテーブル(244 vs 102),ナビゲーションペイン(250 vs 91),ログバックアップ(405 vs 87),テーブルスキーマ(175 vs 86),インポートモード(223 vs 70),プライベートリンク(176 vs 69),パーティションテーブル(507 vs 59),エラーメッセージ(249 vs 57),スレッドプール(142 vs 50),ノードグループ(69 vs 49),ターゲットテーブル(136 vs 46),ベストプラクティス(232 vs 46),ログファイル(233 vs 45),オペレーティングシステム(145 vs 43),バックアップデータ(212 vs 40),データファイル(182 vs 39),コンボボックス(106 vs 39),インポートタスク(91 vs 36),グローバルインデックス(143 vs 36),ターゲットマシン(83 vs 35),シャードテーブル(81 vs 35),リレーログ(168 vs 34),ソースファイル(119 vs 32),プランキャッシュ(342 vs 31),クエリパフォーマンス(78 vs 31).Deliberately excluded pairs with ambiguous or reversed direction, e.g.:
アクセス リスト94 vs 87 — too close to callインタラクティブ モード5 vs 64,デバッグ モード3 vs 55,ターゲット クラスター14 vs 47,インポート ブロック1 vs 30 — space is actually the majority for these; a separate future fix would need the opposite direction.Fix is deliberately narrow: only the 30 selected
(word1, word2)pairs had their exact adjacent occurrence joined. Other katakana compounds sharing a word (e.g.データ エクスポート タスク) were left untouched since they are not among the validated pairs — only the sub-part matching a selected pair got joined (e.g.データ インポート タスク→データ インポートタスク, joiningインポートタスクbut leavingデータseparate, sinceデータ+インポートitself is not one of the 30 validated pairs).Verified 0 remaining spaced instances for all 30 pairs and 0 anomalies in line-count/
**-count/[-count/]-count across all 484 changed files.Remaining long tail (302 more no-space-majority pairs down to freq=5, 79 reversed-direction pairs, and an unvetted <5-freq tail of 1,611 pairs) is deferred to future sweeps.
Which TiDB version(s) do your changes apply to? (Required)
What is the related PR or file link(s)?
AI agent involvement
Do your changes match any of the following descriptions?