i18n(ja): keep literal TiDB error message text in English - #23618
i18n(ja): keep literal TiDB error message text in English#23618yahonda wants to merge 2 commits into
Conversation
Fixes 3 sites where a literal, log-matchable error message string (e.g. "Information schema is out of date") had been translated into Japanese, breaking its usefulness for searching actual log/error output.
ti-chi-bot
Bot
added
the
missing-translation-status
|
[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
the
size/XS
📝 WalkthroughWalkthroughThe documentation updates three Information Schema references from Japanese text to English error-message terminology. The FAQ anchor and troubleshooting explanation remain unchanged. ChangesInformation Schema terminology
Estimated code review effort: 1 (Trivial) | ~3 minutes Merge Risk: 🔵 Low · up to The PR corrects three Japanese documentation references, but one troubleshooting label still differs from the literal TiDB error text and may hinder log searches. This is a bounded documentation issue that is mergeable with explicit owner follow-up. 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. (3 skipped: 3 unsupported.) Full details: Description checkExplanation The description explains the change, lists all three affected files, identifies the applicable Japanese TiDB 8.5 branch, provides a related reference, and records AI involvement. Required sections are substantially complete. ✨ 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 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 33a322d6-8ca5-4bba-990c-35bb2bf94238
📒 Files selected for processing (3)
faq/sql-faq.mdtidb-cloud/sql-concepts.mdtroubleshoot-tidb-cluster.md
Included review availability: Your plan provides up to 4 included reviews per hour; 2 remain after this review.
…and schema) Per CodeRabbit review: the correct error text is "Information schema is out of date" (matching 7 other occurrences across the corpus), not "InformationSchema" (one word) as originally applied.
1 participant
What is changed, added or deleted? (Required)
Found while reviewing #23616 (and the follow-up information_schema check): a literal, log-matchable TiDB error message string had been translated into Japanese, breaking its usefulness for grepping actual log/error output. Fixed 3 sites, all verified against the English source:
faq/sql-faq.md: heading「情報スキーマが古くなっています」というエラーの原因は何ですか?→「Information schema is out of date」というエラーの原因は何ですか?(the body of the same section already correctly kept the literal string in English — the heading was self-contradicting it)troubleshoot-tidb-cluster.md:情報スキーマが古くなっています:→InformationSchema is out of date:(matches the literal log message text)tidb-cloud/sql-concepts.md:「情報スキーマが変更されました」というエラー→「Information schema is changed」というエラーNote: the general translation "情報スキーマ" for the Information Schema feature/concept name elsewhere in the corpus (e.g.
information-schema/information-schema.md's own H1) is correct and unaffected by this PR — only these 3 literal quoted-error-message instances were wrong.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