i18n(ja): remove stray brace artifacts and fix accompanying word-order swaps - #23699
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 |
|
Warning Review limit reachedNext included review available in 40 minutes. View limit detailsLimit details: You’ve used all 4 included reviews currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Team Run ID: 📒 Files selected for processing (11)
📝 WalkthroughWalkthroughThis pull request corrects Japanese documentation wording, terminology, file references, examples, and stray characters across AI, development, migration, SQL, TiDB Cloud, and troubleshooting pages. No code behavior or public entity declarations changed. ChangesAI documentation examples
Development guides and application examples
Migration and Data Migration guides
SQL and database reference text
Cloud, operational, and troubleshooting documentation
Estimated code review effort: 1 (Trivial) | ~5 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Description checkExplanation The description clearly explains the documentation-only fixes, affected scope, validation against the English source, version applicability, and AI involvement. The required sections are present; blank reference-link fields are non-critical. Full details: Docstring CoverageExplanation 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 files. (8 skipped: 8 unsupported.) ✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 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 |
ti-chi-bot
Bot
added
missing-translation-status
ti-chi-bot
Bot
removed
the
do-not-merge/work-in-progress
yahonda
changed the title
yahonda
changed the title
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 7
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Team
Run ID: a0e840b8-9461-4a44-ba4e-f52234fffeef
📒 Files selected for processing (43)
ai/integrations/vector-search-auto-embedding-amazon-titan.mdai/integrations/vector-search-integrate-with-llamaindex.mdai/quickstart-via-sql.mddevelop/dev-guide-create-table.mddevelop/dev-guide-proxysql-integration.mddevelop/dev-guide-sample-application-aws-lambda.mddevelop/dev-guide-sample-application-nextjs.mddevelop/dev-guide-sample-application-nodejs-mysql2.mddevelop/dev-guide-sample-application-nodejs-mysqljs.mddevelop/dev-guide-sample-application-nodejs-prisma.mddevelop/dev-guide-sample-application-nodejs-typeorm.mddevelop/java-app-best-practices.mddevelop/serverless-driver-prisma-example.mddevelop/serverless-driver.mddm/dm-compatibility-catalog.mddm/feature-shard-merge-pessimistic.mddm/manually-upgrade-dm-1.0-to-2.0.mddm/task-configuration-file-full.mdfaq/manage-cluster-faq.mdindex-advisor.mdinformation-schema/information-schema-slow-query.mdmigrate-from-csv-files-to-tidb.mdmigrate-from-parquet-files-to-tidb.mdmigrate-from-sql-files-to-tidb.mdmigrate-large-mysql-shards-to-tidb.mdpartitioned-table.mdplacement-rules-in-sql.mdreleases/release-8.0.0.mdsql-mode.mdsql-statements/sql-statement-alter-resource-group.mdsql-statements/sql-statement-create-index.mdstatement-summary-tables.mdsync-diff-inspector/sync-diff-inspector-overview.mdsystem-variables.mdticdc/ticdc-compatibility.mdtidb-cloud/data-service-oas-with-nextjs.mdtidb-cloud/essential-changefeed-overview.mdtidb-cloud/integrate-tidbcloud-with-netlify.mdtidb-cloud/integrate-tidbcloud-with-vercel.mdtidb-cloud/migrate-from-mysql-using-aws-dms.mdtidb-cloud/set-up-private-endpoint-connections-on-alibaba-cloud.mdtidb-troubleshooting-map.mdtikv-configuration-file.md
Included review availability: Your plan provides up to 4 included reviews per hour; 1 remains after this review.
…rder swaps (part 1) Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…rder swaps (part 2) Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
"SQL ステートメント`ORDER BY`" read as an ungrammatical bare compound; added の to connect ステートメント and ORDER BY properly. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
The JA sentence dropped "index" entirely and mislabeled the index name idx as if it were the expression, instead of LOWER(col1). EN: "create the expression index idx on the expression LOWER(col1)". Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
The sentence dropped "line terminator" (行終端記号) and "CSV file" entirely, leaving only two bare backtick terms with no connecting words. EN: "You need to explicitly specify the line terminator terminator for a strict-format CSV file." Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
- dev-guide-sample-application-nodejs-typeorm.md: restored dropped
"environment variable" and ".env file" wording
- placement-rules-in-sql.md: fixed a dangling sentence fragment
("...1つFollower。") and a garbled second bullet missing "region"
and "label" wording
- tidb-cloud/integrate-tidbcloud-with-vercel.md: moved the misplaced
"dynamic IP addresses" link (and the word 動的) back to its correct
position earlier in the sentence
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
The sentence used リージョン for the first Region mention but switched to the generic 領域 for the second, even though EN uses "Region" (the TiKV concept) both times. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…toml swaps 4 sentences in this file said "X is the value of config.toml within the Y file", when EN says "X is the value of Y within the config.toml file" — Y (output-dir, task.target-instance) is the config KEY and config.toml is the FILE it lives in, not the other way around. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
45ed796 to
b564943
Compare
qiancai
added
translation/no-need
|
@yahonda Coderabbit made some commitable suggestions on this PR. PTAL. Thanks. |
|
@qiancai Reviewed all 7 CodeRabbit suggestions against the EN source (release-8.5):
PTAL. |
[LGTM Timeline notifier]Timeline:
|
2 participants
What is changed, added or deleted? (Required)
Corpus-wide sweep for a stray, unpaired
}character left over from a botched machine-translation pass (usually right after a backtick-quoted code span). Most occurrences of this artifact were also accompanied by a word-order swap of the two nearby terms relative to EN, since the artifact and the swap appear to share the same root cause in the original machine-translation output.Fixed 66 occurrences across 44 files:
}and corrected a swapped pair of terms (e.g.CREATE DATABASE/file-name order, config-item/value order,AUTO_RANDOM/AUTO_INCREMENTorder)}needed removingindex-advisor.md,statement-summary-tables.md,tikv-configuration-file.md,tidb-troubleshooting-map.md,placement-rules-in-sql.md) where more than two terms had been cross-wired, or where a word (e.g. "environment variable", "index", "line terminator", "CSV file") had been dropped entirelytikv-configuration-file.mdconfig.tomlwithin theoutput-dirfile" instead of "value ofoutput-dirwithin theconfig.tomlfile") insync-diff-inspector-overview.md, fixed across all 4 occurrencesEach fix was verified against the corresponding EN source in
release-8.5, including an independent 1:1 review pass. One related site was intentionally left untouched (out of scope for this PR):tidb-cloud/get-started-with-cli.md, already fixed in #23698.Which TiDB version(s) do your changes apply to? (Required)
What is the related PR or file link(s)?
AI agent involvement
Do your changes match any of the following descriptions?
Summary by CodeRabbit