From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "Greg Kroah-Hartman" <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org,
"Tsugikazu Shibata" <tshibata@ab.jp.nec.com>,
"IKEDA Munehiro" <m-ikeda@ds.jp.nec.com>
Subject: Re: [PATCH 1/5] HOWTO: add Japanese translation of Documentation/HOWTO
Date: Thu, 19 Jul 2007 01:43:14 +0200 [thread overview]
Message-ID: <9a8748490707181643v2ad6b0d0ld44226a367a6f937@mail.gmail.com> (raw)
In-Reply-To: <11848012031961-git-send-email-gregkh@suse.de>
On 19/07/07, Greg Kroah-Hartman <gregkh@suse.de> wrote:
> From: Tsugikazu Shibata <tshibata@ab.jp.nec.com>
>
> Add the japanese translation of the Documentation/HOWTO file.
>
A few comments below.
> Signed-off-by: Tsugikazu Shibata <tshibata@ab.jp.nec.com>
> Cc: IKEDA Munehiro <m-ikeda@ds.jp.nec.com>
> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
> ---
> Documentation/ja_JP/HOWTO | 650 +++++++++++++++++++++++++++++++++++++++++++++
> 1 files changed, 650 insertions(+), 0 deletions(-)
> create mode 100644 Documentation/ja_JP/HOWTO
>
> diff --git a/Documentation/ja_JP/HOWTO b/Documentation/ja_JP/HOWTO
> new file mode 100644
> index 0000000..b2446a0
> --- /dev/null
> +++ b/Documentation/ja_JP/HOWTO
> @@ -0,0 +1,650 @@
> +NOTE:
> +This is Japanese translated version of "Documentation/HOWTO".
I'd suggest "This is a Japanese translated version ..." or perhaps
"This is a version of Documentation/HOWTO translated into Japanese".
> +This one is maintained by Tsugikazu Shibata <tshibata@ab.jp.nec.com>
I'd write "This document is maintained by ..."
> +and JF Project team <www.linux.or.jp/JF>.
"and the JF Project team ..."
> +If you find difference with original file or problem in translation,
How about "If you find any difference between this document and the
original file or a problem with the translation,"
> +please contact maintainer of this file or JF project.
"please contact the maintainer ..."
> +
> +Please also note that purpose of this file is easier to read for non
> +English natives and not to be intended to fork. So, if you have any
> +comments or updates of this file, please try to update Original(English)
> +file at first.
Shouldn't this be something along the lines of
"Please also note that the purpose of this file is to be easier to
read for non English (read: Japanese) speakers and is not intended as
a fork. So if you have any comments or updates for this file please
try to update the original English file first."
<snip - can't comment on the actual Japanese text>
--
Jesper Juhl <jesper.juhl@gmail.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
next prev parent reply other threads:[~2007-07-18 23:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-18 23:23 [GIT PATCH] Documentation patches for 2.6.22 Greg KH
2007-07-18 23:26 ` [PATCH 1/5] HOWTO: add Japanese translation of Documentation/HOWTO Greg Kroah-Hartman
2007-07-18 23:26 ` [PATCH 2/5] Documentation: add Japanese translated stable_api_nonsense.txt Greg Kroah-Hartman
2007-07-18 23:26 ` [PATCH 3/5] HOWTO: add Chinese translation of Documentation/HOWTO Greg Kroah-Hartman
2007-07-18 23:26 ` [PATCH 4/5] Chinese translation of Documentation/stable_api_nonsense.txt Greg Kroah-Hartman
2007-07-18 23:26 ` [PATCH 5/5] zh_CN/HOWTO: update URLs of git trees Greg Kroah-Hartman
[not found] ` <9a8748490707181646k1e062a75n86408cd88ef16193@mail.gmail.com>
2007-07-19 5:12 ` [PATCH 3/5] HOWTO: add Chinese translation of Documentation/HOWTO WANG Cong
2007-07-19 5:01 ` Greg KH
2007-07-19 5:32 ` [PATCH 3/5] HOWTO: add Chinese translation ofDocumentation/HOWTO Li Yang-r58472
2007-07-18 23:43 ` Jesper Juhl [this message]
2007-07-19 3:10 ` [PATCH 2/5] Documentation: add Japanese translated stable_api_nonsense.txt IKEDA Munehiro
2007-07-19 5:01 ` Greg KH
[not found] ` <20070720.023534.23010405.tshibata@ab.jp.nec.com>
2007-07-19 17:40 ` [PATCH 1/5] HOWTO: add Japanese translation of Documentation/HOWTO Tsugikazu Shibata
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=9a8748490707181643v2ad6b0d0ld44226a367a6f937@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=gregkh@suse.de \
--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
all inboxes | Powered by JetHome®