<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
That doesn't answer the question posed, which was about not
complying with the OSD.<br>
<br>
Where there is a clause that says that one version is the legally
operative one, then they shouldn't have relied on the translation
provided for convenience. <br>
<br>
I believe it's also true that some countries won't respect the
choice of version stated in the license and will only enforce the
local language no matter what the license says about it. So perhaps
the lesson is only that translations shouldn't be part of the formal
agreement.<br>
<br>
Pam<br>
<br>
<div class="moz-signature">Pamela S. Chestek<br>
Chestek Legal<br>
PO Box 2492<br>
Raleigh, NC 27602<br>
<a class="moz-txt-link-abbreviated" href="mailto:pamela@chesteklegal.com">pamela@chesteklegal.com</a><br>
+1 919-800-8033<br>
<br>
</div>
<div class="moz-cite-prefix">On 3/22/2022 5:02 PM, Russell Nelson
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:92e80468-fd0f-70b2-5365-0b5c273496fe@crynwr.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p>From a legal point of view, it's untenable. Somebody relies on
the English language translation. They get sued because the
Chinese language version says something different. They reply
"But you said that they're the same". YATeam replies that the
Chinese language version is the real license and overrides
anything the English language version says.</p>
<p>No. The proper way is "I cut the cake, you pick the piece." Or
in context, YATeam allows the defendant to choose whichever
language version they want. YATeam then has all the incentive
needed to make the licenses have the same effect, and if they
haven't, the defendant can choose the version most beneficial to
their case. If YATeam doesn't like that, well, they should have
worked harder.</p>
<p>We went through this with a European Union license, where they
wanted the license to have effect in different languages.<br>
</p>
<div class="moz-cite-prefix">On 3/22/22 1:06 PM, Eric Schultz
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAMkzgA5MO0sKAYFudfc0zEtqyhPrK4gxB0r7BEbP7Fdnnk+rtg@mail.gmail.com">
<meta http-equiv="content-type" content="text/html;
charset=UTF-8">
<div dir="auto">Russell,
<div dir="auto"><br>
</div>
<div dir="auto">Could you elaborate on why this isn't
acceptable as it relates to the OSD?</div>
<div dir="auto"><br>
</div>
Eric</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
The opinions expressed in this email are those of the sender and not necessarily those of the Open Source Initiative. Communication from the Open Source Initiative will be sent from an opensource.org email address.
License-review mailing list
<a class="moz-txt-link-abbreviated moz-txt-link-freetext" href="mailto:License-review@lists.opensource.org" moz-do-not-send="true">License-review@lists.opensource.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org" moz-do-not-send="true">http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org</a>
</pre>
</blockquote>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
The opinions expressed in this email are those of the sender and not necessarily those of the Open Source Initiative. Communication from the Open Source Initiative will be sent from an opensource.org email address.
License-review mailing list
<a class="moz-txt-link-abbreviated" href="mailto:License-review@lists.opensource.org">License-review@lists.opensource.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org">http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org</a>
</pre>
</blockquote>
<br>
</body>
</html>