Tetsuya Kitahata <[EMAIL PROTECTED]> writes:
(B
(B>> > <li>$BK\%=%U%H%&%'%"$,[EMAIL PROTECTED]&$"[EMAIL PROTECTED]"(B
(B>> > "Apache" $B5Z$S(B "Apache Software
(B>> > Foundation"$B$NL>>N$r!";vA0$NJ8LL$G$N5v2D(B
(B>> > $B$NL5$$$^$^;HMQ$7$F$O$J$j$^$;$s!#([EMAIL PROTECTED]"Mm$N>e!"(B
(B>> > [EMAIL PROTECTED]&$K$7$F2<$5$$!#(B</li>
(B>>
(B>> I don't think $B!VAH$_9~$^$l$?!W(B is a good translation of
(B>> derived. [EMAIL PROTECTED](B is more common, I think.
(B>>
(B>> The latter sentence can give the feeling that written
(B>> permission is always granted. I'd translate it as
(B>> [EMAIL PROTECTED](B [EMAIL PROTECTED] $B$KO"Mm$7$F$/(B
(B>> [EMAIL PROTECTED](B
(B>
(B> Mmmm. Probably, this is just related to my Japanese sense of beauty,
(B> I prefer
(B> [EMAIL PROTECTED]"Mm$N>e!"[EMAIL PROTECTED]&$K$7$F2<$5$$!#(B],
(B> often used in real business world (and contracts) and rather fluent
(B> Japanese phrase.
(B
(BI still think the same as before. It gives me the
(Bimpression that most of the time written permission is
(Bgiven. I don't care much about those contracts you
(Bmentioned but I imagine those are used when they are willing
(Bto grant permission. I read the original English sentence
(Bas "If you ever want to use the name "Apache" or "Apache
(BSoftware Foundation" to promote your products, be sure to
(Bcontact [EMAIL PROTECTED] first. Depending on the situation
(Bwe might or might not give you the permission." Your
(BJapanese translation of the last sentence of section 4 is
(Blike, "Contact [EMAIL PROTECTED] and get the written
(Bpermission." I don't think it has the same connotation.
(B
(B> $B!VEj9F!W(Bor$B!V9W8%(B/$B4sM?!W(Bare very difficult to distinguish
(B> when we
(B> translate "CONTRIBUTION". The former makes us feel "easiness to
(B> contribute" and the latter rather "barriers for contribution".
(B> ("Apatchy spirits" taken into consideration, "$BEj9F(B" might be
(B> more applicable in Apache Land :-)
(B
(BWe normally use $B!V9W8%!W(B in open source software world. The
(Bfirst meaning come to my mind when I see the word $B!VEj9F!W(B
(Bis to submit something like a research paper. You can
(Bsubmit valuable information but you can also submit rubbish.
(BI don't think you can just send a worthless patch to a
(Bmailing list and claim the contribution. That's why I think
(Bthe word $B!VEj9F!W(B is not an appropriate word for
(Bcontribution.
(B
(B> Also, these sentences are "the most sensitive" part in this
(B> license agreement (In other words, if we translate these lines
(B> precisely, the other ones could be omitted :-P), so the "easy to read"
(B> could be of secondary importance :-)
(B
(BI can't follow you here. What do you mean by "other ones"?
(BWhat I meant by readability is not about the word but the
(Bsyntax used in those sentences like the one in parentheses.
(BI don't know where you get the idea of my suggesting
(Bimprecise translation. You can have readable and precise
(Btranslation. The one thing I don't know is whether it is
(Bpossible in legal documents.
(B
(B> I've put "take 2" in this mail, attached, using more legal mode (L-Mode?)
(B> of expression :)
(B> Maybe, it can be more *fluent* japanese license agreement
(B> compared to the translations of Java 2, Standard Edition (J2SE)
(B> Specification :)
(B
(BWell, I can say nothing about J2SE license because I haven't
(Bread one. I won't read Japanese translation of English
(Blicense because most of the time those are poorly
(Btranslated.
(B
(BI glanced through the translation but I won't do detail
(Breview of this one. I'd like to stay away from legal things
(Bas much as possible. I cannot find obvious mistakes so I
(Bdon't mind using this as a basis for Japanese translation.
(B
(B--
(BYoshiki Hayashi
(B
(B---------------------------------------------------------------------
(BTo unsubscribe, e-mail: [EMAIL PROTECTED]
(BFor additional commands, e-mail: [EMAIL PROTECTED]
