fix(i18n): align zh-CN wording with the other locales - #50
Merged
Merged
Conversation
- Use 一把 instead of 一柄 for the API key quantifier, matching the other occurrences in this file (activeKeyCount, keyCount, docsDescription, saveKeyTitle) which all use 把. - Restore 完整 in the one-time key notice, matching the English source (the full key is shown only once) and the zh-TW wording. - Use 请求次数 in the usage description, matching the existing requests label (请求数) elsewhere in this file.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Aligns three zh-CN strings with the terminology already used elsewhere in
i18n.tsxand with the other locales.homeWithoutKeysnoKeyDescriptionusageDescriptionWhy
homeWithoutKeysdropped "full" from the English source (the full key is shown only once). The zh-TW string already says 完整金鑰, andsaveKeyDescriptionin the same file already uses 完整密钥.noKeyDescriptionused the wrong measure word 一柄 for an API key. Every other occurrence in this file (activeKeyCount,keyCount,docsDescription,saveKeyTitle) uses 把.usageDescriptionsaid 调用次数, while therequestslabel in the same file is translated as 请求数.Scope
Three zh-CN strings only. No zh-TW or en changes, no code changes.