i18n(ja): fix straddling-bracket defects around New Relic's Import dashboard button - #23540
Merged
qiancai merged 1 commit intoAug 17, 2026
Conversation
…shboard button
monitor-new-relic-integration.md had two pre-existing MT defects on
the 'Import dashboard' step (predating any of this session's UI-label
batches): one split the word ダッシュボード in half across a bold
marker boundary ('ダッシュ**ボードのインポート」**'), the other
trapped '[...] を' decoration inside the bold span
('**[ダッシュボードをインポート] を**'). Cleaned both into a single
consistent 「ダッシュボードのインポート」 quoted term, matching the
sibling 「ダッシュボード」 bold-quote convention already used earlier
in the same step.
ti-chi-bot
Bot
added
the
do-not-merge/work-in-progress
|
Skipping CI for Draft Pull Request. |
|
[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 |
|
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 |
ti-chi-bot
Bot
added
missing-translation-status
yahonda
marked this pull request as ready for review
August 17, 2026 05:13
ti-chi-bot
Bot
removed
the
do-not-merge/work-in-progress
3 tasks
qiancai
added
translation/no-need
qiancai
approved these changes
Aug 17, 2026
[LGTM Timeline notifier]Timeline:
|
yahonda
added a commit
to yahonda/docs
that referenced
this pull request
Aug 18, 2026
…onfirmed batch) These 228 candidate labels were skipped by the mechanical 2-word batch (pingcap#23535) because they couldn't be confirmed via a plain dbaas-ui grep (mostly third-party console fields — AWS, Azure, Alibaba Cloud, GCP, Kafka, Datadog, New Relic, n8n, Airbyte, PagerDuty, Slack — which dbaas-ui doesn't cover, plus a handful of TiDB-native labels the grep missed). Each was individually triaged against EN (release-8.5) and, for TiDB-native items, dbaas-ui with a strict STRONG/WEAK/ COMMENT_ONLY/NO_HIT classifier, distinguishing genuine clickable UI elements from prose/marketing/category-header bullets that merely share the same words (the "No cost"/"High availability" false-positive pattern from earlier batches). 265 occurrences fixed across 47 files. ~70 further candidates were deliberately left in Japanese as category-header/concept-heading prose, not clickable UI (same precedent as architecture-concepts.md). Along the way this also fixed several pre-existing defects surfaced by the same EN comparison: mismatched AWS IAM button-label pairs (Attach Policies vs Attach Policy treated as the same word), particle- and bracket-trapped-in-bold spans, a word-order/position-pairing mis-mapping (Source/Target engine, Signing method/Account key, Export Path), a mistranslation (一般公開→Public accessible), and an orphaned bracket left over from an incomplete straddling-bracket fix. "Import dashboard" (monitor-new-relic-integration.md) was explicitly skipped — already handled by pingcap#23540.
yahonda
added a commit
to yahonda/docs
that referenced
this pull request
Aug 19, 2026
…onfirmed batch) These 228 candidate labels were skipped by the mechanical 2-word batch (pingcap#23535) because they couldn't be confirmed via a plain dbaas-ui grep (mostly third-party console fields — AWS, Azure, Alibaba Cloud, GCP, Kafka, Datadog, New Relic, n8n, Airbyte, PagerDuty, Slack — which dbaas-ui doesn't cover, plus a handful of TiDB-native labels the grep missed). Each was individually triaged against EN (release-8.5) and, for TiDB-native items, dbaas-ui with a strict STRONG/WEAK/ COMMENT_ONLY/NO_HIT classifier, distinguishing genuine clickable UI elements from prose/marketing/category-header bullets that merely share the same words (the "No cost"/"High availability" false-positive pattern from earlier batches). 265 occurrences fixed across 47 files. ~70 further candidates were deliberately left in Japanese as category-header/concept-heading prose, not clickable UI (same precedent as architecture-concepts.md). Along the way this also fixed several pre-existing defects surfaced by the same EN comparison: mismatched AWS IAM button-label pairs (Attach Policies vs Attach Policy treated as the same word), particle- and bracket-trapped-in-bold spans, a word-order/position-pairing mis-mapping (Source/Target engine, Signing method/Account key, Export Path), a mistranslation (一般公開→Public accessible), and an orphaned bracket left over from an incomplete straddling-bracket fix. "Import dashboard" (monitor-new-relic-integration.md) was explicitly skipped — already handled by pingcap#23540.
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
2 participants
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)
monitor-new-relic-integration.mdhad two pre-existing MT defects on the "Import dashboard" step, found during review of #23535 (unrelated to that PR — this text was never touched since it wasn't confirmed as literal English UI text, being a third-party New Relic console step):「ダッシュ**ボードのインポート」**をクリックします— the word ダッシュボード was split in half across a bold marker boundary.**[ダッシュボードをインポート] を**クリックします— decoration brackets and the を particle were trapped inside the bold span.Cleaned both into a single consistent
**「ダッシュボードのインポート」**quoted term, matching the sibling**「ダッシュボード」**bold-quote convention already used earlier in the same step.Which TiDB version(s) do your changes apply to? (Required)
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?