Update and improve zh-TW Traditional Chinese locale#22423
Update and improve zh-TW Traditional Chinese locale#22423stonezdj merged 1 commit intogoharbor:mainfrom
Conversation
8241051 to
0a239bc
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #22423 +/- ##
===========================================
+ Coverage 45.36% 65.87% +20.50%
===========================================
Files 244 1073 +829
Lines 13333 116036 +102703
Branches 2719 2931 +212
===========================================
+ Hits 6049 76433 +70384
- Misses 6983 35365 +28382
- Partials 301 4238 +3937
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
693b7f3 to
d809efa
Compare
| @@ -61,52 +61,54 @@ | |||
| "DELETED_FAILURE": "刪除失敗或部分失敗", | |||
| "SWITCH_SUCCESS": "切換成功", | |||
| "SWITCH_FAILURE": "切換失敗", | |||
| "REPLICATE_SUCCESS": "複製成功", | |||
| "REPLICATE_FAILURE": "複製失敗", | |||
| "REPLICATE_SUCCESS": "複製已開始", | |||
There was a problem hiding this comment.
Regarding those two terms related to replication, I prefer the existing ones as they are more concise.
There was a problem hiding this comment.
The meaning here should be closer to “Replication initiated successfully” rather than “Replication (already) successful”?
There was a problem hiding this comment.
For clarity on replication jobs, the UI only confirms they were initiated, so translating it as “Replication started” highlights the action taken without implying the entire workflow already completed.
| "OIDC_VERIFYCERT": "如果您的 OIDC 伺服器是透過自簽章憑證託管的,請取消勾選此核取方塊。", | ||
| "OIDC_AUTOONBOARD": "跳過使用者初次設定畫面,使其無法變更使用者名稱。使用者名稱將由 ID Token 提供。", | ||
| "OIDC_USER_CLAIM": "ID Token 中用來擷取使用者名稱的宣告名稱。如果未指定,預設為 'name'。", | ||
| "NEW_SECRET": "金鑰長度應為 8-128 個字元,且至少包含 1 個大寫字母、1 個小寫字母和 1 個數字。", |
There was a problem hiding this comment.
maybe 密鑰 is more concise here?
There was a problem hiding this comment.
It doesn't seem to be a common zh-TW usage in my opinion, though there's a similar term in Microsoft Globalization terminology - "祕密金鑰" for "Secret Key".
| "ADMIN_RENAME_TIP": "選取此按鈕以將使用者名稱變更為「admin@harbor.local」。此操作無法復原。", | ||
| "RENAME_SUCCESS": "重新命名成功!", | ||
| "RENAME_CONFIRM_INFO": "警告:將名稱變更為 admin@harbor.local 後將無法復原。", | ||
| "CLI_PASSWORD": "CLI 金鑰", |
There was a problem hiding this comment.
I’m a bit confused about the meaning of “金鑰.” Can it refer to “password,” “secret,” or “key”?
There was a problem hiding this comment.
Yeah, they often overlap depending on context. I'd prefer more apparent distinctions, but that's hard in practice.
| "NO_VUL": "我們找不到任何弱點", | ||
| "INVALID_VALUE": "The CVSS3 score should range between 0 and 10", | ||
| "PAGE_TITLE_TOOLTIP": "The comprehensive artifact count comprises the cumulative total of individual artifacts, including artifact accessories, as well as child artifacts associated with the image index and CNAB artifacts" | ||
| "NO_VUL": "找不到任何弱點", |
There was a problem hiding this comment.
Good update. We should avoid having any subject words in the UI components.
Signed-off-by: Peter Dave Hello <hsu@peterdavehello.org>
d809efa to
df91302
Compare
Signed-off-by: Peter Dave Hello <hsu@peterdavehello.org>
Comprehensive Summary of your change
Update and improve zh-TW Traditional Chinese locale
Please indicate you've done the following:
Refs: #18608 #19161