i18n(ja): fix mistranslated letter N in DDL allow-list table - #23459
i18n(ja): fix mistranslated letter N in DDL allow-list table#23459yahonda wants to merge 1 commit into
Conversation
|
Skipping CI for Draft Pull Request. |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus 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 |
|
[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 |
5cfc108 to
a712870
Compare
Every "N" (meaning "replication not supported") in the DDL allow-list table was mistranslated as a kanji character meaning "North" -- 25 occurrences across 25 rows (DROP INDEX, DROP PRIMARY KEY, CREATE TABLE, DROP TABLE, ADD COLUMN, etc.). The table's own legend directly above it already correctly defines the letter N literally, confirming it was meant to stay as-is in the table body, not be translated. Also fixed a missing sentence-boundary period that had merged two separate English sentences into one run-on Japanese sentence.
a712870 to
09221c6
Compare
What is changed, added or deleted? (Required)
Every "N" (meaning "replication not supported") in the DDL allow-list table in
ticdc/ticdc-ddl.mdwas mistranslated as a kanji character meaning "North" — 25 occurrences across 25 rows (DROP INDEX,DROP PRIMARY KEY,CREATE TABLE,DROP TABLE,ADD COLUMN, etc.). The table's own legend directly above it already correctly defines the letter N literally, confirming it was meant to stay as-is in the table body, not be translated.Also fixed a missing sentence-boundary period that had merged two separate English sentences into one run-on Japanese sentence in the same file.
Which TiDB version(s) do your changes apply to? (Required)
Do your changes match any of the following descriptions?