pages.zh/osx: add Chinese translation

[wizarot]

• The page (if new), does not already exist in the repo.
• The page is in the correct platform directory (common/, linux/, etc.)
• The page has 8 or fewer examples.
• The PR title conforms to the recommended templates.
• The page follows the content guidelines.

[CLAassistant]

All committers have signed the CLA.

[agnivade]

@wizarot - Thank you for the contribution !

Kindly rename your commit msgs in the format of ": add Chinese translation". And also please remove the merge commit from between so that we can rebase all the commits to master.

Feel free to ask @mebeim for any sort of git help 😝

[wizarot]

@wizarot - Thank you for the contribution !

Kindly rename your commit msgs in the format of ": add Chinese translation". And also please remove the merge commit from between so that we can rebase all the commits to master.

Feel free to ask @mebeim for any sort of git help 😝

@agnivade
I revised it. Is that OK?

[agnivade]

It's not actually. Sorry if I was not able to explain. I want each page translation to have its own commit. And there should not be any merge commit in the branch.

What you have currently is also "okay", but we prefer to have a separate commit for each page to keep things clean.

[sbrl]

Hrm. Did you mean to translate this page? It looks like English to me.

[wizarot]

Remove it !

[wizarot]

Hi! I changed each page translation to its own commit.
@agnivade

[agnivade]

The commits look good. /cc @HugueLiu

[sbrl]

Thanks, @wizarot!

[HugueLiu]

The contents in {{}} should also be translated. @wizarot

[mebeim]

@HugueLiu oh you're right, we totally missed that.

[urbalazs]

Hello @wizarot and others,
IMHO creation of translated pages manually is waste of time now. I have a pull request with a proposal for translation workflow. I suggest to move your translations to a .po file in i18n folder (not exists yet) called i18n/tldr.zh.po and let generate translated pages with my script located in #2793. See this pull request for more details. You can find a .pot file in the mentioned PR.

With this workflow:

• translated pages can be easy maintainable
• translators will be notified about string changes in the source
• can be generate more output (PDF, EPUB, etc.) if needed

[agnivade]

Yes, it may require extra work to move translations to a .po file. But since the author already has put effort in submitting a PR, I think that should be respected. We can always move to the po4a workflow when it's ready, but until then, I don't see a reason to block all translations.

[urbalazs]

I can help to move existing translations to .po files, if the final decision will be made to use .po for translations. There are some command line tool for this and I have experiences about its usage.

[agnivade]

That's great @urbalazs ! Thanks for helping us out with this. The final decision is indeed to use .po files. But since this is a new workflow, one of us need to own and understand it. @mebeim has graciously offered to lead this, but he needs some time. Let us continue with the existing workflow until then.

[wizarot]

I translated the contents in {{}} . @HugueLiu

[sbrl]

Thanks, @wizarot 😺

[mebeim]

Nice