i18n(ja): restore genuine 2-word TiDB Cloud UI labels to English (unconfirmed batch) - #23543
Conversation
…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.
|
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
EN uses "New principals" (lowercase p) in backup-and-restore.md's GCS bucket-access step, unlike the "New Principals" (capital P) field-label wording used in the other 3 files this batch touched. Found during review of pingcap#23543.
ti-chi-bot
Bot
removed
the
do-not-merge/work-in-progress
qiancai
added
translation/no-need
2 participants
Summary
These 228 candidate labels were skipped by the mechanical 2-word batch (#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) that dbaas-ui doesn't cover, plus a handful of TiDB-native labels the grep missed.
Each candidate 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:
Attach PoliciesvsAttach Policypreviously translated as the same word)[仮想**ネットワーク]**defect flagged earlier this session)Public accessible)Import dashboard(monitor-new-relic-integration.md) was explicitly skipped — already handled by #23540.This PR's base is the same tip as #23535, and the two independently touch many of the same files (~40 overlapping lines). I already worked out and verified the correct merged resolution for all 40 conflicting hunks (combining whichever side had already progressed a given label to English, plus a few extra fixes found while reconciling: a dropped particle in
VPC Peeringを, an incorrect Signing method/Account key field-value swap, and a garbledAvailability zonelabel). That resolution is not included in this PR's diff (to keep this PR's diff scoped to only its own new content), but is ready to hand to whoever merges these two PRs — ping me and I'll apply it directly.While working out that resolution, I also discovered (but have not fixed, as it's out of this PR's scope) that #23535 independently conflicts with #23519 (3/4-word batch, ~142 conflict markers) and with #23516 (Note-label normalization, ~3 conflict markers). Both are pre-existing conflicts between those two already-open PRs, unrelated to this PR's changes — flagging for whoever sequences the merge order.
Test plan
**-parity/paren-balance issues in the diff (automated check)