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: <9a8748490706100524o2dff1954ja7406f9303d8499f@mail.gmail.com>
Date:	Sun, 10 Jun 2007 14:24:51 +0200
From:	"Jesper Juhl" <jesper.juhl@...il.com>
To:	"Tsugikazu Shibata" <tshibata@...jp.nec.com>
Cc:	linux-kernel@...r.kernel.org, gregkh@...e.de, m-ikeda@...jp.nec.com
Subject: Re: [RFD] Documentation/HOWTO translated into Japanese

On 10/06/07, Tsugikazu Shibata <tshibata@...jp.nec.com> wrote:
> Hi all,
>
> I am posting Documentation/HOWTO which is translated into Japanese at
> bottom of this email.

Good job. I'm sure a lot of japanese people will appreciate that.

> This document had been reviewed by JF project which has long history
> to translate documents into Japanese. (not only kernel but also FAQs).
> For JF, please see : http://www.linux.or.jp/JF/index.html
> Please also note that the page is written in Japanese, but you can see
> a lot of results there.
>
> Actually, this is my first trial to post Japanese translated document
> and here are some points I decided ;
>
> - Character encoding is ISO-2022-JP, which is normally used for email
>   using Japanese.

I think there's consensus that documents in the kernel source should
be either plain ASCII or UTF-8 (doesn't UTF-8 work for japanese?).

> - Added "Singed-off-by" line
> - Left the JF header strings which include translator/reviewer's name
> - Non-patch format, simple text
>
> I would be happy if I could get your comments and suggestions.
> Though I know there are several issues to merge it, I want to have
> discussions with you to accomplish it.
>
> This email comes from strong recommendation from Greg K-H when he came
> to Tokyo two weeks ago. Thanks >Greg
>
> ----- Below lines are Japanese Translation of "HOWTO" -----
>
> Signed-off-by: Tsugikazu Shibata <tshibata@...jp.nec.com>
> ---

Unfortunately I don't speak japanese so I can't say anything about the
translation at all, but I do have some other comments/questions.

If we start adding translated versions of documentation to the kernel
source how should we organize the documents? Should each language get
a sepperate directory in Documentation/ - like Documentation/JP/,
Documentation/EN/, Documentation/DA/ etc?

With multiple translated versions of the documentation in the tree,
don't we run the risk that the translations will quickly become
outdated since most people updating the documentation won't be able to
update the translations?

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.

-- 
Jesper Juhl <jesper.juhl@...il.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html
-
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/