i18n(ja): restore literal dotted config/API identifiers mistranslated into Japanese - #23617
i18n(ja): restore literal dotted config/API identifiers mistranslated into Japanese#23617yahonda wants to merge 1 commit into
Conversation
… into Japanese Fixes 8 sites across 6 files where a segment of a literal dotted config key or API permission string (e.g. server.simplify-metrics, gc.auto-compaction, storage.objects.list) had been translated word-by-word into Japanese, breaking the identifier.
|
[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
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (6)
Included review availability: Your plan provides up to 4 included reviews per hour; 3 remain after this review. 📝 WalkthroughWalkthroughThis documentation update corrects TiKV configuration references, normalizes configuration headings, updates release-note links, and fixes GCS IAM permission names. ChangesDocumentation corrections
Estimated code review effort: 1 (Trivial) | ~3 minutes Merge Risk: ⚪ Minimal · up to This change restores literal configuration and API identifiers in Japanese documentation without changing product behavior; no actionable merge-blocking risk remains beyond normal checks and review. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
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. (6 skipped: 6 unsupported.) Full details: Description checkExplanation The description covers the required change summary, affected documentation version, reference context, AI involvement, and change-category checklist. The omitted first-time contributor checklist is optional. ✨ 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 |
1 participant
What is changed, added or deleted? (Required)
Found while reviewing #23616: a dotted config key or API permission string (e.g.
storage.objects.list,server.simplify-metrics,gc.auto-compaction) sometimes had one segment translated word-by-word into Japanese, breaking the literal identifier. Fixed 8 such sites across 6 files, all verified against the English source:tidb-cloud/dedicated-external-storage.md:storage.get(missing "objects" segment) →storage.objects.get;storage.オブジェクトリスト→storage.objects.listreleases/release-6.2.0.md:[サーバー.simplify-metrics]→[server.simplify-metrics];[クォータ.バックグラウンド読み取り帯域幅]→[quota.background-read-bandwidth]tidb-lightning/tidb-lightning-configuration.md:### tidb.セキュリティ→### tidb.security(a separate inline reference to the same section elsewhere in the file was already correctly literal, so this fixes a self-contradiction);### tidb.セッション変数→### tidb.session-varstikv-configuration-file.md:## gc.自動圧縮→## gc.auto-compactiontiproxy/tiproxy-configuration.md:### log.ログファイル→### log.log-filereleases/release-5.3.0.md:ストレージの.block-cache.capacity→storage.block-cache.capacity(also removes a stray leading dot)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