i18n(ja): unify SQL statement terminology to the native noun form - #23668
Conversation
|
Skipping CI for Draft Pull Request. |
|
Important Review skippedToo many files! This PR contains 552 files, which is 402 over the limit of 150. To get a review, reduce the PR to 150 files or fewer by splitting it into smaller PRs or changing its base branch. Upgrade to a paid plan to raise the limit. Usage-priced reviews support at most 300 files. ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Team Run ID: 📒 Files selected for processing (552)
You can disable this status message by setting the 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 |
|
[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 |
4f0dbba to
01f3eb5
Compare
Convert "<SQL-command-keyword>+katakana-loanword-for-statement" to "<SQL-command-keyword>+native-noun-form" across the corpus (SQL/DDL/DML plus individual command keywords such as SELECT/INSERT/UPDATE/DELETE/ CREATE TABLE/ALTER TABLE/EXPLAIN/ANALYZE/EXECUTE/PREPARE/SHOW variants/ GRANT/REVOKE/COMMIT/ROLLBACK/etc.), matching established Japanese DB documentation convention. Left untouched: standalone generic references to a statement, "prepared statement", and STATEMENT_SUMMARY-related compounds. 546 files changed, 2359 occurrences converted.
…de-connection-parameters.md
… fix misplaced wiki link
…takana spelling - dev-guide-insert-data.md: move the ga particle outside the italic-bold emphasis span (matches EN's single-word "must" emphasis) - dev-guide-tidb-basics.md: move the wo particle outside a bold span - Unify covering-index katakana spelling to the dominant no-long-vowel form (12 vs 6 occurrences corpus-wide) across dev-guide-index-best-practice.md, dev-guide-optimize-sql.md (fixes a same-passage self-contradiction between its own heading and body text), and sql-tuning-best-practice.md
…uide-tidb-crud-sql.md
…ng and style register in release-8.0.0.md
…nt-to-bun conversions
…-consumer-dev-guide.md
…stency in partitioned-table.md
57def2a to
ebb5ddc
Compare
[LGTM Timeline notifier]Timeline:
|
What is changed, added or deleted? (Required)
Unifies the Japanese term for "statement" in
<SQL-command-keyword> statementcompounds(e.g. "SELECT statement", "DDL statement") from the katakana loanword form to the native
noun form, matching established Japanese DB documentation convention. Applies to SQL/DDL/DML
plus individual command keywords (SELECT/INSERT/UPDATE/DELETE/CREATE TABLE/ALTER TABLE/
EXPLAIN/ANALYZE/EXECUTE/PREPARE/SHOW variants/GRANT/REVOKE/COMMIT/ROLLBACK/BACKUP/RESTORE/
FLASHBACK/SPLIT/ADMIN ... and more, ~80 recognized keyword patterns).
546 files changed, 2359 occurrences converted.
Left deliberately untouched (mechanical, low-risk-first pass):
<keyword> statementpattern).STATEMENT_SUMMARY-related compounds (statement summary/cache/pool).(
SQL statement string,init_connect statement,SQL BINDING statement).Also found in passing (out of scope for this PR, filed as follow-up items, not fixed here):
WHERE/JOIN/ORDER BY/GROUP BYare mistranslated as "statement" in several files whenthey should say "clause" — a pre-existing translation bug, unrelated to this term-unification pass.
tidb-cloud/changefeed-sink-to-*.mdfiles("...
idstatement...", nonsensical) — a pre-existing MT defect, not a term issue.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?