Skip to content

i18n(ja): replace 'TiDB ダッシュボード' with 'TiDB Dashboard'#23169

Open
yahonda wants to merge 1 commit into
pingcap:i18n-ja-release-8.5from
yahonda:topic-i18n-ja-tidb-dashboard
Open

i18n(ja): replace 'TiDB ダッシュボード' with 'TiDB Dashboard'#23169
yahonda wants to merge 1 commit into
pingcap:i18n-ja-release-8.5from
yahonda:topic-i18n-ja-tidb-dashboard

Conversation

@yahonda

@yahonda yahonda commented Jun 30, 2026

Copy link
Copy Markdown
Member

What is changed, added or deleted? (Required)

Replace Japanese-translated "TiDB ダッシュボード" and "TiDBダッシュボード" with the English product name "TiDB Dashboard" in PD web UI context (112+ files), keeping Japanese grammar particles intact.

Not changed (Grafana context, remains as katakana ダッシュボード):

  • grafana-tidb-dashboard.md, tidb-performance-tuning-config.md, system-variables.md, tidb-upgrade-migration-guide.md, troubleshoot-stale-read.md, troubleshoot-lock-conflicts.md, best-practices/saas-best-practices.md, schema-cache.md

Additional fixes included:

  • キービジュアライザーKey Visualizer (16 occurrences)
  • 遅いクエリ/低速クエリ/最もスロークエリスロークエリ (100+ occurrences)
  • 高価なクエリ負荷の高いクエリ (7 occurrences)
  • Perl依存関係Perl実行環境
  • 機械タイプマシン種別
  • 認証および承認認証および認可
  • DashboardUIDashboard UI
  • 印刷出力 (slow query log context)
  • Various missing particles (を, の) added
  • English config section headings in ticdc-changefeed-config
  • Removed stray annotation numbers not in English original
  • TOC, URL path fixes, and other terminology consistency fixes

Decision criteria

  • TiDB Dashboard (English, capital D): PD web UI product (固有名詞)
  • TiDBダッシュボード (katakana): Grafana TiDB sub-dashboard (一般名称)

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

  • master (the latest development version)
  • v8.5 (TiDB 8.5 versions)
  • v8.4 (TiDB 8.4 versions)
  • v8.3 (TiDB 8.3 versions)
  • v8.2 (TiDB 8.2 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)
  • v5.4 (TiDB 5.4 versions)
  • v5.3 (TiDB 5.3 versions)

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

  • This PR is translated from:
  • Other reference 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 Bot added the area/develop This PR relates to the area of TiDB App development. label Jun 30, 2026
@ti-chi-bot

ti-chi-bot Bot commented Jun 30, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign kissmydb for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

The full list of commands accepted by this bot can be found 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 missing-translation-status This PR does not have translation status info. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Jun 30, 2026

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request consistently updates the Japanese documentation to use "TiDB Dashboard" instead of "TiDBダッシュボード". The reviewer provided highly constructive and actionable feedback across multiple files to correct minor typos, grammatical errors, formatting issues (such as missing backticks or bold markers), and punctuation in the Japanese text. These suggestions significantly improve the natural flow, readability, and correctness of the Japanese documentation. All review comments are valid and should be kept.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

Comment thread deploy-monitoring-services.md
Comment thread troubleshoot-lock-conflicts.md Outdated
Comment thread troubleshoot-lock-conflicts.md Outdated
Comment thread releases/release-8.4.0.md
Comment thread sql-tuning-best-practice.md
Comment thread tidb-cloud/tidb-cloud-clinic.md
Comment thread tidb-monitoring-framework.md Outdated
Comment thread tiup/tiup-cluster.md
Comment thread best-practices/tidb-best-practices.md Outdated
Comment thread dashboard/dashboard-ops-deploy.md Outdated
@yahonda yahonda marked this pull request as draft June 30, 2026 02:23
@ti-chi-bot ti-chi-bot Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 30, 2026
@yahonda yahonda force-pushed the topic-i18n-ja-tidb-dashboard branch 5 times, most recently from f921b09 to c06dd96 Compare July 1, 2026 01:14
@yahonda yahonda force-pushed the topic-i18n-ja-tidb-dashboard branch 3 times, most recently from 166681f to 9d561b4 Compare July 1, 2026 02:52
@yahonda yahonda force-pushed the topic-i18n-ja-tidb-dashboard branch from 9d561b4 to f439867 Compare July 1, 2026 02:53
@yahonda yahonda marked this pull request as ready for review July 1, 2026 03:01
@ti-chi-bot ti-chi-bot Bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/develop This PR relates to the area of TiDB App development. missing-translation-status This PR does not have translation status info. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant