i18n(ja): unescape stray gt entities to literal greater-than - #23570
Open
yahonda wants to merge 2 commits into
Open
i18n(ja): unescape stray gt entities to literal greater-than#23570yahonda wants to merge 2 commits into
yahonda wants to merge 2 commits into
Conversation
Follow-up to PR pingcap#23409, which fixed </&/"/&pingcap#39; but deliberately left > alone pending a per-instance audit (some > usage in this corpus legitimately mirrors English's own escaped <name> placeholders). This sweep classified all 231 files containing >: - 225 files (682 occurrences) where the English source has zero > usage at all: these are MT artifacts across version comparisons ("Python (>=3.10)"), UI breadcrumbs ("**Settings** > **Networking**"), Grafana dashboard paths, and "->" arrows ("PD -> TiKV"). Converted to literal >. - Of those 225, 4 files (operators.md, vector-search-functions-and- operators.md, non-transactional-dml.md, tiup-troubleshooting- guide.md) also had matching < artifacts forming a full escaped pair (SQL operators like `<>`, placeholders like `<component>`) with English also using zero </>; converted both together to avoid leaving a half-fixed pair. - 1 file with no English counterpart (vector-search-changelogs.md, ja-only content): converted the one occurrence, which matches the exact same version-comparison artifact pattern as the 682 above. - 4 files (96 occurrences, Kafka private link setup guides) where English DOES use > for its own <broker_id>/<port> placeholders: preserved those pairs untouched, converted only the surrounding breadcrumb/arrow > instances that don't appear in English. Verified both files' > counts now match English exactly. - 1 file (release-6.0.0-dmr.md) left untouched: its > usage is inside raw HTML table markup and matches English exactly. Verified no heading anchors changed (all touched headings keep their existing {#...} tag) and ** / [ / ] counts are unchanged per file. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
ti-chi-bot
Bot
added
area/develop
|
[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/XXL
|
Important Review skippedToo many files! This PR contains 230 files, which is 80 over the limit of 150. To get a review, reduce the PR to 150 files or fewer by splitting it into smaller PRs or changing its base branch. Upgrade to a paid plan to raise the limit. This review couldn't start because sufficient usage credits or metered capacity aren't available. Add credits or update usage-based reviews in the billing tab, then retry. ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (230)
You can disable this status message by setting the 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 |
…2026-08-19 Resolved 1 conflict: tidb-cloud/premium/tidb-cloud-auditing-premium.md had been rewritten by the PR pingcap#23573 sync (merged in the meantime), superseding the old >-fix line entirely. Took upstream's newer content. Verified 0 remaining > artifacts corpus-wide beyond the 5 files with legitimate <placeholder> usage already confirmed in the original PR. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
test seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
qiancai
added
translation/no-need
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)
Follow-up to PR #23409, which fixed
</&/"/'MT-introduced HTML entity artifacts but deliberately left>alone pending a per-instance audit, since some>usage in this corpus legitimately mirrors English's own escaped<name>placeholders.This PR does that audit across all 231 files containing
>:>usage at all: these are MT artifacts across version comparisons (Python (>=3.10)), UI breadcrumbs (**Settings** > **Networking**), Grafana dashboard paths, and->arrows (PD -> TiKV). Converted to literal>.operators.md,vector-search-functions-and-operators.md,non-transactional-dml.md,tiup-troubleshooting-guide.md) also had matching<artifacts forming a full escaped pair (SQL operators like`<>`, placeholders like`<component>`), with English also using zero</>. Converted both together to avoid leaving a half-fixed pair.vector-search-changelogs.md, ja-only content): converted its one occurrence, which matches the exact same version-comparison artifact pattern as the 682 above.>for its own<broker_id>/<port>placeholders: preserved those pairs untouched, converted only the surrounding breadcrumb/arrow>instances that don't appear in English. Verified both files'>counts now match English exactly after the fix.release-6.0.0-dmr.md) left untouched: its>usage is inside raw HTML table markup and matches English exactly.Verified no heading anchors changed (all touched headings keep their existing
{#...}tag) and**/[/]counts are unchanged per file (mechanical check across all 230 changed files, 0 anomalies).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?