Repository navigation
i18n(ja): fix TiDB Cloud Lake docs, part 1 of 4 (guides, tutorials, and TOC) - #24440
Merged
qiancai merged 49 commits intoOct 14, 2026
Merged
Conversation
Use one term for aggregate functions, the aggregating index, and SQL aggregation in general, which matches other databases' Japanese docs and the rest of the TiDB Japanese docs. Keep the other term where the text means combining values into one array, JSON value, or geometry, and where the English is not "aggregate". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…iDB Cloud Lake docs Translate the "Step N", "Tutorial N", and "Example-N" labels left in English in headings, using the forms that the rest of the Japanese docs use, and unify the one file that used a different word for "Step". Fully translate the few example headings left in English. Translate the "Scenario:" label in the CityDrive guides. Heading anchors are unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…TiDB Cloud Lake docs Translate the titles of the function category pages and the integration task pages that were left in English, matching their sibling pages that are already translated. Update the link texts that repeat these titles. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Translate the titles of feature overview pages whose Japanese term is already used in the page body or in sibling pages (indexes, masking policy, stored procedure, stream, tag, table, external function, EXPLAIN commands, and Information_Schema tables). Keep engine and table-format names, Full-Text Index, and Stage in English. Update the TOC labels and link texts that repeat these titles. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- _index.md: move the "Corresponding EN commit" comment below the front matter. With the comment on line 1, the front matter was not parsed and the page rendered it as body text with an empty title. - Delete guides/ai-powered-features.md and guides/manage-costs.md, and drop the billing role section from guides/roles.md, to match the English docs (pingcap#24422). The translation sync does not carry over file deletions. - Remove links and bold markup that were added to front matter summaries. Summaries are plain text. - Restore the list markers in three notes, so that each item renders as a separate bullet, and move a sentence back to its original item. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… docs The custom anchors in the Japanese headings collapsed double hyphens and changed underscores to hyphens (for example, create-table-like instead of create-table--like, and record-delimiter instead of record_delimiter). Links copied from the English docs use the English slugs, so 38 links in the Japanese Lake docs did not resolve. Set each custom anchor to the slug that the English heading produces, including the -1 suffix for repeated headings. All in-page and cross-page anchor links in the Lake docs now resolve. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Fix sentences whose Japanese meaning differs from the English, each checked against the English source. Examples: - NULL handling in GET, GET_PATH, GET_IGNORE_CASE, JSON_EXTRACT_PATH_TEXT, SHA, XXHASH32, and XXHASH64: the value is returned as the type, and NULL is returned only for NULL input. - "exclusive" bounds were rendered as "mutually exclusive". - The "occurrence" argument of REGEXP_INSTR and REGEXP_SUBSTR is an ordinal, not a count. - "Sets or unsets a setting" was rendered as enable or disable. - "surface area", "candidate", the "View" permission, the "Spec." (specifier) column, "data warehouse", and "extra load" were rendered with the wrong sense. - A network policy limits the source IP ranges of connections, not the destination. - Restore Apache Iceberg and geometry type names that must stay literal. - Fix broken Japanese, stray spaces, and a doubled "see" phrase. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…d Lake docs Translate headings, table header cells, bold prose labels, and page titles that were left in English, and update the link texts that repeat them. Heading anchors are unchanged. Keep in English: identifiers (system.* and information_schema.* tables, option names, data type names), object and feature names (Stage, Warehouse, Worksheets, Fail-Safe, Schema Evolution, and so on), UI field names, data source names, and the admonition labels that the site renders. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Translate ordinary English words and phrases left in the prose of the Lake guides and tutorials, such as integration task, primary key, snapshot, security group, sandbox, role, policy, dataset, and link texts that repeat translated page titles. Translate the Yes/No values in the "Required" columns. Remove the stray space in the Japanese term for row access policy. Keep identifiers, UI labels, feature names, and terms that the translation glossary keeps in English. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Skipping CI for Draft Pull Request. |
|
[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 |
📝 Walkthrough
Merge Risk: 🔵 Low · up to
|
| Check name | Status | Explanation |
|---|---|---|
| Title check |  |
The title clearly identifies a Japanese internationalization fix for the TiDB Cloud Lake documentation and specifies the covered guides, tutorials, and table of contents. |
| Description check | |
The description is complete and explains the scope, themes, affected version, related pull requests, AI involvement, and file deletions. It provides sufficient context for review. |
| Docstring Coverage | |
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0… |
| Linked Issues check | |
Check skipped because no linked issues were found for this pull request. |
| Out of Scope Changes check | |
Check skipped because no linked issues were found for this pull request. |
✨ Finishing Touches: 💡 1
-
🛠️ Fix failing CI checks: 💡
-
- Commit to this branch
- Create a new PR
🧪 Generate unit tests (beta)
-
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
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 @coderabbitai help to get the list of available commands.
This was referenced Oct 13, 2026
…guides Translate the prose "prefix" and "suffix" left in English in the SQS (S3) guides, matching the S3 object key prefix and suffix filter wording that the same guide already uses. Field names in code spans stay in English. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
"Raw access keys" means the long-lived access keys themselves, as opposed to the short-lived credentials that the IAM role provides. Reword the Japanese to say that Lake does not handle the access keys directly, which reads more naturally. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…e guides Use the term that the AWS Japanese docs and the rest of the TiDB Japanese docs use for "external ID" in prose. The External ID field label and parameter names stay in English. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Translate "scalar UDF", "aggregate UDF", "table UDF", and "scalar logic" where the English uses them as lowercase common nouns, matching the parts of the guide that are already translated. The capitalized UDF type labels in the tables and the heading anchors stay unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…L guide Here "export" means setting an environment variable with the shell export command. Use the wording that the rest of the Japanese docs use for setting environment variables. The export command in the code sample is unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…verview The header "I want to... | Recommended" was translated too literally. Name the columns by their content: the goal and the recommended connection method. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…Streams guides These lowercase words describe change types and the join operation in prose, not SQL keywords, so translate them as the rest of the Japanese docs do. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Most TiDB Cloud Lake docs translate the generic noun "task" as a Japanese term. Align the remaining prose sites. UI labels, feature names, headings, and code are unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The SQL reference pages for streams, such as CREATE STREAM and SHOW STREAMS, already use the Japanese term. Align the prose in the guides with them. Feature names, capitalized headings, link text, and code are unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…olicies guide The "Role" column header means a database role, as in the earlier table on the same page. "Permission denied (no SELECT)" and "Rules of thumb" were translated too literally. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The literal translation reads unnaturally as a heading. Use a common Japanese heading for a hands-on walkthrough. The anchor is unchanged, so existing links still work. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ll-text index guides Most TiDB Cloud Lake docs, including the inverted index SQL reference page, translate "inverted index" as a Japanese term. "refresh" in prose is a generic noun, translated as in the refresh SQL reference pages. SQL statements are unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…e optimizer guide Drop the extra word for "table" in the remaining join terms, which came from the glossary entry for "Joins". Also translate "executor", "build/probe", "memo-driven", the join implementation names, "broadcast", "shuffle", and "projection" as natural Japanese, matching earlier fixes on the same page. The "exchange" operator name is unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…uide The rewrite changes how the exchange operator distributes data, from broadcast to hash shuffle. Say that directly so the sentence does not read as if the exchange itself is replaced. The exchange operator name is unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…er guide Here "a matching product" means a matching row in the products table of the example query, so translate it as a generic noun. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…guides The virtual column guide's title and the SQL reference already use the Japanese term, but the guides kept "virtual column(s)" in English in prose. Align them. Where the page defines the term, keep the English in parentheses. SQL statements and anchors are unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…mizer guide These are generic nouns in prose. Use the term that the TiDB Cloud Lake SQL reference uses for partial aggregation. The "partial" and "final" labels in the plan diagram are unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…on guides Other TiDB Cloud Lake docs translate "tenant" in prose. "Stage" is a TiDB Cloud Lake object name and stays in English with the same casing as the English doc. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… guide "logical" is the value of the wal_level parameter, so keep it in English, but say that the WAL level is set to logical, as the same page does later. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…" in the PostgreSQL integration guide These are generic PostgreSQL terms in prose. The section heading already uses the Japanese terms for publication and replication slot. SQL statements are unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Lowercase "bitmap" is a generic noun for the data structure, which the TiDB Cloud Lake SQL reference translates. The BITMAP data type name is unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Use the AWS Japanese term for security groups and the same wording for "PrivateLink service" as other Japanese TiDB docs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…guide Translate "refresh" in prose as the full-text index guide does, restore "its" so that it is clear the view's query is compared with the baseline, and keep "warehouse" lowercase as in the English doc. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The literal translation reads as indexes reserved for someone or something. Use a term that says the indexes are built for specific purposes, such as full-text and ngram search. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…cture guide The English writes "Bloomfilter" as one word, so the glossary entry for "bloom filter" did not match. Use the term that the rest of the Lake docs and the glossary use. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…table The Japanese for "(own)" ended without a noun. Complete it so that it pairs with "(any)" in the row above. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The English uses "inserts" as a lowercase common noun here. Match the Japanese for deletions and insertions earlier in the same sentence. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… guide Follow up on the earlier translation of "dataset" in this guide, which missed three prose occurrences. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Match the term that the object functions page body already uses. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
yahonda
marked this pull request as ready for review
October 14, 2026 01:37
There was a problem hiding this comment.
Actionable comments posted: 1
ℹ️ Review info
⚙️ Run configuration
- Configuration used: Repository: pingcap/docs/.coderabbit.yaml
- Review profile: ASSERTIVE
- Plan: Advanced
- Run ID:
a9b46dbe-03ce-40cf-be28-6a6f8301674a
📒 Files selected for processing: 101
TOC-tidb-cloud-lake.mdtidb-cloud-lake/_index.mdtidb-cloud-lake/guides/ai-powered-features.mdtidb-cloud-lake/guides/amazon-sqs-s3-iam-role.mdtidb-cloud-lake/guides/audit-trail.mdtidb-cloud-lake/guides/authenticate-with-aws-iam-role.mdtidb-cloud-lake/guides/automate-data-loading-with-tasks.mdtidb-cloud-lake/guides/aws-credentials.mdtidb-cloud-lake/guides/benchmark-data-ingestion.mdtidb-cloud-lake/guides/benchmark-tpch-sf100.mdtidb-cloud-lake/guides/benchmark-tpch-sf1000.mdtidb-cloud-lake/guides/choose-a-udf-type.mdtidb-cloud-lake/guides/cluster-key-performance.mdtidb-cloud-lake/guides/compliance-security.mdtidb-cloud-lake/guides/connect-using-golang.mdtidb-cloud-lake/guides/connect-using-java.mdtidb-cloud-lake/guides/connect-using-lakesql.mdtidb-cloud-lake/guides/connect-using-rust.mdtidb-cloud-lake/guides/connect-with-aws-privatelink.mdtidb-cloud-lake/guides/connection-overview.mdtidb-cloud-lake/guides/continuous-data-pipelines.mdtidb-cloud-lake/guides/data-integration-overview.mdtidb-cloud-lake/guides/data-lifecycle.mdtidb-cloud-lake/guides/data-protection-policies.mdtidb-cloud-lake/guides/data-protection.mdtidb-cloud-lake/guides/data-purge-and-recycle.mdtidb-cloud-lake/guides/deepnote.mdtidb-cloud-lake/guides/editions.mdtidb-cloud-lake/guides/full-text-index.mdtidb-cloud-lake/guides/geo-analytics.mdtidb-cloud-lake/guides/how-fuse-engine-works.mdtidb-cloud-lake/guides/how-json-variant-works.mdtidb-cloud-lake/guides/how-optimizer-works.mdtidb-cloud-lake/guides/integrate-with-amazon-s3.mdtidb-cloud-lake/guides/integrate-with-amazon-sqs-s3.mdtidb-cloud-lake/guides/integrate-with-kafka.mdtidb-cloud-lake/guides/integrate-with-mysql.mdtidb-cloud-lake/guides/integrate-with-postgresql.mdtidb-cloud-lake/guides/integrate-with-tidb.mdtidb-cloud-lake/guides/integration-tasks.mdtidb-cloud-lake/guides/json-search.mdtidb-cloud-lake/guides/kafka-credentials.mdtidb-cloud-lake/guides/lake-poc.mdtidb-cloud-lake/guides/lakehouse-etl.mdtidb-cloud-lake/guides/load-avro.mdtidb-cloud-lake/guides/load-csv.mdtidb-cloud-lake/guides/load-from-bucket.mdtidb-cloud-lake/guides/load-from-local-file.mdtidb-cloud-lake/guides/load-from-remote-file.mdtidb-cloud-lake/guides/load-from-stage.mdtidb-cloud-lake/guides/load-parquet.mdtidb-cloud-lake/guides/load-with-dbt.mdtidb-cloud-lake/guides/manage-costs.mdtidb-cloud-lake/guides/masking-policy.mdtidb-cloud-lake/guides/mcp-client-integration.mdtidb-cloud-lake/guides/mcp-server.mdtidb-cloud-lake/guides/multimodal-data-analytics.mdtidb-cloud-lake/guides/mysql-credentials.mdtidb-cloud-lake/guides/network-policy.mdtidb-cloud-lake/guides/ngram-index.mdtidb-cloud-lake/guides/ownership.mdtidb-cloud-lake/guides/password-policy.mdtidb-cloud-lake/guides/performance-optimization.mdtidb-cloud-lake/guides/platforms-regions.mdtidb-cloud-lake/guides/postgresql-credentials.mdtidb-cloud-lake/guides/pricing-billing.mdtidb-cloud-lake/guides/privileges.mdtidb-cloud-lake/guides/query-avro-files-in-stage.mdtidb-cloud-lake/guides/query-csv-files-in-stage.mdtidb-cloud-lake/guides/query-ndjson-files-in-stage.mdtidb-cloud-lake/guides/query-parquet-files-in-stage.mdtidb-cloud-lake/guides/query-stage.mdtidb-cloud-lake/guides/query-tsv-files-in-stage.mdtidb-cloud-lake/guides/roles.mdtidb-cloud-lake/guides/row-access-policy.mdtidb-cloud-lake/guides/schema-evolution.mdtidb-cloud-lake/guides/security-reliability.mdtidb-cloud-lake/guides/sql-analytics.mdtidb-cloud-lake/guides/superset.mdtidb-cloud-lake/guides/support-services.mdtidb-cloud-lake/guides/tableau.mdtidb-cloud-lake/guides/task-flow.mdtidb-cloud-lake/guides/task-management.mdtidb-cloud-lake/guides/tidb-cloud-lake-architecture.mdtidb-cloud-lake/guides/tidb-data-source.mdtidb-cloud-lake/guides/track-and-transform-data-via-streams.mdtidb-cloud-lake/guides/transform-data-on-load.mdtidb-cloud-lake/guides/troubleshooting.mdtidb-cloud-lake/guides/unload-csv-file.mdtidb-cloud-lake/guides/unload-data.mdtidb-cloud-lake/guides/unload-lance-dataset.mdtidb-cloud-lake/guides/unload-ndjson-file.mdtidb-cloud-lake/guides/unload-parquet-file.mdtidb-cloud-lake/guides/unload-tsv-file.mdtidb-cloud-lake/guides/vector-search-guide.mdtidb-cloud-lake/guides/virtual-column.mdtidb-cloud-lake/guides/warehouse.mdtidb-cloud-lake/lake-overview.mdtidb-cloud-lake/lake-quick-start.mdtidb-cloud-lake/tutorials/ingest-json-logs-with-vector-cloud.mdtidb-cloud-lake/tutorials/migrate-from-snowflake.md
💤 Files with no reviewable changes: 2
- tidb-cloud-lake/guides/ai-powered-features.md
- tidb-cloud-lake/guides/manage-costs.md
Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 3 remain after this review.
2 of 14 tasks
qiancai
approved these changes
Oct 14, 2026
[LGTM Timeline notifier]Timeline:
|
yahonda
added a commit
that referenced
this pull request
Oct 15, 2026
The sync re-translated tidb-cloud-lake/guides/lake-poc.md although its English source did not change in this range, which reverted the fixes merged in #24440 (step headings, translated link texts, and terms). Restore the file from i18n-ja-release-8.5 and keep only the removal of the EN-commit marker, as in the other Lake files of this sync. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
qiancai
added a commit
that referenced
this pull request
Oct 15, 2026
…8.5 on 2026-10-15 (#24456) * [create-pull-request] automated change * i18n(ja): restore the merged fixes in the Lake PoC guide The sync re-translated tidb-cloud-lake/guides/lake-poc.md although its English source did not change in this range, which reverted the fixes merged in #24440 (step headings, translated link texts, and terms). Restore the file from i18n-ja-release-8.5 and keep only the removal of the EN-commit marker, as in the other Lake files of this sync. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * i18n(ja): fix terms and wording in the agent memory guide - Translate "embedding" and "candidate" in prose as 埋め込み and 候補. "Candidate" came from the Raft role entry of the glossary. - Use ステップ N for step headings and references, as in other ai/ guides. - Translate "each part of the table" as 各要素. - Keep "preference" for the kind value consistently, remove 代わりに that is not in the English, and add a space after a link. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * i18n(ja): restore lines that the sync changed without an English change - Restore the Japanese full stop that became an ASCII period in maintain-dm-using-tiup.md and titan-configuration.md, and fix the ASCII period in the new release note entry. - Restore `""` that became `\"\"` in the v6.5.0 release notes. - Restore 結合キー in the v5.2.0 release notes (the English only fixed a typo). - Restore changefeed in changefeed-overview.md, where the line mixed two renderings. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * i18n(ja): add a missing paragraph to the DM compatibility catalog - Translate the paragraph about what the compatibility levels mean, which the sync did not add. - Translate the link text to the DM compatibility catalog in dm-precheck.md, as in other pages. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * i18n(ja): fix terms in the hybrid search with SQL guide and the AI TOC - Use ステップ N for step headings and references, as in other ai/ guides, and translate "candidates" as 候補. - Drop the (load) gloss, which the glossary intends for the Lake docs. - Fix the subject of the READ_FROM_STORAGE hint sentence. - Translate "Agent Memory Guide" in TOC-ai.md, and keep "via Python" in the link text to the Python hybrid search guide in TOC-ai.md and ai/_index.md, as for "via SQL". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * i18n(ja): fix terms and punctuation in the RCU capacity mode docs - Use リクエストキャパシティユニット, as in the rest of the tidb-cloud docs. - Replace half-width colons at the end of sentences with a full stop. - Drop the English plural "s" from "2,000 RCUs". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * i18n(ja): translate "preference" as a common noun in the agent memory guide In "When a user changes a preference", the word is a common noun, so translate it as 好み. Other sites keep "preference" because they refer to rows whose kind is 'preference'. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * i18n(ja): fix the stale read note in the agent memory guide The Japanese read as if reading took a short time. Translate "can still be read for a short time ... until garbage collection removes the old row versions" so that the short time is the period before garbage collection, and drop the hedge that is not in the English. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * i18n(ja): fix the wording for "do not support at all" in the partitioned tables best practices Translate "do not support DROP PARTITION at all" with そもそも, which reads more naturally than まったくサポートしていない. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * i18n(ja): translate "presigned URL" in the load from local file guide Translate the lowercase "presigned URL" as 事前署名付き URL, as in the PRESIGN reference. The setting name stays in English. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * i18n(ja): translate "Baseline RCU" in prose to contrast with the maximum RCU Translate "Baseline RCU" as ベースラインRCU in prose, so that it reads as a pair with 最大RCU. Keep the bold **Baseline RCU**, which is the label of the console setting. Spacing follows the neighboring 最大RCU in each file. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * i18n(ja): translate the H1 of the Lake TOC Use 目次 for the H1 of TOC-tidb-cloud-lake.md, as in all other Japanese TOC files. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * i18n(ja): fix accuracy and wording in the ai/ docs from the second review - vector-search-index.md: "limit the final result" is a plain verb, so do not render it as `LIMIT`, and make the filter the subject of the sentence about fewer rows. - vector-search-hybrid-search-sql.md: localize the AWS region list as in the sibling guides. - agent-memory.md: the application is authorized to access the users' memories, not the users; split a sentence with two concessive clauses; reorder the example clause in the delete sentence. - TOC-ai.md: drop "AI", which is not in the English TOC entry. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * i18n(ja): fix residual English and casing in the DM compatibility catalog Translate the lowercase "tagged GTIDs" and the two link texts, and use lowercase "binlog" as in the English and the rest of the file. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * i18n(ja): fix accuracy and wording in the RCU capacity mode docs - tidb-cloud-release-notes.md: say "for workloads that require more than 100,000 RCUs" instead of "if you need a workload that exceeds". - monitor-built-in-alerting.md: avoid repeating 場合は in one clause. - architecture-concepts.md: smooth the でもあり、つまり sentence. - backup-and-restore-serverless.md: reorder the fixed Baseline RCU phrase, as in create-tidb-cluster-serverless.md. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: qiancai <79440533+qiancai@users.noreply.github.com> Co-authored-by: Yasuo Honda <yahonda@pingcap.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2 of 6 tasks
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
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)
This PR is part 1 of 4 that fix the Japanese TiDB Cloud Lake docs (
tidb-cloud-lake/, added in #24373 and synced in #24431). The changes come from a full review of all 1,121 Japanese Lake files against the English source onrelease-8.5. Following the request to group related fixes, the fixes are filed as four PRs that do not touch the same files. Each PR keeps one commit per theme, so you can review it commit by commit.This PR covers
tidb-cloud-lake/guides/,tidb-cloud-lake/tutorials/,_index.md,lake-overview.md,lake-quick-start.md, andTOC-tidb-cloud-lake.md(101 files).Commits (themes):
_index.mdbelow the front matter (the page rendered the front matter as text with an empty title), deleteguides/ai-powered-features.mdandguides/manage-costs.mdand the billing role section inguides/roles.mdto match docs(lake): remove AI-powered features and cost entries #24422 (the sync does not carry over deletions), remove links and bold markup added to front matter summaries, and restore lost list markers in notes.Kept in English on purpose: identifiers, SQL keywords, function and type names, UI labels, the admonition labels that the site renders, and the terms that
resources/terms-en-ja.mdkeeps in English (stage, Warehouse, Worksheet, Schema Evolution, and so on). The "ロード (load)" gloss is kept because the glossary requires it.Related: the glossary entry
Aggregation → 集計is removed in #24438 so that the translator can choose the term from context.Other parts of this series: #24441, #24442, #24443
Which TiDB version(s) do your changes apply to? (Required)
Tips for choosing the affected version(s):
By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.
For details, see tips for choosing the affected versions.
What is the related PR or file link(s)?
AI agent involvement
Do your changes match any of the following descriptions?
🤖 Generated with Claude Code
Summary by CodeRabbit