linux-kernel - Re: [PATCH] Chinese translation of Documentation/HOWTO

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200706221445.24353.rob@landley.net>
Date:	Fri, 22 Jun 2007 14:45:22 -0400
From:	Rob Landley <rob@...dley.net>
To:	"dave young" <hidave.darkstar@...il.com>
Cc:	"Li Yang" <leoli@...escale.com>, gregkh@...e.de,
	linux-kernel@...r.kernel.org, xiyou.wangcong@...il.com,
	bryan.wu@...log.com, "TripleX Chung" <xxx.phy@...il.com>,
	"Maggie Chen" <chenqi@...ondsoft.com>,
	torvalds@...ux-foundation.org
Subject: Re: [PATCH] Chinese translation of Documentation/HOWTO

On Friday 22 June 2007 02:07:57 dave young wrote:
> > > 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 agree, but this is just an opinion.  (I see where Greg KH wants to merge it 
into the kernel.)

> > 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 agree that programming talent can exist without the ability to speak 
English.  But will the resulting patches get merged if the developer can't 
communicate with the Linux development community?

I dealt with a programmer on the BusyBox project who only speaks Russian, and 
uses a babelfish variant to translate everything.  This was incredibly 
frustrating: he regularly misunderstood what we were saying, we regularly had 
no idea what he was saying, his attempts at commenting the code were often 
worse than not commeting it at all, and after three years his ability to 
communicate hadn't improved in the slightest.

Possibly we'd need some volunteer translators just for the purpose of merging 
code in languages we'd translated the documentation into?  A "chinese patch 
maintainer" or some such?

Rob
-- 
"One of my most productive days was throwing away 1000 lines of code."
  - Ken Thompson.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/