123123213weqw opened a new issue, #5221: URL: https://github.com/apache/rocketmq-dashboard/issues/5221
### Before creating - [x] I have searched the existing issues and found no duplicate. - [x] I have checked the latest `rocketmq-studio` branch where this problem still exists. ### Bug report **Which page or component** `web/src/pages/settings/AboutTab.tsx`, `web/src/i18n/translations.ts` **What happened** #4803 (merged) localized the About tab: every Descriptions label went through `t()` (`settings.aboutVersion`, `settings.aboutBuildCommit`, …), the "相关链接" heading and the "文档中心" / "RocketMQ 社区" link texts were keyed, and the nine `settings.about*` entries were added to the translation table, with a test mocking `t` to identity and asserting the keys render. On the current `rocketmq-studio` head (`4ee173ad`) all of that is gone: - `AboutTab.tsx` renders the hardcoded Chinese literals again (`label="版本"`, `label="构建提交"`, `相关链接`, `文档中心`, `RocketMQ 社区`); - the `settings.about*` keys are absent from `translations.ts`; - the test's localization assertions are gone. So an English viewer again gets a fully Chinese About tab. The likely cause is one of the branch folds losing the file wholesale — the tab's content values did move on (3.0.0, "Spring Boot 4.1"), so a later rebase re-introduced a pre-#4803 copy of the component. **Steps to reproduce** 1. Switch the display language to English. 2. Open Settings → About. 3. Every label is Chinese: 版本 / 构建提交 / 构建时间 / RocketMQ 支持版本 / 前端框架 / 后端框架 / 相关链接 / 文档中心 / RocketMQ 社区. **Expected behaviour** The #4803 state restored on top of the current content values: labels through `t()`, the nine `settings.about*` keys back in the table, and the identity-t test pinning them. **Environment** branch `rocketmq-studio`, commit `4ee173ad`. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
