public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthias Schniedermeyer <ms@citd.de>
To: Greg KH <gregkh@suse.de>
Cc: 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: [RFD] Documentation/HOWTO translated into Japanese
Date: Sun, 10 Jun 2007 19:56:52 +0200	[thread overview]
Message-ID: <466C3B64.4070806@citd.de> (raw)
In-Reply-To: <20070610162221.GA12830@suse.de>

Greg KH wrote:
> On Sun, Jun 10, 2007 at 02:24:51PM +0200, Jesper Juhl wrote:
>>  Since the common language of most kernel contributors is english I
>>  personally feel that we should stick to just that one language in the
>>  tree and then perhaps keep translations on a website somewhere. So the
>>  authoritative docs stay in the tree, in english, so that as many
>>  contributors as possible can read and update them. It would then be a
>>  seperate project to generate translations and keep them updated
>>  according to what's in the tree.  Perhaps we could get the kernel.org
>>  people to create an official space for that and then place a pointer
>>  to that site in Documentation/ somewhere.
> 
> No, I think the translated files should be in the tree proper, we have
> the space :)

Frankly i don't see the difference between this and the annual reoccurring "why can't the kernel messages be localized" discussion.
(Which is a little overdue, but maybe this replaces it this time.)

I could see the point in ONE "HOWTO" file per language to get people started, but everything else is a pointless exercise.
A developer/bug-reporter has to be able to express him-/herself in English and understand English, otherwise you can not accomplish very much.

All the points of the localized-messages discussion:
- You have to have a common language, otherwise you can't communicate.
- The translation will per definition be out of sync
- Translations tend to introduce (translation-)errors
- ...
also apply here.

A little anecdote:
Very Long ago (last millennium i think) SuSE defaulted to a german translated kernel for one release of their distribution. (And optionally for a few more)
But even though i'm german i couldn't understand a single word.


And here is the FAQ-Entry about the annually reoccurring discussion:
http://www.tux.org/lkml/#s9-16





Bis denn

-- 
Real Programmers consider "what you see is what you get" to be just as
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated,
cryptic, powerful, unforgiving, dangerous.


  parent reply	other threads:[~2007-06-10 18:23 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
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     ` Matthias Schniedermeyer [this message]
2007-06-11  6:07       ` [RFD] Documentation/HOWTO translated into Japanese 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=466C3B64.4070806@citd.de \
    --to=ms@citd.de \
    --cc=gregkh@suse.de \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m-ikeda@ds.jp.nec.com \
    --cc=tshibata@ab.jp.nec.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