From: Rob Landley <rob@landley.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Li Yang-r58472 <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>
Subject: Re: [PATCH] Chinese translation of Documentation/HOWTO
Date: Fri, 22 Jun 2007 15:11:45 -0400 [thread overview]
Message-ID: <200706221511.46775.rob@landley.net> (raw)
In-Reply-To: <alpine.LFD.0.98.0706220950110.3593@woody.linux-foundation.org>
On Friday 22 June 2007 13:02:26 Linus Torvalds wrote:
> In fact, I suspect pretty much any documentation (whether technical or
> about processes and/or style) makes sense to have translated if the energy
> and ability to do that exists. I suspect the "policies and processes"
> kinds of docs make _more_ sense to translate initially, simply because
> they are approachable on their own - but I certainly would never
> discourage anybody from translating anything at all.
>
> That said, I don't think that merging the result into the standard kernel
> makes sense - like it or not, right now English ends up being required
> to be part of actually getting things into the "standard" kernel, and as
> such, at _some_ point there has to be a connection point that switches
> over to English, and trying to make the translations be an in-kernel thing
> is thus kind of pointless.
>
> But as part of some "documentation site", it makes 100% sense.
Ok, I've got some documentation site, specifically http://kernel.org/doc (and
I'll be completely redoing it as soon as I've recovered from my recent laptop
crash and OLS).
Send me translations (preferably in HTML format), and I'll put 'em up. (I've
already got the one that started this thread.)
Thanks,
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 19: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
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 [this message]
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=200706221511.46775.rob@landley.net \
--to=rob@landley.net \
--cc=LeoLi@freescale.com \
--cc=bryan.wu@analog.com \
--cc=chenqi@beyondsoft.com \
--cc=gregkh@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).