From: Matthew Wilcox <willy@infradead.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Hu Haowen <src.res@email.cn>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: add traditional Chinese translation for kernel Documentation
Date: Mon, 14 Jun 2021 01:18:04 +0100 [thread overview]
Message-ID: <YMagPMuKYKWDpUj8@casper.infradead.org> (raw)
In-Reply-To: <87wnqxbcjb.fsf@meer.lwn.net>
On Sun, Jun 13, 2021 at 04:55:04PM -0600, Jonathan Corbet wrote:
> Hu Haowen <src.res@email.cn> writes:
> > 在 2021/6/7 下午9:24, Hu Haowen 写道:
> >> Add traditional Chinese translation (zh_TW) for the Linux Kernel
> >> documentation with a series of translated files.
> >
> > Is this patch applied? I have another amount of changes on this, so
> > please handle it as soon as possible.
>
> I have been away from the keyboard for the last week, and haven't had a
> chance to look at it yet. That will happen soon. Meanwhile, please be
> patient; it has not yet even been a week since you posted this work.
>
> Taking a quick look, there are a couple of things you can do:
>
> - We have a Chinese translation, now you are creating a different one.
> Please explain why that is needed?
I think this explains it:
https://stackoverflow.com/questions/4892372/language-codes-for-simplified-chinese-and-traditional-chinese
So if we would consider having (eg) fr_FR and fr_CA, it's reasonable to
have both zh_CN and zh_TW. No, I'm not volunteering to produce en_GB
(or is that en_UK?)
next prev parent reply other threads:[~2021-06-14 0:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 13:24 [PATCH] docs: add traditional Chinese translation for kernel Documentation Hu Haowen
2021-06-13 6:08 ` Hu Haowen
2021-06-13 22:55 ` Jonathan Corbet
2021-06-14 0:18 ` Matthew Wilcox [this message]
2021-06-17 6:38 ` Hu Haowen
2021-06-17 19:20 ` Jonathan Corbet
2021-06-18 1:13 ` Hu Haowen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YMagPMuKYKWDpUj8@casper.infradead.org \
--to=willy@infradead.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=src.res@email.cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox