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

Rebased & reviewed translations for zh_CN & zh_TW #136

Closed
wants to merge 9 commits into from

Conversation

Artoria2e5
Copy link

@Artoria2e5 Artoria2e5 commented Aug 24, 2016

all:

  • update to the latest en.po (msgmerge)
  • whitespace and punctuation

zh_CN:

  • fix mistranslations on description keys

msgid "How do I <i>use</i> pool.ntp.org?"
msgstr "我如何能<i>使用</i> pool.ntp.org?"
msgid "How do I <i>use</i> pool.ntp.org?"
msgstr "如何<u>使用</u> pool.ntp.org"
Copy link
Author

@Artoria2e5 Artoria2e5 Aug 24, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Chinese is generally unsuitable for italics (often computer-generated oblique instead), therefore using underline for emphasis instead.

@Artoria2e5
Copy link
Author

Now attempting to add #106 to my bundle...

@Artoria2e5 Artoria2e5 changed the title i18n/zh*: update and various fixes Rebased & reviewed translations for zh_CN & zh_TW Aug 24, 2016
@abh
Copy link
Owner

abh commented Aug 26, 2016

This is great, thank you!

Because I didn't know what I was doing at the time, the system only supports two letter language codes. Do you think it'd be okay to call the Simplified Chinese version 'zh' and the Traditional Chinese version 'tw'? Or is there something else that'd be more appropriate?

@Artoria2e5
Copy link
Author

Sounds acceptable.

@biergaizi
Copy link

Wow, I just wanted to fork and start the translation, but soon realized my colleagues has finished already, I don't even know! Any progress for merging? I think a Chinese homepage is important for telling the people that they can contribute their servers.

@biergaizi
Copy link

By the way, we need to merge it as soon as possible, otherwise more and more duplicate works pop up (3 of them for now).

@Artoria2e5
Copy link
Author

but soon realized my colleagues has finished already

In fact I realized @m13253 has done this long ago after finishing the PO...

@Artoria2e5
Copy link
Author

Artoria2e5 commented Oct 1, 2016

Merge from #138 docs: keep homepage/intro and use (by 13253), replace the rest. Review aggressively. Just act like a Borg.

Artoria2e5 and others added 7 commits October 1, 2016 17:00
all:
  - update to the latest en.po (msgmerge)
  - whitespace and punctuation
zh_CN:
  - fix mistranslations on description keys
@Artoria2e5: In this rebased commit, I selectively used many of
@m13253's strings.
@m13253's translations seems to be of better quality, so I combined
them with @wustudent's translations strings and did some polishing.
加入计划的服务器不能把 <tt>pool.ntp.org</tt> 用作上游服务器,但是需要手动设置一些 <a href="http://support.ntp.org/bin/view/Servers/StratumTwoTimeServers">好的服务器</a> (这些服务器
<b>可以</b> 从池中选取。 重要的是它们是被静态选择的,而不是在每台服务器重启后动态分配的。 这将有助于提供令人质量的服务。)
注意,对于你的服务器是1层或者是2层(stratum 1 or 2)的我们没有要求 - 正如这个项目是最大程度上分散负载,对于为什么
3层或者是4层的服务器(stratum 3 or 4)不应该加入,我想我们不必解释。
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

woah, never noticed "why 3/4 should not join"

@abh abh deleted the branch abh:master August 26, 2021 01:15
@abh abh closed this Aug 26, 2021
@Artoria2e5
Copy link
Author

That’s… a surprising side effect of branch rename.

@abh
Copy link
Owner

abh commented Aug 26, 2021

@Artoria2e5 yikes, indeed!! Ugh.

@Artoria2e5
Copy link
Author

Artoria2e5 commented Sep 13, 2021

I will pick this back up when I have time. (Was randomly browsing stuff when I saw into the Swift people serving a branch switch notice. I guess that's the way if you have more repos to migrate.)

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.

5 participants