From: Rob Landley <rob@landley.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "dave young" <hidave.darkstar@gmail.com>,
"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 14:53:59 -0400 [thread overview]
Message-ID: <200706221454.03926.rob@landley.net> (raw)
In-Reply-To: <20070622102123.49182855@the-village.bc.nu>
On Friday 22 June 2007 05:21:23 Alan Cox wrote:
> > 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
>
> The majority of the world population do not speak English. There are
> existing contributors do not speak English (and I'm not being funny about
> the USSA here) - you don't notice because they have a team member who
> speaks passable English.
Ok. Cool. If this is not a problem, that's good to know.
> There are also entire non-English sites around things like Linux that
> monoglot English speakers generally don't notice exist.
I'm aware of this.
> > 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
>
> For the kernel I would follow the kernel tree so that its always
>
> /[languagecode]/Documentation/...
That PS was about putting up a kernel doc web page, not about the existing
kernel Documentation tree.
The existing Documentation tree has, at the top level, coding style
guidelines, files documenting the kernel community, a file documenting the
Amiga "zorro" bus, a half-dozen files about old multiport serial cards,
documentation about several different types of locking, a penguin graphic
from 1996, your documentation on the tty layer, a document on how to
configure BINFMT_MISC to autorun .NET files with mono, and zillions of other
random unrelated topics that are sorted based on where random passerby put
things down last.
I sent a couple patches to shuffle stuff around in there but it got lost on
the noise. More to the point, an HTML index can hotlink but text files have
a harder time doing that, so if I'm making an HTML index it's probably best
to link to the text files but not attempt to navigate with them.
Rob
--
"One of my most productive days was throwing away 1000 lines of code."
- Ken Thompson.
next prev parent reply other threads:[~2007-06-22 18:54 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
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 [this message]
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=200706221454.03926.rob@landley.net \
--to=rob@landley.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bryan.wu@analog.com \
--cc=chenqi@beyondsoft.com \
--cc=gregkh@suse.de \
--cc=hidave.darkstar@gmail.com \
--cc=leoli@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--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
Powered by JetHome