i18n(ja): restore literal quoted config/status/enum values across the corpus - #23760
Draft
yahonda wants to merge 18 commits into
Draft
i18n(ja): restore literal quoted config/status/enum values across the corpus#23760yahonda wants to merge 18 commits into
yahonda wants to merge 18 commits into
Conversation
|
Important Review skippedToo many files! This PR contains 252 files, which is 102 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 configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Team Run ID: 📒 Files selected for processing (252)
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 |
|
[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
…not a literal value
…hanged to straight quotes
…er, and force insert
…atching body usage
…t Least Once semantics
# Conflicts: # dm/dm-query-status.md # dm/relay-log.md # tiup/tiup-component-dm-import.md # tiup/tiup-dm-topology-reference.md
…pped topic particle
yahonda
marked this pull request as draft
September 7, 2026 07:04
ti-chi-bot
Bot
added
the
do-not-merge/work-in-progress
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
1 participant
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)
Exhaustive corpus-wide sweep (all ~809 「」 occurrences in the JA docs, verified individually against the EN source on
release-8.5) for the defect class already fixed narrowly in #23758/#23759: a literal English system/API/UI/config/log value quoted with full-width Japanese corner brackets (「」) around a mistranslated Japanese word, or around the correct English word but in the wrong quote style — should be the literal string in straight double (or occasionally single, matching EN) quotes, or in backticks/bold where EN uses those instead.256 files, 241 fixes. Representative categories:
"index out of range","invalid connection","Can't find column in schema","GC can not work")"stderr","pd","tikv"/"unistore","offline","unified", SQL mode names, tiup/dmctl command strings)"Health Report","Logout","Overview","Alerts", various"Apply for ..."request-form literal text)"before"/"p", Canal-JSON/Avro protocol single-letter event codes, DMsynced/Check/Dump/Load/Sync— most of these were already fixed in i18n(ja): restore literal quoted status/enum values in DM docs #23758)Every non-fix candidate was checked against EN and left untouched when the quoting was ordinary Japanese punctuation or rhetorical/scare-quote emphasis that EN itself uses non-literally (e.g.
sql-mode.md's "traditional" SQL database description).Net diff is balanced (482 insertions / 482 deletions across the two triage passes, i.e. every changed line is a like-for-like single-line replacement) — no content was added or removed beyond the quoted value itself.
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?