Skip to content

br: reword 'Base64-encoded storage' for accurate machine translation (#21714)#21726

Merged
ti-chi-bot[bot] merged 1 commit into
pingcap:masterfrom
ti-chi-bot:cherry-pick-21714-to-master
Jun 18, 2026
Merged

br: reword 'Base64-encoded storage' for accurate machine translation (#21714)#21726
ti-chi-bot[bot] merged 1 commit into
pingcap:masterfrom
ti-chi-bot:cherry-pick-21714-to-master

Conversation

@ti-chi-bot

Copy link
Copy Markdown
Member

This is an automated cherry-pick of #21714

What is changed, added or deleted? (Required)

This PR rewords ambiguous English phrases in br/br-compact-log-backup.md to produce more accurate machine translations to Japanese.

Problem:
The original English text contains the phrase "Base64-encoded storage", which machine translators (and human translators) interpret as "storage itself being Base64-encoded". This leads to unnatural Japanese translations like "Base64エンコードストレージ" (Base64-encoded storage), which is confusing because what is actually encoded is the storage URI/string, not the storage.

The root cause traces back to the Chinese source phrase "有了存储的 Base64" (the Base64 of the storage / the storage's Base64), which was translated to English as "Base64-encoded storage" — reversing the possessive relationship and changing the meaning.

Changes:

Before After Why
"matches the storage output" "should match the output" "storage output" is a confusing compound noun that MT renders literally as "storage出力"
"With the Base64-encoded storage, you can initiate the compaction..." "Once you have the Base64-encoded string from the previous step, you can start compaction..." Clarifies that the string (not the storage) was encoded; "initiate the compaction" is also overly formal
"the Base64-encoded storage string obtained earlier" "the Base64-encoded string obtained in the previous step" Same compound-noun ambiguity as above

These changes ensure machine translation produces natural Japanese: e.g., "Base64エンコードされた文字列" instead of the nonsensical "Base64エンコードストレージ".

Which TiDB version(s) do your changes apply to? (Required)

  • master (the latest development version)
  • v9.0 (TiDB 9.0 versions)
  • v8.5 (TiDB 8.5 versions)
  • v8.1 (TiDB 8.1 versions)
  • v7.5 (TiDB 7.5 versions)
  • v7.1 (TiDB 7.1 versions)
  • v6.5 (TiDB 6.5 versions)
  • v6.1 (TiDB 6.1 versions)

What is the related PR or file link(s)?

Do your changes match any of the following descriptions?

  • Delete files
  • Change aliases
  • Need modification after applied to another branch
  • Might cause conflicts after applied to another branch

@ti-chi-bot ti-chi-bot added lgtm size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. type/cherry-pick-for-master This PR is cherry-picked to master from a source PR. type/enhancement The issue or PR belongs to an enhancement. labels Jun 18, 2026
@qiancai

qiancai commented Jun 18, 2026

Copy link
Copy Markdown
Collaborator

/approve

@ti-chi-bot

ti-chi-bot Bot commented Jun 18, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: qiancai

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ti-chi-bot ti-chi-bot Bot added the approved label Jun 18, 2026
@ti-chi-bot ti-chi-bot Bot merged commit 642d782 into pingcap:master Jun 18, 2026
10 checks passed
@ti-chi-bot ti-chi-bot Bot deleted the cherry-pick-21714-to-master branch June 18, 2026 04:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved lgtm size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. type/cherry-pick-for-master This PR is cherry-picked to master from a source PR. type/enhancement The issue or PR belongs to an enhancement.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants