Skip to content

Conversation

@craigary
Copy link
Contributor

1. Added vacations section

  • Added a complete set of translations for the vacations section.
  • Covers the team's break from Feb 14–21 and Discord availability.

2. Punctuation & Key Completion

  • Punctuation: Standardized the use of full-width parentheses and two-em dashes for better CJK typography.
  • Missing Keys: Updated translation for pkg.versions.y_axis_label.

3. Terminology: Reverting Copy to 拷贝

Updated 10 instances of Copy related actions to use 拷贝 instead of 复制.

Regarding this point, I previously updated Copy to 拷贝 in a prior PR. However, it was reverted back to 复制 in PR #1108. I believe 拷贝 is a more appropriate translation for Copy than 复制 for the following reasons:

  • Semantic Clarity: In Chinese, 复制 is more synonymous with Duplicate (creating an identical replica). 拷贝 better represents the action of placing content onto the clipboard for a "Copy and Paste" workflow.
  • Platform Standards: Following the standard established by Apple's Human Interface Guidelines, "Copy" is localized as 拷贝. While 复制 is common in some Windows-influenced contexts (which is clearly wrong imo 😈), translating "Copy" as 拷贝 is both accurate and unambiguous.
  • Phonetic & Technical Precision: As a direct transliteration of Copy, 拷贝 is a well-established technical term in Chinese that eliminates ambiguity, maintaining a consistent professional tone throughout the project.

cc @danielroe @9romise @KazariEX

@vercel
Copy link

vercel bot commented Feb 12, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
npmx.dev Ready Ready Preview, Comment Feb 12, 2026 8:14pm
2 Skipped Deployments
Project Deployment Actions Updated (UTC)
docs.npmx.dev Ignored Ignored Preview Feb 12, 2026 8:14pm
npmx-lunaria Ignored Ignored Feb 12, 2026 8:14pm

Request Review

@github-actions
Copy link

github-actions bot commented Feb 12, 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
lunaria/files/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

codecov bot commented Feb 12, 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
Contributor

coderabbitai bot commented Feb 12, 2026

📝 Walkthrough

Walkthrough

This pull request updates Chinese locale files for both i18n/locales/zh-CN.json and lunaria/files/zh-CN.json. The changes include replacing "复制" with "拷贝" across copy-related UI string keys, normalising punctuation and bracket styles in multiple translated strings, adding a new top-level "vacations" section containing maintenance/休假 announcement content, and introducing a new versions.distributions date_range_tooltip.y_axis_label key with value "下载". All changes are value updates within JSON locale keys; there are no structural data model changes.

Possibly related PRs

Suggested reviewers

  • danielroe
🚥 Pre-merge checks | ✅ 2
✅ Passed checks (2 passed)
Check name Status Explanation
Description check ✅ Passed The pull request description clearly relates to the changeset, detailing the addition of vacation translations, punctuation standardization, and terminology updates from 復制 to 拷貝 across 10 instances.
Merge Conflict Detection ✅ Passed ✅ No merge conflicts detected when merging into main

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

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

No actionable comments were generated in the recent review. 🎉

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.


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

Copy link
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: 2

@RYGRIT
Copy link
Contributor

RYGRIT commented Feb 12, 2026

Thanks for the PR and detailed rationale!

I still prefer sticking with 复制 for these reasons:

  • It matches what most users see in browsers (Chrome/Edge right-click → 复制), which is the main way people access npmx.dev.

  • In the Chinese dev community (B站, Zhihu, 掘金, etc.), 复制 is the overwhelming default for clipboard actions like copy install command or code snippets.

  • While Apple uses 拷贝, this is a cross-platform web app, not a macOS-native one. Aligning with browser/default Chinese usage feels more natural for our audience.

Happy to discuss more if you have other thoughts!

@9romise
Copy link
Member

9romise commented Feb 13, 2026

Personally, I prefer "复制", just like my original translation. To me, it clearly reads as shorthand for "复制到剪贴板" (copy to clipboard).
In most mainstream Chinese apps (WeChat, Douyin, Xiaohongshu, etc.), "复制" is the standard translation for "copy". It’s already a very commonly used term.
I don’t think repeatedly toggling between "复制" and "拷贝" adds much value, both are perfectly understandable. All it really does is drain the maintainers’ energy.

@serhalp serhalp requested a review from 9romise February 13, 2026 01:18
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