i18n(ja): remove stray zero-width-space MT artifacts - #23778
Open
yahonda wants to merge 1 commit into
Open
Conversation
Removes 381 stray U+200B (zero-width space) characters embedded mid-word across 111 files -- a known legacy MT-tool artifact class. Scope decided by cross-checking upstream/release-8.5: 380 occurrences across 110 files had no corresponding zero-width space anywhere in the EN source file at all, confirming a pure JA-side artifact, safely removed. One more occurrence (releases/release-6.0.0-dmr.md) was in a file that also contains zero-width spaces in EN, but at different, unrelated lines -- checked this specific occurrence's exact EN counterpart sentence individually and confirmed it has no zero-width space there either, so removed just this one instance while leaving the file's other unrelated EN-side artifacts alone (out of scope for a JA translation fix). Deliberately LEFT UNCHANGED: dm/dm-binlog-event-filter.md (3 occurrences) and dm/dm-block-allow-table-lists.md (2 occurrences) -- both have the identical zero-width space at the identical position in the EN source (inside YAML config-block snippets), so this is inherited from EN, not a JA-only translation defect, and out of scope for this ja PR. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
Skipping CI for Draft Pull Request. |
ti-chi-bot
Bot
added
the
do-not-merge/work-in-progress
📝 WalkthroughWalkthroughThis documentation-only change normalizes Japanese text across AI, developer, TiDB Cloud, reference, and release-note pages. It removes invisible characters and applies minor wording and spacing corrections. No code or documented behavior changes. ChangesJapanese documentation normalization
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Other Merge Risk: 🔵 Low · up to This change cleans invisible characters from Japanese documentation, but several updated setup instructions remain grammatically unclear, including connection-string copy steps, a support-contact sentence, and TiProxy configuration guidance. The issues are low risk but should be corrected for clear user instructions before merge. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 Generate unit tests (beta)
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 |
|
[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 |
ti-chi-bot
Bot
added
missing-translation-status
yahonda
marked this pull request as ready for review
September 9, 2026 00:29
ti-chi-bot
Bot
removed
the
do-not-merge/work-in-progress
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 5
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Advanced
Run ID: f88558db-7382-4712-8b4a-68c4c3208767
📒 Files selected for processing (111)
ai/guides/vector-search-full-text-search-python.mdai/guides/vector-search-full-text-search-sql.mdai/integrations/vector-search-integrate-with-amazon-bedrock.mdai/vector-search-get-started-using-python.mdbasic-features.mdbasic-sql-operations.mdbest-practices/haproxy-best-practices.mdbest-practices/high-concurrency-best-practices.mdbest-practices/index-management-best-practices.mdbest-practices/massive-regions-best-practices.mdbest-practices/tidb-best-practices.mdbest-practices/tidb-partitioned-tables-best-practices.mdbr/backup-and-restore-overview.mdbr/br-log-architecture.mdbr/br-snapshot-architecture.mddashboard/dashboard-intro.mddevelop/dev-guide-build-cluster-in-cloud.mddevelop/dev-guide-create-table.mddevelop/dev-guide-proxysql-integration.mddevelop/dev-guide-sample-application-aws-lambda.mddevelop/dev-guide-sample-application-golang-gorm.mddevelop/dev-guide-sample-application-golang-sql-driver.mddevelop/dev-guide-sample-application-java-hibernate.mddevelop/dev-guide-sample-application-java-jdbc.mddevelop/dev-guide-sample-application-java-mybatis.mddevelop/dev-guide-sample-application-java-spring-boot.mddevelop/dev-guide-sample-application-nextjs.mddevelop/dev-guide-sample-application-python-django.mddevelop/dev-guide-sample-application-python-mysql-connector.mddevelop/dev-guide-sample-application-python-mysqlclient.mddevelop/dev-guide-sample-application-python-peewee.mddevelop/dev-guide-sample-application-python-pymysql.mddevelop/dev-guide-sample-application-python-sqlalchemy.mddevelop/dev-guide-third-party-tools-compatibility.mddevelop/dev-guide-tidb-crud-sql.mddevelop/dev-guide-wordpress.mddevelop/serverless-driver-kysely-example.mddm/dm-precheck.mddynamic-config.mdfaq/deploy-and-maintain-faq.mdfaq/sql-faq.mdfunctions-and-operators/bit-functions-and-operators.mdfunctions-and-operators/json-functions/json-functions-validate.mdglossary.mdgrafana-tikv-dashboard.mdmigrate-from-mariadb.mdpd-control.mdperformance-tuning-practices.mdplacement-rules-in-sql.mdreleases/release-5.2.4.mdreleases/release-5.3.0.mdreleases/release-5.4.0.mdreleases/release-6.0.0-dmr.mdreleases/release-6.2.0.mdreleases/release-6.6.0.mdreleases/release-7.1.0.mdreleases/release-7.1.4.mdreleases/release-7.5.1.mdreleases/release-7.6.0.mdreleases/release-8.4.0.mdreleases/release-8.5.2.mdreleases/release-8.5.3.mdreleases/release-8.5.5.mdsql-statements/sql-statement-distribute-table.mdsql-statements/sql-statement-overview.mdticdc/deploy-ticdc.mdticdc/integrate-confluent-using-ticdc.mdticdc/ticdc-architecture.mdticdc/ticdc-faq.mdtidb-cloud/built-in-monitoring.mdtidb-cloud/connect-to-tidb-cluster.mdtidb-cloud/connect-via-standard-connection-serverless.mdtidb-cloud/connect-via-standard-connection.mdtidb-cloud/connected-ai-chat-in-im.mdtidb-cloud/connected-lark-ticket-creation.mdtidb-cloud/connected-lark-ticket-interaction.mdtidb-cloud/dedicated-external-storage.mdtidb-cloud/import-with-mysql-cli.mdtidb-cloud/integrate-tidbcloud-with-airbyte.mdtidb-cloud/manage-serverless-spend-limit.mdtidb-cloud/manage-user-access.mdtidb-cloud/migrate-metrics-integrations.mdtidb-cloud/migrate-prometheus-metrics-integrations.mdtidb-cloud/premium/built-in-monitoring-premium.mdtidb-cloud/premium/connect-to-premium-via-alibaba-cloud-private-endpoint.mdtidb-cloud/premium/connect-to-premium-via-public-connection.mdtidb-cloud/premium/tidb-cloud-billing-ticdc-ccu.mdtidb-cloud/releases/release-notes-2020.mdtidb-cloud/releases/release-notes-2022.mdtidb-cloud/releases/release-notes-2023.mdtidb-cloud/releases/release-notes-2025.mdtidb-cloud/select-cluster-tier.mdtidb-cloud/serverless-high-availability.mdtidb-cloud/serverless-private-link-connection-to-amazon-msk.mdtidb-cloud/serverless-private-link-connection-to-self-hosted-kafka-in-alicloud.mdtidb-cloud/serverless-private-link-connection.mdtidb-cloud/set-up-private-endpoint-connections-on-alibaba-cloud.mdtidb-cloud/set-up-private-endpoint-connections-on-azure.mdtidb-cloud/set-up-private-endpoint-connections-on-google-cloud.mdtidb-cloud/set-up-private-endpoint-connections-serverless.mdtidb-cloud/setup-aws-self-hosted-kafka-private-link-service.mdtidb-cloud/tidb-cloud-glossary.mdtidb-cloud/tidb-x-architecture.mdtidb-cloud/tidbx-instance-move-faq.mdtidb-lightning/tidb-lightning-configuration.mdtidb-troubleshooting-map.mdtime-to-live.mdtiproxy/tiproxy-configuration.mdtiup/tiup-cluster-topology-reference.mdtiup/tiup-cluster.mdtune-tikv-memory-performance.md
Included review availability: Your plan provides up to 4 included reviews per hour; 3 remain after this review.
6 tasks
yahonda
added a commit
to yahonda/docs
that referenced
this pull request
Sep 9, 2026
…his PR PR pingcap#23778 (zero-width-space removal) touches the exact same lines this PR already modifies for the missing-particle/parenthesis fix. Removing the zero-width space here too avoids a same-line merge conflict regardless of which PR merges first. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This was referenced Sep 9, 2026
qiancai
added
translation/no-need
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)
Removes 381 stray U+200B (zero-width space) characters embedded mid-word across 111 files -- a known legacy MT-tool artifact class (see other examples already fixed under this class in prior PRs).
Scope decided by cross-checking
upstream/release-8.5: 380 occurrences across 110 files had no corresponding zero-width space anywhere in the EN source file at all, confirming a pure JA-side artifact, safely removed. One more occurrence (releases/release-6.0.0-dmr.md) was in a file that also contains zero-width spaces in EN, but at different, unrelated lines -- checked this specific occurrence's exact EN counterpart sentence individually and confirmed it has no zero-width space there either, so removed just this one instance.Deliberately LEFT UNCHANGED:
dm/dm-binlog-event-filter.md(3 occurrences) anddm/dm-block-allow-table-lists.md(2 occurrences) -- both have the identical zero-width space at the identical position in the EN source (inside YAML config-block snippets), so this is inherited from EN, not a JA-only translation defect, and out of scope for this ja PR.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?
Summary by CodeRabbit