From: IKEDA Munehiro <m-ikeda@ds.jp.nec.com>
To: Alistair John Strachan <s0348365@sms.ed.ac.uk>
Cc: linux-kernel@vger.kernel.org,
Tsugikazu Shibata <tshibata@ab.jp.nec.com>,
gregkh@suse.de
Subject: Re: [RFD] Documentation/stable_api_nonsense.txt translated into Japanese
Date: Mon, 11 Jun 2007 10:33:53 +0900 [thread overview]
Message-ID: <466CA681.4090709@ds.jp.nec.com> (raw)
In-Reply-To: <200706101800.58658.s0348365@sms.ed.ac.uk>
Alistair John Strachan wrote:
> On Sunday 10 June 2007 13:03:15 you wrote:
>
>>訳注(2)
>>「引火性の高い」の原文は "valatile"。
>>valatile には「揮発性の」「爆発しやすい」という意味の他、「変わり
>>やすい」「移り気な」という意味がある。
>>「（この話題は）爆発的に激しい論争を巻き起こしかねない」ということ
>>を、「（カーネルのソースレベルインターフェースは）移ろい行くもので
>>ある」ということを連想させる "valatile" という単語で表現している。
>
>
> Not speaking Japanese, I'm probably missing some fundamental translation
> issue, but the English word is "volatile", not "valatile".
This is a translation note for the "volatile" which is used as a
double-meaning word in original.
"valatile" is my mistake to spell, wrong spelling 3 times...sorry.
--
IKEDA, Munehiro
next prev parent reply other threads:[~2007-06-11 1:35 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 [this message]
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 ` [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=466CA681.4090709@ds.jp.nec.com \
--to=m-ikeda@ds.jp.nec.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=s0348365@sms.ed.ac.uk \
--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