Repository navigation
l10n: revise and update zh_TW translation - #2477
Open
kisaragi-hiu wants to merge 1 commit into
Open
kisaragi-hiu wants to merge 1 commit into
kisaragi-hiu wants to merge 1 commit into
Conversation
Translate: - Address Bar Using 網址列 for Address Bar because that's what Firefox zh_TW uses. - Sticky ancestor tab strings "sticky" as in "if it would scroll off keep it at the top instead" is not in zh (or even really anywhere except English), so I had to just expand out the definition (固定於上方顯示, "keep it displayed on top"). - Everything else Revise: - Use '不切換' for settings.scroll_through_tabs_none. A single 不 is very unnatural. This is like settings.switch_panel_after_switching_tab_no, where it's necessary to repeat what action we don't do to make it grammatical. - Fix 快照 being used as a counting word (settings.snap_limit_snap) In the snapshot limit, "snapshots" is used for a count of snapshots (like "10 snapshots"), but "10 快照" is not valid zh_TW or zh_CN. I chose to use 快照數 instead of ...個快照 since this string is also doubling as an option for what limit mode to use. "個快照" does not sound like a limit mode. - Use "Proxy 設定", not just 代理, for Proxy The issue with 代理 alone is that it is ambiguous with Agent (代理程式 in full, often also shortened to 代理). (I'm not sure if this issue exists in zh_CN, which is why I only added a zh_TW translation.) Firefox zh_TW uses both 代理伺服器 and "Proxy", with "Proxy" being the one that's used more primarily (like "手動設定 Proxy" or "使用系統 Proxy"), so I chose Proxy over 代理伺服器. - zh_TW 禁用 means Prohibit, not Disable. Disable is 停用 in zh_TW - Fix 字符串 in "substring or /RegExp/" 字符串 is not in zh_TW. It's as jarring in zh_TW as saying a lift instead of an elevator in en_US. I localized the quotes to hopefully make it more clear they don't go into the rule (double quotes are literal in the field, "github" with quotes matches URLs that also contain the quotes). - 當前 -> 目前 The zh_TW word for "current" is 目前; "當前" is as jarring as "colour" would be in en_US. Because 非目前的 is not a word, I replaced it with the next best thing, "非作用中的". - 折疊 -> 摺疊 zh_TW has 3 valid translations for "collapse" (collapsing a previously expanded thing): 收起, 折疊, and 摺疊. 折疊 is fine, but Firefox zh_TW mainly uses 摺疊. Searching on firefox-l10n: 摺疊: 19 matches https://github.com/search?q=repo%3Amozilla-l10n%2Ffirefox-l10n%20path%3A%2F%5Ezh-TW%2F%20%E6%91%BA%E7%96%8A&type=code 折疊: 2 matches, both seem like consistency mistakes 收起: 3 matches, which are from accessibility properties for 3 platforms so it's really more like 1 match.
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
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.
The main thing is addressing vocabulary that are unnatural in zh_TW (eg. 當前 is as zh_CN as color is en_US), but I also made some revisions for grammar and translated everything that hasn't been translated yet.
Translate
Address Bar
Using 網址列 for Address Bar because that's what Firefox zh_TW uses.
Sticky ancestor tab strings
"sticky" as in "if it would scroll off keep it at the top instead" is not in zh (or even really anywhere except English), so I had to just expand out the definition (固定於上方顯示, "keep it displayed on top").
Everything else
Revise
Use '不切換' for settings.scroll_through_tabs_none.
A single 不 is very unnatural. This is like settings.switch_panel_after_switching_tab_no, where it's necessary to repeat what action we don't do to make it grammatical.
Fix 快照 being used as a counting word (settings.snap_limit_snap)
In the snapshot limit, "snapshots" is used for a count of snapshots (like "10 snapshots"), but "10 快照" is not valid zh_TW or zh_CN.
I chose to use 快照數 instead of ...個快照 since this string is also doubling as an option for what limit mode to use. "個快照" does not sound like a limit mode.
Use "Proxy 設定", not just 代理, for Proxy
The issue with 代理 alone is that it is ambiguous with Agent (代理程式 in full, often also shortened to 代理). (I'm not sure if this issue exists in zh_CN, which is why I only added a zh_TW translation.)
Firefox zh_TW uses both 代理伺服器 and "Proxy", with "Proxy" being the one that's used more primarily (like "手動設定 Proxy" or "使用系統 Proxy"), so I chose Proxy over 代理伺服器.
zh_TW 禁用 means Prohibit, not Disable. Disable is 停用 in zh_TW
Fix 字符串 in "substring or /RegExp/"
字符串 is not in zh_TW. It's as jarring in zh_TW as saying a lift instead of an elevator in en_US.
I localized the quotes to hopefully make it more clear they don't go into the rule (double quotes are literal in the field, "github" with quotes matches URLs that also contain the quotes).
當前 -> 目前
The zh_TW word for "current" is 目前; "當前" is as jarring as "colour" would be in en_US.
Because 非目前的 is not a word, I replaced it with the next best thing, "非作用中的".
折疊 -> 摺疊
zh_TW has 3 valid translations for "collapse" (collapsing a previously expanded thing): 收起, 折疊, and 摺疊.
折疊 is fine, but Firefox zh_TW mainly uses 摺疊.
Searching on firefox-l10n: 摺疊 has 19 matches; 折疊 has 2 matches, both seem like consistency mistakes; 收起 has 3 matches but they are from accessibility properties for 3 platforms so it's really more like 1 match.