i18n(ja): fix the "thread"/"yarn" mistranslation#23329
Conversation
|
Skipping CI for Draft Pull Request. |
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
The old MT pipeline rendered English "thread" as 糸 (literal "thread/yarn"): - system-variables.md: "Unit: Threads" → 単位:スレッド (16 places) - tidb-cloud/data-service-oas-with-nextjs.md: [yarn] link text → [yarn] (1 place) Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
008089e to
6e0e5e6
Compare
What is changed, added or deleted? (Required)
The old machine-translation pipeline rendered English "thread" as 糸 (the literal Japanese word for thread/yarn), which is wrong in these technical contexts:
system-variables.md(16 places):Unit: Threadswas translated as単位:糸→ corrected to単位:スレッド. Affects concurrency variables such astidb_distsql_scan_concurrency,tidb_build_stats_concurrency, etc.tidb-cloud/data-service-oas-with-nextjs.md(1 place): the link text for the yarn package manager was translated to[糸]→ restored to[yarn].No English/source content changed; only the Japanese rendering.
Which TiDB version(s) do your changes apply to? (Required)
What is the related PR or file link(s)?
N/A — cleanup of legacy MT artifacts on the ja translation branch.