From: WANG Cong <xiyou.wangcong@gmail.com>
To: Li Yang-r58472 <LeoLi@freescale.com>
Cc: Rob Landley <rob@landley.net>,
gregkh@suse.de, linux-kernel@vger.kernel.org,
bryan.wu@analog.com, TripleX Chung <xxx.phy@gmail.com>,
Maggie Chen <chenqi@beyondsoft.com>,
torvalds@linux-foundation.org
Subject: Re: [PATCH] Chinese translation of Documentation/HOWTO
Date: Fri, 22 Jun 2007 13:12:59 +0800 [thread overview]
Message-ID: <20070622051259.GB2911@localhost.localdomain> (raw)
In-Reply-To: <989B956029373F45A0B8AF0297081890D83001@zch01exm26.fsl.freescale.net>
On Fri, Jun 22, 2007 at 11:58:58AM +0800, Li Yang-r58472 wrote:
>> -----Original Message-----
>> From: Rob Landley [mailto:rob@landley.net]
>> Sent: Friday, June 22, 2007 10:49 AM
>>
>> On Thursday 21 June 2007 10:40:17 Li Yang wrote:
>> > This is a Chinese translated version of Documentation/HOWTO.
>Currently
>> > Chinese involvement in Linux kernel is very low, especially
>comparing to
>> > its largest population base. Language could be the main obstacle.
>Hope
>> > this document will help more Chinese to contribute to Linux kernel.
>>
>> I'm putting together a kernel documentation directory at
>http://kernel.org/doc
>> and I could easily add translations in there. I just don't know if
>this is a
>> good idea.
>>
>> The problem is, the submission of patches happens on the various
>kernel.org
>> mailing lists, which are all in English. Kernel development is done
>in a
>> single common language: English. (If you'd like to argue for it to be
>done
>> in another language, please make the proposal in Linus's native
>Swedish.)
>>
>> Setting aside for the moment version skew and coverage issues when
>translating
>> Documentation, which aren't really serious blocking issues, my
>question is
>> this: If developers aren't fluent enough with English to follow the
>> documentation, how can they follow any of the technical discussions
>necessary
>> to merge their patches back into the mainstream kernel? Doesn't this
>> encourage the creation of patches that can't easily be merged back
>into the
>> kernel?
>
>So as I argued in a previous email, non-native English speakers tend to
>be more confused by the policies and processes. I also don't think it's
>necessary to translate the technical documents. To be a software
>developer, one has to be educated or experienced in technical terms.
>Technical discussion can be done without too much requirement to grammar
>and emotional expressing. The translated document of policies and
>processes will help these people to understand the process better and go
>smoother in the process.
>
Yes, I agree.
Many people from China are trying to contribute to Linux kernel (like me),
a Chinese document which describes and explains the non-technical things
needed by Linux kernel will help them _much_ to join the development soon.
Also, IMO, a translation shows Linux kernel is friendly and open to
people from all over the world.
Regards!
WANG Cong
next prev parent reply other threads:[~2007-06-22 5:11 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 14:40 [PATCH] Chinese translation of Documentation/HOWTO 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 [this message]
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
[not found] <a8e1da0706191858w73a453dfjf28895150af85cfe@mail.gmail.com>
2007-06-20 5:13 ` Li Yang-r58472
2007-06-20 5:22 ` dave young
2007-06-20 5:57 ` Greg KH
-- 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=20070622051259.GB2911@localhost.localdomain \
--to=xiyou.wangcong@gmail.com \
--cc=LeoLi@freescale.com \
--cc=bryan.wu@analog.com \
--cc=chenqi@beyondsoft.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@landley.net \
--cc=torvalds@linux-foundation.org \
--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