i18n(ja): fix false-friend table header translations (Field/Value) - #23435
Open
yahonda wants to merge 15 commits into
Open
i18n(ja): fix false-friend table header translations (Field/Value)#23435yahonda wants to merge 15 commits into
yahonda wants to merge 15 commits into
Conversation
English table headers "Field" and "Value" were mistranslated as 分野
("domain"/"field of study") and 価値 ("worth"/"business value") instead of
the correct 分野->フィールド (a data field / column name) and 価値->値 (a data
value). These are false friends: 分野/価値 are valid Japanese words but the
wrong sense of the English homonym for a schema/config table header.
19 changes / 12 files: information-schema-slow-query.md, information-schema-cluster-info.md
("Field description:" heading), tidb-cloud/essential-database-audit-logging.md,
tidb-cloud/premium/tidb-cloud-auditing-premium.md, ticdc/integrate-confluent-using-ticdc.md
(both 分野 and 価値 in the same table), data-type-string.md, functions-and-operators/operators.md
("Negates value"), and 5 self-hosted-Kafka Private Link setup guides
("Information | Value | Note" tables).
Guardrails (verified): the many GENUINE uses of 分野 ("in the security field",
"financial sector", etc., 7 remaining) and 価値 ("business value", "TTL data
value", etc., 18 remaining) elsewhere are untouched -- counts dropped by
exactly 11 and 9 respectively, matching the number of header fixes.
|
[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
Two tables in this doc show the mapping of literal example values (from an
ENUM/SET column definition shown in a preceding SQL code block) to their
internal numeric/binary representation. The literal values were mistranslated,
breaking the correspondence with the SQL example they describe:
- ENUM('apple', 'orange', 'pear') table: 'apple'/'orange'/'pear' had been
translated to りんご/オレンジ/梨 (and wrapped in HTML entities instead of
quotes) -- restored to the literal English strings, matching the SQL example.
- SET('a','b','c','d') table: 'a'/'b'/'d' had been transliterated to the
phonetic Japanese characters 「あ」/「b」/「d」 (spelling out the letter name)
and 'c' was HTML-entity-encoded -- restored to literal 'a'/'b'/'c'/'d'.
Also fixed the ENUM table header 番号 ("serial number") -> 数値 ("numeric
value"), matching both the English "Number" (the numeric value stored
internally) and the doc's own preceding sentence which already says 数値.
The NULL row of the ENUM value-mapping table (data-type-string.md) rendered the literal SQL keyword NULL as the katakana transliteration ヌル. Since this table exists specifically to show the exact literal values a user would see/ type, matching the EN source's literal "NULL" (not translated/transliterated, unlike the surrounding descriptive prose) keeps it consistent with the already-fixed 'apple'/'orange'/'pear' cells in the same table.
English "Tool"/"Tools" (software tools like Dumpling, TiDB Lightning, BR) was
mistranslated as 道具 (a physical tool/implement, e.g. a hammer) instead of
ツール. Fixed in download-ecosystem-tools.md's table header (the very next
sentence in the same doc already correctly uses ツール, making the
inconsistency obvious) and the "## Prepare tools" heading + body in
migrate-from-op-tidb.md and its premium sibling. Anchor {#prepare-tools} is
English-derived and unchanged. All 5 occurrences of 道具 in the corpus were
this same defect (verified: 0 remaining, no legitimate uses touched).
ti-chi-bot
Bot
added
size/L
English "Component" (a TiDB/TiKV/PD system component) was mistranslated as
成分 (a chemical/mixture ingredient) instead of the standard IT term
コンポーネント. Affects 19 occurrences across 9 files, mostly hardware-
requirements tables listing components (TiDB, TiKV, PD, TiFlash, ...) and
their CPU/memory/network requirements, plus a heading in
tiup/tiup-mirror-reference.md (anchor #component kept, English-derived).
English "Document" was mistranslated as 書類 (physical paperwork) instead of
ドキュメント. Affects 8 occurrences: 6 table headers in ai/_index.md (a list
of doc-page links) and 2 body sentences in
vector-search-integrate-with-django-orm.md describing an API that returns
"documents" in the data-record sense (a Django ORM query result), which is
also not physical paperwork. Also normalized the register of the first of
these two sentences (入手してください -> 入手する) to match its sibling row's
plain descriptive style, since the English for both is the same terse phrase
("Get the 3-nearest neighbor documents." / "Get documents within a certain
distance."), not an explicit polite request.
Both terms are already the dominant, pre-existing convention elsewhere in the
corpus (コンポーネント and ドキュメント are each used 1000+ times), confirming
these were isolated false-friend defects, not a stylistic choice.
yahonda
force-pushed
the
i18n-ja-field-value-header-term
branch
from
August 5, 2026 04:36
2b08ec0 to
9a02145
Compare
The row "Number of copies for each data region" in the cluster limits table had a stray "部" (a leftover machine-translation fragment, not a real word in context) inserted between the glossary link and "あたりのコピー数": "...region) 部あたりのコピー数". Removed it -- "...region)あたりのコピー数" reads naturally as "the number of copies per data region", matching the English.
The deployment topology table in dr-secondary-cluster.md rendered the "Primary"/"Secondary" cluster-role column as 主要な/二次, while the rest of this same document consistently uses プライマリ/セカンダリ (プライマリクラスタ/ セカンダリクラスタ) dozens of times, including in the heading and summary. Unified the table's 9 rows to match the document's own established terms.
…rge)
The AWS EC2 instance type names c5.2xlarge and m5.2xlarge (literal identifiers
a user must type verbatim into the AWS console/CLI) had their "xlarge" suffix
translated to 特大 ("extra-large", the size-adjective sense), producing
c5.2特大/m5.2特大 -- strings that do not match any real AWS instance type.
Restored the literal English suffix. Repo-wide check confirms this was the
only file with this defect (5 occurrences, 0 elsewhere).
The literal MySQL/TiDB username "root" (a fixed account name a user must type
verbatim) had been translated to 根 ("root" in the botanical/mathematical
sense, e.g. tree root or square root) instead of kept as the literal English
identifier. Fixed all 3 occurrences in the upstream/downstream connection
table of dm/migrate-data-using-dm.md. The other 根 occurrences in the corpus
(平方根 "square root" math term, 根ざした "rooted/grounded" idiom) are correct
and untouched.
The API description row for `/get_nearest_neighbors_documents` had been
translated as "get documents about the 3 nearest real-estate properties"
(最近隣の3軒の物件に関するドキュメントを入手する), inventing a real-estate
context not present in the English source ("Get the 3-nearest neighbor
documents."). Fixed to a literal translation matching EN.
小数値 (decimal fraction, e.g. 0.5) is the wrong sense of "Decimal Value" in the SET() base-10-vs-binary value table; fixed to 10進値.
The heading at line 334 used 一次/二次 for "Primary and secondary switchover", inconsistent with the sibling heading for the same English phrase earlier in the same document, which uses プライマリ/セカンダリ. Unified to match.
…are-and-software-requirements
- 保管要件 (safekeeping requirements) -> ストレージ要件 for "Storage requirements",
matching the established convention used in 8+ other files for the same
English heading (anchor unchanged).
- 生産環境 (manufacturing/industrial production) -> 本番環境 for "Production
environment", the established IT term (301 existing occurrences repo-wide
vs 4 outliers being fixed here).
- TiFlash Compute Node left untranslated while the sibling "TiFlash Write
Node" was translated (TiFlash書き込みノード) -> TiFlash計算ノード, matching
the convention used elsewhere (e.g. serverless-high-availability.md,
tiflash-disaggregated-and-s3.md). Also fixed two mid-sentence English
remnants ("Write Node"/"Compute Node") referring back to these terms.
- 以下の注記を参照 -> 以下のノートを参照, so the in-text reference matches the
English "Note:" label of the admonition it points to.
生産環境 -> 本番環境 for "Production environment" heading, matching the established IT term used elsewhere in the same files and repo-wide.
…e Link guides The `<broker_id>`/`<port>` template placeholders in the "Kafka Advertised Listener Pattern" table rows had been translated to <ブローカーID>/<ポート>, breaking their correspondence with the literal `<broker_id>`/`<port>` tokens used in the code-block examples elsewhere in the same documents. Restored to English. Also fixed a missing `<ul>` wrapper around the AZ ID list in the same table (present in the English source's `<ul><li>...</li></ul>`, dropped during translation in 3 files: the alicloud/aws serverless docs and the AWS setup guide), and reconstructed the aws.md "Kafka Advertised Listener Pattern" cell's markup, which had additionally picked up backslash-escaped literals and mismatched closing tags during translation.
ti-chi-bot
Bot
added
the
area/develop
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
1 participant
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)
English table headers "Field" and "Value" were mistranslated as 分野 ("domain"/"field of study") and 価値 ("worth"/"business value") instead of the correct sense for a schema/config table header: 分野 → フィールド (a data field / column name) and 価値 → 値 (a data value). These are false friends: 分野/価値 are valid Japanese words, just the wrong sense of the English homonym.
Scope: 19 changes across 12 files:
information-schema/information-schema-slow-query.md,information-schema/information-schema-cluster-info.md("Field description:" heading)tidb-cloud/essential-database-audit-logging.md(4x),tidb-cloud/premium/tidb-cloud-auditing-premium.md(4x)ticdc/integrate-confluent-using-ticdc.md(both 分野→フィールド and 価値→値 in the same table)data-type-string.md(ENUM value table),functions-and-operators/operators.md("Negates value" ×2)Guardrails (verified): the many GENUINE uses of 分野 ("in the security field", "financial sector", etc.) and 価値 ("business value", "TTL data value", etc.) elsewhere are untouched — their repo-wide counts dropped by exactly 11 and 9 respectively, matching the number of header fixes (18→7 for 分野, 27→18 for 価値).
Which TiDB version(s) do your changes apply to? (Required)
What is the related PR or file link(s)?
N/A
Do your changes match any of the following descriptions?