Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

po: fully translate and revise zh_TW #155

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

kisaragi-hiu
Copy link

@kisaragi-hiu kisaragi-hiu commented Aug 29, 2024

Although there is the old Transifex page, since CONTRIBUTE now says translation is also submitted via GitHub, I've opted to submit this PR.

  • Use 裝置 for devices. 設備 is zh_CN; in zh_TW 設備 stands for "equipment" not "device".
  • Reflect source text progressive tense ("starting", "calibrating" etc.) in translated text more
  • Use 封裝 for "cpu package", which is a better term for this context
  • Use 合適/不合適 for GOOD/BAD as 好/壞 reads somewhat unnatural
  • Fix "[Feature] for [Device]" being consistently mistranslated as nonsense equivalent to "[Feature] at [Device]"
overview idle stats frequency stats
1 2 3
device stats tunables wakeup
4 5 6

There are some misalignments in the stats pages, probably because somewhere in the code assumed that a character would always be 1-char wide (Han characters are 2-chars wide). I was able to work around it in the overview page by adding some extra spaces in the translated text, but this doesn't work for other tabs, so those misalignments are beyond what I can fix with translation strings.

- Use 裝置 for devices. 設備 is zh_CN; in zh_TW 設備 stands for
  "equipment" not "device".
- Reflect source text progressive tense ("starting", "calibrating" etc.)
  in translated text more
- Use 封裝 for "cpu package", which is a better term for this context
- Use 合適/不合適 for GOOD/BAD as 好/壞 reads somewhat unnatural
- Fix "[Feature] for [Device]" being consistently mistranslated as
  nonsense equivalent to "[Feature] at [Device]"
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.

1 participant