Skip to content

feat(i18n): update missing Chinese Simple(zh-CN) translations#2367

Open
fnoopv wants to merge 1 commit intonpmx-dev:mainfrom
fnoopv:main
Open

feat(i18n): update missing Chinese Simple(zh-CN) translations#2367
fnoopv wants to merge 1 commit intonpmx-dev:mainfrom
fnoopv:main

Conversation

@fnoopv
Copy link
Copy Markdown

@fnoopv fnoopv commented Apr 3, 2026

🔗 Linked issue

No GitHub issue, general call for translation support.

🧭 Context

屏幕截图_20260403_152002

📚 Description

Add missing translation entries.

@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 3, 2026

Hello! Thank you for opening your first PR to npmx, @fnoopv! 🚀

Here’s what will happen next:

  1. Our GitHub bots will run to check your changes.
    If they spot any issues you will see some error messages on this PR.
    Don’t hesitate to ask any questions if you’re not sure what these mean!

  2. In a few minutes, you’ll be able to see a preview of your changes on Vercel

  3. One or more of our maintainers will take a look and may ask you to make changes.
    We try to be responsive, but don’t worry if this takes a few days.

@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 3, 2026

Lunaria Status Overview

🌕 This pull request will trigger status changes.

Learn more

By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.

You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File Note
i18n/locales/zh-CN.json Localization changed, will be marked as complete.
Warnings reference
Icon Description
🔄️ The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

@codecov
Copy link
Copy Markdown

codecov bot commented Apr 3, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Apr 3, 2026

📝 Walkthrough

Walkthrough

This pull request expands the Chinese localisation file (zh-CN.json) with 192 new lines of translation strings across multiple UI sections. The changes introduce localised text for brand navigation and assets, enhanced blog and settings sections, improved package and profile displays with skills labels and version information, extended code viewer controls, new filtering and comparison UI components, and additional comparison panel features including diff controls and validation messaging. A complete translation status page section and vacations section with metadata are also added.

Possibly related PRs

Suggested reviewers

  • danielroe
  • 9romise
  • ghostdevv
🚥 Pre-merge checks | ✅ 1
✅ Passed checks (1 passed)
Check name Status Explanation
Description check ✅ Passed The pull request description directly relates to the changeset, which adds missing Chinese translation entries to zh-CN.json as indicated by the screenshot showing missing translations.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1


ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 1bc15fb3-8254-4b46-bfd8-744ba620c3ab

📥 Commits

Reviewing files that changed from the base of the PR and between d3f60cb and e434578.

📒 Files selected for processing (1)
  • i18n/locales/zh-CN.json

Comment on lines +1420 to +1427
"p1_count": "0 条消息 | 1 条消息 | {count} 条消息",
"p2": "开始之前,请先阅读我们的 {guide},了解翻译流程以及你可以如何参与。",
"guide": "本地化(i18n)指南",
"by_locale": "按语言区域查看翻译进度",
"by_file": "按文件查看翻译进度",
"complete_text": "该翻译已完成,做得太棒了!",
"missing_text": "缺失",
"missing_keys": "没有缺失的翻译 | 缺失翻译 | 缺失翻译",
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot Apr 3, 2026

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Fix the counted translation_status plural strings.

The last p1_count branch should not start with a space, otherwise the surrounding sentence renders with a double space. Also, missing_keys currently drops the number for non-zero cases, so the status no longer tells the reader how many strings are still missing.

[suggested patch]

Suggested patch
-    "p1_count": "0 条消息 | 1 条消息 | {count} 条消息",
+    "p1_count": "0 条消息 | 1 条消息 |{count} 条消息",
@@
-    "missing_keys": "没有缺失的翻译 | 缺失翻译 | 缺失翻译",
+    "missing_keys": "没有缺失的翻译 | 1 项缺少翻译 | {count} 项缺少翻译",

Based on learnings: In locale JSON files under i18n/locales/ (including en.json), for the translation_status.p1_count key’s third plural form, the formatting intentionally omits the space before {count}.

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.

Could you take a look at this suggestion @fnoopv 🙏

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.

Seems like the humans are having a chat. I'll hop back into my burrow for now. If you need me again, just tag @coderabbitai in a new comment, and I'll come hopping out!

},
"chart_view_toggle": "切换视图",
"chart_view_combined": "合并视图",
"chart_view_split": "分离视图",
Copy link
Copy Markdown
Contributor

@RYGRIT RYGRIT Apr 4, 2026

Choose a reason for hiding this comment

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

I think using "拆分试图" here would be more appropriate.

Copy link
Copy Markdown
Contributor

@RYGRIT RYGRIT left a comment

Choose a reason for hiding this comment

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

What do you think?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants