i18n-ja-release-8.5: translate doc changes from pingcap/docs release-8.5 on 2026-09-17 - #23900
Open
github-actions[bot] wants to merge 91 commits into
Open
github-actions[bot] wants to merge 91 commits into
github-actions[bot] wants to merge 91 commits into
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced 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
contribution
|
Hi @github-actions[bot]. Thanks for your PR. I'm waiting for a pingcap member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
[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
- identify-slow-queries.md: remove the obsolete tidb_slow_log_rules section (superseded by config-slow-query-trigger-rules.md) and fix two stale anchor links, matching the EN source deletion - ai/integrations/vector-search-integrate-with-langchain.md, ai/vector-search-get-started-using-python.md: fix links pointing to ai/concepts/vector-search-overview.md, which this PR renames to ai/guides/vector-search-overview.md - ai/examples/basic-with-pytidb.md: delete to match the EN source deletion (no longer referenced from TOC-ai.md) Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
EN source is identical across all 8 ai/guides/*-with-pytidb.md files
for these bullet-list labels, but the JA sync produced inconsistent
renderings per file. Unify to a single form in each case:
- "Source Code" -> "ソースコード" (translated label), link text ->
"GitHub で見る" (majority form)
- "A {{{ .starter }}} instance" -> "{{{ .starter }}} インスタンス"
(translated, matching existing majority precedent)
- "OpenAI API key" / "Jina AI API key" -> "OpenAI APIキー" /
"Jina AI APIキー", matching the katakana convention used elsewhere
in the repo (e.g. Datadog APIキー, TiDB Cloud APIキー)
- "Text-to-image search" / "Image-to-image search" (capability
description, not literal UI text) -> translated to match the
file's own already-translated summary line
Also add missing trailing newlines to the touched files.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Translate bare "Vector Search" to "ベクトル検索" throughout the body (title, headings, prose, and link text), matching the corpus-wide convention already used elsewhere. Also normalize "TiDB Vector Search" to "TiDBベクトル検索" to match the settled rendering used in 19 other files (e.g. ai-feature-concepts.md, dev-guide-vector-search.md). Left untouched: - The image alt text on line 48, matching the existing literal-alt-text precedent (e.g. "Process Schematic" in dashboard-ops-deploy.md) - The "[Vector data types]" / "[Vector search index]" link texts, which are different terms tied to their own target pages Also add the missing trailing newline. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…ew.md - "[Vector data types]" / "[Vector search index]" -> match the H1 headings of their target pages: "ベクトルデータ型" and "ベクトル検索インデックス" - "[distance function]" -> "距離関数", matching the existing rendering in releases/release-8.4.0.md for a link to the same page - "embedding とも呼ばれます" -> "単に埋め込みとも呼ばれます": the English word was redundant since 埋め込み is already the established JA rendering of "embedding" used throughout this file Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
"API コントラクト" is an unprecedented, unnatural rendering of "API contract" with zero other occurrences in the corpus. Use "API 仕様", matching the established "OpenAPI仕様" convention used throughout the repo for this kind of interface-specification concept. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…i/ti/ The MT sync left the English nouns "mount"/"unmount" untranslated in prose across ~17 files in ai/ti/, while the verb forms in the very same sentences were already correctly rendered as マウント/アンマウント. Convert the noun forms to マウント/アンマウント to match, following the established repo-wide convention (マウントオプション, マウントパス, etc.) Code fences, inline code spans, link URLs, and heading anchors are left untouched, including literal CLI command/flag names such as `mount-file-system` and `--mount-path`. Also, in manage-filesystem-layers.md: - "checkpoint mount" -> "チェックポイントマウント", matching this file's own majority use of チェックポイント in its title and headings - bare "fork" -> "フォーク", matching the well-established rendering used throughout the rest of the corpus (e.g. CONTRIBUTING.md) Also add missing trailing newlines to the touched files. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Same class of defect as the earlier mount/unmount sweep: the MT sync
left the English noun "token"/"tokens" untranslated in prose across
33 files in ai/ti/, while the established convention already used
トークン extensively elsewhere in this same directory (e.g.
manage-filesystem-tokens.md).
Skips: fenced code blocks, inline code spans, link URLs, heading
anchors, and any "token" adjacent to a hyphen (protects literal CLI
command names like `ti fs delete-file-system-token` and compound
terms like `token-management`). One hyphenated non-CLI instance
("owner-token") was manually normalized to match this file's own
"owner token" usage before the sweep would apply.
Also add missing trailing newlines to the touched files.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
"Choose one outcome for a layer" was translated as "choose a result", but 結果 (result/consequence) isn't something you choose beforehand — what follows are two concrete operations (rollback or commit). Use 操作 (operation) instead. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…ion section In manage-filesystem-layers.md's "move local state to another machine" section, translate the terms that already have an established rendering elsewhere in this same corpus: - overlay directory/root -> オーバーレイディレクトリ/オーバーレイルート (matches ti-fs-unpack-file-system.md's own "ローカルオーバーレイルート") - archive path -> アーカイブパス, cache -> キャッシュ, pack (verb) -> パック(します) (all well-established elsewhere in ai/ti/) - restore (verb) -> 復元する (matches ti-fs-create-layer.md's "レイヤーを復元できます") Left as-is: "write-back" (no katakana equivalent exists anywhere in the corpus; it's tied to the literal --write-back-cache flag), and "pack と unpack" in the sentence that immediately precedes links to the literal pack-file-system/unpack-file-system command references (unpack has no katakana precedent anywhere, so translating only "pack" here would read as more inconsistent, not less). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Same class of defect as the mount/token sweeps: the MT sync left the
English noun "owner" untranslated in prose across most of ai/ti/,
while オーナー was already used for the identical concept (owner
token, owner FS token, owner access) in a handful of other files
(e.g. manage-filesystem-vault-secrets.md, ti-fs-vault-mount-vault.md).
Skips: fenced code blocks, inline code spans, link URLs, heading
anchors, and any "owner" adjacent to a hyphen. One hyphenated
instance ("owner-only file") was manually translated to "オーナー専用
ファイル" instead of being left bare.
Also add missing trailing newlines to the touched files.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
"Companion state and mount locators" was translated using a native word (付随, "attached/accompanying"), but "companion" refers to the specific ti-drive9 background runtime component and stays literal English everywhere else in this file and across ai/ti/ (companion runtime, companion home, companion-home). Keep it literal here too for consistency. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
"scoped" and "owner" name the two token kinds in the TiDB Cloud Filesystem token system, and オーナー was already unified for the latter. For the same consistency, translate "scoped" to スコープ付き, matching the existing (if minority) precedent in ti-parallel-agent-dataset-example.md and ti-fs-list-file-system-tokens.md. Skips: fenced code blocks, inline code spans, and any "scoped" adjacent to a hyphen (the literal `generate-file-system-scoped-token` command name stays untouched). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Same class of defect as mount/unset: the verb form is already consistently translated (委任する, 13+ occurrences), and the adjectival "delegated X" form even has existing precedent using the same native rendering (委任された vault トークン, 委任されたフィールド in ti-vault-agent-secrets-example.md), but 8 more prose occurrences were left as bare English. Unify them to 委任された rather than introducing a new katakana loanword. Skips: fenced code blocks and inline code spans (e.g. the "# Read the delegated token ..." bash comments stay untouched). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
"新しい認可済み操作は防止されます" literally reads as "new already-authorized operations are prevented", which is self-contradictory (an already-authorized operation wouldn't need preventing). The EN source means revocation stops new operations from being authorized going forward. Rephrase to match. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
"secret"/"secrets" is translated to シークレット 7 other times in this same file; this one instance was left bare English. Keep "Vault" literal, matching its consistent use elsewhere as part of the "TiDB Cloud Filesystem Vault" feature name. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
"hydration"/"hydrate" stays literal English everywhere else across ai/ti/ (25+ occurrences in 6 files, including mixed constructions like "hydrate する"/"hydrate している"). This one katakana instance in ti-overview.md was an isolated outlier, and "ハイドレーション" risks being read as the skincare/moisture term rather than the Git-object sense intended here. Revert to match the dominant convention. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…ention "dirty" has broad, well-established katakana precedent across the TiDB docs corpus (dirty read/write isolation levels, dirty page cache, dirty data), including within ai/ti/ itself (ti-fs-drain-file-system.md's "ダーティハンドル"). This one instance was left as bare English. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…unt-filesystem.md
- "durability barrier" -> 耐久性バリア, matching
ti-regions-security-and-limitations.md's own description of the
same drain-file-system concept ("FUSE 専用のオンライン耐久性バリア")
- "layer checkpoint" -> レイヤーのチェックポイント, matching the phrasing
in manage-filesystem-layers.md ("レイヤーのチェックポイントを作成する前に")
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…tem.md "device、capability、security、および environment" summarizes the docker run flags shown just above (--device, --cap-add, --security-opt, --env) in plain descriptive prose, not literal code. Translate to デバイス、ケーパビリティ、セキュリティ、および環境変数. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…ai/ti/ Found 8 more prose occurrences of bare "overlay" beyond the one the user flagged in mount-filesystem.md, across ti-filesystem.md, ti-fs-mount-file-system.md, and ti-fs-unmount-file-system.md. Unify all of them to オーバーレイ, matching the dominant convention already established across ai/ti/ (オーバーレイルート, オーバーレイディレクトリ, etc.). Skips CLI flags, code, and literal file paths like "local-overlay.tar.gz". Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…ology Checked the live labs.tidb.io Japanese UI (landing page and in-lab step panel for this exact lab, demo_901): "Lab" is consistently rendered as 演習 throughout (nav "実践演習", exercise cards, sidebars), and no "Lab Guide" label appears anywhere in the actual product UI. Translate accordingly instead of leaving it as literal English. The linked title "TiDB Cloud Filesystem for Agent Sandbox Lab" stays literal, matching the corpus-wide convention for lab/resource link titles elsewhere (e.g. the <ResourceCard title="..."> instances). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…eadings Commit 1e3dda4 translated the "## Entry JSON format" and "## Grant permissions" headings to エントリ JSON 形式 / 付与可能な権限, but missed the same-page cross-reference links pointing at them ([Entry JSON format](#entry-json-format), [Grant permissions](#grant-permissions)), leaving the link text out of sync with its target heading. Anchors are unchanged; only the visible link text now matches the heading it jumps to. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…stem.md This file had accumulated many untranslated terms that already have established renderings elsewhere in ai/ti/: - checkpoint -> チェックポイント (5 sites, matching corpus-wide precedent used throughout this same review) - automatic -> 自動 (matching 自動化/自動 used pervasively; "auto" the literal --driver enum value is left untouched) - manual -> 手動 - layer ID -> レイヤー ID (matching ti-fs-fork-layer.md) - pack archive -> パックされたアーカイブ (matching the exact phrase already used in ti-fs-pack-file-system.md/ti-fs-unpack-file-system.md) - auto-unpack -> 自動 unpack (translates "auto" per the sibling --no-auto-pack description in ti-fs-unmount-file-system.md, which already translates "auto"; "unpack" itself stays literal per the earlier decision in this review to avoid colliding with the established "restore" -> 復元 mapping) - [Global options](#global-options) link text -> [グローバルオプション] (77 other files already translate this exact link; this was the only untranslated holdout) `portable` (a literal mount-profile enum value) is now backtick-quoted to match how its sibling ti-fs-unmount-file-system.md renders the same literal value. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…events.md エージェント has 56 occurrences elsewhere in ai/ti/; only this file's intro sentence and --agent-id description left the prose noun "agent" bare. Literal identifier values like agent-task/deploy-agent/coding- agent are unaffected. Lowercase "vault" (as opposed to the branded "Filesystem Vault") is confirmed to consistently stay literal English throughout the corpus, so it is left untouched here. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Matches "Vault シークレット名" already used identically in ti-fs-vault-read-secret.md, ti-fs-vault-delete-secret.md, and ti-fs-vault-create-secret.md for the same --secret-name option. "Vault" (capitalized, the branded Filesystem Vault feature) stays literal per the same sibling precedent. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…ile's sweep Same defect class as the intro sentence and --agent-id description fixed earlier in this file (commit f8b3b0a). This was the last bare English prose term in ti-fs-vault-list-audit-events.md. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…pdate.md Matches the established シークレット rendering used throughout ai/ti/ (secret manager, secret value, etc.), fixed in many other files earlier in this review. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…cluster Full sweep of this file's remaining bare English, deferred earlier in this review (2026-09-17) because embedding/extraction alone couldn't be fixed cleanly without leaving provider/app-managed/etc. worse off. Now that more established precedent has accumulated corpus-wide during this review, each term is fixed against a specific matching site: - extraction -> 抽出, embedding -> 埋め込み (settled decision, PR #23515) - provider -> プロバイダー (AI プロバイダー, extraction プロバイダー, embedding プロバイダー all established elsewhere) - layer -> レイヤー (matches this same file's own parallel list at line 43 and the ti-drive9 companion sentence) - journal -> ジャーナル, Git workspace -> Git ワークスペース (both massively established; the companion sentence had left them bare) - interface -> インターフェース, contract -> コントラクト (matching the near-identical twin sentence in ti-fs-update-file-system-extract-configuration.md, which covers the exact same OpenAI-compatibility topic) - image/audio/video -> 画像/音声/動画 (matching configure-filesystem-ai-providers.md's identical sentence) - app-managed -> アプリケーション管理, database-managed -> データベース管理 (matching configure-filesystem-ai-providers.md and this same file's own line 90, which already used データベース管理) - telemetry -> テレメトリー, serverless-function -> サーバーレス関数 (サーバーレス already established for the product's own "serverless distributed file system" description) "vault" (lowercase, generic sense) and "file system ID" (the compound identifier field, distinct from generic "file system") are confirmed to consistently stay literal English throughout the corpus and are left untouched, per the same reasoning already applied elsewhere in this review. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…nd-limitations.md "API key" -> API キー: corpus-wide the translated form is dominant (24 sites) vs bare English (9, and every one of those 9 outside this file is a literal bash comment or printf string, not real prose). This file's credential-requirements table and security-practices bullet were the only remaining real-prose holdouts, all fixed together for internal table consistency. "locator" -> ロケーター (established via "マウントロケーター", used in this file's own sibling file ti-configuration-and-credentials.md and mount-filesystem.md). "non-secret" -> 機密情報を含まない, matching the identical EN phrase "a non-secret locator" already rendered as "機密情報を含まないロケーター" in ti-configuration-and-credentials.md. "drain" is left as literal English, matching its consistent treatment everywhere else in ai/ti/ (mount-filesystem.md, ti-fs-drain-file-system.md, etc.). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Matches the overwhelming パック precedent used throughout ai/ti/ (this same file's own "pack" fix earlier in the review, plus dozens of sites in ti-fs-pack-file-system.md and elsewhere). "file" stays literal and "vault" (generic, lowercase) stays literal, matching this row's own established treatment confirmed earlier in this review; read/list/run are literal operation-name identifiers. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Matches the established rendering used elsewhere in ai/ti/ (ti-db-create-db-sql-users.md's "生成されたユーザー名とパスワード", ti-configuration-and-credentials.md's "DB SQL のユーザー名、パスワード"). Digest/Basic/TLS stay literal, matching standard protocol-name treatment throughout the corpus. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
"コマンド契約" was technically defensible ("design by contract" is a
real software-engineering sense of 契約), but the user felt it read
awkwardly for a general reader. コマンドの仕様 ("command
specification") more plainly conveys "the CLI's command behavior can
change during preview" without leaning on the legal/contract sense.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Full sweep of this file's remaining bare English, prompted by several
lines the user pasted in review:
- sandbox -> サンドボックス, shell -> シェル, profile -> プロファイル
(63 occ elsewhere), import -> インポート, role -> ロール (33 occ
elsewhere), path -> パス, endpoint -> エンドポイント (established
within ai/ti/ itself, e.g. configure-filesystem-ai-providers.md)
- commit -> コミット, matching manage-filesystem-layers.md's
established rendering for the same generic "finalize an operation"
sense (distinct from the literal Git "commit" kept English in
ti-git-workspace-for-agents-example.md, which this isn't)
- "Mount does not become ready" heading -> "マウントが準備完了に
ならない", matching 準備完了 used for the same "become ready"
concept in ti-overview.md/ti-quick-start.md
- "Unmount reports busy" heading -> "アンマウント時にビジーが
報告されます" (no established precedent either way; ビジー is a
standard, widely understood Japanese IT loanword)
- standalone -> スタンドアロン (no established precedent; a standard
loanword, translated for consistency with the rest of this sweep)
Anchors ({#mount-does-not-become-ready}, {#unmount-reports-busy})
preserved; only visible text changed.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
quota -> クォータ (established: ti-fs-describe-file-system.md, ti-fs-list-file-systems.md), fixed in this file's summary, heading, and body (3 sites). capacity -> 容量 (matches ti-daily-workflow-example.md's prose rendering; the bash-comment "cache capacity" instance elsewhere correctly stays literal). billing -> 課金 (matches configure-filesystem-ai-providers.md). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
mode -> モード (established earlier this review for POSIX file mode). locator -> ロケーター (established via マウントロケーター in ti-configuration-and-credentials.md, mount-filesystem.md, and fixed elsewhere in this file's own credential-requirements table earlier this review). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
… a stale link text - "TiDB Cloud console" -> "TiDB Cloud コンソール" (ti-quick-start.md), matching コンソール already used in ti-overview.md and this same file's own sibling ti-install-configure-update.md. - "public key"/"private key" -> "public キー"/"private キー" (5 sites across both files), matching the API-key キー rendering established earlier this review in ti-regions-security-and-limitations.md. - "[Supported regions]" link text -> "[サポートされるリージョン]" (ti-quick-start.md), matching its target heading in ti-regions-security-and-limitations.md -- same class of stale link-text defect fixed earlier this review (commit f40f051) for Entry JSON format / Grant permissions. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Three links pointed at pages whose titles are already translated but the link text itself was left as literal EN: - "TiDB Cloud Command Line Interface Overview" -> "TiDB Cloud CLI (`ti`) の概要", matching ti-overview.md's actual title (EN's own link text is a paraphrase, not identical to the target's own H1; translating it to match the target's real heading is more useful to the reader than a literal translation of the paraphrase) - "Filesystem resources" -> "Filesystem リソース", matching the partial-phrase rendering already used in ti-filesystem.md - "TiDB Cloud CLI Command Reference" -> "TiDB Cloud CLI (`ti`) コマンドリファレンス", matching ti-cli-reference.md's title exactly Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…ecision PR #23856 (2026-09-14) unified "(TiDB) Vector Search" to katakana ベクトル検索/TiDBベクトル検索 corpus-wide (308+ existing sites), a deliberate exception to 1:1 EN-fidelity for readability. This exact file already correctly uses ベクトル検索 at lines 199-201 (reference-section links) but had 5 untranslated "Vector Search" sites in the quickstart/guides sections above -- a same-file self-contradiction. User caught this after I incorrectly told them it was intentional; re-checked memory of the settled decision and confirmed the fix. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
The target page's own title (config-slow-query-trigger-rules.md) is
"スロークエリのトリガールールを設定する", and スロークエリ is the
overwhelmingly dominant corpus-wide rendering of "slow query" (401
sites/101 files vs 3). In TOC.md this entry sits directly between two
sibling entries that both correctly say スロークエリ
("スロークエリを特定する"/"スロークエリを分析する"), making the lone
低速クエリ an obvious same-list inconsistency. A third occurrence in
releases/release-7.3.0.md is unrelated pre-existing content, not part
of this PR's diff, and is left untouched.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…glers in ai/ti/ Final sanity sweep found 6 leftover bare-English verbs, each already translated consistently elsewhere in the same corpus: - pack -> パック (manage-filesystem-layers.md summary, ti-regions-security-and-limitations.md), matching ti-fs-mount-file-system.md's established form - restore -> 復元 (manage-filesystem-layers.md summary), matching the same file's own body text - export -> エクスポート (ti-fs-vault-mount-vault.md), matching the near-identical sentence in configure-filesystem-ai-providers.md - refresh -> 更新 (ti-fs-refresh-file-system-token.md x3, ti-troubleshooting.md), matching every sibling command-reference page's own central-verb translation pattern and manage-filesystem-tokens.md's summary - revoke -> 失効 (ti-troubleshooting.md x2, ti-fs-generate-file-system-scoped-token.md), matching the byte-for-byte identical sentence already correctly translated in the sibling ti-fs-generate-file-system-token.md Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
… CLI docs
Same defect class as the ai/ti/ link-text-vs-heading fixes earlier
this review, now found in the wider tidb-cloud/ docs that also
reference the new ai/ti/ pages:
- "[TiDB Cloud CLI (`ti`) Quick Start]" -> "[TiDB Cloud CLI を使い始める]",
matching ti-quick-start.md's actual title (cli-reference.md,
get-started-with-cli.md, tidb-cloud-release-notes.md)
- "[Differences between `ti` and `ticloud`]" / "[TiDB Cloud CLI (`ti`)
Overview]" -> matching ti-overview.md's actual heading/title
(get-started-with-cli.md, tidb-cloud-release-notes.md)
- cli-reference.md: stray untranslated "The " left stranded before a
backtick term in 2 sentences ("The `ticloud` CLIは..." x2)
- cli-reference.md: dropped clause -- EN "imports and exports data"
was only translated as "データをインポートしたり" (import only),
missing "and exports" entirely
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Member
|
It would take some more time to review this pull request. Will be done tomorrow. |
5 formulas had their LaTeX subscript syntax corrupted from _{...} to
*{...} (e.g. \limits _{i=1} became \limits *{i=1}), breaking
KaTeX/LaTeX rendering entirely. Restored the exact EN source LaTeX.
Also unified "DISTANCE" -> 距離 in the one formula that had been left
as literal "DISTANCE" while the other 4 sibling formulas in this same
file already use 距離 (self-contradiction); NORM/INNER_PROD are left
as literal function-name symbols matching EN, same as before.
Also fixed a `<>` comparison operator that had been corrupted into
literal HTML entities (`<>`) inside a code span, which will not
decode inside markdown code spans and would render as literal text.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
… translation
The site's Hugo/build template placeholder {{{ .starter }}} (renders
as the product's tier-specific name, e.g. TiDB Cloud Starter, TiDB
Cloud Essential, etc. depending on the docs variant) was replaced
with the literal hardcoded text "TiDB Cloud Starter" in ~35 prose
sites across 16 files during translation. This breaks the templating
for any docs build/variant where the placeholder should resolve to a
different tier name. Restored the exact template token to match each
site's EN source.
Also fixed the accompanying dropped-particle-after-link defect in the
7 identical auto-embedding Note lines (missing は), and restored
langchain.md's [{{{ .starter }}}] link to use the correct upstream
docs.pingcap.com URL (it had been altered to a different, wrong
relative link).
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…or-search docs
- ai/quickstart-via-python.md: table/field names were swapped
("text_vec table's chunks field" instead of "chunks table's
text_vec field"), factually wrong in a hands-on tutorial
- vector-search-integrate-with-langchain.md: "### Use as a retriever"
heading mistranslated as "回収犬" (a retriever DOG breed), a false
friend for the LangChain Retriever interface; the very next
sentence in the same section correctly keeps "Retriever" as-is
- ai/guides/vector-search.md: dropped "you need to" clause and left a
stray un-converted English period ending the sentence
- ai/guides/vector-search.md: unified post-filtering/pre-filtering to
match the established corpus-wide rendering (ポストフィルタリング /
事前フィルタリング, used consistently in the sibling
full-text-search guides) -- this file alone had 3 different
renderings of "post-filtering" (後フィルタリング/ポストフィルタリング/
後続フィルタリング) and 2 of "pre-filtering"
(プレフィルタリング/事前フィルタリング)
- ai/guides/vector-search.md: "vector field(s)" mistranslated as
physics-style "ベクトル場" in one heading/example title while the
rest of the file (and the concept itself, a database column)
consistently uses ベクトルフィールド
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
The entire trailing ## Related resources section (with its <RelatedResources>/<ResourceCard> blog-link component) was missing from the JA translation. Restored it, translating only the heading (matching the established 関連リソース rendering used for this same component elsewhere, e.g. overview.md) -- the ResourceCard's own title/author/date attributes are data values describing a specific English-language blog post and stay literal, matching how the same component is handled in every other file that uses it. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…and/or/with - auto-embedding-with-pytidb.md: H1 and its own cross-reference link left "Auto Embedding" bare, while ~20 other files across the corpus consistently link to the same target as [自動埋め込み], and the sibling ai/guides/auto-embedding.md's own H1 already uses 自動埋め込み. Fixed the H1 and the in-body link text to match (title: frontmatter intentionally left untranslated, matching this same pattern in the sibling files). - ai/_index.md: "[表の操作]" link text corrected from "テーブルの操作" to match tables.md's actual H1 (表の操作); 3 bare English and/or/or connectors between JA links translated to および/または. - vector-search-auto-embedding-jina-ai.md: bare English "with" left stranded between two Japanese-context links. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…earch docs
- 4 auto-embedding integration files (cohere/huggingface/openai/gemini)
had their intro sentence split into two disconnected noun-phrase
clauses stuck together with a bare comma (missing the connecting
"て" verb form), producing a run-on non-sentence. Rewrote to match
amazon-titan.md's clean rendering of the byte-for-byte identical EN
sentence.
- vector-search-integrate-with-amazon-bedrock.md: a bullet list item
was missing its verb/particle entirely ("[required permissions]AWS
account and access to..."), not parseable as Japanese; restored
based on EN ("An AWS account with the [required permissions] and
access to the following models:").
- vector-search-full-text-search-sql.md: removed a stray duplicated
"テキストデータ" fragment sitting immediately before a link that
already contains the same text.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…earch docs Recurring MT-artifact defect class (dropped particle immediately after a closing markdown link or backtick), found at 10 sites across 7 files: - vector-search-limitations.md: 4 sites (missing は x3, restructured a reversed subject/verb clause for "each vector supports up to 16383 dimensions") - vector-search-data-types.md: missing を before 構築できない - vector-search-improve-performance.md: 2 sites (missing は, missing を) - image-search.md: missing で after `VectorField()` - quickstart-via-python.md: missing を before 扱う場合 - vector-search-full-text-search-sql.md: missing を before ご覧ください Also fixed a bare English "or" left between [Discord]/[Slack] links in 3 files (vector-search-limitations.md and both full-text-search guides, identical boilerplate sentence) -> または. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…ter drift
- vector-search-full-text-search-python.md and vector-search-hybrid-search.md:
a heading used a raw <a href="...">pytidb</a> HTML tag instead of markdown
link syntax, corrupting the auto-generated anchor slug into
"step-1-install-the-a-href-https-github-com-pingcap-pytidb-pytidb-a-python-sdk".
Converted to markdown link syntax and repaired the anchor to the
EN-derived slug; no inbound links referenced the broken anchor.
- vector-search-data-types.md: italic markers trapped the か/が particles
("*大きいかが*決まります" instead of "*大きい*かが決まります").
- vector-search-index.md: link text "[EXPLAIN コマンド]" didn't match its
target's actual title (explain-walkthrough.md's own H1 is
"`EXPLAIN`ウォークスルー"); EN link text is "EXPLAIN Walkthrough", not
a command reference.
- quickstart-via-sql.md: 2 sites with a plain-form (だ/である) sentence
ending stranded among otherwise polite (です/ます) sentences.
- vector-search-integrate-with-amazon-bedrock.md: a prerequisites bullet
was missing its が particle and used a different tense than its 2
sibling bullets in the same list.
- vector-search-integrate-with-django-orm.md: 2 of 3 rows in one small
table used plain form while the third used polite form.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Correction to d3e69e4: fixed the 3 bullets to be internally consistent (がインストールされました) but that form describes a past event, which reads oddly for a prerequisites checklist stating a required state. 6 sibling files with the identical "以下が必要です" intro (vector-search-get-started-using-python.md, vector-search-integrate-with-{llamaindex,peewee,langchain, jinaai-embedding,sqlalchemy,django-orm}.md) all consistently use the nominalized state form "がインストールされていること。" for this exact kind of bullet. Matched that established convention. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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)
Translate documentation changes from
pingcap/docsrelease-8.5to Japanese viaai-markdown-translatorcommit-diff sync.English commit diff:
bb4a157...6acba5d
Which TiDB version(s) do your changes apply to? (Required)
What is the related PR or file link(s)?
pingcap/docsrelease-8.5TOC.md,TOC-ai.md,TOC-api.md,TOC-best-practices.md,TOC-develop.md,TOC-tidb-releases.md,TOC-tidb-cloud.md,TOC-tidb-cloud-starter.md,TOC-tidb-cloud-essential.md,TOC-tidb-cloud-premium.md,TOC-tidb-cloud-releases.mdTOC-ai.md,TOC-tidb-cloud-essential.md,TOC-tidb-cloud-premium.md,TOC-tidb-cloud-starter.md,TOC.md,ai/_index.md,ai/guides/auto-embedding-with-pytidb.md,ai/guides/auto-embedding.md,ai/guides/fulltext-search-with-pytidb.md,ai/guides/hybrid-search-with-pytidb.md,ai/guides/image-search-with-pytidb.md,ai/guides/image-search.md,ai/guides/memory-with-pytidb.md,ai/guides/rag-with-pytidb.md,ai/guides/tables.md,ai/guides/text2sql-with-pytidb.md,ai/guides/vector-search-full-text-search-python.md,ai/guides/vector-search-full-text-search-sql.md,ai/guides/vector-search-overview.md,ai/guides/vector-search-with-pytidb.md,ai/guides/vector-search.md,ai/integrations/vector-search-auto-embedding-amazon-titan.md,ai/integrations/vector-search-auto-embedding-cohere.md,ai/integrations/vector-search-auto-embedding-gemini.md,ai/integrations/vector-search-auto-embedding-huggingface.md,ai/integrations/vector-search-auto-embedding-jina-ai.md,ai/integrations/vector-search-auto-embedding-nvidia-nim.md,ai/integrations/vector-search-auto-embedding-openai.md,ai/integrations/vector-search-integrate-with-amazon-bedrock.md,ai/integrations/vector-search-integrate-with-django-orm.md,ai/integrations/vector-search-integrate-with-jinaai-embedding.md,ai/integrations/vector-search-integrate-with-llamaindex.md,ai/integrations/vector-search-integrate-with-peewee.md,ai/integrations/vector-search-integrate-with-sqlalchemy.md,ai/integrations/vector-search-integration-overview.md,ai/quickstart-via-python.md,ai/quickstart-via-sql.md,ai/reference/vector-search-data-types.md,ai/reference/vector-search-functions-and-operators.md,ai/reference/vector-search-improve-performance.md,ai/reference/vector-search-index.md,ai/reference/vector-search-limitations.md,ai/ti/guides/configure-filesystem-ai-providers.md,ai/ti/guides/manage-filesystem-layers.md,ai/ti/guides/manage-filesystem-resources.md,ai/ti/guides/manage-filesystem-tokens.md,ai/ti/guides/manage-filesystem-vault-secrets.md,ai/ti/guides/manage-git-workspaces.md,ai/ti/guides/manage-starter-instances.md,ai/ti/guides/mount-filesystem.md,ai/ti/guides/ti-agent-sandbox-example.md,ai/ti/guides/ti-ci-artifact-handoff-example.md,ai/ti/guides/ti-daily-workflow-example.md,ai/ti/guides/ti-git-workspace-for-agents-example.md,ai/ti/guides/ti-journal-agent-workflow-example.md,ai/ti/guides/ti-parallel-agent-dataset-example.md,ai/ti/guides/ti-persistent-agent-state-example.md,ai/ti/guides/ti-query-sql-with-roles-example.md,ai/ti/guides/ti-share-filesystem-across-machines-example.md,ai/ti/guides/ti-vault-agent-secrets-example.md,ai/ti/guides/use-filesystem-journals.md,ai/ti/guides/work-with-filesystem-data.md,ai/ti/reference/ti-cli-reference.md,ai/ti/reference/ti-configuration-and-credentials.md,ai/ti/reference/ti-configure.md,ai/ti/reference/ti-db-create-db-cluster-branch.md,ai/ti/reference/ti-db-create-db-cluster.md,ai/ti/reference/ti-db-create-db-sql-users.md,ai/ti/reference/ti-db-delete-db-cluster-branch.md,ai/ti/reference/ti-db-delete-db-cluster.md,ai/ti/reference/ti-db-describe-db-cluster-branch.md,ai/ti/reference/ti-db-describe-db-cluster.md,ai/ti/reference/ti-db-execute-sql-statement.md,ai/ti/reference/ti-db-format-db-connection-string.md,ai/ti/reference/ti-db-list-db-cluster-branches.md,ai/ti/reference/ti-db-list-db-clusters.md,ai/ti/reference/ti-db-update-db-cluster.md,ai/ti/reference/ti-filesystem-git.md,ai/ti/reference/ti-filesystem-journal.md,ai/ti/reference/ti-filesystem-vault.md,ai/ti/reference/ti-filesystem.md,ai/ti/reference/ti-fs-check-file-system.md,ai/ti/reference/ti-fs-chmod-file.md,ai/ti/reference/ti-fs-commit-layer.md,ai/ti/reference/ti-fs-copy-file.md,ai/ti/reference/ti-fs-create-directory.md,ai/ti/reference/ti-fs-create-file-system.md,ai/ti/reference/ti-fs-create-hardlink.md,ai/ti/reference/ti-fs-create-layer-checkpoint.md,ai/ti/reference/ti-fs-create-layer.md,ai/ti/reference/ti-fs-create-symlink.md,ai/ti/reference/ti-fs-delete-file-system-token.md,ai/ti/reference/ti-fs-delete-file-system.md,ai/ti/reference/ti-fs-delete-file.md,ai/ti/reference/ti-fs-delete-layer.md,ai/ti/reference/ti-fs-describe-file-system-embedding-configuration.md,ai/ti/reference/ti-fs-describe-file-system-extract-configuration.md,ai/ti/reference/ti-fs-describe-file-system.md,ai/ti/reference/ti-fs-describe-file.md,ai/ti/reference/ti-fs-describe-layer.md,ai/ti/reference/ti-fs-diff-layer.md,ai/ti/reference/ti-fs-disable-file-system-token.md,ai/ti/reference/ti-fs-drain-file-system.md,ai/ti/reference/ti-fs-enable-file-system-token.md,ai/ti/reference/ti-fs-find-files.md,ai/ti/reference/ti-fs-fork-layer.md,ai/ti/reference/ti-fs-generate-file-system-scoped-token.md,ai/ti/reference/ti-fs-generate-file-system-token.md,ai/ti/reference/ti-fs-git-add-git-worktree.md,ai/ti/reference/ti-fs-git-clone-git-workspace.md,ai/ti/reference/ti-fs-git-hydrate-git-workspace.md,ai/ti/reference/ti-fs-git-remove-git-worktree.md,ai/ti/reference/ti-fs-import-file-system-token.md,ai/ti/reference/ti-fs-journal-append-journal-entries.md,ai/ti/reference/ti-fs-journal-create-journal.md,ai/ti/reference/ti-fs-journal-read-journal-entries.md,ai/ti/reference/ti-fs-journal-search-journal-entries.md,ai/ti/reference/ti-fs-journal-verify-journal.md,ai/ti/reference/ti-fs-list-file-system-tokens.md,ai/ti/reference/ti-fs-list-file-systems.md,ai/ti/reference/ti-fs-list-files.md,ai/ti/reference/ti-fs-list-layer-chain.md,ai/ti/reference/ti-fs-list-layers.md,ai/ti/reference/ti-fs-mount-file-system.md,ai/ti/reference/ti-fs-move-file.md,ai/ti/reference/ti-fs-pack-file-system.md,ai/ti/reference/ti-fs-read-file.md,ai/ti/reference/ti-fs-refresh-file-system-token.md,ai/ti/reference/ti-fs-rollback-layer.md,ai/ti/reference/ti-fs-search-file-content.md,ai/ti/reference/ti-fs-unmount-file-system.md,ai/ti/reference/ti-fs-unpack-file-system.md,ai/ti/reference/ti-fs-update-file-system-embedding-configuration.md,ai/ti/reference/ti-fs-update-file-system-extract-configuration.md,ai/ti/reference/ti-fs-vault-create-grant.md,ai/ti/reference/ti-fs-vault-create-secret.md,ai/ti/reference/ti-fs-vault-delete-grant.md,ai/ti/reference/ti-fs-vault-delete-secret.md,ai/ti/reference/ti-fs-vault-list-audit-events.md,ai/ti/reference/ti-fs-vault-list-secrets.md,ai/ti/reference/ti-fs-vault-mount-vault.md,ai/ti/reference/ti-fs-vault-read-secret.md,ai/ti/reference/ti-fs-vault-replace-secret.md,ai/ti/reference/ti-fs-vault-run-with-secret.md,ai/ti/reference/ti-fs-vault-unmount-vault.md,ai/ti/reference/ti-install-configure-update.md,ai/ti/reference/ti-migrate-from-tdc.md,ai/ti/reference/ti-regions-security-and-limitations.md,ai/ti/reference/ti-starter-database.md,ai/ti/reference/ti-troubleshooting.md,ai/ti/reference/ti-update.md,ai/ti/ti-overview.md,ai/ti/ti-quick-start.md,basic-features.md,config-slow-query-trigger-rules.md,develop/dev-guide-vector-search.md,functions-and-operators/json-functions/json-functions-return.md,glossary.md,identify-slow-queries.md,performance-tuning-methods.md,releases/release-2.0.6.md,releases/release-4.0.16.md,releases/release-5.0.6.md,releases/release-5.1.4.md,releases/release-6.1.0.md,releases/release-6.1.3.md,releases/release-8.4.0.md,releases/release-8.5.6.md,releases/release-8.5.8.md,sql-statements/sql-statement-grant-privileges.md,system-variables.md,tidb-cloud/ai-feature-concepts.md,tidb-cloud/cli-reference.md,tidb-cloud/connected-ai-chat-in-im.md,tidb-cloud/get-started-with-cli.md,tidb-cloud/releases/release-notes-2024.md,tidb-cloud/releases/tidb-cloud-release-notes.md,tidb-cloud/select-cluster-tier.md,tidb-cloud/tidb-cloud-billing.md,tidb-cloud/tidb-cloud-glossary.md,tidb-cloud/tidb-cloud-intro.md,tidb-cloud/tidb-cloud-org-sso-authentication.md,tidb-cloud/tune-performance.md,tiflash-upgrade-guide.mdincrementalsuccessPartial or incomplete translations
The following files contain useful generated output, but still require review or retry.
ai/ti/guides/ti-share-filesystem-across-machines-example.md: Markdown table 1 remains suspicious after repair: 1 natural-language body row(s) are unchanged from the sourceai/ti/reference/ti-filesystem.md: Markdown table 1 repair rejected: repair changed protected numbers; Markdown table 1 remains suspicious after repair: table header is unchanged from the sourceai/ti/reference/ti-fs-journal-append-journal-entries.md: Markdown table 1 remains suspicious after repair: 1 natural-language body row(s) are unchanged from the sourceai/ti/reference/ti-regions-security-and-limitations.md: Markdown table 1 remains suspicious after repair: 1 natural-language body row(s) are unchanged from the source; Markdown table 2 remains suspicious after repair: 2 natural-language body row(s) are unchanged from the sourceDo your changes match any of the following descriptions?