From: WANG Cong <xiyou.wangcong@gmail.com>
To: Oleg Verych <olecom@flower.upol.cz>
Cc: WANG Cong <xiyou.wangcong@gmail.com>,
Adrian Bunk <bunk@kernel.org>, Sam Ravnborg <sam@ravnborg.org>,
linux-kbuild <linux-kbuild@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: translations (Re: Kbuild update)
Date: Tue, 15 Jan 2008 09:33:47 +0800 [thread overview]
Message-ID: <20080115013347.GA3112@hacking> (raw)
In-Reply-To: <20080109135024.GD24008@flower.upol.cz>
>
>ftp://flower.upol.cz/upload/Configure.help
>
>OK, please, take a look at stuff, Korean guys did 5-6 years ago. One
>particular ARM port (S3C2410X) along with an ARM bootloader (vivi) was
>done. Yet for some reason official Linux port has another developers, and,
>it seems, it was done some time (~1-2 years) later.
I glanced at the page. I don't know Korean, but it seems OK.
What do you mean by saying this? I can't catch your points.
>> I abosutely agree that we should focus on the exsiting bugs of Linux,
>> but like Greg's inclusion of some kernel doc translations, this kind
>> of work is really helpful to attract some kernel newbies from none
>> English-speaking countries. Even we can't make offical efforts,
>> the civil work, like TLKTP, is still worthy.
>...
>
>> Believe me, I am leading a local LUG in my college and I found that one
>> _big_ reason that why the newbies are afraid of Linux kernel is
>> English, instead of the C tricks or low-level programming.
>
>IMHO, there is so much stuff done, that any brilliant C or whatever-asm
>coder *have* to study at least something of it. And, in order to do a
>valuable contribution, one must know the work-flow, people *and* English.
>This is usually done by reading mailing list *and* archives for quite
>some time. This takes time, this takes effort, but this also have huge
>impact on intelligence and culture of the `coders'.
>
>Do you ever have a question about why History exists and is studied on
>all levels of education? Same with programming. Without
>history-via-English, one have no strong roots, thus base for grow and
>flower.
I think you've overstated.
Translation does _not_ mean avoiding learning English. I agree with
what you said above about English. But just as you said, it needs
_time_ and translation *is* a good way to help this. I, myself,
began to learn computer English by reading the translations of some
famous English textbooks, and then reading the original ones.
>OTOH, Internet has so much noise and crap all over the place, that
>information is very hard to find. It takes much time to sort and see it.
>Yet, providing noise generating, like in-tree translations, seems, is a
>very easy way around (not taking maintaining in account).
Translations can be put in .po files.
Thanks.
Cong
prev parent reply other threads:[~2008-01-15 1:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-03 21:32 Kbuild update Sam Ravnborg
2008-01-03 21:46 ` Josh Boyer
2008-01-03 22:33 ` Jan Engelhardt
2008-01-04 19:43 ` Sam Ravnborg
2008-01-04 20:09 ` Jan Engelhardt
2008-01-04 13:23 ` WANG Cong
2008-01-04 14:39 ` Sam Ravnborg
2008-01-04 14:39 ` Sam Ravnborg
2008-01-05 5:48 ` Adrian Bunk
2008-01-06 14:26 ` WANG Cong
2008-01-06 15:07 ` Adrian Bunk
2008-01-06 15:45 ` Sam Ravnborg
2008-01-09 2:32 ` WANG Cong
2008-01-09 5:18 ` Sam Ravnborg
2008-01-09 2:28 ` WANG Cong
2008-01-06 21:41 ` translations (Re: Kbuild update) Oleg Verych
2008-01-06 22:03 ` Sam Ravnborg
2008-01-09 2:22 ` WANG Cong
2008-01-09 13:50 ` Oleg Verych
2008-01-15 1:33 ` WANG Cong [this message]
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=20080115013347.GA3112@hacking \
--to=xiyou.wangcong@gmail.com \
--cc=bunk@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olecom@flower.upol.cz \
--cc=sam@ravnborg.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.