From: "dave young" <hidave.darkstar@gmail.com>
To: "Li Yang-r58472" <LeoLi@freescale.com>
Cc: "WANG Cong" <xiyou.wangcong@gmail.com>,
linux-kernel@vger.kernel.org, gregkh@suse.de,
"TripleX Chung" <xxx.phy@gmail.com>,
"Maggie Chen" <chenqi@beyondsoft.com>,
"Tejun Heo" <htejun@gmail.com>,
"Fengguang Wu" <fengguang.wu@gmail.com>,
"Chen Li-jun" <cljun@xiyou.edu.cn>
Subject: Re: [PATCH] Chinese translation of Documentation/HOWTO
Date: Wed, 20 Jun 2007 05:22:49 +0000 [thread overview]
Message-ID: <a8e1da0706192222h1a47a103y38ea2b41b83ceb35@mail.gmail.com> (raw)
In-Reply-To: <989B956029373F45A0B8AF0297081890D82DF1@zch01exm26.fsl.freescale.net>
Hi,
2007/6/20, Li Yang-r58472 <LeoLi@freescale.com>:
> > -----Original Message-----
> > From: dave young [mailto:hidave.darkstar@gmail.com]
> > Sent: Wednesday, June 20, 2007 9:58 AM
> > To: WANG Cong
> > Cc: Li Yang-r58472; linux-kernel@vger.kernel.org; gregkh@suse.de;
> TripleX Chung;
> > Maggie Chen; Tejun Heo; Fengguang Wu; Chen Li-jun
> > Subject: Re: [PATCH] Chinese translation of Documentation/HOWTO
> >
> > Hi,
> > IMHO, it is not very suitable for translations merging into kernel.
> >
> > first, It's impossible to be 100% accurate.
>
> It can be accurate by meaning. And it can be improved.
>
> > second, two or more language need to be synced with english one, it's
> > a problem in the long run.
>
> This can be done through good maintenance. I don't think it's harder
> than maintaining the code in kernel source tree.
Yes, but the documents updating are always late than the sources.
In my personal opinion, Of course chinese translaton is a valuable
work, But I don't like huge kernel source with tuns of translations,
english only is always better choice.
Anyway thanks for the work :)
Regards
dave
next prev parent reply other threads:[~2007-06-20 5:22 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a8e1da0706191858w73a453dfjf28895150af85cfe@mail.gmail.com>
2007-06-20 5:13 ` Li Yang-r58472
2007-06-20 5:22 ` dave young [this message]
2007-06-20 5:57 ` Greg KH
2007-06-21 14:40 Li Yang
2007-06-21 15:18 ` WANG Cong
2007-06-21 15:29 ` Eugene Teo
2007-06-21 16:23 ` Bryan Wu
2007-06-22 2:48 ` Rob Landley
2007-06-22 3:23 ` dave young
2007-06-22 5:33 ` Rob Landley
2007-06-22 6:07 ` dave young
2007-06-22 18:45 ` Rob Landley
2007-06-22 6:09 ` Li Yang-r58472
2007-06-22 9:21 ` Alan Cox
2007-06-22 18:53 ` Rob Landley
2007-06-22 3:58 ` Li Yang-r58472
2007-06-22 4:22 ` Bryan Wu
2007-06-22 5:12 ` WANG Cong
2007-06-22 17:02 ` Linus Torvalds
2007-06-22 17:16 ` Tomas Neme
2007-06-22 18:39 ` TripleX
2007-06-22 18:58 ` Li, Tong N
2007-06-22 21:00 ` Rob Landley
2007-06-22 19:11 ` Rob Landley
2007-06-23 4:53 ` WANG Cong
2007-06-28 17:53 ` Pavel Machek
2007-06-29 18:22 ` Rob Landley
2007-06-22 5:29 ` Rob Landley
-- strict thread matches above, loose matches on Subject: below --
2007-06-19 14:21 Li Yang
2007-06-19 15:26 ` Li Yang-r58472
2007-06-19 15:31 ` Greg KH
2007-06-17 19:19 ` Pavel Machek
2007-06-24 16:34 ` Alan Cox
2007-06-24 16:43 ` Rene Herman
2007-06-19 15:36 ` WANG Cong
2007-06-19 16:14 ` Li Yang-r58472
2007-06-20 5:09 ` WANG Cong
2007-06-20 2:52 ` Bryan Wu
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=a8e1da0706192222h1a47a103y38ea2b41b83ceb35@mail.gmail.com \
--to=hidave.darkstar@gmail.com \
--cc=LeoLi@freescale.com \
--cc=chenqi@beyondsoft.com \
--cc=cljun@xiyou.edu.cn \
--cc=fengguang.wu@gmail.com \
--cc=gregkh@suse.de \
--cc=htejun@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xiyou.wangcong@gmail.com \
--cc=xxx.phy@gmail.com \
/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
all inboxes | Powered by JetHome®