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]

Date:	Fri, 22 Jun 2007 12:22:08 +0800
From:	Bryan Wu <bryan.wu@...log.com>
To:	Li Yang-r58472 <LeoLi@...escale.com>
Cc:	Rob Landley <rob@...dley.net>, 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 Fri, 2007-06-22 at 11:58 +0800, Li Yang-r58472 wrote:
> > -----Original Message-----
> > From: Rob Landley [mailto:rob@...dley.net]
> > Sent: Friday, June 22, 2007 10:49 AM
> > 
> > On Thursday 21 June 2007 10:40:17 Li Yang wrote:
> > > This is a Chinese translated version of Documentation/HOWTO.
> Currently
> > > Chinese involvement in Linux kernel is very low, especially
> comparing to
> > > its largest population base.  Language could be the main obstacle.
> Hope
> > > this document will help more Chinese to contribute to Linux kernel.
> > 
> > I'm putting together a kernel documentation directory at
> http://kernel.org/doc
> > and I could easily add translations in there.  I just don't know if
> this is a
> > good idea.
> > 
> > The problem is, the submission of patches happens on the various
> kernel.org
> > mailing lists, which are all in English.  Kernel development is done
> in a
> > single common language: English.  (If you'd like to argue for it to be
> done
> > in another language, please make the proposal in Linus's native
> Swedish.)
> > 
> > Setting aside for the moment version skew and coverage issues when
> translating
> > Documentation, which aren't really serious blocking issues, my
> question is
> > this:  If developers aren't fluent enough with English to follow the
> > documentation, how can they follow any of the technical discussions
> necessary
> > to merge their patches back into the mainstream kernel?  Doesn't this
> > encourage the creation of patches that can't easily be merged back
> into the
> > kernel?
> 
> So as I argued in a previous email, non-native English speakers tend to
> be more confused by the policies and processes.  I also don't think it's
> necessary to translate the technical documents.  To be a software
> developer, one has to be educated or experienced in technical terms.
> Technical discussion can be done without too much requirement to grammar
> and emotional expressing.  The translated document of policies and
> processes will help these people to understand the process better and go
> smoother in the process.
> 
> - Leo

Leo is right. Policies and processes should be clear for all developer
including non-native English speakers, while other technical documents
do not need to be translated.

After I read the translations, I also found something I missed before.

Thanks for the work
- Bryan Wu
-
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/