linux-kernel - Re: [RFD] Documentation/HOWTO translated into Japanese

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: <466C3B64.4070806@citd.de>
Date:	Sun, 10 Jun 2007 19:56:52 +0200
From:	Matthias Schniedermeyer <ms@...d.de>
To:	Greg KH <gregkh@...e.de>
CC:	Jesper Juhl <jesper.juhl@...il.com>,
	Tsugikazu Shibata <tshibata@...jp.nec.com>,
	linux-kernel@...r.kernel.org, m-ikeda@...jp.nec.com
Subject: Re: [RFD] Documentation/HOWTO translated into Japanese

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.

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