LKML Archive on
help / color / mirror / Atom feed
From: Oleg Verych <>
To: WANG Cong <>
Cc: Adrian Bunk <>, Sam Ravnborg <>,
	linux-kbuild <>,
	LKML <>
Subject: Re: translations (Re: Kbuild update)
Date: Wed, 9 Jan 2008 14:50:24 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20080109022208.GD2480@hacking>

@ Wed, Jan 09, 2008 at 10:22:08AM +0800, WANG Cong wrote:
> >"I will use ...
> >
> >... for making translations..."
> >
> >?
> >
> >In case if people will help Google to have better quality of translation,
> >that will be better generally for much bigger number of *people*,
> >especially in China, isn't it?
> Perhaps yes.
> But at least now, that kind of translation still sucks. It can
> satisfy me.
> >
> >Making any official world-domination/new-world-order projects with
> >Linux will not help IMHO. Very fast code flow and almost no up to date
> >documentation is still relevant and google search + email archives
> >are not going to be obsolete in the near future.
> >
> >Also, future of the linux codebase with Chinese comments in C or in
> >ASM is kind of wired nightmare. Those, who cannot read actual source
> >code (i.e. C) will not go too far.
> >
> >So, translation guys, maybe you will stop making noise and will start
> >to make e.g. less buggy Linux? Greg KH have much more stuff to care,
> >than some translations IMHO.
> I never say to translate C comments. What we want to translate is the
> strings in Kconfig.

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 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

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).

  reply	other threads:[~2008-01-09 13:33 UTC|newest]

Thread overview: 19+ 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-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 [this message]
2008-01-15  1:33               ` WANG Cong

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* 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).