www-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

www/licenses/po license-list.cs.po license-list...


From: GNUN
Subject: www/licenses/po license-list.cs.po license-list...
Date: Tue, 8 Jan 2019 04:29:08 -0500 (EST)

CVSROOT:        /web/www
Module name:    www
Changes by:     GNUN <gnun>     19/01/08 04:29:07

Modified files:
        licenses/po    : license-list.cs.po license-list.de-diff.html 
                         license-list.de.po license-list.es.po 
                         license-list.fr.po license-list.it-diff.html 
                         license-list.it.po license-list.ja-diff.html 
                         license-list.ja.po license-list.pl.po 
                         license-list.pot license-list.ru.po 

Log message:
        Automatic update by GNUnited Nations.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/license-list.cs.po?cvsroot=www&r1=1.27&r2=1.28
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/license-list.de-diff.html?cvsroot=www&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/license-list.de.po?cvsroot=www&r1=1.290&r2=1.291
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/license-list.es.po?cvsroot=www&r1=1.271&r2=1.272
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/license-list.fr.po?cvsroot=www&r1=1.377&r2=1.378
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/license-list.it-diff.html?cvsroot=www&r1=1.13&r2=1.14
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/license-list.it.po?cvsroot=www&r1=1.315&r2=1.316
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/license-list.ja-diff.html?cvsroot=www&r1=1.27&r2=1.28
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/license-list.ja.po?cvsroot=www&r1=1.176&r2=1.177
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/license-list.pl.po?cvsroot=www&r1=1.26&r2=1.27
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/license-list.pot?cvsroot=www&r1=1.191&r2=1.192
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/license-list.ru.po?cvsroot=www&r1=1.312&r2=1.313

Patches:
Index: license-list.cs.po
===================================================================
RCS file: /web/www/www/licenses/po/license-list.cs.po,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -b -r1.27 -r1.28
--- license-list.cs.po  8 Jan 2019 04:58:54 -0000       1.27
+++ license-list.cs.po  8 Jan 2019 09:29:07 -0000       1.28
@@ -7,7 +7,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: license-list.html\n"
-"POT-Creation-Date: 2019-01-08 04:56+0000\n"
+"POT-Creation-Date: 2019-01-08 09:26+0000\n"
 "PO-Revision-Date: \n"
 "Last-Translator: Thérèse Godefroy <godef.th AT free.fr>\n"
 "Language-Team: web-translators <address@hidden>\n"
@@ -1049,8 +1049,8 @@
 #. type: Content of: <dl><dd><p>
 msgid ""
 "This license had an unfortunate wording choice: it provided recipients with "
-"&quot;Permission to use, copy, modify, and distribute this software&hellip;"
-"&quot;. This was the same language from the license of Pine that the "
+"&ldquo;Permission to use, copy, modify, and distribute this software&hellip;"
+"&rdquo; This was the same language from the license of Pine that the "
 "University of Washington later claimed prohibited people from distributing "
 "modified versions of the software."
 msgstr ""
@@ -1059,14 +1059,14 @@
 msgid ""
 "ISC has told us they do not share the University of Washington's "
 "interpretation, and we have every reason to believe them. ISC also updated "
-"the license to read &quot;Permission to use, copy, modify, *and/or* "
-"distribute this software&hellip;&quot;. While the inclusion of &quot;and/"
-"or&quot; doesn't completely solve the issue, there's no reason to avoid "
-"software released under this license. However, to help make sure this "
-"language cannot cause any trouble in the future, we encourage developers to "
-"choose a different license for their own works. The <a href=\"#FreeBSD"
-"\">FreeBSD License</a> is similarly permissive and brief. However, if you "
-"want a lax, weak license, we recommend using the Apache 2.0 license."
+"the license to read &ldquo;Permission to use, copy, modify, <strong>and/or</"
+"strong> distribute this software&hellip;&rdquo; While the inclusion of "
+"&ldquo;and/or&rdquo; doesn't completely solve the issue, there's no reason "
+"to avoid software released under this license. However, to help make sure "
+"this language cannot cause any trouble in the future, we encourage "
+"developers to choose a different license for their own works. The <a href="
+"\"#FreeBSD\">FreeBSD License</a> is similarly permissive and brief. However, "
+"if you want a lax, weak license, we recommend using the Apache 2.0 license."
 msgstr ""
 
 #. type: Content of: <dl><dt>

Index: license-list.de-diff.html
===================================================================
RCS file: /web/www/www/licenses/po/license-list.de-diff.html,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- license-list.de-diff.html   8 Jan 2019 04:58:56 -0000       1.11
+++ license-list.de-diff.html   8 Jan 2019 09:29:07 -0000       1.12
@@ -667,15 +667,16 @@
 &lt;p&gt;This license <span class="removed"><del><strong>is sometimes also 
known as the OpenBSD License,
 although there is one minor difference between the two licenses. The
 OpenBSD license was updated to remove the ambiguous term:
-&quot;and/or&quot;. The ISC license provides</strong></del></span> <span 
class="inserted"><ins><em>had an unfortunate wording choice: it 
provided</em></ins></span> recipients with &quot;Permission to use, copy, 
modify, <span class="removed"><del><strong>and/or</strong></del></span> <span 
class="inserted"><ins><em>and</em></ins></span> distribute this
+&quot;and/or&quot;. The ISC license provides</strong></del></span> <span 
class="inserted"><ins><em>had an unfortunate wording choice: it 
provided</em></ins></span> recipients with
+<span class="removed"><del><strong>&quot;Permission</strong></del></span> 
<span class="inserted"><ins><em>&ldquo;Permission</em></ins></span> to use, 
copy, modify, <span class="removed"><del><strong>and/or</strong></del></span> 
<span class="inserted"><ins><em>and</em></ins></span> distribute this
 <span class="removed"><del><strong>software&hellip;&quot;, whereas the OpenBSD 
license provides
 recipients with &quot;Permission to use, copy, modify, and
 distribute&hellip;&quot;. &lt;/p&gt;
 
-&lt;p&gt;At the time the ISC license</strong></del></span> <span 
class="inserted"><ins><em>software&hellip;&quot;. This</em></ins></span> was 
<span class="removed"><del><strong>released,</strong></del></span> the <span 
class="removed"><del><strong>use of
+&lt;p&gt;At the time the ISC license</strong></del></span> <span 
class="inserted"><ins><em>software&hellip;&rdquo; This</em></ins></span> was 
<span class="removed"><del><strong>released,</strong></del></span> the <span 
class="removed"><del><strong>use of
 &quot;and/or&quot; construct was a concern because it is 
similar</strong></del></span> <span 
class="inserted"><ins><em>same</em></ins></span> language <span 
class="removed"><del><strong>used in</strong></del></span> <span 
class="inserted"><ins><em>from</em></ins></span> the license of Pine that the 
University of Washington later claimed prohibited people from distributing 
modified versions of the <span class="removed"><del><strong>software. However, 
ISC</strong></del></span> <span class="inserted"><ins><em>software.&lt;/p&gt;
 
-&lt;p&gt;ISC</em></ins></span> has told us they do not share the University of 
Washington's interpretation, and we have every reason to believe them.  <span 
class="removed"><del><strong>Thus,</strong></del></span> <span 
class="inserted"><ins><em>ISC also updated the license to read &quot;Permission 
to use, copy, modify, *and/or* distribute this software&hellip;&quot;. While 
the inclusion of &quot;and/or&quot; doesn't completely solve the 
issue,</em></ins></span> there's no reason to avoid software released under 
this license. However, to help make sure this language cannot cause any trouble 
in the future, we encourage developers to choose a different license for their 
own works. The &lt;a <span class="removed"><del><strong>href="#Expat"&gt;Expat
+&lt;p&gt;ISC</em></ins></span> has told us they do not share the University of 
Washington's interpretation, and we have every reason to believe them.  <span 
class="removed"><del><strong>Thus,</strong></del></span> <span 
class="inserted"><ins><em>ISC also updated the license to read 
&ldquo;Permission to use, copy, modify, &lt;strong&gt;and/or&lt;/strong&gt; 
distribute this software&hellip;&rdquo; While the inclusion of 
&ldquo;and/or&rdquo; doesn't completely solve the issue,</em></ins></span> 
there's no reason to avoid software released under this license. However, to 
help make sure this language cannot cause any trouble in the future, we 
encourage developers to choose a different license for their own works. The 
&lt;a <span class="removed"><del><strong>href="#Expat"&gt;Expat
 License&lt;/a&gt; and &lt;a</strong></del></span> href="#FreeBSD"&gt;FreeBSD 
License&lt;/a&gt; <span class="removed"><del><strong>are</strong></del></span> 
<span class="inserted"><ins><em>is</em></ins></span> similarly permissive and 
<span 
class="removed"><del><strong>brief.&lt;/p&gt;&lt;/dd&gt;</strong></del></span> 
<span class="inserted"><ins><em>brief. However, if you want a lax, weak 
license, we recommend using the Apache 2.0 
license.&lt;/p&gt;&lt;/dd&gt;</em></ins></span>
 
 &lt;dt&gt;&lt;a id="MPL-2.0"
@@ -2789,7 +2790,7 @@
 
 &lt;p class="unprintable"&gt;Updated:
 &lt;!-- timestamp start --&gt;
-$Date: 2019/01/08 04:58:56 $
+$Date: 2019/01/08 09:29:07 $
 &lt;!-- timestamp end --&gt;
 &lt;/p&gt;
 &lt;/div&gt;

Index: license-list.de.po
===================================================================
RCS file: /web/www/www/licenses/po/license-list.de.po,v
retrieving revision 1.290
retrieving revision 1.291
diff -u -b -r1.290 -r1.291
--- license-list.de.po  8 Jan 2019 04:58:56 -0000       1.290
+++ license-list.de.po  8 Jan 2019 09:29:07 -0000       1.291
@@ -7,7 +7,7 @@
 msgstr ""
 "Project-Id-Version: license-list.html\n"
 "Report-Msgid-Bugs-To: Licensing & Compliance Lab <address@hidden>\n"
-"POT-Creation-Date: 2019-01-08 04:56+0000\n"
+"POT-Creation-Date: 2019-01-08 09:26+0000\n"
 "PO-Revision-Date: 2018-08-12 22:00+0200\n"
 "Last-Translator: Jоегg Kоhпе <joeko (AT) online [PUNKT] de>\n"
 "Language-Team: German <address@hidden>\n"
@@ -1148,8 +1148,9 @@
 
 #. type: Content of: <dl><dd><p>
 # | This license [-does have-] {+had+} an unfortunate wording choice: it
-# | provide[-s-]{+d+} recipients with &quot;Permission to use, copy, modify,
-# | [-and/or-] {+and+} distribute this software&hellip;&quot;{+.+} This [-is
+# | provide[-s-]{+d+} recipients with [-&quot;Permission-]
+# | {+&ldquo;Permission+} to use, copy, modify, [-and/or-] {+and+} distribute
+# | this [-software&hellip;&quot;-] {+software&hellip;&rdquo;+} This [-is
 # | roughly-] {+was+} the same language from the license of Pine that the
 # | University of Washington later claimed prohibited people from distributing
 # | modified versions of the software.
@@ -1162,8 +1163,8 @@
 #| "prohibited people from distributing modified versions of the software."
 msgid ""
 "This license had an unfortunate wording choice: it provided recipients with "
-"&quot;Permission to use, copy, modify, and distribute this software&hellip;"
-"&quot;. This was the same language from the license of Pine that the "
+"&ldquo;Permission to use, copy, modify, and distribute this software&hellip;"
+"&rdquo; This was the same language from the license of Pine that the "
 "University of Washington later claimed prohibited people from distributing "
 "modified versions of the software."
 msgstr ""
@@ -1176,15 +1177,16 @@
 #. type: Content of: <dl><dd><p>
 # | ISC has told us they do not share the University of Washington's
 # | interpretation, and we have every reason to believe them.  [-Thus,-] {+ISC
-# | also updated the license to read &quot;Permission to use, copy, modify,
-# | *and/or* distribute this software&hellip;&quot;. While the inclusion of
-# | &quot;and/or&quot; doesn't completely solve the issue,+} there's no reason
-# | to avoid software released under this license. However, to help make sure
-# | this language cannot cause any trouble in the future, we encourage
-# | developers to choose a different license for their own works. The <a
-# | [-href=\"#Expat\">Expat License</a> and <a-] href=\"#FreeBSD\">FreeBSD
-# | License</a> [-are-] {+is+} similarly permissive and brief. {+However, if
-# | you want a lax, weak license, we recommend using the Apache 2.0 license.+}
+# | also updated the license to read &ldquo;Permission to use, copy, modify,
+# | <strong>and/or</strong> distribute this software&hellip;&rdquo; While the
+# | inclusion of &ldquo;and/or&rdquo; doesn't completely solve the issue,+}
+# | there's no reason to avoid software released under this license. However,
+# | to help make sure this language cannot cause any trouble in the future, we
+# | encourage developers to choose a different license for their own works.
+# | The <a [-href=\"#Expat\">Expat License</a> and <a-]
+# | href=\"#FreeBSD\">FreeBSD License</a> [-are-] {+is+} similarly permissive
+# | and brief. {+However, if you want a lax, weak license, we recommend using
+# | the Apache 2.0 license.+}
 #, fuzzy
 #| msgid ""
 #| "ISC has told us they do not share the University of Washington's "
@@ -1197,14 +1199,14 @@
 msgid ""
 "ISC has told us they do not share the University of Washington's "
 "interpretation, and we have every reason to believe them. ISC also updated "
-"the license to read &quot;Permission to use, copy, modify, *and/or* "
-"distribute this software&hellip;&quot;. While the inclusion of &quot;and/"
-"or&quot; doesn't completely solve the issue, there's no reason to avoid "
-"software released under this license. However, to help make sure this "
-"language cannot cause any trouble in the future, we encourage developers to "
-"choose a different license for their own works. The <a href=\"#FreeBSD"
-"\">FreeBSD License</a> is similarly permissive and brief. However, if you "
-"want a lax, weak license, we recommend using the Apache 2.0 license."
+"the license to read &ldquo;Permission to use, copy, modify, <strong>and/or</"
+"strong> distribute this software&hellip;&rdquo; While the inclusion of "
+"&ldquo;and/or&rdquo; doesn't completely solve the issue, there's no reason "
+"to avoid software released under this license. However, to help make sure "
+"this language cannot cause any trouble in the future, we encourage "
+"developers to choose a different license for their own works. The <a href="
+"\"#FreeBSD\">FreeBSD License</a> is similarly permissive and brief. However, "
+"if you want a lax, weak license, we recommend using the Apache 2.0 license."
 msgstr ""
 "ISC teilte uns mit, sie würden die Interpretation der Universität von "
 "Washington nicht teilen, und wir haben allen Grund, dies zu glauben. Somit "

Index: license-list.es.po
===================================================================
RCS file: /web/www/www/licenses/po/license-list.es.po,v
retrieving revision 1.271
retrieving revision 1.272
diff -u -b -r1.271 -r1.272
--- license-list.es.po  8 Jan 2019 04:58:56 -0000       1.271
+++ license-list.es.po  8 Jan 2019 09:29:07 -0000       1.272
@@ -12,7 +12,7 @@
 msgstr ""
 "Project-Id-Version: license-list.html\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2019-01-08 04:56+0000\n"
+"POT-Creation-Date: 2019-01-08 09:26+0000\n"
 "PO-Revision-Date: 2019-01-03 11:19+0100\n"
 "Last-Translator: Javier Fdez. Retenaga <address@hidden>\n"
 "Language-Team: Spanish <address@hidden>\n"
@@ -1246,8 +1246,8 @@
 #. type: Content of: <dl><dd><p>
 msgid ""
 "This license had an unfortunate wording choice: it provided recipients with "
-"&quot;Permission to use, copy, modify, and distribute this software&hellip;"
-"&quot;. This was the same language from the license of Pine that the "
+"&ldquo;Permission to use, copy, modify, and distribute this software&hellip;"
+"&rdquo; This was the same language from the license of Pine that the "
 "University of Washington later claimed prohibited people from distributing "
 "modified versions of the software."
 msgstr ""
@@ -1260,15 +1260,16 @@
 # | from distributing modified versions of the software. However,-]ISC has
 # | told us they do not share the University of Washington's interpretation,
 # | and we have every reason to believe them.  [-Thus,-] {+ISC also updated
-# | the license to read &quot;Permission to use, copy, modify, *and/or*
-# | distribute this software&hellip;&quot;. While the inclusion of
-# | &quot;and/or&quot; doesn't completely solve the issue,+} there's no reason
-# | to avoid software released under this license. However, to help make sure
-# | this language cannot cause any trouble in the future, we encourage
-# | developers to choose a different license for their own works. The <a
-# | [-href=\"#Expat\">Expat License</a> and <a-] href=\"#FreeBSD\">FreeBSD
-# | License</a> [-are-] {+is+} similarly permissive and brief. {+However, if
-# | you want a lax, weak license, we recommend using the Apache 2.0 license.+}
+# | the license to read &ldquo;Permission to use, copy, modify,
+# | <strong>and/or</strong> distribute this software&hellip;&rdquo; While the
+# | inclusion of &ldquo;and/or&rdquo; doesn't completely solve the issue,+}
+# | there's no reason to avoid software released under this license. However,
+# | to help make sure this language cannot cause any trouble in the future, we
+# | encourage developers to choose a different license for their own works.
+# | The <a [-href=\"#Expat\">Expat License</a> and <a-]
+# | href=\"#FreeBSD\">FreeBSD License</a> [-are-] {+is+} similarly permissive
+# | and brief. {+However, if you want a lax, weak license, we recommend using
+# | the Apache 2.0 license.+}
 #, fuzzy
 #| msgid ""
 #| "At the time the ISC license was released, the use of &quot;and/or&quot; "
@@ -1285,14 +1286,14 @@
 msgid ""
 "ISC has told us they do not share the University of Washington's "
 "interpretation, and we have every reason to believe them. ISC also updated "
-"the license to read &quot;Permission to use, copy, modify, *and/or* "
-"distribute this software&hellip;&quot;. While the inclusion of &quot;and/"
-"or&quot; doesn't completely solve the issue, there's no reason to avoid "
-"software released under this license. However, to help make sure this "
-"language cannot cause any trouble in the future, we encourage developers to "
-"choose a different license for their own works. The <a href=\"#FreeBSD"
-"\">FreeBSD License</a> is similarly permissive and brief. However, if you "
-"want a lax, weak license, we recommend using the Apache 2.0 license."
+"the license to read &ldquo;Permission to use, copy, modify, <strong>and/or</"
+"strong> distribute this software&hellip;&rdquo; While the inclusion of "
+"&ldquo;and/or&rdquo; doesn't completely solve the issue, there's no reason "
+"to avoid software released under this license. However, to help make sure "
+"this language cannot cause any trouble in the future, we encourage "
+"developers to choose a different license for their own works. The <a href="
+"\"#FreeBSD\">FreeBSD License</a> is similarly permissive and brief. However, "
+"if you want a lax, weak license, we recommend using the Apache 2.0 license."
 msgstr ""
 "Cuando se publicó la licencia ISC, el uso de la expresión «y/o» fue 
motivo "
 "de inquietud porque es similar al léxico utilizado en la licencia de Pine,  "

Index: license-list.fr.po
===================================================================
RCS file: /web/www/www/licenses/po/license-list.fr.po,v
retrieving revision 1.377
retrieving revision 1.378
diff -u -b -r1.377 -r1.378
--- license-list.fr.po  8 Jan 2019 04:58:56 -0000       1.377
+++ license-list.fr.po  8 Jan 2019 09:29:07 -0000       1.378
@@ -11,7 +11,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: license-list.html\n"
-"POT-Creation-Date: 2019-01-08 04:56+0000\n"
+"POT-Creation-Date: 2019-01-08 09:26+0000\n"
 "PO-Revision-Date: 2018-12-29 19:21+0100\n"
 "Last-Translator: Thérèse godefroy <godef.th AT free.fr>\n"
 "Language-Team: French <address@hidden>\n"
@@ -1157,8 +1157,8 @@
 #. type: Content of: <dl><dd><p>
 msgid ""
 "This license had an unfortunate wording choice: it provided recipients with "
-"&quot;Permission to use, copy, modify, and distribute this software&hellip;"
-"&quot;. This was the same language from the license of Pine that the "
+"&ldquo;Permission to use, copy, modify, and distribute this software&hellip;"
+"&rdquo; This was the same language from the license of Pine that the "
 "University of Washington later claimed prohibited people from distributing "
 "modified versions of the software."
 msgstr ""
@@ -1170,15 +1170,16 @@
 # | from distributing modified versions of the software. However,-]ISC has
 # | told us they do not share the University of Washington's interpretation,
 # | and we have every reason to believe them.  [-Thus,-] {+ISC also updated
-# | the license to read &quot;Permission to use, copy, modify, *and/or*
-# | distribute this software&hellip;&quot;. While the inclusion of
-# | &quot;and/or&quot; doesn't completely solve the issue,+} there's no reason
-# | to avoid software released under this license. However, to help make sure
-# | this language cannot cause any trouble in the future, we encourage
-# | developers to choose a different license for their own works. The <a
-# | [-href=\"#Expat\">Expat License</a> and <a-] href=\"#FreeBSD\">FreeBSD
-# | License</a> [-are-] {+is+} similarly permissive and brief. {+However, if
-# | you want a lax, weak license, we recommend using the Apache 2.0 license.+}
+# | the license to read &ldquo;Permission to use, copy, modify,
+# | <strong>and/or</strong> distribute this software&hellip;&rdquo; While the
+# | inclusion of &ldquo;and/or&rdquo; doesn't completely solve the issue,+}
+# | there's no reason to avoid software released under this license. However,
+# | to help make sure this language cannot cause any trouble in the future, we
+# | encourage developers to choose a different license for their own works.
+# | The <a [-href=\"#Expat\">Expat License</a> and <a-]
+# | href=\"#FreeBSD\">FreeBSD License</a> [-are-] {+is+} similarly permissive
+# | and brief. {+However, if you want a lax, weak license, we recommend using
+# | the Apache 2.0 license.+}
 #, fuzzy
 #| msgid ""
 #| "At the time the ISC license was released, the use of &quot;and/or&quot; "
@@ -1195,14 +1196,14 @@
 msgid ""
 "ISC has told us they do not share the University of Washington's "
 "interpretation, and we have every reason to believe them. ISC also updated "
-"the license to read &quot;Permission to use, copy, modify, *and/or* "
-"distribute this software&hellip;&quot;. While the inclusion of &quot;and/"
-"or&quot; doesn't completely solve the issue, there's no reason to avoid "
-"software released under this license. However, to help make sure this "
-"language cannot cause any trouble in the future, we encourage developers to "
-"choose a different license for their own works. The <a href=\"#FreeBSD"
-"\">FreeBSD License</a> is similarly permissive and brief. However, if you "
-"want a lax, weak license, we recommend using the Apache 2.0 license."
+"the license to read &ldquo;Permission to use, copy, modify, <strong>and/or</"
+"strong> distribute this software&hellip;&rdquo; While the inclusion of "
+"&ldquo;and/or&rdquo; doesn't completely solve the issue, there's no reason "
+"to avoid software released under this license. However, to help make sure "
+"this language cannot cause any trouble in the future, we encourage "
+"developers to choose a different license for their own works. The <a href="
+"\"#FreeBSD\">FreeBSD License</a> is similarly permissive and brief. However, "
+"if you want a lax, weak license, we recommend using the Apache 2.0 license."
 msgstr ""
 "Au moment où la licence de l'ISC a été publiée, l'emploi de la 
construction "
 "« et/ou » était préoccupante parce qu'elle est semblable à la 
formulation "

Index: license-list.it-diff.html
===================================================================
RCS file: /web/www/www/licenses/po/license-list.it-diff.html,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -b -r1.13 -r1.14
--- license-list.it-diff.html   8 Jan 2019 04:58:56 -0000       1.13
+++ license-list.it-diff.html   8 Jan 2019 09:29:07 -0000       1.14
@@ -667,15 +667,16 @@
 &lt;p&gt;This license <span class="removed"><del><strong>is sometimes also 
known as the OpenBSD License,
 although there is one minor difference between the two licenses. The
 OpenBSD license was updated to remove the ambiguous term:
-&quot;and/or&quot;. The ISC license provides</strong></del></span> <span 
class="inserted"><ins><em>had an unfortunate wording choice: it 
provided</em></ins></span> recipients with &quot;Permission to use, copy, 
modify, <span class="removed"><del><strong>and/or</strong></del></span> <span 
class="inserted"><ins><em>and</em></ins></span> distribute this
+&quot;and/or&quot;. The ISC license provides</strong></del></span> <span 
class="inserted"><ins><em>had an unfortunate wording choice: it 
provided</em></ins></span> recipients with
+<span class="removed"><del><strong>&quot;Permission</strong></del></span> 
<span class="inserted"><ins><em>&ldquo;Permission</em></ins></span> to use, 
copy, modify, <span class="removed"><del><strong>and/or</strong></del></span> 
<span class="inserted"><ins><em>and</em></ins></span> distribute this
 <span class="removed"><del><strong>software&hellip;&quot;, whereas the OpenBSD 
license provides
 recipients with &quot;Permission to use, copy, modify, and
 distribute&hellip;&quot;. &lt;/p&gt;
 
-&lt;p&gt;At the time the ISC license</strong></del></span> <span 
class="inserted"><ins><em>software&hellip;&quot;. This</em></ins></span> was 
<span class="removed"><del><strong>released,</strong></del></span> the <span 
class="removed"><del><strong>use of
+&lt;p&gt;At the time the ISC license</strong></del></span> <span 
class="inserted"><ins><em>software&hellip;&rdquo; This</em></ins></span> was 
<span class="removed"><del><strong>released,</strong></del></span> the <span 
class="removed"><del><strong>use of
 &quot;and/or&quot; construct was a concern because it is 
similar</strong></del></span> <span 
class="inserted"><ins><em>same</em></ins></span> language <span 
class="removed"><del><strong>used in</strong></del></span> <span 
class="inserted"><ins><em>from</em></ins></span> the license of Pine that the 
University of Washington later claimed prohibited people from distributing 
modified versions of the <span class="removed"><del><strong>software. However, 
ISC</strong></del></span> <span class="inserted"><ins><em>software.&lt;/p&gt;
 
-&lt;p&gt;ISC</em></ins></span> has told us they do not share the University of 
Washington's interpretation, and we have every reason to believe them.  <span 
class="removed"><del><strong>Thus,</strong></del></span> <span 
class="inserted"><ins><em>ISC also updated the license to read &quot;Permission 
to use, copy, modify, *and/or* distribute this software&hellip;&quot;. While 
the inclusion of &quot;and/or&quot; doesn't completely solve the 
issue,</em></ins></span> there's no reason to avoid software released under 
this license. However, to help make sure this language cannot cause any trouble 
in the future, we encourage developers to choose a different license for their 
own works. The &lt;a <span class="removed"><del><strong>href="#Expat"&gt;Expat
+&lt;p&gt;ISC</em></ins></span> has told us they do not share the University of 
Washington's interpretation, and we have every reason to believe them.  <span 
class="removed"><del><strong>Thus,</strong></del></span> <span 
class="inserted"><ins><em>ISC also updated the license to read 
&ldquo;Permission to use, copy, modify, &lt;strong&gt;and/or&lt;/strong&gt; 
distribute this software&hellip;&rdquo; While the inclusion of 
&ldquo;and/or&rdquo; doesn't completely solve the issue,</em></ins></span> 
there's no reason to avoid software released under this license. However, to 
help make sure this language cannot cause any trouble in the future, we 
encourage developers to choose a different license for their own works. The 
&lt;a <span class="removed"><del><strong>href="#Expat"&gt;Expat
 License&lt;/a&gt; and &lt;a</strong></del></span> href="#FreeBSD"&gt;FreeBSD 
License&lt;/a&gt; <span class="removed"><del><strong>are</strong></del></span> 
<span class="inserted"><ins><em>is</em></ins></span> similarly permissive and 
<span 
class="removed"><del><strong>brief.&lt;/p&gt;&lt;/dd&gt;</strong></del></span> 
<span class="inserted"><ins><em>brief. However, if you want a lax, weak 
license, we recommend using the Apache 2.0 
license.&lt;/p&gt;&lt;/dd&gt;</em></ins></span>
 
 &lt;dt&gt;&lt;a id="MPL-2.0"
@@ -2804,7 +2805,7 @@
 
 &lt;p class="unprintable"&gt;Updated:
 &lt;!-- timestamp start --&gt;
-$Date: 2019/01/08 04:58:56 $
+$Date: 2019/01/08 09:29:07 $
 &lt;!-- timestamp end --&gt;
 &lt;/p&gt;
 &lt;/div&gt;

Index: license-list.it.po
===================================================================
RCS file: /web/www/www/licenses/po/license-list.it.po,v
retrieving revision 1.315
retrieving revision 1.316
diff -u -b -r1.315 -r1.316
--- license-list.it.po  8 Jan 2019 04:58:57 -0000       1.315
+++ license-list.it.po  8 Jan 2019 09:29:07 -0000       1.316
@@ -8,7 +8,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: license-list.html\n"
-"POT-Creation-Date: 2019-01-08 04:56+0000\n"
+"POT-Creation-Date: 2019-01-08 09:26+0000\n"
 "PO-Revision-Date: 2018-02-16 09:15+0100\n"
 "Last-Translator: Andrea Pescetti <address@hidden>\n"
 "Language-Team: Italian\n"
@@ -1245,8 +1245,8 @@
 #. type: Content of: <dl><dd><p>
 msgid ""
 "This license had an unfortunate wording choice: it provided recipients with "
-"&quot;Permission to use, copy, modify, and distribute this software&hellip;"
-"&quot;. This was the same language from the license of Pine that the "
+"&ldquo;Permission to use, copy, modify, and distribute this software&hellip;"
+"&rdquo; This was the same language from the license of Pine that the "
 "University of Washington later claimed prohibited people from distributing "
 "modified versions of the software."
 msgstr ""
@@ -1259,15 +1259,16 @@
 # | from distributing modified versions of the software. However,-]ISC has
 # | told us they do not share the University of Washington's interpretation,
 # | and we have every reason to believe them.  [-Thus,-] {+ISC also updated
-# | the license to read &quot;Permission to use, copy, modify, *and/or*
-# | distribute this software&hellip;&quot;. While the inclusion of
-# | &quot;and/or&quot; doesn't completely solve the issue,+} there's no reason
-# | to avoid software released under this license. However, to help make sure
-# | this language cannot cause any trouble in the future, we encourage
-# | developers to choose a different license for their own works. The <a
-# | [-href=\"#Expat\">Expat License</a> and <a-] href=\"#FreeBSD\">FreeBSD
-# | License</a> [-are-] {+is+} similarly permissive and brief. {+However, if
-# | you want a lax, weak license, we recommend using the Apache 2.0 license.+}
+# | the license to read &ldquo;Permission to use, copy, modify,
+# | <strong>and/or</strong> distribute this software&hellip;&rdquo; While the
+# | inclusion of &ldquo;and/or&rdquo; doesn't completely solve the issue,+}
+# | there's no reason to avoid software released under this license. However,
+# | to help make sure this language cannot cause any trouble in the future, we
+# | encourage developers to choose a different license for their own works.
+# | The <a [-href=\"#Expat\">Expat License</a> and <a-]
+# | href=\"#FreeBSD\">FreeBSD License</a> [-are-] {+is+} similarly permissive
+# | and brief. {+However, if you want a lax, weak license, we recommend using
+# | the Apache 2.0 license.+}
 #, fuzzy
 #| msgid ""
 #| "At the time the ISC license was released, the use of &quot;and/or&quot; "
@@ -1284,14 +1285,14 @@
 msgid ""
 "ISC has told us they do not share the University of Washington's "
 "interpretation, and we have every reason to believe them. ISC also updated "
-"the license to read &quot;Permission to use, copy, modify, *and/or* "
-"distribute this software&hellip;&quot;. While the inclusion of &quot;and/"
-"or&quot; doesn't completely solve the issue, there's no reason to avoid "
-"software released under this license. However, to help make sure this "
-"language cannot cause any trouble in the future, we encourage developers to "
-"choose a different license for their own works. The <a href=\"#FreeBSD"
-"\">FreeBSD License</a> is similarly permissive and brief. However, if you "
-"want a lax, weak license, we recommend using the Apache 2.0 license."
+"the license to read &ldquo;Permission to use, copy, modify, <strong>and/or</"
+"strong> distribute this software&hellip;&rdquo; While the inclusion of "
+"&ldquo;and/or&rdquo; doesn't completely solve the issue, there's no reason "
+"to avoid software released under this license. However, to help make sure "
+"this language cannot cause any trouble in the future, we encourage "
+"developers to choose a different license for their own works. The <a href="
+"\"#FreeBSD\">FreeBSD License</a> is similarly permissive and brief. However, "
+"if you want a lax, weak license, we recommend using the Apache 2.0 license."
 msgstr ""
 "Quando la licenza ISC fu pubblicata, l'uso di &quot;and/or&quot; destava "
 "preoccupazione perché una simile clusola usate nelle licenza di Pine era "

Index: license-list.ja-diff.html
===================================================================
RCS file: /web/www/www/licenses/po/license-list.ja-diff.html,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -b -r1.27 -r1.28
--- license-list.ja-diff.html   8 Jan 2019 04:58:57 -0000       1.27
+++ license-list.ja-diff.html   8 Jan 2019 09:29:07 -0000       1.28
@@ -668,15 +668,16 @@
 &lt;p&gt;This license <span class="removed"><del><strong>is sometimes also 
known as the OpenBSD License,
 although there is one minor difference between the two licenses. The
 OpenBSD license was updated to remove the ambiguous term:
-&quot;and/or&quot;. The ISC license provides</strong></del></span> <span 
class="inserted"><ins><em>had an unfortunate wording choice: it 
provided</em></ins></span> recipients with &quot;Permission to use, copy, 
modify, <span class="removed"><del><strong>and/or</strong></del></span> <span 
class="inserted"><ins><em>and</em></ins></span> distribute this
+&quot;and/or&quot;. The ISC license provides</strong></del></span> <span 
class="inserted"><ins><em>had an unfortunate wording choice: it 
provided</em></ins></span> recipients with
+<span class="removed"><del><strong>&quot;Permission</strong></del></span> 
<span class="inserted"><ins><em>&ldquo;Permission</em></ins></span> to use, 
copy, modify, <span class="removed"><del><strong>and/or</strong></del></span> 
<span class="inserted"><ins><em>and</em></ins></span> distribute this
 <span class="removed"><del><strong>software&hellip;&quot;, whereas the OpenBSD 
license provides
 recipients with &quot;Permission to use, copy, modify, and
 distribute&hellip;&quot;. &lt;/p&gt;
 
-&lt;p&gt;At the time the ISC license</strong></del></span> <span 
class="inserted"><ins><em>software&hellip;&quot;. This</em></ins></span> was 
<span class="removed"><del><strong>released,</strong></del></span> the <span 
class="removed"><del><strong>use of
+&lt;p&gt;At the time the ISC license</strong></del></span> <span 
class="inserted"><ins><em>software&hellip;&rdquo; This</em></ins></span> was 
<span class="removed"><del><strong>released,</strong></del></span> the <span 
class="removed"><del><strong>use of
 &quot;and/or&quot; construct was a concern because it is 
similar</strong></del></span> <span 
class="inserted"><ins><em>same</em></ins></span> language <span 
class="removed"><del><strong>used in</strong></del></span> <span 
class="inserted"><ins><em>from</em></ins></span> the license of Pine that the 
University of Washington later claimed prohibited people from distributing 
modified versions of the <span class="removed"><del><strong>software. However, 
ISC</strong></del></span> <span class="inserted"><ins><em>software.&lt;/p&gt;
 
-&lt;p&gt;ISC</em></ins></span> has told us they do not share the University of 
Washington's interpretation, and we have every reason to believe them.  <span 
class="removed"><del><strong>Thus,</strong></del></span> <span 
class="inserted"><ins><em>ISC also updated the license to read &quot;Permission 
to use, copy, modify, *and/or* distribute this software&hellip;&quot;. While 
the inclusion of &quot;and/or&quot; doesn't completely solve the 
issue,</em></ins></span> there's no reason to avoid software released under 
this license. However, to help make sure this language cannot cause any trouble 
in the future, we encourage developers to choose a different license for their 
own works. The &lt;a <span class="removed"><del><strong>href="#Expat"&gt;Expat
+&lt;p&gt;ISC</em></ins></span> has told us they do not share the University of 
Washington's interpretation, and we have every reason to believe them.  <span 
class="removed"><del><strong>Thus,</strong></del></span> <span 
class="inserted"><ins><em>ISC also updated the license to read 
&ldquo;Permission to use, copy, modify, &lt;strong&gt;and/or&lt;/strong&gt; 
distribute this software&hellip;&rdquo; While the inclusion of 
&ldquo;and/or&rdquo; doesn't completely solve the issue,</em></ins></span> 
there's no reason to avoid software released under this license. However, to 
help make sure this language cannot cause any trouble in the future, we 
encourage developers to choose a different license for their own works. The 
&lt;a <span class="removed"><del><strong>href="#Expat"&gt;Expat
 License&lt;/a&gt; and &lt;a</strong></del></span> href="#FreeBSD"&gt;FreeBSD 
License&lt;/a&gt; <span class="removed"><del><strong>are</strong></del></span> 
<span class="inserted"><ins><em>is</em></ins></span> similarly permissive and 
<span 
class="removed"><del><strong>brief.&lt;/p&gt;&lt;/dd&gt;</strong></del></span> 
<span class="inserted"><ins><em>brief. However, if you want a lax, weak 
license, we recommend using the Apache 2.0 
license.&lt;/p&gt;&lt;/dd&gt;</em></ins></span>
 
 &lt;dt&gt;&lt;a id="MPL-2.0"
@@ -1174,7 +1175,7 @@
 for</strong></del></span> <span class="inserted"><ins><em>obligations set
 forth in</em></ins></span> this <span 
class="removed"><del><strong>reason.&lt;/p&gt;
 
-&lt;p&gt;For an illustrative</strong></del></span> <span 
class="inserted"><ins><em>Article.&rdquo;&lt;/p&gt;
+&lt;p&gt;For an illustrative example of why you</strong></del></span> <span 
class="inserted"><ins><em>Article.&rdquo;&lt;/p&gt;
 
 &lt;p&gt;Please do not release software under this 
license.&lt;/p&gt;&lt;/dd&gt;
 
@@ -1203,7 +1204,7 @@
 cannot legally be linked together.  We urge you not to use the CDDL
 for this reason.&lt;/p&gt;
 
-&lt;p&gt;For an illustrative</em></ins></span> example of why you should not 
combine
+&lt;p&gt;For an illustrative example of why you</em></ins></span> should not 
combine
 CDDL-licensed works with the GPL-licensed works, see the FSF's
 statement, &lt;a href="https://www.fsf.org/licensing/zfs-and-linux"&gt;
 &lt;em&gt;Interpreting, enforcing and changing the GNU GPL, as applied to
@@ -2816,7 +2817,7 @@
 
 &lt;p class="unprintable"&gt;Updated:
 &lt;!-- timestamp start --&gt;
-$Date: 2019/01/08 04:58:57 $
+$Date: 2019/01/08 09:29:07 $
 &lt;!-- timestamp end --&gt;
 &lt;/p&gt;
 &lt;/div&gt;

Index: license-list.ja.po
===================================================================
RCS file: /web/www/www/licenses/po/license-list.ja.po,v
retrieving revision 1.176
retrieving revision 1.177
diff -u -b -r1.176 -r1.177
--- license-list.ja.po  8 Jan 2019 04:58:57 -0000       1.176
+++ license-list.ja.po  8 Jan 2019 09:29:07 -0000       1.177
@@ -7,7 +7,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: license-list.html\n"
-"POT-Creation-Date: 2019-01-08 04:56+0000\n"
+"POT-Creation-Date: 2019-01-08 09:26+0000\n"
 "PO-Revision-Date: 2016-10-31 10:00+0900\n"
 "Last-Translator: NIIBE Yutaka <address@hidden>\n"
 "Language-Team: Japanese <address@hidden>\n"
@@ -1149,8 +1149,8 @@
 #| "prohibited people from distributing modified versions of the software."
 msgid ""
 "This license had an unfortunate wording choice: it provided recipients with "
-"&quot;Permission to use, copy, modify, and distribute this software&hellip;"
-"&quot;. This was the same language from the license of Pine that the "
+"&ldquo;Permission to use, copy, modify, and distribute this software&hellip;"
+"&rdquo; This was the same language from the license of Pine that the "
 "University of Washington later claimed prohibited people from distributing "
 "modified versions of the software."
 msgstr ""
@@ -1178,14 +1178,14 @@
 msgid ""
 "ISC has told us they do not share the University of Washington's "
 "interpretation, and we have every reason to believe them. ISC also updated "
-"the license to read &quot;Permission to use, copy, modify, *and/or* "
-"distribute this software&hellip;&quot;. While the inclusion of &quot;and/"
-"or&quot; doesn't completely solve the issue, there's no reason to avoid "
-"software released under this license. However, to help make sure this "
-"language cannot cause any trouble in the future, we encourage developers to "
-"choose a different license for their own works. The <a href=\"#FreeBSD"
-"\">FreeBSD License</a> is similarly permissive and brief. However, if you "
-"want a lax, weak license, we recommend using the Apache 2.0 license."
+"the license to read &ldquo;Permission to use, copy, modify, <strong>and/or</"
+"strong> distribute this software&hellip;&rdquo; While the inclusion of "
+"&ldquo;and/or&rdquo; doesn't completely solve the issue, there's no reason "
+"to avoid software released under this license. However, to help make sure "
+"this language cannot cause any trouble in the future, we encourage "
+"developers to choose a different license for their own works. The <a href="
+"\"#FreeBSD\">FreeBSD License</a> is similarly permissive and brief. However, "
+"if you want a lax, weak license, we recommend using the Apache 2.0 license."
 msgstr ""
 
"ISCライセンスがリリースされた時点で、&quot;and/or&quot;の構成は懸念でした。な"
 
"ぜならPineのライセンスで同様な言葉遣いが使われており、ワシントン大学が後に"

Index: license-list.pl.po
===================================================================
RCS file: /web/www/www/licenses/po/license-list.pl.po,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -b -r1.26 -r1.27
--- license-list.pl.po  8 Jan 2019 04:58:57 -0000       1.26
+++ license-list.pl.po  8 Jan 2019 09:29:07 -0000       1.27
@@ -7,7 +7,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: license-list.html\n"
-"POT-Creation-Date: 2019-01-08 04:56+0000\n"
+"POT-Creation-Date: 2019-01-08 09:26+0000\n"
 "PO-Revision-Date: 2017-04-24 16:01-0600\n"
 "Last-Translator: Jan Owoc <jsowoc AT gmail.com>\n"
 "Language-Team: Polish <address@hidden>\n"
@@ -1197,8 +1197,8 @@
 #. type: Content of: <dl><dd><p>
 msgid ""
 "This license had an unfortunate wording choice: it provided recipients with "
-"&quot;Permission to use, copy, modify, and distribute this software&hellip;"
-"&quot;. This was the same language from the license of Pine that the "
+"&ldquo;Permission to use, copy, modify, and distribute this software&hellip;"
+"&rdquo; This was the same language from the license of Pine that the "
 "University of Washington later claimed prohibited people from distributing "
 "modified versions of the software."
 msgstr ""
@@ -1207,14 +1207,14 @@
 msgid ""
 "ISC has told us they do not share the University of Washington's "
 "interpretation, and we have every reason to believe them. ISC also updated "
-"the license to read &quot;Permission to use, copy, modify, *and/or* "
-"distribute this software&hellip;&quot;. While the inclusion of &quot;and/"
-"or&quot; doesn't completely solve the issue, there's no reason to avoid "
-"software released under this license. However, to help make sure this "
-"language cannot cause any trouble in the future, we encourage developers to "
-"choose a different license for their own works. The <a href=\"#FreeBSD"
-"\">FreeBSD License</a> is similarly permissive and brief. However, if you "
-"want a lax, weak license, we recommend using the Apache 2.0 license."
+"the license to read &ldquo;Permission to use, copy, modify, <strong>and/or</"
+"strong> distribute this software&hellip;&rdquo; While the inclusion of "
+"&ldquo;and/or&rdquo; doesn't completely solve the issue, there's no reason "
+"to avoid software released under this license. However, to help make sure "
+"this language cannot cause any trouble in the future, we encourage "
+"developers to choose a different license for their own works. The <a href="
+"\"#FreeBSD\">FreeBSD License</a> is similarly permissive and brief. However, "
+"if you want a lax, weak license, we recommend using the Apache 2.0 license."
 msgstr ""
 
 #. type: Content of: <dl><dt>

Index: license-list.pot
===================================================================
RCS file: /web/www/www/licenses/po/license-list.pot,v
retrieving revision 1.191
retrieving revision 1.192
diff -u -b -r1.191 -r1.192
--- license-list.pot    8 Jan 2019 04:58:57 -0000       1.191
+++ license-list.pot    8 Jan 2019 09:29:07 -0000       1.192
@@ -7,7 +7,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: license-list.html\n"
-"POT-Creation-Date: 2019-01-08 04:56+0000\n"
+"POT-Creation-Date: 2019-01-08 09:26+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <address@hidden>\n"
 "Language-Team: LANGUAGE <address@hidden>\n"
@@ -811,8 +811,8 @@
 #. type: Content of: <dl><dd><p>
 msgid ""
 "This license had an unfortunate wording choice: it provided recipients with "
-"&quot;Permission to use, copy, modify, and distribute this "
-"software&hellip;&quot;. This was the same language from the license of Pine "
+"&ldquo;Permission to use, copy, modify, and distribute this "
+"software&hellip;&rdquo; This was the same language from the license of Pine "
 "that the University of Washington later claimed prohibited people from "
 "distributing modified versions of the software."
 msgstr ""
@@ -821,13 +821,13 @@
 msgid ""
 "ISC has told us they do not share the University of Washington's "
 "interpretation, and we have every reason to believe them. ISC also updated "
-"the license to read &quot;Permission to use, copy, modify, *and/or* "
-"distribute this software&hellip;&quot;. While the inclusion of "
-"&quot;and/or&quot; doesn't completely solve the issue, there's no reason to "
-"avoid software released under this license. However, to help make sure this "
-"language cannot cause any trouble in the future, we encourage developers to "
-"choose a different license for their own works. The <a "
-"href=\"#FreeBSD\">FreeBSD License</a> is similarly permissive and "
+"the license to read &ldquo;Permission to use, copy, modify, "
+"<strong>and/or</strong> distribute this software&hellip;&rdquo; While the "
+"inclusion of &ldquo;and/or&rdquo; doesn't completely solve the issue, "
+"there's no reason to avoid software released under this license. However, to "
+"help make sure this language cannot cause any trouble in the future, we "
+"encourage developers to choose a different license for their own works. The "
+"<a href=\"#FreeBSD\">FreeBSD License</a> is similarly permissive and "
 "brief. However, if you want a lax, weak license, we recommend using the "
 "Apache 2.0 license."
 msgstr ""

Index: license-list.ru.po
===================================================================
RCS file: /web/www/www/licenses/po/license-list.ru.po,v
retrieving revision 1.312
retrieving revision 1.313
diff -u -b -r1.312 -r1.313
--- license-list.ru.po  8 Jan 2019 04:58:57 -0000       1.312
+++ license-list.ru.po  8 Jan 2019 09:29:07 -0000       1.313
@@ -7,7 +7,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: license-list.html\n"
-"POT-Creation-Date: 2019-01-08 04:56+0000\n"
+"POT-Creation-Date: 2019-01-08 09:26+0000\n"
 "PO-Revision-Date: 2018-12-29 17:17+0000\n"
 "Last-Translator: Ineiev <address@hidden>\n"
 "Language-Team: Russian <address@hidden>\n"
@@ -1150,8 +1150,9 @@
 
 #. type: Content of: <dl><dd><p>
 # | This license [-does have-] {+had+} an unfortunate wording choice: it
-# | provide[-s-]{+d+} recipients with &quot;Permission to use, copy, modify,
-# | [-and/or-] {+and+} distribute this software&hellip;&quot;{+.+} This [-is
+# | provide[-s-]{+d+} recipients with [-&quot;Permission-]
+# | {+&ldquo;Permission+} to use, copy, modify, [-and/or-] {+and+} distribute
+# | this [-software&hellip;&quot;-] {+software&hellip;&rdquo;+} This [-is
 # | roughly-] {+was+} the same language from the license of Pine that the
 # | University of Washington later claimed prohibited people from distributing
 # | modified versions of the software.
@@ -1164,8 +1165,8 @@
 #| "prohibited people from distributing modified versions of the software."
 msgid ""
 "This license had an unfortunate wording choice: it provided recipients with "
-"&quot;Permission to use, copy, modify, and distribute this software&hellip;"
-"&quot;. This was the same language from the license of Pine that the "
+"&ldquo;Permission to use, copy, modify, and distribute this software&hellip;"
+"&rdquo; This was the same language from the license of Pine that the "
 "University of Washington later claimed prohibited people from distributing "
 "modified versions of the software."
 msgstr ""
@@ -1182,15 +1183,16 @@
 # | from distributing modified versions of the software. However,-]ISC has
 # | told us they do not share the University of Washington's interpretation,
 # | and we have every reason to believe them.  [-Thus,-] {+ISC also updated
-# | the license to read &quot;Permission to use, copy, modify, *and/or*
-# | distribute this software&hellip;&quot;. While the inclusion of
-# | &quot;and/or&quot; doesn't completely solve the issue,+} there's no reason
-# | to avoid software released under this license. However, to help make sure
-# | this language cannot cause any trouble in the future, we encourage
-# | developers to choose a different license for their own works. The <a
-# | [-href=\"#Expat\">Expat License</a> and <a-] href=\"#FreeBSD\">FreeBSD
-# | License</a> [-are-] {+is+} similarly permissive and brief. {+However, if
-# | you want a lax, weak license, we recommend using the Apache 2.0 license.+}
+# | the license to read &ldquo;Permission to use, copy, modify,
+# | <strong>and/or</strong> distribute this software&hellip;&rdquo; While the
+# | inclusion of &ldquo;and/or&rdquo; doesn't completely solve the issue,+}
+# | there's no reason to avoid software released under this license. However,
+# | to help make sure this language cannot cause any trouble in the future, we
+# | encourage developers to choose a different license for their own works.
+# | The <a [-href=\"#Expat\">Expat License</a> and <a-]
+# | href=\"#FreeBSD\">FreeBSD License</a> [-are-] {+is+} similarly permissive
+# | and brief. {+However, if you want a lax, weak license, we recommend using
+# | the Apache 2.0 license.+}
 #, fuzzy
 #| msgid ""
 #| "At the time the ISC license was released, the use of &quot;and/or&quot; "
@@ -1207,14 +1209,14 @@
 msgid ""
 "ISC has told us they do not share the University of Washington's "
 "interpretation, and we have every reason to believe them. ISC also updated "
-"the license to read &quot;Permission to use, copy, modify, *and/or* "
-"distribute this software&hellip;&quot;. While the inclusion of &quot;and/"
-"or&quot; doesn't completely solve the issue, there's no reason to avoid "
-"software released under this license. However, to help make sure this "
-"language cannot cause any trouble in the future, we encourage developers to "
-"choose a different license for their own works. The <a href=\"#FreeBSD"
-"\">FreeBSD License</a> is similarly permissive and brief. However, if you "
-"want a lax, weak license, we recommend using the Apache 2.0 license."
+"the license to read &ldquo;Permission to use, copy, modify, <strong>and/or</"
+"strong> distribute this software&hellip;&rdquo; While the inclusion of "
+"&ldquo;and/or&rdquo; doesn't completely solve the issue, there's no reason "
+"to avoid software released under this license. However, to help make sure "
+"this language cannot cause any trouble in the future, we encourage "
+"developers to choose a different license for their own works. The <a href="
+"\"#FreeBSD\">FreeBSD License</a> is similarly permissive and brief. However, "
+"if you want a lax, weak license, we recommend using the Apache 2.0 license."
 msgstr ""
 "Когда была выпущена лицензия ISC, 
конструкция &ldquo;и/или&rdquo; вызывала "
 "опасения, потому что она сходна с 
формулировкой, применявшейся в лицензии "



reply via email to

[Prev in Thread] Current Thread [Next in Thread]