public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@gmail.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: Denis Vlasenko <vda.linux@googlemail.com>,
	Sam Ravnborg <sam@ravnborg.org>, Greg KH <gregkh@suse.de>,
	Jesper Juhl <jesper.juhl@gmail.com>,
	Tsugikazu Shibata <tshibata@ab.jp.nec.com>,
	linux-kernel@vger.kernel.org, m-ikeda@ds.jp.nec.com
Subject: Re: kconfig .po files in kernel tree? [Was: Documentation/HOWTO	translated into Japanese]
Date: Mon, 11 Jun 2007 11:28:27 +0200	[thread overview]
Message-ID: <466D15BB.2080705@gmail.com> (raw)
In-Reply-To: <20070611001434.GD3588@stusta.de>

On 06/11/2007 02:14 AM, Adrian Bunk wrote:

> On Mon, Jun 11, 2007 at 01:59:00AM +0200, Denis Vlasenko wrote:

>> I agree. i18n efforts won't help one iota because people just have
>> to know English in order to participate in l-k development.
>> They should be able to read _and_ reply_ to lkml posts,
>> and read and understnd code _and_ comments_.
>> ...
> 
> Kconfig is different since the target audience and the majority of users 
> are not kernel developers.

Well, hardly. The percentages quoted vary wildly with the point someone is 
trying to make but "user users" are expected to just use whatever their 
distribution provided them with meaning the Kconfig target audience is 
developers and "power users". Enough of the latter around certainly but I 
have no indication whatsoever that a significant number of them is lost in 
the water without Kconfig translations either.

Internationalization is not very useful, has great potential to introduce 
even more chronically bit-rotting content and is finally counter-productive 
  in maintaining a non-forking single community, at least in so far as it is 
today. One should spit on internationalization.

Rene.

  reply	other threads:[~2007-06-11  9:31 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-10 11:48 [RFD] Documentation/HOWTO translated into Japanese Tsugikazu Shibata
2007-06-10 12:03 ` [RFD] Documentation/stable_api_nonsense.txt " IKEDA Munehiro
2007-06-10 12:23   ` Jan Engelhardt
2007-06-10 17:00   ` Alistair John Strachan
2007-06-11  1:33     ` IKEDA Munehiro
2007-06-10 12:24 ` [RFD] Documentation/HOWTO " Jesper Juhl
2007-06-10 12:29   ` Jan Engelhardt
2007-06-10 14:25   ` IKEDA Munehiro
2007-06-10 16:22   ` Greg KH
2007-06-10 16:34     ` Tsugikazu Shibata
2007-06-10 16:46       ` Jan Engelhardt
2007-06-11  0:25         ` Adrian Bunk
2007-06-10 17:52     ` kconfig .po files in kernel tree? [Was: Documentation/HOWTO translated into Japanese] Sam Ravnborg
2007-06-10 18:35       ` Jan Engelhardt
2007-06-10 19:04         ` Sam Ravnborg
2007-06-10 22:13         ` Matt Mackall
2007-06-10 18:58       ` Rene Herman
2007-06-10 21:13         ` Rene Herman
2007-06-10 23:59         ` Denis Vlasenko
2007-06-11  0:14           ` Adrian Bunk
2007-06-11  9:28             ` Rene Herman [this message]
2007-06-11  0:56           ` Paul Mundt
2007-06-11  7:46             ` Denis Vlasenko
2007-06-11  8:34               ` Paul Mundt
2007-06-11  9:08             ` Rene Herman
2007-06-10 19:41       ` Diego Calleja
2007-06-11  0:21         ` Adrian Bunk
2007-06-11  0:29       ` Adrian Bunk
2007-06-11  6:02       ` Greg KH
2007-06-10 17:56     ` [RFD] Documentation/HOWTO translated into Japanese Matthias Schniedermeyer
2007-06-11  6:07       ` Greg KH
2007-06-11  7:24         ` Matthias Schniedermeyer
2007-06-11 13:43         ` Matt Mackall
2007-06-11 17:38           ` Tony Luck
2007-06-15  0:29             ` Kyle Moffett
2007-06-12  0:55         ` Tsugikazu Shibata
2007-06-12  1:07           ` IKEDA Munehiro
2007-06-12  7:44           ` Junio C Hamano
2007-06-12  8:44             ` IKEDA Munehiro
2007-07-03 21:32               ` Rob Landley
2007-06-13 14:18         ` Pavel Machek
2007-06-13 20:37           ` Greg KH
2007-06-13 20:43             ` Pavel Machek
2007-06-10 22:08 ` Matt Mackall
2007-06-11  2:55 ` KAMEZAWA Hiroyuki
2007-06-11  6:09   ` Greg KH
2007-06-11  8:45     ` Hiro Yoshioka
2007-06-11 10:21   ` Qi Yong
2007-06-11 10:46     ` KAMEZAWA Hiroyuki
2007-06-11 11:16       ` Rene Herman
2007-06-11 11:28         ` KAMEZAWA Hiroyuki
2007-06-11 11:34           ` Rene Herman

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=466D15BB.2080705@gmail.com \
    --to=rene.herman@gmail.com \
    --cc=bunk@stusta.de \
    --cc=gregkh@suse.de \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m-ikeda@ds.jp.nec.com \
    --cc=sam@ravnborg.org \
    --cc=tshibata@ab.jp.nec.com \
    --cc=vda.linux@googlemail.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