mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "dave young" <hidave.darkstar@gmail.com>
To: "Rob Landley" <rob@landley.net>
Cc: "Li Yang" <leoli@freescale.com>,
	gregkh@suse.de, linux-kernel@vger.kernel.org,
	xiyou.wangcong@gmail.com, 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 06:07:57 +0000	[thread overview]
Message-ID: <a8e1da0706212307l7bdebbabl72478d1c734b60bd@mail.gmail.com> (raw)
In-Reply-To: <200706220133.19496.rob@landley.net>

Hi,
2007/6/22, Rob Landley <rob@landley.net>:
> On Thursday 21 June 2007 23:23:54 dave young wrote:
> > Hi,
> >
> > 2007/6/22, Rob Landley <rob@landley.net>:
> > > 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.
> >
> > I think it's not a good idea to merge translations into kernel.
> >
> > > 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.)
> >
> > Yes, I agree with you, and there's so many other languages, It's
> > better for someone to  create a standalone kdoc translation project
> > than to merge them into kernel.
>
> I wasn't suggesting merging them into the kernel.

I'm misunderstanded.

I means:
Yes, I agree with you.
There's so many other languages, It's better for someone to  create a
standalone kdoc translation project than to merge them into kernel.


> I'm doing a web page to put together html versions of lots of kernel
> documentation in a place Google can find it.  Peter Anvin was kind enough to
> give me http://kernel.org/doc for this.  It would not be technically
> difficult for this web page to host translated versions of this
> documentation.
>
> The question is, do the kernel developers want to encourage people who don't
> speak English to mess with the kernel, any more than they want to encourage
> kernel developers who don't know C?  Is kernel documentation in Chinese a
> better idea than a repository of kernel patches in C++?  (Either way, work
> resulting from this is much less likely than normal to be merged into the
> kernel.)
>
It's another issue.

Someone don't speak english , but it don't means they haven't
programming skilles. As long as one can help to promote the kernel
development  he is welcomed.

> I don't know if this is a valid concern or not.  That's why I'm asking.
>
> Rob
>
> P.S.  The hardest part of putting together a kernel documentation web page is
> actually indexing it coherently.  It's not very useful to just dump together
> huge amounts of stuff from Documentation and make htmldocs and linux weekly
> news' kernel index and kerneltrap and kernel traffic and the kernelnewbies
> wiki and kernelplanet and man-pages-2.57 coverted to html with doclifter...
> Ahem.  I finally figured out how I wanted it indexed, made a skeleton to hang
> stuff on, and my laptop blew up.  Grrr.  Mostly recovered, but now OLS is
> bearing down on me and I still haven't got a new laptop...
>
> Don't mind me, I'll catch up.
> --
> "One of my most productive days was throwing away 1000 lines of code."
>   - Ken Thompson.
>
Regards
dave

  reply	other threads:[~2007-06-22  6:08 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
     [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=a8e1da0706212307l7bdebbabl72478d1c734b60bd@mail.gmail.com \
    --to=hidave.darkstar@gmail.com \
    --cc=bryan.wu@analog.com \
    --cc=chenqi@beyondsoft.com \
    --cc=gregkh@suse.de \
    --cc=leoli@freescale.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob@landley.net \
    --cc=torvalds@linux-foundation.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®