www-commits
[Top][All Lists]
Advanced

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

www/licenses/po license-recommendations.fr.po l...


From: GNUN
Subject: www/licenses/po license-recommendations.fr.po l...
Date: Thu, 19 Jun 2014 19:57:16 +0000

CVSROOT:        /web/www
Module name:    www
Changes by:     GNUN <gnun>     14/06/19 19:57:16

Modified files:
        licenses/po    : license-recommendations.fr.po 
                         license-recommendations.ja.po 
                         license-recommendations.pot 
                         license-recommendations.ru.po 

Log message:
        Automatic update by GNUnited Nations.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/license-recommendations.fr.po?cvsroot=www&r1=1.20&r2=1.21
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/license-recommendations.ja.po?cvsroot=www&r1=1.14&r2=1.15
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/license-recommendations.pot?cvsroot=www&r1=1.18&r2=1.19
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/license-recommendations.ru.po?cvsroot=www&r1=1.26&r2=1.27

Patches:
Index: license-recommendations.fr.po
===================================================================
RCS file: /web/www/www/licenses/po/license-recommendations.fr.po,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -b -r1.20 -r1.21
--- license-recommendations.fr.po       19 Apr 2014 12:21:53 -0000      1.20
+++ license-recommendations.fr.po       19 Jun 2014 19:57:13 -0000      1.21
@@ -6,7 +6,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: license-recommendations.html\n"
-"POT-Creation-Date: 2014-04-05 00:01+0000\n"
+"POT-Creation-Date: 2014-06-19 19:55+0000\n"
 "PO-Revision-Date: 2014-04-19 13:57+0200\n"
 "Last-Translator: Thérèse Godefroy <godef.th AT free.fr>\n"
 "Language-Team: French <address@hidden>\n"
@@ -14,6 +14,7 @@
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=utf-8\n"
 "Content-Transfer-Encoding: 8bit\n"
+"X-Outdated-Since: 2014-06-19 19:55+0000\n"
 "Plural-Forms: \n"
 "X-Generator: Gtranslator 2.91.5\n"
 
@@ -198,16 +199,36 @@
 "copyleft sur le code du projet."
 
 #. type: Content of: <p>
+# | In these special situations where copyleft is not appropriate, we
+# | recommend the <a
+# | href=\"http://www.apache.org/licenses/LICENSE-2.0\";>Apache License
+# | 2.0</a>.  This is a [-permissive, non-protective-] {+pushover
+# | (non-copyleft)+}  software license that has terms to prevent contributors
+# | and distributors from suing for patent infringement.  This doesn't make
+# | the software immune to threats from patents, but it does prevent patent
+# | holders from setting up a &ldquo;bait and switch&rdquo; where they release
+# | the software under free [-terms, but-] {+terms then+} require recipients
+# | to agree to [-royalties or other-] nonfree terms in a patent license.
+#, fuzzy
+#| msgid ""
+#| "In these special situations where copyleft is not appropriate, we "
+#| "recommend the <a href=\"http://www.apache.org/licenses/";
+#| "LICENSE-2.0\">Apache License 2.0</a>.  This is a permissive, non-"
+#| "protective software license that has terms to prevent contributors and "
+#| "distributors from suing for patent infringement.  This doesn't make the "
+#| "software immune to threats from patents, but it does prevent patent "
+#| "holders from setting up a &ldquo;bait and switch&rdquo; where they "
+#| "release the software under free terms, but require recipients to agree to "
+#| "royalties or other nonfree terms in a patent license."
 msgid ""
 "In these special situations where copyleft is not appropriate, we recommend "
 "the <a href=\"http://www.apache.org/licenses/LICENSE-2.0\";>Apache License "
-"2.0</a>.  This is a permissive, non-protective software license that has "
-"terms to prevent contributors and distributors from suing for patent "
+"2.0</a>.  This is a pushover (non-copyleft)  software license that has terms "
+"to prevent contributors and distributors from suing for patent "
 "infringement.  This doesn't make the software immune to threats from "
 "patents, but it does prevent patent holders from setting up a &ldquo;bait "
-"and switch&rdquo; where they release the software under free terms, but "
-"require recipients to agree to royalties or other nonfree terms in a patent "
-"license."
+"and switch&rdquo; where they release the software under free terms then "
+"require recipients to agree to nonfree terms in a patent license."
 msgstr ""
 "Dans ces situations particulières où le copyleft n'est pas adapté, nous "
 "recommandons la <a href=\"http://www.apache.org/licenses/";
@@ -221,22 +242,58 @@
 "libres, au moyen d'une licence de brevet."
 
 #. type: Content of: <p>
+# | In all other cases, we recommend some kind of copyleft.  If your project
+# | is a library, and developers are already using an established alternative
+# | library released under a nonfree {+license+} or [-permissive-] {+a lax
+# | pushover+} license, then we recommend using the <a
+# | href=\"/licenses/lgpl.html\">GNU Lesser General Public License (LGPL)</a>.
+# |  Unlike the case discussed earlier where the project implements a
+# | standard, here adoption for its own sake will not accomplish any
+# | particular goal, so there's no reason to avoid copyleft entirely. 
+# | However, if you ask developers who use your library to release their work
+# | under a full copyleft, they'll simply use one of the alternatives
+# | available, and that won't advance our cause either.  The Lesser GPL was
+# | designed to fill the middle ground between these cases, allowing
+# | proprietary software developers to use the covered library, but providing
+# | a weak copyleft that benefits users when they do.  If you want to learn
+# | more about our thinking in these cases, read <a
+# | href=\"/licenses/why-not-lgpl.html\">&ldquo;Why you shouldn't use the
+# | Lesser GPL for your next library&rdquo;</a>.
+#, fuzzy
+#| msgid ""
+#| "In all other cases, we recommend some kind of copyleft.  If your project "
+#| "is a library, and developers are already using an established alternative "
+#| "library released under a nonfree or permissive license, then we recommend "
+#| "using the <a href=\"/licenses/lgpl.html\">GNU Lesser General Public "
+#| "License (LGPL)</a>.  Unlike the case discussed earlier where the project "
+#| "implements a standard, here adoption for its own sake will not accomplish "
+#| "any particular goal, so there's no reason to avoid copyleft entirely.  "
+#| "However, if you ask developers who use your library to release their work "
+#| "under a full copyleft, they'll simply use one of the alternatives "
+#| "available, and that won't advance our cause either.  The Lesser GPL was "
+#| "designed to fill the middle ground between these cases, allowing "
+#| "proprietary software developers to use the covered library, but providing "
+#| "a weak copyleft that benefits users when they do.  If you want to learn "
+#| "more about our thinking in these cases, read <a href=\"/licenses/why-not-"
+#| "lgpl.html\">&ldquo;Why you shouldn't use the Lesser GPL for your next "
+#| "library&rdquo;</a>."
 msgid ""
 "In all other cases, we recommend some kind of copyleft.  If your project is "
 "a library, and developers are already using an established alternative "
-"library released under a nonfree or permissive license, then we recommend "
-"using the <a href=\"/licenses/lgpl.html\">GNU Lesser General Public License "
-"(LGPL)</a>.  Unlike the case discussed earlier where the project implements "
-"a standard, here adoption for its own sake will not accomplish any "
-"particular goal, so there's no reason to avoid copyleft entirely.  However, "
-"if you ask developers who use your library to release their work under a "
-"full copyleft, they'll simply use one of the alternatives available, and "
-"that won't advance our cause either.  The Lesser GPL was designed to fill "
-"the middle ground between these cases, allowing proprietary software "
-"developers to use the covered library, but providing a weak copyleft that "
-"benefits users when they do.  If you want to learn more about our thinking "
-"in these cases, read <a href=\"/licenses/why-not-lgpl.html\">&ldquo;Why you "
-"shouldn't use the Lesser GPL for your next library&rdquo;</a>."
+"library released under a nonfree license or a lax pushover license, then we "
+"recommend using the <a href=\"/licenses/lgpl.html\">GNU Lesser General "
+"Public License (LGPL)</a>.  Unlike the case discussed earlier where the "
+"project implements a standard, here adoption for its own sake will not "
+"accomplish any particular goal, so there's no reason to avoid copyleft "
+"entirely.  However, if you ask developers who use your library to release "
+"their work under a full copyleft, they'll simply use one of the alternatives "
+"available, and that won't advance our cause either.  The Lesser GPL was "
+"designed to fill the middle ground between these cases, allowing proprietary "
+"software developers to use the covered library, but providing a weak "
+"copyleft that benefits users when they do.  If you want to learn more about "
+"our thinking in these cases, read <a href=\"/licenses/why-not-lgpl.html"
+"\">&ldquo;Why you shouldn't use the Lesser GPL for your next library&rdquo;</"
+"a>."
 msgstr ""
 "Dans tous les autres cas, nous recommandons un copyleft, quel qu'il soit. Si "
 "votre projet est une bibliothèque, et que les développeurs utilisent déjà 
"

Index: license-recommendations.ja.po
===================================================================
RCS file: /web/www/www/licenses/po/license-recommendations.ja.po,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -b -r1.14 -r1.15
--- license-recommendations.ja.po       28 Apr 2014 07:26:44 -0000      1.14
+++ license-recommendations.ja.po       19 Jun 2014 19:57:13 -0000      1.15
@@ -6,7 +6,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: license-recommendations.html\n"
-"POT-Creation-Date: 2014-04-05 00:01+0000\n"
+"POT-Creation-Date: 2014-06-19 19:55+0000\n"
 "PO-Revision-Date: 2014-04-28 16:20+0200\n"
 "Last-Translator: NIIBE Yutaka <address@hidden>\n"
 "Language-Team: Japanese <address@hidden>\n"
@@ -14,6 +14,7 @@
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
+"X-Outdated-Since: 2014-06-19 19:55+0000\n"
 
 #. type: Content of: <title>
 msgid ""
@@ -188,16 +189,26 @@
 "りよいと考えられます。"
 
 #. type: Content of: <p>
+#, fuzzy
+#| msgid ""
+#| "In these special situations where copyleft is not appropriate, we "
+#| "recommend the <a href=\"http://www.apache.org/licenses/";
+#| "LICENSE-2.0\">Apache License 2.0</a>.  This is a permissive, non-"
+#| "protective software license that has terms to prevent contributors and "
+#| "distributors from suing for patent infringement.  This doesn't make the "
+#| "software immune to threats from patents, but it does prevent patent "
+#| "holders from setting up a &ldquo;bait and switch&rdquo; where they "
+#| "release the software under free terms, but require recipients to agree to "
+#| "royalties or other nonfree terms in a patent license."
 msgid ""
 "In these special situations where copyleft is not appropriate, we recommend "
 "the <a href=\"http://www.apache.org/licenses/LICENSE-2.0\";>Apache License "
-"2.0</a>.  This is a permissive, non-protective software license that has "
-"terms to prevent contributors and distributors from suing for patent "
+"2.0</a>.  This is a pushover (non-copyleft)  software license that has terms "
+"to prevent contributors and distributors from suing for patent "
 "infringement.  This doesn't make the software immune to threats from "
 "patents, but it does prevent patent holders from setting up a &ldquo;bait "
-"and switch&rdquo; where they release the software under free terms, but "
-"require recipients to agree to royalties or other nonfree terms in a patent "
-"license."
+"and switch&rdquo; where they release the software under free terms then "
+"require recipients to agree to nonfree terms in a patent license."
 msgstr ""
 "コピーレフトが適さないような特別の状況では、<a 
href=\"http://www.apache.org/";
 
"licenses/LICENSE-2.0\">Apacheライセンス2.0</a>をわたしたちは推奨します。これ"
@@ -208,22 +219,41 @@
 "条項
を要請するという「おとり商法」を設定することを防ぎます。"
 
 #. type: Content of: <p>
+#, fuzzy
+#| msgid ""
+#| "In all other cases, we recommend some kind of copyleft.  If your project "
+#| "is a library, and developers are already using an established alternative "
+#| "library released under a nonfree or permissive license, then we recommend "
+#| "using the <a href=\"/licenses/lgpl.html\">GNU Lesser General Public "
+#| "License (LGPL)</a>.  Unlike the case discussed earlier where the project "
+#| "implements a standard, here adoption for its own sake will not accomplish "
+#| "any particular goal, so there's no reason to avoid copyleft entirely.  "
+#| "However, if you ask developers who use your library to release their work "
+#| "under a full copyleft, they'll simply use one of the alternatives "
+#| "available, and that won't advance our cause either.  The Lesser GPL was "
+#| "designed to fill the middle ground between these cases, allowing "
+#| "proprietary software developers to use the covered library, but providing "
+#| "a weak copyleft that benefits users when they do.  If you want to learn "
+#| "more about our thinking in these cases, read <a href=\"/licenses/why-not-"
+#| "lgpl.html\">&ldquo;Why you shouldn't use the Lesser GPL for your next "
+#| "library&rdquo;</a>."
 msgid ""
 "In all other cases, we recommend some kind of copyleft.  If your project is "
 "a library, and developers are already using an established alternative "
-"library released under a nonfree or permissive license, then we recommend "
-"using the <a href=\"/licenses/lgpl.html\">GNU Lesser General Public License "
-"(LGPL)</a>.  Unlike the case discussed earlier where the project implements "
-"a standard, here adoption for its own sake will not accomplish any "
-"particular goal, so there's no reason to avoid copyleft entirely.  However, "
-"if you ask developers who use your library to release their work under a "
-"full copyleft, they'll simply use one of the alternatives available, and "
-"that won't advance our cause either.  The Lesser GPL was designed to fill "
-"the middle ground between these cases, allowing proprietary software "
-"developers to use the covered library, but providing a weak copyleft that "
-"benefits users when they do.  If you want to learn more about our thinking "
-"in these cases, read <a href=\"/licenses/why-not-lgpl.html\">&ldquo;Why you "
-"shouldn't use the Lesser GPL for your next library&rdquo;</a>."
+"library released under a nonfree license or a lax pushover license, then we "
+"recommend using the <a href=\"/licenses/lgpl.html\">GNU Lesser General "
+"Public License (LGPL)</a>.  Unlike the case discussed earlier where the "
+"project implements a standard, here adoption for its own sake will not "
+"accomplish any particular goal, so there's no reason to avoid copyleft "
+"entirely.  However, if you ask developers who use your library to release "
+"their work under a full copyleft, they'll simply use one of the alternatives "
+"available, and that won't advance our cause either.  The Lesser GPL was "
+"designed to fill the middle ground between these cases, allowing proprietary "
+"software developers to use the covered library, but providing a weak "
+"copyleft that benefits users when they do.  If you want to learn more about "
+"our thinking in these cases, read <a href=\"/licenses/why-not-lgpl.html"
+"\">&ldquo;Why you shouldn't use the Lesser GPL for your next library&rdquo;</"
+"a>."
 msgstr ""
 
"そのほかのすべてのケースでは、わたしたちはなんらかのコピーレフトを推奨しま"
 
"す。あなたのプロジェクトがライブラリであり、不自由か寛容なライセンスでリリー"

Index: license-recommendations.pot
===================================================================
RCS file: /web/www/www/licenses/po/license-recommendations.pot,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- license-recommendations.pot 5 Apr 2014 00:41:30 -0000       1.18
+++ license-recommendations.pot 19 Jun 2014 19:57:13 -0000      1.19
@@ -7,7 +7,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: license-recommendations.html\n"
-"POT-Creation-Date: 2014-04-05 00:01+0000\n"
+"POT-Creation-Date: 2014-06-19 19:55+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"
@@ -137,32 +137,32 @@
 msgid ""
 "In these special situations where copyleft is not appropriate, we recommend "
 "the <a href=\"http://www.apache.org/licenses/LICENSE-2.0\";>Apache License "
-"2.0</a>.  This is a permissive, non-protective software license that has "
-"terms to prevent contributors and distributors from suing for patent "
+"2.0</a>.  This is a pushover (non-copyleft)  software license that has terms "
+"to prevent contributors and distributors from suing for patent "
 "infringement.  This doesn't make the software immune to threats from "
 "patents, but it does prevent patent holders from setting up a &ldquo;bait "
-"and switch&rdquo; where they release the software under free terms, but "
-"require recipients to agree to royalties or other nonfree terms in a patent "
-"license."
+"and switch&rdquo; where they release the software under free terms then "
+"require recipients to agree to nonfree terms in a patent license."
 msgstr ""
 
 #. type: Content of: <p>
 msgid ""
 "In all other cases, we recommend some kind of copyleft.  If your project is "
 "a library, and developers are already using an established alternative "
-"library released under a nonfree or permissive license, then we recommend "
-"using the <a href=\"/licenses/lgpl.html\">GNU Lesser General Public License "
-"(LGPL)</a>.  Unlike the case discussed earlier where the project implements "
-"a standard, here adoption for its own sake will not accomplish any "
-"particular goal, so there's no reason to avoid copyleft entirely.  However, "
-"if you ask developers who use your library to release their work under a "
-"full copyleft, they'll simply use one of the alternatives available, and "
-"that won't advance our cause either.  The Lesser GPL was designed to fill "
-"the middle ground between these cases, allowing proprietary software "
-"developers to use the covered library, but providing a weak copyleft that "
-"benefits users when they do.  If you want to learn more about our thinking "
-"in these cases, read <a href=\"/licenses/why-not-lgpl.html\">&ldquo;Why you "
-"shouldn't use the Lesser GPL for your next library&rdquo;</a>."
+"library released under a nonfree license or a lax pushover license, then we "
+"recommend using the <a href=\"/licenses/lgpl.html\">GNU Lesser General "
+"Public License (LGPL)</a>.  Unlike the case discussed earlier where the "
+"project implements a standard, here adoption for its own sake will not "
+"accomplish any particular goal, so there's no reason to avoid copyleft "
+"entirely.  However, if you ask developers who use your library to release "
+"their work under a full copyleft, they'll simply use one of the alternatives "
+"available, and that won't advance our cause either.  The Lesser GPL was "
+"designed to fill the middle ground between these cases, allowing proprietary "
+"software developers to use the covered library, but providing a weak "
+"copyleft that benefits users when they do.  If you want to learn more about "
+"our thinking in these cases, read <a "
+"href=\"/licenses/why-not-lgpl.html\">&ldquo;Why you shouldn't use the Lesser "
+"GPL for your next library&rdquo;</a>."
 msgstr ""
 
 #. type: Content of: <p>

Index: license-recommendations.ru.po
===================================================================
RCS file: /web/www/www/licenses/po/license-recommendations.ru.po,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -b -r1.26 -r1.27
--- license-recommendations.ru.po       5 Apr 2014 05:47:29 -0000       1.26
+++ license-recommendations.ru.po       19 Jun 2014 19:57:13 -0000      1.27
@@ -7,7 +7,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: license-recommendations.html\n"
-"POT-Creation-Date: 2014-04-05 00:01+0000\n"
+"POT-Creation-Date: 2014-06-19 19:55+0000\n"
 "PO-Revision-Date: 2014-04-05 17:17+0000\n"
 "Last-Translator: Ineiev <address@hidden>\n"
 "Language-Team: Russian <address@hidden>\n"
@@ -15,6 +15,7 @@
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
+"X-Outdated-Since: 2014-06-19 19:55+0000\n"
 
 #. type: Content of: <title>
 msgid ""
@@ -200,16 +201,36 @@
 "авторского лева."
 
 #. type: Content of: <p>
+# | In these special situations where copyleft is not appropriate, we
+# | recommend the <a
+# | href=\"http://www.apache.org/licenses/LICENSE-2.0\";>Apache License
+# | 2.0</a>.  This is a [-permissive, non-protective-] {+pushover
+# | (non-copyleft)+}  software license that has terms to prevent contributors
+# | and distributors from suing for patent infringement.  This doesn't make
+# | the software immune to threats from patents, but it does prevent patent
+# | holders from setting up a &ldquo;bait and switch&rdquo; where they release
+# | the software under free [-terms, but-] {+terms then+} require recipients
+# | to agree to [-royalties or other-] nonfree terms in a patent license.
+#, fuzzy
+#| msgid ""
+#| "In these special situations where copyleft is not appropriate, we "
+#| "recommend the <a href=\"http://www.apache.org/licenses/";
+#| "LICENSE-2.0\">Apache License 2.0</a>.  This is a permissive, non-"
+#| "protective software license that has terms to prevent contributors and "
+#| "distributors from suing for patent infringement.  This doesn't make the "
+#| "software immune to threats from patents, but it does prevent patent "
+#| "holders from setting up a &ldquo;bait and switch&rdquo; where they "
+#| "release the software under free terms, but require recipients to agree to "
+#| "royalties or other nonfree terms in a patent license."
 msgid ""
 "In these special situations where copyleft is not appropriate, we recommend "
 "the <a href=\"http://www.apache.org/licenses/LICENSE-2.0\";>Apache License "
-"2.0</a>.  This is a permissive, non-protective software license that has "
-"terms to prevent contributors and distributors from suing for patent "
+"2.0</a>.  This is a pushover (non-copyleft)  software license that has terms "
+"to prevent contributors and distributors from suing for patent "
 "infringement.  This doesn't make the software immune to threats from "
 "patents, but it does prevent patent holders from setting up a &ldquo;bait "
-"and switch&rdquo; where they release the software under free terms, but "
-"require recipients to agree to royalties or other nonfree terms in a patent "
-"license."
+"and switch&rdquo; where they release the software under free terms then "
+"require recipients to agree to nonfree terms in a patent license."
 msgstr ""
 "В этих особых случаях, для которых 
авторское лево не подходит, мы "
 "рекомендуем <a 
href=\"http://www.apache.org/licenses/LICENSE-2.0\";>версию "
@@ -222,22 +243,58 @@
 "выплаты или другие несвободные условия 
патентной лицензии."
 
 #. type: Content of: <p>
+# | In all other cases, we recommend some kind of copyleft.  If your project
+# | is a library, and developers are already using an established alternative
+# | library released under a nonfree {+license+} or [-permissive-] {+a lax
+# | pushover+} license, then we recommend using the <a
+# | href=\"/licenses/lgpl.html\">GNU Lesser General Public License (LGPL)</a>.
+# |  Unlike the case discussed earlier where the project implements a
+# | standard, here adoption for its own sake will not accomplish any
+# | particular goal, so there's no reason to avoid copyleft entirely. 
+# | However, if you ask developers who use your library to release their work
+# | under a full copyleft, they'll simply use one of the alternatives
+# | available, and that won't advance our cause either.  The Lesser GPL was
+# | designed to fill the middle ground between these cases, allowing
+# | proprietary software developers to use the covered library, but providing
+# | a weak copyleft that benefits users when they do.  If you want to learn
+# | more about our thinking in these cases, read <a
+# | href=\"/licenses/why-not-lgpl.html\">&ldquo;Why you shouldn't use the
+# | Lesser GPL for your next library&rdquo;</a>.
+#, fuzzy
+#| msgid ""
+#| "In all other cases, we recommend some kind of copyleft.  If your project "
+#| "is a library, and developers are already using an established alternative "
+#| "library released under a nonfree or permissive license, then we recommend "
+#| "using the <a href=\"/licenses/lgpl.html\">GNU Lesser General Public "
+#| "License (LGPL)</a>.  Unlike the case discussed earlier where the project "
+#| "implements a standard, here adoption for its own sake will not accomplish "
+#| "any particular goal, so there's no reason to avoid copyleft entirely.  "
+#| "However, if you ask developers who use your library to release their work "
+#| "under a full copyleft, they'll simply use one of the alternatives "
+#| "available, and that won't advance our cause either.  The Lesser GPL was "
+#| "designed to fill the middle ground between these cases, allowing "
+#| "proprietary software developers to use the covered library, but providing "
+#| "a weak copyleft that benefits users when they do.  If you want to learn "
+#| "more about our thinking in these cases, read <a href=\"/licenses/why-not-"
+#| "lgpl.html\">&ldquo;Why you shouldn't use the Lesser GPL for your next "
+#| "library&rdquo;</a>."
 msgid ""
 "In all other cases, we recommend some kind of copyleft.  If your project is "
 "a library, and developers are already using an established alternative "
-"library released under a nonfree or permissive license, then we recommend "
-"using the <a href=\"/licenses/lgpl.html\">GNU Lesser General Public License "
-"(LGPL)</a>.  Unlike the case discussed earlier where the project implements "
-"a standard, here adoption for its own sake will not accomplish any "
-"particular goal, so there's no reason to avoid copyleft entirely.  However, "
-"if you ask developers who use your library to release their work under a "
-"full copyleft, they'll simply use one of the alternatives available, and "
-"that won't advance our cause either.  The Lesser GPL was designed to fill "
-"the middle ground between these cases, allowing proprietary software "
-"developers to use the covered library, but providing a weak copyleft that "
-"benefits users when they do.  If you want to learn more about our thinking "
-"in these cases, read <a href=\"/licenses/why-not-lgpl.html\">&ldquo;Why you "
-"shouldn't use the Lesser GPL for your next library&rdquo;</a>."
+"library released under a nonfree license or a lax pushover license, then we "
+"recommend using the <a href=\"/licenses/lgpl.html\">GNU Lesser General "
+"Public License (LGPL)</a>.  Unlike the case discussed earlier where the "
+"project implements a standard, here adoption for its own sake will not "
+"accomplish any particular goal, so there's no reason to avoid copyleft "
+"entirely.  However, if you ask developers who use your library to release "
+"their work under a full copyleft, they'll simply use one of the alternatives "
+"available, and that won't advance our cause either.  The Lesser GPL was "
+"designed to fill the middle ground between these cases, allowing proprietary "
+"software developers to use the covered library, but providing a weak "
+"copyleft that benefits users when they do.  If you want to learn more about "
+"our thinking in these cases, read <a href=\"/licenses/why-not-lgpl.html"
+"\">&ldquo;Why you shouldn't use the Lesser GPL for your next library&rdquo;</"
+"a>."
 msgstr ""
 "Во всех прочих случаях мы рекомендуем ту 
или иную разновидность авторского "
 "лева. Если ваш проект является 
библиотекой и разработчики уже применяют "



reply via email to

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