i18n(ja): standardize the translation of the multi-valued index term#23263
Conversation
|
Skipping CI for Draft Pull Request. |
ti-chi-bot
Bot
added
the
do-not-merge/work-in-progress
|
[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
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request standardizes the Japanese translation of "multi-valued index" to "多値インデックス" across multiple documentation and release note files. The review feedback highlights several minor issues, including a broken template tag, missing grammatical particles, and a lack of punctuation separators in a list of functions, all of which have been addressed with clear, actionable suggestions.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
Unify the Japanese translation of "multi-valued index", which was inconsistently rendered as 複数値インデックス, 多値インデックス, マルチ値インデックス, 複数値のインデックス, and 多値指標. Standardize on 多値インデックス. This keeps the whole "multi-valued" family consistent, since the related terms 多値列 (multi-valued column) and 多値部分 (multi-valued part) already use 多値, and it stays clearly distinct from 複合インデックス (composite index). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
yahonda
force-pushed
the
fix-ja-multivalued-index
branch
from
4fc290d to
c462691
Compare
yahonda
changed the title
qiancai
added
translation/no-need
Apply gemini-code-assist review suggestions on lines touched by the term standardization: - choose-index.md: remove a stray `E}}` template artifact and normalize punctuation spacing in the json_member_of / json_contains / json_overlaps list - choose-index.md: add the missing を particle before 使用すると in the use_index_merge clause - releases/release-7.1.0.md: separate the MEMBER OF() / JSON_CONTAINS() / JSON_OVERLAPS() function list with 、 and または - sql-statements/sql-statement-create-index.md: add a comma after 詳細については and the missing を before 参照してください Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
ti-chi-bot
Bot
removed
the
do-not-merge/work-in-progress
[LGTM Timeline notifier]Timeline:
|
2 participants
What is changed, added or deleted? (Required)
This PR standardizes the Japanese translation of "multi-valued index" (MV index) across the Japanese documentation so that a single term is used consistently.
The term was previously translated in several inconsistent ways, including
複数値インデックス,多値インデックス,マルチ値インデックス,マルチバリューインデックス,複数値のインデックス, and多値指標. All of these are now unified to多値インデックス(69 lines updated across 14 files).Rationale for choosing
多値インデックス:多値列(multi-valued column) and多値部分(multi-valued part of a composite index) already use the多値prefix, so standardizing the index term on多値インデックスkeeps the whole "multi-valued" family consistent.複合インデックス(composite index), which even co-occurs with it in the same sentence insql-statement-create-index.md.Notes:
{#multi-valued-indexes}) and internal links are unchanged; only the displayed Japanese text was updated.複数値式(multi-valued expression) and複数値条件(multi-valued condition).Which TiDB version(s) do your changes apply to? (Required)
This PR targets the
i18n-ja-release-8.5Japanese translation branch, not the English v8.5 docs, so no version box is checked.What is the related PR or file link(s)?
Do your changes match any of the following descriptions?