From: Greg KH <gregkh@suse.de>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: 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 09:22:21 -0700 [thread overview]
Message-ID: <20070610162221.GA12830@suse.de> (raw)
In-Reply-To: <9a8748490706100524o2dff1954ja7406f9303d8499f@mail.gmail.com>
On Sun, Jun 10, 2007 at 02:24:51PM +0200, Jesper Juhl wrote:
> On 10/06/07, Tsugikazu Shibata <tshibata@ab.jp.nec.com> wrote:
> > Hi all,
> >
> > I am posting Documentation/HOWTO which is translated into Japanese at
> > bottom of this email.
Great, thanks for posting this and doing the work.
> > 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?).
Is it hard to convert it to UTF-8?
> > - 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@ab.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?
That's up to the people maintaining the translations to do.
> 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 :)
thanks,
greg k-h
next prev parent reply other threads:[~2007-06-10 16:20 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 [this message]
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 ` [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=20070610162221.GA12830@suse.de \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.