i18n(ja): fix redundant or broken verb after get-support/report-a-bug links - #23460
i18n(ja): fix redundant or broken verb after get-support/report-a-bug links#23460yahonda wants to merge 1 commit into
Conversation
… links
The link text "[サポートを受ける](/support.md)" ("get support") and
"[バグを報告する](.../support)" ("report a bug") already contain a complete
verb. In 53 files, the MT pipeline appended (or scrambled in) a second,
unrelated trailing verb after the link (e.g. 取得してください, リクエスト
してください, 参照してください, お知らせください), producing redundant or
grammatically broken sentences.
Fixed by putting the intended verb form inside the link and leaving only a
plain sentence-ending period outside, matching the two correct patterns that
already existed in this corpus:
- imperative EN ("..., get support.") -> [サポートを受けて](...)ください。
- "you can get support" EN -> [サポートを受ける](...)ことができます。
Same two patterns applied to the 44 sql-statements/*.md "report a bug"
compatibility-note footers (38 imperative -> [バグを報告してください](...)。,
5 "you can report a bug" -> [バグを報告する](...)ことができます。;
sql-statement-create-table-like.md was already correct and left untouched).
Several tiflash/troubleshoot-tiflash.md sentences also had the log-collection
clause and the get-support clause scrambled together; reordered to collect
logs first, then get support, matching the English source.
Left out of scope: error-codes.md's one "Contact the developer ... or get
support" sentence, which lists three alternatives instead of English's two
but is not the redundant-trailing-verb defect this PR targets.
|
Skipping CI for Draft Pull Request. |
ti-chi-bot
Bot
added
the
do-not-merge/work-in-progress
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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
ti-chi-bot
Bot
removed
the
do-not-merge/work-in-progress
1 participant
What is changed, added or deleted? (Required)
Fixes a systematic MT artifact affecting 53 files: the link text
[サポートを受ける](/support.md)("get support") and[バグを報告する](.../support)("report a bug") already contain a complete verb, but the MT pipeline appended a second, redundant or scrambled trailing verb after the link (e.g.取得してください,リクエストしてください,参照してください,お知らせください,に収集します), producing broken or nonsensical sentences.Fix: move the intended verb form inside the link, matching the two correct patterns already present elsewhere in the corpus:
[サポートを受けて](...)ください。[サポートを受ける](...)ことができます。Same two patterns applied to the 44
sql-statements/*.mdMySQL-compatibility "report a bug" footers (38 imperative sites, 5 "you can report a bug" sites;sql-statement-create-table-like.mdwas already correct and left untouched).A few
tiflash/troubleshoot-tiflash.mdsentences also had the log-collection clause and the get-support clause scrambled together across the link boundary; reordered to "collect logs, then get support" to match the English source.Left out of scope:
error-codes.md's one "Contact the developer ... or get support" sentence, which lists three alternatives instead of English's two — not the redundant-trailing-verb defect this PR targets, deferred separately.Which TiDB version(s) do your changes apply to? (Required)
What is the related PR or file link(s)?
N/A
AI agent involvement
Do your changes match any of the following descriptions?