i18n(ja): fix swapped word order across the corpus - #23698
Conversation
|
Skipping CI for Draft Pull Request. |
ti-chi-bot
Bot
added
the
do-not-merge/work-in-progress
|
[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
|
Warning Review limit reachedNext included review available in 15 minutes. View limit detailsLimit details: You’ve used all 4 included reviews currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Team Run ID: 📒 Files selected for processing (3)
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Team Run ID: 📒 Files selected for processing (17)
Included review availability: Your plan provides up to 4 included reviews per hour; 2 remain after this review. 📝 WalkthroughWalkthroughThe diff corrects Japanese wording in TiDB release notes from versions 5.1.0 through 8.5.2 and in TiDB Cloud CLI documentation. The changes clarify technical term relationships, command attribution, error descriptions, and sentence structure. ChangesJapanese documentation corrections
Estimated code review effort: 1 (Trivial) | ~5 minutes Merge Risk: 🔵 Low · up to This change improves Japanese release-note and CLI wording, but three release-note entries still contain punctuation, terminology, or code-formatting defects that can confuse readers. The impact is limited to documentation and is suitable for prompt owner follow-up. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Description checkExplanation The description explains the changes, affected files, validation method, target version, AI involvement, and applicable checklist items. The reference-link fields are blank, but they are non-critical because the description provides sufficient context. Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (17 skipped: 17 unsupported.) ✨ 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 |
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: 3
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Team
Run ID: 15f5254d-f313-4e77-b43e-7dde2b4b58ba
📒 Files selected for processing (17)
releases/release-5.1.0.mdreleases/release-5.1.5.mdreleases/release-5.2.0.mdreleases/release-5.2.4.mdreleases/release-6.3.0.mdreleases/release-6.4.0.mdreleases/release-7.3.0.mdreleases/release-7.5.0.mdreleases/release-7.6.0.mdreleases/release-8.0.0.mdreleases/release-8.2.0.mdreleases/release-8.3.0.mdreleases/release-8.4.0.mdreleases/release-8.5.0.mdreleases/release-8.5.1.mdreleases/release-8.5.2.mdtidb-cloud/get-started-with-cli.md
Included review availability: Your plan provides up to 4 included reviews per hour; 2 remain after this review.
ec5d538 to
901bb3e
Compare
qiancai
added
translation/no-need
EN says to use \`tiup cloud\` instead of \`ticloud\` when using TiUP, but JA had it backwards, and carried a stray MT-artifact brace after \`ticloud\`. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Corpus-wide sweep of release notes found 41 sentences where two backtick-quoted identifiers (config items, error strings, SQL keywords, table/column names) had their positions swapped relative to EN, reversing which term modifies which. Fixed across 16 files. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
The bullet ended with the continuative form 修正し instead of the sentence-final 修正しました used by every sibling bullet in this list. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
901bb3e to
3712c30
Compare
|
Note GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer. |
2 participants
What is changed, added or deleted? (Required)
Corpus-wide sweep for a recurring defect class: a sentence contains two backtick-quoted identifiers (config items, table/column names, SQL keywords, error strings) whose relative positions got swapped in the Japanese translation, reversing which term modifies which (e.g. "the DELETE privilege on user" becoming "the user privilege on DELETE").
Fixed 42 occurrences across 17 files:
tidb-cloud/get-started-with-cli.md: reversed recommendation to useticloudinstead oftiup cloud(should be the other way around per EN), plus a stray MT-artifact bracereleases/*.mdfiles (release-5.1.0.md through release-8.5.2.md)Each fix was verified against the corresponding EN source in
release-8.5, including cross-checking sibling release files that backport the same PR/issue (several already had the correct order, confirming these were isolated translation slips rather than systemic).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
tiup cloudcommand and removal of an extraneous character.