i18n(ja): fix state/executions/plans mistranslated as unrelated homonyms - #23749
Conversation
|
Warning Review limit reachedNext included review available in 4 minutes. View limit detailsLimit details: You’ve used all 4 included reviews currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Team Run ID: 📒 Files selected for processing (8)
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 |
…er terminology in PR pingcap#23635
[LGTM Timeline notifier]Timeline:
|
What is changed, added or deleted? (Required)
Found while investigating a similar defect reported on PR #23635 (DM-worker's "state" mistranslated as 州, the word for a US state/province). A corpus-wide search turned up the same false-friend pattern (an English word, or a literal system/UI value, mistranslated using an unrelated homonym or an unnecessary Japanese rendering) in several files:
"state" mistranslated as 州 (province):
ticdc/ticdc-open-api.md,ticdc/ticdc-open-api-v2.md: "the currentstateof the replication task" — corrected the mistranslation and a stray duplicated状態.tidb-cloud/essential-changefeed-overview.md: "The states are described as follows"."execution" mistranslated as 処刑 (capital punishment):
sql-statements/sql-statement-show-backups.md:Wait | Waiting for execution.tidb-cloud/top-ru.md: theExecutionscolumn, in both of the file's two RU tables.Literal UI/API/output values unnecessarily translated into Japanese (a user comparing the doc against actual product output would no longer find a match):
sql-statements/sql-statement-show-backups.md: theStatecolumn's literal enum values (Backup/Wait/Checksum) had been translated into Japanese words; restored to the literal English values shown bySHOW BACKUPS.tidb-cloud/top-ru.md: both tables' "Column"/"Section" values (SQL Statement,Total RU,Mean RU,Share,Executions,Plans,Total latency,Mean latency,SQL Digest) are the literal column/section names shown in the TiDB Cloud dashboard; restored from their translated Japanese forms to the literal English names (the adjacentPlanscolumn was also previously mistranslated as 予定, "a scheduled appointment").tidb-cloud/tidb-cloud-console-auditing.md: all 89 rows of the "Console audit event types" table had the literal event-type identifier (e.g.CreateOrganization,LoginOrganization,PauseCluster) translated into a Japanese descriptive phrase instead of being kept as the literal value that appears in actual console audit logs.ticdc/ticdc-canal-json.md: 5 of 14 literal Canal-JSON output field names (database,table,type,data,old, and the casing ofsql) were translated instead of kept as the literal JSON keys a user parses from real TiCDC output.ticdc/ticdc-open-protocol.md: literal example JSON values in the column-value mapping table ("test","key1"/"value1") had been translated into Japanese text inside the JSON example, which would no longer match real output.All fixes verified against the English source on
release-8.5.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?