[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www distros/free-system-distribution-guidelines...
|
From: |
GNUN |
|
Subject: |
www distros/free-system-distribution-guidelines... |
|
Date: |
Tue, 05 Jun 2012 08:29:09 +0000 |
CVSROOT: /web/www
Module name: www
Changes by: GNUN <gnun> 12/06/05 08:29:09
Modified files:
distros : free-system-distribution-guidelines.ja.html
distros/po : free-system-distribution-guidelines.ja-en.html
free-system-distribution-guidelines.ja.po
licenses/old-licenses/po: gpl-2.0-faq.translist
philosophy/po : kevin-cole-response.de.po
kevin-cole-response.fr.po
kevin-cole-response.pot
sylvester-response.de.po
sylvester-response.fr.po sylvester-response.pot
server : sitemap.ja.html
server/po : sitemap.ja-en.html sitemap.ja.po
Added files:
licenses/old-licenses: gpl-2.0-faq.ru.html
licenses/old-licenses/po: gpl-2.0-faq.ru-en.html
Log message:
Automatic update by GNUnited Nations.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/distros/free-system-distribution-guidelines.ja.html?cvsroot=www&r1=1.6&r2=1.7
http://web.cvs.savannah.gnu.org/viewcvs/www/distros/po/free-system-distribution-guidelines.ja-en.html?cvsroot=www&r1=1.6&r2=1.7
http://web.cvs.savannah.gnu.org/viewcvs/www/distros/po/free-system-distribution-guidelines.ja.po?cvsroot=www&r1=1.12&r2=1.13
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/old-licenses/gpl-2.0-faq.ru.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/old-licenses/po/gpl-2.0-faq.translist?cvsroot=www&r1=1.5&r2=1.6
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/old-licenses/po/gpl-2.0-faq.ru-en.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/kevin-cole-response.de.po?cvsroot=www&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/kevin-cole-response.fr.po?cvsroot=www&r1=1.12&r2=1.13
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/kevin-cole-response.pot?cvsroot=www&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/sylvester-response.de.po?cvsroot=www&r1=1.2&r2=1.3
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/sylvester-response.fr.po?cvsroot=www&r1=1.17&r2=1.18
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/sylvester-response.pot?cvsroot=www&r1=1.5&r2=1.6
http://web.cvs.savannah.gnu.org/viewcvs/www/server/sitemap.ja.html?cvsroot=www&r1=1.20&r2=1.21
http://web.cvs.savannah.gnu.org/viewcvs/www/server/po/sitemap.ja-en.html?cvsroot=www&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/www/server/po/sitemap.ja.po?cvsroot=www&r1=1.51&r2=1.52
Patches:
Index: distros/free-system-distribution-guidelines.ja.html
===================================================================
RCS file: /web/www/www/distros/free-system-distribution-guidelines.ja.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -b -r1.6 -r1.7
--- distros/free-system-distribution-guidelines.ja.html 19 May 2012 01:17:35
-0000 1.6
+++ distros/free-system-distribution-guidelines.ja.html 5 Jun 2012 08:26:58
-0000 1.7
@@ -37,7 +37,7 @@
class="reference"
href="/licenses/license-list.html">ã©ã¤ã»ã³ã¹ä¸è¦§</a>ã«ããããããããã½ããã¦ã§ã¢ãããã¥ã¡ã³ãããã©ã³ããããã¦ããã®ä»ã®æç¨ãªä½åã«é©åã§ããã©ã¤ã»ã³ã¹ã¨ãã»ã¯ã·ã§ã³ãåãã¦ããã¾ãããããä½åãè¤æ°ã®ã©ã¤ã»ã³ã¹ã®ãã¨ã§ãªãªã¼ã¹ãããå
´åãå°ãªãã¨ãä¸ã¤ãèªç±ã§ãããªãã°ãã·ã¹ãã
ã«å«ãããã¨ãã§ãã¾ããã·ã¹ãã éçºè
ã¯ãé
å¸ãããã¯å¤æ´ããéã«ãå©ç¨å¯è½ãªèªç±ãªã©ã¤ã»ã³ã¹(è¤æ°ããããã¾ãã)ã®æ¡é
ã«åã«ããããã°è¯ãã®ã§ãã</p>
-<p>èªç±ãªã·ã¹ãã
ã»ãã£ã¹ããªãã¥ã¼ã·ã§ã³ã¯ãå®éã®ä½¿ç¨ã®æ
å
±ã«ã¤ãã¦ãä¸èªç±ãªãã®ãå
¥æããããã«æ¡å
ãããããããããã¨ãæ¨å¥¨ãã¦ã¯ãªãã¾ãããä¸èªç±ãªã½ããã¦ã§ã¢ã«ã¤ãã¦ã¯ããªãã¸ããªãportããã£ã¦ã¯ãªãã¾ãããã¾ãããã®ãã£ã¹ããªãã¥ã¼ã·ã§ã³ã¯ãèªç±ã½ããã¦ã§ã¢ã
ããå«ãã¨å
¬ç´ããããã®ã§ãªã第ä¸è
ã®ãªãã¸ããªãåç
§ãããã¨ããã£ã¦ã¯ãªãã¾ããã(ä»æ¥ããããèªç±ã½ããã¦ã§ã¢ã
ããä¿æããã®ã§ãã£ã¦ããææ¥ã«ã¯ãããçå®ã§ã¯ãªãããç¥ãã¾ããã)ã·ã¹ãã
ã«ãããããã°ã©ã
ã¯ãä¸èªç±ãªãã©ã°ã¤ã³ãããã¥ã¡ã³ããªã©ãã¤ã³ã¹ãã¼ã«ãããã¨ãææ¡ãã¦ã¯ããã¾ããã</p>
+<p>èªç±ãªã·ã¹ãã
ã»ãã£ã¹ããªãã¥ã¼ã·ã§ã³ã¯ãå®éã®ä½¿ç¨ã®æ
å
±ã«ã¤ãã¦ãä¸èªç±ãªãã®ãå
¥æããããã«æ¡å
ãããããããããã¨ãæ¨å¥¨ãã¦ã¯ãªãã¾ãããã·ã¹ãã
ã«ã¯ãä¸èªç±ãªã½ããã¦ã§ã¢ã«ã¤ãã¦ã®ãªãã¸ããªãæã¤ã¹ãã§ã¯ãªããç¹å®ã®ä¸èªç±ãªããã°ã©ã
ã®ã¤ã³ã¹ãã¼ã«æ¹æ³ã®ã¬ã·ããæã¤ã¹ãã§ã¯ããã¾ãããã¾ãããã®ãã£ã¹ããªãã¥ã¼ã·ã§ã³ã¯ãèªç±ã½ããã¦ã§ã¢ã
ããå«ãã¨å
¬ç´ããããã®ã§ãªã第ä¸è
ã®ãªãã¸ããªãåç
§ãããã¨ããã£ã¦ã¯ãªãã¾ããã(ä»æ¥ããããèªç±ã½ããã¦ã§ã¢ã
ããä¿æããã®ã§ãã£ã¦ããææ¥ã«ã¯ãããçå®ã§ã¯ãªãããç¥ãã¾ããã)ã·ã¹ãã
ã«ãããããã°ã©ã
ã¯ãä¸èªç±ãªãã©ã°ã¤ã³ãããã¥ã¡ã³ããªã©ãã¤ã³ã¹ãã¼ã«ãããã¨ãææ¡ãã¦ã¯ããã¾ããã</p>
<p>èªç±ãªã·ã¹ãã
ã»ãã£ã¹ããªãã¥ã¼ã·ã§ã³ã¯ãã»ã«ããã¹ãã£ã³ã°ã§ããã¹ãã§ããããã¯ãã·ã¹ãã
ãæä¾ãããã¼ã«ã«ãã£ã¦ãã®ã·ã¹ãã
ãéçºãæ§ç¯ã§ããªããã°ãªããªããã¨ãæå³ãã¾ããçµæã¨ãã¦ãèªç±ãªã·ã¹ãã
ã»ãã£ã¹ããªãã¥ã¼ã·ã§ã³ã¯ãä¸èªç±ãªã½ããã¦ã§ã¢ã使ããã¨ã«ãã£ã¦ã®ã¿æ§ç¯ã§ããèªç±ã½ããã¦ã§ã¢ãå«ããã¨ã¯ã§ããªããªãã¾ãã</p>
@@ -163,7 +163,7 @@
<p><!-- timestamp start -->
æçµæ´æ°:
-$Date: 2012/05/19 01:17:35 $
+$Date: 2012/06/05 08:26:58 $
<!-- timestamp end -->
</p>
Index: distros/po/free-system-distribution-guidelines.ja-en.html
===================================================================
RCS file:
/web/www/www/distros/po/free-system-distribution-guidelines.ja-en.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -b -r1.6 -r1.7
--- distros/po/free-system-distribution-guidelines.ja-en.html 19 May 2012
01:17:42 -0000 1.6
+++ distros/po/free-system-distribution-guidelines.ja-en.html 5 Jun 2012
08:27:23 -0000 1.7
@@ -56,7 +56,8 @@
<p>A free system distribution must not steer users towards obtaining
any nonfree information for practical use, or encourage them to do so.
-There should be no repositories or ports for nonfree software. Nor
+The system should have no repositories for nonfree software and no
+specific recipes for installation of particular nonfree programs. Nor
should the distribution refer to third-party repositories that are not
committed to only including free software; even if they only have free
software today, that may not be true tomorrow. Programs in the system
@@ -280,7 +281,7 @@
<p>Updated:
<!-- timestamp start -->
-$Date: 2012/05/19 01:17:42 $
+$Date: 2012/06/05 08:27:23 $
<!-- timestamp end -->
</p>
</div>
Index: distros/po/free-system-distribution-guidelines.ja.po
===================================================================
RCS file: /web/www/www/distros/po/free-system-distribution-guidelines.ja.po,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -b -r1.12 -r1.13
--- distros/po/free-system-distribution-guidelines.ja.po 5 Jun 2012
07:48:32 -0000 1.12
+++ distros/po/free-system-distribution-guidelines.ja.po 5 Jun 2012
08:27:26 -0000 1.13
@@ -123,15 +123,14 @@
"installing nonfree plugins, documentation, and so on."
msgstr ""
"èªç±ãªã·ã¹ãã
ã»ãã£ã¹ããªãã¥ã¼ã·ã§ã³ã¯ãå®éã®ä½¿ç¨ã®æ
å
±ã«ã¤ãã¦ãä¸èªç±ãª"
-"ãã®ãå
¥æããããã«æ¡å
ãããããããããã¨ãæ¨å¥¨ãã¦ã¯ãªãã¾ããã"
-"ã·ã¹ãã
ã«ã¯ãä¸èªç±ãªã½ããã¦ã§ã¢ã«ã¤ãã¦ã®ãªãã¸ããªãæã¤ã¹ãã§ã¯ãªãã"
-"ç¹å®ã®ä¸èªç±ãªããã°ã©ã
ã®ã¤ã³ã¹ãã¼ã«æ¹æ³ã®ã¬ã·ããæã¤ã¹ãã§ã¯ããã¾ããã"
-"ã¾ãããã®ãã£"
-"ã¹ããªãã¥ã¼ã·ã§ã³ã¯ãèªç±ã½ããã¦ã§ã¢ã ããå«ãã¨å
¬ç´ããããã®ã§ãªã第ä¸è
"
-"ã®ãªãã¸ããªãåç
§ãããã¨ããã£ã¦ã¯ãªãã¾ããã(ä»æ¥ããããèªç±ã½ããã¦ã§ã¢"
-"ã
ããä¿æããã®ã§ãã£ã¦ããææ¥ã«ã¯ãããçå®ã§ã¯ãªãããç¥ãã¾ããã)ã·ã¹ã"
-"ã ã«ãããããã°ã©ã
ã¯ãä¸èªç±ãªãã©ã°ã¤ã³ãããã¥ã¡ã³ããªã©ãã¤ã³ã¹ãã¼ã«ã"
-"ããã¨ãææ¡ãã¦ã¯ããã¾ããã"
+"ãã®ãå
¥æããããã«æ¡å
ãããããããããã¨ãæ¨å¥¨ãã¦ã¯ãªãã¾ãããã·ã¹ãã "
+"ã«ã¯ãä¸èªç±ãªã½ããã¦ã§ã¢ã«ã¤ãã¦ã®ãªãã¸ããªãæã¤ã¹ãã§ã¯ãªããç¹å®ã®ä¸èª"
+"ç±ãªããã°ã©ã
ã®ã¤ã³ã¹ãã¼ã«æ¹æ³ã®ã¬ã·ããæã¤ã¹ãã§ã¯ããã¾ãããã¾ãããã®"
+"ãã£ã¹ããªãã¥ã¼ã·ã§ã³ã¯ãèªç±ã½ããã¦ã§ã¢ã
ããå«ãã¨å
¬ç´ããããã®ã§ãªã第"
+"ä¸è
ã®ãªãã¸ããªãåç
§ãããã¨ããã£ã¦ã¯ãªãã¾ããã(ä»æ¥ããããèªç±ã½ãã"
+"ã¦ã§ã¢ã
ããä¿æããã®ã§ãã£ã¦ããææ¥ã«ã¯ãããçå®ã§ã¯ãªãããç¥ãã¾ããã)"
+"ã·ã¹ãã ã«ãããããã°ã©ã
ã¯ãä¸èªç±ãªãã©ã°ã¤ã³ãããã¥ã¡ã³ããªã©ãã¤ã³ã¹"
+"ãã¼ã«ãããã¨ãææ¡ãã¦ã¯ããã¾ããã"
#. type: Content of: <p>
msgid ""
Index: licenses/old-licenses/po/gpl-2.0-faq.translist
===================================================================
RCS file: /web/www/www/licenses/old-licenses/po/gpl-2.0-faq.translist,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -b -r1.5 -r1.6
--- licenses/old-licenses/po/gpl-2.0-faq.translist 11 Mar 2012 11:53:01
-0000 1.5
+++ licenses/old-licenses/po/gpl-2.0-faq.translist 5 Jun 2012 08:28:07
-0000 1.6
@@ -22,6 +22,8 @@
<li><a
href="/licenses/old-licenses/gpl-2.0-faq.pl.html">polski</a> [pl]</li>
<!-- Brazilian Portuguese -->
<li><a href="/licenses/old-licenses/gpl-2.0-faq.pt-br.html">português do
Brasil</a> [pt-br]</li>
+<!-- Russian -->
+<li><a
href="/licenses/old-licenses/gpl-2.0-faq.ru.html">ÑÑÑÑкий</a> [ru]</li>
</ul>
</div> <!-- id="translations" -->
<div class="netscape4" id="skiptrans"></div>
Index: philosophy/po/kevin-cole-response.de.po
===================================================================
RCS file: /web/www/www/philosophy/po/kevin-cole-response.de.po,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- philosophy/po/kevin-cole-response.de.po 2 May 2012 00:45:45 -0000
1.9
+++ philosophy/po/kevin-cole-response.de.po 5 Jun 2012 08:28:17 -0000
1.10
@@ -6,17 +6,22 @@
msgid ""
msgstr ""
"Project-Id-Version: kevin-cole-response.html\n"
-"POT-Creation-Date: 2011-09-20 12:29-0300\n"
+"POT-Creation-Date: 2012-06-05 04:25-0300\n"
"PO-Revision-Date: 2012-02-12 20:39+0100\n"
"Last-Translator: Wesley Kohne <address@hidden>\n"
"Language-Team: German <address@hidden>\n"
-"Language: de\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8-bit\n"
+"Outdated-Since: 2012-06-05 04:25-0300\n"
+"Language: de\n"
-#. type: Content of: <h2>
-msgid "A Response Letter to the Word Attachments"
+#. type: Content of: <title>
+#, fuzzy
+#| msgid "A Response Letter to the Word Attachments"
+msgid ""
+"A Response Letter to the Word Attachments - GNU Project - Free Software "
+"Foundation"
msgstr "Eine Antwort auf Word-Anlagen"
#. type: Attribute 'content' of: <meta>
@@ -26,6 +31,10 @@
"word attachment, microsoft"
msgstr " "
+#. type: Content of: <h2>
+msgid "A Response Letter to the Word Attachments"
+msgstr "Eine Antwort auf Word-Anlagen"
+
#. type: Content of: <p>
msgid "This is an automatic message:"
msgstr "Diese Nachricht wurde automatisch versendet:"
@@ -98,32 +107,59 @@
#. type: Content of: <div><p>
msgid ""
-"Please send FSF & GNU inquiries to <a href=\"mailto:address@hidden";
-"\"><em>address@hidden</em></a>. There are also <a href=\"/contact/\">other "
-"ways to contact</a> the FSF."
+"Please send general FSF & GNU inquiries to <a
href=\"mailto:address@hidden";
+"\"><address@hidden></a>. There are also <a href=\"/contact/\">other
ways "
+"to contact</a> the FSF. Broken links and other corrections or suggestions "
+"can be sent to <a href=\"mailto:address@hidden";><address@hidden"
+"org></a>."
msgstr ""
"Bitte senden Sie Fragen zur FSF & GNU an <a href=\"mailto:address@hidden";
"\"><address@hidden></a>. Sie können auch die <a
href=\"/contact/\">Free "
-"Software Foundation kontaktieren</a>."
-
+"Software Foundation kontaktieren</a>. Ungültige Verweise und andere "
+"Korrekturen oder Vorschläge können an <a href=\"mailto:address@hidden";
+"org\"><address@hidden></a> gesendet werden."
+
+#. TRANSLATORS: Ignore the original text in this paragraph,
+#. replace it with the translation of these two:
+#. We work hard and do our best to provide accurate, good quality
+#. translations. However, we are not exempt from imperfection.
+#. Please send your comments and general suggestions in this regard
+#. to <a href="mailto:address@hidden";>
+#. <address@hidden></a>.</p>
+#. <p>For information on coordinating and submitting translations of
+#. our web pages, see <a
+#. href="/server/standards/README.translations.html">Translations
+#. README</a>.
#. type: Content of: <div><p>
msgid ""
-"Please send broken links and other corrections or suggestions to <a href="
-"\"mailto:address@hidden";><em>address@hidden</em></a>."
+"For information on coordinating and submitting translations of this article, "
+"see <a href=\"/server/standards/README.translations.html\">Translations "
+"README</a>."
+msgstr ""
+"Bei der Ãbersetzung dieses Werkes wurde mit gröÃter Sorgfalt vorgegangen. "
+"Trotzdem können Fehler nicht völlig ausgeschlossen werden. Sollten Sie "
+"Fehler bemerken oder Vorschläge, Kommentare oder Anfragen zu dieser Webseite
"
+"haben, kontaktieren Sie bitte unser Ãbersetzungsteam <a href=\"mailto:web-";
+"address@hidden@gnu.org\"><address@hidden"
+"org></a>.</p>\n"
+"<p>Weitere Informationen über die Koordinierung und Einsendung von "
+"Ãbersetzungen unserer Webseiten finden Sie in der <a href=\"/server/"
+"standards/README.translations\">LIESMICH für Ãbersetzungen</a>."
+
+#. type: Content of: <div><p>
+msgid "Copyright © 2003 Kevin Cole"
msgstr ""
-"Bitte senden Sie ungültige Verweise und andere Korrekturen oder Vorschläge "
-"an <a href=\"mailto:address@hidden";><address@hidden>"
-"</a>."
#. type: Content of: <div><p>
msgid ""
-"Please see the <a href=\"/server/standards/README.translations.html"
-"\">Translations README</a> for information on coordinating and submitting "
-"translations of this article."
-msgstr ""
-"Bitte beachten Sie die <a href=\"/server/standards/README.translations"
-"\">LIESMICH für Ãbersetzungen</a>, um weitere Informationen über die "
-"Koordinierung und Einsendung von Ãbersetzungen zu erhalten."
+"This page is licensed under a <a rel=\"license\" href=\"http://";
+"creativecommons.org/licenses/by-nd/3.0/us/\">Creative Commons Attribution-"
+"NoDerivs 3.0 United States License</a>."
+msgstr ""
+"Dieses Werk steht unter einer <a rel=\"license\" href=\"http://";
+"creativecommons.org/licenses/by-nd/3.0/us/deed.de\">Creative Commons "
+"Namensnennung-Keine Bearbeitung 3.0 Vereinigte Staaten von Amerika Lizenz</"
+"a>."
# <strong>UÌbersetzung:</strong> Wesley Kohne, 2011, 2012.
#. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.
Index: philosophy/po/kevin-cole-response.fr.po
===================================================================
RCS file: /web/www/www/philosophy/po/kevin-cole-response.fr.po,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -b -r1.12 -r1.13
--- philosophy/po/kevin-cole-response.fr.po 20 May 2012 20:04:12 -0000
1.12
+++ philosophy/po/kevin-cole-response.fr.po 5 Jun 2012 08:28:18 -0000
1.13
@@ -8,18 +8,25 @@
msgid ""
msgstr ""
"Project-Id-Version: kevin-cole-response.html\n"
-"POT-Creation-Date: 2012-05-18 20:30-0300\n"
+"POT-Creation-Date: 2012-06-05 04:25-0300\n"
"PO-Revision-Date: 2012-05-15 16:37+0200\n"
"Last-Translator: Thérèse Godefroy <godef.th AT free.fr>\n"
"Language-Team: French <address@hidden>\n"
-"Language: fr\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"Outdated-Since: 2012-06-05 04:25-0300\n"
+"Language: fr\n"
"Plural-Forms: \n"
-#. type: Content of: <h2>
-msgid "A Response Letter to the Word Attachments"
+#. type: Content of: <title>
+# | A Response Letter to the Word Attachments {+- GNU Project - Free Software
+# | Foundation+}
+#, fuzzy
+#| msgid "A Response Letter to the Word Attachments"
+msgid ""
+"A Response Letter to the Word Attachments - GNU Project - Free Software "
+"Foundation"
msgstr "Une lettre de réponse aux pièces jointes Word"
#. type: Attribute 'content' of: <meta>
@@ -32,6 +39,10 @@
"licence générale publique, liberté, logiciel, pouvoir, droits, pièces "
"jointes, word, microsoft"
+#. type: Content of: <h2>
+msgid "A Response Letter to the Word Attachments"
+msgstr "Une lettre de réponse aux pièces jointes Word"
+
#. type: Content of: <p>
msgid "This is an automatic message:"
msgstr "Ceci est un message automatique :"
@@ -106,33 +117,76 @@
msgstr " "
#. type: Content of: <div><p>
-msgid ""
-"Please send FSF & GNU inquiries to <a href=\"mailto:address@hidden";
-"\"><em>address@hidden</em></a>. There are also <a href=\"/contact/\">other "
-"ways to contact</a> the FSF."
+# || No change detected. The change might only be in amounts of spaces.
+#, fuzzy
+#| msgid ""
+#| "Please send general FSF & GNU inquiries to <a
href=\"mailto:address@hidden";
+#| "org\"><address@hidden></a>. There are also <a href=\"/contact/"
+#| "\">other ways to contact</a> the FSF. Broken links and other corrections "
+#| "or suggestions can be sent to <a href=\"mailto:address@hidden";><"
+#| "address@hidden></a>."
+msgid ""
+"Please send general FSF & GNU inquiries to <a
href=\"mailto:address@hidden";
+"\"><address@hidden></a>. There are also <a href=\"/contact/\">other
ways "
+"to contact</a> the FSF. Broken links and other corrections or suggestions "
+"can be sent to <a href=\"mailto:address@hidden";><address@hidden"
+"org></a>."
msgstr ""
"Veuillez envoyer les requêtes concernant la FSF et GNU à <a href=\"mailto:";
"address@hidden"><address@hidden></a>. Il existe aussi <a
href=\"/contact/"
-"\">d'autres moyens de contacter</a> la FSF."
-
+"\">d'autres moyens de contacter</a> la FSF. Les liens orphelins et autres "
+"corrections ou suggestions peuvent être signalés à <a href=\"mailto:";
+"address@hidden"><address@hidden></a>."
+
+#
+#
+#
+#. TRANSLATORS: Ignore the original text in this paragraph,
+#. replace it with the translation of these two:
+#. We work hard and do our best to provide accurate, good quality
+#. translations. However, we are not exempt from imperfection.
+#. Please send your comments and general suggestions in this regard
+#. to <a href="mailto:address@hidden";>
+#. <address@hidden></a>.</p>
+#. <p>For information on coordinating and submitting translations of
+#. our web pages, see <a
+#. href="/server/standards/README.translations.html">Translations
+#. README</a>.
#. type: Content of: <div><p>
-msgid ""
-"Please send broken links and other corrections or suggestions to <a href="
-"\"mailto:address@hidden";><em>address@hidden</em></a>."
+# || No change detected. The change might only be in amounts of spaces.
+#, fuzzy
+#| msgid ""
+#| "For information on coordinating and submitting translations of this "
+#| "article, see <a href=\"/server/standards/README.translations.html"
+#| "\">Translations README</a>."
+msgid ""
+"For information on coordinating and submitting translations of this article, "
+"see <a href=\"/server/standards/README.translations.html\">Translations "
+"README</a>."
msgstr ""
-"Veuillez indiquer (en anglais) les liens orphelins et autres corrections ou "
-"suggestions à <a href=\"mailto:address@hidden";><em>address@hidden</"
-"em></a>."
+"Veuillez consulter le <a href=\"/server/standards/README.translations.html"
+"\">README des traductions</a> pour toute information sur la coordination et "
+"la soumission de traductions de cet article."
#. type: Content of: <div><p>
-msgid ""
-"Please see the <a href=\"/server/standards/README.translations.html"
-"\">Translations README</a> for information on coordinating and submitting "
-"translations of this article."
+msgid "Copyright © 2003 Kevin Cole"
msgstr ""
-"Veuillez consulter le <a href=\"/server/standards/README.translations.html"
-"\">README des traductions</a> pour des informations sur la coordination et "
-"la soumission de traductions de cet article."
+
+#. type: Content of: <div><p>
+# || No change detected. The change might only be in amounts of spaces.
+#, fuzzy
+#| msgid ""
+#| "This page is licensed under a <a rel=\"license\" href=\"http://";
+#| "creativecommons.org/licenses/by-nd/3.0/us/\">Creative Commons Attribution-"
+#| "NoDerivs 3.0 United States License</a>."
+msgid ""
+"This page is licensed under a <a rel=\"license\" href=\"http://";
+"creativecommons.org/licenses/by-nd/3.0/us/\">Creative Commons Attribution-"
+"NoDerivs 3.0 United States License</a>."
+msgstr ""
+"Cette page peut être utilisée suivant les conditions de la licence <a rel="
+"\"license\" href=\"http://creativecommons.org/licenses/by-nd/3.0/us/";
+"\">Creative Commons Attribution-NoDerivs 3.0 United States</a>."
#. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.
#. type: Content of: <div><div>
@@ -145,3 +199,29 @@
#. type: Content of: <div><p>
msgid "Updated:"
msgstr "Dernière mise à jour :"
+
+#~ msgid ""
+#~ "Please send FSF & GNU inquiries to <a href=\"mailto:address@hidden";
+#~ "\"><em>address@hidden</em></a>. There are also <a
href=\"/contact/\">other "
+#~ "ways to contact</a> the FSF."
+#~ msgstr ""
+#~ "Veuillez envoyer les requêtes concernant la FSF et GNU à <a
href=\"mailto:";
+#~ "address@hidden"><address@hidden></a>. Il existe aussi <a
href=\"/contact/"
+#~ "\">d'autres moyens de contacter</a> la FSF."
+
+#~ msgid ""
+#~ "Please send broken links and other corrections or suggestions to <a href="
+#~ "\"mailto:address@hidden";><em>address@hidden</em></a>."
+#~ msgstr ""
+#~ "Veuillez indiquer (en anglais) les liens orphelins et autres corrections "
+#~ "ou suggestions à <a href=\"mailto:address@hidden";><em>address@hidden"
+#~ "org</em></a>."
+
+#~ msgid ""
+#~ "Please see the <a href=\"/server/standards/README.translations.html"
+#~ "\">Translations README</a> for information on coordinating and submitting "
+#~ "translations of this article."
+#~ msgstr ""
+#~ "Veuillez consulter le <a href=\"/server/standards/README.translations.html"
+#~ "\">README des traductions</a> pour des informations sur la coordination "
+#~ "et la soumission de traductions de cet article."
Index: philosophy/po/kevin-cole-response.pot
===================================================================
RCS file: /web/www/www/philosophy/po/kevin-cole-response.pot,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- philosophy/po/kevin-cole-response.pot 19 May 2012 01:31:06 -0000
1.4
+++ philosophy/po/kevin-cole-response.pot 5 Jun 2012 08:28:18 -0000
1.5
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: kevin-cole-response.html\n"
-"POT-Creation-Date: 2012-05-18 20:30-0300\n"
+"POT-Creation-Date: 2012-06-05 04:25-0300\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <address@hidden>\n"
"Language-Team: LANGUAGE <address@hidden>\n"
@@ -15,9 +15,10 @@
"Content-Type: text/plain; charset=CHARSET\n"
"Content-Transfer-Encoding: ENCODING"
-#. type: Content of: <h2>
-#:
-msgid "A Response Letter to the Word Attachments"
+#. type: Content of: <title>
+msgid ""
+"A Response Letter to the Word Attachments - GNU Project - Free Software "
+"Foundation"
msgstr ""
#. type: Attribute 'content' of: <meta>
@@ -27,6 +28,10 @@
"word attachment, microsoft"
msgstr ""
+#. type: Content of: <h2>
+msgid "A Response Letter to the Word Attachments"
+msgstr ""
+
#. type: Content of: <p>
msgid "This is an automatic message:"
msgstr ""
@@ -77,22 +82,43 @@
#. type: Content of: <div><p>
msgid ""
-"Please send FSF & GNU inquiries to <a "
-"href=\"mailto:address@hidden";><em>address@hidden</em></a>. There are also <a
"
-"href=\"/contact/\">other ways to contact</a> the FSF."
+"Please send general FSF & GNU inquiries to <a "
+"href=\"mailto:address@hidden";><address@hidden></a>. There are also <a "
+"href=\"/contact/\">other ways to contact</a> the FSF. Broken links and "
+"other corrections or suggestions can be sent to <a "
+"href=\"mailto:address@hidden";><address@hidden></a>."
+msgstr ""
+
+#. TRANSLATORS: Ignore the original text in this paragraph,
+#. replace it with the translation of these two:
+#
+#. We work hard and do our best to provide accurate, good quality
+#. translations. However, we are not exempt from imperfection.
+#. Please send your comments and general suggestions in this regard
+#. to <a href="mailto:address@hidden";>
+#
+#. <address@hidden></a>.</p>
+#
+#. <p>For information on coordinating and submitting translations of
+#. our web pages, see <a
+#. href="/server/standards/README.translations.html">Translations
+#. README</a>.
+#. type: Content of: <div><p>
+msgid ""
+"For information on coordinating and submitting translations of this article, "
+"see <a href=\"/server/standards/README.translations.html\">Translations "
+"README</a>."
msgstr ""
#. type: Content of: <div><p>
-msgid ""
-"Please send broken links and other corrections or suggestions to <a "
-"href=\"mailto:address@hidden";><em>address@hidden</em></a>."
+msgid "Copyright © 2003 Kevin Cole"
msgstr ""
#. type: Content of: <div><p>
msgid ""
-"Please see the <a "
-"href=\"/server/standards/README.translations.html\">Translations README</a> "
-"for information on coordinating and submitting translations of this article."
+"This page is licensed under a <a rel=\"license\" "
+"href=\"http://creativecommons.org/licenses/by-nd/3.0/us/\";>Creative Commons "
+"Attribution-NoDerivs 3.0 United States License</a>."
msgstr ""
#. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.
Index: philosophy/po/sylvester-response.de.po
===================================================================
RCS file: /web/www/www/philosophy/po/sylvester-response.de.po,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- philosophy/po/sylvester-response.de.po 22 May 2012 08:28:18 -0000
1.2
+++ philosophy/po/sylvester-response.de.po 5 Jun 2012 08:28:18 -0000
1.3
@@ -7,17 +7,22 @@
msgid ""
msgstr ""
"Project-Id-Version: sylvester-response.html\n"
-"POT-Creation-Date: 2012-05-18 20:32-0300\n"
+"POT-Creation-Date: 2012-06-05 04:25-0300\n"
"PO-Revision-Date: 2012-05-21 18:24+0200\n"
"Last-Translator: Joerg Kohne <joeko (AT) online [PUNKT] de>\n"
"Language-Team: Deutsch <address@hidden>\n"
-"Language: de\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"Outdated-Since: 2012-06-05 04:25-0300\n"
+"Language: de\n"
-#. type: Content of: <h2>
-msgid "A Response Letter to the Word Attachments"
+#. type: Content of: <title>
+#, fuzzy
+#| msgid "A Response Letter to the Word Attachments"
+msgid ""
+"A Response Letter to the Word Attachments - GNU Project - Free Software "
+"Foundation"
msgstr "Eine Antwort auf Word-Anhänge"
#. type: Attribute 'content' of: <meta>
@@ -33,6 +38,10 @@
"describes what you can do to help stop this practice."
msgstr " "
+#. type: Content of: <h2>
+msgid "A Response Letter to the Word Attachments"
+msgstr "Eine Antwort auf Word-Anhänge"
+
#. type: Content of: <p>
msgid "From: The Reverend Father Martin Sylvester"
msgstr "Von: The Reverend Father Martin Sylvester"
@@ -73,11 +82,16 @@
"möglicherweise überhaupt nicht lesen."
#. type: Content of: <p>
+#, fuzzy
+#| msgid ""
+#| "Receiving Word attachments is not good for you because they can carry "
+#| "viruses: see <a href=\"http://www.viruslist.com/en/virusesdescribed?";
+#| "chapter=153313603\"> http://www.viruslist.com/en/virusesdescribed?";
+#| "chapter=153313603</a>."
msgid ""
"Receiving Word attachments is not good for you because they can carry "
-"viruses: see <a href=\"http://www.viruslist.com/en/virusesdescribed?";
-"chapter=153313603\"> http://www.viruslist.com/en/virusesdescribed?";
-"chapter=153313603</a>."
+"viruses: see <a href=\"http://en.wikipedia.org/wiki/Macro_virus_(computing)"
+"\"> http://en.wikipedia.org/wiki/Macro_virus_(computing)</a>."
msgstr ""
"Empfangen von Word-Anhängen ist nicht gut für Sie, weil sie Viren enthalten
"
"können: siehe <a href=\"http://www.viruslist.com/en/virusesdescribed?";
@@ -266,6 +280,18 @@
"Dokumenttyp entsprechend Nur Text- oder RTF-Dokument."
#. type: Content of: <p>
+#, fuzzy
+#| msgid ""
+#| "Your computer may also have a program to convert to the PDF (or Adobe "
+#| "Acrobat) format, which was designed to make sure that when someone else "
+#| "views your document, it looks exactly the same on their computer as it "
+#| "did on yours. Select File => Print. Scroll through available printers "
+#| "and select the pdf converter. Click on the Print button and enter a name "
+#| "for the pdf file when requested, then attach that file to your email. "
+#| "There are some cheap or even free programs to make PDF files: use the "
+#| "search function at <a href=\"http://www.download.com/\";>http://www.";
+#| "download.com/</a> or <a href=\"http://www.tucows.com/\";>http://www.tucows.";
+#| "com/</a> to find them."
msgid ""
"Your computer may also have a program to convert to the PDF (or Adobe "
"Acrobat) format, which was designed to make sure that when someone else "
@@ -274,8 +300,8 @@
"select the pdf converter. Click on the Print button and enter a name for "
"the pdf file when requested, then attach that file to your email. There are "
"some cheap or even free programs to make PDF files: use the search function "
-"at <a href=\"http://www.download.com/\";>http://www.download.com/</a> or <a "
-"href=\"http://www.tucows.com/\";>http://www.tucows.com/</a> to find them."
+"at <a href=\"http://directory.fsf.org/\";>http://directory.fsf.org/</a> to "
+"find them."
msgstr ""
"Auf Ihrem Rechner ist vielleicht auch ein Programm vorhanden, um Dokumente "
"ins PDF (oder Adobe Acrobat)-Format zu konvertieren, das entwickelt wurde, "
@@ -319,32 +345,59 @@
#. type: Content of: <div><p>
msgid ""
-"Please send FSF & GNU inquiries to <a href=\"mailto:address@hidden";
-"\"><em>address@hidden</em></a>. There are also <a href=\"/contact/\">other "
-"ways to contact</a> the FSF."
+"Please send general FSF & GNU inquiries to <a
href=\"mailto:address@hidden";
+"\"><address@hidden></a>. There are also <a href=\"/contact/\">other
ways "
+"to contact</a> the FSF. Broken links and other corrections or suggestions "
+"can be sent to <a href=\"mailto:address@hidden";><address@hidden"
+"org></a>."
msgstr ""
"Bitte senden Sie Fragen zur FSF & GNU an <a href=\"mailto:address@hidden";
"\"><address@hidden></a>. Sie können auch die <a
href=\"/contact/\">Free "
-"Software Foundation kontaktieren</a>."
-
+"Software Foundation kontaktieren</a>. Ungültige Verweise und andere "
+"Korrekturen oder Vorschläge können an <a href=\"mailto:address@hidden";
+"org\"><address@hidden></a> gesendet werden."
+
+#. TRANSLATORS: Ignore the original text in this paragraph,
+#. replace it with the translation of these two:
+#. We work hard and do our best to provide accurate, good quality
+#. translations. However, we are not exempt from imperfection.
+#. Please send your comments and general suggestions in this regard
+#. to <a href="mailto:address@hidden";>
+#. <address@hidden></a>.</p>
+#. <p>For information on coordinating and submitting translations of
+#. our web pages, see <a
+#. href="/server/standards/README.translations.html">Translations
+#. README</a>.
#. type: Content of: <div><p>
msgid ""
-"Please send broken links and other corrections or suggestions to <a href="
-"\"mailto:address@hidden";><em>address@hidden</em></a>."
+"For information on coordinating and submitting translations of this article, "
+"see <a href=\"/server/standards/README.translations.html\">Translations "
+"README</a>."
+msgstr ""
+"Bei der Ãbersetzung dieses Werkes wurde mit gröÃter Sorgfalt vorgegangen. "
+"Trotzdem können Fehler nicht völlig ausgeschlossen werden. Sollten Sie "
+"Fehler bemerken oder Vorschläge, Kommentare oder Anfragen zu dieser Webseite
"
+"haben, kontaktieren Sie bitte unser Ãbersetzungsteam <a href=\"mailto:web-";
+"address@hidden@gnu.org\"><address@hidden"
+"org></a>.</p>\n"
+"<p>Weitere Informationen über die Koordinierung und Einsendung von "
+"Ãbersetzungen unserer Webseiten finden Sie in der <a href=\"/server/"
+"standards/README.translations\">LIESMICH für Ãbersetzungen</a>."
+
+#. type: Content of: <div><p>
+msgid "Copyright © 2004 Martin Sylvester"
msgstr ""
-"Bitte senden Sie ungültige Verweise und andere Korrekturen oder Vorschläge "
-"an <a href=\"mailto:address@hidden";><address@hidden>"
-"</a>."
#. type: Content of: <div><p>
msgid ""
-"Please see the <a href=\"/server/standards/README.translations.html"
-"\">Translations README</a> for information on coordinating and submitting "
-"translations of this article."
-msgstr ""
-"Bitte beachten Sie die <a href=\"/server/standards/README.translations"
-"\">LIESMICH für Ãbersetzungen</a>, um weitere Informationen über die "
-"Koordinierung und Einsendung von Ãbersetzungen zu erhalten."
+"This page is licensed under a <a rel=\"license\" href=\"http://";
+"creativecommons.org/licenses/by-nd/3.0/us/\">Creative Commons Attribution-"
+"NoDerivs 3.0 United States License</a>."
+msgstr ""
+"Dieses Werk steht unter einer <a rel=\"license\" href=\"http://";
+"creativecommons.org/licenses/by-nd/3.0/us/deed.de\">Creative Commons "
+"Namensnennung-Keine Bearbeitung 3.0 Vereinigte Staaten von Amerika Lizenz</"
+"a>."
#. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.
#. type: Content of: <div><div>
Index: philosophy/po/sylvester-response.fr.po
===================================================================
RCS file: /web/www/www/philosophy/po/sylvester-response.fr.po,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -b -r1.17 -r1.18
--- philosophy/po/sylvester-response.fr.po 20 May 2012 20:04:18 -0000
1.17
+++ philosophy/po/sylvester-response.fr.po 5 Jun 2012 08:28:19 -0000
1.18
@@ -7,18 +7,25 @@
msgid ""
msgstr ""
"Project-Id-Version: sylvester-response.html\n"
-"POT-Creation-Date: 2012-05-18 20:32-0300\n"
+"POT-Creation-Date: 2012-06-05 04:25-0300\n"
"PO-Revision-Date: 2012-05-17 21:15+0200\n"
"Last-Translator: Thérèse Godefroy <godef.th AT free.fr>\n"
"Language-Team: French <address@hidden>\n"
-"Language: fr\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"Outdated-Since: 2012-06-05 04:25-0300\n"
+"Language: fr\n"
"Plural-Forms: \n"
-#. type: Content of: <h2>
-msgid "A Response Letter to the Word Attachments"
+#. type: Content of: <title>
+# | A Response Letter to the Word Attachments {+- GNU Project - Free Software
+# | Foundation+}
+#, fuzzy
+#| msgid "A Response Letter to the Word Attachments"
+msgid ""
+"A Response Letter to the Word Attachments - GNU Project - Free Software "
+"Foundation"
msgstr "Une lettre de réponse aux pièces jointes Word"
#. type: Attribute 'content' of: <meta>
@@ -40,6 +47,10 @@
"Microsoft Word avec les courriels, et décrit ce que vous pouvez faire pour "
"arrêter cette pratique."
+#. type: Content of: <h2>
+msgid "A Response Letter to the Word Attachments"
+msgstr "Une lettre de réponse aux pièces jointes Word"
+
#. type: Content of: <p>
msgid "From: The Reverend Father Martin Sylvester"
msgstr "De : Révérend Martin Sylvester"
@@ -80,11 +91,22 @@
"personnes pourraient même ne pas être capables de les lire du tout."
#. type: Content of: <p>
+# | Receiving Word attachments is not good for you because they can carry
+# | viruses: see <a
+# | [-href=\"http://www.viruslist.com/en/virusesdescribed?chapter=153313603\";>
+# | http://www.viruslist.com/en/virusesdescribed?chapter=153313603</a>.-]
+# | {+href=\"http://en.wikipedia.org/wiki/Macro_virus_(computing)\">
+# | http://en.wikipedia.org/wiki/Macro_virus_(computing)</a>.+}
+#, fuzzy
+#| msgid ""
+#| "Receiving Word attachments is not good for you because they can carry "
+#| "viruses: see <a href=\"http://www.viruslist.com/en/virusesdescribed?";
+#| "chapter=153313603\"> http://www.viruslist.com/en/virusesdescribed?";
+#| "chapter=153313603</a>."
msgid ""
"Receiving Word attachments is not good for you because they can carry "
-"viruses: see <a href=\"http://www.viruslist.com/en/virusesdescribed?";
-"chapter=153313603\"> http://www.viruslist.com/en/virusesdescribed?";
-"chapter=153313603</a>."
+"viruses: see <a href=\"http://en.wikipedia.org/wiki/Macro_virus_(computing)"
+"\"> http://en.wikipedia.org/wiki/Macro_virus_(computing)</a>."
msgstr ""
"Recevoir des pièces jointes Word n'est pas bon pour vous car elles peuvent "
"contenir des virus : voir <a href=\"http://www.viruslist.com/en/";
@@ -277,6 +299,30 @@
"« Document texte » (ou RTF ou Rich text Format) dans le type de document."
#. type: Content of: <p>
+# | Your computer may also have a program to convert to the PDF (or Adobe
+# | Acrobat) format, which was designed to make sure that when someone else
+# | views your document, it looks exactly the same on their computer as it did
+# | on yours. Select File => Print. Scroll through available printers and
+# | select the pdf converter. Click on the Print button and enter a name for
+# | the pdf file when requested, then attach that file to your email. There
+# | are some cheap or even free programs to make PDF files: use the search
+# | function at <a
+# | [-href=\"http://www.download.com/\";>http://www.download.com/</a> or <a
+# | href=\"http://www.tucows.com/\";>http://www.tucows.com/</a>-]
+# | {+href=\"http://directory.fsf.org/\";>http://directory.fsf.org/</a>+} to
+# | find them.
+#, fuzzy
+#| msgid ""
+#| "Your computer may also have a program to convert to the PDF (or Adobe "
+#| "Acrobat) format, which was designed to make sure that when someone else "
+#| "views your document, it looks exactly the same on their computer as it "
+#| "did on yours. Select File => Print. Scroll through available printers "
+#| "and select the pdf converter. Click on the Print button and enter a name "
+#| "for the pdf file when requested, then attach that file to your email. "
+#| "There are some cheap or even free programs to make PDF files: use the "
+#| "search function at <a href=\"http://www.download.com/\";>http://www.";
+#| "download.com/</a> or <a href=\"http://www.tucows.com/\";>http://www.tucows.";
+#| "com/</a> to find them."
msgid ""
"Your computer may also have a program to convert to the PDF (or Adobe "
"Acrobat) format, which was designed to make sure that when someone else "
@@ -285,8 +331,8 @@
"select the pdf converter. Click on the Print button and enter a name for "
"the pdf file when requested, then attach that file to your email. There are "
"some cheap or even free programs to make PDF files: use the search function "
-"at <a href=\"http://www.download.com/\";>http://www.download.com/</a> or <a "
-"href=\"http://www.tucows.com/\";>http://www.tucows.com/</a> to find them."
+"at <a href=\"http://directory.fsf.org/\";>http://directory.fsf.org/</a> to "
+"find them."
msgstr ""
"Votre ordinateur peut aussi contenir un programme pour convertir au format "
"PDF (ou Adobe Acrobat), qui a été conçu pour s'assurer que votre document "
@@ -329,33 +375,76 @@
msgstr " "
#. type: Content of: <div><p>
-msgid ""
-"Please send FSF & GNU inquiries to <a href=\"mailto:address@hidden";
-"\"><em>address@hidden</em></a>. There are also <a href=\"/contact/\">other "
-"ways to contact</a> the FSF."
+# || No change detected. The change might only be in amounts of spaces.
+#, fuzzy
+#| msgid ""
+#| "Please send general FSF & GNU inquiries to <a
href=\"mailto:address@hidden";
+#| "org\"><address@hidden></a>. There are also <a href=\"/contact/"
+#| "\">other ways to contact</a> the FSF. Broken links and other corrections "
+#| "or suggestions can be sent to <a href=\"mailto:address@hidden";><"
+#| "address@hidden></a>."
+msgid ""
+"Please send general FSF & GNU inquiries to <a
href=\"mailto:address@hidden";
+"\"><address@hidden></a>. There are also <a href=\"/contact/\">other
ways "
+"to contact</a> the FSF. Broken links and other corrections or suggestions "
+"can be sent to <a href=\"mailto:address@hidden";><address@hidden"
+"org></a>."
msgstr ""
"Veuillez envoyer les requêtes concernant la FSF et GNU à <a href=\"mailto:";
"address@hidden"><address@hidden></a>. Il existe aussi <a
href=\"/contact/"
-"\">d'autres moyens de contacter</a> la FSF."
-
+"\">d'autres moyens de contacter</a> la FSF. Les liens orphelins et autres "
+"corrections ou suggestions peuvent être signalés à <a href=\"mailto:";
+"address@hidden"><address@hidden></a>."
+
+#
+#
+#
+#. TRANSLATORS: Ignore the original text in this paragraph,
+#. replace it with the translation of these two:
+#. We work hard and do our best to provide accurate, good quality
+#. translations. However, we are not exempt from imperfection.
+#. Please send your comments and general suggestions in this regard
+#. to <a href="mailto:address@hidden";>
+#. <address@hidden></a>.</p>
+#. <p>For information on coordinating and submitting translations of
+#. our web pages, see <a
+#. href="/server/standards/README.translations.html">Translations
+#. README</a>.
#. type: Content of: <div><p>
-msgid ""
-"Please send broken links and other corrections or suggestions to <a href="
-"\"mailto:address@hidden";><em>address@hidden</em></a>."
+# || No change detected. The change might only be in amounts of spaces.
+#, fuzzy
+#| msgid ""
+#| "For information on coordinating and submitting translations of this "
+#| "article, see <a href=\"/server/standards/README.translations.html"
+#| "\">Translations README</a>."
+msgid ""
+"For information on coordinating and submitting translations of this article, "
+"see <a href=\"/server/standards/README.translations.html\">Translations "
+"README</a>."
msgstr ""
-"Veuillez indiquer (en anglais) les liens orphelins et autres corrections ou "
-"suggestions à <a href=\"mailto:address@hidden";><em>address@hidden</"
-"em></a>."
+"Veuillez consulter le <a href=\"/server/standards/README.translations.html"
+"\">README des traductions</a> pour toute information sur la coordination et "
+"la soumission de traductions de cet article."
#. type: Content of: <div><p>
-msgid ""
-"Please see the <a href=\"/server/standards/README.translations.html"
-"\">Translations README</a> for information on coordinating and submitting "
-"translations of this article."
+msgid "Copyright © 2004 Martin Sylvester"
msgstr ""
-"Veuillez consulter le <a href=\"/server/standards/README.translations.html"
-"\">README des traductions</a> pour des informations sur la coordination et "
-"la soumission de traductions de cet article."
+
+#. type: Content of: <div><p>
+# || No change detected. The change might only be in amounts of spaces.
+#, fuzzy
+#| msgid ""
+#| "This page is licensed under a <a rel=\"license\" href=\"http://";
+#| "creativecommons.org/licenses/by-nd/3.0/us/\">Creative Commons Attribution-"
+#| "NoDerivs 3.0 United States License</a>."
+msgid ""
+"This page is licensed under a <a rel=\"license\" href=\"http://";
+"creativecommons.org/licenses/by-nd/3.0/us/\">Creative Commons Attribution-"
+"NoDerivs 3.0 United States License</a>."
+msgstr ""
+"Cette page peut être utilisée suivant les conditions de la licence <a rel="
+"\"license\" href=\"http://creativecommons.org/licenses/by-nd/3.0/us/";
+"\">Creative Commons Attribution-NoDerivs 3.0 United States</a>."
#. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.
#. type: Content of: <div><div>
@@ -368,3 +457,29 @@
#. type: Content of: <div><p>
msgid "Last updated:"
msgstr "Dernière mise à jour :"
+
+#~ msgid ""
+#~ "Please send FSF & GNU inquiries to <a href=\"mailto:address@hidden";
+#~ "\"><em>address@hidden</em></a>. There are also <a
href=\"/contact/\">other "
+#~ "ways to contact</a> the FSF."
+#~ msgstr ""
+#~ "Veuillez envoyer les requêtes concernant la FSF et GNU à <a
href=\"mailto:";
+#~ "address@hidden"><address@hidden></a>. Il existe aussi <a
href=\"/contact/"
+#~ "\">d'autres moyens de contacter</a> la FSF."
+
+#~ msgid ""
+#~ "Please send broken links and other corrections or suggestions to <a href="
+#~ "\"mailto:address@hidden";><em>address@hidden</em></a>."
+#~ msgstr ""
+#~ "Veuillez indiquer (en anglais) les liens orphelins et autres corrections "
+#~ "ou suggestions à <a href=\"mailto:address@hidden";><em>address@hidden"
+#~ "org</em></a>."
+
+#~ msgid ""
+#~ "Please see the <a href=\"/server/standards/README.translations.html"
+#~ "\">Translations README</a> for information on coordinating and submitting "
+#~ "translations of this article."
+#~ msgstr ""
+#~ "Veuillez consulter le <a href=\"/server/standards/README.translations.html"
+#~ "\">README des traductions</a> pour des informations sur la coordination "
+#~ "et la soumission de traductions de cet article."
Index: philosophy/po/sylvester-response.pot
===================================================================
RCS file: /web/www/www/philosophy/po/sylvester-response.pot,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -b -r1.5 -r1.6
--- philosophy/po/sylvester-response.pot 19 May 2012 01:31:33 -0000
1.5
+++ philosophy/po/sylvester-response.pot 5 Jun 2012 08:28:19 -0000
1.6
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: sylvester-response.html\n"
-"POT-Creation-Date: 2012-05-18 20:32-0300\n"
+"POT-Creation-Date: 2012-06-05 04:25-0300\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <address@hidden>\n"
"Language-Team: LANGUAGE <address@hidden>\n"
@@ -15,9 +15,10 @@
"Content-Type: text/plain; charset=CHARSET\n"
"Content-Transfer-Encoding: ENCODING"
-#. type: Content of: <h2>
-#:
-msgid "A Response Letter to the Word Attachments"
+#. type: Content of: <title>
+msgid ""
+"A Response Letter to the Word Attachments - GNU Project - Free Software "
+"Foundation"
msgstr ""
#. type: Attribute 'content' of: <meta>
@@ -33,6 +34,10 @@
"describes what you can do to help stop this practice."
msgstr ""
+#. type: Content of: <h2>
+msgid "A Response Letter to the Word Attachments"
+msgstr ""
+
#. type: Content of: <p>
msgid "From: The Reverend Father Martin Sylvester"
msgstr ""
@@ -62,8 +67,8 @@
msgid ""
"Receiving Word attachments is not good for you because they can carry "
"viruses: see <a "
-"href=\"http://www.viruslist.com/en/virusesdescribed?chapter=153313603\";> "
-"http://www.viruslist.com/en/virusesdescribed?chapter=153313603</a>."
+"href=\"http://en.wikipedia.org/wiki/Macro_virus_(computing)\"> "
+"http://en.wikipedia.org/wiki/Macro_virus_(computing)</a>."
msgstr ""
#. type: Content of: <p>
@@ -184,8 +189,8 @@
"select the pdf converter. Click on the Print button and enter a name for "
"the pdf file when requested, then attach that file to your email. There are "
"some cheap or even free programs to make PDF files: use the search function "
-"at <a href=\"http://www.download.com/\";>http://www.download.com/</a> or <a "
-"href=\"http://www.tucows.com/\";>http://www.tucows.com/</a> to find them."
+"at <a href=\"http://directory.fsf.org/\";>http://directory.fsf.org/</a> to "
+"find them."
msgstr ""
#. type: Content of: <p>
@@ -211,22 +216,43 @@
#. type: Content of: <div><p>
msgid ""
-"Please send FSF & GNU inquiries to <a "
-"href=\"mailto:address@hidden";><em>address@hidden</em></a>. There are also <a
"
-"href=\"/contact/\">other ways to contact</a> the FSF."
+"Please send general FSF & GNU inquiries to <a "
+"href=\"mailto:address@hidden";><address@hidden></a>. There are also <a "
+"href=\"/contact/\">other ways to contact</a> the FSF. Broken links and "
+"other corrections or suggestions can be sent to <a "
+"href=\"mailto:address@hidden";><address@hidden></a>."
+msgstr ""
+
+#. TRANSLATORS: Ignore the original text in this paragraph,
+#. replace it with the translation of these two:
+#
+#. We work hard and do our best to provide accurate, good quality
+#. translations. However, we are not exempt from imperfection.
+#. Please send your comments and general suggestions in this regard
+#. to <a href="mailto:address@hidden";>
+#
+#. <address@hidden></a>.</p>
+#
+#. <p>For information on coordinating and submitting translations of
+#. our web pages, see <a
+#. href="/server/standards/README.translations.html">Translations
+#. README</a>.
+#. type: Content of: <div><p>
+msgid ""
+"For information on coordinating and submitting translations of this article, "
+"see <a href=\"/server/standards/README.translations.html\">Translations "
+"README</a>."
msgstr ""
#. type: Content of: <div><p>
-msgid ""
-"Please send broken links and other corrections or suggestions to <a "
-"href=\"mailto:address@hidden";><em>address@hidden</em></a>."
+msgid "Copyright © 2004 Martin Sylvester"
msgstr ""
#. type: Content of: <div><p>
msgid ""
-"Please see the <a "
-"href=\"/server/standards/README.translations.html\">Translations README</a> "
-"for information on coordinating and submitting translations of this article."
+"This page is licensed under a <a rel=\"license\" "
+"href=\"http://creativecommons.org/licenses/by-nd/3.0/us/\";>Creative Commons "
+"Attribution-NoDerivs 3.0 United States License</a>."
msgstr ""
#. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.
Index: server/sitemap.ja.html
===================================================================
RCS file: /web/www/www/server/sitemap.ja.html,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -b -r1.20 -r1.21
--- server/sitemap.ja.html 21 May 2012 08:29:04 -0000 1.20
+++ server/sitemap.ja.html 5 Jun 2012 08:28:35 -0000 1.21
@@ -1,9 +1,10 @@
<!--#include virtual="/server/header.ja.html" -->
+<!-- Parent-Version: 1.68 -->
<!-- This file is automatically generated by GNUnited Nations! -->
-<title>www.gnu.org ãµã¤ãããã - GNUããã¸ã§ã¯ã -
ããªã¼ã½ããã¦ã§ã¢ãã¡ã¦ã³ãã¼ã·ã§ã³ (FSF)</title>
+<title>www.gnu.org ãµã¤ãããã - GNUããã¸ã§ã¯ã -
ããªã¼ã½ããã¦ã§ã¢ãã¡ã¦ã³ãã¼ã·ã§ã³</title>
<style type="text/css">
.sitemap-directory { margin-left: 1.2em } .sitemap-directory-depth-0,
@@ -21,12 +22,9 @@
</style>
<!--#include virtual="/server/banner.ja.html" -->
+<!--#include virtual="/server/po/sitemap.translist" -->
<h2>www.gnu.orgãµã¤ãããã</h2>
-<!-- When you replace this graphic, make sure you change -->
-<!-- the link to also point to the correct HTML page. -->
-<!-- If you make a new graphic for this page, make sure it -->
-<!-- has a corresponding entry in /graphics/graphics.html. -->
<div class="sitemap-directory
sitemap-directory-depth-0"><div>[ãããã¬ãã«ã»ãã£ã¬ã¯ããª: <a
href="#directory-accessibility">ã¢ã¯ã»ã¹ããªãã£</a> <a
href="#directory-award">ã¢ã¯ã¼ã</a> <a href="#directory-bulletins">ä¼å
±</a> <a
href="#directory-contact">é£çµ¡å
</a> <a
href="#directory-copyleft">ã³ãã¼ã¬ãã</a>
@@ -298,9 +296,9 @@
<li><a href="/fun/jokes/doctor.manifesto.html">doctor.manifesto.html -
Dr. Emacsã¨GNU宣è¨</a></li>
<li><a href="/fun/jokes/echo-msg.html">echo-msg.html - GNU Echo</a></li>
- <li><a href="/fun/jokes/ed.html">ed.html -
edã®ã½ã¼ã¹ã³ã¼ã(?)</a></li>
- <li><a href="/fun/jokes/ed.msg.html">ed.msg.html - Ed, man! !man ed-
+ <li><a href="/fun/jokes/ed-msg.html">ed-msg.html - Ed, man! !man ed-
GNUããã¸ã§ã¯ã</a></li>
+ <li><a href="/fun/jokes/ed.html">ed.html -
edã®ã½ã¼ã¹ã³ã¼ã(?)</a></li>
<li><a href="/fun/jokes/errno.2.html">errno.2.html -
errno(2)ã³ã¼ã</a></li>
<li><a href="/fun/jokes/error-haiku.html">error-haiku.html -
ã¨ã©ã¼ã¡ãã»ã¼ã¸ã俳å¥ã§</a></li>
<li><a href="/fun/jokes/eternal-flame.html">eternal-flame.html - æ°¸é
ãªãç</a></li>
@@ -762,6 +760,8 @@
<li><a
href="/philosophy/android-and-users-freedom.html">android-and-users-freedom.html
- ã¢ã³ããã¤ãã¨å©ç¨è
ã®èªç±</a></li>
+ <li><a href="/philosophy/anonymous-response.html">anonymous-response.html -
+ã¯ã¼ãæ·»ä»ã¸ã®è¿ä¿¡</a></li>
<li><a href="/philosophy/apsl.html">apsl.html -
Appleãããªãã¯ã»ã½ã¼ã¹ã»ã©ã¤ã»ã³ã¹(APSL)ã«å¯¾ãã¦ã®FSFã®è¦è§£</a></li>
<li><a href="/philosophy/assigning-copyright.html">assigning-copyright.html -
@@ -937,8 +937,6 @@
href="/philosophy/open-source-misses-the-point.html">open-source-misses-the-point.html
-
ãªãããªã¼ãã³ã½ã¼ã¹ã¯èªç±ã½ããã¦ã§ã¢ã®çãå¤ãã®ã</a></li>
<li><a
href="/philosophy/opposing-drm.html">ãã¸ã¿ã«å¶é管çã«å対ãã</a></li>
- <li><a
href="/philosophy/papadopoulos-response.html">papadopoulos-response.html
-- ã¯ã¼ãæ·»ä»ã¸ã®å¯¾å¿ã®æç´</a></li>
<li><a
href="/philosophy/patent-practice-panel.html">patent-practice-panel.html
- Daniel Ravicherã®FFIIããã«è¨è«ã2004å¹´11æ10æ¥</a></li>
<li><a
@@ -1257,21 +1255,20 @@
<div id="directory-testimonials" class="sitemap-directory
sitemap-directory-depth-1">
<div class="sitemap-header"><a
href="/testimonials/testimonials.html">testimonials - GNUæ¨è¦æ</a></div>
<ul>
- <li><a href="/testimonials/reliable.html">reliable.html -
èªç±ã½ããã¦ã§ã¢ã¯ä¿¡é ¼ã§ãã -
-GNUæ¨è¦æ</a></li>
+ <li><a href="/testimonials/reliable.html">reliable.html -
èªç±ã½ããã¦ã§ã¢ã¯ä¿¡é ¼ã§ãã</a></li>
<li><a href="/testimonials/supported.html">supported.html -
èªç±ã½ããã¦ã§ã¢ã¯ãµãã¼ãããã¦ãã</a></li>
<li><a href="/testimonials/testimonial_cadcam.html">testimonial_cadcam.html -
-GNUæ¨è¦æ - CAD/CAMéçº</a></li>
+CAD/CAMéçº</a></li>
<li><a href="/testimonials/testimonial_HIRLAM.html">testimonial_HIRLAM.html -
-GNUæ¨è¦æ - HIRLAMã³ã³ã½ã¼ã·ã¢ã </a></li>
+HIRLAMã³ã³ã½ã¼ã·ã¢ã </a></li>
<li><a href="/testimonials/testimonial_media.html">testimonial_media.html -
-GNUæ¨è¦æ - Alexander Ewering</a></li>
+Alexander Ewering</a></li>
<li><a
href="/testimonials/testimonial_mondrup.html">testimonial_mondrup.html -
-GNUæ¨è¦æ - Christian Mondrup</a></li>
+Christian Mondrup</a></li>
<li><a
href="/testimonials/testimonial_research_ships.html">testimonial_research_ships.html
-- GNUæ¨è¦æ - Robert Harvey</a></li>
+- Robert Harvey</a></li>
<li><a href="/testimonials/useful.html">useful.html -
èªç±ã½ããã¦ã§ã¢ã¯å½¹ç«ã¡ã¾ã</a></li>
</ul>
</div>
@@ -1281,20 +1278,20 @@
<div id="directory-thankgnus" class="sitemap-directory
sitemap-directory-depth-1">
<div class="sitemap-header"><a href="/thankgnus/thankgnus.html">thankgnus -
Thank GNUs</a></div>
<ul>
- <li><a href="/thankgnus/1997supporters.html">1997supporters.html - Thanks
-GNUs</a></li>
- <li><a href="/thankgnus/1998supporters.html">1998supporters.html - Thanks
-GNUs</a></li>
+ <li><a href="/thankgnus/1997supporters.html">1997supporters.html - Thanks
GNUs
+1997</a></li>
+ <li><a href="/thankgnus/1998supporters.html">1998supporters.html - Thanks
GNUs
+1998</a></li>
<li><a href="/thankgnus/1999.html">1999.html - 1999å¹´FSFæ¯æè
</a></li>
- <li><a href="/thankgnus/1999supporters.html">1999supporters.html - Thanks
-GNUs</a></li>
- <li><a href="/thankgnus/2000supporters.html">2000supporters.html - Thanks
-GNUs</a></li>
- <li><a href="/thankgnus/2001supporters.html">2001supporters.html - Thanks
-GNUs</a></li>
- <li><a href="/thankgnus/2002supporters.html">2002supporters.html - Thanks
-GNUs</a></li>
- <li><a href="/thankgnus/2003supporters.html">2003supporters.html - Thank GNUs
+ <li><a href="/thankgnus/1999supporters.html">1999supporters.html - Thanks
GNUs
+1999</a></li>
+ <li><a href="/thankgnus/2000supporters.html">2000supporters.html - Thanks
GNUs
+2000</a></li>
+ <li><a href="/thankgnus/2001supporters.html">2001supporters.html - Thanks
GNUs
+2001</a></li>
+ <li><a href="/thankgnus/2002supporters.html">2002supporters.html - Thanks
GNUs
+2002</a></li>
+ <li><a href="/thankgnus/2003supporters.html">2003supporters.html - Thanks
GNUs
2003</a></li>
<li><a href="/thankgnus/2004supporters.html">2004supporters.html - Thank GNUs
2004</a></li>
@@ -1345,27 +1342,62 @@
</div>
+<!-- If needed, change the copyright block at the bottom. In general,
+ pages on the GNU web server should be under CC BY-ND 3.0 US.
+ Please do NOT change or remove this without talking
+ with the webmasters or licensing team first.
+ Please make sure the copyright date is consistent with the document.
+ For web pages, it is ok to list just the latest year the document
+ was modified, or published.
+
+ If you wish to list earlier years, that is ok too.
+ Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+ years, as long as each year in the range is in fact a copyrightable
+ year, i.e., a year in which the document was published (including
+ being publicly visible on the web or in a revision control system).
+
+ There is more detail about copyright years in the GNU Maintainers
+ Information document, www.gnu.org/prep/maintain. -->
<div style="font-size: small;">
<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
</div>
</div>
+<!-- for id="content", starts in the include above -->
<!--#include virtual="/server/footer.ja.html" -->
<div id="footer">
-<p>
-FSF ããã³ GNU ã«é¢ããåãåãã㯠<a
+
+<p>FSFããã³GNUã«é¢ããåãåããã¯<a
href="mailto:address@hidden";><address@hidden></a>ã¾ã§ãé¡ããã¾ã(è±èª)ãFSFã¸ã®é£çµ¡ã¯<a
-href="/contact/">ä»ã®æ¹æ³</a>ãããã¾ãã
-<br />
-ãªã³ã¯åããä»ã®ä¿®æ£ãææ¡ã¯<a
-href="mailto:address@hidden";><address@hidden></a>ã¾ã§ãéããã
ããã
+href="/contact/">ä»ã®æ¹æ³</a>ãããã¾ãããªã³ã¯åããä»ã®ä¿®æ£ãææ¡ã¯<a
+href="mailto:address@hidden";><address@hidden></a>ã¾ã§ãéããã
ããã</p>
+
+<p>
+
+<!-- TRANSLATORS: Ignore the original text in this paragraph,
+ replace it with the translation of these two:
+
+ We work hard and do our best to provide accurate, good quality
+ translations. However, we are not exempt from imperfection.
+ Please send your comments and general suggestions in this regard
+ to <a href="mailto:address@hidden";>
+
+ <address@hidden></a>.</p>
+
+ <p>For information on coordinating and submitting translations of
+ our web pages, see <a
+ href="/server/standards/README.translations.html">Translations
+ README</a>. -->
+æ£ç¢ºã§è¯ãå質ã®ç¿»è¨³ãæä¾ããããåªåãã¦ãã¾ãããä¸å®å
¨ãªå
´åããããã¨æãã¾ãã翻訳ã«é¢ããã³ã¡ã³ãã¨ä¸è¬çãªææ¡ã¯ã<a
+href="mailto:address@hidden";><address@hidden></a>ã¾ã§ãããããã¾ããããããã¡ã®ã¦ã§ããã¼ã¸ã®ç¿»è¨³ã®èª¿æ´ã¨æåºã«ã¤ãã¦ã¯ã<a
+href="/server/standards/README.translations.html">翻訳
README</a>ãã覧ãã ããã
</p>
<p>
Copyright © 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
-2006, 2007, 2008, 2011 Free Software Foundation, Inc.,</p>
-<address>51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA</address>
+2006, 2007, 2008, 2011, 2012 Free Software Foundation, Inc.</p>
+
<p>
ãã®ãã¼ã¸ã¯<a rel="license"
href="http://creativecommons.org/licenses/by-nd/3.0/us/";>Creative Commons
@@ -1383,79 +1415,11 @@
<!-- timestamp start -->
æçµæ´æ°:
-$Date: 2012/05/21 08:29:04 $
+$Date: 2012/06/05 08:28:35 $
<!-- timestamp end -->
</p>
</div>
-
-<!-- All pages on the GNU web server should have the section about -->
-<!-- verbatim copying. Please do NOT remove this without talking -->
-<!-- with the webmasters first. -->
-<!-- Please make sure the copyright date is consistent with the document -->
-<!-- and that it is like this "2001, 2002" not this "2001-2002." -->
-<div id="translations">
-<h4>ãã®ãã¼ã¸ã®ç¿»è¨³</h4>
-
-<!-- Please keep this list alphabetical by language code. -->
-<!-- Comment what the language is for each type, i.e. de is German. -->
-<!-- Write the language name in its own language (Deutsch) in the text. -->
-<!-- If you add a new language here, please -->
-<!-- advise address@hidden and add it to -->
-<!-- - /home/www/html/server/standards/README.translations.html -->
-<!-- - one of the lists under the section "Translations Underway" -->
-<!-- - if there is a translation team, you also have to add an alias -->
-<!-- to mail.gnu.org:/com/mailer/aliases -->
-<!-- Please also check you have the 2 letter language code right, cf. -->
-<!-- <http://www.loc.gov/standards/iso639-2/php/code_list.php>
- -->
-<!-- If ISO 639-1 code is not available, use the 3 letter ISO 639-2. -->
-<!-- Please use W3C normative character entities. -->
-<ul class="translations-list">
-
-<!-- Arabic -->
-<li><a
-href="/server/sitemap.ar.html">العربية</a> [ar]</li>
-
-<!-- Catalan -->
-<li><a href="/server/sitemap.ca.html">Català</a> [ca]</li>
-
-<!-- German -->
-<li><a href="/server/sitemap.de.html">Deutsch</a> [de]</li>
-
-<!-- English -->
-<li><a href="/server/sitemap.html">English</a> [en]</li>
-
-<!-- Spanish -->
-<li><a href="/server/sitemap.es.html">Español</a> [es]</li>
-
-<!-- French -->
-<li><a href="/server/sitemap.fr.html">Français</a> [fr]</li>
-
-<!-- Italiano -->
-<li><a href="/server/sitemap.it.html">Italiano</a> [it]</li>
-
-<!-- Japanese -->
-<li><a
href="/server/sitemap.ja.html">日本語</a> [ja]</li>
-
-<!-- Dutch -->
-<li><a href="/server/sitemap.nl.html">Nederlands</a> [nl]</li>
-
-<!-- Polish -->
-<li><a href="/server/sitemap.pl.html">Polski</a> [pl]</li>
-
-<!-- Romanian -->
-<li><a href="/server/sitemap.ro.html">Română</a> [ro]</li>
-
-<!-- Ukrainian -->
-<li><a
-href="/server/sitemap.uk.html">українська</a> [uk]</li>
-
-<!-- Chinese (Traditional) -->
-<li><a
-href="/server/sitemap.zh-tw.html">繁體中文</a> [zh-tw]</li>
-</ul>
-</div>
</div>
</body>
</html>
Index: server/po/sitemap.ja-en.html
===================================================================
RCS file: /web/www/www/server/po/sitemap.ja-en.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- server/po/sitemap.ja-en.html 21 May 2012 08:29:17 -0000 1.4
+++ server/po/sitemap.ja-en.html 5 Jun 2012 08:28:52 -0000 1.5
@@ -1,6 +1,7 @@
<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.68 -->
-<title>Site map of www.gnu.org - GNU Project - Free Software Foundation
(FSF)</title>
+<title>Site map of www.gnu.org - GNU Project - Free Software Foundation</title>
<style type="text/css">
.sitemap-directory { margin-left: 1.2em }
@@ -18,16 +19,10 @@
</style>
<!--#include virtual="/server/banner.html" -->
+<!--#include virtual="/server/po/sitemap.translist" -->
<h2>Site map of www.gnu.org</h2>
- <!-- When you replace this graphic, make sure you change -->
- <!-- the link to also point to the correct HTML page. -->
- <!-- If you make a new graphic for this page, make sure it -->
- <!-- has a corresponding entry in /graphics/graphics.html. -->
-
-
-
<div class="sitemap-directory sitemap-directory-depth-0"><div>[top-level
directories: <a href="#directory-accessibility">accessibility</a> <a
href="#directory-award">award</a> <a href="#directory-bulletins">bulletins</a>
<a href="#directory-contact">contact</a> <a
href="#directory-copyleft">copyleft</a> <a
href="#directory-distros">distros</a> <a href="#directory-doc">doc</a> <a
href="#directory-education">education</a> <a
href="#directory-encyclopedia">encyclopedia</a> <a
href="#directory-events">events</a> <a href="#directory-fun">fun</a> <a
href="#directory-gnu">gnu</a> <a href="#directory-graphics">graphics</a> <a
href="#directory-help">help</a> <a href="#directory-licenses">licenses</a> <a
href="#directory-links">links</a> <a href="#directory-manual">manual</a> <a
href="#directory-music">music</a> <a href="#directory-people">people</a> <a
href="#directory-philosophy">philosophy</a> <a href="#directory-prep">prep</a>
<a href="#directory-press">press</a> <a
href="#directory-pronunciation">pronunciation</a> <a
href="#directory-server">server</a> <a href="#directory-software">software</a>
<a href="#directory-testimonials">testimonials</a> <a
href="#directory-thankgnus">thankgnus</a> <a
href="#directory-usenet">usenet</a>]</div>
<ul>
@@ -236,8 +231,8 @@
<li><a href="/fun/jokes/dna.html">dna.html - Human DNA as C code</a></li>
<li><a href="/fun/jokes/doctor.manifesto.html">doctor.manifesto.html - Dr.
Emacs and the GNU Manifesto</a></li>
<li><a href="/fun/jokes/echo-msg.html">echo-msg.html - GNU Echo</a></li>
+ <li><a href="/fun/jokes/ed-msg.html">ed-msg.html - Ed, man! !man ed- GNU
Project</a></li>
<li><a href="/fun/jokes/ed.html">ed.html - Ed source code</a></li>
- <li><a href="/fun/jokes/ed.msg.html">ed.msg.html - Ed, man! !man ed- GNU
Project</a></li>
<li><a href="/fun/jokes/errno.2.html">errno.2.html - errno(2) codes</a></li>
<li><a href="/fun/jokes/error-haiku.html">error-haiku.html - Haiku error
messages</a></li>
<li><a href="/fun/jokes/eternal-flame.html">eternal-flame.html - Eternal
Flame</a></li>
@@ -580,6 +575,7 @@
<li><a href="/philosophy/amazon.html">amazon.html - (Formerly) Boycott
Amazon!</a></li>
<li><a href="/philosophy/amazonpatent.html">amazonpatent.html - United
States Patent: 5,960,411</a></li>
<li><a
href="/philosophy/android-and-users-freedom.html">android-and-users-freedom.html
- Android and Users' Freedom</a></li>
+ <li><a href="/philosophy/anonymous-response.html">anonymous-response.html -
A Response Letter to the Word Attachments</a></li>
<li><a href="/philosophy/apsl.html">apsl.html - FSF's Opinion on the Apple
Public Source License (APSL)</a></li>
<li><a href="/philosophy/assigning-copyright.html">assigning-copyright.html
- When a Company Asks For Your Copyright</a></li>
<li><a href="/philosophy/basic-freedoms.html">basic-freedoms.html - Freedom
of Speech, Press and Association on the Internet</a></li>
@@ -674,7 +670,6 @@
<li><a href="/philosophy/not-ipr.html">not-ipr.html - Did You Say
“Intellectual Property”? It's a Seductive Mirage</a></li>
<li><a
href="/philosophy/open-source-misses-the-point.html">open-source-misses-the-point.html
- Why Open Source Misses the Point of Free Software</a></li>
<li><a href="/philosophy/opposing-drm.html">opposing-drm.html - Opposing
Digital Rights Mismanagement</a></li>
- <li><a
href="/philosophy/papadopoulos-response.html">papadopoulos-response.html - A
Response Letter to the Word Attachments</a></li>
<li><a
href="/philosophy/patent-practice-panel.html">patent-practice-panel.html -
Daniel Ravicher's FFII panel presentation, November 10, 2004</a></li>
<li><a
href="/philosophy/patent-reform-is-not-enough.html">patent-reform-is-not-enough.html
- Patent Reform Is Not Enough</a></li>
<li><a href="/philosophy/pirate-party.html">pirate-party.html - How the
Swedish Pirate Party Platform Backfires on Free Software</a></li>
@@ -857,7 +852,7 @@
</ul>
<div id="directory-server-source" class="sitemap-directory
sitemap-directory-depth-2">
-<div class="sitemap-header"><a href="/server/source/source.html">server/source
- Web server utility sources</a></div>
+<div class="sitemap-header"><a href="/server/source/source.html">server/source
- Web Server Utility Sources</a></div>
</div>
<div id="directory-server-standards" class="sitemap-directory
sitemap-directory-depth-2">
@@ -899,13 +894,13 @@
<div id="directory-testimonials" class="sitemap-directory
sitemap-directory-depth-1">
<div class="sitemap-header"><a
href="/testimonials/testimonials.html">testimonials - GNU Testimonials</a></div>
<ul>
- <li><a href="/testimonials/reliable.html">reliable.html - Free Software is
Reliable - GNU Testimonials</a></li>
+ <li><a href="/testimonials/reliable.html">reliable.html - Free Software is
Reliable</a></li>
<li><a href="/testimonials/supported.html">supported.html - Free Software is
Supported</a></li>
- <li><a href="/testimonials/testimonial_cadcam.html">testimonial_cadcam.html
- GNU Testimonials - CAD/CAM Development</a></li>
- <li><a href="/testimonials/testimonial_HIRLAM.html">testimonial_HIRLAM.html
- GNU Testimonials - HIRLAM Consortium</a></li>
- <li><a href="/testimonials/testimonial_media.html">testimonial_media.html -
GNU Testimonials - Alexander Ewering</a></li>
- <li><a
href="/testimonials/testimonial_mondrup.html">testimonial_mondrup.html - GNU
Testimonials - Christian Mondrup</a></li>
- <li><a
href="/testimonials/testimonial_research_ships.html">testimonial_research_ships.html
- GNU Testimonials - Robert Harvey</a></li>
+ <li><a href="/testimonials/testimonial_cadcam.html">testimonial_cadcam.html
- CAD/CAM Development</a></li>
+ <li><a href="/testimonials/testimonial_HIRLAM.html">testimonial_HIRLAM.html
- HIRLAM Consortium</a></li>
+ <li><a href="/testimonials/testimonial_media.html">testimonial_media.html -
Alexander Ewering</a></li>
+ <li><a
href="/testimonials/testimonial_mondrup.html">testimonial_mondrup.html -
Christian Mondrup</a></li>
+ <li><a
href="/testimonials/testimonial_research_ships.html">testimonial_research_ships.html
- Robert Harvey</a></li>
<li><a href="/testimonials/useful.html">useful.html - Free Software is
Useful</a></li>
</ul>
</div>
@@ -915,14 +910,14 @@
<div id="directory-thankgnus" class="sitemap-directory
sitemap-directory-depth-1">
<div class="sitemap-header"><a href="/thankgnus/thankgnus.html">thankgnus -
Thank GNUs</a></div>
<ul>
- <li><a href="/thankgnus/1997supporters.html">1997supporters.html - Thanks
GNUs</a></li>
- <li><a href="/thankgnus/1998supporters.html">1998supporters.html - Thanks
GNUs</a></li>
+ <li><a href="/thankgnus/1997supporters.html">1997supporters.html - Thanks
GNUs 1997</a></li>
+ <li><a href="/thankgnus/1998supporters.html">1998supporters.html - Thanks
GNUs 1998</a></li>
<li><a href="/thankgnus/1999.html">1999.html - List of 1999 FSF
Supporters</a></li>
- <li><a href="/thankgnus/1999supporters.html">1999supporters.html - Thanks
GNUs</a></li>
- <li><a href="/thankgnus/2000supporters.html">2000supporters.html - Thanks
GNUs</a></li>
- <li><a href="/thankgnus/2001supporters.html">2001supporters.html - Thanks
GNUs</a></li>
- <li><a href="/thankgnus/2002supporters.html">2002supporters.html - Thanks
GNUs</a></li>
- <li><a href="/thankgnus/2003supporters.html">2003supporters.html - Thank
GNUs 2003</a></li>
+ <li><a href="/thankgnus/1999supporters.html">1999supporters.html - Thanks
GNUs 1999</a></li>
+ <li><a href="/thankgnus/2000supporters.html">2000supporters.html - Thanks
GNUs 2000</a></li>
+ <li><a href="/thankgnus/2001supporters.html">2001supporters.html - Thanks
GNUs 2001</a></li>
+ <li><a href="/thankgnus/2002supporters.html">2002supporters.html - Thanks
GNUs 2002</a></li>
+ <li><a href="/thankgnus/2003supporters.html">2003supporters.html - Thanks
GNUs 2003</a></li>
<li><a href="/thankgnus/2004supporters.html">2004supporters.html - Thank
GNUs 2004</a></li>
<li><a href="/thankgnus/2005supporters.html">2005supporters.html - Thank
GNUs 2005</a></li>
<li><a href="/thankgnus/2006supporters.html">2006supporters.html - Thank
GNUs 2006</a></li>
@@ -946,25 +941,57 @@
<div>[top-level directories: <a
href="#directory-accessibility">accessibility</a> <a
href="#directory-award">award</a> <a href="#directory-bulletins">bulletins</a>
<a href="#directory-contact">contact</a> <a
href="#directory-copyleft">copyleft</a> <a
href="#directory-distros">distros</a> <a href="#directory-doc">doc</a> <a
href="#directory-education">education</a> <a
href="#directory-encyclopedia">encyclopedia</a> <a
href="#directory-events">events</a> <a href="#directory-fun">fun</a> <a
href="#directory-gnu">gnu</a> <a href="#directory-graphics">graphics</a> <a
href="#directory-help">help</a> <a href="#directory-licenses">licenses</a> <a
href="#directory-links">links</a> <a href="#directory-manual">manual</a> <a
href="#directory-music">music</a> <a href="#directory-people">people</a> <a
href="#directory-philosophy">philosophy</a> <a href="#directory-prep">prep</a>
<a href="#directory-press">press</a> <a
href="#directory-pronunciation">pronunciation</a> <a
href="#directory-server">server</a> <a href="#directory-software">software</a>
<a href="#directory-testimonials">testimonials</a> <a
href="#directory-thankgnus">thankgnus</a> <a
href="#directory-usenet">usenet</a>]</div>
</div>
-</div>
+<!-- If needed, change the copyright block at the bottom. In general,
+ pages on the GNU web server should be under CC BY-ND 3.0 US.
+ Please do NOT change or remove this without talking
+ with the webmasters or licensing team first.
+ Please make sure the copyright date is consistent with the document.
+ For web pages, it is ok to list just the latest year the document
+ was modified, or published.
+
+ If you wish to list earlier years, that is ok too.
+ Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+ years, as long as each year in the range is in fact a copyrightable
+ year, i.e., a year in which the document was published (including
+ being publicly visible on the web or in a revision control system).
+
+ There is more detail about copyright years in the GNU Maintainers
+ Information document, www.gnu.org/prep/maintain. -->
-<!--#include virtual="/server/footer.html" -->
+</div><!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.html" -->
<div id="footer">
-<p>
-Please send FSF & GNU inquiries to
-<a href="mailto:address@hidden";><em>address@hidden</em></a>.
+
+<p>Please send general FSF & GNU inquiries to
+<a href="mailto:address@hidden";><address@hidden></a>.
There are also <a href="/contact/">other ways to contact</a>
-the FSF.
-<br />
-Please send broken links and other corrections or suggestions to
-<a href="mailto:address@hidden";><em>address@hidden</em></a>.
+the FSF. Broken links and other corrections or suggestions can be sent
+to <a href="mailto:address@hidden";><address@hidden></a>.</p>
+
+<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
+ replace it with the translation of these two:
+
+ We work hard and do our best to provide accurate, good quality
+ translations. However, we are not exempt from imperfection.
+ Please send your comments and general suggestions in this regard
+ to <a href="mailto:address@hidden";>
+ <address@hidden></a>.</p>
+
+ <p>For information on coordinating and submitting translations of
+ our web pages, see <a
+ href="/server/standards/README.translations.html">Translations
+ README</a>. -->
+
+For information on coordinating and submitting translations of this
+article, see <a
+href="/server/standards/README.translations.html">Translations README</a>.
</p>
<p>
Copyright © 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004,
-2005, 2006, 2007, 2008, 2011 Free Software Foundation, Inc.,</p>
-<address>51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA</address>
+2005, 2006, 2007, 2008, 2011, 2012 Free Software Foundation, Inc.</p>
+
<p>
This page is licensed under a <a rel="license"
href="http://creativecommons.org/licenses/by-nd/3.0/us/";>Creative
@@ -974,62 +1001,10 @@
<p>
Updated:
<!-- timestamp start -->
-$Date: 2012/05/21 08:29:17 $
+$Date: 2012/06/05 08:28:52 $
<!-- timestamp end -->
</p>
</div>
-<!-- All pages on the GNU web server should have the section about -->
-<!-- verbatim copying. Please do NOT remove this without talking -->
-<!-- with the webmasters first. -->
-<!-- Please make sure the copyright date is consistent with the document -->
-<!-- and that it is like this "2001, 2002" not this "2001-2002." -->
-
-<div id="translations">
-<h4>Translations of this page</h4>
-
-<!-- Please keep this list alphabetical by language code. -->
-<!-- Comment what the language is for each type, i.e. de is German. -->
-<!-- Write the language name in its own language (Deutsch) in the text. -->
-<!-- If you add a new language here, please -->
-<!-- advise address@hidden and add it to -->
-<!-- - /home/www/html/server/standards/README.translations.html -->
-<!-- - one of the lists under the section "Translations Underway" -->
-<!-- - if there is a translation team, you also have to add an alias -->
-<!-- to mail.gnu.org:/com/mailer/aliases -->
-<!-- Please also check you have the 2 letter language code right, cf. -->
-<!-- <http://www.loc.gov/standards/iso639-2/php/code_list.php> -->
-<!-- If ISO 639-1 code is not available, use the 3 letter ISO 639-2. -->
-<!-- Please use W3C normative character entities. -->
-
-<ul class="translations-list">
-<!-- Arabic -->
-<li><a
href="/server/sitemap.ar.html">العربية</a> [ar]</li>
-<!-- Catalan -->
-<li><a href="/server/sitemap.ca.html">Català</a> [ca]</li>
-<!-- German -->
-<li><a href="/server/sitemap.de.html">Deutsch</a> [de]</li>
-<!-- English -->
-<li><a href="/server/sitemap.html">English</a> [en]</li>
-<!-- Spanish -->
-<li><a href="/server/sitemap.es.html">Español</a> [es]</li>
-<!-- French -->
-<li><a href="/server/sitemap.fr.html">Français</a> [fr]</li>
-<!-- Italiano -->
-<li><a href="/server/sitemap.it.html">Italiano</a> [it]</li>
-<!-- Japanese -->
-<li><a
href="/server/sitemap.ja.html">日本語</a> [ja]</li>
-<!-- Dutch -->
-<li><a href="/server/sitemap.nl.html">Nederlands</a> [nl]</li>
-<!-- Polish -->
-<li><a href="/server/sitemap.pl.html">Polski</a> [pl]</li>
-<!-- Romanian -->
-<li><a href="/server/sitemap.ro.html">Română</a> [ro]</li>
-<!-- Ukrainian -->
-<li><a
href="/server/sitemap.uk.html">українська</a> [uk]</li>
-<!-- Chinese (Traditional) -->
-<li><a
href="/server/sitemap.zh-tw.html">繁體中文</a> [zh-tw]</li>
-</ul>
-</div>
</div>
</body>
</html>
Index: server/po/sitemap.ja.po
===================================================================
RCS file: /web/www/www/server/po/sitemap.ja.po,v
retrieving revision 1.51
retrieving revision 1.52
diff -u -b -r1.51 -r1.52
--- server/po/sitemap.ja.po 5 Jun 2012 07:49:18 -0000 1.51
+++ server/po/sitemap.ja.po 5 Jun 2012 08:28:54 -0000 1.52
@@ -4349,16 +4349,16 @@
"<a href=\"/thankgnus/1997supporters.html\">1997supporters.html - Thanks GNUs "
"1997</a>"
msgstr ""
-"<a href=\"/thankgnus/1997supporters.html\">1997supporters.html - Thanks "
-"GNUs 1997</a>"
+"<a href=\"/thankgnus/1997supporters.html\">1997supporters.html - Thanks GNUs "
+"1997</a>"
#. type: Content of: <div><div><ul><li>
msgid ""
"<a href=\"/thankgnus/1998supporters.html\">1998supporters.html - Thanks GNUs "
"1998</a>"
msgstr ""
-"<a href=\"/thankgnus/1998supporters.html\">1998supporters.html - Thanks "
-"GNUs 1998</a>"
+"<a href=\"/thankgnus/1998supporters.html\">1998supporters.html - Thanks GNUs "
+"1998</a>"
#. type: Content of: <div><div><ul><li>
msgid ""
@@ -4370,32 +4370,32 @@
"<a href=\"/thankgnus/1999supporters.html\">1999supporters.html - Thanks GNUs "
"1999</a>"
msgstr ""
-"<a href=\"/thankgnus/1999supporters.html\">1999supporters.html - Thanks "
-"GNUs 1999</a>"
+"<a href=\"/thankgnus/1999supporters.html\">1999supporters.html - Thanks GNUs "
+"1999</a>"
#. type: Content of: <div><div><ul><li>
msgid ""
"<a href=\"/thankgnus/2000supporters.html\">2000supporters.html - Thanks GNUs "
"2000</a>"
msgstr ""
-"<a href=\"/thankgnus/2000supporters.html\">2000supporters.html - Thanks "
-"GNUs 2000</a>"
+"<a href=\"/thankgnus/2000supporters.html\">2000supporters.html - Thanks GNUs "
+"2000</a>"
#. type: Content of: <div><div><ul><li>
msgid ""
"<a href=\"/thankgnus/2001supporters.html\">2001supporters.html - Thanks GNUs "
"2001</a>"
msgstr ""
-"<a href=\"/thankgnus/2001supporters.html\">2001supporters.html - Thanks "
-"GNUs 2001</a>"
+"<a href=\"/thankgnus/2001supporters.html\">2001supporters.html - Thanks GNUs "
+"2001</a>"
#. type: Content of: <div><div><ul><li>
msgid ""
"<a href=\"/thankgnus/2002supporters.html\">2002supporters.html - Thanks GNUs "
"2002</a>"
msgstr ""
-"<a href=\"/thankgnus/2002supporters.html\">2002supporters.html - Thanks "
-"GNUs 2002</a>"
+"<a href=\"/thankgnus/2002supporters.html\">2002supporters.html - Thanks GNUs "
+"2002</a>"
#. type: Content of: <div><div><ul><li>
msgid ""
@@ -4524,8 +4524,8 @@
"see <a href=\"/server/standards/README.translations.html\">Translations "
"README</a>."
msgstr ""
-"æ£ç¢ºã§è¯ãå質ã®ç¿»è¨³ãæä¾ããããåªåãã¦ãã¾ãããä¸å®å
¨ãªå ´åããããã¨æã"
-"ã¾ãã翻訳ã«é¢ããã³ã¡ã³ãã¨ä¸è¬çãªææ¡ã¯ã<a
href=\"mailto:web-";
+"æ£ç¢ºã§è¯ãå質ã®ç¿»è¨³ãæä¾ããããåªåãã¦ãã¾ãããä¸å®å
¨ãªå ´åããããã¨æ"
+"ãã¾ãã翻訳ã«é¢ããã³ã¡ã³ãã¨ä¸è¬çãªææ¡ã¯ã<a
href=\"mailto:web-";
"address@hidden"><address@hidden></a>ã¾ã§ãããããã¾ãã"
"ããããã¡ã®ã¦ã§ããã¼ã¸ã®ç¿»è¨³ã®èª¿æ´ã¨æåºã«ã¤ãã¦ã¯ã<a
href=\"/server/"
"standards/README.translations.html\">翻訳 README</a>ãã覧ãã
ããã"
Index: licenses/old-licenses/gpl-2.0-faq.ru.html
===================================================================
RCS file: licenses/old-licenses/gpl-2.0-faq.ru.html
diff -N licenses/old-licenses/gpl-2.0-faq.ru.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ licenses/old-licenses/gpl-2.0-faq.ru.html 5 Jun 2012 08:27:51 -0000
1.1
@@ -0,0 +1,2543 @@
+
+
+<!--#include virtual="/server/header.ru.html" -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>ÐÑвеÑÑ Ð½Ð° вопÑоÑÑ Ð¾ GNU GPL v2.0 - пÑÐ¾ÐµÐºÑ GNU -
Фонд Ñвободного пÑогÑаммного
+обеÑпеÑÐµÐ½Ð¸Ñ (ФСÐÐ)</title>
+
+<!--#include virtual="/server/banner.ru.html" -->
+<!--#include virtual="/licenses/old-licenses/po/gpl-2.0-faq.translist" -->
+<h2>ÐÑвеÑÑ Ð½Ð° вопÑоÑÑ Ð¾ веÑÑии 2 GNU GPL</h2>
+
+<p>
+ÐÑа ÑÑÑаниÑа ÑодеÑÐ¶Ð¸Ñ Ð¾ÑвеÑÑ Ð½Ð° обÑÑно
задаваемÑе вопÑоÑÑ Ð¾ веÑÑии 2
+СÑандаÑÑной обÑеÑÑвенной лиÑензии (GPL) GNU.
СпиÑок Ð´Ð»Ñ ÑекÑÑей веÑÑии GPL
+наÑ
одиÑÑÑ Ð½Ð° <a href="/licenses/gpl-faq.html">дÑÑгой
ÑÑÑаниÑе</a>. Ðа более
+подÑобнÑми ÑведениÑми о дÑÑгиÑ
лиÑензиÑÑ
Фонда Ñвободного пÑогÑаммного
+обеÑпеÑÐµÐ½Ð¸Ñ Ð¾Ð±ÑаÑайÑеÑÑ, пожалÑйÑÑа, к <a
+href="/licenses/licenses.html">наÑей ÑÑÑаниÑе
лиÑензий</a>.</p>
+
+<p>
+ÐоÑле ÑÑÐµÐ½Ð¸Ñ ÑÑого ÑпиÑка Ð²Ñ Ð¼Ð¾Ð¶ÐµÑе
пÑовеÑиÑÑ Ñвое знание лиÑензиÑованиÑ
+ÑвободнÑÑ
пÑогÑамм Ñ Ð¿Ð¾Ð¼Ð¾ÑÑÑ <a
href="/cgi-bin/license-quiz.cgi">наÑего
+опÑоÑника</a>.
+</p>
+
+<!-- Replace this list with the page's contents. -->
+<h4>СодеÑжание</h4>
+
+ <h4>ÐÑоÑÑÑе вопÑоÑÑ Ð¾ GPL, пÑоекÑе GNU и Фонде
Ñвободного пÑогÑаммного
+обеÑпеÑениÑ</h4>
+
+ <ul>
+ <li><a href="#WhatDoesGPLStandFor" name="TOCWhatDoesGPLStandFor">Ðак
+ÑаÑÑиÑÑовÑваеÑÑÑ “GPL”?</a></li>
+
+ <li><a href="#DoesFreeSoftwareMeanUsingTheGPL"
+name="TOCDoesFreeSoftwareMeanUsingTheGPL">ÐодÑазÑÐ¼ÐµÐ²Ð°ÐµÑ Ð»Ð¸
вÑÑажение
+“ÑÐ²Ð¾Ð±Ð¾Ð´Ð½Ð°Ñ Ð¿ÑогÑамма” пÑименение
GPL?</a></li>
+
+ <li><a href="#WhyUseGPL" name="TOCWhyUseGPL">ÐоÑÐµÐ¼Ñ Ð¼Ð½Ðµ
ÑледÑÐµÑ Ð¿ÑименÑÑÑ GNU
+GPL, а не дÑÑгие лиÑензии ÑвободнÑÑ
пÑогÑамм?</a></li>
+
+ <li><a href="#DoesAllGNUSoftwareUseTheGNUGPLAsItsLicense"
+name="TOCDoesAllGNUSoftwareUseTheGNUGPLAsItsLicense">ÐÑе ли
пÑогÑÐ°Ð¼Ð¼Ñ GNU
+иÑполÑзÑÑÑ Ð² каÑеÑÑве лиÑензии GNU GPL?</a></li>
+
+ <li><a href="#DoesUsingTheGPLForAProgramMakeItGNUSoftware"
+name="TOCDoesUsingTheGPLForAProgramMakeItGNUSoftware">ÐÑли длÑ
пÑогÑаммÑ
+пÑименÑеÑÑÑ GPL, Ñо Ð´ÐµÐ»Ð°ÐµÑ Ð»Ð¸ ÑÑо ее
пÑогÑаммой GNU?</a></li>
+
+ <li><a href="#GPLOtherThanSoftware"
name="TOCGPLOtherThanSoftware">ÐÐ¾Ð³Ñ Ñ
+пÑименÑÑÑ GPL Ð´Ð»Ñ Ñего-нибÑÐ´Ñ ÐºÑоме
пÑогÑамм?</a></li>
+
+ <li><a href="#WhyNotGPLForManuals"
name="TOCWhyNotGPLForManuals">ÐоÑÐµÐ¼Ñ Ð²Ñ Ð½Ðµ
+пÑименÑеÑе GPL Ð´Ð»Ñ ÑÑководÑÑв?</a></li>
+
+ <li><a href="#GPLTranslations"
name="TOCGPLTranslations">СÑÑеÑÑвÑÑÑ Ð»Ð¸ пеÑеводÑ
+GPL на дÑÑгие ÑзÑки?</a></li>
+
+ <li><a href="#WhySomeGPLAndNotLGPL"
name="TOCWhySomeGPLAndNotLGPL">ÐоÑемÑ
+некоÑоÑÑе библиоÑеки GNU вÑпÑÑкаÑÑÑÑ Ð¿Ð¾
обÑÑной GPL, а не по ÐенÑÑей
+GPL?</a></li>
+
+ <li><a href="#WhoHasThePower" name="TOCWhoHasThePower">ÐÑо впÑаве
ÑÑебоваÑÑ
+ÑоблÑÐ´ÐµÐ½Ð¸Ñ GPL?</a></li>
+
+ <li><a href="#AssignCopyright" name="TOCAssignCopyright">ÐоÑемÑ
ФСÐÐ ÑÑебÑеÑ,
+ÑÑÐ¾Ð±Ñ Ñе, кÑо вноÑÐ¸Ñ Ð²ÐºÐ»Ð°Ð´ в пÑогÑаммÑ,
авÑоÑÑкие пÑава на коÑоÑÑе
+пÑÐ¸Ð½Ð°Ð´Ð»ÐµÐ¶Ð°Ñ Ð¤Ð¡ÐÐ, пеÑедавали ÑондÑ
авÑоÑÑкие пÑава? СледÑÐµÑ Ð»Ð¸ и мне делаÑÑ
+ÑÑо, еÑли мне пÑÐ¸Ð½Ð°Ð´Ð»ÐµÐ¶Ð°Ñ Ð°Ð²ÑоÑÑкие пÑава
на пÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL? ÐÑли да, Ñо
+как?</a></li>
+
+ <li><a href="#ModifyGPL" name="TOCModifyGPL">Ðожно мне
измениÑÑ GPL и ÑделаÑÑ
+дÑÑгÑÑ Ð»Ð¸ÑензиÑ?</a></li>
+
+ </ul>
+
+ <h4>ÐбÑее понимание GPL</h4>
+
+ <ul>
+ <li><a href="#WhyDoesTheGPLPermitUsersToPublishTheirModifiedVersions"
+name="TOCWhyDoesTheGPLPermitUsersToPublishTheirModifiedVersions">ÐоÑемÑ
GPL
+ÑазÑеÑÐ°ÐµÑ Ð¿Ð¾Ð»ÑзоваÑелÑм пÑбликоваÑÑ Ñвои
измененнÑе веÑÑии?</a></li>
+
+ <li><a href="#GPLRequireSourcePostedPublic"
+name="TOCGPLRequireSourcePostedPublic">ТÑебÑÐµÑ Ð»Ð¸ GPL, ÑÑобÑ
иÑÑ
однÑй ÑекÑÑ
+измененнÑÑ
веÑÑий вÑÑÑавлÑлÑÑ Ð½Ð° вÑеобÑее
обозÑение?</a></li>
+
+ <li><a href="#GPLAndNonfreeOnSameMachine"
+name="TOCGPLAndNonfreeOnSameMachine">ÐÐ¾Ð¶ÐµÑ Ñ Ð¼ÐµÐ½Ñ Ð±ÑÑÑ
пÑогÑамма под GPL и
+не ÑвÑÐ·Ð°Ð½Ð½Ð°Ñ Ñ Ð½ÐµÐ¹ неÑÐ²Ð¾Ð±Ð¾Ð´Ð½Ð°Ñ Ð¿ÑогÑамма
на одном и Ñом же компÑÑÑеÑе?</a></li>
+
+ <li><a href="#CanIDemandACopy" name="TOCCanIDemandACopy">ÐÑли Ñ
знаÑ, ÑÑо Ñ
+кого-Ñо еÑÑÑ ÐºÐ¾Ð¿Ð¸Ñ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL, Ð¼Ð¾Ð³Ñ Ð»Ð¸
Ñ ÑÑебоваÑÑ, ÑÑÐ¾Ð±Ñ Ð¾Ð½ дал мне
+копиÑ?</a></li>
+
+ <li><a href="#WhatDoesWrittenOfferValid"
name="TOCWhatDoesWrittenOfferValid">ЧÑо
+ознаÑÐ°ÐµÑ Ð² GPL веÑÑии 2 “пиÑÑменное
пÑедложение, дейÑÑвиÑелÑное
+Ð´Ð»Ñ Ð»Ñбой ÑÑеÑÑей ÑÑоÑонє? ÐнаÑÐ¸Ñ Ð»Ð¸
ÑÑо, ÑÑо вÑе на ÑвеÑе могÑÑ
+полÑÑиÑÑ Ð¸ÑÑ
однÑй ÑекÑÑ Ð»Ñбой пÑогÑаммÑ
под GPL, вÑе Ñавно, какой
+именно?</a></li>
+
+ <li><a href="#TheGPLSaysModifiedVersions"
name="TOCTheGPLSaysModifiedVersions">Ð
+веÑÑии 2 GPL Ñказано, ÑÑо еÑли вÑпÑÑкаÑÑÑÑ
измененнÑе веÑÑии, Ñо они должнÑ
+бÑÑÑ “лиÑензиÑованх Ð´Ð»Ñ Ð²ÑеÑ
ÑÑеÑÑиÑ
ÑÑоÑон”. ÐÑо ÑÑи
+ÑÑеÑÑи ÑÑоÑонÑ?</a></li>
+
+ <li><a href="#DoesTheGPLAllowMoney"
name="TOCDoesTheGPLAllowMoney">ÐозволÑÐµÑ Ð»Ð¸
+мне GPL пÑодаваÑÑ ÐºÐ¾Ð¿Ð¸Ð¸ пÑогÑÐ°Ð¼Ð¼Ñ Ð·Ð°
денÑги?</a></li>
+
+ <li><a href="#DoesTheGPLAllowDownloadFee"
+name="TOCDoesTheGPLAllowDownloadFee">ÐозволÑÐµÑ Ð»Ð¸ мне GPL
бÑаÑÑ Ð¿Ð»Ð°ÑÑ Ð·Ð°
+полÑÑение пÑогÑÐ°Ð¼Ð¼Ñ Ñ Ð¼Ð¾ÐµÐ³Ð¾ ÑайÑа?</a></li>
+
+ <li><a href="#DoesTheGPLAllowRequireFee"
+name="TOCDoesTheGPLAllowRequireFee">ÐозволÑÐµÑ Ð»Ð¸ мне GPL
ÑÑебоваÑÑ, ÑÑобÑ
+вÑÑкий, кÑо полÑÑÐ°ÐµÑ Ð¿ÑогÑаммÑ, плаÑил мне
или извеÑал менÑ?</a></li>
+
+ <li><a href="#DoesTheGPLRequireAvailabilityToPublic"
+name="TOCDoesTheGPLRequireAvailabilityToPublic">ÐÑли Ñ
ÑаÑпÑоÑÑÑанÑÑ
+пÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL за денÑги, ÑÑебÑеÑÑÑ Ð»Ð¸ оÑ
Ð¼ÐµÐ½Ñ Ñакже пÑедоÑÑавиÑÑ ÐµÐµ
+обÑеÑÑÐ²Ñ Ð±ÐµÑплаÑно?</a></li>
+
+ <li><a href="#DoesTheGPLAllowNDA"
name="TOCDoesTheGPLAllowNDA">ÐозволÑÐµÑ Ð»Ð¸ мне
+GPL ÑаÑпÑоÑÑÑанÑÑÑ ÐºÐ¾Ð¿Ð¸Ð¸ по договоÑÑ Ð¾
неÑазглаÑении?</a></li>
+
+ <li><a href="#DoesTheGPLAllowModNDA"
name="TOCDoesTheGPLAllowModNDA">ÐозволÑеÑ
+ли мне GPL ÑаÑпÑоÑÑÑанÑÑÑ Ð¸Ð·Ð¼ÐµÐ½ÐµÐ½Ð½ÑÑ Ð¸Ð»Ð¸
ÑеÑÑовÑÑ Ð²ÐµÑÑÐ¸Ñ Ð¿Ð¾ договоÑÑ Ð¾
+неÑазглаÑении?</a></li>
+
+ <li><a href="#DevelopChangesUnderNDA"
name="TOCDevelopChangesUnderNDA">ÐозволÑеÑ
+ли мне GPL ÑазÑабаÑÑваÑÑ Ð¸Ð·Ð¼ÐµÐ½ÐµÐ½Ð½ÑÑ Ð²ÐµÑÑиÑ
по договоÑÑ Ð¾ неÑазглаÑении?</a></li>
+
+ <li><a href="#WhyMustIInclude" name="TOCWhyMustIInclude">ÐоÑÐµÐ¼Ñ GPL
ÑÑебÑеÑ
+пеÑедаÑи копии GPL в каждой копии
пÑогÑаммÑ?</a></li>
+
+ <li><a href="#WhatIfWorkIsShort" name="TOCWhatIfWorkIsShort">ЧÑо,
еÑли ÑабоÑа не
+намного болÑÑе Ñамой лиÑензии?</a></li>
+
+ <li><a href="#RequiredToClaimCopyright"
+name="TOCRequiredToClaimCopyright">ТÑебÑеÑÑÑ Ð»Ð¸ Ð¾Ñ Ð¼ÐµÐ½Ñ
заÑвление авÑоÑÑкиÑ
+пÑав на мои Ð¸Ð·Ð¼ÐµÐ½ÐµÐ½Ð¸Ñ Ð² пÑогÑамме под
GPL?</a></li>
+
+ <li><a href="#CombinePublicDomainWithGPL"
+name="TOCCombinePublicDomainWithGPL">ÐÑли пÑогÑамма
ÑоÑеÑÐ°ÐµÑ ÑекÑÑÑ Ð¸Ð·
+обÑеÑÑвенного доÑÑоÑÐ½Ð¸Ñ Ñ ÑекÑÑами под GPL,
Ð¼Ð¾Ð³Ñ Ð»Ð¸ Ñ Ð²Ð·ÑÑÑ ÑаÑÑÑ Ð¸Ð·
+обÑеÑÑвенного доÑÑоÑÐ½Ð¸Ñ Ð¸ полÑзоваÑÑÑÑ
еÑ, как ÑекÑÑом из обÑеÑÑвенного
+доÑÑоÑниÑ?</a></li>
+
+ <li><a href="#IWantCredit" name="TOCIWantCredit">Я Ñ
оÑÑ
пÑÐ¸Ð·Ð½Ð°Ð½Ð¸Ñ Ð·Ð° ÑвоÑ
+ÑабоÑÑ. Я Ñ
оÑÑ, ÑÑÐ¾Ð±Ñ Ð»Ñди знали, ÑÑо Ñ
напиÑал. ÐÐ¾Ð³Ñ Ñ ÑÑебоваÑÑ Ð¿ÑизнаниÑ,
+еÑли Ñ Ð¿ÑименÑÑ GPL?</a></li>
+
+ <li><a href="#GPLOmitPreamble" name="TOCGPLOmitPreamble">ÐÐ¾Ð³Ñ Ñ
опÑÑÑиÑÑ
+пÑеамбÑÐ»Ñ GPL или инÑÑÑÑкÑии по пÑименениÑ
ее Ð´Ð»Ñ ÑобÑÑвеннÑÑ
пÑогÑамм,
+ÑÑÐ¾Ð±Ñ ÑÑкономиÑÑ Ð¼ÐµÑÑо?</a></li>
+
+ <li><a href="#TOCWhatIsCompatible" name="WhatIsCompatible">ЧÑо
имеÑÑ Ð² видÑ,
+когда говоÑÑÑ, ÑÑо две лиÑензии
“ÑовмеÑÑимє?</a></li>
+
+ <li><a href="#WhatDoesCompatMean" name="TOCWhatDoesCompatMean">ЧÑо
ознаÑаÑÑ
+Ñлова “лиÑÐµÐ½Ð·Ð¸Ñ ÑовмеÑÑима Ñ GPL”?</a></li>
+
+ <li><a href="#OrigBSD" name="TOCOrigBSD">ÐоÑемÑ
пеÑвонаÑалÑÐ½Ð°Ñ Ð»Ð¸ÑÐµÐ½Ð·Ð¸Ñ BSD
+неÑовмеÑÑима Ñ GPL?</a></li>
+
+ <li><a href="#MereAggregation" name="TOCMereAggregation">Ðакова
ÑазниÑа междÑ
+“пÑоÑÑÑм ÑазмеÑением на одном
ноÑиÑеле” и “комбиниÑованием
+двÑÑ
модÑлей в одной пÑогÑамме”?</a></li>
+
+ <li><a href="#AssignCopyright" name="TOCAssignCopyright">ÐоÑемÑ
ФСÐÐ ÑÑебÑеÑ,
+ÑÑÐ¾Ð±Ñ Ñе, кÑо вноÑÐ¸Ñ Ð²ÐºÐ»Ð°Ð´ в пÑогÑаммÑ,
авÑоÑÑкие пÑава на коÑоÑÑе
+пÑÐ¸Ð½Ð°Ð´Ð»ÐµÐ¶Ð°Ñ Ð¤Ð¡ÐÐ, пеÑедавали ÑондÑ
авÑоÑÑкие пÑава? СледÑÐµÑ Ð»Ð¸ и мне делаÑÑ
+ÑÑо, еÑли мне пÑÐ¸Ð½Ð°Ð´Ð»ÐµÐ¶Ð°Ñ Ð°Ð²ÑоÑÑкие пÑава
на пÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL? ÐÑли да, Ñо
+как?</a></li>
+
+ <li><a href="#GPLCommercially" name="TOCGPLCommercially">ÐÑли Ñ
полÑзÑÑÑÑ
+пÑогÑаммой, коÑоÑÐ°Ñ Ð¿Ð¾Ð»ÑÑена на ÑÑловиÑÑ
GNU GPL, Ð¼Ð¾Ð³Ñ Ð»Ð¸ Ñ Ð²Ð¸Ð´Ð¾Ð¸Ð·Ð¼ÐµÐ½Ð¸ÑÑ
+пеÑвонаÑалÑнÑй иÑÑ
однÑй ÑекÑÑ Ð² новÑÑ
пÑогÑаммÑ, а заÑем ÑаÑпÑоÑÑÑанÑÑÑ Ð¸
+пÑодаваÑÑ ÑÑÑ Ð½Ð¾Ð²ÑÑ Ð¿ÑогÑаммÑ
коммеÑÑеÑки?</a></li>
+
+ <li><a href="#GPLOtherThanSoftware"
name="TOCGPLOtherThanSoftware">ÐÐ¾Ð³Ñ Ñ
+пÑименÑÑÑ GPL Ð´Ð»Ñ Ñего-нибÑÐ´Ñ ÐºÑоме
пÑогÑамм?</a></li>
+
+ <li><a href="#LGPLJava" name="TOCLGPLJava">Ðак LGPL ÑабоÑÐ°ÐµÑ Ñ
Java?</a></li>
+
+
+ </ul>
+
+ <h4>ÐÑименение GPL в ваÑиÑ
пÑогÑаммаÑ
</h4>
+
+ <ul>
+
+ <li><a href="#CouldYouHelpApplyGPL" name="TOCCouldYouHelpApplyGPL">Ðе
могли бÑ
+Ð²Ñ Ð´Ð°ÑÑ Ð¼Ð½Ðµ подÑобнÑе ÑÐºÐ°Ð·Ð°Ð½Ð¸Ñ Ð½Ð°ÑÑеÑ
Ñого, как пÑимениÑÑ GPL к моей
+пÑогÑамме?</a></li>
+
+ <li><a href="#WhyUseGPL" name="TOCWhyUseGPL">ÐоÑÐµÐ¼Ñ Ð¼Ð½Ðµ
ÑледÑÐµÑ Ð¿ÑименÑÑÑ GNU
+GPL, а не дÑÑгие лиÑензии ÑвободнÑÑ
пÑогÑамм?</a></li>
+
+ <li><a href="#WhyMustIInclude" name="TOCWhyMustIInclude">ÐоÑÐµÐ¼Ñ GPL
ÑÑебÑеÑ
+пеÑедаÑи копии GPL в каждой копии
пÑогÑаммÑ?</a></li>
+
+ <li><a href="#WhatIfWorkIsShort" name="TOCWhatIfWorkIsShort">ЧÑо,
еÑли ÑабоÑа не
+намного болÑÑе Ñамой лиÑензии?</a></li>
+
+ <li><a href="#GPLOmitPreamble" name="TOCGPLOmitPreamble">ÐÐ¾Ð³Ñ Ñ
опÑÑÑиÑÑ
+пÑеамбÑÐ»Ñ GPL или инÑÑÑÑкÑии по пÑименениÑ
ее Ð´Ð»Ñ ÑобÑÑвеннÑÑ
пÑогÑамм,
+ÑÑÐ¾Ð±Ñ ÑÑкономиÑÑ Ð¼ÐµÑÑо?</a></li>
+
+ <li><a href="#HowIGetCopyright" name="TOCHowIGetCopyright">Ðак мне
полÑÑиÑÑ
+авÑоÑÑкие пÑава на ÑÐ²Ð¾Ñ Ð¿ÑогÑаммÑ, ÑÑобÑ
вÑпÑÑÑиÑÑ ÐµÐµ под GPL?</a></li>
+
+ <li><a href="#WhatIfSchool" name="TOCWhatIfSchool">ЧÑо, еÑли мое
ÑÑебное
+заведение заÑ
оÑÐµÑ Ð¾Ð±ÑаÑиÑÑ Ð¼Ð¾Ñ Ð¿ÑогÑаммÑ
в Ñвой неÑвободнÑй пÑогÑаммнÑй
+пÑодÑкÑ?</a></li>
+
+ <li><a href="#ReleaseUnderGPLAndNF" name="TOCReleaseUnderGPLAndNF">Ðне
Ñ
оÑелоÑÑ
+Ð±Ñ Ð²ÑпÑÑÑиÑÑ Ð½Ð°Ð¿Ð¸ÑаннÑÑ Ð¼Ð½Ð¾Ð¹ пÑогÑаммÑ
под GNU GPL, но Ñ Ñ
оÑÑ Ð¸ÑполÑзоваÑÑ
+Ñе же иÑÑ
однÑе ÑекÑÑÑ Ð² неÑвободнÑÑ
пÑогÑаммаÑ
.</a></li>
+
+ <li><a href="#CanDeveloperThirdParty"
name="TOCCanDeveloperThirdParty">ÐÐ¾Ð¶ÐµÑ Ð»Ð¸
+ÑазÑабоÑÑик пÑогÑаммÑ, ÑаÑпÑоÑÑÑанÑвÑий
ее по GPL, впоÑледÑÑвии пеÑедаÑÑ
+иÑклÑÑиÑелÑнÑе пÑава на нее дÑÑгой
ÑÑоÑоне?</a></li>
+
+ <li><a href="#GPLUSGov" name="TOCGPLUSGov">ÐÐ¾Ð¶ÐµÑ Ð»Ð¸
пÑавиÑелÑÑÑво СШРвÑпÑÑÑиÑÑ
+пÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GNU GPL?</a></li>
+
+ <li><a href="#GPLUSGovAdd" name="TOCGPLUSGovAdd">ÐÐ¾Ð¶ÐµÑ Ð»Ð¸
пÑавиÑелÑÑÑво СШÐ
+вÑпÑÑкаÑÑ ÑлÑÑÑÐµÐ½Ð¸Ñ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL?</a></li>
+
+ <li><a href="#VersionThreeOrLater"
name="TOCVersionTwoOrLater">ÐоÑÐµÐ¼Ñ Ð²
+пÑогÑаммаÑ
должно бÑÑÑ Ñказано
“веÑÑÐ¸Ñ 2 GPL или лÑÐ±Ð°Ñ Ð±Ð¾Ð»ÐµÐµ
+позднÑÑ Ð²ÐµÑÑиє?</a></li>
+
+ <li><a href="#GPLOutput" name="TOCGPLOutput">ÐÑÑÑ Ð»Ð¸ ÑпоÑоб
ÑаÑпÑоÑÑÑаниÑÑ GPL
+на вÑÑ
однÑе даннÑе, коÑоÑÑе лÑди полÑÑаÑÑ
пÑи полÑзовании моей пÑогÑаммой?
+ÐапÑимеÑ, еÑли Ð¼Ð¾Ñ Ð¿ÑогÑамма пÑименÑеÑÑÑ
Ð´Ð»Ñ ÑазÑабоÑки аппаÑаÑÑÑÑ, Ð¼Ð¾Ð³Ñ Ñ
+поÑÑебоваÑÑ, ÑÑÐ¾Ð±Ñ ÑÑи ÑазÑабоÑки бÑли
ÑвободнÑ?</a></li>
+
+ <li><a href="#WhyNotGPLForManuals"
name="TOCWhyNotGPLForManuals">ÐоÑÐµÐ¼Ñ Ð²Ñ Ð½Ðµ
+пÑименÑеÑе GPL Ð´Ð»Ñ ÑÑководÑÑв?</a></li>
+
+ <li><a href="#FontException" name="TOCFontException">ÐÑименима
ли GPL к
+ÑÑиÑÑам?</a></li>
+
+ <li><a href="#WMS" name="TOCWMS">ÐакÑÑ Ð»Ð¸ÑÐµÐ½Ð·Ð¸Ñ Ð¼Ð½Ðµ
иÑполÑзоваÑÑ Ð´Ð»Ñ Ñаблонов
+ÑиÑÑÐµÐ¼Ñ Ð¿Ð¾Ð´Ð´ÐµÑжки ÑайÑа?</a></li>
+
+ <li><a href="#NonFreeTools" name="TOCNonFreeTools">ÐÐ¾Ð³Ñ Ñ
вÑпÑÑÑиÑÑ Ð¿ÑогÑаммÑ,
+коÑоÑÑÑ Ñ ÑазÑабоÑал Ñ Ð¿Ð¾Ð¼Ð¾ÑÑÑ Ð½ÐµÑвободнÑÑ
ÑÑедÑÑв, под GPL?</a></li>
+ </ul>
+
+ <h4>РаÑпÑоÑÑÑанение пÑогÑамм, вÑпÑÑеннÑÑ
под GPL</h4>
+
+ <ul>
+
+ <li><a href="#ModifiedJustBinary" name="TOCModifiedJustBinary">ÐÐ¾Ð³Ñ Ñ
вÑпÑÑÑиÑÑ
+измененнÑÑ Ð²ÐµÑÑÐ¸Ñ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL ÑолÑко
в двоиÑном виде?</a></li>
+
+ <li><a href="#UnchangedJustBinary" name="TOCUnchangedJustBinary">Я
взÑл по ÑеÑи
+ÑолÑко двоиÑнÑй Ñайл. ÐÑли Ñ ÑаÑпÑоÑÑÑанÑÑ
копии, должен ли Ñ Ð¿Ð¾Ð»ÑÑиÑÑ
+иÑÑ
однÑй ÑекÑÑ Ð¸ ÑаÑпÑоÑÑÑанÑÑÑ ÐµÐ³Ð¾
Ñоже?</a></li>
+
+ <li><a href="#DistributeWithSourceOnInternet"
+name="TOCDistributeWithSourceOnInternet">Я Ñ
оÑÑ
ÑаÑпÑоÑÑÑанÑÑÑ Ð´Ð²Ð¾Ð¸ÑнÑе
+ÑÐ°Ð¹Ð»Ñ Ð½Ð° ÑизиÑеÑком ноÑиÑеле без
ÑопÑовождаÑÑиÑ
иÑÑ
однÑÑ
ÑекÑÑов. ÐÐ¾Ð³Ñ Ñ
+поÑÑавлÑÑÑ Ð¸ÑÑ
однÑй ÑекÑÑ Ð¿Ð¾ FTP вмеÑÑо
заказа по поÑÑе?</a></li>
+
+ <li><a href="#RedistributedBinariesGetSource"
+name="TOCRedistributedBinariesGetSource">Ðой знакомÑй
полÑÑил двоиÑнÑй Ñайл
+под GPL Ñ Ð¿Ñедложением поÑÑавки иÑÑ
одного
ÑекÑÑа и Ñделал Ð´Ð»Ñ Ð¼ÐµÐ½Ñ
+копиÑ. ÐÐ¾Ð³Ñ Ñ Ð²Ð¾ÑполÑзоваÑÑÑÑ
пÑедложением, ÑÑÐ¾Ð±Ñ Ð¿Ð¾Ð»ÑÑиÑÑ Ð¸ÑÑ
однÑй
+ÑекÑÑ?</a></li>
+
+ <li><a href="#SourceAndBinaryOnDifferentSites"
+name="TOCSourceAndBinaryOnDifferentSites">ÐÐ¾Ð³Ñ Ñ ÑазмеÑÑиÑÑ
двоиÑнÑе ÑайлÑ
+на Ñвоем ÑеÑвеÑе в ÐнÑеÑнеÑе, а иÑÑ
однÑе
ÑекÑÑÑ — на дÑÑгом
+ÑайÑе?</a></li>
+
+ <li><a href="#DistributeExtendedBinary"
name="TOCDistributeExtendedBinary">Я
+Ñ
оÑÑ ÑаÑпÑоÑÑÑанÑÑÑ ÑаÑÑиÑеннÑÑ Ð²ÐµÑÑиÑ
пÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL в двоиÑной ÑоÑме.
+ÐоÑÑаÑоÑно ли ÑаÑпÑоÑÑÑанÑÑÑ Ð¸ÑÑ
однÑй
ÑекÑÑ Ð¸ÑÑ
одной веÑÑии?</a></li>
+
+ <li><a href="#DistributingSourceIsInconvenient"
+name="TOCDistributingSourceIsInconvenient">Я Ñ
оÑÑ
ÑаÑпÑоÑÑÑанÑÑÑ Ð´Ð²Ð¾Ð¸ÑнÑе
+ÑайлÑ, но ÑаÑпÑоÑÑÑанение полного иÑÑ
одного ÑекÑÑа неÑдобно. ÐÑÐ´ÐµÑ Ð»Ð¸
+доÑÑаÑоÑно, еÑли Ñ Ñ Ð´Ð²Ð¾Ð¸ÑнÑми Ñайлами
бÑÐ´Ñ Ð¿ÐµÑедаваÑÑ Ð¿Ð¾Ð»ÑзоваÑелÑм ÑоÑнÑе
+опиÑÐ°Ð½Ð¸Ñ Ð¾ÑлиÑий Ð¾Ñ “ÑÑандаÑÑной”
веÑÑии?</a></li>
+
+ <li><a href="#AnonFTPAndSendSources"
name="TOCAnonFTPAndSendSources">ÐÐ¾Ð³Ñ Ñ
+пÑедоÑÑавлÑÑÑ Ð´Ð¾ÑÑÑп к двоиÑнÑм Ñайлам на
ÑеÑвеÑе в ÑеÑи, но вÑÑÑлаÑÑ
+иÑÑ
однÑе ÑекÑÑÑ ÑолÑко Ñем, кÑо иÑ
закажеÑ?</a></li>
+
+ <li><a href="#HowCanIMakeSureEachDownloadGetsSource"
+name="TOCHowCanIMakeSureEachDownloadGetsSource">Ðак мне
гаÑанÑиÑоваÑÑ, ÑÑо
+каждÑй полÑзоваÑелÑ, полÑÑаÑÑий по ÑеÑи
двоиÑнÑе ÑайлÑ, полÑÑÐ°ÐµÑ Ñакже
+иÑÑ
однÑй ÑекÑÑ?</a></li>
+
+ <li><a href="#ReleaseNotOriginal" name="TOCReleaseNotOriginal">ÐÐ¾Ð³Ñ Ñ
вÑпÑÑкаÑÑ
+пÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ лиÑензией, в коÑоÑой
Ñказано, ÑÑо ее измененнÑе веÑÑии
+ÑаÑпÑоÑÑÑанÑÑÑ Ð¿Ð¾Ð´ GPL можно, а ÑамÑ
пеÑвонаÑалÑнÑÑ Ð²ÐµÑÑÐ¸Ñ —
+нелÑзÑ?</a></li>
+
+ <li><a href="#CompanyGPLCostsMoney" name="TOCCompanyGPLCostsMoney">Ðне
ÑолÑко
+ÑÑо ÑÑало извеÑÑно, ÑÑо Ñ Ð¾Ð´Ð½Ð¾Ð¹ компании
еÑÑÑ ÐºÐ¾Ð¿Ð¸Ñ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL, и
+ÑÑÐ¾Ð±Ñ Ð¿Ð¾Ð»ÑÑиÑÑ ÐµÐµ, нÑжно плаÑиÑÑ Ð´ÐµÐ½Ñги. Ðе
наÑÑÑаÑÑ Ð»Ð¸ они GPL, не Ð´ÐµÐ»Ð°Ñ ÐµÐµ
+доÑÑÑпной по ÐнÑеÑнеÑÑ?</a></li>
+
+ <li><a href="#UnreleasedMods" name="TOCUnreleasedMods">ФиÑма
иÑполнÑÐµÑ Ð½Ð° ÑайÑе
+модиÑиÑиÑованнÑÑ Ð²ÐµÑÑÐ¸Ñ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL.
Сказано ли в GPL, ÑÑо они должнÑ
+вÑпÑÑÑиÑÑ Ñвои модиÑиÑиÑованнÑе иÑÑ
однÑе
ÑекÑÑÑ?</a></li>
+
+ <li><a href="#InternalDistribution"
name="TOCInternalDistribution">ЯвлÑеÑÑÑ Ð»Ð¸
+Ñазмножение и пÑименение многиÑ
копий
внÑÑÑи одной оÑганизаÑии или
+пÑедпÑиÑÑÐ¸Ñ “ÑаÑпÑоÑÑÑанением”?</a></li>
+
+ <li><a href="#StolenCopy" name="TOCStolenCopy">ÐÑли
кÑо-нибÑÐ´Ñ ÑкÑадеÑ
+компакÑ-диÑк Ñ Ð²ÐµÑÑией пÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL,
Ð´Ð°ÐµÑ Ð»Ð¸ GPL ÐµÐ¼Ñ Ð¿Ñаво
+ÑаÑпÑоÑÑÑанÑÑÑ ÑÑÑ Ð²ÐµÑÑÐ¸Ñ Ð´Ð°Ð»ÑÑе?</a></li>
+
+ <li><a href="#TradeSecretRelease" name="TOCTradeSecretRelease">ЧÑо,
еÑли
+пÑедпÑиÑÑие пеÑÐµÐ´Ð°ÐµÑ ÐºÐ¾Ð¿Ð¸Ñ ÐºÐ°Ðº
коммеÑÑеÑкÑÑ ÑайнÑ?</a></li>
+
+ <li><a href="#GPLFairUse" name="TOCGPLFairUse">ÐÑÑÑ Ð»Ð¸ Ñ Ð¼ÐµÐ½Ñ
пÑаво на
+“добÑоÑовеÑÑное иÑполÑзование” иÑÑ
одного ÑекÑÑа пÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´
+GPL?</a></li>
+
+ <li><a href="#DistributeSubsidiary"
name="TOCDistributeSubsidiary">ЯвлÑеÑÑÑ Ð»Ð¸
+ÑаÑпÑоÑÑÑанением пеÑедаÑа копии в
конÑÑолиÑÑемое доÑеÑнее пÑедпÑиÑÑие?</a></li>
+
+ <li><a href="#ClickThrough" name="TOCClickThrough">Ðожно ли в
пÑогÑамме
+ÑÑÑановки пÑоÑиÑÑ Ð»Ñдей нажаÑÑ ÐºÐ½Ð¾Ð¿ÐºÑ Ð²
знак ÑоглаÑÐ¸Ñ Ñ GPL? ÐÑли Ñ Ð¿Ð¾Ð»ÑÑаÑ
+какÑÑ-Ñо пÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾ GPL, ÑÑебÑеÑÑÑ Ð»Ð¸ оÑ
Ð¼ÐµÐ½Ñ ÑоглаÑаÑÑÑÑ Ñ Ñем Ð±Ñ Ñо ни
+бÑло?</a></li>
+
+ <li><a href="#GPLCompatInstaller" name="TOCGPLCompatInstaller">Ðне Ñ
оÑелоÑÑ Ð±Ñ
+обÑединиÑÑ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL Ñ Ð½ÐµÐºÐ¾ÑоÑого
Ñода пÑогÑаммой ÑÑÑановки. Ðолжна
+ли Ñ ÑÑой пÑогÑÐ°Ð¼Ð¼Ñ ÑÑÑановки бÑÑÑ
лиÑензиÑ, ÑовмеÑÑÐ¸Ð¼Ð°Ñ Ñ GPL?</a></li>
+
+ </ul>
+
+ <h4>ÐÑполÑзование пÑогÑамм, вÑпÑÑеннÑÑ
на
ÑÑловиÑÑ
GPL, пÑи напиÑании дÑÑгиÑ
+пÑогÑамм</h4>
+
+ <ul>
+
+ <li><a href="#GPLAndNonfreeOnSameMachine"
+name="TOCGPLAndNonfreeOnSameMachine">ÐÐ¾Ð¶ÐµÑ Ñ Ð¼ÐµÐ½Ñ Ð±ÑÑÑ
пÑогÑамма под GPL и
+не ÑвÑÐ·Ð°Ð½Ð½Ð°Ñ Ñ Ð½ÐµÐ¹ неÑÐ²Ð¾Ð±Ð¾Ð´Ð½Ð°Ñ Ð¿ÑогÑамма
на одном и Ñом же компÑÑÑеÑе?</a></li>
+
+ <li><a href="#CanIUseGPLToolsForNF"
name="TOCCanIUseGPLToolsForNF">Ðожно мне
+полÑзоваÑÑÑÑ ÑедакÑоÑами под GPL, Ñакими,
как GNU Emacs, Ð´Ð»Ñ ÑазÑабоÑки
+неÑвободнÑÑ
пÑогÑамм? Ðожно мне
полÑзоваÑÑÑÑ ÑÑедÑÑвами ÑазÑабоÑки под GPL,
+Ñакими, как GCC, ÑÑÐ¾Ð±Ñ ÐºÐ¾Ð¼Ð¿Ð¸Ð»Ð¸ÑоваÑÑ Ð¸Ñ
?</a></li>
+
+ <li><a href="#GPLOutput" name="TOCGPLOutput">ÐÑÑÑ Ð»Ð¸ ÑпоÑоб
ÑаÑпÑоÑÑÑаниÑÑ GPL
+на вÑÑ
однÑе даннÑе, коÑоÑÑе лÑди полÑÑаÑÑ
пÑи полÑзовании моей пÑогÑаммой?
+ÐапÑимеÑ, еÑли Ð¼Ð¾Ñ Ð¿ÑогÑамма пÑименÑеÑÑÑ
Ð´Ð»Ñ ÑазÑабоÑки аппаÑаÑÑÑÑ, Ð¼Ð¾Ð³Ñ Ñ
+поÑÑебоваÑÑ, ÑÑÐ¾Ð±Ñ ÑÑи ÑазÑабоÑки бÑли
ÑвободнÑ?</a></li>
+
+ <li><a href="#WhatCaseIsOutputGPL" name="TOCWhatCaseIsOutputGPL">Ð
какиÑ
ÑлÑÑаÑÑ
+GPL ÑаÑпÑоÑÑÑанÑеÑÑÑ Ð¸ на ÑезÑлÑÑÐ°Ñ ÑабоÑÑ
пÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL?</a></li>
+
+ <li><a href="#PortProgramToGL" name="TOCPortProgramToGL">ÐÑли Ñ
пеÑеноÑÑ ÑвоÑ
+пÑогÑÐ°Ð¼Ð¼Ñ Ð½Ð° GNU/Linux, знаÑÐ¸Ñ Ð»Ð¸ ÑÑо, ÑÑо мне
необÑ
одимо вÑпÑÑÑиÑÑ ÐµÐµ как
+ÑвободнÑÑ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL или дÑÑгой
лиÑензией ÑвободнÑÑ
пÑогÑамм?</a></li>
+
+ <li><a href="#GPLInProprietarySystem"
name="TOCGPLInProprietarySystem">Ðне
+Ñ
оÑелоÑÑ Ð±Ñ Ð²ÐºÐ»ÑÑиÑÑ Ð¿ÑогÑаммÑ,
ÑаÑпÑоÑÑÑанÑемÑÑ Ð¿Ð¾ GPL, в ÑÐ²Ð¾Ñ Ð½ÐµÑвободнÑÑ
+ÑиÑÑемÑ. Ðожно мне ÑÑо делаÑÑ?</a></li>
+
+ <li><a href="#LibGCCException"
name="TOCLibGCCException">ÐопÑÑÐºÐ°ÐµÑ Ð»Ð¸ иÑклÑÑение
+libstdc++ динамиÑеÑкое ÑвÑзÑвание?</a></li>
+
+ </ul>
+
+ <h4>ÐомбиниÑование ÑабоÑÑ Ñ ÑекÑÑами,
вÑпÑÑеннÑми на ÑÑловиÑÑ
GPL</h4>
+
+ <ul>
+
+ <li><a href="#MereAggregation" name="TOCMereAggregation">Ðакова
ÑазниÑа междÑ
+“пÑоÑÑÑм ÑазмеÑением на одном
ноÑиÑеле” и “комбиниÑованием
+двÑÑ
модÑлей в одной пÑогÑамме”?</a></li>
+
+ <li><a href="#GPLFairUse" name="TOCGPLFairUse">ÐÑÑÑ Ð»Ð¸ Ñ Ð¼ÐµÐ½Ñ
пÑаво на
+“добÑоÑовеÑÑное иÑполÑзование” иÑÑ
одного ÑекÑÑа пÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´
+GPL?</a></li>
+
+ <li><a href="#GPLUSGovAdd" name="TOCGPLUSGovAdd">ÐÐ¾Ð¶ÐµÑ Ð»Ð¸
пÑавиÑелÑÑÑво СШÐ
+вÑпÑÑкаÑÑ ÑлÑÑÑÐµÐ½Ð¸Ñ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL?</a></li>
+
+ <li><a href="#IfLibraryIsGPL" name="TOCIfLibraryIsGPL">ÐÑли
библиоÑека
+вÑпÑÑкаеÑÑÑ Ð½Ð° ÑÑловиÑÑ
GPL (не LGPL), знаÑиÑ
ли ÑÑо, ÑÑо лÑÐ±Ð°Ñ Ð¿ÑогÑамма,
+коÑоÑÐ°Ñ ÐµÑ Ð¿Ð¾Ð»ÑзÑеÑÑÑ, должна вÑпÑÑкаÑÑÑÑ
на ÑÑловиÑÑ
GPL?</a></li>
+
+ <li><a href="#LinkingWithGPL" name="TOCLinkingWithGPL">У Ð²Ð°Ñ ÐµÑÑÑ
пÑогÑамма под
+GPL, коÑоÑÑÑ Ð¼Ð½Ðµ Ñ
оÑелоÑÑ Ð±Ñ ÑкомпоноваÑÑ Ñ
моими пÑогÑаммами, ÑÑобÑ
+полÑÑиÑÑ Ð½ÐµÑвободнÑÑ Ð¿ÑогÑаммÑ. ÐзнаÑаеÑ
ли ÑÐ°ÐºÑ ÐºÐ¾Ð¼Ð¿Ð¾Ð½Ð¾Ð²ÐºÐ¸ Ñ Ð²Ð°Ñей
+пÑогÑаммой, ÑÑо Ð¾Ñ Ð¼ÐµÐ½Ñ ÑÑебÑеÑÑÑ
вÑпÑÑкаÑÑ ÑÐ²Ð¾Ñ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL?</a></li>
+
+ <li><a href="#SwitchToLGPL" name="TOCSwitchToLGPL">Ð Ñаком
ÑлÑÑае, еÑÑÑ Ð»Ð¸ Ñ
+Ð¼ÐµÐ½Ñ Ñ
оÑÑ ÐºÐ°ÐºÐ°Ñ-Ñо надежда на полÑÑение оÑ
Ð²Ð°Ñ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð½Ð° ÑÑловиÑÑ
ÐенÑÑей
+GPL?</a></li>
+
+ <li><a href="#WillYouMakeAnException"
+name="TOCWillYouMakeAnException">ÐÑименение опÑеделенной
пÑогÑÐ°Ð¼Ð¼Ñ GNU под
+GPL не ÑкладÑваеÑÑÑ Ð² Ð½Ð°Ñ Ð¿ÑÐ¾ÐµÐºÑ Ð¿Ð¾ ÑозданиÑ
неÑвободнÑÑ
пÑогÑамм. Ðе
+ÑделаеÑе ли Ð²Ñ Ð´Ð»Ñ Ð½Ð°Ñ Ð¸ÑклÑÑениÑ? ÐÑо
ознаÑало Ð²Ñ Ð±Ð¾Ð»ÑÑее ÑиÑло
+полÑзоваÑелей ÑÑой пÑогÑаммÑ.</a></li>
+
+ <li><a href="#IfInterpreterIsGPL" name="TOCIfInterpreterIsGPL">ÐÑли
+инÑеÑпÑеÑаÑÐ¾Ñ ÑзÑка пÑогÑаммиÑованиÑ
вÑпÑÑкаеÑÑÑ Ð¿Ð¾Ð´ GPL, знаÑÐ¸Ñ Ð»Ð¸ ÑÑо, ÑÑо
+пÑогÑÐ°Ð¼Ð¼Ñ Ð´Ð»Ñ Ð½ÐµÐ³Ð¾ Ð´Ð¾Ð»Ð¶Ð½Ñ Ð²ÑпÑÑкаÑÑÑÑ Ð½Ð°
ÑÑловиÑÑ
ÑовмеÑÑимÑÑ
Ñ GPL
+лиÑензий?</a></li>
+
+ <li><a href="#InterpreterIncompat" name="TOCInterpreterIncompat">ÐÑли
лиÑензиÑ
+инÑеÑпÑеÑаÑоÑа ÑзÑка пÑогÑаммиÑованиÑ
неÑовмеÑÑима Ñ GPL, Ð¼Ð¾Ð³Ñ Ð»Ð¸ Ñ
+вÑполнÑÑÑ Ð½Ð° нем пÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL?</a></li>
+
+ <li><a href="#GPLModuleLicense" name="TOCGPLModuleLicense">ÐÑли Ñ
добавлÑÑ
+модÑÐ»Ñ Ðº пÑогÑамме под GPL, ÑÑебÑеÑÑÑ Ð»Ð¸ оÑ
Ð¼ÐµÐ½Ñ Ð¸ÑполÑзование GPL в
+каÑеÑÑве лиÑензии Ð´Ð»Ñ Ð¼Ð¾ÐµÐ³Ð¾ модÑлÑ?</a></li>
+
+ <li><a href="#GPLAndPlugins" name="TOCGPLAndPlugins">ÐÑли
пÑогÑамма, вÑпÑÑеннаÑ
+под GPL, полÑзÑеÑÑÑ Ð²Ð½ÐµÑними модÑлÑми,
ÐºÐ°ÐºÐ¾Ð²Ñ ÑÑÐµÐ±Ð¾Ð²Ð°Ð½Ð¸Ñ Ðº лиÑензиÑм
+модÑлÑ?</a></li>
+
+ <li><a href="#GPLPluginsInNF" name="TOCGPLPluginsInNF">ÐÐ¾Ð³Ñ Ñ
пÑименÑÑÑ GPL,
+когда пиÑÑ Ð²Ð½ÐµÑний модÑÐ»Ñ Ðº неÑвободной
пÑогÑамме?</a></li>
+
+ <li><a href="#NFUseGPLPlugins" name="TOCNFUseGPLPlugins">ÐÐ¾Ð³Ñ Ñ
вÑпÑÑÑиÑÑ
+неÑвободнÑÑ Ð¿ÑогÑаммÑ, ÑоÑÑавленнÑÑ Ñак,
ÑÑÐ¾Ð±Ñ Ð¿Ð¾Ð´Ð³ÑÑжаÑÑ Ð²Ð½ÐµÑний модÑÐ»Ñ Ð¿Ð¾Ð´
+GPL?</a></li>
+
+ <li><a href="#GPLInProprietarySystem"
name="TOCGPLInProprietarySystem">Ðне
+Ñ
оÑелоÑÑ Ð±Ñ Ð²ÐºÐ»ÑÑиÑÑ Ð¿ÑогÑаммÑ,
ÑаÑпÑоÑÑÑанÑемÑÑ Ð¿Ð¾ GPL, в ÑÐ²Ð¾Ñ Ð½ÐµÑвободнÑÑ
+ÑиÑÑемÑ. Ðожно мне ÑÑо делаÑÑ?</a></li>
+
+ <li><a href="#GPLWrapper" name="TOCGPLWrapper">Ðне Ñ
оÑелоÑÑ
Ð±Ñ Ð²ÐºÐ»ÑÑиÑÑ
+пÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL в ÑÐ²Ð¾Ñ Ð½ÐµÑвободнÑÑ
ÑиÑÑемÑ. ÐÐ¾Ð³Ñ Ñ ÑÑо ÑделаÑÑ, поÑÑавив
+“обеÑÑÑваÑÑий” модÑÐ»Ñ Ð¿Ð¾Ð´
ÑовмеÑÑимой Ñ GPL неогÑаниÑиÑелÑной
+лиÑензией (как, напÑимеÑ, лиÑÐµÐ½Ð·Ð¸Ñ X11) междÑ
ÑаÑÑÑÑ, ÑаÑпÑоÑÑÑанÑемой по
+GPL, и неÑвободной ÑаÑÑÑÑ?</a></li>
+
+ <li><a href="#FSWithNFLibs" name="TOCFSWithNFLibs">ÐÐ¾Ð³Ñ Ð»Ð¸ Ñ
напиÑаÑÑ ÑвободнÑÑ
+пÑогÑаммÑ, коÑоÑÐ°Ñ Ð¿Ð¾Ð»ÑзÑеÑÑÑ
неÑвободнÑми библиоÑеками?</a></li>
+
+ <li><a href="#GPLIncompatibleLibs" name="TOCGPLIncompatibleLibs">Ðакие
+ÑÑидиÑеÑкие пÑÐ¾Ð±Ð»ÐµÐ¼Ñ Ð²Ð¾Ð·Ð½Ð¸ÐºÐ°ÑÑ, еÑли Ñ
пÑименÑÑ Ð½ÐµÑовмеÑÑимÑе Ñ GPL
+библиоÑеки Ñ Ð¿ÑогÑаммами под GPL?</a></li>
+
+ <li><a href="#WindowsRuntimeAndGPL" name="TOCWindowsRuntimeAndGPL">Я
пиÑÑ
+пÑиложение Ð´Ð»Ñ Windows на Microsoft Visual C++ (или Visual
Basic) и бÑдÑ
+вÑпÑÑкаÑÑ ÐµÐ³Ð¾ под GPL. ÐопÑÑÐºÐ°ÐµÑ Ð»Ð¸ GPL
динамиÑеÑкое ÑвÑзÑвание моей
+пÑогÑÐ°Ð¼Ð¼Ñ Ñ Ð±Ð¸Ð±Ð»Ð¸Ð¾Ñеками вÑемени
иÑÐ¿Ð¾Ð»Ð½ÐµÐ½Ð¸Ñ Visual C++ (или Visual
+Basic)?</a></li>
+
+ <li><a href="#MoneyGuzzlerInc" name="TOCMoneyGuzzlerInc">Ðне Ñ
оÑелоÑÑ Ð±Ñ
+измениÑÑ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL и ÑвÑзаÑÑ Ð¸Ñ
Ñ
библиоÑеками пеÑеноÑимоÑÑи ÐÐÐ
+“ÐаÑмоед”. Я не Ð¼Ð¾Ð³Ñ ÑаÑпÑоÑÑÑанÑÑÑ
иÑÑ
однÑй ÑекÑÑ ÑÑиÑ
+библиоÑек, Ñак ÑÑо ÐºÐ°Ð¶Ð´Ð¾Ð¼Ñ Ð¿Ð¾Ð»ÑзоваÑелÑ,
коÑоÑÑй Ñ
оÑел Ð±Ñ Ð¸Ð·Ð¼ÐµÐ½Ð¸ÑÑ ÑÑи
+веÑÑии, пÑиÑлоÑÑ Ð±Ñ Ð¿Ð¾Ð»ÑÑиÑÑ ÑÑи
библиоÑеки оÑделÑно. ÐоÑÐµÐ¼Ñ GPL не
+допÑÑÐºÐ°ÐµÑ ÑÑого?</a></li>
+
+ <li><a href="#GPLIncompatibleAlone"
name="TOCGPLIncompatibleAlone">ÐÑли в
+лиÑензии Ð´Ð»Ñ Ð¼Ð¾Ð´ÑÐ»Ñ Ð ÐµÑÑÑ ÑÑебование,
неÑовмеÑÑимое Ñ GPL, но ÑÑебование
+дейÑÑвÑеÑ, ÑолÑко когда Ð
ÑаÑпÑоÑÑÑанÑеÑÑÑ Ñам по Ñебе, а не когда он
+вклÑÑаеÑÑÑ Ð² более кÑÑпнÑÑ Ð¿ÑогÑаммÑ,
Ð´ÐµÐ»Ð°ÐµÑ Ð»Ð¸ ÑÑо лиÑÐµÐ½Ð·Ð¸Ñ Ð½ÐµÑовмеÑÑимой Ñ
+GPL? ÐÐ¾Ð³Ñ Ñ ÐºÐ¾Ð¼Ð±Ð¸Ð½Ð¸ÑоваÑÑ Ð¸Ð»Ð¸ ÑвÑзÑваÑÑ Ð Ñ
пÑогÑаммой под GPL?</a></li>
+
+ <li><a href="#OOPLang" name="TOCOOPLANG">ÐÑли в Ñаком
обÑекÑно-оÑиенÑиÑованном
+ÑзÑке, как Java, Ñ Ð¸ÑполÑзÑÑ ÐºÐ»Ð°ÑÑ Ð¿Ð¾Ð´ GPL без
изменений и обÑазÑÑ Ð¸Ð· него
+подклаÑÑ, каким обÑазом GPL влиÑÐµÑ Ð½Ð° более
кÑÑпнÑÑ Ð¿ÑогÑаммÑ?</a></li>
+
+ <li><a href="#LinkingOverControlledInterface"
+name="TOCLinkingOverControlledInterface">Ðак мне позволиÑÑ
компоноваÑÑ
+неÑвободнÑе модÑли Ñо Ñвоей библиоÑекой
под GPL ÑолÑко по опÑеделенномÑ
+пÑоÑоколÑ?</a></li>
+
+ <li><a href="#Consider" name="TOCConsider">РаÑÑмоÑÑим
ÑиÑÑаÑиÑ: 1) X вÑпÑÑкаеÑ
+веÑÑÐ¸Ñ V1 пÑоекÑа под GPL. 2) Y вноÑиÑ
доÑабоÑки в веÑÑÐ¸Ñ V2, коÑоÑÑе
+вклÑÑаÑÑ Ð¸Ð·Ð¼ÐµÐ½ÐµÐ½Ð¸Ñ Ð¸ новÑе ÑекÑÑÑ
пÑогÑамм, оÑнованнÑе на V1. 3) X Ñ
оÑеÑ
+вÑпÑÑкаÑÑ V2 под лиÑензией, оÑлиÑной Ð¾Ñ GPL.
ÐÑжно ли X ÑазÑеÑение Y?</a></li>
+
+ <li><a href="#ManyDifferentLicenses"
name="TOCManyDifferentLicenses">Ðной
+напиÑано пÑиложение, коÑоÑое компонÑеÑÑÑ
Ñ Ð±Ð¾Ð»ÑÑим ÑиÑлом ÑазнÑÑ
+ÑоÑÑавлÑÑÑиÑ
Ñ ÑазнÑми лиÑензиÑми. Я никак
не Ð¼Ð¾Ð³Ñ Ð¿Ð¾Ð½ÑÑÑ, какие ÑÑебованиÑ
+пÑедÑÑвлÑÑÑÑÑ Ðº лиÑензиÑÐ¾Ð²Ð°Ð½Ð¸Ñ Ð¼Ð¾ÐµÐ¹
пÑогÑаммÑ. Ðе бÑли Ð±Ñ Ð²Ñ Ñак лÑбезнÑ
+ÑаÑÑказаÑÑ Ð¼Ð½Ðµ, какими лиÑензиÑми Ñ Ð¼Ð¾Ð³Ñ
полÑзоваÑÑÑÑ?</a></li>
+
+ </ul>
+
+ <h4>ÐопÑоÑÑ Ð¾ наÑÑÑениÑÑ
GPL</h4>
+
+ <ul>
+
+ <li><a href="#ReportingViolation" name="TOCReportingViolation">ЧÑо
мне ÑледÑеÑ
+делаÑÑ, еÑли Ñ Ð¾Ð±Ð½Ð°ÑÑÐ¶Ð¸Ð²Ð°Ñ Ð²Ð¾Ð·Ð¼Ð¾Ð¶Ð½Ð¾Ðµ
наÑÑÑение GPL?</a></li>
+
+ <li><a href="#WhoHasThePower" name="TOCWhoHasThePower">ÐÑо впÑаве
ÑÑебоваÑÑ
+ÑоблÑÐ´ÐµÐ½Ð¸Ñ GPL?</a></li>
+
+ <li><a href="#HeardOtherLicense" name="TOCHeardOtherLicense">Ðне
говоÑили, ÑÑо
+кÑо-Ñо полÑÑил ÐºÐ¾Ð¿Ð¸Ñ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL по
дÑÑгой лиÑензии. Ðозможно ли
+ÑÑо?</a></li>
+
+ <li><a href="#DeveloperViolate" name="TOCDeveloperViolate">СвÑзан
ли ÑазÑабоÑÑик
+пÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL ÑекÑÑом лиÑензии? ÐогÑÑ Ð»Ð¸
бÑÑÑ Ð´ÐµÐ¹ÑÑÐ²Ð¸Ñ ÑазÑабоÑÑика
+наÑÑÑением GPL?</a></li>
+
+ <li><a href="#CompanyGPLCostsMoney" name="TOCCompanyGPLCostsMoney">Ðне
ÑолÑко
+ÑÑо ÑÑало извеÑÑно, ÑÑо Ñ Ð¾Ð´Ð½Ð¾Ð¹ компании
еÑÑÑ ÐºÐ¾Ð¿Ð¸Ñ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL, и
+ÑÑÐ¾Ð±Ñ Ð¿Ð¾Ð»ÑÑиÑÑ ÐµÐµ, нÑжно плаÑиÑÑ Ð´ÐµÐ½Ñги. Ðе
наÑÑÑаÑÑ Ð»Ð¸ они GPL, не Ð´ÐµÐ»Ð°Ñ ÐµÐµ
+доÑÑÑпной по ÐнÑеÑнеÑÑ?</a></li>
+
+ </ul>
+
+<hr />
+
+<dl>
+
+<dt><a href="#TOCWhatDoesGPLStandFor" name="WhatDoesGPLStandFor">Ðак
+ÑаÑÑиÑÑовÑваеÑÑÑ “GPL”?</a></dt>
+
+<dd>“GPL” ÑаÑÑиÑÑовÑваеÑÑÑ ÐºÐ°Ðº “General
Public License”
+(“СÑандаÑÑÐ½Ð°Ñ Ð¾Ð±ÑеÑÑвеннаÑ
лиÑензиє). Ðаиболее ÑиÑоко из ÑакиÑ
+лиÑензий ÑаÑпÑоÑÑÑанена СÑандаÑÑнаÑ
обÑеÑÑÐ²ÐµÐ½Ð½Ð°Ñ Ð»Ð¸ÑÐµÐ½Ð·Ð¸Ñ GNU, коÑоÑко
+обознаÑÐ°ÐµÐ¼Ð°Ñ ÐºÐ°Ðº “GNU GPL”. ÐÑо
вÑÑажение можно далÑÑе ÑокÑаÑиÑÑ
+до “GPL”, когда ÑÑно, ÑÑо имееÑÑÑ Ð² видÑ
именно GNU GPL.
+<p></p></dd>
+
+<dt><a href="#TOCDoesFreeSoftwareMeanUsingTheGPL"
+name="DoesFreeSoftwareMeanUsingTheGPL">ÐодÑазÑÐ¼ÐµÐ²Ð°ÐµÑ Ð»Ð¸
вÑÑажение
+“ÑÐ²Ð¾Ð±Ð¾Ð´Ð½Ð°Ñ Ð¿ÑогÑамма” пÑименение
GPL?</a></dt>
+
+<dd>
+ÐовÑе Ð½ÐµÑ — еÑÑÑ Ð¼Ð½Ð¾Ð³Ð¾ дÑÑгиÑ
лиÑензий ÑвободнÑÑ
пÑогÑамм. У наÑ
+еÑÑÑ <a href="/licenses/license-list.html">неполнÑй
ÑпиÑок</a>. ÐÑбаÑ
+лиÑензиÑ, коÑоÑÐ°Ñ Ð¿ÑедоÑÑавлÑеÑ
полÑзоваÑÐµÐ»Ñ <a
+href="/philosophy/free-sw.html">опÑеделеннÑе оÑобÑе
ÑвободÑ</a>, ÑвлÑеÑÑÑ
+лиÑензией ÑвободнÑÑ
пÑогÑамм.
+<p></p></dd>
+
+<dt><a href="#TOCWhyUseGPL" name="WhyUseGPL">ÐоÑÐµÐ¼Ñ Ð¼Ð½Ðµ
ÑледÑÐµÑ Ð¿ÑименÑÑÑ GNU
+GPL, а не дÑÑгие лиÑензии ÑвободнÑÑ
пÑогÑамм?</a></dt>
+
+<dd>
+GNU GPL ÑÑебÑеÑ, ÑÑÐ¾Ð±Ñ Ð²Ñе <a
href="/philosophy/pragmatic.html">вÑпÑÑеннÑе
+ÑлÑÑÑеннÑе веÑÑии бÑли ÑвободнÑми
пÑогÑаммами</a>. ÐÑо знаÑиÑ, ÑÑо вÑ
+избегаеÑе ÑиÑка необÑ
одимоÑÑи
конкÑÑиÑоваÑÑ Ñ Ð½ÐµÑвободной измененной
веÑÑией
+ваÑей ÑобÑÑвенной ÑабоÑÑ. Ðднако в
некоÑоÑÑÑ
оÑобÑÑ
ÑиÑÑаÑиÑÑ
Ð¼Ð¾Ð¶ÐµÑ Ð±ÑÑÑ
+лÑÑÑе полÑзоваÑÑÑÑ <a
href="/licenses/why-not-lgpl.html">более либеÑалÑной
+лиÑензией</a>.
+<p></p></dd>
+
+<dt><a href="#TOCDoesAllGNUSoftwareUseTheGNUGPLAsItsLicense"
+name="DoesAllGNUSoftwareUseTheGNUGPLAsItsLicense">ÐÑе ли
пÑогÑÐ°Ð¼Ð¼Ñ GNU
+иÑполÑзÑÑÑ Ð² каÑеÑÑве лиÑензии GNU GPL?</a></dt>
+
+<dd>
+ÐолÑÑинÑÑво пакеÑов пÑогÑамм GNU
иÑполÑзÑÑÑ GNU GPL, но еÑÑÑ Ð½ÐµÑколÑко
+пÑогÑамм GNU (и ÑаÑÑей пÑогÑамм), коÑоÑÑе
полÑзÑÑÑÑÑ Ð¼ÐµÐ½ÐµÐµ ÑлабÑми
+лиÑензиÑми, Ñакими, как ÐенÑÑÐ°Ñ GPL. Ðогда мÑ
Ñак поÑÑÑпаем, ÑÑо вопÑÐ¾Ñ <a
+href="/licenses/why-not-lgpl.html">ÑÑÑаÑегии</a>.
+<p></p></dd>
+
+<dt><a href="#TOCDoesUsingTheGPLForAProgramMakeItGNUSoftware"
+name="DoesUsingTheGPLForAProgramMakeItGNUSoftware">ÐÑли длÑ
пÑогÑаммÑ
+пÑименÑеÑÑÑ GPL, Ñо Ð´ÐµÐ»Ð°ÐµÑ Ð»Ð¸ ÑÑо ее
пÑогÑаммой GNU?</a></dt>
+
+<dd>
+ÐÑо Ñгодно Ð¼Ð¾Ð¶ÐµÑ Ð²ÑпÑÑÑиÑÑ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´
GNU GPL, но ÑÑо не Ð´ÐµÐ»Ð°ÐµÑ ÐµÐµ
+пакеÑом GNU.
+<p>
+СделаÑÑ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð°ÐºÐµÑом GNU знаÑиÑ
ÑделаÑÑ Ð²ÐºÐ»Ð°Ð´ в пÑÐ¾ÐµÐºÑ GNU ÑвнÑм
+обÑазом. ÐÑо пÑоиÑÑ
одиÑ, когда
ÑазÑабоÑÑики пÑогÑÐ°Ð¼Ð¼Ñ Ð¸ пÑÐ¾ÐµÐºÑ GNU даÑÑ Ð½Ð°
+ÑÑо ÑоглаÑие. ÐÑли Ð²Ñ Ð·Ð°Ð¸Ð½ÑеÑеÑÐ¾Ð²Ð°Ð½Ñ Ð²
добавлении пÑогÑÐ°Ð¼Ð¼Ñ Ð² пÑÐ¾ÐµÐºÑ GNU,
+напиÑиÑе, пожалÑйÑÑа, по адÑеÑÑ: <a
+href="mailto:address@hidden";><address@hidden></a>.
+</p></dd>
+
+<dt><a href="#TOCReportingViolation" name="ReportingViolation">ЧÑо мне
ÑледÑеÑ
+делаÑÑ, еÑли Ñ Ð¾Ð±Ð½Ð°ÑÑÐ¶Ð¸Ð²Ð°Ñ Ð²Ð¾Ð·Ð¼Ð¾Ð¶Ð½Ð¾Ðµ
наÑÑÑение GPL?</a></dt>
+
+<dd>
+Ðам ÑледÑÐµÑ <a href="/licenses/gpl-violation.html">пÑиÑлаÑÑ
оÑÑÐµÑ Ð¾Ð±
+ÑÑом</a>. СпеÑва как можно ÑÑаÑелÑнее
пÑовеÑÑÑе ÑакÑÑ. ÐаÑем ÑаÑÑкажиÑе
+пÑавообладаÑÐµÐ»Ñ Ð¸Ð»Ð¸ ÑомÑ, кÑо опÑбликовал
конкÑеÑнÑÑ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾ GPL. ÐÑли
+ÑÑо Фонд Ñвободного пÑогÑаммного
обеÑпеÑениÑ, напиÑиÑе по адÑеÑÑ: <a
+href="mailto:address@hidden";><address@hidden></a>.
+РпÑоÑивном ÑлÑÑае ÑоÑ, кÑо поддеÑживаеÑ
пÑогÑаммÑ, Ð¼Ð¾Ð¶ÐµÑ Ð±ÑÑÑ
+пÑавообладаÑелем или знаÑÑ, как Ñ Ð½Ð¸Ð¼
ÑвÑзаÑÑÑÑ, Ñак ÑÑо пÑиÑлиÑе оÑÑеÑ
+ÑомÑ, кÑо поддеÑÐ¶Ð¸Ð²Ð°ÐµÑ Ð¿ÑогÑаммÑ.
+<p></p></dd>
+
+<dt><a href="#TOCWhyDoesTheGPLPermitUsersToPublishTheirModifiedVersions"
+name="WhyDoesTheGPLPermitUsersToPublishTheirModifiedVersions">ÐоÑÐµÐ¼Ñ GPL
+ÑазÑеÑÐ°ÐµÑ Ð¿Ð¾Ð»ÑзоваÑелÑм пÑбликоваÑÑ Ñвои
измененнÑе веÑÑии?</a></dt>
+
+<dd>
+ÐÑинÑипиалÑно важнÑй аÑÐ¿ÐµÐºÑ ÑвободнÑÑ
пÑогÑамм ÑоÑÑÐ¾Ð¸Ñ Ð² Ñом, ÑÑо Ñ Ð¸Ñ
+полÑзоваÑелей еÑÑÑ Ñвобода
ÑоÑÑÑдниÑеÑÑва. ÐÑо ÑазÑеÑение ÑовеÑÑенно
+необÑ
одимо Ð´Ð»Ñ Ð¿Ð¾Ð»ÑзоваÑелей, коÑоÑÑе
желаÑÑ Ð¿Ð¾Ð¼Ð¾Ð³Ð°ÑÑ Ð´ÑÑг дÑÑÐ³Ñ Ð´ÐµÐ»Ð¸ÑÑÑÑ
+Ñвоими иÑпÑавлениÑми оÑибок и ÑлÑÑÑениÑми
Ñ Ð´ÑÑгими полÑзоваÑелÑми.
+<p>
+ÐекоÑоÑÑе пÑедлагали алÑÑеÑнаÑÐ¸Ð²Ñ GPL,
коÑоÑÑе ÑÑебÑÑÑ, ÑÑÐ¾Ð±Ñ Ð¸Ð·Ð¼ÐµÐ½ÐµÐ½Ð½Ñе
+веÑÑии пÑоÑ
одили ÑеÑез пеÑвонаÑалÑного
авÑоÑа. Ðока пеÑвонаÑалÑнÑй авÑоÑ
+ÑдовлеÑвоÑиÑелÑно поддеÑживаеÑ
пÑогÑаммÑ, ÑÑо Ð¼Ð¾Ð¶ÐµÑ Ñ
оÑоÑо ÑабоÑаÑÑ Ð½Ð°
+пÑакÑике, но еÑли авÑÐ¾Ñ Ð¿ÑекÑаÑÐ°ÐµÑ (более
или менее) делаÑÑ ÑÑо-Ñо дÑÑгое
+или не ÑдовлеÑвоÑÑÐµÑ Ð²ÑеÑ
нÑжд
полÑзоваÑелей, в ÑÑой ÑÑ
еме пÑоиÑÑ
одиÑ
+Ñбой. ÐÑоме пÑакÑиÑеÑкиÑ
пÑоблем, ÑÑа ÑÑ
ема не позволÑÐµÑ Ð¿Ð¾Ð»ÑзоваÑелÑм
+помогаÑÑ Ð´ÑÑг дÑÑгÑ.</p>
+<p>
+Ðногда пÑедлагаÑÑ ÐºÐ¾Ð½ÑÑолиÑоваÑÑ
измененнÑе веÑÑии Ð´Ð»Ñ Ð¿ÑедоÑвÑаÑениÑ
+пÑÑаниÑÑ ÑÑеди ÑазлиÑнÑÑ
веÑÑий, ÑозданнÑÑ
полÑзоваÑелÑми. Ðо наÑÐµÐ¼Ñ Ð¾Ð¿ÑÑÑ
+ÑÑа пÑÑаниÑа ÑеÑÑезной пÑÐ¾Ð±Ð»ÐµÐ¼Ñ Ð½Ðµ
пÑедÑÑавлÑеÑ. Ðне пÑоекÑа GNU Ñоздано
+множеÑÑво веÑÑий Emacs, но полÑзоваÑели иÑ
ÑазлиÑаÑÑ. GPL ÑÑебÑеÑ, ÑÑобÑ
+ÑоздаÑÐµÐ»Ñ Ð²ÐµÑÑии ÑÑавил на ней Ñвое имÑ,
ÑÑÐ¾Ð±Ñ Ð¾ÑлиÑиÑÑ ÐµÐµ Ð¾Ñ Ð´ÑÑгиÑ
веÑÑий
+и Ð´Ð»Ñ Ð¿ÑедоÑ
ÑÐ°Ð½ÐµÐ½Ð¸Ñ ÑепÑÑаÑии дÑÑгиÑ
ÑазÑабоÑÑиков.
+</p></dd>
+
+<dt><a href="#TOCGPLRequireSourcePostedPublic"
+name="GPLRequireSourcePostedPublic">ТÑебÑÐµÑ Ð»Ð¸ GPL, ÑÑÐ¾Ð±Ñ Ð¸ÑÑ
однÑй ÑекÑÑ
+измененнÑÑ
веÑÑий вÑÑÑавлÑлÑÑ Ð½Ð° вÑеобÑее
обозÑение?</a></dt>
+
+<dd>
+GPL не ÑÑебÑÐµÑ Ð¾Ñ Ð²Ð°Ñ Ð²ÑпÑÑка измененной
веÑÑии. ÐÑ Ð²Ð¾Ð»ÑÐ½Ñ Ð²Ð½Ð¾ÑиÑÑ Ð¸Ð·Ð¼ÐµÐ½ÐµÐ½Ð¸Ñ
+и пÑименÑÑÑ Ð¸Ñ
в лиÑнÑÑ
ÑелÑÑ
безо вÑÑкого
вÑпÑÑка иÑ
. ÐÑо оÑноÑиÑÑÑ Ð¸ к
+оÑганизаÑиÑм (вклÑÑÐ°Ñ ÐºÐ¾Ð¼Ð¼ÐµÑÑеÑкие);
оÑганизаÑÐ¸Ñ Ð¼Ð¾Ð¶ÐµÑ ÑоздаÑÑ
+модиÑиÑиÑованнÑÑ Ð²ÐµÑÑÐ¸Ñ Ð¸ пÑименÑÑÑ ÐµÐµ
внÑÑÑи безо вÑÑкого вÑпÑÑка ее за
+пÑÐµÐ´ÐµÐ»Ñ Ð¾ÑганизаÑии.
+<p>
+Ðо <em>еÑли</em> Ð²Ñ ÐºÐ°Ðº-Ñо вÑпÑÑкаеÑе
измененнÑÑ Ð²ÐµÑÑÐ¸Ñ Ð² ÑвеÑ, Ñо GPL
+ÑÑебÑеÑ, ÑÑÐ¾Ð±Ñ Ð²Ñ Ñделали измененнÑй иÑÑ
однÑй ÑекÑÑ Ð´Ð¾ÑÑÑпнÑм полÑзоваÑелÑм
+пÑогÑÐ°Ð¼Ð¼Ñ Ð½Ð° ÑÑловиÑÑ
GPL.</p>
+<p>
+ÐÑак, GPL Ð´Ð°ÐµÑ ÑазÑеÑение вÑпÑÑкаÑÑ
измененнÑÑ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð½Ðµ инаÑе, как
+опÑеделеннÑми ÑпоÑобами; но Ð²Ñ Ð²Ð¿Ð¾Ð»Ð½Ðµ
можеÑе ÑеÑаÑÑ, вÑпÑÑкаÑÑ ÐµÐµ или неÑ.
+</p></dd>
+
+<dt><a href="#TOCGPLAndNonfreeOnSameMachine"
+name="GPLAndNonfreeOnSameMachine">ÐÐ¾Ð¶ÐµÑ Ñ Ð¼ÐµÐ½Ñ Ð±ÑÑÑ
пÑогÑамма под GPL и не
+ÑвÑÐ·Ð°Ð½Ð½Ð°Ñ Ñ Ð½ÐµÐ¹ неÑÐ²Ð¾Ð±Ð¾Ð´Ð½Ð°Ñ Ð¿ÑогÑамма на
одном и Ñом же компÑÑÑеÑе?</a></dt>
+<dd>
+Ðа. ÐÑÐ½ÐºÑ GPL о “пÑоÑÑом ÑазмеÑении”
Ð´ÐµÐ»Ð°ÐµÑ ÑÑо ÑазÑеÑение
+ÑвнÑм, но ÑÑо ÑолÑко подÑвеÑÐ¶Ð´Ð°ÐµÑ Ñо, ÑÑо,
по наÑÐµÐ¼Ñ ÑбеждениÑ, бÑло бÑ
+веÑно в лÑбом ÑлÑÑае.
+<p></p></dd>
+
+<dt><a href="#TOCCanIDemandACopy" name="CanIDemandACopy">ÐÑли Ñ Ð·Ð½Ð°Ñ,
ÑÑо Ñ
+кого-Ñо еÑÑÑ ÐºÐ¾Ð¿Ð¸Ñ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL, Ð¼Ð¾Ð³Ñ Ð»Ð¸
Ñ ÑÑебоваÑÑ, ÑÑÐ¾Ð±Ñ Ð¾Ð½ дал мне
+копиÑ?</a></dt>
+
+<dd>
+ÐеÑ. GPL Ð´Ð°ÐµÑ ÐµÐ¼Ñ ÑазÑеÑение ÑоздаваÑÑ Ð¸
ÑаÑпÑоÑÑÑанÑÑÑ ÐºÐ¾Ð¿Ð¸Ð¸ пÑогÑаммÑ,
+<em>еÑли он ÑеÑÐ¸Ñ ÑÑо делаÑÑ</em>. У него еÑÑÑ
Ñакже пÑаво не ÑаÑпÑоÑÑÑанÑÑÑ
+пÑогÑаммÑ, еÑли Ñаково его ÑеÑение.
+<p></p></dd>
+
+<dt><a href="#TOCWhatDoesWrittenOfferValid"
name="WhatDoesWrittenOfferValid">ЧÑо
+ознаÑÐ°ÐµÑ Ð² GPL веÑÑии 2 “пиÑÑменное
пÑедложение, дейÑÑвиÑелÑное
+Ð´Ð»Ñ Ð»Ñбой ÑÑеÑÑей ÑÑоÑонє? ÐнаÑÐ¸Ñ Ð»Ð¸
ÑÑо, ÑÑо вÑе на ÑвеÑе могÑÑ
+полÑÑиÑÑ Ð¸ÑÑ
однÑй ÑекÑÑ Ð»Ñбой пÑогÑаммÑ
под GPL, вÑе Ñавно, какой
+именно?</a></dt>
+
+<dd>
+<p>ÐÑли Ð²Ñ ÑеÑили пÑедоÑÑавлÑÑÑ Ð¸ÑÑ
однÑй
ÑекÑÑ Ð¿Ð¾ пиÑÑÐ¼ÐµÐ½Ð½Ð¾Ð¼Ñ Ð¿ÑедложениÑ, Ñо
+лÑбой, кÑо поÑÑебÑÐµÑ Ð¾Ñ Ð²Ð°Ñ Ð¸ÑÑ
однÑй ÑекÑÑ,
Ð¸Ð¼ÐµÐµÑ Ð¿Ñаво его полÑÑиÑÑ.</p>
+<p>
+ÐÑли Ð²Ñ ÐºÐ¾Ð¼Ð¼ÐµÑÑеÑки ÑаÑпÑоÑÑÑанÑеÑе
двоиÑнÑе ÑайлÑ, не ÑопÑовождаемÑе
+иÑÑ
однÑм ÑекÑÑом, Ñо ÑоглаÑно GPL Ð²Ñ Ð´Ð¾Ð»Ð¶Ð½Ñ
пÑедоÑÑавиÑÑ Ð¿Ð¸ÑÑменное
+пÑедложение поÑÑавиÑÑ Ð¸ÑÑ
однÑй ÑекÑÑ
впоÑледÑÑвии. Ðогда полÑзоваÑели
+некоммеÑÑеÑки ÑаÑпÑоÑÑÑанÑÑÑ Ð¿Ð¾Ð»ÑÑеннÑе
Ð¾Ñ Ð²Ð°Ñ Ð´Ð²Ð¾Ð¸ÑнÑе ÑайлÑ, они должнÑ
+пеÑедаÑÑ ÐºÐ¾Ð¿Ð¸Ñ Ð¿Ð¸ÑÑменного пÑедложениÑ.
ÐÑо знаÑиÑ, ÑÑо Ñе, кÑо не полÑÑил
+двоиÑнÑе ÑÐ°Ð¹Ð»Ñ Ð½ÐµÐ¿Ð¾ÑÑедÑÑвенно Ð¾Ñ Ð²Ð°Ñ, вÑе
Ñавно могÑÑ Ð¿Ð¾Ð»ÑÑиÑÑ ÐºÐ¾Ð¿Ð¸Ð¸
+иÑÑ
однÑÑ
ÑекÑÑов вмеÑÑе Ñ Ð¿Ð¸ÑÑменнÑм
пÑедложением.</p>
+<p>
+ÐÑ ÑÑебÑем, ÑÑÐ¾Ð±Ñ Ð¿Ñедложение бÑло
дейÑÑвиÑелÑнÑм Ð´Ð»Ñ Ð»Ñбой ÑÑеÑÑей ÑÑоÑонÑ,
+ÑÑÐ¾Ð±Ñ Ñе, кÑо Ñаким обÑазом полÑÑил ÑÑи
двоиÑнÑе ÑÐ°Ð¹Ð»Ñ ÐºÐ¾Ñвенно, могли
+заказаÑÑ Ð¸ÑÑ
однÑй ÑекÑÑ Ñ Ð²Ð°Ñ.
+</p></dd>
+
+<dt><a href="#TOCTheGPLSaysModifiedVersions"
name="TheGPLSaysModifiedVersions">Ð
+веÑÑии 2 GPL Ñказано, ÑÑо еÑли вÑпÑÑкаÑÑÑÑ
измененнÑе веÑÑии, Ñо они должнÑ
+бÑÑÑ “лиÑензиÑованх Ð´Ð»Ñ Ð²ÑеÑ
ÑÑеÑÑиÑ
ÑÑоÑон”. ÐÑо ÑÑи
+ÑÑеÑÑи ÑÑоÑонÑ?</a></dt>
+
+<dd>
+Ð Ñазделе 2 Ñказано, ÑÑо измененнÑе веÑÑии,
коÑоÑÑе Ð²Ñ ÑаÑпÑоÑÑÑанÑеÑе,
+Ð´Ð¾Ð»Ð¶Ð½Ñ Ð±ÑÑÑ Ð»Ð¸ÑензиÑÐ¾Ð²Ð°Ð½Ñ Ð´Ð»Ñ Ð²ÑеÑ
ÑÑеÑÑиÑ
ÑÑоÑон по GPL. Слова “вÑе
+ÑÑеÑÑи ÑÑоÑонє ознаÑаÑÑ Ð°Ð±ÑолÑÑно вÑеÑ
— но ÑÑо не ÑÑебÑеÑ
+Ð¾Ñ Ð²Ð°Ñ <strong>делаÑÑ</strong> Ð´Ð»Ñ Ð½Ð¸Ñ
ÑÑо-Ñо
ÑизиÑеÑки. ÐÑо ÑолÑко знаÑиÑ,
+ÑÑо Ð²Ñ Ð´Ð°Ð»Ð¸ им ÑазÑеÑение пÑименÑÑÑ Ð²Ð°ÑÑ
веÑÑÐ¸Ñ Ð¿Ð¾ GPL.
+<p></p></dd>
+
+<dt><a href="#TOCRequiredToClaimCopyright"
+name="RequiredToClaimCopyright">ТÑебÑеÑÑÑ Ð»Ð¸ Ð¾Ñ Ð¼ÐµÐ½Ñ
заÑвление авÑоÑÑкиÑ
+пÑав на мои Ð¸Ð·Ð¼ÐµÐ½ÐµÐ½Ð¸Ñ Ð² пÑогÑамме под
GPL?</a></dt>
+
+<dd>
+ÐÑ Ð²Ð°Ñ Ð½Ðµ ÑÑебÑеÑÑÑ Ð·Ð°ÑвлÑÑÑ Ð°Ð²ÑоÑÑкие
пÑава на Ñвои изменениÑ. Ðднако в
+болÑÑинÑÑве ÑÑÑан по ÑмолÑÐ°Ð½Ð¸Ñ ÑÑо пÑоиÑÑ
Ð¾Ð´Ð¸Ñ Ð°Ð²ÑомаÑиÑеÑки, Ñак ÑÑо вам
+нÑжно Ñвно помеÑаÑÑ Ñвои Ð¸Ð·Ð¼ÐµÐ½ÐµÐ½Ð¸Ñ Ð²
обÑеÑÑвенное доÑÑоÑние, еÑли Ð²Ñ Ð½Ðµ
+Ñ
оÑиÑе, ÑÑÐ¾Ð±Ñ Ð½Ð° ниÑ
ÑаÑпÑоÑÑÑанÑлиÑÑ
иÑклÑÑиÑелÑнÑе авÑоÑÑкие пÑава.
+<p>
+ÐезавиÑимо Ð¾Ñ Ñого, заÑвиÑе ли вÑ
авÑоÑÑкие пÑава на Ñвои изменениÑ, в лÑбом
+ÑлÑÑае Ð²Ñ Ð´Ð¾Ð»Ð¶Ð½Ñ Ð²ÑпÑÑкаÑÑ Ð¸Ð·Ð¼ÐµÐ½ÐµÐ½Ð½ÑÑ
веÑÑÐ¸Ñ Ð² Ñелом под GPL (<a
+href="#GPLRequireSourcePostedPublic">еÑли Ð²Ñ Ð²Ð¾Ð¾Ð±Ñе
вÑпÑÑкаеÑе ÑвоÑ
+измененнÑÑ Ð²ÐµÑÑÐ¸Ñ </a>).
+</p></dd>
+
+
+<dt><a href="#TOCCombinePublicDomainWithGPL"
+name="CombinePublicDomainWithGPL">ÐÑли пÑогÑамма ÑоÑеÑаеÑ
ÑекÑÑÑ Ð¸Ð·
+обÑеÑÑвенного доÑÑоÑÐ½Ð¸Ñ Ñ ÑекÑÑами под GPL,
Ð¼Ð¾Ð³Ñ Ð»Ð¸ Ñ Ð²Ð·ÑÑÑ ÑаÑÑÑ Ð¸Ð·
+обÑеÑÑвенного доÑÑоÑÐ½Ð¸Ñ Ð¸ полÑзоваÑÑÑÑ
еÑ, как ÑекÑÑом из обÑеÑÑвенного
+доÑÑоÑниÑ?</a></dt>
+
+<dd>
+ÐÑ Ð¼Ð¾Ð¶ÐµÑе делаÑÑ ÑÑо, еÑли Ð²Ñ Ð¼Ð¾Ð¶ÐµÑе
понÑÑÑ, ÐºÐ°ÐºÐ°Ñ ÑаÑÑÑ Ð¾ÑноÑиÑÑÑ Ðº
+обÑеÑÑÐ²ÐµÐ½Ð½Ð¾Ð¼Ñ Ð´Ð¾ÑÑоÑниÑ, и оÑделиÑÑ ÐµÐµ оÑ
оÑÑалÑного. ÐÑли ÑекÑÑ Ð¿Ð¾Ð¼ÐµÑен в
+обÑеÑÑвенное доÑÑоÑние его ÑазÑабоÑÑиком,
он оÑÑаеÑÑÑ Ð² обÑеÑÑвенном
+доÑÑоÑнии незавиÑимо Ð¾Ñ Ñого, где он
побÑвал.
+<p></p></dd>
+
+<dt><a href="#TOCDoesTheGPLAllowMoney"
name="DoesTheGPLAllowMoney">ÐозволÑÐµÑ Ð»Ð¸
+мне GPL пÑодаваÑÑ ÐºÐ¾Ð¿Ð¸Ð¸ пÑогÑÐ°Ð¼Ð¼Ñ Ð·Ð°
денÑги?</a></dt>
+
+<dd>
+Ðа, GPL ÑазÑеÑÐ°ÐµÑ Ð´ÐµÐ»Ð°ÑÑ ÑÑо вÑем. <a
href="/philosophy/selling.html">ÐÑаво
+пÑодаваÑÑ ÐºÐ¾Ð¿Ð¸Ð¸</a> — ÑаÑÑÑ
опÑÐµÐ´ÐµÐ»ÐµÐ½Ð¸Ñ Ñвободной
+пÑогÑаммÑ. ÐÑоме одной оÑобой ÑиÑÑаÑии, на
ÑенÑ, коÑоÑÑÑ Ð²Ñ Ð¼Ð¾Ð¶ÐµÑе взимаÑÑ,
+не налагаеÑÑÑ Ð¾Ð³ÑаниÑений (ÑÑо
единÑÑвенное иÑклÑÑение —
+обÑзаÑелÑное пиÑÑменное пÑедложение
поÑÑавки иÑÑ
одного ÑекÑÑа, коÑоÑое
+должно ÑопÑовождаÑÑ Ð²ÑпÑÑк ÑолÑко
двоиÑнÑÑ
Ñайлов).
+<p></p></dd>
+
+<dt><a href="#TOCDoesTheGPLAllowDownloadFee"
+name="DoesTheGPLAllowDownloadFee">ÐозволÑÐµÑ Ð»Ð¸ мне GPL
бÑаÑÑ Ð¿Ð»Ð°ÑÑ Ð·Ð°
+полÑÑение пÑогÑÐ°Ð¼Ð¼Ñ Ñ Ð¼Ð¾ÐµÐ³Ð¾ ÑайÑа?</a></dt>
+
+<dd>
+Ðа. ÐÑ Ð¼Ð¾Ð¶ÐµÑе бÑаÑÑ Ð»ÑбÑÑ Ð¿Ð»Ð°ÑÑ, какÑÑ
ÑолÑко пожелаеÑе, за ÑаÑпÑоÑÑÑанение
+копии пÑогÑаммÑ. ÐÑли Ð²Ñ ÑаÑпÑоÑÑÑанÑеÑе
двоиÑнÑе ÑÐ°Ð¹Ð»Ñ Ð¿Ð¾ ÑеÑи, Ð²Ñ Ð´Ð¾Ð»Ð¶Ð½Ñ
+пÑедоÑÑавиÑÑ “ÑквиваленÑнÑй доÑÑÑп”
Ð´Ð»Ñ Ð¿Ð¾Ð»ÑÑÐµÐ½Ð¸Ñ Ð¸ÑÑ
одного
+ÑекÑÑа — ÑледоваÑелÑно, плаÑа за
полÑÑение по ÑеÑи иÑÑ
одного
+ÑекÑÑа не должна бÑÑÑ Ð±Ð¾Ð»ÑÑе, Ñем плаÑа за
полÑÑение двоиÑнÑÑ
Ñайлов.
+<p></p></dd>
+
+<dt><a href="#TOCDoesTheGPLAllowRequireFee"
+name="DoesTheGPLAllowRequireFee">ÐозволÑÐµÑ Ð»Ð¸ мне GPL
ÑÑебоваÑÑ, ÑÑобÑ
+вÑÑкий, кÑо полÑÑÐ°ÐµÑ Ð¿ÑогÑаммÑ, плаÑил мне
или извеÑал менÑ?</a></dt>
+
+<dd>
+ÐеÑ. ФакÑиÑеÑки подобное ÑÑебование
Ñделало Ð±Ñ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð½ÐµÑвободной. ÐÑли
+лÑди Ð´Ð¾Ð»Ð¶Ð½Ñ Ð¿Ð»Ð°ÑиÑÑ, когда они полÑÑаÑÑ
ÐºÐ¾Ð¿Ð¸Ñ Ð¿ÑогÑаммÑ, или еÑли они должнÑ
+оповеÑаÑÑ ÐºÐ¾Ð³Ð¾-Ñо конкÑеÑно, Ñо пÑогÑамма
не Ñвободна. См. <a
+href="/philosophy/free-sw.html">опÑеделение Ñвободной
пÑогÑаммÑ</a>.
+<p>
+GPL — лиÑÐµÐ½Ð·Ð¸Ñ ÑвободнÑÑ
пÑогÑамм, и
ÑледоваÑелÑно, она ÑазÑеÑаеÑ
+лÑдÑм иÑполÑзоваÑÑ Ð¸ даже ÑаÑпÑоÑÑÑанÑÑÑ
пÑогÑÐ°Ð¼Ð¼Ñ Ð±ÐµÐ· ÑÑÐµÐ±Ð¾Ð²Ð°Ð½Ð¸Ñ Ð¿Ð»Ð°ÑиÑÑ Ð·Ð°
+ÑÑо ÐºÐ¾Ð¼Ñ Ð±Ñ Ñо ни бÑло.
+</p></dd>
+
+<dt><a href="#TOCDoesTheGPLRequireAvailabilityToPublic"
+name="DoesTheGPLRequireAvailabilityToPublic">ÐÑли Ñ
ÑаÑпÑоÑÑÑанÑÑ Ð¿ÑогÑаммÑ
+под GPL за денÑги, ÑÑебÑеÑÑÑ Ð»Ð¸ Ð¾Ñ Ð¼ÐµÐ½Ñ Ñакже
пÑедоÑÑавиÑÑ ÐµÐµ обÑеÑÑвÑ
+беÑплаÑно?</a></dt>
+
+<dd>
+ÐеÑ. Ðднако еÑли кÑо-Ñо заплаÑил вам и
полÑÑил копиÑ, GPL Ð´Ð°ÐµÑ ÐµÐ¼Ñ ÑвободÑ
+вÑпÑÑкаÑÑ ÐµÐµ в обÑеÑÑве, за денÑги или
беÑплаÑно. ÐапÑимеÑ, кÑо-нибÑÐ´Ñ Ð¼Ð¾Ð³
+Ð±Ñ Ð²Ð°Ð¼ заплаÑиÑÑ, а заÑем ÑазмеÑÑиÑÑ ÑвоÑ
ÐºÐ¾Ð¿Ð¸Ñ Ð½Ð° ÑайÑе в обÑем доÑÑÑпе.
+<p></p></dd>
+
+<dt><a href="#TOCDoesTheGPLAllowNDA"
name="DoesTheGPLAllowNDA">ÐозволÑÐµÑ Ð»Ð¸ мне
+GPL ÑаÑпÑоÑÑÑанÑÑÑ ÐºÐ¾Ð¿Ð¸Ð¸ по договоÑÑ Ð¾
неÑазглаÑении?</a></dt>
+
+<dd>
+ÐеÑ. Ð GPL Ñказано, ÑÑо вÑÑкий, кÑо полÑÑаеÑ
Ð¾Ñ Ð²Ð°Ñ ÐºÐ¾Ð¿Ð¸Ñ, впÑаве
+пеÑеÑаÑпÑоÑÑÑанÑÑÑ ÐºÐ¾Ð¿Ð¸Ð¸, Ñ Ð¸Ð·Ð¼ÐµÐ½ÐµÐ½Ð¸Ñми
или без ниÑ
. Ðам не ÑазÑеÑено
+ÑаÑпÑоÑÑÑанÑÑÑ ÑабоÑÑ Ð½Ð° ÑколÑко-нибÑдÑ
более огÑаниÑиÑелÑной оÑнове.
+<p>ÐÑли кÑо-Ñо пÑоÑÐ¸Ñ Ð²Ð°Ñ Ð¿Ð¾Ð´Ð¿Ð¸ÑаÑÑ Ð´Ð¾Ð³Ð¾Ð²Ð¾Ñ
о неÑазглаÑении Ð´Ð»Ñ Ð¿Ð¾Ð»ÑÑениÑ
+пÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL, авÑоÑÑкие пÑава на
коÑоÑÑÑ Ð¿ÑÐ¸Ð½Ð°Ð´Ð»ÐµÐ¶Ð°Ñ Ð¤Ð¡ÐÐ, пожалÑйÑÑа,
+инÑоÑмиÑÑйÑе Ð½Ð°Ñ Ð½ÐµÐ¼ÐµÐ´Ð»ÐµÐ½Ð½Ð¾, напиÑав по
адÑеÑÑ: <a
+href="mailto:address@hidden";>address@hidden</a>.</p>
+<p>
+ÐÑли наÑÑÑение каÑаеÑÑÑ Ð¿ÑогÑамм под GPL,
пÑавообладаÑелÑ
+коÑоÑÑÑ
— кÑо-Ñо дÑÑгой, пожалÑйÑÑа,
пÑоинÑоÑмиÑÑйÑе ÑÑого
+пÑавообладаÑÐµÐ»Ñ ÑоÑно Ñак же, как вÑ
Ñделали Ð±Ñ ÑÑо в оÑноÑении к лÑбомÑ
+дÑÑÐ³Ð¾Ð¼Ñ Ð½Ð°ÑÑÑÐµÐ½Ð¸Ñ GPL.
+</p></dd>
+
+
+<dt><a href="#TOCDoesTheGPLAllowModNDA"
name="DoesTheGPLAllowModNDA">ÐозволÑеÑ
+ли мне GPL ÑаÑпÑоÑÑÑанÑÑÑ Ð¸Ð·Ð¼ÐµÐ½ÐµÐ½Ð½ÑÑ Ð¸Ð»Ð¸
ÑеÑÑовÑÑ Ð²ÐµÑÑÐ¸Ñ Ð¿Ð¾ договоÑÑ Ð¾
+неÑазглаÑении?</a></dt>
+
+<dd>
+ÐеÑ. Ð GPL Ñказано, ÑÑо ваÑи
модиÑиÑиÑованнÑе веÑÑии Ð´Ð¾Ð»Ð¶Ð½Ñ Ð½ÐµÑÑи вÑе
+ÑвободÑ, обÑÑвленнÑе в GPL. Так ÑÑо лÑбой,
кÑо полÑÑÐ°ÐµÑ Ð¾Ñ Ð²Ð°Ñ ÐºÐ¾Ð¿Ð¸Ñ Ð²Ð°Ñей
+веÑÑии, впÑаве ÑаÑпÑоÑÑÑанÑÑÑ ÐºÐ¾Ð¿Ð¸Ð¸ (Ñ
изменениÑми или без ниÑ
) ÑÑой
+веÑÑии. ÐÑ Ð½Ðµ можеÑе ÑаÑпÑоÑÑÑанÑÑÑ ÐºÐ°ÐºÑÑ
Ð±Ñ Ñо ни бÑло веÑÑÐ¸Ñ ÑабоÑÑ Ð½Ð°
+более огÑаниÑиÑелÑной оÑнове.
+<p></p></dd>
+
+<dt><a href="#TOCDevelopChangesUnderNDA"
name="DevelopChangesUnderNDA">ÐозволÑеÑ
+ли мне GPL ÑазÑабаÑÑваÑÑ Ð¸Ð·Ð¼ÐµÐ½ÐµÐ½Ð½ÑÑ Ð²ÐµÑÑиÑ
по договоÑÑ Ð¾ неÑазглаÑении?</a></dt>
+
+<dd>
+Ðа. ÐапÑимеÑ, Ð²Ñ Ð¼Ð¾Ð¶ÐµÑе заклÑÑиÑÑ ÐºÐ¾Ð½ÑÑакÑ
на ÑазÑабоÑÐºÑ Ð¸Ð·Ð¼ÐµÐ½ÐµÐ½Ð¸Ð¹ и
+договоÑиÑÑÑÑ Ð½Ðµ вÑпÑÑкаÑÑ <em>Ñвои
изменениÑ</em>, пока на ÑÑо не ÑоглаÑиÑÑÑ
+заказÑик. ÐÑо ÑазÑеÑаеÑÑÑ, поÑÐ¾Ð¼Ñ ÑÑо в
ÑÑом ÑлÑÑае никакие ÑекÑÑÑ Ð¿Ð¾Ð´ GPL
+не ÑаÑпÑоÑÑÑанÑÑÑÑÑ Ð½Ð° ÑÑловиÑÑ
неÑазглаÑениÑ.
+<p>
+ÐÑ Ð¼Ð¾Ð¶ÐµÑе Ñакже пеÑедаÑÑ Ñвои изменениÑ
заказÑÐ¸ÐºÑ Ð¿Ð¾ GPL, но договоÑиÑÑÑÑ Ð½Ðµ
+пеÑедаваÑÑ Ð¸Ñ
ÐºÐ¾Ð¼Ñ Ð±Ñ Ñо ни бÑло дÑÑгомÑ
без ÑоглаÑÐ¸Ñ Ð·Ð°ÐºÐ°Ð·Ñика. Ð ÑÑом
+ÑлÑÑае Ñоже никакие ÑекÑÑÑ Ð¿Ð¾Ð´ GPL не
ÑаÑпÑоÑÑÑанÑÑÑÑÑ Ð½Ð° ÑÑловиÑÑ
+неÑазглаÑÐµÐ½Ð¸Ñ Ð¸Ð»Ð¸ какиÑ
-Ñо дополниÑелÑнÑÑ
огÑаниÑений.</p>
+<p>
+GPL дала Ð±Ñ Ð¿Ñаво заказÑикÑ
пеÑеÑаÑпÑоÑÑÑанÑÑÑ Ð²Ð°ÑÑ Ð²ÐµÑÑиÑ. Ð ÑакиÑ
+обÑÑоÑÑелÑÑÑваÑ
заказÑик, веÑоÑÑно, ÑеÑиÑ
не полÑзоваÑÑÑÑ ÑÑим пÑавом, но
+оно Ñ Ð½ÐµÐ³Ð¾ <em>еÑÑÑ</em>.
+</p></dd>
+
+<dt><a href="#TOCIWantCredit" name="IWantCredit">Я Ñ
оÑÑ
пÑÐ¸Ð·Ð½Ð°Ð½Ð¸Ñ Ð·Ð° ÑвоÑ
+ÑабоÑÑ. Я Ñ
оÑÑ, ÑÑÐ¾Ð±Ñ Ð»Ñди знали, ÑÑо Ñ
напиÑал. ÐÐ¾Ð³Ñ Ñ ÑÑебоваÑÑ Ð¿ÑизнаниÑ,
+еÑли Ñ Ð¿ÑименÑÑ GPL?</a></dt>
+
+<dd>
+ÐÑ Ð±ÐµÐ·ÑÑловно можеÑе ÑÑебоваÑÑ Ð¿ÑизнаниÑ
за ÑÐ²Ð¾Ñ ÑабоÑÑ. ЧаÑÑÑ Ð¿ÑоÑедÑÑÑ
+вÑпÑÑка пÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL — запиÑÑ
пÑимеÑÐ°Ð½Ð¸Ñ Ð¾Ð± авÑоÑÑкиÑ
пÑаваÑ
+Ñ Ð²Ð°Ñим именем (пÑедполагаеÑÑÑ, ÑÑо
Ð²Ñ — пÑавообладаÑелÑ). GPL
+ÑÑебÑеÑ, ÑÑÐ¾Ð±Ñ Ð²Ñе копии неÑли
ÑооÑвеÑÑÑвÑÑÑее пÑимеÑание об авÑоÑÑкиÑ
+пÑаваÑ
.
+<p></p></dd>
+
+<dt><a href="#TOCWhyMustIInclude" name="WhyMustIInclude">ÐоÑÐµÐ¼Ñ GPL
ÑÑебÑеÑ
+пеÑедаÑи копии GPL в каждой копии
пÑогÑаммÑ?</a></dt>
+
+<dd>
+ÐеÑедаваÑÑ ÐºÐ¾Ð¿Ð¸Ñ Ð»Ð¸Ñензии Ñ Ð¿Ñоизведением
жизненно важно, ÑÑÐ¾Ð±Ñ ÐºÐ°Ð¶Ð´Ñй, кÑо
+полÑÑÐ°ÐµÑ ÐºÐ¾Ð¿Ð¸Ñ Ð¿ÑогÑаммÑ, мог знаÑÑ,
ÐºÐ°ÐºÐ¾Ð²Ñ ÐµÐ³Ð¾ пÑава.
+<p>
+Ðог Ð±Ñ Ð²Ð¾Ð·Ð½Ð¸ÐºÐ½ÑÑÑ Ñоблазн вклÑÑаÑÑ Ð°Ð´ÑÐµÑ Ð²
ÐнÑеÑнеÑе, коÑоÑÑй ÑказÑÐ²Ð°ÐµÑ Ð½Ð°
+лиÑензиÑ, вмеÑÑо Ñамой лиÑензии. Ðо Ð²Ñ Ð½Ðµ
можеÑе бÑÑÑ ÑвеÑенÑ, ÑÑо ÑÑоÑ
+адÑÐµÑ Ð²Ñе еÑе бÑÐ´ÐµÑ Ð´ÐµÐ¹ÑÑвиÑелен пÑÑÑ Ð¸Ð»Ð¸
деÑÑÑÑ Ð»ÐµÑ ÑпÑÑÑÑ. ЧеÑез двадÑаÑÑ
+Ð»ÐµÑ Ð°Ð´ÑеÑа в ÐнÑеÑнеÑе в Ñом виде, в каком
Ð¼Ñ Ð¸Ñ
знаем ÑейÑаÑ, возможно,
+болÑÑе не бÑдÑÑ ÑÑÑеÑÑвоваÑÑ.</p>
+<p>
+ÐдинÑÑвеннÑй ÑпоÑоб гаÑанÑиÑоваÑÑ, ÑÑо Ñ
лÑдей, Ñ ÐºÐ¾ÑоÑÑÑ
еÑÑÑ ÐºÐ¾Ð¿Ð¸Ñ
+пÑогÑаммÑ, бÑÐ´ÐµÑ Ð¿Ð¾ÑÑоÑÐ½Ð½Ð°Ñ Ð²Ð¾Ð·Ð¼Ð¾Ð¶Ð½Ð¾ÑÑÑ
взглÑнÑÑÑ Ð½Ð° лиÑензиÑ, неÑмоÑÑÑ Ð½Ð°
+вÑе изменениÑ, коÑоÑÑе пÑоизойдÑÑ Ð²
ÑеÑи,— вклÑÑиÑÑ ÐºÐ¾Ð¿Ð¸Ñ Ð»Ð¸Ñензии в
+пÑогÑаммÑ.
+</p></dd>
+
+<dt><a href="#TOCWhatIfWorkIsShort" name="WhatIfWorkIsShort">ЧÑо, еÑли
ÑабоÑа не
+намного болÑÑе Ñамой лиÑензии?</a></dt>
+
+<dd>
+ÐÑли оÑделÑÐ½Ð°Ñ Ð¿ÑогÑамма наÑÑолÑко
коÑоÑка, Ð²Ñ Ð¼Ð¾Ð¶ÐµÑе иÑполÑзоваÑÑ Ð´Ð»Ñ Ð½ÐµÐµ и
+пÑоÑÑÑÑ Ð²ÑеÑазÑеÑаÑÑÑÑ Ð»Ð¸ÑензиÑ, а не GNU GPL.
+<p></p></dd>
+
+<dt><a href="#TOCGPLOmitPreamble" name="GPLOmitPreamble">ÐÐ¾Ð³Ñ Ñ
опÑÑÑиÑÑ
+пÑеамбÑÐ»Ñ GPL или инÑÑÑÑкÑии по пÑименениÑ
ее Ð´Ð»Ñ ÑобÑÑвеннÑÑ
пÑогÑамм,
+ÑÑÐ¾Ð±Ñ ÑÑкономиÑÑ Ð¼ÐµÑÑо?</a></dt>
+<dd>
+ÐÑеамбÑла и инÑÑÑÑкÑии — ÑоÑÑавнÑе
ÑаÑÑи GNU GPL, они не могÑÑ
+опÑÑкаÑÑÑÑ. Ðо ÑÑÑи, на GPL ÑаÑпÑоÑÑÑанÑеÑÑÑ
авÑоÑÑкое пÑаво, и ее лиÑензиÑ
+допÑÑÐºÐ°ÐµÑ ÑолÑко доÑловное копиÑование
вÑей GPL в Ñелом (Ð²Ñ Ð¼Ð¾Ð¶ÐµÑе
+полÑзоваÑÑÑÑ ÑÑидиÑеÑкими ÑÑловиÑми,
ÑÑÐ¾Ð±Ñ ÑоÑÑавиÑÑ <a
+href="#ModifyGPL">дÑÑгÑÑ Ð»Ð¸ÑензиÑ</a>, но ÑÑо не
бÑÐ´ÐµÑ GNU GPL).
+<p>
+ÐÑеамбÑла и инÑÑÑÑкÑии добавлÑÑÑ Ð¿ÑимеÑно
до 5000 Ñимволов, менÑÑе, Ñем 1/3
+обÑего ÑазмеÑа GPL. ÐÑо не ÑоÑÑавиÑ
ÑÑÑеÑÑвенного оÑноÑиÑелÑного ÑвелиÑениÑ
+в ÑазмеÑе пакеÑа пÑогÑамм, еÑли ÑолÑко Ñам
Ð¿Ð°ÐºÐµÑ Ð½Ðµ оÑÐµÐ½Ñ Ð¼Ð°Ð»; в ÑÑом ÑлÑÑае
+Ð²Ñ Ð¼Ð¾Ð¶ÐµÑе иÑполÑзоваÑÑ Ð¸ пÑоÑÑÑÑ
вÑеÑазÑеÑаÑÑÑÑ Ð»Ð¸ÑензиÑ, а не GNU GPL.
+</p></dd>
+
+<dt><a href="#TOCWhatIsCompatible" name="WhatIsCompatible">ЧÑо имеÑÑ
в видÑ,
+когда говоÑÑÑ, ÑÑо две лиÑензии
“ÑовмеÑÑимє?</a></dt>
+
+<dd>
+ЧÑÐ¾Ð±Ñ ÐºÐ¾Ð¼Ð±Ð¸Ð½Ð¸ÑоваÑÑ Ð´Ð²Ðµ пÑогÑÐ°Ð¼Ð¼Ñ (или
ÑÑÑеÑÑвеннÑе иÑ
ÑаÑÑи) в одной более
+кÑÑпной ÑабоÑе, вам нÑжно ÑазÑеÑение
иÑполÑзоваÑÑ Ð¾Ð±Ðµ пÑогÑÐ°Ð¼Ð¼Ñ Ñаким
+обÑазом. ÐÑли лиÑензии двÑÑ
пÑогÑамм
допÑÑкаÑÑ ÑÑо, Ñо они ÑовмеÑÑимÑ. ÐÑли
+невозможно одновÑеменно ÑдовлеÑвоÑиÑÑ
ÑÑебованиÑм обеиÑ
лиÑензий, Ñо они
+неÑовмеÑÑимÑ.
+<p>
+ÐÐ»Ñ Ð½ÐµÐºÐ¾ÑоÑÑÑ
лиÑензий ÑпоÑоб
комбиниÑÐ¾Ð²Ð°Ð½Ð¸Ñ Ð¼Ð¾Ð¶ÐµÑ Ð²Ð»Ð¸ÑÑÑ Ð½Ð° Ñо,
ÑовмеÑÑимÑ
+ли они — напÑимеÑ, они могÑÑ
позволÑÑÑ ÑвÑзÑваÑÑ Ð´ÑÑг Ñ Ð´ÑÑгом
+два модÑлÑ, но не позволÑÑÑ ÑливаÑÑ Ð¸Ñ
ÑекÑÑÑ Ð² одном модÑле.</p>
+<p>
+ÐÑли Ð²Ñ Ñ
оÑиÑе пÑоÑÑо ÑÑÑановиÑÑ Ð´Ð²Ðµ
оÑделÑнÑе пÑогÑÐ°Ð¼Ð¼Ñ Ð² одной и Ñой же
+ÑиÑÑеме, необÑ
одимоÑÑи в Ñом, ÑÑÐ¾Ð±Ñ Ð¸Ñ
лиÑензии бÑли ÑовмеÑÑимÑ, неÑ, поÑомÑ
+ÑÑо ÑÑо не обÑединÑÐµÑ Ð¸Ñ
в более кÑÑпнÑÑ
ÑабоÑÑ.</p>
+</dd>
+
+<dt><a href="#TOCWhatDoesCompatMean" name="WhatDoesCompatMean">ЧÑо
ознаÑаÑÑ
+Ñлова “лиÑÐµÐ½Ð·Ð¸Ñ ÑовмеÑÑима Ñ GPL”?</a></dt>
+
+<dd>
+ÐÑо знаÑиÑ, ÑÑо ÑÑа лиÑÐµÐ½Ð·Ð¸Ñ Ð¸ GNU GPL
ÑовмеÑÑимÑ; Ð²Ñ Ð¼Ð¾Ð¶ÐµÑе комбиниÑоваÑÑ
+ÑекÑÑ, вÑпÑÑеннÑй по ÑÑой лиÑензии, Ñ
ÑекÑÑом, вÑпÑÑеннÑм по GNU GPL, в
+одной более кÑÑпной пÑогÑамме.
+<p>
+GPL ÑазÑеÑÐ°ÐµÑ Ð´ÐµÐ»Ð°ÑÑ Ñакие комбинаÑии в
ÑлÑÑае, еÑли комбинаÑÐ¸Ñ Ð²ÑпÑÑкаеÑÑÑ
+по GNU GPL. ÐÑÑÐ³Ð°Ñ Ð»Ð¸ÑÐµÐ½Ð·Ð¸Ñ ÑовмеÑÑима Ñ GPL,
еÑли она Ñоже ÑазÑеÑÐ°ÐµÑ ÑÑо.
+</p></dd>
+
+
+<dt><a href="#TOCFSWithNFLibs" name="FSWithNFLibs">ÐÐ¾Ð³Ñ Ð»Ð¸ Ñ
напиÑаÑÑ ÑвободнÑÑ
+пÑогÑаммÑ, коÑоÑÐ°Ñ Ð¿Ð¾Ð»ÑзÑеÑÑÑ
неÑвободнÑми библиоÑеками?</a></dt>
+
+<dd>
+ÐÑли Ð²Ñ ÑÑо ÑделаеÑе, ваÑей пÑогÑаммой
нелÑÐ·Ñ Ð±ÑÐ´ÐµÑ Ð¿Ð¾Ð»Ð½Ð¾Ñенно полÑзоваÑÑÑÑ
+в Ñвободной ÑÑеде. ÐÑли ваÑей пÑогÑамме
Ð´Ð»Ñ Ð²ÑÐ¿Ð¾Ð»Ð½ÐµÐ½Ð¸Ñ Ð¾Ð¿Ñеделенной ÑабоÑÑ
+необÑ
одима неÑÐ²Ð¾Ð±Ð¾Ð´Ð½Ð°Ñ Ð±Ð¸Ð±Ð»Ð¸Ð¾Ñека, Ñо
пÑогÑамма не Ð¼Ð¾Ð¶ÐµÑ Ð²ÑполнÑÑÑ ÑÑÑ
+ÑабоÑÑ Ð² миÑе ÑвободÑ. ÐÑли пÑогÑамма без
неÑвободной библиоÑеки вообÑе не
+Ð¼Ð¾Ð¶ÐµÑ Ð²ÑполнÑÑÑÑÑ, Ñо она не Ð¼Ð¾Ð¶ÐµÑ Ð±ÑÑÑ
ÑаÑÑÑÑ Ñакой Ñвободной опеÑаÑионной
+ÑиÑÑемÑ, как GNU; она ÑÑÐ¾Ð¸Ñ Ð¿Ð¾Ð»Ð½Ð¾ÑÑÑÑ Ð·Ð°
пÑеделами миÑа ÑвободÑ.
+<p>
+ÐÑак, подÑмайÑе, пожалÑйÑÑа: нелÑÐ·Ñ Ð»Ð¸
найÑи ÑпоÑоб вÑполниÑÑ ÑÑÑ ÑабоÑÑ Ð±ÐµÐ·
+полÑÐ·Ð¾Ð²Ð°Ð½Ð¸Ñ ÑÑой библиоÑекой? ÐожеÑе ли вÑ
напиÑаÑÑ ÑвободнÑÑ Ð·Ð°Ð¼ÐµÐ½Ñ ÑÑой
+библиоÑеки?</p>
+<p>
+ÐÑли пÑогÑамма Ñже напиÑана Ñ
иÑполÑзованием неÑвободной библиоÑеки,
+возможно, менÑÑÑ ÑеÑение Ñже поздно. ÐÑли
Ð²Ñ Ð²ÑпÑÑÑиÑе пÑогÑÐ°Ð¼Ð¼Ñ Ð² Ñом виде,
+в каком она еÑÑÑ, ÑÑо не бÑÐ´ÐµÑ Ñ
Ñже, Ñем
еÑли Ð²Ñ ÐµÐµ не вÑпÑÑÑиÑе. Ðо
+ÑпомÑниÑе, пожалÑйÑÑа, в Ñайле README, ÑÑо
завиÑимоÑÑÑ Ð¾Ñ Ð½ÐµÑвободной
+библиоÑеки — ÑÑо недоÑÑаÑок, и
поÑÑавÑÑе задаÑÑ Ð¸Ð·Ð¼ÐµÐ½Ð¸ÑÑ
+пÑогÑÐ°Ð¼Ð¼Ñ Ñак, ÑÑÐ¾Ð±Ñ Ð¾Ð½Ð° делала Ñо же Ñамое
без неÑвободной
+библиоÑеки. ÐÑедложиÑе, пожалÑйÑÑа, ÑомÑ,
кÑо дÑÐ¼Ð°ÐµÑ Ð² далÑнейÑем пÑовеÑÑи
+ÑÑÑеÑÑвеннÑÑ ÑабоÑÑ Ð½Ð°Ð´ пÑогÑаммой,
пÑежде вÑего оÑвободиÑÑ ÐµÐµ Ð¾Ñ ÑÑой
+завиÑимоÑÑи.</p>
+<p>
+ÐбÑаÑиÑе внимание, ÑÑо ÑоÑеÑание
опÑеделеннÑÑ
неÑвободнÑÑ
библиоÑек Ñо
+ÑвободнÑми пÑогÑаммами под GPL Ð¼Ð¾Ð¶ÐµÑ Ð±ÑÑÑ
ÑопÑÑжено Ñ ÑÑидиÑеÑкими
+пÑоблемами. Ðа более подÑобнÑми
ÑведениÑми обÑаÑайÑеÑÑ, пожалÑйÑÑа, к <a
+href="#GPLIncompatibleLibs">оÑвеÑÑ Ð½Ð° вопÑÐ¾Ñ Ð¾
пÑогÑаммаÑ
под GPL Ñ
+библиоÑеками, неÑовмеÑÑимÑми Ñ GPL</a>.
+</p></dd>
+
+
+<dt><a href="#TOCGPLIncompatibleLibs" name="GPLIncompatibleLibs">Ðакие
+ÑÑидиÑеÑкие пÑÐ¾Ð±Ð»ÐµÐ¼Ñ Ð²Ð¾Ð·Ð½Ð¸ÐºÐ°ÑÑ, еÑли Ñ
пÑименÑÑ Ð½ÐµÑовмеÑÑимÑе Ñ GPL
+библиоÑеки Ñ Ð¿ÑогÑаммами под GPL?</a></dt>
+
+<dd>
+ÐÑли библиоÑеки, Ñ ÐºÐ¾ÑоÑÑми вÑ
компонÑеÑеÑÑ, попадаÑÑ Ð¿Ð¾Ð´ ÑледÑÑÑее
+иÑклÑÑение в GPL:
+<blockquote><p>
+ Ðднако, как оÑобое иÑклÑÑение, в иÑÑ
однÑй ÑекÑÑ, коÑоÑÑй ÑаÑпÑоÑÑÑанÑеÑÑÑ,
+не обÑзаÑелÑно вклÑÑаÑÑ ÑÑо-либо из Ñого,
ÑÑо обÑÑно ÑаÑпÑоÑÑÑанÑеÑÑÑ (либо
+в виде иÑÑ
одного ÑекÑÑа, либо в двоиÑной
ÑоÑме) Ñ Ð¾ÑновнÑми компоненÑами
+(компилÑÑоÑом, ÑдÑом и Ñак далее)
опеÑаÑионной ÑиÑÑемÑ, под ÑпÑавлением
+коÑоÑой ÑÑÐ¾Ñ Ð¸ÑполнÑемÑй Ñайл ÑабоÑаеÑ,
еÑли ÑÑÐ¾Ñ ÐºÐ¾Ð¼Ð¿Ð¾Ð½ÐµÐ½Ñ Ñам не
+ÑопÑÐ¾Ð²Ð¾Ð¶Ð´Ð°ÐµÑ Ð¸ÑполнÑемÑй Ñайл.
+</p></blockquote>
+<p>
+Ñо Ð²Ñ Ð½Ðµ обÑÐ·Ð°Ð½Ñ Ð´ÐµÐ»Ð°ÑÑ ÑÑо-Ñо оÑобо, ÑÑобÑ
пÑименÑÑÑ Ð¸Ñ
; ÑÑебование
+ÑаÑпÑоÑÑÑанÑÑÑ Ð¸ÑÑ
однÑй ÑекÑÑ Ð²Ñей
пÑогÑÐ°Ð¼Ð¼Ñ Ð½Ðµ вклÑÑÐ°ÐµÑ ÑÑи библиоÑеки,
+даже еÑли Ð²Ñ ÑаÑпÑоÑÑÑанÑеÑе иÑ
в
Ñкомпонованном иÑполнÑемом Ñайле. Таким
+обÑазом, еÑли библиоÑеки, коÑоÑÑе вам
нÑжнÑ, поÑÑавлÑÑÑÑÑ Ñ Ð¾ÑновнÑми
+компоненÑами неÑвободной опеÑаÑионной
ÑиÑÑемÑ, в GPL Ñказано, ÑÑо лÑди могÑÑ
+компоноваÑÑ Ð²Ð°ÑÑ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ñ Ð½Ð¸Ð¼Ð¸ безо
вÑÑкиÑ
ÑÑловий.
+</p><p>
+ÐÑли Ð²Ñ Ñ
оÑиÑе, ÑÑÐ¾Ð±Ñ Ð²Ð°Ñа пÑогÑамма
компоновалаÑÑ Ñ Ð±Ð¸Ð±Ð»Ð¸Ð¾Ñекой, коÑоÑÐ°Ñ Ð½Ðµ
+Ð¿Ð¾Ð¿Ð°Ð´Ð°ÐµÑ Ð¿Ð¾Ð´ ÑÑо иÑклÑÑение, вам нÑжно
добавиÑÑ Ñвое ÑобÑÑвенное иÑклÑÑение,
+полноÑÑÑÑ Ð²Ð½ÐµÑнее по оÑноÑÐµÐ½Ð¸Ñ Ðº GPL.
СледÑÑÑее Ñведомление об авÑоÑÑкиÑ
+пÑаваÑ
и о лиÑензии Ð´Ð°ÐµÑ ÑазÑеÑение
компоноваÑÑ Ñ Ð¿ÑогÑаммой ÐÐÐ:</p>
+
+<blockquote><p>
+ Copyright (C) [годÑ] <Ð¸Ð¼Ñ Ð¿ÑавообладаÑелÑ>
+</p><p>
+ ÐÑа пÑогÑамма Ñвободна; Ð²Ñ Ð¼Ð¾Ð¶ÐµÑе
пеÑеÑаÑпÑоÑÑÑанÑÑÑ Ð¸/или изменÑÑÑ ÐµÐµ на
+ÑÑловиÑÑ
СÑандаÑÑной обÑеÑÑвенной
лиÑензии GNU, опÑбликованной Фондом
+Ñвободного пÑогÑаммного обеÑпеÑениÑ; либо
веÑÑии 2 ÑÑой лиÑензии, либо
+(по ваÑÐµÐ¼Ñ Ð²ÑбоÑÑ) лÑбой более поздней
веÑÑии.
+</p><p>
+ ÐÑа пÑогÑамма ÑаÑпÑоÑÑÑанÑеÑÑÑ Ð²
надежде на Ñо, ÑÑо бÑÐ´ÐµÑ Ð¿Ð¾Ð»ÐµÐ·Ð½Ð¾Ð¹, но ÐÐÐÐ
+ÐСЯÐÐÐ ÐÐÐ ÐÐТÐÐ; даже без неÑвной гаÑанÑии
ТÐÐÐÐ ÐÐÐÐ ÐÐÐРили ÐÐ ÐÐÐÐÐÐСТÐ
+ÐÐЯ ÐÐÐ ÐÐÐÐÐÐÐЫХ ÐУÐÐ. ÐодÑобноÑÑи Ñм. в
СÑандаÑÑной обÑеÑÑвенной лиÑензии
+GNU.
+</p><p>
+ ÐÑ Ð´Ð¾Ð»Ð¶Ð½Ñ Ð±Ñли полÑÑиÑÑ ÐºÐ¾Ð¿Ð¸Ñ
СÑандаÑÑной обÑеÑÑвенной лиÑензии GNU
вмеÑÑе Ñ
+ÑÑой пÑогÑаммой; еÑли ÑÑо не Ñак, напиÑиÑе
по адÑеÑÑ: Free Software
+Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
+</p>
+
+<p>Ð ÑезÑлÑÑаÑе ÐинамиÑеÑкой или
ÑÑаÑиÑеÑкой компоновки ÐÐÐ Ñ Ð´ÑÑгими
модÑлÑми
+полÑÑаеÑÑÑ Ð¿Ñоизведение, пÑоизводное оÑ
ÐÐÐ. Таким обÑазом, ÑÑÐ»Ð¾Ð²Ð¸Ñ Ð¸
+ÑÑÐµÐ±Ð¾Ð²Ð°Ð½Ð¸Ñ Ð¡ÑандаÑÑной обÑеÑÑвенной
лиÑензии GNU ÑаÑпÑоÑÑÑанÑÑÑÑÑ Ð½Ð°
+комбинаÑÐ¸Ñ Ð² Ñелом.</p>
+
+<p>Рдополнение, как оÑобое иÑклÑÑение,
пÑавообладаÑели ÐÐРдаÑÑ Ð²Ð°Ð¼ ÑазÑеÑение
+комбиниÑоваÑÑ ÐÐÐ Ñо ÑвободнÑми
пÑогÑаммами или библиоÑеками, вÑпÑÑкаемÑми
+под GNU LGPL, и Ñ Ð¿ÑогÑаммами, вклÑÑеннÑми в
ÑÑандаÑÑнÑй вÑпÑÑк ÐÐРпод
+лиÑензией ÐÐÐ (или модиÑиÑиÑованнÑми
веÑÑиÑми под Ñой же лиÑензией). ÐÑ
+можеÑе копиÑоваÑÑ Ð¸ ÑаÑпÑоÑÑÑанÑÑÑ ÑакÑÑ
ÑиÑÑемÑ, ÑледÑÑ ÑÑебованиÑм GNU GPL
+в оÑноÑении ÐÐРи ÑÑебованиÑм лиÑензий
дÑÑгиÑ
пÑогÑамм, коÑоÑÑе
+иÑполÑзÑÑÑÑÑ, пÑи ÑÑловии, ÑÑо вÑ
пÑедоÑÑавлÑеÑе иÑÑ
однÑй ÑекÑÑ ÑÑиÑ
дÑÑгиÑ
+пÑогÑамм, когда и как GNU GPL ÑÑебÑеÑ
ÑаÑпÑоÑÑÑанÑÑÑ Ð¸ÑÑ
однÑй ÑекÑÑ.</p>
+
+<p>ÐбÑаÑиÑе внимание, ÑÑо Ñе, кÑо делаеÑ
измененнÑÑ Ð²ÐµÑÑÐ¸Ñ ÐÐÐ, не обÑзанÑ
+пÑедоÑÑавлÑÑÑ ÑÑо оÑобое иÑклÑÑение длÑ
ÑвоиÑ
измененнÑÑ
веÑÑий; ÑÑо ÑеÑаÑÑ
+они. СÑандаÑÑÐ½Ð°Ñ Ð¾Ð±ÑеÑÑÐ²ÐµÐ½Ð½Ð°Ñ Ð»Ð¸ÑÐµÐ½Ð·Ð¸Ñ GNU
Ð´Ð°ÐµÑ ÑазÑеÑение вÑпÑÑкаÑÑ
+измененнÑÑ Ð²ÐµÑÑÐ¸Ñ Ð±ÐµÐ· ÑÑого иÑклÑÑениÑ;
ÑÑо иÑклÑÑение Ñакже ÑоздаеÑ
+возможноÑÑÑ Ð²ÑпÑÑка измененной веÑÑии, в
коÑоÑой ÑÑо иÑклÑÑение
+пÑодлеваеÑÑÑ.</p>
+
+</blockquote>
+<p>
+Ðам ÑледÑÐµÑ ÑазмеÑÑиÑÑ ÑÑÐ¾Ñ ÑекÑÑ Ð² каждом
Ñайле, к коÑоÑÐ¾Ð¼Ñ Ð¾ÑноÑиÑÑÑ
+иÑклÑÑение.
+</p><p>
+Ðо Ð·Ð°ÐºÐ¾Ð½Ñ ÑолÑко пÑавообладаÑели
пÑогÑÐ°Ð¼Ð¼Ñ Ð¼Ð¾Ð³ÑÑ ÑанкÑиониÑоваÑÑ ÑÑо
+иÑклÑÑение. ÐÑли Ð²Ñ Ð½Ð°Ð¿Ð¸Ñали вÑÑ Ð¿ÑогÑаммÑ
Ñами, Ñо (пÑедполагаÑ, ÑÑо ваÑ
+ÑабоÑодаÑÐµÐ»Ñ Ð¸Ð»Ð¸ ÑÑебное заведение не
пÑеÑендÑÐµÑ Ð½Ð° авÑоÑÑкие пÑава) вÑ
+ÑвлÑеÑеÑÑ Ð¿ÑавообладаÑелем — Ñак ÑÑо
Ð²Ñ Ð¼Ð¾Ð¶ÐµÑе ÑанкÑиониÑоваÑÑ
+иÑклÑÑение. Ðо еÑли Ð²Ñ Ñ
оÑиÑе
воÑполÑзоваÑÑÑÑ ÑаÑÑÑми дÑÑгиÑ
пÑогÑамм
под
+GPL, напиÑаннÑÑ
дÑÑгими авÑоÑами, в Ñвоей
пÑогÑамме, Ð²Ñ Ð½Ðµ можеÑе
+ÑанкÑиониÑоваÑÑ ÑÑо иÑклÑÑение за ниÑ
. ÐÑ
Ð´Ð¾Ð»Ð¶Ð½Ñ Ð¿Ð¾Ð»ÑÑиÑÑ ÑоглаÑие оÑ
+пÑавообладаÑелей ÑÑиÑ
пÑогÑамм.
+</p><p>
+Ðогда дÑÑгие изменÑÑÑ Ð¿ÑогÑаммÑ, им не
обÑзаÑелÑно делаÑÑ ÑÑо же иÑклÑÑение
+Ð´Ð»Ñ ÑвоиÑ
ÑекÑÑов — они Ñами ÑеÑаÑÑ,
ÑделаÑÑ Ð»Ð¸ ÑÑо.
+</p><p>
+ÐÑли библиоÑеки, Ñ ÐºÐ¾ÑоÑÑми Ð²Ñ ÑобиÑаеÑеÑÑ
компоноваÑÑ Ð¿ÑогÑаммÑ,
+неÑвободнÑ, пÑоÑÑиÑе, пожалÑйÑÑа, <a
href="#FSWithNFLibs">оÑÐ²ÐµÑ Ð½Ð° вопÑÐ¾Ñ Ð¾
+напиÑании ÑвободнÑÑ
пÑогÑамм Ñ
иÑполÑзованием неÑвободнÑÑ
библиоÑек</a>.
+</p></dd>
+
+<dt><a href="#TOCHowIGetCopyright" name="HowIGetCopyright">Ðак мне
полÑÑиÑÑ
+авÑоÑÑкие пÑава на ÑÐ²Ð¾Ñ Ð¿ÑогÑаммÑ, ÑÑобÑ
вÑпÑÑÑиÑÑ ÐµÐµ под GPL?</a></dt>
+
+<dd>
+Ð ÑооÑвеÑÑÑвии Ñ ÐеÑнÑкой конвенÑией вÑе,
ÑÑо напиÑано, авÑомаÑиÑеÑки
+Ð¿Ð¾Ð¿Ð°Ð´Ð°ÐµÑ Ð¿Ð¾Ð´ дейÑÑвие авÑоÑÑкого пÑава,
как ÑолÑко оно пÑинимаеÑ
+ÑикÑиÑованнÑÑ ÑоÑмÑ. Так ÑÑо вам не нÑжно
делаÑÑ ÑÑо Ð±Ñ Ñо ни бÑло, ÑÑобÑ
+“полÑÑиÑÑ” авÑоÑÑкие пÑава на Ñо, ÑÑо
Ð²Ñ Ð¿Ð¸ÑеÑе — до
+ÑеÑ
поÑ, пока никÑо дÑÑгой не можеÑ
заÑвиÑÑ, ÑÑо он —
+пÑавообладаÑÐµÐ»Ñ Ð²Ð°Ñей ÑабоÑÑ.
+<p>
+Ðднако заÑегиÑÑÑиÑоваÑÑ Ð°Ð²ÑоÑÑкие пÑава в
СШР— оÑÐµÐ½Ñ Ð½ÐµÐ¿Ð»Ð¾Ñ
аÑ
+идеÑ. ÐÑо пÑидаÑÑ Ð²Ð°Ð¼ болÑÑе веÑа в
ÑазбиÑаÑелÑÑÑваÑ
Ñ Ð½Ð°ÑÑÑиÑелÑми в СШÐ.</p>
+<p>
+СлÑÑай, когда Ñ ÐºÑо-Ñо дÑÑгого могла бÑ
бÑÑÑ Ð²Ð¾Ð·Ð¼Ð¾Ð¶Ð½Ð¾ÑÑÑ Ð·Ð°ÑвиÑÑ Ð°Ð²ÑоÑÑкие
+пÑава — ÑÑо еÑли Ð²Ñ Ð½Ð°ÐµÐ¼Ð½Ñй ÑабоÑник
или ÑÑаÑийÑÑ; в ÑÑом ÑлÑÑае
+нанимаÑÐµÐ»Ñ Ð¸Ð»Ð¸ ÑÑебное заведение могли бÑ
заÑвиÑÑ, ÑÑо Ð²Ñ Ð´ÐµÐ»Ð°Ð»Ð¸ ÑÑÑ ÑабоÑÑ
+Ð´Ð»Ñ Ð½Ð¸Ñ
и ÑÑо авÑоÑÑкие пÑава пÑинадлежаÑ
им. ÐÑло ли Ð±Ñ Ð¸Ñ
заÑвление
+обоÑнованнÑм, завиÑÐ¸Ñ Ð¾Ñ ÑакиÑ
обÑÑоÑÑелÑÑÑв, как Ð·Ð°ÐºÐ¾Ð½Ñ ÑеÑ
меÑÑ, где вÑ
+живеÑе, Ð¾Ñ Ð²Ð°Ñего договоÑа Ñ Ð½Ð°Ð½Ð¸Ð¼Ð°Ñелем и
Ñода ÑабоÑ, коÑоÑÑе вÑ
+вÑполнÑеÑе. ÐÑли еÑÑÑ ÐºÐ°ÐºÐ¾Ðµ-Ñо Ñомнение,
лÑÑÑе вÑего пÑоконÑÑлÑÑиÑоваÑÑÑÑ Ñ
+ÑÑиÑÑом.</p>
+<p>
+ÐÑли Ð²Ñ Ð´ÑмаеÑе, ÑÑо нанимаÑÐµÐ»Ñ Ð¸Ð»Ð¸
ÑÑебное заведение могли Ð±Ñ Ð¿ÑеÑендоваÑÑ
+на авÑоÑÑкие пÑава, Ð²Ñ Ð¼Ð¾Ð¶ÐµÑе ÑÑÑÑаниÑÑ
неÑÑноÑÑÑ, полÑÑив оÑказ оÑ
+авÑоÑÑкиÑ
пÑав, подпиÑаннÑй
ÑполномоÑеннÑм на ÑÑо ÑÑководиÑелем
компании или
+ÑÑебного Ð·Ð°Ð²ÐµÐ´ÐµÐ½Ð¸Ñ (Ð²Ð°Ñ Ð½ÐµÐ¿Ð¾ÑÑедÑÑвеннÑй
наÑалÑник или пÑеподаваÑÐµÐ»Ñ Ð¾Ð±ÑÑно
+<strong>не</strong> ÑполномоÑен подпиÑÑваÑÑ Ñакие
докÑменÑÑ).
+</p></dd>
+
+<dt><a href="#TOCWhatIfSchool" name="WhatIfSchool">ЧÑо, еÑли мое
ÑÑебное
+заведение заÑ
оÑÐµÑ Ð¾Ð±ÑаÑиÑÑ Ð¼Ð¾Ñ Ð¿ÑогÑаммÑ
в Ñвой неÑвободнÑй пÑогÑаммнÑй
+пÑодÑкÑ?</a></dt>
+
+<dd>
+РнаÑи дни многие ÑнивеÑÑиÑеÑÑ Ð¿ÑÑаÑÑÑÑ
ÑобиÑаÑÑ ÑондÑ, огÑаниÑиваÑ
+полÑзование знаниÑми, коÑоÑÑе они
вÑÑабаÑÑваÑÑ; ÑакÑиÑеÑки иÑ
поведение мало
+оÑлиÑаеÑÑÑ Ð¾Ñ Ð¿Ð¾Ð²ÐµÐ´ÐµÐ½Ð¸Ñ ÐºÐ¾Ð¼Ð¼ÐµÑÑеÑкиÑ
пÑедпÑиÑÑий (Ñм. обÑее обÑÑждение ÑÑой
+пÑÐ¾Ð±Ð»ÐµÐ¼Ñ Ð¸ ее поÑледÑÑвий в ÑÑаÑÑе
“ÐÑибÑаннÑй ÑнивеÑÑиÑеє в
+“ÐÑланÑиÑеÑком ежемеÑÑÑнике” в
маÑÑе 2000 года).
+<p>
+ÐÑли Ð²Ñ Ð²Ð¸Ð´Ð¸Ñе, ÑÑо еÑÑÑ Ñ
оÑÑ ÐºÐ°ÐºÐ°Ñ-Ñо
возможноÑÑÑ, ÑÑо ваÑе ÑÑебное
+заведение Ð¼Ð¾Ð¶ÐµÑ Ð¾ÑказаÑÑ Ð²Ð°Ð¼ в позволении
вÑпÑÑÑиÑÑ Ð²Ð°ÑÑ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ ÐºÐ°Ðº
+ÑвободнÑÑ, лÑÑÑе вÑего поднÑÑÑ Ð²Ð¾Ð¿ÑÐ¾Ñ Ð½Ð°
как можно более Ñанней ÑÑадии. Чем
+ближе пÑогÑамма к ÑомÑ, ÑÑÐ¾Ð±Ñ Ð¿Ð¾Ð»ÐµÐ·Ð½Ð¾
ÑабоÑаÑÑ, Ñем болÑÑий Ñоблазн можеÑ
+оÑÑÑаÑÑ Ð°Ð´Ð¼Ð¸Ð½Ð¸ÑÑÑаÑиÑ, ÑÑÐ¾Ð±Ñ Ð·Ð°Ð±ÑаÑÑ ÐµÐµ Ñ
Ð²Ð°Ñ Ð¸ завеÑÑиÑÑ Ð±ÐµÐ· ваÑ. Ðа Ñанней
+ÑÑадии вам бÑÐ´ÐµÑ Ð»ÐµÐ³Ñе.</p>
+<p>
+ÐÑак, Ð¼Ñ ÑекомендÑем вам подойÑи к ним,
когда пÑогÑамма гоÑова еÑе ÑолÑко
+наполовинÑ, и ÑказаÑÑ: “ÐÑли вÑ
ÑоглаÑиÑеÑÑ Ð²ÑпÑÑÑиÑÑ ÑÑо как
+ÑвободнÑÑ Ð¿ÑогÑаммÑ, Ñ Ð´Ð¾Ð´ÐµÐ»Ð°Ñ ÐµÐµ”. Ðе
оÑноÑиÑеÑÑ Ðº ÑÑÐ¾Ð¼Ñ ÐºÐ°Ðº к
+блеÑÑ. ЧÑÐ¾Ð±Ñ Ð²ÑйÑи победиÑелем, нÑжно
имеÑÑ ÑмелоÑÑÑ ÑказаÑÑ: “ÐоÑ
+пÑогÑамма бÑÐ´ÐµÑ Ñвободна; инаÑе она не
ÑÐ²Ð¸Ð´Ð¸Ñ Ñвеє.
+</p></dd>
+
+<dt><a href="#TOCCouldYouHelpApplyGPL" name="CouldYouHelpApplyGPL">Ðе
могли бÑ
+Ð²Ñ Ð´Ð°ÑÑ Ð¼Ð½Ðµ подÑобнÑе ÑÐºÐ°Ð·Ð°Ð½Ð¸Ñ Ð½Ð°ÑÑеÑ
Ñого, как пÑимениÑÑ GPL к моей
+пÑогÑамме?</a></dt>
+
+<dd>
+См. ÑÑÑаниÑÑ Ñ <a
href="/licenses/gpl-howto.html">ÑказаниÑми по GPL</a>.
+<p></p></dd>
+
+<dt><a href="#TOCHeardOtherLicense" name="HeardOtherLicense">Ðне
говоÑили, ÑÑо
+кÑо-Ñо полÑÑил ÐºÐ¾Ð¿Ð¸Ñ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL по
дÑÑгой лиÑензии. Ðозможно ли
+ÑÑо?</a></dt>
+
+<dd>
+GNU GPL не Ð´Ð°ÐµÑ Ð¿Ð¾Ð»ÑзоваÑелÑм ÑазÑеÑениÑ
пÑилагаÑÑ Ð´ÑÑгие лиÑензии к
+пÑогÑамме. Ðо пÑавообладаÑÐµÐ»Ñ Ð¿ÑогÑаммÑ
Ð¼Ð¾Ð¶ÐµÑ Ð²ÑпÑÑкаÑÑ ÐµÐµ под неÑколÑкими
+ÑазнÑми лиÑензиÑми паÑаллелÑно. Ðдной из
ниÑ
Ð¼Ð¾Ð¶ÐµÑ Ð±ÑÑÑ GNU GPL.
+<p>
+ÐиÑензиÑ, коÑоÑÐ°Ñ ÑодеÑжиÑÑÑ Ð² ваÑей копии
(в пÑедположении, ÑÑо она бÑла
+помеÑена ÑÑда пÑавообладаÑелем и ÑÑо вÑ
полÑÑили ÐºÐ¾Ð¿Ð¸Ñ Ð·Ð°ÐºÐ¾Ð½Ð½Ñм пÑÑем),
+ÑвлÑеÑÑÑ Ð»Ð¸Ñензией, коÑоÑаÑ
ÑаÑпÑоÑÑÑанÑеÑÑÑ Ð½Ð° ваÑÑ ÐºÐ¾Ð¿Ð¸Ñ.
+</p></dd>
+
+<dt><a href="#TOCReleaseUnderGPLAndNF" name="ReleaseUnderGPLAndNF">Ðне Ñ
оÑелоÑÑ
+Ð±Ñ Ð²ÑпÑÑÑиÑÑ Ð½Ð°Ð¿Ð¸ÑаннÑÑ Ð¼Ð½Ð¾Ð¹ пÑогÑаммÑ
под GNU GPL, но Ñ Ñ
оÑÑ Ð¸ÑполÑзоваÑÑ
+Ñе же иÑÑ
однÑе ÑекÑÑÑ Ð² неÑвободнÑÑ
пÑогÑаммаÑ
.</a></dt>
+
+<dd>
+ÐÑпÑÑк неÑвободной пÑогÑÐ°Ð¼Ð¼Ñ Ð²Ñегда
ÑÑиÑеÑки неÑиÑÑ, но ÑÑидиÑеÑки Ñ Ð²Ð°Ñ Ðº
+ÑÑÐ¾Ð¼Ñ Ð½ÐµÑ Ð½Ð¸ÐºÐ°ÐºÐ¸Ñ
пÑепÑÑÑÑвий. ÐÑли
Ð²Ñ — пÑавообладаÑелÑ
+пÑогÑаммÑ, Ð²Ñ Ð¼Ð¾Ð¶ÐµÑе вÑпÑÑкаÑÑ ÐµÐµ под
ÑазнÑми неиÑклÑÑиÑелÑнÑми лиÑензиÑми в
+ÑазнÑÑ
ÑлÑÑаÑÑ
.
+<p></p></dd>
+
+<dt><a href="#TOCDeveloperViolate" name="DeveloperViolate">СвÑзан ли
ÑазÑабоÑÑик
+пÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL ÑекÑÑом лиÑензии? ÐогÑÑ Ð»Ð¸
бÑÑÑ Ð´ÐµÐ¹ÑÑÐ²Ð¸Ñ ÑазÑабоÑÑика
+наÑÑÑением GPL?</a></dt>
+
+<dd>
+СÑÑого говоÑÑ, GPL — лиÑензиÑ
ÑазÑабоÑÑика Ð´Ð»Ñ Ð¸ÑполÑзованиÑ,
+ÑаÑпÑоÑÑÑÐ°Ð½ÐµÐ½Ð¸Ñ Ð¸ Ð¸Ð·Ð¼ÐµÐ½ÐµÐ½Ð¸Ñ Ð¿ÑогÑаммÑ
дÑÑгими. Сам ÑазÑабоÑÑик не ÑвÑзан
+лиÑензией, поÑÑÐ¾Ð¼Ñ Ð½ÐµÐ·Ð°Ð²Ð¸Ñимо Ð¾Ñ Ñого, ÑÑо
Ð´ÐµÐ»Ð°ÐµÑ ÑазÑабоÑÑик, ÑÑо не
+ÑвлÑеÑÑÑ “наÑÑÑением” GPL.
+<p>
+Ðднако еÑли ÑазÑабоÑÑик Ð´ÐµÐ»Ð°ÐµÑ ÑÑо-Ñо, ÑÑо
наÑÑÑало Ð±Ñ GPL, еÑли Ð±Ñ ÑÑо
+делал кÑо-Ñо дÑÑгой, Ñо ÑазÑабоÑÑик,
неÑомненно, ÑÑÑаÑÐ¸Ñ Ñвои моÑалÑнÑе
+позиÑии в ÑообÑеÑÑве.
+</p></dd>
+
+<dt><a href="#TOCCanDeveloperThirdParty"
name="CanDeveloperThirdParty">ÐÐ¾Ð¶ÐµÑ Ð»Ð¸
+ÑазÑабоÑÑик пÑогÑаммÑ, ÑаÑпÑоÑÑÑанÑвÑий
ее по GPL, впоÑледÑÑвии пеÑедаÑÑ
+иÑклÑÑиÑелÑнÑе пÑава на нее дÑÑгой
ÑÑоÑоне?</a></dt>
+
+<dd>
+ÐеÑ, поÑÐ¾Ð¼Ñ ÑÑо обÑеÑÑво Ñже полÑÑило
пÑаво полÑзоваÑÑÑÑ Ð¿ÑогÑаммой на
+ÑÑловиÑÑ
GPL и ÑÑо пÑаво не Ð¼Ð¾Ð¶ÐµÑ Ð±ÑÑÑ
оÑозвано.
+<p></p></dd>
+
+<dt><a href="#TOCCanIUseGPLToolsForNF" name="CanIUseGPLToolsForNF">Ðожно
мне
+полÑзоваÑÑÑÑ ÑедакÑоÑами под GPL, Ñакими,
как GNU Emacs, Ð´Ð»Ñ ÑазÑабоÑки
+неÑвободнÑÑ
пÑогÑамм? Ðожно мне
полÑзоваÑÑÑÑ ÑÑедÑÑвами ÑазÑабоÑки под GPL,
+Ñакими, как GCC, ÑÑÐ¾Ð±Ñ ÐºÐ¾Ð¼Ð¿Ð¸Ð»Ð¸ÑоваÑÑ Ð¸Ñ
?</a></dt>
+
+<dd>
+Ðа, поÑÐ¾Ð¼Ñ ÑÑо авÑоÑÑкое пÑаво на
ÑедакÑоÑÑ Ð¸ ÑÑедÑÑва ÑазÑабоÑки не
+ÑаÑпÑоÑÑÑанÑеÑÑÑ Ð½Ð° Ñо, ÑÑо Ð²Ñ Ð¿Ð¸ÑеÑе.
ÐÑименение иÑ
не Ð½Ð°Ð»Ð°Ð³Ð°ÐµÑ Ð½Ð¸ÐºÐ°ÐºÐ¸Ñ
+ÑÑидиÑеÑкиÑ
огÑаниÑений на лиÑензиÑ,
коÑоÑÑÑ Ð²Ñ Ð¸ÑполÑзÑеÑе Ð´Ð»Ñ ÑвоиÑ
+пÑогÑамм.
+<p>
+ÐекоÑоÑÑе пÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾ ÑеÑ
ниÑеÑким
пÑиÑинам вÑÑавлÑÑÑ ÑаÑÑи ÑамиÑ
ÑÐµÐ±Ñ Ð²
+вÑÑ
однÑе ÑÐ°Ð¹Ð»Ñ — напÑимеÑ, Bison
копиÑÑÐµÑ ÑÑандаÑÑнÑÑ Ð¿ÑогÑаммÑ
+ÑинÑакÑиÑеÑкого анализаÑоÑа в Ñвой вÑÑ
одной Ñайл. Ð ÑакиÑ
ÑлÑÑаÑÑ
на
+ÑкопиÑованнÑй ÑекÑÑ Ð² вÑÑ
одном Ñайле
ÑаÑпÑоÑÑÑанÑеÑÑÑ Ñа же ÑÐ°Ð¼Ð°Ñ Ð»Ð¸ÑензиÑ,
+коÑоÑÐ°Ñ ÑаÑпÑоÑÑÑанÑеÑÑÑ Ð½Ð° него в ÑекÑÑе
иÑÑ
одного пакеÑа. Ð Ñо же вÑемÑ
+ÑаÑÑÑ Ð²ÑÑ
одного Ñайла, пÑÐ¾Ð¸Ð·Ð²Ð¾Ð´Ð½Ð°Ñ Ð¾Ñ Ð²Ñ
однÑÑ
даннÑÑ
пÑогÑаммÑ, наÑледÑеÑ
+авÑоÑÑко-пÑавовой ÑÑаÑÑÑ Ð²Ñ
однÑÑ
даннÑÑ
.</p>
+<p>
+ÐмеÑÑе Ñ Ñем, Bison Ñоже можно пÑименÑÑÑ Ð´Ð»Ñ
ÑазÑабоÑки неÑвободнÑÑ
+пÑогÑамм — благодаÑÑ ÑомÑ, ÑÑо мÑ
ÑеÑили Ñвно ÑазÑеÑиÑÑ
+пÑименение ÑÑандаÑÑной пÑогÑÐ°Ð¼Ð¼Ñ ÐµÐ³Ð¾
ÑинÑакÑиÑеÑкого анализаÑоÑа в вÑÑ
однÑÑ
+ÑайлаÑ
без огÑаниÑений. ÐÑ Ð¿ÑинÑли Ñакое
ÑеÑение, поÑÐ¾Ð¼Ñ ÑÑо Ñже бÑли дÑÑгие
+ÑÑедÑÑва, ÑопоÑÑавимÑе Ñ Bison, коÑоÑÑе
допÑÑкали пÑименение Ð´Ð»Ñ Ð½ÐµÑвободнÑÑ
+пÑогÑамм.
+</p></dd>
+
+<dt><a href="#TOCGPLFairUse" name="GPLFairUse">ÐÑÑÑ Ð»Ð¸ Ñ Ð¼ÐµÐ½Ñ
пÑаво на
+“добÑоÑовеÑÑное иÑполÑзование” иÑÑ
одного ÑекÑÑа пÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´
+GPL?</a></dt>
+
+<dd>
+Ðа, еÑÑÑ. “ÐобÑоÑовеÑÑное
иÑполÑзование” — ÑÑо
+иÑполÑзование, коÑоÑое допÑÑкаеÑÑÑ Ð±ÐµÐ·
какого Ð±Ñ Ñо ни бÑло оÑобого
+ÑазÑеÑениÑ. ÐоÑколÑÐºÑ Ð²Ð°Ð¼ не нÑжно
ÑазÑеÑение ÑазÑабоÑÑиков на Ñакое
+иÑполÑзование, Ð²Ñ Ð¼Ð¾Ð¶ÐµÑе делаÑÑ ÑÑо
незавиÑимо Ð¾Ñ Ñого, ÑÑо об ÑÑом говоÑÑÑ
+ÑазÑабоÑÑики — в лиÑензии или где-Ñо
еÑе, незавиÑимо Ð¾Ñ Ñого,
+ÑвлÑеÑÑÑ Ð»Ð¸ лиÑензией GNU GPL или лÑбаÑ
дÑÑÐ³Ð°Ñ Ð»Ð¸ÑÐµÐ½Ð·Ð¸Ñ ÑвободнÑÑ
пÑогÑамм.
+<p>
+Ðднако обÑаÑиÑе внимание, ÑÑо не
ÑÑÑеÑÑвÑÐµÑ Ð¾Ð±ÑемиÑовÑÑ
пÑинÑипов
+добÑоÑовеÑÑного иÑполÑзованиÑ; Ñо, какого
Ñода иÑполÑзование ÑÑиÑаеÑÑÑ
+“добÑоÑовеÑÑнÑм”, менÑеÑÑÑ Ð¾Ñ Ð¾Ð´Ð½Ð¾Ð¹
ÑÑÑане к дÑÑгой.
+</p></dd>
+
+<dt><a href="#TOCGPLUSGov" name="GPLUSGov">ÐÐ¾Ð¶ÐµÑ Ð»Ð¸
пÑавиÑелÑÑÑво СШРвÑпÑÑÑиÑÑ
+пÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GNU GPL?</a></dt>
+<dd>
+ÐÑли пÑогÑамма напиÑана ÑоÑÑÑдниками
ÑедеÑалÑнÑÑ
оÑганов СШРв пÑоÑеÑÑе иÑ
+ÑабоÑÑ, Ñо она наÑ
одиÑÑÑ Ð² обÑеÑÑвенном
доÑÑоÑнии, Ñо еÑÑÑ Ð¸ÑклÑÑиÑелÑное
+авÑоÑÑкое пÑаво на нее не
ÑаÑпÑоÑÑÑанÑеÑÑÑ. ÐоÑколÑÐºÑ GNU GPL оÑнована
на
+авÑоÑÑком пÑаве, ÑакÑÑ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð½ÐµÐ»ÑзÑ
вÑпÑÑÑиÑÑ Ð¿Ð¾Ð´ GNU GPL (ÑÑо, однако,
+не меÑÐ°ÐµÑ ÐµÐ¹ бÑÑÑ <a
href="/philosophy/free-sw.html">Ñвободной</a>:
+пÑогÑамма в обÑеÑÑвенном доÑÑоÑнии
Ñвободна).
+<p>
+Ðднако когда ÑедеÑалÑное гоÑÑдаÑÑÑвенное
агенÑÑÑво СШРпÑименÑÐµÑ Ð´Ð»Ñ
+ÑазÑабоÑки пÑогÑамм конÑÑакÑÑ, ÑÑо дÑÑгое
дело. Ðо конÑÑакÑÑ Ð¾Ñ Ð¿Ð¾Ð´ÑÑдÑика
+Ð¼Ð¾Ð¶ÐµÑ ÑÑебоваÑÑÑÑ Ð²ÑпÑÑк пÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GNU
GPL (Ñаким обÑазом ÑазÑабаÑÑвалÑÑ
+компилÑÑÐ¾Ñ GNU Ada). Ðли по конÑÑакÑÑ
авÑоÑÑкие пÑава могÑÑ Ð¿ÐµÑедаваÑÑÑÑ
+гоÑÑдаÑÑÑÐ²ÐµÐ½Ð½Ð¾Ð¼Ñ Ð°Ð³ÐµÐ½ÑÑÑвÑ, коÑоÑое можеÑ
заÑем вÑпÑÑÑиÑÑ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GNU
+GPL. </p></dd>
+
+<dt><a href="#TOCGPLUSGovAdd" name="GPLUSGovAdd">ÐÐ¾Ð¶ÐµÑ Ð»Ð¸
пÑавиÑелÑÑÑво СШÐ
+вÑпÑÑкаÑÑ ÑлÑÑÑÐµÐ½Ð¸Ñ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL?</a></dt>
+<dd>
+Ðа. ÐÑли ÑлÑÑÑÐµÐ½Ð¸Ñ Ð½Ð°Ð¿Ð¸ÑÐ°Ð½Ñ ÑоÑÑÑдниками
гоÑÑдаÑÑÑвеннÑÑ
ÑÑÑеждений СШРв
+пÑоÑеÑÑе иÑ
ÑабоÑÑ, Ñо ÑлÑÑÑÐµÐ½Ð¸Ñ Ð½Ð°Ñ
одÑÑÑÑ
в обÑеÑÑвенном доÑÑоÑнии. Ðднако
+на ÑлÑÑÑеннÑÑ Ð²ÐµÑÑÐ¸Ñ Ð² Ñелом вÑе Ñавно
ÑаÑпÑоÑÑÑанÑеÑÑÑ GNU GPL. ÐикакиÑ
+заÑÑÑднений ÑÑо не пÑедÑÑавлÑеÑ.
+<p>
+ÐÑли гоÑÑдаÑÑÑво пÑименÑÐµÑ Ð´Ð»Ñ ÑÑой
ÑабоÑÑ ÐºÐ¾Ð½ÑÑакÑÑ, Ñо на Ñами ÑлÑÑÑениÑ
+могÑÑ ÑаÑпÑоÑÑÑанÑÑÑÑÑ ÑÑÐ»Ð¾Ð²Ð¸Ñ GPL.
+</p></dd>
+
+<dt><a href="#TOCGPLOutput" name="GPLOutput">ÐÑÑÑ Ð»Ð¸ ÑпоÑоб
ÑаÑпÑоÑÑÑаниÑÑ GPL
+на вÑÑ
однÑе даннÑе, коÑоÑÑе лÑди полÑÑаÑÑ
пÑи полÑзовании моей пÑогÑаммой?
+ÐапÑимеÑ, еÑли Ð¼Ð¾Ñ Ð¿ÑогÑамма пÑименÑеÑÑÑ
Ð´Ð»Ñ ÑазÑабоÑки аппаÑаÑÑÑÑ, Ð¼Ð¾Ð³Ñ Ñ
+поÑÑебоваÑÑ, ÑÑÐ¾Ð±Ñ ÑÑи ÑазÑабоÑки бÑли
ÑвободнÑ?</a></dt>
+
+<dd>
+ÐообÑе ÑÑо ÑÑидиÑеÑки невозможно;
авÑоÑÑкое пÑаво не Ð´Ð°ÐµÑ Ð²Ð°Ð¼ никакой
+возможноÑÑи налагаÑÑ ÑÑÐµÐ±Ð¾Ð²Ð°Ð½Ð¸Ñ Ð½Ð°
ÑезÑлÑÑаÑÑ, коÑоÑÑе лÑди полÑÑаÑÑ Ð¸Ð·
+ÑвоиÑ
иÑÑ
однÑÑ
даннÑÑ
Ñ Ð¿Ð¾Ð¼Ð¾ÑÑÑ Ð²Ð°Ñей
пÑогÑаммÑ. ÐÑли полÑзоваÑÐµÐ»Ñ Ð¿ÑименÑеÑ
+ваÑÑ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð´Ð»Ñ Ð²Ð²Ð¾Ð´Ð° или
пÑеобÑÐ°Ð·Ð¾Ð²Ð°Ð½Ð¸Ñ ÑвоиÑ
ÑобÑÑвеннÑÑ
даннÑÑ
,
Ñо
+авÑоÑÑкое пÑаво на вÑÑ
однÑе даннÑе
пÑÐ¸Ð½Ð°Ð´Ð»ÐµÐ¶Ð¸Ñ ÐµÐ¼Ñ, а не вам. Рболее обÑем
+ÑлÑÑае, когда пÑогÑамма пÑеобÑазÑÐµÑ Ð¸ÑÑ
однÑе даннÑе в какÑÑ-Ñо дÑÑгÑÑ ÑоÑмÑ,
+авÑоÑÑко-пÑавовой ÑÑаÑÑÑ Ð²ÑÑ
однÑÑ
даннÑÑ
наÑледÑÐµÑ ÑÑаÑÑÑ Ð¸ÑÑ
однÑÑ
даннÑÑ
,
+из коÑоÑÑÑ
они бÑли полÑÑенÑ.
+<p>
+ÐÑак, единÑÑвеннÑй Ð´Ð»Ñ Ð²Ð°Ñ ÑпоÑоб полÑÑиÑÑ
возможноÑÑÑ Ð½Ð°Ð»Ð°Ð³Ð°ÑÑ ÑÑебованиÑ
+на вÑÑ
однÑе даннÑе — ÑделаÑÑ Ñак,
ÑÑÐ¾Ð±Ñ ÑÑÑеÑÑÐ²ÐµÐ½Ð½Ð°Ñ ÑаÑÑÑ
+вÑÑ
однÑÑ
даннÑÑ
копиÑовалаÑÑ (более или
менее) из ÑекÑÑа ваÑей
+пÑогÑаммÑ. ÐапÑимеÑ, на ÑаÑÑÑ Ð²ÑÑ
однÑÑ
Ñайлов пÑогÑÐ°Ð¼Ð¼Ñ Bison (Ñм. вÑÑе)
+ÑаÑпÑоÑÑÑанÑлаÑÑ Ð±Ñ GPL, еÑли Ð±Ñ Ð¼Ñ Ð½Ðµ
Ñделали оÑобого иÑклÑÑÐµÐ½Ð¸Ñ Ð´Ð»Ñ ÑÑого
+ÑлÑÑаÑ.</p>
+<p>
+ÐÑ Ð¼Ð¾Ð³Ð»Ð¸ Ð±Ñ Ð·Ð°ÑÑавиÑÑ Ð¿ÑогÑаммÑ
иÑкÑÑÑÑвенно вÑÑавлÑÑÑ Ð¾Ð¿ÑеделеннÑй ÑекÑÑ
в
+Ñвои вÑÑ
однÑе даннÑе, даже еÑли Ð´Ð»Ñ ÑÑого
Ð½ÐµÑ ÑеÑ
ниÑеÑкой необÑ
одимоÑÑи. Ðо
+еÑли ÑÑÐ¾Ñ Ð²ÑÑавлÑемÑй ÑекÑÑ Ð½Ðµ ÑлÑжиÑ
никакой пÑакÑиÑеÑкой Ñели, Ñо
+полÑзоваÑÐµÐ»Ñ Ð¼Ð¾Ð³ Ð±Ñ Ð¿ÑоÑÑо ÑдалÑÑÑ ÑÑоÑ
ÑекÑÑ Ð¸Ð· вÑÑ
однÑÑ
даннÑÑ
и
+полÑзоваÑÑÑÑ ÑолÑко Ñем, ÑÑо оÑÑанеÑÑÑ.
Тогда ÐµÐ¼Ñ Ð½Ðµ пÑиÑлоÑÑ Ð±Ñ Ð¿Ð¾Ð´ÑинÑÑÑÑÑ
+ÑÑловиÑм ÑаÑпÑоÑÑÑÐ°Ð½ÐµÐ½Ð¸Ñ Ð²ÑÑавлÑемого
ÑекÑÑа.
+</p></dd>
+
+<dt><a href="#TOCWhatCaseIsOutputGPL" name="WhatCaseIsOutputGPL">РкакиÑ
ÑлÑÑаÑÑ
+GPL ÑаÑпÑоÑÑÑанÑеÑÑÑ Ð¸ на ÑезÑлÑÑÐ°Ñ ÑабоÑÑ
пÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL?</a></dt>
+
+<dd>
+ТолÑко когда пÑогÑамма копиÑÑÐµÑ ÑаÑÑÑ
Ñамой ÑÐµÐ±Ñ Ð² вÑÑ
однÑе даннÑе.
+<p></p></dd>
+
+<dt><a href="#TOCGPLModuleLicense" name="GPLModuleLicense">ÐÑли Ñ
добавлÑÑ
+модÑÐ»Ñ Ðº пÑогÑамме под GPL, ÑÑебÑеÑÑÑ Ð»Ð¸ оÑ
Ð¼ÐµÐ½Ñ Ð¸ÑполÑзование GPL в
+каÑеÑÑве лиÑензии Ð´Ð»Ñ Ð¼Ð¾ÐµÐ³Ð¾ модÑлÑ?</a></dt>
+
+<dd>
+Ð GPL Ñказано, ÑÑо комбиниÑованнаÑ
пÑогÑамма в Ñелом должна вÑпÑÑкаÑÑÑÑ Ð¿Ð¾Ð´
+GPL. Так ÑÑо Ð²Ð°Ñ Ð¼Ð¾Ð´ÑÐ»Ñ Ð´Ð¾Ð»Ð¶ÐµÐ½ бÑÑÑ Ð´Ð¾ÑÑÑпен
Ð´Ð»Ñ Ð¸ÑполÑÐ·Ð¾Ð²Ð°Ð½Ð¸Ñ Ð½Ð° ÑÑловиÑÑ
+GPL.
+<p>
+Ðо Ð²Ñ Ð¼Ð¾Ð¶ÐµÑе даÑÑ Ð´Ð¾Ð¿Ð¾Ð»Ð½Ð¸ÑелÑное
ÑазÑеÑение Ð´Ð»Ñ Ð¿Ð¾Ð»ÑÐ·Ð¾Ð²Ð°Ð½Ð¸Ñ Ð²Ð°Ñим
+ÑекÑÑом. ÐÑ Ð¼Ð¾Ð¶ÐµÑе, еÑли желаеÑе, вÑпÑÑÑиÑÑ
ÑÐ²Ð¾Ñ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾ лиÑензии,
+коÑоÑÐ°Ñ Ð±Ð¾Ð»ÐµÐµ либеÑалÑна, Ñем GPL, но
ÑовмеÑÑима Ñ GPL. Ðа <a
+href="/licenses/license-list.html">ÑÑÑаниÑе Ñо ÑпиÑком
лиÑензий</a>
+пÑиводиÑÑÑ Ð½ÐµÐ¿Ð¾Ð»Ð½Ñй ÑпиÑок ÑовмеÑÑимÑÑ
Ñ
GPL лиÑензий.
+</p></dd>
+
+<dt><a href="#TOCIfLibraryIsGPL" name="IfLibraryIsGPL">ÐÑли
библиоÑека
+вÑпÑÑкаеÑÑÑ Ð½Ð° ÑÑловиÑÑ
GPL (не LGPL), знаÑиÑ
ли ÑÑо, ÑÑо лÑÐ±Ð°Ñ Ð¿ÑогÑамма,
+коÑоÑÐ°Ñ ÐµÑ Ð¿Ð¾Ð»ÑзÑеÑÑÑ, должна вÑпÑÑкаÑÑÑÑ
на ÑÑловиÑÑ
GPL?</a></dt>
+
+<dd>
+Ðа, поÑÐ¾Ð¼Ñ ÑÑо пÑогÑамма, коÑоÑÐ°Ñ Ð½Ð° Ñамом
деле вÑполнÑеÑÑÑ, вклÑÑÐ°ÐµÑ Ð² ÑебÑ
+ÑÑÑ Ð±Ð¸Ð±Ð»Ð¸Ð¾ÑекÑ.
+<p></p></dd>
+
+<dt><a href="#TOCIfInterpreterIsGPL" name="IfInterpreterIsGPL">ÐÑли
+инÑеÑпÑеÑаÑÐ¾Ñ ÑзÑка пÑогÑаммиÑованиÑ
вÑпÑÑкаеÑÑÑ Ð¿Ð¾Ð´ GPL, знаÑÐ¸Ñ Ð»Ð¸ ÑÑо, ÑÑо
+пÑогÑÐ°Ð¼Ð¼Ñ Ð´Ð»Ñ Ð½ÐµÐ³Ð¾ Ð´Ð¾Ð»Ð¶Ð½Ñ Ð²ÑпÑÑкаÑÑÑÑ Ð½Ð°
ÑÑловиÑÑ
ÑовмеÑÑимÑÑ
Ñ GPL
+лиÑензий?</a></dt>
+
+<dd>
+ÐÑли инÑеÑпÑеÑаÑÐ¾Ñ ÑолÑко инÑеÑпÑеÑиÑÑеÑ
ÑзÑк, оÑÐ²ÐµÑ Ð¾ÑÑиÑаÑелен. ÐлÑ
+инÑеÑпÑеÑаÑоÑа вÑполнÑемаÑ
пÑогÑамма — ÑÑо ÑолÑко даннÑе; Ñакие
+лиÑензии ÑвободнÑÑ
пÑогÑамм, как GPL,
оÑнованнÑе на авÑоÑÑком пÑаве, не
+могÑÑ Ð¾Ð³ÑаниÑиваÑÑ Ñого, какие даннÑе вÑ
иÑполÑзÑеÑе Ñ Ð¸Ð½ÑеÑпÑеÑаÑоÑом. ÐÑ
+можеÑе вÑполнÑÑÑ ÐµÐ³Ð¾ Ñ Ð»ÑбÑми даннÑми
(инÑеÑпÑеÑиÑÑемой пÑогÑаммой), как вам
+Ñгодно, Ð½ÐµÑ Ð½Ð¸ÐºÐ°ÐºÐ¸Ñ
ÑÑебований
оÑноÑиÑелÑно лиÑензиÑÐ¾Ð²Ð°Ð½Ð¸Ñ ÑÑиÑ
даннÑÑ
комÑ
+Ð±Ñ Ñо ни бÑло.
+<p>Ðднако когда инÑеÑпÑеÑаÑÐ¾Ñ ÑаÑÑиÑÑеÑÑÑ
Ð´Ð»Ñ Ñого, ÑÑÐ¾Ð±Ñ Ð¾Ð±ÐµÑпеÑиÑÑ
+“пÑивÑзки” к дÑÑгим ÑÑедÑÑвам (ÑаÑÑо,
но не вÑегда —
+к библиоÑекам), инÑеÑпÑеÑиÑÑемаÑ
пÑогÑамма ÑакÑиÑеÑки компонÑеÑÑÑ Ñо
+ÑÑедÑÑвами, коÑоÑÑми она полÑзÑеÑÑÑ Ñ
помоÑÑÑ ÑÑиÑ
пÑивÑзок. Так ÑÑо еÑли
+ÑÑи ÑÑедÑÑва вÑпÑÑкаÑÑÑÑ Ð¿Ð¾Ð´ GPL, Ñо
инÑеÑпÑеÑиÑÑÐµÐ¼Ð°Ñ Ð¿ÑогÑамма должна
+вÑпÑÑкаÑÑÑÑ ÑовмеÑÑимÑм Ñ GPL обÑазом. JNI (Java
Native
+Interface) — пÑÐ¸Ð¼ÐµÑ Ð¼ÐµÑ
анизма Ñакой
пÑивÑзки; библиоÑеки, к
+коÑоÑÑм пÑедоÑÑавлÑеÑÑÑ Ð´Ð¾ÑÑÑп Ñаким
обÑазом, компонÑÑÑÑÑ Ð´Ð¸Ð½Ð°Ð¼Ð¸ÑеÑки Ñ
+пÑогÑаммами на Java, коÑоÑÑе вÑзÑваÑÑ Ð¸Ñ
. ÐÑи
библиоÑеки компонÑÑÑÑÑ Ñакже Ñ
+инÑеÑпÑеÑаÑоÑом. ÐÑли инÑеÑпÑеÑаÑоÑ
ÑÑаÑиÑеÑки ÑвÑзÑваеÑÑÑ Ñ ÑÑими
+библиоÑеками или еÑли он ÑазÑабоÑан Ñак,
ÑÑÐ¾Ð±Ñ <a
+href="#GPLPluginsInNF">динамиÑеÑки компоноваÑÑÑÑ Ñ
ÑÑими конкÑеÑнÑми
+библиоÑеками</a>, Ñо он Ñоже должен
вÑпÑÑкаÑÑÑÑ ÑовмеÑÑимÑм Ñ GPL обÑазом.</p>
+<p>
+ÐÑÑгой ÑÑ
однÑй и оÑÐµÐ½Ñ ÑаÑпÑоÑÑÑаненнÑй
ÑлÑÑай — поÑÑавка Ñ
+инÑеÑпÑеÑаÑоÑом библиоÑек, коÑоÑÑе Ñами
инÑеÑпÑеÑиÑÑÑÑÑÑ. ÐапÑимеÑ, Perl
+поÑÑавлÑеÑÑÑ Ñ Ð±Ð¾Ð»ÑÑим набоÑом модÑлей на
ÑзÑке Perl, а ÑеализаÑÐ¸Ñ Java
+поÑÑавлÑеÑÑÑ Ñ Ð±Ð¾Ð»ÑÑим набоÑом клаÑÑов
ÑзÑка Java. ÐÑи библиоÑеки и
+пÑогÑаммÑ, коÑоÑÑе иÑ
вÑзÑваÑÑ, вÑегда
динамиÑеÑки компонÑÑÑÑÑ Ð´ÑÑг Ñ
+дÑÑгом.</p>
+<p>
+Ðак ÑледÑÑвие, еÑли Ð²Ñ ÑеÑили полÑзоваÑÑÑÑ
модÑлÑми Perl или клаÑÑами Java
+под GPL в Ñвоей пÑогÑамме, Ñо Ð²Ñ Ð´Ð¾Ð»Ð¶Ð½Ñ
вÑпÑÑкаÑÑ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ ÑовмеÑÑимÑм Ñ
+GPL обÑазом незавиÑимо Ð¾Ñ Ð»Ð¸Ñензии,
пÑименÑемой Ð´Ð»Ñ Perl или инÑеÑпÑеÑаÑоÑа
+Java, на коÑоÑом бÑÐ´ÐµÑ Ð²ÑполнÑÑÑÑÑ
комбиниÑÐ¾Ð²Ð°Ð½Ð½Ð°Ñ Ð¿ÑогÑамма на ÑзÑке Perl
+или Java.
+</p></dd>
+
+<dt><a href="#TOCWindowsRuntimeAndGPL" name="WindowsRuntimeAndGPL">Я пиÑÑ
+пÑиложение Ð´Ð»Ñ Windows на Microsoft Visual C++ (или Visual
Basic) и бÑдÑ
+вÑпÑÑкаÑÑ ÐµÐ³Ð¾ под GPL. ÐопÑÑÐºÐ°ÐµÑ Ð»Ð¸ GPL
динамиÑеÑкое ÑвÑзÑвание моей
+пÑогÑÐ°Ð¼Ð¼Ñ Ñ Ð±Ð¸Ð±Ð»Ð¸Ð¾Ñеками вÑемени
иÑÐ¿Ð¾Ð»Ð½ÐµÐ½Ð¸Ñ Visual C++ (или Visual
+Basic)?</a></dt>
+
+<dd>
+GPL допÑÑÐºÐ°ÐµÑ ÑÑо, поÑÐ¾Ð¼Ñ ÑÑо библиоÑека
вÑемени иÑполнениÑ, как пÑавило,
+ÑопÑÐ¾Ð²Ð¾Ð¶Ð´Ð°ÐµÑ ÐºÐ¾Ð¼Ð¿Ð¸Ð»ÑÑÐ¾Ñ Ð¸Ð»Ð¸
инÑеÑпÑеÑаÑоÑ, коÑоÑÑм Ð²Ñ Ð¿Ð¾Ð»ÑзÑеÑеÑÑ. Так
ÑÑо
+она Ð¿Ð¾Ð¿Ð°Ð´Ð°ÐµÑ Ð¿Ð¾Ð´ иÑклÑÑение в Ñазделе 3
GPL.
+<p>
+ÐÑо не знаÑиÑ, ÑÑо пиÑаÑÑ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ñак,
ÑÑÐ¾Ð±Ñ Ð¾Ð½Ð° ÑабоÑала ÑолÑко под
+Windows — неплоÑ
Ð°Ñ Ð¸Ð´ÐµÑ. ÐÑо пÑÐ¸Ð²Ð¾Ð´Ð¸Ñ Ðº
пÑогÑамме, коÑоÑаÑ
+Ñвободна, но “<a href="/philosophy/java-trap.html">ÑидиÑ
в
+западне</a>” (в данном ÑлÑÑае в западне
Windows, а не Java, но
+ÑезÑлÑÑÐ°Ñ — ÑÐ¾Ñ Ð¶Ðµ). (ÐÑÑоÑиÑеÑкое
замеÑание: на декабÑÑ
+2006 года Sun наÑ
одиÑÑÑ Ð² пÑоÑеÑÑе <a
+href="http://www.fsf.org/news/fsf-welcomes-gpl-java.html";>пеÑевÑпÑÑка
Ñвоей
+плаÑÑоÑÐ¼Ñ Java под GNU GPL</a>.)
+</p></dd>
+
+<dt><a href="#TOCOrigBSD" name="OrigBSD">ÐоÑемÑ
пеÑвонаÑалÑÐ½Ð°Ñ Ð»Ð¸ÑÐµÐ½Ð·Ð¸Ñ BSD
+неÑовмеÑÑима Ñ GPL?</a></dt>
+
+<dd>
+ÐоÑÐ¾Ð¼Ñ ÑÑо она Ð½Ð°Ð»Ð°Ð³Ð°ÐµÑ Ð½ÐµÐºÐ¾Ðµ ÑÑебование,
коÑоÑого Ð½ÐµÑ Ð² GPL; а именно,
+ÑÑебование на ÑекламнÑе маÑеÑÐ¸Ð°Ð»Ñ Ð´Ð»Ñ
пÑогÑаммÑ. Ð GPL Ñказано:
+<pre>
+ You may not impose any further restrictions on the recipients' exercise
+ of the rights granted herein.
+
+ ÐÑ Ð½Ðµ можеÑе налагаÑÑ Ð½Ð¸ÐºÐ°ÐºÐ¸Ñ
дополниÑелÑнÑÑ
огÑаниÑений
+ на оÑÑÑеÑÑвление полÑÑаÑелÑми пÑав,
пÑедоÑÑавлÑемÑÑ
данной лиÑензией.
+</pre>
+<p>
+ÐÑÐ½ÐºÑ Ð¾ Ñекламе как Ñаз и ÑÑÑанавливаеÑ
Ñакое дополниÑелÑное огÑаниÑение, и
+вÑледÑÑвие ÑÑого неÑовмеÑÑим Ñ GPL.</p>
+<p>
+РпеÑеÑмоÑÑенной лиÑензии BSD пÑнкÑа о
Ñекламе неÑ, ÑÑо ÑÑÑÑанÑÐµÑ Ð¿ÑоблемÑ.
+</p></dd>
+
+<dt><a href="#TOCGPLAndPlugins" name="GPLAndPlugins">ÐÑли
пÑогÑамма, вÑпÑÑеннаÑ
+под GPL, полÑзÑеÑÑÑ Ð²Ð½ÐµÑними модÑлÑми,
ÐºÐ°ÐºÐ¾Ð²Ñ ÑÑÐµÐ±Ð¾Ð²Ð°Ð½Ð¸Ñ Ðº лиÑензиÑм
+модÑлÑ?</a></dt>
+
+<dd>
+ÐÑо завиÑÐ¸Ñ Ð¾Ñ Ñого, как пÑогÑамма
задейÑÑвÑÐµÑ Ñвои внеÑние модÑли. ÐÑли
+пÑогÑамма полÑзÑеÑÑÑ Ð´Ð»Ñ ÑÑого вÑзовами
<em>fork</em> или <em>exec</em>, Ñо
+модÑли — ÑÑо оÑделÑнÑе пÑогÑаммÑ, Ñак
ÑÑо лиÑÐµÐ½Ð·Ð¸Ñ Ð³Ð»Ð°Ð²Ð½Ð¾Ð¹
+пÑогÑÐ°Ð¼Ð¼Ñ Ð½Ðµ пÑедÑÑвлÑÐµÑ Ðº ним никакиÑ
ÑÑебований.
+<p>
+ÐÑли пÑогÑамма динамиÑеÑки компонÑеÑÑÑ Ñ
модÑлÑми и они вÑзÑваÑÑ ÑÑнкÑии
+дÑÑг из дÑÑга и ÑазделÑÑÑ Ð¾Ð±Ñие ÑÑÑÑкÑÑÑÑ
даннÑÑ
, Ð¼Ñ ÑбежденÑ, ÑÑо они
+ÑоÑмиÑÑÑÑ ÐµÐ´Ð¸Ð½ÑÑ Ð¿ÑогÑаммÑ, коÑоÑаÑ
должна ÑаÑÑмаÑÑиваÑÑÑÑ ÐºÐ°Ðº ÑаÑÑиÑение и
+главной пÑогÑаммÑ, и модÑлей. ÐÑо знаÑиÑ,
ÑÑо модÑли Ð´Ð¾Ð»Ð¶Ð½Ñ Ð²ÑпÑÑкаÑÑÑÑ Ð¿Ð¾Ð´
+GPL или ÑовмеÑÑимой Ñ Ð½ÐµÐ¹ лиÑензией
ÑвободнÑÑ
пÑогÑамм и ÑÑо ÑÑÐ»Ð¾Ð²Ð¸Ñ GPL
+Ð´Ð¾Ð»Ð¶Ð½Ñ ÑоблÑдаÑÑÑÑ Ð¿Ñи ÑаÑпÑоÑÑÑанении
ÑÑиÑ
модÑлей.</p>
+<p>
+Ðак пÑеделÑнÑй Ð¼Ð¾Ð¶ÐµÑ ÑаÑÑмаÑÑиваÑÑÑÑ
ÑлÑÑай, когда пÑогÑамма динамиÑеÑки
+компонÑеÑÑÑ Ñ Ð¼Ð¾Ð´ÑлÑми, но ÑообÑение междÑ
ними огÑаниÑиваеÑÑÑ Ð²Ñзовом
+“главной” ÑÑнкÑии модÑÐ»Ñ Ñ
некоÑоÑÑми аÑгÑменÑами и ожиданием,
+когда пÑÐ¾Ð¸Ð·Ð¾Ð¹Ð´ÐµÑ Ð²Ð¾Ð·Ð²ÑÐ°Ñ Ð¸Ð· ÑÑнкÑии.
+</p></dd>
+
+<dt><a href="#TOCGPLPluginsInNF" name="GPLPluginsInNF">ÐÐ¾Ð³Ñ Ñ
пÑименÑÑÑ GPL,
+когда пиÑÑ Ð²Ð½ÐµÑний модÑÐ»Ñ Ðº неÑвободной
пÑогÑамме?</a></dt>
+
+<dd>
+ÐÑли пÑогÑамма полÑзÑеÑÑÑ Ð²Ñзовами
<em>fork</em> и <em>exec</em> Ð´Ð»Ñ Ñого,
+ÑÑÐ¾Ð±Ñ Ð·Ð°Ð´ÐµÐ¹ÑÑвоваÑÑ Ð¼Ð¾Ð´ÑлÑ, Ñо модÑли
ÑвлÑÑÑÑÑ Ð¾ÑделÑнÑми пÑогÑаммами, Ñак
+ÑÑо лиÑÐµÐ½Ð·Ð¸Ñ Ð³Ð»Ð°Ð²Ð½Ð¾Ð¹ пÑогÑÐ°Ð¼Ð¼Ñ Ð½Ðµ
пÑедÑÑвлÑÐµÑ Ðº ним никакиÑ
ÑÑебований. Так
+ÑÑо Ð²Ñ Ð¼Ð¾Ð¶ÐµÑе пÑименÑÑÑ GPL Ð´Ð»Ñ Ð¼Ð¾Ð´ÑÐ»Ñ Ð¸
никакиÑ
оÑобÑÑ
ÑÑебований неÑ.
+<p>
+ÐÑли пÑогÑамма динамиÑеÑки компонÑеÑÑÑ Ñ
модÑлÑми и они вÑзÑваÑÑ ÑÑнкÑии
+дÑÑг из дÑÑга и ÑазделÑÑÑ Ð¾Ð±Ñие ÑÑÑÑкÑÑÑÑ
даннÑÑ
, Ð¼Ñ ÑбежденÑ, ÑÑо они
+ÑоÑмиÑÑÑÑ ÐµÐ´Ð¸Ð½ÑÑ Ð¿ÑогÑаммÑ, коÑоÑаÑ
должна ÑаÑÑмаÑÑиваÑÑÑÑ ÐºÐ°Ðº ÑаÑÑиÑение и
+главной пÑогÑаммÑ, и модÑлей. ÐÑо знаÑиÑ,
ÑÑо обÑединение модÑÐ»Ñ Ð¿Ð¾Ð´ GPL Ñ
+неÑвободной пÑогÑаммой наÑÑÑало Ð±Ñ GPL.
Ðднако Ð²Ñ Ð¼Ð¾Ð¶ÐµÑе ÑеÑиÑÑ ÑÑÑ
+ÑÑидиÑеÑкÑÑ Ð¿ÑоблемÑ, добавив иÑклÑÑение
к лиÑензии Ñвоего модÑлÑ, в коÑоÑом
+даеÑÑÑ ÑазÑеÑение компоноваÑÑ ÐµÐ³Ð¾ Ñ
неÑвободной главной пÑогÑаммой.</p>
+<p>
+См. Ñакже оÑÐ²ÐµÑ Ð½Ð° вопÑÐ¾Ñ <a href="#FSWithNFLibs">о
напиÑании ÑвободнÑÑ
+пÑогÑамм Ñ Ð¸ÑполÑзованием неÑвободнÑÑ
библиоÑек</a>.
+</p></dd>
+
+<dt><a href="#TOCNFUseGPLPlugins" name="NFUseGPLPlugins">ÐÐ¾Ð³Ñ Ñ
вÑпÑÑÑиÑÑ
+неÑвободнÑÑ Ð¿ÑогÑаммÑ, ÑоÑÑавленнÑÑ Ñак,
ÑÑÐ¾Ð±Ñ Ð¿Ð¾Ð´Ð³ÑÑжаÑÑ Ð²Ð½ÐµÑний модÑÐ»Ñ Ð¿Ð¾Ð´
+GPL?</a></dt>
+
+<dd>
+ÐÑо завиÑÐ¸Ñ Ð¾Ñ Ñого, как пÑогÑамма
задейÑÑвÑÐµÑ Ñвои внеÑние модÑли. ÐÑли
+пÑогÑамма иÑполÑзÑÐµÑ Ð²ÑÐ·Ð¾Ð²Ñ <em>fork</em> и
<em>exec</em> Ð´Ð»Ñ Ð·Ð°Ð³ÑÑзки
+модÑлей, Ñо ÑÑи модÑли ÑвлÑÑÑÑÑ Ð¾ÑделÑнÑми
пÑогÑаммами, Ñак ÑÑо лиÑензиÑ
+модÑÐ»Ñ Ð½Ðµ пÑедÑÑвлÑÐµÑ ÑÑебований к
главной пÑогÑамме.
+<p>
+ÐÑли пÑогÑамма динамиÑеÑки компонÑеÑÑÑ Ñ
модÑлÑми и они вÑзÑваÑÑ ÑÑнкÑии
+дÑÑг из дÑÑга и ÑазделÑÑÑ Ð¾Ð±Ñие ÑÑÑÑкÑÑÑÑ
даннÑÑ
, Ð¼Ñ ÑбежденÑ, ÑÑо они
+ÑоÑмиÑÑÑÑ ÐµÐ´Ð¸Ð½ÑÑ Ð¿ÑогÑаммÑ, коÑоÑаÑ
должна ÑаÑÑмаÑÑиваÑÑÑÑ ÐºÐ°Ðº ÑаÑÑиÑение и
+главной пÑогÑаммÑ, и модÑлей. ЧÑобÑ
полÑзоваÑÑÑÑ Ð¼Ð¾Ð´ÑлÑми под GPL, главнаÑ
+пÑогÑамма должна вÑпÑÑкаÑÑÑÑ Ð¿Ð¾Ð´ GPL или
ÑовмеÑÑимой Ñ Ð½ÐµÐ¹ лиÑензией
+ÑвободнÑÑ
пÑогÑамм и ÑÑÐ»Ð¾Ð²Ð¸Ñ GPL должнÑ
ÑоблÑдаÑÑÑÑ, когда Ð³Ð»Ð°Ð²Ð½Ð°Ñ Ð¿ÑогÑамма
+ÑаÑпÑоÑÑÑанÑеÑÑÑ Ð´Ð»Ñ Ð¸ÑполÑÐ·Ð¾Ð²Ð°Ð½Ð¸Ñ Ñ
ÑÑими модÑлÑми.</p>
+<p>
+Ðак пÑеделÑнÑй Ð¼Ð¾Ð¶ÐµÑ ÑаÑÑмаÑÑиваÑÑÑÑ
ÑлÑÑай, когда пÑогÑамма динамиÑеÑки
+компонÑеÑÑÑ Ñ Ð¼Ð¾Ð´ÑлÑми, но ÑообÑение междÑ
ними огÑаниÑиваеÑÑÑ Ð²Ñзовом
+“главной” ÑÑнкÑии модÑÐ»Ñ Ñ
некоÑоÑÑми аÑгÑменÑами и ожиданием,
+когда пÑÐ¾Ð¸Ð·Ð¾Ð¹Ð´ÐµÑ Ð²Ð¾Ð·Ð²ÑÐ°Ñ Ð¸Ð· ÑÑнкÑии.</p>
+<p>
+См. Ñакже оÑÐ²ÐµÑ Ð½Ð° вопÑÐ¾Ñ <a href="#FSWithNFLibs">о
напиÑании ÑвободнÑÑ
+пÑогÑамм Ñ Ð¸ÑполÑзованием неÑвободнÑÑ
библиоÑек</a>.
+</p></dd>
+
+<dt><a href="#TOCLinkingWithGPL" name="LinkingWithGPL">У Ð²Ð°Ñ ÐµÑÑÑ
пÑогÑамма под
+GPL, коÑоÑÑÑ Ð¼Ð½Ðµ Ñ
оÑелоÑÑ Ð±Ñ ÑкомпоноваÑÑ Ñ
моими пÑогÑаммами, ÑÑобÑ
+полÑÑиÑÑ Ð½ÐµÑвободнÑÑ Ð¿ÑогÑаммÑ. ÐзнаÑаеÑ
ли ÑÐ°ÐºÑ ÐºÐ¾Ð¼Ð¿Ð¾Ð½Ð¾Ð²ÐºÐ¸ Ñ Ð²Ð°Ñей
+пÑогÑаммой, ÑÑо Ð¾Ñ Ð¼ÐµÐ½Ñ ÑÑебÑеÑÑÑ
вÑпÑÑкаÑÑ ÑÐ²Ð¾Ñ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL?</a></dt>
+
+<dd>
+Ðа.
+<p></p></dd>
+
+<dt><a href="#TOCSwitchToLGPL" name="SwitchToLGPL">Ð Ñаком ÑлÑÑае,
еÑÑÑ Ð»Ð¸ Ñ
+Ð¼ÐµÐ½Ñ Ñ
оÑÑ ÐºÐ°ÐºÐ°Ñ-Ñо надежда на полÑÑение оÑ
Ð²Ð°Ñ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð½Ð° ÑÑловиÑÑ
ÐенÑÑей
+GPL?</a></dt>
+
+<dd>
+ÐопÑоÑиÑÑ Ð¼Ð¾Ð¶Ð½Ð¾, но болÑÑинÑÑво авÑоÑов
оÑвеÑÑÑ ÑвеÑдÑм оÑказом. ÐÐ´ÐµÑ GPL
+заклÑÑаеÑÑÑ Ð² Ñом, ÑÑо еÑли Ð²Ñ Ñ
оÑиÑе
вклÑÑаÑÑ Ð½Ð°Ñ Ð¸ÑÑ
однÑй ÑекÑÑ Ð² ÑвоÑ
+пÑогÑаммÑ, Ñо ваÑа пÑогÑамма Ñоже должна
бÑÑÑ Ñвободной. ÐÑедполагаеÑÑÑ, ÑÑо
+ÑÑо Ð¾ÐºÐ°Ð¶ÐµÑ Ð´Ð°Ð²Ð»ÐµÐ½Ð¸Ðµ на ваÑ, ÑÑÐ¾Ð±Ñ Ð²Ñ
вÑпÑÑкали ÑÐ²Ð¾Ñ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ñаким обÑазом,
+ÑÑÐ¾Ð±Ñ Ð¾Ð½Ð° воÑла в наÑе ÑообÑеÑÑво.
+<p>
+У Ð²Ð°Ñ Ð²Ñегда еÑÑÑ Ð·Ð°ÐºÐ¾Ð½Ð½Ð°Ñ Ð°Ð»ÑÑеÑнаÑива:
не полÑзоваÑÑÑÑ Ð½Ð°Ñим иÑÑ
однÑм
+ÑекÑÑом.
+</p></dd>
+
+<dt><a href="#TOCLinkingOverControlledInterface"
+name="LinkingOverControlledInterface">Ðак мне позволиÑÑ
компоноваÑÑ
+неÑвободнÑе модÑли Ñо Ñвоей библиоÑекой
под GPL ÑолÑко по опÑеделенномÑ
+пÑоÑоколÑ?</a></dt>
+
+<dd>
+ÐобавÑÑе ÑледÑÑÑий ÑекÑÑ Ðº замеÑÐ°Ð½Ð¸Ñ Ð¾
лиÑензии в каждÑй Ñайл пакеÑа в конÑе
+ÑекÑÑа, в коÑоÑом говоÑиÑÑÑ Ð¾ Ñом, ÑÑо Ñайл
ÑаÑпÑоÑÑÑанÑеÑÑÑ Ð½Ð° ÑÑловиÑÑ
GNU
+GPL:
+<pre>
+
+Ð ÑезÑлÑÑаÑе ÐинамиÑеÑкой или ÑÑаÑиÑеÑкой
компоновки ÐÐÐ Ñ Ð´ÑÑгими
+модÑлÑми полÑÑаеÑÑÑ Ð¿Ñоизведение,
пÑоизводное Ð¾Ñ ÐÐÐ. Таким обÑазом,
+ÑÑÐ»Ð¾Ð²Ð¸Ñ Ð¸ ÑÑÐµÐ±Ð¾Ð²Ð°Ð½Ð¸Ñ Ð¡ÑандаÑÑной
обÑеÑÑвенной лиÑензии GNU
+ÑаÑпÑоÑÑÑанÑÑÑÑÑ Ð½Ð° комбинаÑÐ¸Ñ Ð² Ñелом.
+Рдополнение, как оÑобое иÑклÑÑение,
пÑавообладаÑели ÐÐРдаÑÑ Ð²Ð°Ð¼
+ÑазÑеÑение комбиниÑоваÑÑ ÐÐÐ Ñо
ÑвободнÑми пÑогÑаммами или библиоÑеками,
+вÑпÑÑкаемÑми под GNU LGPL, и Ñ Ð½ÐµÐ·Ð°Ð²Ð¸ÑимÑми
модÑлÑми, коÑоÑÑе ÑообÑаÑÑÑÑ
+Ñ ÐÐРиÑклÑÑиÑелÑно по пÑоÑÐ¾ÐºÐ¾Ð»Ñ ÐÐÐÐÐÐ.
ÐÑ Ð¼Ð¾Ð¶ÐµÑе копиÑоваÑÑ
+и ÑаÑпÑоÑÑÑанÑÑÑ ÑакÑÑ ÑиÑÑемÑ, ÑледÑÑ
ÑÑебованиÑм GNU GPL в оÑноÑении ÐÐÐ
+и ÑÑебованиÑм лиÑензий дÑÑгиÑ
пÑогÑамм,
коÑоÑÑе иÑполÑзÑÑÑÑÑ, пÑи ÑÑловии,
+ÑÑо Ð²Ñ Ð¿ÑедоÑÑавлÑеÑе иÑÑ
однÑй ÑекÑÑ ÑÑиÑ
дÑÑгиÑ
пÑогÑамм, когда и как
+GNU GPL ÑÑебÑÐµÑ ÑаÑпÑоÑÑÑанÑÑÑ Ð¸ÑÑ
однÑй
ÑекÑÑ.
+
+ÐбÑаÑиÑе внимание, ÑÑо Ñе, кÑо делаеÑ
измененнÑÑ Ð²ÐµÑÑÐ¸Ñ ÐÐÐ, не обÑзанÑ
+пÑедоÑÑавлÑÑÑ ÑÑо оÑобое иÑклÑÑение длÑ
ÑвоиÑ
измененнÑÑ
веÑÑий; ÑÑо ÑеÑаÑÑ
+они. СÑандаÑÑÐ½Ð°Ñ Ð¾Ð±ÑеÑÑÐ²ÐµÐ½Ð½Ð°Ñ Ð»Ð¸ÑÐµÐ½Ð·Ð¸Ñ GNU
Ð´Ð°ÐµÑ ÑазÑеÑение вÑпÑÑкаÑÑ
+измененнÑÑ Ð²ÐµÑÑÐ¸Ñ Ð±ÐµÐ· ÑÑого иÑклÑÑениÑ;
ÑÑо иÑклÑÑение Ñакже ÑоздаеÑ
+возможноÑÑÑ Ð²ÑпÑÑка измененной веÑÑии, в
коÑоÑой ÑÑо иÑклÑÑение
+пÑодлеваеÑÑÑ.
+
+</pre>
+<p>
+Ðо Ð·Ð°ÐºÐ¾Ð½Ñ ÑолÑко пÑавообладаÑели
пÑогÑÐ°Ð¼Ð¼Ñ Ð¼Ð¾Ð³ÑÑ ÑанкÑиониÑоваÑÑ ÑÑо
+иÑклÑÑение. ÐÑли Ð²Ñ Ð½Ð°Ð¿Ð¸Ñали вÑÑ Ð¿ÑогÑаммÑ
Ñами, Ñо (пÑедполагаÑ, ÑÑо ваÑ
+ÑабоÑодаÑÐµÐ»Ñ Ð¸Ð»Ð¸ ÑÑебное заведение не
пÑеÑендÑÐµÑ Ð½Ð° авÑоÑÑкие пÑава) вÑ
+ÑвлÑеÑеÑÑ Ð¿ÑавообладаÑелем — Ñак ÑÑо
Ð²Ñ Ð¼Ð¾Ð¶ÐµÑе ÑанкÑиониÑоваÑÑ
+иÑклÑÑение. Ðо еÑли Ð²Ñ Ñ
оÑиÑе
воÑполÑзоваÑÑÑÑ ÑаÑÑÑми дÑÑгиÑ
пÑогÑамм
под
+GPL, напиÑаннÑÑ
дÑÑгими авÑоÑами, в Ñвоей
пÑогÑамме, Ð²Ñ Ð½Ðµ можеÑе
+ÑанкÑиониÑоваÑÑ ÑÑо иÑклÑÑение за ниÑ
. ÐÑ
Ð´Ð¾Ð»Ð¶Ð½Ñ Ð¿Ð¾Ð»ÑÑиÑÑ ÑоглаÑие оÑ
+пÑавообладаÑелей ÑÑиÑ
пÑогÑамм.
+</p><p></p></dd>
+
+<dt><a href="#TOCManyDifferentLicenses" name="ManyDifferentLicenses">Ðной
+напиÑано пÑиложение, коÑоÑое компонÑеÑÑÑ
Ñ Ð±Ð¾Ð»ÑÑим ÑиÑлом ÑазнÑÑ
+ÑоÑÑавлÑÑÑиÑ
Ñ ÑазнÑми лиÑензиÑми. Я никак
не Ð¼Ð¾Ð³Ñ Ð¿Ð¾Ð½ÑÑÑ, какие ÑÑебованиÑ
+пÑедÑÑвлÑÑÑÑÑ Ðº лиÑензиÑÐ¾Ð²Ð°Ð½Ð¸Ñ Ð¼Ð¾ÐµÐ¹
пÑогÑаммÑ. Ðе бÑли Ð±Ñ Ð²Ñ Ñак лÑбезнÑ
+ÑаÑÑказаÑÑ Ð¼Ð½Ðµ, какими лиÑензиÑми Ñ Ð¼Ð¾Ð³Ñ
полÑзоваÑÑÑÑ?</a></dt>
+
+<dd>
+ЧÑÐ¾Ð±Ñ Ð¾ÑвеÑиÑÑ Ð½Ð° ÑÑÐ¾Ñ Ð²Ð¾Ð¿ÑоÑ, нам нÑжно
взглÑнÑÑÑ Ð½Ð° ÑпиÑок вÑеÑ
+компоненÑов, коÑоÑÑми полÑзÑеÑÑÑ Ð²Ð°Ñа
пÑогÑамма, и кÑаÑкое (доÑÑаÑоÑно
+неÑколÑко пÑедложений на каждÑй
компоненÑ) опиÑание Ñого, как ваÑе
+пÑиложение иÑполÑзÑÐµÑ ÑÑÐ¾Ñ ÐºÐ¾Ð¼Ð¿Ð¾Ð½ÐµÐ½Ñ. ÐоÑ
два пÑимеÑа:
+<ul>
+<li>ЧÑÐ¾Ð±Ñ Ð¼Ð¾Ñ Ð¿ÑогÑамма ÑабоÑала, ее нÑжно
ÑкомпоноваÑÑ Ñ Ð±Ð¸Ð±Ð»Ð¸Ð¾Ñекой ÐÐÐ,
+ÑаÑпÑоÑÑÑанÑемой на ÑÑловиÑÑ
ÐенÑÑей GPL.</li>
+<li>ÐÐ¾Ñ Ð¿ÑогÑамма Ð´ÐµÐ»Ð°ÐµÑ ÑиÑÑемнÑй вÑзов (Ñ
командной ÑÑÑокой, коÑоÑÑÑ Ñ
+ÑоÑÑавлÑÑ), ÑÑÐ¾Ð±Ñ Ð·Ð°Ð¿ÑÑÑиÑÑ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ ÐÐÐ,
коÑоÑÐ°Ñ Ð»Ð¸ÑензиÑÑеÑÑÑ Ð¿Ð¾
+“GPL Ñ Ð¾ÑобÑм иÑклÑÑением, позволÑÑÑим
компоноваÑÑ Ñ QUUX”.</li>
+</ul>
+<p></p></dd>
+
+<dt><a href="#TOCMereAggregation" name="MereAggregation">Ðакова
ÑазниÑа междÑ
+“пÑоÑÑÑм ÑазмеÑением на одном
ноÑиÑеле” и “комбиниÑованием
+двÑÑ
модÑлей а одной пÑогÑамме”?</a></dt>
+
+<dd>
+ÐÑоÑÑое ÑазмеÑение двÑÑ
пÑогÑамм
ознаÑаеÑ, ÑÑо иÑ
запиÑÑваÑÑ Ð¾Ð´Ð½Ñ ÑÑдом Ñ
+дÑÑгой на одном и Ñом же компакÑ-диÑке или
на жеÑÑком диÑке. ÐÑ ÑпоÑÑеблÑем
+ÑÑÐ¾Ñ ÑеÑмин в ÑлÑÑае, когда они ÑвлÑÑÑÑÑ
оÑделÑнÑми пÑогÑаммами, а не
+ÑаÑÑÑми единой пÑогÑаммÑ. ÐÑли в ÑÑом
ÑлÑÑае на Ð¾Ð´Ð½Ñ Ð¸Ð· пÑогÑамм
+ÑаÑпÑоÑÑÑанÑеÑÑÑ GPL, ÑÑо не ÑказÑваеÑÑÑ Ð½Ð°
дÑÑгой пÑогÑамме.
+<p>
+ÐомбиниÑование двÑÑ
модÑлей ознаÑаеÑ
Ñоединение иÑ
вмеÑÑе Ñак, ÑÑо они
+обÑазÑÑÑ ÐµÐ´Ð¸Ð½ÑÑ Ð±Ð¾Ð»ÐµÐµ кÑÑпнÑÑ Ð¿ÑогÑаммÑ.
ÐÑли на лÑбÑÑ Ð¸Ð· ÑаÑÑей
+ÑаÑпÑоÑÑÑанÑеÑÑÑ GPL, вÑе ÑоÑеÑание должно
Ñакже вÑпÑÑкаÑÑÑÑ Ð¿Ð¾Ð´
+GPL — еÑли Ð²Ñ Ð½Ðµ можеÑе или не Ñ
оÑиÑе
ÑÑого делаÑÑ, вам нелÑÐ·Ñ Ð¸Ñ
+комбиниÑоваÑÑ.</p>
+<p>
+ЧÑо пÑедÑÑавлÑÐµÑ Ñобой комбиниÑование
двÑÑ
ÑаÑÑей в Ð¾Ð´Ð½Ñ Ð¿ÑогÑаммÑ? ÐÑо
+ÑÑидиÑеÑкий вопÑоÑ, коÑоÑÑй в конеÑном
ÑÑеÑе ÑеÑаÑÑ ÑÑдÑи. ÐÑ ÑбежденÑ, ÑÑо
+пÑавилÑнÑй кÑиÑеÑий пÑÐ¸Ð½Ð¸Ð¼Ð°ÐµÑ Ð² ÑаÑÑеÑ
как меÑ
анизм взаимодейÑÑÐ²Ð¸Ñ (запÑÑк
+пÑоÑеÑÑов, ÐºÐ°Ð½Ð°Ð»Ñ Ð¾Ð±Ð¼ÐµÐ½Ð° даннÑми,
ÑдаленнÑе вÑÐ·Ð¾Ð²Ñ Ð¿ÑоÑедÑÑ, вÑÐ·Ð¾Ð²Ñ ÑÑнкÑий
+в обÑем адÑеÑном пÑоÑÑÑанÑÑве и Ñ. д.),
Ñак и ÑодеÑжание взаимодейÑÑвиÑ
+(обмен какого Ñода инÑоÑмаÑией пÑоиÑÑ
одиÑ).</p>
+<p>
+ÐÑли модÑли вклÑÑаÑÑÑÑ Ð² один и ÑÐ¾Ñ Ð¶Ðµ
иÑполнÑемÑй Ñайл, они опÑеделенно
+комбиниÑÑÑÑÑÑ Ð² одной пÑогÑамме. ÐÑли
модÑли ÑоÑÑавленÑ, ÑÑÐ¾Ð±Ñ ÑабоÑаÑÑ,
+ÑвÑзÑваÑÑÑ Ð² обÑем адÑеÑном пÑоÑÑÑанÑÑве,
ÑÑо поÑÑи навеÑное ознаÑаеÑ, ÑÑо
+они комбиниÑÑÑÑÑÑ Ð² Ð¾Ð´Ð½Ñ Ð¿ÑогÑаммÑ.</p>
+<p>
+ÐапÑоÑив, ÐºÐ°Ð½Ð°Ð»Ñ Ð¾Ð±Ð¼ÐµÐ½Ð° даннÑми, ÑокеÑÑ Ð¸
аÑгÑменÑÑ ÐºÐ¾Ð¼Ð°Ð½Ð´Ð½Ð¾Ð¹
+ÑÑÑоки — меÑ
Ð°Ð½Ð¸Ð·Ð¼Ñ Ð²Ð·Ð°Ð¸Ð¼Ð¾Ð´ÐµÐ¹ÑÑвиÑ,
обÑÑно иÑполÑзÑемÑе междÑ
+двÑÐ¼Ñ Ð¾ÑделÑнÑми пÑогÑаммами. Так ÑÑо
когда они пÑименÑÑÑÑÑ Ð´Ð»Ñ
+взаимодейÑÑвиÑ, модÑли обÑÑно ÑвлÑÑÑÑÑ
оÑделÑнÑми пÑогÑаммами. Ðо еÑли
+ÑодеÑжание взаимодейÑÑÐ²Ð¸Ñ Ð´Ð¾ÑÑаÑоÑно
глÑбоко, еÑли пÑоиÑÑ
Ð¾Ð´Ð¸Ñ Ð¾Ð±Ð¼ÐµÐ½ ÑложнÑми
+внÑÑÑенними ÑÑÑÑкÑÑÑами даннÑÑ
, ÑÑо Ñоже
Ð¼Ð¾Ð¶ÐµÑ Ð±ÑÑÑ Ð¾Ñнованием Ð´Ð»Ñ Ñого,
+ÑÑÐ¾Ð±Ñ ÑÑиÑаÑÑ Ð´Ð²Ðµ ÑаÑÑи ÑоÑÑавлÑÑÑими
одной более кÑÑпной пÑогÑаммÑ.
+</p></dd>
+
+<dt><a href="#AssignCopyright">ÐоÑÐµÐ¼Ñ Ð¤Ð¡ÐÐ ÑÑебÑеÑ,
ÑÑÐ¾Ð±Ñ Ñе, кÑо вноÑÐ¸Ñ Ð²ÐºÐ»Ð°Ð´ в
+пÑогÑаммÑ, авÑоÑÑкие пÑава на коÑоÑÑе
пÑÐ¸Ð½Ð°Ð´Ð»ÐµÐ¶Ð°Ñ Ð¤Ð¡ÐÐ, пеÑедавали ÑондÑ
+авÑоÑÑкие пÑава? СледÑÐµÑ Ð»Ð¸ и мне делаÑÑ
ÑÑо, еÑли мне пÑÐ¸Ð½Ð°Ð´Ð»ÐµÐ¶Ð°Ñ Ð°Ð²ÑоÑÑкие
+пÑава на пÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL? ÐÑли да, Ñо
как?</a></dt>
+
+<dd>
+ÐаÑи ÑÑиÑÑÑ Ñказали нам, ÑÑо Ð´Ð»Ñ Ñого,
ÑÑÐ¾Ð±Ñ <a
+href="/licenses/why-assign.html">занÑÑÑ Ð½Ð°Ð¸Ð±Ð¾Ð»ÐµÐµ
вÑгоднÑÑ Ð¿Ð¾Ð·Ð¸ÑÐ¸Ñ Ð¿Ð¾
+обеÑпеÑÐµÐ½Ð¸Ñ ÑÑебований GPL</a> в ÑÑдебном
пÑоÑеÑÑе пÑоÑив наÑÑÑиÑелей, нам
+ÑледÑÐµÑ Ð¿ÑинимаÑÑ Ð¼ÐµÑÑ Ðº ÑомÑ, ÑÑобÑ
авÑоÑÑко-пÑавовой ÑÑаÑÑÑ Ð¿ÑогÑаммÑ
+оÑÑавалÑÑ ÐºÐ°Ðº можно более пÑоÑÑÑм. ÐÑ
делаем ÑÑо, пÑоÑÑ ÐºÐ°Ð¶Ð´Ð¾Ð³Ð¾ ÑазÑабоÑÑика
+либо пеÑедаÑÑ Ð°Ð²ÑоÑÑкие пÑава на его вклад
ФСÐÐ, либо оÑказаÑÑÑÑ Ð¾Ñ
+авÑоÑÑкиÑ
пÑав на него и Ñем ÑамÑм
помеÑÑиÑÑ ÐµÐ³Ð¾ в обÑеÑÑвенное доÑÑоÑние.
+<p>
+ÐÑ Ð¿ÑоÑим Ñакже оÑделÑнÑÑ
ÑазÑабоÑÑиков
полÑÑаÑÑ Ð¾Ñказ Ð¾Ñ Ð°Ð²ÑоÑÑкиÑ
пÑав Ñо
+ÑÑоÑÐ¾Ð½Ñ Ð¸Ñ
ÑабоÑодаÑелей (еÑли они еÑÑÑ),
ÑÑÐ¾Ð±Ñ Ð¼Ñ Ð¼Ð¾Ð³Ð»Ð¸ бÑÑÑ ÑвеÑенÑ, ÑÑо
+ÑÑи ÑабоÑодаÑели не заÑвÑÑ, ÑÑо пÑава на
вклад пÑÐ¸Ð½Ð°Ð´Ð»ÐµÐ¶Ð°Ñ Ð¸Ð¼.</p>
+<p>
+ÐонеÑно, еÑли вÑе ÑазÑабоÑÑики помеÑаÑÑ
Ñвои иÑÑ
однÑе ÑекÑÑÑ Ð² обÑеÑÑвенное
+доÑÑоÑние, Ñо Ð½ÐµÑ Ð°Ð²ÑоÑÑкого пÑава, Ñ
помоÑÑÑ ÐºÐ¾ÑоÑого можно бÑло бÑ
+ÑÑебоваÑÑ ÑоблÑÐ´ÐµÐ½Ð¸Ñ GPL. ÐоÑÑÐ¾Ð¼Ñ Ð¼Ñ
пÑизÑваем лÑдей пеÑедаваÑÑ Ð°Ð²ÑоÑÑкие
+пÑава на кÑÑпнÑе Ð²ÐºÐ»Ð°Ð´Ñ Ð¸ÑÑ
однÑÑ
ÑекÑÑов и
помеÑаÑÑ Ð² обÑеÑÑвенное доÑÑоÑние
+ÑолÑко неболÑÑие изменениÑ.</p>
+<p>
+ÐÑли Ð²Ñ Ñ
оÑиÑе ÑабоÑаÑÑ Ð½Ð°Ð´ обеÑпеÑением
ÑоблÑÐ´ÐµÐ½Ð¸Ñ GPL в оÑноÑении ваÑей
+пÑогÑаммÑ, Ñо Ð´Ð»Ñ Ð²Ð°Ñ, веÑоÑÑно, бÑло бÑ
неплоÑ
ой идеей ÑледоваÑÑ Ð¿Ð¾Ð´Ð¾Ð±Ð½Ð¾Ð¼Ñ
+пÑавилÑ. ÐапиÑиÑе, пожалÑйÑÑа, по адÑеÑÑ <a
+href="mailto:address@hidden";><address@hidden></a>, еÑли Ñ
оÑиÑе
+полÑÑиÑÑ Ð±Ð¾Ð»ÐµÐµ подÑобнÑе ÑведениÑ.
+</p></dd>
+
+<dt><a href="#TOCModifyGPL" name="ModifyGPL">Ðожно мне
измениÑÑ GPL и ÑделаÑÑ
+дÑÑгÑÑ Ð»Ð¸ÑензиÑ?</a></dt>
+
+<dd>
+ÐÑ Ð¼Ð¾Ð¶ÐµÑе полÑзоваÑÑÑÑ ÑÑловиÑми GPL
(возможно, измененнÑми) в дÑÑгой
+лиÑензии пÑи ÑÑловии, ÑÑо Ð²Ñ Ð½Ð°Ð·Ð¾Ð²ÐµÑе ÑвоÑ
лиÑÐµÐ½Ð·Ð¸Ñ Ð¿Ð¾-дÑÑÐ³Ð¾Ð¼Ñ Ð¸ не вклÑÑиÑе
+в нее пÑеамбÑÐ»Ñ GPL, и пÑи ÑÑловии, ÑÑо вÑ
внеÑеÑе Ð¸Ð·Ð¼ÐµÐ½ÐµÐ½Ð¸Ñ Ð² ÑÑководÑÑво к
+пÑÐ¸Ð¼ÐµÐ½ÐµÐ½Ð¸Ñ Ð² конÑе, доÑÑаÑоÑнÑе, ÑÑÐ¾Ð±Ñ ÐµÐ³Ð¾
ÑоÑмÑлиÑовки Ñвно оÑлиÑалиÑÑ Ð¾Ñ
+иÑÑ
однÑÑ
и ÑÑÐ¾Ð±Ñ Ð¾Ð½Ð¾ не Ñпоминало GNU (Ñ
оÑÑ Ð²
дейÑÑвиÑелÑноÑÑи пÑоÑедÑÑа,
+коÑоÑÑÑ Ð²Ñ Ð¾Ð¿Ð¸ÑÑваеÑе, Ð¼Ð¾Ð¶ÐµÑ Ð±ÑÑÑ ÑÑ
одна).
+<p>
+ÐÑли Ð²Ñ Ñ
оÑиÑе воÑполÑзоваÑÑÑÑ Ð½Ð°Ñей
пÑеамбÑлой в измененной лиÑензии,
+запÑоÑиÑе, пожалÑйÑÑа, ÑазÑеÑение по
адÑеÑÑ <a
+href="mailto:address@hidden";><address@hidden></a>. ÐÐ»Ñ ÑÑого мÑ
+Ñ
оÑели Ð±Ñ Ð¿ÑоанализиÑоваÑÑ ÑÑебованиÑ
лиÑензии, ÑÑÐ¾Ð±Ñ Ð¿Ð¾Ð½ÑÑÑ, одобÑÑем ли мÑ
+иÑ
.</p>
+<p>
+ХоÑÑ Ð¼Ñ Ð½Ðµ бÑдем вÑдвигаÑÑ ÑоÑмалÑнÑÑ
возÑажений пÑоÑив ÑÐ¾Ð·Ð´Ð°Ð½Ð¸Ñ Ð²Ð°Ð¼Ð¸ Ñаким
+обÑазом измененной веÑÑии, Ð¼Ñ Ð½Ð°Ð´ÐµÐµÐ¼ÑÑ,
ÑÑо Ð²Ñ Ð´Ð²Ð°Ð¶Ð´Ñ Ð¿Ð¾Ð´ÑмаеÑе и оÑкажеÑеÑÑ
+Ð¾Ñ ÑÑого. ÐÐ·Ð¼ÐµÐ½ÐµÐ½Ð½Ð°Ñ Ñаким обÑазом
лиÑÐµÐ½Ð·Ð¸Ñ Ð±ÑÐ´ÐµÑ Ð¿Ð¾ÑÑи навеÑное <a
+href="#WhatIsCompatible">неÑовмеÑÑима Ñ GNU GPL</a>, а
ÑÐ°ÐºÐ°Ñ Ð½ÐµÑовмеÑÑимоÑÑÑ
+пÑепÑÑÑÑвÑÐµÑ Ð¿Ð¾Ð»ÐµÐ·Ð½Ð¾Ð¼Ñ ÐºÐ¾Ð¼Ð±Ð¸Ð½Ð¸ÑованиÑ
модÑлей. Уже одно ÑвелиÑение
+ÑиÑленноÑÑи ÑазнÑÑ
лиÑензий ÑвободнÑÑ
пÑогÑамм Ñамо по Ñебе ÑоздаеÑ
+дополниÑелÑнÑе ÑложноÑÑи.
+</p></dd>
+
+<dt><a href="#TOCGPLCommercially" name="GPLCommercially">ÐÑли Ñ
полÑзÑÑÑÑ
+пÑогÑаммой, коÑоÑÐ°Ñ Ð¿Ð¾Ð»ÑÑена на ÑÑловиÑÑ
GNU GPL, Ð¼Ð¾Ð³Ñ Ð»Ð¸ Ñ Ð²Ð¸Ð´Ð¾Ð¸Ð·Ð¼ÐµÐ½Ð¸ÑÑ
+пеÑвонаÑалÑнÑй иÑÑ
однÑй ÑекÑÑ Ð² новÑÑ
пÑогÑаммÑ, а заÑем ÑаÑпÑоÑÑÑанÑÑÑ Ð¸
+пÑодаваÑÑ ÑÑÑ Ð½Ð¾Ð²ÑÑ Ð¿ÑогÑаммÑ
коммеÑÑеÑки?</a></dt>
+
+<dd>
+Ðам позволено пÑодаваÑÑ ÐºÐ¾Ð¿Ð¸Ð¸ измененной
пÑогÑÐ°Ð¼Ð¼Ñ Ð·Ð° денÑги, но ÑолÑко на
+ÑÑловиÑÑ
GNU GPL. Таким обÑазом, Ð²Ñ Ð´Ð¾Ð»Ð¶Ð½Ñ,
напÑимеÑ, ÑделаÑÑ Ð¸ÑÑ
однÑй ÑекÑÑ
+доÑÑÑпнÑм Ð´Ð»Ñ Ð¿Ð¾Ð»ÑзоваÑелей пÑогÑаммÑ,
как опиÑано в GPL, и им должно бÑÑÑ
+ÑазÑеÑено изменÑÑÑ Ð¸ пеÑеÑаÑпÑоÑÑÑанÑÑÑ
ее, как опиÑано в GPL.
+<p>
+ÐÑи ÑÑÐµÐ±Ð¾Ð²Ð°Ð½Ð¸Ñ — ÑÑÐ»Ð¾Ð²Ð¸Ñ Ð²ÐºÐ»ÑÑениÑ
ÑаÑÑей пÑогÑамм под GPL,
+коÑоÑÑе Ð²Ñ Ð¿Ð¾Ð»ÑÑили, в ÑÐ²Ð¾Ñ ÑобÑÑвеннÑÑ
пÑогÑаммÑ.
+</p></dd>
+
+
+<dt><a href="#TOCGPLOtherThanSoftware" name="GPLOtherThanSoftware">ÐÐ¾Ð³Ñ Ñ
+пÑименÑÑÑ GPL Ð´Ð»Ñ Ñего-нибÑÐ´Ñ ÐºÑоме
пÑогÑамм?</a></dt>
+
+<dd>
+GPL можно пÑименÑÑÑ Ð´Ð»Ñ ÑÐ°Ð±Ð¾Ñ Ð»Ñбого Ñода,
еÑли ÑолÑко ÑÑно, ÑÑо ÑоÑÑавлÑеÑ
+“иÑÑ
однÑй ÑекÑÑ” Ð´Ð»Ñ ÑÑой ÑабоÑÑ. GPL
опÑеделÑÐµÑ ÐµÐ³Ð¾ как
+пÑедпоÑÑиÑелÑнÑÑ Ð´Ð»Ñ Ð²Ð½ÐµÑÐµÐ½Ð¸Ñ Ð¸Ð·Ð¼ÐµÐ½ÐµÐ½Ð¸Ð¹
ÑоÑÐ¼Ñ ÑабоÑÑ.
+<p>
+Ðднако Ð´Ð»Ñ ÑÑководÑÑв и ÑÑебников или,
вообÑе, Ð´Ð»Ñ Ð»Ñбого Ñода ÑабоÑ,
+коÑоÑÑе пÑедназнаÑÐµÐ½Ñ Ð´Ð»Ñ Ð¾Ð±ÑÑениÑ
пÑедмеÑÑ, Ð¼Ñ ÑекомендÑем иÑполÑзоваÑÑ
+GFDL, а не GPL.
+</p></dd>
+
+
+<dt><a href="#LGPLJava">Ðак LGPL ÑабоÑÐ°ÐµÑ Ñ Java?</a></dt>
+
+<dd>
+
+<p>Ðна ÑабоÑÐ°ÐµÑ Ð² ÑооÑвеÑÑÑвии Ñ Ñем, как
она ÑоÑÑавлена, Ð´Ð»Ñ Ñего
+пÑедназнаÑена и Ñак, как ÑÑо задÑмано.
ÐодÑобноÑÑи Ñм. в <a
+href="/licenses/lgpl-java.html">оÑделÑной ÑÑаÑÑе</a>.
+</p></dd>
+
+<dt><a href="#TOCConsider" name="Consider">РаÑÑмоÑÑим
ÑиÑÑаÑиÑ: 1) X вÑпÑÑкаеÑ
+веÑÑÐ¸Ñ V1 пÑоекÑа под GPL. 2) Y вноÑиÑ
доÑабоÑки в веÑÑÐ¸Ñ V2, коÑоÑÑе
+вклÑÑаÑÑ Ð¸Ð·Ð¼ÐµÐ½ÐµÐ½Ð¸Ñ Ð¸ новÑе ÑекÑÑÑ
пÑогÑамм, оÑнованнÑе на V1. 3) X Ñ
оÑеÑ
+вÑпÑÑкаÑÑ V2 под лиÑензией, оÑлиÑной Ð¾Ñ GPL.
ÐÑжно ли X ÑазÑеÑение Y?</a></dt>
+
+<dd>
+Ðа. Y бÑл обÑзан вÑпÑÑÑиÑÑ ÑÐ²Ð¾Ñ Ð²ÐµÑÑÐ¸Ñ Ð¿Ð¾Ð´
GNU GPL как ÑледÑÑвие Ñого, ÑÑо
+она бÑла оÑнована на веÑÑии V1, полÑÑенной
Ð¾Ñ X. ÐиÑÑо не ÑÑебовало Ð¾Ñ Y
+ÑоглаÑиÑÑÑÑ Ð½Ð° лÑбÑÑ Ð´ÑÑгÑÑ Ð»Ð¸ÑÐµÐ½Ð·Ð¸Ñ Ð´Ð»Ñ
ÑекÑÑов Y. СледоваÑелÑно, X должен
+полÑÑиÑÑ ÑазÑеÑение Y пеÑед Ñем, как
вÑпÑÑÑиÑÑ ÑÑи пÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ дÑÑгой
+лиÑензией.
+<p></p></dd>
+
+
+<dt><a href="#TOCGPLInProprietarySystem" name="GPLInProprietarySystem">Ðне
+Ñ
оÑелоÑÑ Ð±Ñ Ð²ÐºÐ»ÑÑиÑÑ Ð¿ÑогÑаммÑ,
ÑаÑпÑоÑÑÑанÑемÑÑ Ð¿Ð¾ GPL, в ÑÐ²Ð¾Ñ Ð½ÐµÑвободнÑÑ
+ÑиÑÑемÑ. Ðожно мне ÑÑо делаÑÑ?</a></dt>
+
+<dd>
+ÐÑ Ð½Ðµ можеÑе вклÑÑаÑÑ Ð¿ÑогÑаммÑ,
ÑаÑпÑоÑÑÑанÑемÑе по GPL, в неÑвободнÑÑ
+ÑиÑÑемÑ. Ð¦ÐµÐ»Ñ GPL — пÑедоÑÑавиÑÑ
ÐºÐ°Ð¶Ð´Ð¾Ð¼Ñ ÑÐ²Ð¾Ð±Ð¾Ð´Ñ ÐºÐ¾Ð¿Ð¸ÑоваÑÑ,
+пеÑедаваÑÑ, понимаÑÑ Ð¸ изменÑÑÑ Ð¿ÑогÑаммÑ.
ÐÑли Ð±Ñ Ð²Ñ Ð¼Ð¾Ð³Ð»Ð¸ вклÑÑаÑÑ
+пÑогÑаммÑ, ÑаÑпÑоÑÑÑанÑемÑе по GPL, в
неÑвободнÑÑ ÑиÑÑемÑ, ÑÑо пÑивело Ð±Ñ Ðº
+ÑомÑ, ÑÑо Ñакие пÑогÑÐ°Ð¼Ð¼Ñ Ñоже ÑÑали бÑ
неÑвободнÑми.
+<p>
+СиÑÑема, вклÑÑаÑÑÐ°Ñ Ð¿ÑогÑаммÑ,
ÑаÑпÑоÑÑÑанÑемÑÑ Ð¿Ð¾ GPL, ÑвлÑеÑÑÑ
ÑаÑÑиÑеннÑм
+ваÑианÑом ÑÑой пÑогÑаммÑ. Ð GPL Ñказано, ÑÑо
ÑаÑÑиÑÐµÐ½Ð½Ð°Ñ Ð²ÐµÑÑÐ¸Ñ Ð¿ÑогÑаммÑ
+должна вÑпÑÑкаÑÑÑÑ Ð¿Ð¾Ð´ GPL, еÑли она вообÑе
вÑпÑÑкаеÑÑÑ. ÐÑо делаеÑÑÑ Ð¿Ð¾
+двÑм пÑиÑинам: во-пеÑвÑÑ
, ÑÑобÑ
гаÑанÑиÑоваÑÑ, ÑÑо полÑзоваÑели, коÑоÑÑе
+полÑÑаÑÑ Ð¿ÑогÑаммÑ, полÑÑаÑÑ ÑвободÑ,
коÑоÑÐ°Ñ Ñ Ð½Ð¸Ñ
должна бÑÑÑ, а
+во-вÑоÑÑÑ
, ÑÑÐ¾Ð±Ñ Ð¿Ð¾Ð¾ÑÑиÑÑ Ð»Ñдей возвÑаÑаÑÑ
ÑлÑÑÑениÑ, коÑоÑÑе они делаÑÑ.</p>
+<p>
+Ðднако во многиÑ
ÑлÑÑаÑÑ
Ð²Ñ Ð¼Ð¾Ð¶ÐµÑе
ÑаÑпÑоÑÑÑанÑÑÑ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL вмеÑÑе
+Ñо Ñвоей неÑвободной ÑиÑÑемой. ЧÑобÑ
делаÑÑ ÑÑо пÑавилÑно, Ð²Ñ Ð´Ð¾Ð»Ð¶Ð½Ñ
+ÑдоÑÑовеÑиÑÑÑÑ, ÑÑо ÑвободнÑе и
неÑвободнÑе пÑогÑÐ°Ð¼Ð¼Ñ Ð¾Ð±ÑаÑÑÑÑ Ð½Ð°
ÑаÑÑÑоÑнии
+вÑÑÑнÑÑой ÑÑки, ÑÑо они не ÑоÑеÑаÑÑÑÑ
наÑÑолÑко ÑеÑно, ÑÑо ÑÑо Ð´ÐµÐ»Ð°ÐµÑ Ð¸Ñ
+ÑакÑиÑеÑки единой пÑогÑаммой.</p>
+<p>
+РазниÑа Ð¼ÐµÐ¶Ð´Ñ ÑÑим и “вклÑÑением”
пÑогÑамм под GPL ÑаÑÑиÑно
+ÑоÑÑÐ¾Ð¸Ñ Ð² ÑÑÑноÑÑи, а ÑаÑÑиÑно — в
ÑоÑме взаимодейÑÑвиÑ. ЧаÑÑÑ,
+коÑоÑÐ°Ñ ÐºÐ°ÑаеÑÑÑ ÑÑÑноÑÑи, Ñакова: еÑли
две пÑогÑÐ°Ð¼Ð¼Ñ ÑоÑеÑаÑÑÑÑ Ñак, ÑÑо
+ÑакÑиÑеÑки ÑÑановÑÑÑÑ Ð´Ð²ÑÐ¼Ñ ÑаÑÑÑми одной
пÑогÑаммÑ, Ñо Ð²Ñ Ð½Ðµ можеÑе
+ÑаÑÑмаÑÑиваÑÑ Ð¸Ñ
как ÑазделÑнÑе
пÑогÑаммÑ. Таким обÑазом, GPL должна
+ÑаÑпÑоÑÑÑанÑÑÑÑÑ Ð½Ð° вÑе ÑÑо.</p>
+<p>
+ÐÑли две пÑогÑÐ°Ð¼Ð¼Ñ Ð¾ÑÑаÑÑÑÑ ÐºÐ°Ðº ÑледÑеÑ
ÑазделеннÑми, как компилÑÑÐ¾Ñ Ð¸ ÑдÑо
+или как ÑедакÑÐ¾Ñ Ð¸ команднÑй
инÑеÑпÑеÑаÑоÑ, Ñо Ð²Ñ Ð¼Ð¾Ð¶ÐµÑе оÑноÑиÑÑÑÑ Ðº
ним
+как к двÑм ÑазделÑнÑм пÑогÑаммам — но
Ð²Ñ Ð´Ð¾Ð»Ð¶Ð½Ñ Ð´ÐµÐ»Ð°ÑÑ ÑÑо
+ÑооÑвеÑÑÑвÑÑÑим обÑазом. ÐдеÑÑ Ð´ÐµÐ»Ð¾
пÑоÑÑо в ÑоÑме: как Ð²Ñ Ð¾Ð¿Ð¸ÑÑваеÑе Ñо,
+ÑÑо Ð²Ñ Ð´ÐµÐ»Ð°ÐµÑе. ÐоÑÐµÐ¼Ñ Ð´Ð»Ñ Ð½Ð°Ñ ÑÑо не
безÑазлиÑно? ÐоÑÐ¾Ð¼Ñ ÑÑо Ð¼Ñ Ñ
оÑим
+гаÑанÑиÑоваÑÑ, ÑÑо полÑзоваÑели ÑÑно
оÑознаÑÑ ÑвободнÑй ÑÑаÑÑÑ Ð¿ÑогÑамм под
+GPL в ÑбоÑнике.</p>
+<p>
+ÐÑли Ð±Ñ Ð»Ñди ÑобиÑалиÑÑ ÑаÑпÑоÑÑÑанÑÑÑ
пÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL, назÑÐ²Ð°Ñ Ð¸Ñ
+“ÑаÑÑÑÑ” ÑиÑÑемÑ, о коÑоÑой
полÑзоваÑели знаÑÑ, ÑÑо она ÑаÑÑиÑно
+неÑвободна, Ñо Ñ Ð¿Ð¾Ð»ÑзоваÑелей могла бÑ
возникнÑÑÑ Ð½ÐµÑвеÑенноÑÑÑ Ð² ÑвоиÑ
+пÑаваÑ
по оÑноÑÐµÐ½Ð¸Ñ Ðº пÑогÑаммам под GPL. Ðо
еÑли они бÑдÑÑ Ð·Ð½Ð°ÑÑ, ÑÑо Ñо,
+ÑÑо они полÑÑили — ÑÑо ÑвободнаÑ
пÑогÑамма плÑÑ Ð´ÑÑÐ³Ð°Ñ Ð¿ÑогÑамма,
+бок о бок, Ñо иÑ
пÑава бÑдÑÑ ÑÑнÑ.
+</p></dd>
+
+<dt><a href="#TOCGPLWrapper" name="GPLWrapper">Ðне Ñ
оÑелоÑÑ Ð±Ñ
вклÑÑиÑÑ
+пÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL в ÑÐ²Ð¾Ñ Ð½ÐµÑвободнÑÑ
ÑиÑÑемÑ. ÐÐ¾Ð³Ñ Ñ ÑÑо ÑделаÑÑ, поÑÑавив
+“обеÑÑÑваÑÑий” модÑÐ»Ñ Ð¿Ð¾Ð´
ÑовмеÑÑимой Ñ GPL неогÑаниÑиÑелÑной
+лиÑензией (как, напÑимеÑ, лиÑÐµÐ½Ð·Ð¸Ñ X11) междÑ
ÑаÑÑÑÑ, ÑаÑпÑоÑÑÑанÑемой по
+GPL, и неÑвободной ÑаÑÑÑÑ?</a></dt>
+
+<dd><p>ÐеÑ. ÐиÑÐµÐ½Ð·Ð¸Ñ X11 ÑовмеÑÑима Ñ GPL, Ñак ÑÑо
Ð²Ñ Ð¼Ð¾Ð¶ÐµÑе добавлÑÑÑ Ð¼Ð¾Ð´ÑÐ»Ñ Ð²
+пÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL и помеÑаÑÑ ÐµÐ³Ð¾ под
лиÑÐµÐ½Ð·Ð¸Ñ X11. Ðо еÑли Ð±Ñ Ð²Ñ ÑобиÑалиÑÑ
+вÑÑÑаиваÑÑ Ð¾Ð±Ðµ ÑаÑÑи в более кÑÑпнÑÑ
пÑогÑаммÑ, Ñо вÑе ÑÑо в Ñелом вклÑÑало
+Ð±Ñ ÑаÑÑÑ, ÑаÑпÑоÑÑÑанÑемÑÑ Ð¿Ð¾ GPL, Ñак ÑÑо
ÑÑо нÑжно бÑло Ð±Ñ Ð»Ð¸ÑензиÑоваÑÑ
+<em>в Ñелом</em> по GNU GPL.</p>
+
+<p>Ð¢Ð¾Ñ ÑакÑ, ÑÑо неÑвободнÑй модÑÐ»Ñ Ð
ÑоединÑеÑÑÑ Ñ Ð¼Ð¾Ð´Ñлем Ð, ÑаÑпÑоÑÑÑанÑемÑм
+по GPL, ÑолÑко ÑеÑез модÑÐ»Ñ Ð,
ÑаÑпÑоÑÑÑанÑемÑй по лиÑензии X11, Ñ ÑоÑки
+зÑÐµÐ½Ð¸Ñ Ð·Ð°ÐºÐ¾Ð½Ð° знаÑÐµÐ½Ð¸Ñ Ð½Ðµ имееÑ; знаÑение
Ð¸Ð¼ÐµÐµÑ ÑÐ¾Ñ ÑакÑ, ÑÑо модÑÐ»Ñ Ð
+вклÑÑаеÑÑÑ Ð² Ñелое.
+</p></dd>
+
+<dt><a href="#TOCLibGCCException" name="LibGCCException"> ÐопÑÑкаеÑ
ли
+иÑклÑÑение libstdc++ динамиÑеÑкое
ÑвÑзÑвание?</a></dt>
+
+<dd><p>Ðа. ÐÑклÑÑение пÑедназнаÑено Ð´Ð»Ñ Ñого,
ÑÑÐ¾Ð±Ñ Ð¿Ð¾Ð·Ð²Ð¾Ð»Ð¸ÑÑ Ð»ÑдÑм компилиÑоваÑÑ
+неÑвободнÑе пÑогÑÐ°Ð¼Ð¼Ñ Ñ Ð¿Ð¾Ð¼Ð¾ÑÑÑ gcc.</p></dd>
+
+<dt><a href="#TOCMoneyGuzzlerInc" name="MoneyGuzzlerInc">Ðне Ñ
оÑелоÑÑ Ð±Ñ
+измениÑÑ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL и ÑвÑзаÑÑ Ð¸Ñ
Ñ
библиоÑеками пеÑеноÑимоÑÑи ÐÐÐ
+“ÐаÑмоед”. Я не Ð¼Ð¾Ð³Ñ ÑаÑпÑоÑÑÑанÑÑÑ
иÑÑ
однÑй ÑекÑÑ ÑÑиÑ
+библиоÑек, Ñак ÑÑо ÐºÐ°Ð¶Ð´Ð¾Ð¼Ñ Ð¿Ð¾Ð»ÑзоваÑелÑ,
коÑоÑÑй Ñ
оÑел Ð±Ñ Ð¸Ð·Ð¼ÐµÐ½Ð¸ÑÑ ÑÑи
+веÑÑии, пÑиÑлоÑÑ Ð±Ñ Ð¿Ð¾Ð»ÑÑиÑÑ ÑÑи
библиоÑеки оÑделÑно. ÐоÑÐµÐ¼Ñ GPL не
+допÑÑÐºÐ°ÐµÑ ÑÑого?</a></dt>
+
+<dd>
+GPL не допÑÑÐºÐ°ÐµÑ ÑÑого по двÑм пÑиÑинам.
+<p>
+Ðо-пеÑвÑÑ
, обÑÐ°Ñ Ð¿ÑиÑина. ÐÑли Ð±Ñ Ð¼Ñ
ÑазÑеÑили компании Ð ÑделаÑÑ
+неÑвободнÑй Ñайл, а компании Ð
ÑаÑпÑоÑÑÑанÑÑÑ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL,
ÑоединеннÑÑ
+Ñ ÑÑим Ñайлом, полÑÑилаÑÑ Ð±Ñ Ð´ÑÑа в GPL,
доÑÑаÑоÑно болÑÑаÑ, ÑÑÐ¾Ð±Ñ ÑеÑез нее
+пÑоеÑ
ал гÑÑзовик. ÐÑо ÑазÑеÑило бÑ
ÑдеÑживаÑÑ Ð¸ÑÑ
однÑй ÑекÑÑ Ð²ÑевозможнÑÑ
+изменений и ÑаÑÑиÑений пÑогÑамм под GPL.</p>
+<p>
+ÐÑедоÑÑавление вÑем полÑзоваÑелÑм
доÑÑÑпа к иÑÑ
Ð¾Ð´Ð½Ð¾Ð¼Ñ ÑекÑÑÑ —
+одна из наÑиÑ
главнÑÑ
Ñелей, Ñак ÑÑо Ñакого
поÑледÑÑÐ²Ð¸Ñ Ð¼Ñ Ð¾Ð¿Ñеделенно Ñ
оÑим
+избежаÑÑ.</p>
+<p>
+Ðолее конкÑеÑно, веÑÑии пÑогÑамм,
ÑвÑзаннÑе Ñ Ð±Ð¸Ð±Ð»Ð¸Ð¾Ñеками ÐÐÐ
+“ÐаÑмоед”, в дейÑÑвиÑелÑноÑÑи не
бÑли Ð±Ñ ÑвободнÑми в наÑем
+понимании — они не поÑÑавлÑлиÑÑ Ð±Ñ Ñ
полнÑм иÑÑ
однÑм ÑекÑÑом,
+коÑоÑÑй позволÑÐµÑ Ð¿Ð¾Ð»ÑзоваÑелÑм пÑавиÑÑ Ð¸
пеÑекомпилиÑоваÑÑ Ð¿ÑогÑаммÑ.
+</p></dd>
+
+<dt><a href="#TOCGPLIncompatibleAlone" name="GPLIncompatibleAlone">ÐÑли в
+лиÑензии Ð´Ð»Ñ Ð¼Ð¾Ð´ÑÐ»Ñ Ð ÐµÑÑÑ ÑÑебование,
неÑовмеÑÑимое Ñ GPL, но ÑÑебование
+дейÑÑвÑеÑ, ÑолÑко когда Ð
ÑаÑпÑоÑÑÑанÑеÑÑÑ Ñам по Ñебе, а не когда он
+вклÑÑаеÑÑÑ Ð² более кÑÑпнÑÑ Ð¿ÑогÑаммÑ,
Ð´ÐµÐ»Ð°ÐµÑ Ð»Ð¸ ÑÑо лиÑÐµÐ½Ð·Ð¸Ñ Ð½ÐµÑовмеÑÑимой Ñ
+GPL? ÐÐ¾Ð³Ñ Ñ ÐºÐ¾Ð¼Ð±Ð¸Ð½Ð¸ÑоваÑÑ Ð¸Ð»Ð¸ ÑвÑзÑваÑÑ Ð Ñ
пÑогÑаммой под GPL?</a></dt>
+
+<dd>
+ÐÑли пÑогÑамма РвÑпÑÑкаеÑÑÑ Ð¿Ð¾Ð´ GPL, ÑÑо
знаÑиÑ, ÑÑо <strong>лÑÐ±Ð°Ñ Ð¸ каждаÑ
+ÑаÑÑÑ ÐµÐµ</strong> Ð¼Ð¾Ð¶ÐµÑ Ð¸ÑполÑзоваÑÑÑÑ Ð¿Ð¾ GPL.
ÐÑли Ð²Ñ Ð²ÐºÐ»ÑÑаеÑе модÑÐ»Ñ Ð Ð¸
+вÑпÑÑкаеÑе комбиниÑованнÑÑ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð+Ð
под GPL, ÑÑо знаÑиÑ, ÑÑо лÑбаÑ
+ÑаÑÑÑ Ð+Ð Ð¼Ð¾Ð¶ÐµÑ Ð¸ÑполÑзоваÑÑÑÑ Ð¿Ð¾ GPL.
Ð — одна из ÑаÑÑей
+Ð+Ð. Таким обÑазом, вÑпÑÑк Ð+Рпод GPL
ознаÑаеÑ, ÑÑо Ð Ð¼Ð¾Ð¶ÐµÑ Ð¸ÑполÑзоваÑÑÑÑ
+по GPL. ÐнаÑе говоÑÑ, полÑзоваÑелÑ,
полÑÑивÑий Ð+Рпо GPL, Ð¼Ð¾Ð¶ÐµÑ ÑдалиÑÑ Ð,
+Ñак ÑÑо РоÑÑанеÑÑÑ Ð¿Ð¾Ð´ GPL.
+<p>
+ÐÑли лиÑÐµÐ½Ð·Ð¸Ñ Ð¼Ð¾Ð´ÑÐ»Ñ Ð ÑазÑеÑÐ°ÐµÑ Ð²Ð°Ð¼
даваÑÑ Ñакое ÑазÑеÑение, Ñо она
+ÑовмеÑÑима Ñ GPL. РпÑоÑивном ÑлÑÑае она не
ÑовмеÑÑима Ñ GPL.</p>
+<p>
+ÐÑли в лиÑензии РнедвÑÑмÑÑленно Ñказано,
ÑÑо Ð²Ñ Ð´Ð¾Ð»Ð¶Ð½Ñ ÑовеÑÑаÑÑ
+опÑеделеннÑе дейÑÑÐ²Ð¸Ñ (неÑовмеÑÑимÑе Ñ GPL),
когда Ð²Ñ ÑаÑпÑоÑÑÑанÑеÑе модÑлÑ
+Ð Ñам по Ñебе, Ñо ÑÑо не позволÑÐµÑ Ð²Ð°Ð¼
ÑаÑпÑоÑÑÑанÑÑÑ Ð Ð¿Ð¾ GPL. ÐÑÑÑда
+ÑледÑеÑ, ÑÑо и Ð+Рпо GPL вам вÑпÑÑкаÑÑ
нелÑзÑ. Таким обÑазом, вам нелÑзÑ
+ÑвÑзÑваÑÑ Ð¸Ð»Ð¸ комбиниÑоваÑÑ Ð Ñ Ð.
+</p></dd>
+
+<dt><a href="#TOCModifiedJustBinary" name="ModifiedJustBinary">ÐÐ¾Ð³Ñ Ñ
вÑпÑÑÑиÑÑ
+измененнÑÑ Ð²ÐµÑÑÐ¸Ñ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL ÑолÑко
в двоиÑном виде?</a></dt>
+<dd>
+ÐеÑ. ÐеÑÑ ÑмÑÑл GPL заклÑÑаеÑÑÑ Ð² Ñом, ÑÑо
вÑе модиÑиÑиÑованнÑе веÑÑии
+Ð´Ð¾Ð»Ð¶Ð½Ñ Ð±ÑÑÑ <a href="/philosophy/free-sw.html">ÑвободнÑми
+пÑогÑаммами</a> — ÑÑо ознаÑаеÑ, в
ÑаÑÑноÑÑи, ÑÑо иÑÑ
однÑй ÑекÑÑ
+модиÑиÑиÑованной веÑÑии доÑÑÑпен
полÑзоваÑелÑм.
+<p></p></dd>
+
+
+<dt><a href="#TOCUnchangedJustBinary" name="UnchangedJustBinary">Я взÑл
по ÑеÑи
+ÑолÑко двоиÑнÑй Ñайл. ÐÑли Ñ ÑаÑпÑоÑÑÑанÑÑ
копии, должен ли Ñ Ð¿Ð¾Ð»ÑÑиÑÑ
+иÑÑ
однÑй ÑекÑÑ Ð¸ ÑаÑпÑоÑÑÑанÑÑÑ ÐµÐ³Ð¾
Ñоже?</a></dt>
+<dd>
+Ðа. ÐбÑее пÑавило Ñаково: еÑли вÑ
ÑаÑпÑоÑÑÑанÑеÑе двоиÑнÑе ÑайлÑ, Ð²Ñ Ð´Ð¾Ð»Ð¶Ð½Ñ
+ÑаÑпÑоÑÑÑанÑÑÑ Ð¸ полнÑй иÑÑ
однÑй ÑекÑÑ.
ÐÑклÑÑение Ð´Ð»Ñ ÑлÑÑаÑ, когда вÑ
+полÑÑили пиÑÑменное пÑедложение иÑÑ
одного ÑекÑÑа, веÑÑма огÑаниÑено.
+<p></p></dd>
+
+<dt><a href="#TOCDistributeWithSourceOnInternet"
+name="DistributeWithSourceOnInternet">Я Ñ
оÑÑ ÑаÑпÑоÑÑÑанÑÑÑ
двоиÑнÑе ÑайлÑ
+на ÑизиÑеÑком ноÑиÑеле без ÑопÑовождаÑÑиÑ
иÑÑ
однÑÑ
ÑекÑÑов. ÐÐ¾Ð³Ñ Ñ
+поÑÑавлÑÑÑ Ð¸ÑÑ
однÑй ÑекÑÑ Ð¿Ð¾ FTP вмеÑÑо
заказа по поÑÑе?</a></dt>
+
+<dd>
+ÐÑ Ð²Ð°Ñ ÑÑебÑеÑÑÑ Ð¿ÑедоÑÑавиÑÑ Ð¸ÑÑ
однÑй
ÑекÑÑ Ð² оÑÐ²ÐµÑ Ð½Ð° заказ по поÑÑе на
+ÑизиÑеÑком ноÑиÑеле, еÑли кÑо-нибÑдÑ
Ð·Ð°ÐºÐ°Ð¶ÐµÑ ÐµÐ³Ð¾. ÐÑ, ÑазÑмееÑÑÑ, можеÑе
+пÑедлагаÑÑ ÑооÑвеÑÑÑвÑÑÑий иÑÑ
однÑй
ÑекÑÑ Ð¿Ð¾ FTP в дополнение к возможноÑÑи
+заказа по поÑÑе, но доÑÑÑпа к иÑÑ
одномÑ
ÑекÑÑÑ Ð¿Ð¾ FTP не доÑÑаÑоÑно, ÑÑобÑ
+вÑполниÑÑ ÑÑÐ»Ð¾Ð²Ð¸Ñ Ñаздела 3 GPL.
+<p>
+Ðогда полÑзоваÑÐµÐ»Ñ Ð·Ð°ÐºÐ°Ð·ÑÐ²Ð°ÐµÑ Ð¸ÑÑ
однÑй
ÑекÑÑ, Ð²Ñ Ð´Ð¾Ð»Ð¶Ð½Ñ Ð³Ð°ÑанÑиÑоваÑÑ, ÑÑо
+иÑÑ
однÑй ÑекÑÑ Ð´Ð¾Ð¹Ð´ÐµÑ Ð´Ð¾ ÑÑого
полÑзоваÑелÑ. ÐÑли конкÑеÑнÑй полÑзоваÑелÑ
+Ð¼Ð¾Ð¶ÐµÑ Ð»ÐµÐ³ÐºÐ¾ и Ñдобно полÑÑиÑÑ Ð¾Ñ Ð²Ð°Ñ Ð¸ÑÑ
однÑй ÑекÑÑ Ð¿Ð¾ FTP,
+пÑекÑаÑно — ÑÑо ÑеÑÐ°ÐµÑ Ð·Ð°Ð´Ð°ÑÑ. Ðо не
каждÑй полÑзоваÑÐµÐ»Ñ Ð¼Ð¾Ð¶ÐµÑ
+ÑделаÑÑ ÑÑо. ÐÑÑалÑнÑе полÑзоваÑели имеÑÑ
Ñакое же пÑаво на полÑÑение Ð¾Ñ Ð²Ð°Ñ
+иÑÑ
одного ÑекÑÑа, а ÑÑо знаÑиÑ, ÑÑо вÑ
Ð´Ð¾Ð»Ð¶Ð½Ñ Ð±ÑÑÑ Ð³Ð¾ÑÐ¾Ð²Ñ Ð²ÑÑлаÑÑ ÐµÐ³Ð¾ им по
+поÑÑе.</p>
+<p>
+ÐÑли доÑÑÑп по FTP доÑÑаÑоÑно Ñдобен,
возможно, никÑо не ÑÑÐ°Ð½ÐµÑ Ð·Ð°ÐºÐ°Ð·ÑваÑÑ
+ÐºÐ¾Ð¿Ð¸Ñ Ð¿Ð¾ поÑÑе. ÐÑли ÑÑо Ñак, Ñо вам никогда
не пÑидеÑÑÑ Ð¿Ð¾ÑÑлаÑÑ ÐµÐµ. Ðо вÑ
+не можеÑе пÑедполагаÑÑ ÑÑого.</p>
+<p>
+ÐонеÑно, легÑе вÑего пÑоÑÑо Ñ Ñамого
наÑала поÑÑлаÑÑ Ð¸ÑÑ
однÑй ÑекÑÑ Ñ
+двоиÑнÑми Ñайлами.
+</p>
+<p>ÐÑли Ð²Ñ ÑаÑпÑоÑÑÑанÑеÑе двоиÑнÑе ÑайлÑ
по FTP, <a
+href="#AnonFTPAndSendSources">Ð²Ñ Ð´Ð¾Ð»Ð¶Ð½Ñ ÑаÑпÑоÑÑÑанÑÑÑ
иÑÑ
однÑй ÑекÑÑ Ð¿Ð¾
+FTP.</a></p>
+
+</dd>
+
+<dt><a href="#TOCRedistributedBinariesGetSource"
+name="RedistributedBinariesGetSource">Ðой знакомÑй полÑÑил
двоиÑнÑй Ñайл под
+GPL Ñ Ð¿Ñедложением поÑÑавки иÑÑ
одного
ÑекÑÑа и Ñделал Ð´Ð»Ñ Ð¼ÐµÐ½Ñ ÐºÐ¾Ð¿Ð¸Ñ. ÐÐ¾Ð³Ñ Ñ
+воÑполÑзоваÑÑÑÑ Ð¿Ñедложением, ÑÑобÑ
полÑÑиÑÑ Ð¸ÑÑ
однÑй ÑекÑÑ?</a></dt>
+
+<dd>
+Ðа, можеÑе. ÐÑедложение должно бÑÑÑ
дейÑÑвиÑелÑнÑм Ð´Ð»Ñ Ð²ÑÑкого, Ñ ÐºÐ¾Ð³Ð¾ еÑÑÑ
+ÐºÐ¾Ð¿Ð¸Ñ Ð´Ð²Ð¾Ð¸Ñного Ñайла, коÑоÑÑй оно
ÑопÑовождаеÑ. ÐÐ¾Ñ Ð¿Ð¾ÑÐµÐ¼Ñ Ð² GPL Ñказано,
+ÑÑо Ð²Ð°Ñ Ð·Ð½Ð°ÐºÐ¾Ð¼Ñй должен даÑÑ Ð²Ð°Ð¼ копиÑ
пÑÐµÐ´Ð»Ð¾Ð¶ÐµÐ½Ð¸Ñ Ð²Ð¼ÐµÑÑе Ñ ÐºÐ¾Ð¿Ð¸ÐµÐ¹ двоиÑного
+Ñайла — Ñак ÑÑо Ð²Ñ Ð¼Ð¾Ð¶ÐµÑе им
воÑполÑзоваÑÑÑÑ.
+<p></p></dd>
+
+<dt><a href="#TOCSourceAndBinaryOnDifferentSites"
+name="SourceAndBinaryOnDifferentSites">ÐÐ¾Ð³Ñ Ñ ÑазмеÑÑиÑÑ
двоиÑнÑе ÑÐ°Ð¹Ð»Ñ Ð½Ð°
+Ñвоем ÑеÑвеÑе в ÐнÑеÑнеÑе, а иÑÑ
однÑе
ÑекÑÑÑ — на дÑÑгом
+ÑайÑе?</a></dt>
+
+<dd>
+Ð GPL Ñказано, ÑÑо Ð²Ñ Ð´Ð¾Ð»Ð¶Ð½Ñ Ð¿ÑедлагаÑÑ
доÑÑÑп к копии иÑÑ
одного ÑекÑÑа
+“из Ñого же Ñамого меÑÑа”; Ñо еÑÑÑ,
ÑÑдом Ñ Ð´Ð²Ð¾Ð¸ÑнÑми
+Ñайлами. Ðднако еÑли Ð²Ñ Ð´Ð¾Ð³Ð¾Ð²Ð¾ÑиÑеÑÑ Ñ
дÑÑгим ÑайÑом, ÑÑÐ¾Ð±Ñ Ð¸ÑÑ
однÑй ÑекÑÑ
+бÑл доÑÑÑпен, и ÑазмеÑÑиÑе ÑÑÑÐ»ÐºÑ Ð¸Ð»Ð¸
пеÑекÑеÑÑнÑй ÑказаÑÐµÐ»Ñ Ð½Ð° иÑÑ
однÑй
+ÑекÑÑ ÑÑдом Ñ Ð´Ð²Ð¾Ð¸ÑнÑми Ñайлами, Ð¼Ñ Ð´Ñмаем,
ÑÑо ÑÑо можно ÑÑиÑаÑÑ “Ñем
+же ÑамÑм меÑÑом”.
+<p>
+ÐбÑаÑиÑе внимание, однако, ÑÑо найÑи
какой-нибÑÐ´Ñ ÑайÑ, на коÑоÑом ÑегоднÑ
+оказалÑÑ ÑооÑвеÑÑÑвÑÑÑий иÑÑ
однÑй ÑекÑÑ,
и ÑказаÑÑ, ÑÑÐ¾Ð±Ñ Ð»Ñди иÑкали Ñам,
+не доÑÑаÑоÑно. ÐавÑÑа Ñ Ñого ÑайÑа иÑÑ
однÑй ÑекÑÑ Ð¼Ð¾Ð³ÑÑ ÑдалиÑÑ Ð¸Ð»Ð¸ пÑоÑÑо
+замениÑÑ Ð½Ð° более новÑÑ Ð²ÐµÑÑÐ¸Ñ Ñой же
пÑогÑаммÑ. Тогда Ð²Ñ Ð±Ð¾Ð»ÑÑе не бÑдеÑе
+ÑдовлеÑвоÑÑÑÑ ÑÑебованиÑм GPL. ЧÑобÑ
пÑиложиÑÑ ÑазÑмнÑе ÑÑÐ¸Ð»Ð¸Ñ Ðº ÑоблÑдениÑ
+лиÑензии, вам нÑжно доÑÑигнÑÑÑ
положиÑелÑной договоÑенноÑÑи Ñ Ñем дÑÑгим
+ÑайÑом и Ñаким обÑазом гаÑанÑиÑоваÑÑ, ÑÑо
иÑÑ
однÑй ÑекÑÑ Ð±ÑÐ´ÐµÑ Ð½Ð° нем
+доÑÑÑпен до ÑеÑ
поÑ, пока вÑ
пÑедоÑÑавлÑеÑе доÑÑÑп к двоиÑнÑм Ñайлам.
+</p></dd>
+
+<dt><a href="#DistributeExtendedBinary" name="DistributeExtendedBinary">Я Ñ
оÑÑ
+ÑаÑпÑоÑÑÑанÑÑÑ ÑаÑÑиÑеннÑÑ Ð²ÐµÑÑиÑ
пÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL в двоиÑной
+ÑоÑме. ÐоÑÑаÑоÑно ли ÑаÑпÑоÑÑÑанÑÑÑ Ð¸ÑÑ
однÑй ÑекÑÑ Ð¸ÑÑ
одной веÑÑии?</a></dt>
+
+<dd>
+ÐеÑ, Ð²Ñ Ð´Ð¾Ð»Ð¶Ð½Ñ Ð¿Ð¾ÑÑавлÑÑÑ Ð¸ÑÑ
однÑй ÑекÑÑ,
коÑоÑÑй ÑооÑвеÑÑÑвÑÐµÑ Ð´Ð²Ð¾Ð¸ÑномÑ
+ÑайлÑ. “СооÑвеÑÑÑвÑÑÑий иÑÑ
однÑй
ÑекÑÑ” ознаÑÐ°ÐµÑ Ð¸ÑÑ
однÑй ÑекÑÑ,
+из коÑоÑого полÑзоваÑели могÑÑ
пеÑеÑобÑаÑÑ ÑÐ¾Ñ Ð¶Ðµ ÑамÑй двоиÑнÑй Ñайл.
+<p>
+РпонÑÑие Ñвободной пÑогÑÐ°Ð¼Ð¼Ñ Ð²Ñ
Ð¾Ð´Ð¸Ñ Ñо,
ÑÑо Ñ Ð¿Ð¾Ð»ÑзоваÑелей должен бÑÑÑ
+доÑÑÑп к иÑÑ
Ð¾Ð´Ð½Ð¾Ð¼Ñ ÑекÑÑÑ <strong>пÑогÑамм,
коÑоÑÑми они
+полÑзÑÑÑÑÑ</strong>. У ÑеÑ
, кÑо полÑзÑеÑÑÑ
ваÑей веÑÑией, должен бÑÑÑ Ð´Ð¾ÑÑÑп
+к иÑÑ
Ð¾Ð´Ð½Ð¾Ð¼Ñ ÑекÑÑÑ Ð²Ð°Ñей веÑÑии.</p>
+<p>
+Ðдна из важнейÑиÑ
Ñелей GPL —
вÑÑÑÑоиÑÑ ÐÐ¸Ñ ÑвободÑ, гаÑанÑиÑÑÑ,
+ÑÑо ÑлÑÑÑÐµÐ½Ð¸Ñ Ñвободной пÑогÑÐ°Ð¼Ð¼Ñ Ñами
бÑдÑÑ ÑвободнÑ. ÐÑли Ð²Ñ Ð²ÑпÑÑкаеÑе
+ÑлÑÑÑеннÑÑ Ð²ÐµÑÑÐ¸Ñ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL, вÑ
Ð´Ð¾Ð»Ð¶Ð½Ñ Ð²ÑпÑÑÑиÑÑ ÑлÑÑÑеннÑй иÑÑ
однÑй
+ÑекÑÑ Ð¿Ð¾ GPL.
+</p></dd>
+
+<dt><a href="#DistributingSourceIsInconvenient"
+name="DistributingSourceIsInconvenient">Я Ñ
оÑÑ
ÑаÑпÑоÑÑÑанÑÑÑ Ð´Ð²Ð¾Ð¸ÑнÑе
+ÑайлÑ, но ÑаÑпÑоÑÑÑанение полного иÑÑ
одного ÑекÑÑа неÑдобно. ÐÑÐ´ÐµÑ Ð»Ð¸
+доÑÑаÑоÑно, еÑли Ñ Ñ Ð´Ð²Ð¾Ð¸ÑнÑми Ñайлами
бÑÐ´Ñ Ð¿ÐµÑедаваÑÑ Ð¿Ð¾Ð»ÑзоваÑелÑм ÑоÑнÑе
+опиÑÐ°Ð½Ð¸Ñ Ð¾ÑлиÑий Ð¾Ñ “ÑÑандаÑÑной”
веÑÑии?</a></dt>
+
+<dd>
+Ð Ñаком желании Ð½ÐµÑ Ð½Ð¸Ñего плоÑ
ого, но ÑÑоÑ
меÑод пÑедоÑÑÐ°Ð²Ð»ÐµÐ½Ð¸Ñ Ð¸ÑÑ
однÑÑ
+ÑекÑÑов в дейÑÑвиÑелÑноÑÑи не вÑполнÑеÑ
ÑвоиÑ
задаÑ.
+<p>
+ÐолÑзоваÑелÑ, коÑоÑÐ¾Ð¼Ñ Ð¿Ð¾Ð½Ð°Ð´Ð¾Ð±Ð¸ÑÑÑ Ð¸ÑÑ
однÑй ÑекÑÑ ÑеÑез год, Ð¼Ð¾Ð¶ÐµÑ Ðº ÑомÑ
+вÑемени бÑÑÑ Ð½Ðµ в ÑоÑÑоÑнии полÑÑиÑÑ
нÑжнÑÑ Ð²ÐµÑÑÐ¸Ñ Ñ Ð´ÑÑгого ÑайÑа. Ðа ÑайÑе
+Ñо ÑÑандаÑÑной пÑогÑаммой Ð¼Ð¾Ð¶ÐµÑ Ð±ÑÑÑ
Ð½Ð¾Ð²Ð°Ñ Ð²ÐµÑÑиÑ, а опиÑÐ°Ð½Ð¸Ñ Ð¾ÑлиÑий,
+веÑоÑÑно, к Ñой веÑÑии не подойдÑÑ.</p>
+<p>
+ÐÑак, Ñ Ð´Ð²Ð¾Ð¸ÑнÑми Ñайлами вам нÑжно
пÑедоÑÑавлÑÑÑ Ð¿Ð¾Ð»Ð½Ñе иÑÑ
однÑе ÑекÑÑÑ, а
+не ÑазлиÑиÑ.
+</p></dd>
+
+<dt><a href="#AnonFTPAndSendSources" name="AnonFTPAndSendSources">ÐÐ¾Ð³Ñ Ñ
+пÑедоÑÑавлÑÑÑ Ð´Ð¾ÑÑÑп к двоиÑнÑм Ñайлам на
ÑеÑвеÑе в ÑеÑи, но вÑÑÑлаÑÑ
+иÑÑ
однÑе ÑекÑÑÑ ÑолÑко Ñем, кÑо иÑ
закажеÑ?</a></dt>
+
+<dd>
+<p>ÐÑли Ð²Ñ Ñ
оÑиÑе ÑаÑпÑоÑÑÑанÑÑÑ Ð´Ð²Ð¾Ð¸ÑнÑе
ÑÐ°Ð¹Ð»Ñ Ð¿Ð¾ Ð°Ð½Ð¾Ð½Ð¸Ð¼Ð½Ð¾Ð¼Ñ FTP, вÑ
+по-пÑÐµÐ¶Ð½ÐµÐ¼Ñ Ð´Ð¾Ð»Ð¶Ð½Ñ Ð¿ÑедоÑÑавлÑÑÑ Ð¸ÑÑ
однÑй
ÑекÑÑ Ð¾Ð´Ð½Ð¸Ð¼ из ваÑианÑов,
+пеÑеÑиÑленнÑÑ
в Ñазделе 3. ÐÑо не должно
бÑÑÑ ÑÑÑдно. ÐÑли Ñ
оÑиÑе, вÑ
+можеÑе пÑедоÑÑавиÑÑ Ð¿Ð¸ÑÑменное
пÑедложение иÑÑ
одного ÑекÑÑа; ÑÑо
допÑÑкаеÑÑÑ
+Ñазделом 3(b). Ðо еÑли Ð²Ñ Ð¼Ð¾Ð¶ÐµÑе найÑи ÑайÑ,
ÑÑÐ¾Ð±Ñ ÑаÑпÑоÑÑÑанÑÑÑ ÑвоÑ
+пÑогÑаммÑ, вÑ, конеÑно, можеÑе найÑи и
Ñакой, на коÑоÑом Ñ
ваÑило Ð±Ñ Ð¼ÐµÑÑа
+Ð´Ð»Ñ Ð¸ÑÑ
однÑÑ
ÑекÑÑов.
+</p><p>ÐезавиÑимо Ð¾Ñ Ñого, как вÑ
ÑаÑпÑоÑÑÑанÑеÑе иÑÑ
однÑй ÑекÑÑ, иÑÑ
однÑе
ÑекÑÑÑ,
+коÑоÑÑе Ð²Ñ Ð¿ÑедоÑÑавлÑеÑе, Ð´Ð¾Ð»Ð¶Ð½Ñ ÑоÑно
ÑооÑвеÑÑÑвоваÑÑ Ð´Ð²Ð¾Ð¸ÑнÑм Ñайлам. Ð
+ÑаÑÑноÑÑи, Ð²Ñ Ð´Ð¾Ð»Ð¶Ð½Ñ ÑбедиÑÑÑÑ, ÑÑо ÑÑо
ÑекÑÑÑ Ñой же веÑÑии
+пÑогÑÐ°Ð¼Ð¼Ñ — не ÑÑаÑой веÑÑии и не
более новой.</p>
+<p>
+ÐÑ Ð¼Ð¾Ð¶ÐµÑе пÑедоÑÑавлÑÑÑ Ð¸ÑÑ
однÑе ÑекÑÑÑ Ð¸
двоиÑнÑе ÑÐ°Ð¹Ð»Ñ Ñ ÑазнÑÑ
маÑин пÑи
+ÑÑловии, ÑÑо до ниÑ
одинаково легко
добÑаÑÑÑÑ, и пÑи ÑÑловии, ÑÑо ÑÑдом Ñ
+двоиÑнÑми Ñайлами Ñ Ð²Ð°Ñ ÐµÑÑÑ ÑÐ²ÐµÐ´ÐµÐ½Ð¸Ñ Ð¾
Ñом, где найÑи иÑÑ
однÑе ÑекÑÑÑ.
+</p></dd>
+
+<dt><a href="#HowCanIMakeSureEachDownloadGetsSource"
+name="HowCanIMakeSureEachDownloadGetsSource">Ðак мне
гаÑанÑиÑоваÑÑ, ÑÑо
+каждÑй полÑзоваÑелÑ, полÑÑаÑÑий по ÑеÑи
двоиÑнÑе ÑайлÑ, полÑÑÐ°ÐµÑ Ñакже
+иÑÑ
однÑй ÑекÑÑ?</a></dt>
+
+<dd>
+ÐÑ Ð½Ðµ обÑÐ·Ð°Ð½Ñ ÑÑого гаÑанÑиÑоваÑÑ. Ðак
ÑолÑко Ð²Ñ Ð¿ÑедоÑÑавили доÑÑÑп к
+иÑÑ
Ð¾Ð´Ð½Ð¾Ð¼Ñ ÑекÑÑÑ Ð¸ двоиÑнÑм Ñайлам Ñак,
ÑÑо полÑзоваÑели видÑÑ, ÑÑо
+доÑÑÑпно, и беÑÑÑ Ñо, ÑÑо им нÑжно, вÑ
Ñделали вÑе, ÑÑо Ð¾Ñ Ð²Ð°Ñ
+ÑÑебÑеÑÑÑ. ÐÑаÑÑ Ð»Ð¸ Ñ Ð²Ð°Ñ Ð¸ÑÑ
однÑй
ÑекÑÑ — дело полÑзоваÑелÑ.
+<p>
+ÐаÑи ÑÑÐµÐ±Ð¾Ð²Ð°Ð½Ð¸Ñ Ðº ÑаÑпÑоÑÑÑаниÑелÑм
ÑоÑÑÐ°Ð²Ð»ÐµÐ½Ñ Ð´Ð»Ñ Ñого, ÑÑобÑ
+гаÑанÑиÑоваÑÑ, ÑÑо полÑзоваÑели могÑÑ
полÑÑиÑÑ Ð¸ÑÑ
однÑй ÑекÑÑ, а не длÑ
+Ñого, ÑÑÐ¾Ð±Ñ Ð·Ð°ÑÑавлÑÑÑ Ð¿Ð¾Ð»ÑзоваÑелей
полÑÑаÑÑ Ð¸ÑÑ
однÑй ÑекÑÑ, даже еÑли он
+им не нÑжен.
+</p></dd>
+
+<dt><a href="#UnreleasedMods" name="UnreleasedMods">ФиÑма
иÑполнÑÐµÑ Ð½Ð° ÑайÑе
+модиÑиÑиÑованнÑÑ Ð²ÐµÑÑÐ¸Ñ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL.
Сказано ли в GPL, ÑÑо они должнÑ
+вÑпÑÑÑиÑÑ Ñвои модиÑиÑиÑованнÑе иÑÑ
однÑе
ÑекÑÑÑ?</a></dt>
+
+<dd>
+GPL ÑазÑеÑÐ°ÐµÑ Ð²Ñем делаÑÑ Ð¼Ð¾Ð´Ð¸ÑиÑиÑованнÑе
веÑÑии и пÑименÑÑÑ Ð¸Ð· безо вÑÑкой
+пеÑедаÑи дÑÑгим. То, ÑÑо Ð´ÐµÐ»Ð°ÐµÑ ÑÑа
ÑиÑма — оÑобÑй ÑлÑÑай ÑакиÑ
+дейÑÑвий. СледоваÑелÑно, ÑиÑма не обÑзана
вÑпÑÑкаÑÑ Ð¼Ð¾Ð´Ð¸ÑиÑиÑованнÑе
+иÑÑ
однÑе ÑекÑÑÑ.
+<p>
+Ðажно, ÑÑÐ¾Ð±Ñ Ñ Ð»Ñдей бÑла Ñвобода вноÑиÑÑ
Ð¸Ð·Ð¼ÐµÐ½ÐµÐ½Ð¸Ñ Ð´Ð»Ñ Ð»Ð¸Ñного полÑзованиÑ
+безо вÑÑкой пÑбликаÑии ÑÑиÑ
изменений.
Ðднако ÑазмеÑение пÑогÑÐ°Ð¼Ð¼Ñ Ð½Ð°
+ÑеÑвеÑе, ÑÑÐ¾Ð±Ñ Ð¿Ñблика Ñ Ð½ÐµÐ¹ обÑалаÑÑ, едва
ли ÑвлÑеÑÑÑ “лиÑнÑм”
+иÑполÑзованием, Ñак ÑÑо бÑло Ð±Ñ Ð·Ð°ÐºÐ¾Ð½Ð½Ñм
поÑÑебоваÑÑ Ð²ÑпÑÑка иÑÑ
одного
+ÑекÑÑа в ÑÑом оÑобом ÑлÑÑае. ÐÑ Ð´Ñмаем о
Ñом ÑÑÐ¾Ð±Ñ ÑделаÑÑ ÑÑо-Ñо подобное в
+веÑÑии 3 GPL, но ÑоÑÐ½Ð°Ñ ÑоÑмÑлиÑовка нам
пока в Ð³Ð¾Ð»Ð¾Ð²Ñ Ð½Ðµ пÑиÑла.</p>
+<p>
+Ðо ÑеÑ
Ð¿Ð¾Ñ Ð´Ð»Ñ Ð¿ÑогÑамм, ÑоÑÑавленнÑÑ
длÑ
пÑÐ¸Ð¼ÐµÐ½ÐµÐ½Ð¸Ñ Ð½Ð° ÑеÑевом ÑеÑвеÑе, вам
+Ð¼Ð¾Ð¶ÐµÑ Ð¿Ð¾Ð´Ð¾Ð¹Ñи <a href="http://www.affero.org/oagpl.html";>GPL
ÐÑÑеÑо</a>.
+</p></dd>
+
+<dt><a href="#InternalDistribution"
name="InternalDistribution">ЯвлÑеÑÑÑ Ð»Ð¸
+Ñазмножение и пÑименение многиÑ
копий
внÑÑÑи одной оÑганизаÑии или
+пÑедпÑиÑÑÐ¸Ñ “ÑаÑпÑоÑÑÑанением”?</a></dt>
+
+<dd>
+ÐеÑ, в ÑÑом ÑлÑÑае оÑганизаÑÐ¸Ñ Ð¿ÑоÑÑо
Ð´ÐµÐ»Ð°ÐµÑ ÐºÐ¾Ð¿Ð¸Ð¸ Ð´Ð»Ñ ÑебÑ. Ðак ÑледÑÑвие,
+пÑедпÑиÑÑие или дÑÑÐ³Ð°Ñ Ð¾ÑганизаÑÐ¸Ñ Ð¼Ð¾Ð¶ÐµÑ
ÑазÑабоÑаÑÑ Ð¸Ð·Ð¼ÐµÐ½ÐµÐ½Ð½ÑÑ Ð²ÐµÑÑÐ¸Ñ Ð¸
+ÑÑÑановиÑÑ ÐµÐµ на Ñвои ÑобÑÑвеннÑе
вÑÑиÑлиÑелÑнÑе ÑÑедÑÑва, не ÑазÑеÑаÑ
+пеÑÑÐ¾Ð½Ð°Ð»Ñ ÑаÑпÑоÑÑÑанÑÑÑ ÑÑÑ Ð¸Ð·Ð¼ÐµÐ½ÐµÐ½Ð½ÑÑ
веÑÑÐ¸Ñ Ð²Ð½Ðµ оÑганизаÑии.
+<p>
+Ðднако когда оÑганизаÑÐ¸Ñ Ð¿ÐµÑÐµÐ´Ð°ÐµÑ ÐºÐ¾Ð¿Ð¸Ð¸
дÑÑгим оÑганизаÑиÑм или ÑаÑÑнÑм
+лиÑам, ÑÑо ÑвлÑеÑÑÑ ÑаÑпÑоÑÑÑанением. Ð
ÑаÑÑноÑÑи, пеÑедаÑа копий
+подÑÑдÑикам Ð´Ð»Ñ Ð¿Ð¾Ð»ÑÐ·Ð¾Ð²Ð°Ð½Ð¸Ñ Ð²Ð½Ðµ ÑайÑа
ÑвлÑеÑÑÑ ÑаÑпÑоÑÑÑанением.
+</p></dd>
+
+
+<dt><a href="#StolenCopy" name="StolenCopy">ÐÑли кÑо-нибÑдÑ
ÑкÑÐ°Ð´ÐµÑ ÐºÐ¾Ð¼Ð¿Ð°ÐºÑ-диÑк
+Ñ Ð²ÐµÑÑией пÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL, Ð´Ð°ÐµÑ Ð»Ð¸ GPL емÑ
пÑаво ÑаÑпÑоÑÑÑанÑÑÑ ÑÑÑ Ð²ÐµÑÑиÑ
+далÑÑе?</a></dt>
+
+<dd>
+ÐÑли ÑÑа веÑÑÐ¸Ñ Ð±Ñла вÑпÑÑена где-Ñо еÑе,
Ñо пÑаво делаÑÑ Ð¸
+пеÑеÑаÑпÑоÑÑÑанÑÑÑ ÐºÐ¾Ð¿Ð¸Ð¸ по GPL Ñ Ð²Ð¾Ñа,
веÑоÑÑно, еÑÑÑ, но еÑли его поÑадÑÑ
+в ÑÑÑÑÐ¼Ñ Ð·Ð° кÑÐ°Ð¶Ñ ÐºÐ¾Ð¼Ð¿Ð°ÐºÑ-диÑка, емÑ,
возможно, пÑидеÑÑÑ Ð¿Ð¾Ð´Ð¾Ð¶Ð´Ð°ÑÑ, когда
+его вÑпÑÑÑÑÑ Ð½Ð° ÑвободÑ, ÑÑÐ¾Ð±Ñ Ð¸Ð¼ÐµÑÑ
возможноÑÑÑ Ð´ÐµÐ»Ð°ÑÑ ÑÑо.
+<p>
+ÐÑли веÑÑиÑ, о коÑоÑой Ð¸Ð´ÐµÑ ÑеÑÑ, не
опÑбликована, и пÑедпÑиÑÑие ÑÑиÑÐ°ÐµÑ ÐµÐµ
+Ñвоей коммеÑÑеÑкой Ñайной, Ñо пÑбликаÑиÑ
Ð¼Ð¾Ð¶ÐµÑ Ð±ÑÑÑ Ð½Ð°ÑÑÑением закона о
+коммеÑÑеÑкой Ñайне, в завиÑимоÑÑи оÑ
дÑÑгиÑ
обÑÑоÑÑелÑÑÑв. GPL ÑÑого не
+оÑменÑеÑ. ÐÑли Ð±Ñ Ð¿ÑедпÑиÑÑие пÑÑалоÑÑ
вÑпÑÑÑиÑÑ ÑÐ²Ð¾Ñ Ð²ÐµÑÑÐ¸Ñ Ð¸ Ñем не менее
+оÑноÑиÑÑÑÑ Ðº ней как к коммеÑÑеÑкой Ñайне,
Ñо ÑÑо бÑло Ð±Ñ Ð½Ð°ÑÑÑением GPL, но
+еÑли пÑедпÑиÑÑие ÑÑÑ Ð²ÐµÑÑÐ¸Ñ Ð½Ðµ вÑпÑÑÑило,
Ñо Ñакого наÑÑÑÐµÐ½Ð¸Ñ Ð½Ðµ бÑло.
+</p></dd>
+
+<dt><a href="#TradeSecretRelease" name="TradeSecretRelease">ЧÑо, еÑли
+пÑедпÑиÑÑие пеÑÐµÐ´Ð°ÐµÑ ÐºÐ¾Ð¿Ð¸Ñ ÐºÐ°Ðº
коммеÑÑеÑкÑÑ ÑайнÑ?</a></dt>
+<dd>
+ÐÑли пÑедпÑиÑÑие пеÑÐµÐ´Ð°ÐµÑ Ð²Ð°Ð¼ ÐºÐ¾Ð¿Ð¸Ñ Ð¸
заÑвлÑеÑ, ÑÑо она ÑвлÑеÑÑÑ
+коммеÑÑеÑкой Ñайной, ÑÑо пÑедпÑиÑÑие
наÑÑÑило GPL и должно бÑÐ´ÐµÑ Ð¿ÑекÑаÑиÑÑ
+ÑаÑпÑоÑÑÑанение. ÐбÑаÑиÑе внимание, ÑÑо
ÑÑо оÑлиÑаеÑÑÑ Ð¾Ñ Ð¿ÑедÑдÑÑего ÑлÑÑаÑ
+Ñ ÐºÑажей: пÑедпÑиÑÑие не ÑаÑпÑоÑÑÑанÑеÑ
ÐºÐ¾Ð¿Ð¸Ñ Ð¿ÑеднамеÑенно, когда ее
+кÑадÑÑ, Ñак ÑÑо в ÑÑом ÑлÑÑае пÑедпÑиÑÑие
не наÑÑÑÐ°ÐµÑ GPL.
+<p></p></dd>
+
+<dt><a href="#WhySomeGPLAndNotLGPL" name="WhySomeGPLAndNotLGPL">ÐоÑемÑ
некоÑоÑÑе
+библиоÑеки GNU вÑпÑÑкаÑÑÑÑ Ð¿Ð¾ обÑÑной GPL, а
не по ÐенÑÑей GPL?</a></dt>
+
+<dd>
+ÐÑименение ÐенÑÑей GPL Ð´Ð»Ñ Ð»Ñбой конкÑеÑной
библиоÑеки ÑвлÑеÑÑÑ Ð¾ÑÑÑÑплением
+Ð¾Ñ Ð¿ÑинÑипов Ñвободного пÑогÑаммного
обеÑпеÑениÑ. ÐÑо знаÑиÑ, ÑÑо мÑ
+ÑаÑÑиÑно оÑбÑаÑÑваем ÑÑÐ¸Ð»Ð¸Ñ Ð·Ð°ÑиÑиÑÑ
ÑÐ²Ð¾Ð±Ð¾Ð´Ñ Ð¿Ð¾Ð»ÑзоваÑелей и некоÑоÑÑе из
+ÑÑебований по возвÑаÑÐµÐ½Ð¸Ñ Ñого, ÑÑо
вÑÑÑÑоено повеÑÑ
пÑогÑамм под GPL. Сами
+по Ñебе ÑÑо Ð¸Ð·Ð¼ÐµÐ½ÐµÐ½Ð¸Ñ Ðº Ñ
ÑдÑемÑ.
+<p>
+Ðногда меÑÑное оÑÑÑÑпление ÑÑÑаÑегиÑеÑки
вÑгодно. Ðногда пÑименение LGPL длÑ
+библиоÑеки могло Ð±Ñ Ð¿ÑивеÑÑи к более
ÑиÑÐ¾ÐºÐ¾Ð¼Ñ Ð¿ÑÐ¸Ð¼ÐµÐ½ÐµÐ½Ð¸Ñ ÑÑой библиоÑеки и,
+Ñаким обÑазом, болÑÑÐµÐ¼Ñ ÑиÑÐ»Ñ ÑлÑÑÑений в
ней, более ÑиÑокой поддеÑжке
+ÑвободнÑÑ
пÑогÑамм и Ñак далее. ÐÑо могло
Ð±Ñ Ð±ÑÑÑ Ð¿Ð¾Ð»ÐµÐ·Ð½Ð¾ Ð´Ð»Ñ ÑвободнÑÑ
+пÑогÑамм, еÑли ÑÑо пÑоиÑÑ
Ð¾Ð´Ð¸Ñ Ð² ÑиÑокиÑ
маÑÑÑабаÑ
. Ðо наÑколÑко они бÑдÑÑ
+ÑиÑоки? Ðожно ÑолÑко гадаÑÑ.</p>
+<p>
+ÐÑло Ð±Ñ Ñ
оÑоÑо опÑобоваÑÑ Ð½Ð° коÑоÑкое
вÑÐµÐ¼Ñ LGPL Ð´Ð»Ñ ÐºÐ°Ð¶Ð´Ð¾Ð¹ библиоÑеки,
+поÑмоÑÑеÑÑ, Ð¿Ð¾Ð¼Ð¾Ð³Ð°ÐµÑ Ð»Ð¸ ÑÑо, и веÑнÑÑÑÑÑ Ðº
GPL, еÑли неÑ. Ðо ÑÑо
+неÑеалÑно. ÐоÑле Ñого, как Ð¼Ñ Ð¿Ñименили LGPL
Ð´Ð»Ñ ÐºÐ¾Ð½ÐºÑеÑной библиоÑеки,
+веÑнÑÑÑÑÑ Ð½Ð°Ð·Ð°Ð´ ÑÑÑдно.</p>
+<p>
+ÐÑак, Ð¼Ñ ÑеÑаем, какÑÑ Ð»Ð¸ÑÐµÐ½Ð·Ð¸Ñ Ð¿ÑименÑÑÑ,
оÑделÑно Ð´Ð»Ñ ÐºÐ°Ð¶Ð´Ð¾Ð¹
+библиоÑеки. ÐÑÑÑ <a
href="/licenses/why-not-lgpl.html">длинное
+обÑÑÑнение</a> Ñого, как Ð¼Ñ Ð¿Ñинимаем
ÑеÑение по ÑÑÐ¾Ð¼Ñ Ð²Ð¾Ð¿ÑоÑÑ.
+</p></dd>
+
+<dt><a href="#WillYouMakeAnException"
name="WillYouMakeAnException">ÐÑименение
+опÑеделенной пÑогÑÐ°Ð¼Ð¼Ñ GNU под GPL не
ÑкладÑваеÑÑÑ Ð² Ð½Ð°Ñ Ð¿ÑÐ¾ÐµÐºÑ Ð¿Ð¾ ÑозданиÑ
+неÑвободнÑÑ
пÑогÑамм. Ðе ÑделаеÑе ли вÑ
Ð´Ð»Ñ Ð½Ð°Ñ Ð¸ÑклÑÑениÑ? ÐÑо ознаÑало вÑ
+болÑÑее ÑиÑло полÑзоваÑелей ÑÑой
пÑогÑаммÑ.</a></dt>
+
+<dd>
+ÐÑоÑÑиÑе, Ð¼Ñ Ð½Ðµ делаем ÑакиÑ
иÑклÑÑений.
ÐÑо бÑло Ð±Ñ Ð½ÐµÐ¿ÑавилÑно.
+<p>
+ÐакÑимизаÑÐ¸Ñ ÑиÑла полÑзоваÑелей не
ÑвлÑеÑÑÑ Ð½Ð°Ñей ÑелÑÑ. ÐмеÑÑо ÑÑого мÑ
+пÑÑаемÑÑ Ð´Ð°ÑÑ Ð¶Ð¸Ð·Ð½ÐµÐ½Ð½Ð¾ важнÑе ÑÐ²Ð¾Ð±Ð¾Ð´Ñ ÐºÐ°Ðº
можно болÑÑÐµÐ¼Ñ ÑиÑлÑ
+полÑзоваÑелей. ÐовоÑÑ Ð²Ð¾Ð¾Ð±Ñе, пÑоекÑÑ Ð¿Ð¾
ÑÐ¾Ð·Ð´Ð°Ð½Ð¸Ñ Ð½ÐµÑвободнÑÑ
пÑогÑамм
+меÑаÑÑ, а не помогаÑÑ Ð´ÐµÐ»Ñ ÑвободÑ.</p>
+<p>
+Ðногда Ð¼Ñ Ð´ÐµÐ¹ÑÑвиÑелÑно делаем иÑклÑÑениÑ
в лиÑензиÑÑ
, ÑÑÐ¾Ð±Ñ Ð¿Ð¾Ð´Ð´ÐµÑжаÑÑ
+пÑоекÑ, коÑоÑÑй пÑÐ¾Ð¸Ð·Ð²Ð¾Ð´Ð¸Ñ ÑвободнÑе
пÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ лиÑензией, оÑлиÑной оÑ
+GPL. Ðднако Ð´Ð»Ñ ÑÑого Ñ Ð½Ð°Ñ Ð´Ð¾Ð»Ð¶ÐµÐ½ бÑÑÑ
веÑкий довод в полÑÐ·Ñ Ñого, ÑÑо ÑÑо
+бÑÐ´ÐµÑ ÑодейÑÑвоваÑÑ Ð´ÐµÐ»Ñ ÑвободÑ
пÑогÑамм.</p>
+<p>
+Ðногда Ð¼Ñ Ñакже дейÑÑвиÑелÑно изменÑем
ÑÑÐ»Ð¾Ð²Ð¸Ñ ÑаÑпÑоÑÑÑÐ°Ð½ÐµÐ½Ð¸Ñ Ð¿Ð°ÐºÐµÑа, когда
+оказÑваеÑÑÑ ÑÑно, ÑÑо именно Ñак ÑледÑеÑ
ÑлÑжиÑÑ Ð´ÐµÐ»Ñ ÑÐ²Ð¾Ð±Ð¾Ð´Ñ Ð¿ÑогÑамм; но
+Ð¼Ñ Ð´ÐµÐ»Ð°ÐµÐ¼ ÑÑо Ñ Ð±Ð¾Ð»ÑÑими
пÑедоÑÑоÑожноÑÑÑми, Ñак ÑÑо вам нÑжно бÑдеÑ
+пÑедÑÑвиÑÑ Ð½Ð°Ð¼ оÑÐµÐ½Ñ ÑбедиÑелÑнÑе доводÑ.
+</p></dd>
+
+<dt><a href="#VersionThreeOrLater" name="VersionTwoOrLater">ÐоÑÐµÐ¼Ñ Ð²
пÑогÑаммаÑ
+должно бÑÑÑ Ñказано “веÑÑÐ¸Ñ 2 GPL или
лÑÐ±Ð°Ñ Ð±Ð¾Ð»ÐµÐµ позднÑÑ
+веÑÑиє?</a></dt>
+
+<dd>
+ÐÑÐµÐ¼Ñ Ð¾Ñ Ð²Ñемени, Ñ Ð¸Ð½ÑеÑвалом в неÑколÑко
леÑ, Ð²Ñ Ð²Ð½Ð¾Ñим Ð¸Ð·Ð¼ÐµÐ½ÐµÐ½Ð¸Ñ Ð²
+GPL — иногда Ð´Ð»Ñ Ð¿Ð¾ÑÑÐ½ÐµÐ½Ð¸Ñ ÐµÐµ, иногда
Ð´Ð»Ñ ÑазÑеÑениÑ
+опÑеделенного Ñода пÑименений, Ñанее не
ÑазÑеÑеннÑÑ
, а иногда Ð´Ð»Ñ ÑÑилениÑ
+ÑÑебований. (ÐоÑледнее изменение бÑло в
1991 годÑ.) ÐÑименение ÑÑого
+“коÑвенного ÑказаÑелє в каждой
пÑогÑамме Ð´ÐµÐ»Ð°ÐµÑ Ð²Ð¾Ð·Ð¼Ð¾Ð¶Ð½Ñм длÑ
+Ð½Ð°Ñ Ð¸Ð·Ð¼ÐµÐ½ÑÑÑ ÑÑÐ»Ð¾Ð²Ð¸Ñ ÑаÑпÑоÑÑÑанениÑ
вÑего ÑобÑÐ°Ð½Ð¸Ñ Ð¿ÑогÑамм GNU, когда мÑ
+обновлÑем GPL.
+<p>
+ÐÑли Ð±Ñ Ð² каждой пÑогÑамме оÑÑÑÑÑÑвовал
коÑвеннÑй ÑказаÑелÑ, Ð¼Ñ Ð±Ñли бÑ
+вÑнÑÐ¶Ð´ÐµÐ½Ñ Ð¾Ð±ÑÑждаÑÑ ÐºÐ°Ð¶Ð´Ð¾Ðµ изменение по
полной пÑогÑамме Ñ Ð¼Ð½Ð¾Ð³Ð¾ÑиÑленнÑми
+пÑавообладаÑелÑми, ÑÑо бÑло Ð±Ñ ÑакÑиÑеÑки
невозможно. Ðа пÑакÑике не бÑло бÑ
+никакой возможноÑÑи полÑÑиÑÑ
ÑниÑиÑиÑованнÑе ÑÑÐ»Ð¾Ð²Ð¸Ñ ÑаÑпÑоÑÑÑанениÑ
длÑ
+пÑогÑамм GNU.</p>
+<p>
+ÐÑедположим, в пÑогÑамме Ñказано
“веÑÑÐ¸Ñ 2 GPL или лÑÐ±Ð°Ñ Ð±Ð¾Ð»ÐµÐµ
+позднÑÑ Ð²ÐµÑÑиє, и вÑпÑÑкаеÑÑÑ Ð½Ð¾Ð²Ð°Ñ
веÑÑÐ¸Ñ GPL. ÐÑли Ð½Ð¾Ð²Ð°Ñ Ð²ÐµÑÑÐ¸Ñ GPL
+Ð´Ð°ÐµÑ Ð´Ð¾Ð¿Ð¾Ð»Ð½Ð¸ÑелÑное ÑазÑеÑение, ÑÑо
ÑазÑеÑение бÑÐ´ÐµÑ Ð½ÐµÐ¼ÐµÐ´Ð»ÐµÐ½Ð½Ð¾ доÑÑÑпно
+вÑем полÑзоваÑелÑм пÑогÑаммÑ. Ðо еÑли в
новой веÑÑии GPL еÑÑÑ Ð±Ð¾Ð»ÐµÐµ жеÑÑкое
+ÑÑебование, оно не огÑаниÑÐ¸Ñ Ð¿Ñименение
ÑекÑÑей веÑÑии пÑогÑаммÑ, поÑÐ¾Ð¼Ñ ÑÑо
+ее по-пÑÐµÐ¶Ð½ÐµÐ¼Ñ Ð¼Ð¾Ð¶Ð½Ð¾ бÑÐ´ÐµÑ Ð¸ÑполÑзоваÑÑ Ð½Ð°
ÑÑловиÑÑ
веÑÑии 2 GPL. Ðогда
+в пÑогÑамме Ñказано “веÑÑÐ¸Ñ 2 GPL или
лÑÐ±Ð°Ñ Ð±Ð¾Ð»ÐµÐµ позднÑÑ
+веÑÑиє, полÑзоваÑелÑм вÑегда бÑдеÑ
ÑазÑеÑено пÑименÑÑÑ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð¸
+даже изменÑÑÑ ÐµÐµ в ÑооÑвеÑÑÑвии Ñ
ÑÑебованиÑми веÑÑии 2
+GPL — даже поÑле Ñого, как ÑÑанÑÑ
доÑÑÑÐ¿Ð½Ñ Ð±Ð¾Ð»ÐµÐµ поздние веÑÑии.</p>
+<p>
+ÐÑли пÑимениÑелÑно к ÑÑÑеÑÑвÑÑÑим
пÑогÑаммам более жеÑÑкое ÑÑебование в
+новой веÑÑии GPL ÑоблÑдаÑÑ Ð½Ðµ обÑзаÑелÑно,
Ñо ÐºÐ°ÐºÐ°Ñ Ð¾Ñ ÑÑого полÑза? Ðак
+ÑолÑко ÑÑÐ°Ð½ÐµÑ Ð´Ð¾ÑÑÑпной веÑÑÐ¸Ñ 3 GPL,
ÑазÑабоÑÑики болÑÑинÑÑва пÑогÑамм
+под GPL вÑпÑÑÑÑÑ Ð¾ÑеÑеднÑе веÑÑии ÑвоиÑ
пÑогÑамм Ñ Ñказанием
+“веÑÑÐ¸Ñ 3 GPL или лÑÐ±Ð°Ñ Ð±Ð¾Ð»ÐµÐµ позднÑÑ
веÑÑиє. Тогда
+полÑзоваÑелÑм пÑидеÑÑÑ ÑледоваÑÑ Ð±Ð¾Ð»ÐµÐµ
жеÑÑким ÑÑебованиÑм веÑÑии 3 GPL
+в оÑноÑении к поÑледÑÑÑим веÑÑиÑм
пÑогÑаммÑ.</p>
+<p>
+Ðднако ÑазÑабоÑÑики не обÑÐ·Ð°Ð½Ñ Ð´ÐµÐ»Ð°ÑÑ ÑÑо;
ÑазÑабоÑÑики могÑÑ Ð¿ÑодолжиÑÑ
+ÑазÑеÑаÑÑ Ð¿Ð¾Ð»ÑзоваÑÑÑÑ Ð¿ÑедÑдÑÑей
веÑÑией GPL, еÑли Ð´Ð»Ñ Ð½Ð¸Ñ
ÑÑо
+пÑедпоÑÑиÑелÑно.
+</p></dd>
+
+
+<dt><a href="#WhyNotGPLForManuals" name="WhyNotGPLForManuals">ÐоÑемÑ
Ð²Ñ Ð½Ðµ
+пÑименÑеÑе GPL Ð´Ð»Ñ ÑÑководÑÑв?</a></dt>
+
+<dd>
+ÐÐ»Ñ ÑÑководÑÑва GPL пÑименÑÑÑ Ð¼Ð¾Ð¶Ð½Ð¾, но
ÐиÑÐµÐ½Ð·Ð¸Ñ Ñвободной докÑменÑаÑии GNU
+(GFDL) Ð´Ð»Ñ Ð½Ð¸Ñ
гоÑаздо лÑÑÑе.
+<p>
+GPL бÑла ÑоÑÑавлена Ð´Ð»Ñ Ð¿ÑогÑамм; она
ÑодеÑÐ¶Ð¸Ñ Ð¼Ð½Ð¾Ð¶ÐµÑÑво ÑложнÑÑ
пÑнкÑов,
+коÑоÑÑе жизненно Ð²Ð°Ð¶Ð½Ñ Ð´Ð»Ñ Ð¿ÑогÑамм, но
бÑли Ð±Ñ Ð¾Ð±ÑемениÑелÑÐ½Ñ Ð¸ не нÑжнÑ
+Ð´Ð»Ñ ÐºÐ½Ð¸Ð³Ð¸ или ÑÑководÑÑва. ÐапÑимеÑ,
каждÑй пÑбликÑÑÑий ÐºÐ½Ð¸Ð³Ñ Ð¸Ð»Ð¸ ÑÑаÑÑÑ
+должен бÑл Ð±Ñ Ð»Ð¸Ð±Ð¾ поÑÑавлÑÑÑ “иÑÑ
однÑй
ÑекÑÑ” книги на маÑинном
+ноÑиÑеле Ñ ÐºÐ°Ð¶Ð´Ð¾Ð¹ ÑипогÑаÑÑкой копией,
либо пÑедоÑÑавлÑÑÑ Ð¿Ð¸ÑÑменное
+пÑедложение вÑÑлаÑÑ “иÑÑ
однÑй
ÑекÑÑ” позднее.</p>
+<p>
+Ð Ñо же вÑÐµÐ¼Ñ Ð² GFDL еÑÑÑ Ð¿ÑнкÑÑ, коÑоÑÑе
помогаÑÑ Ð¸Ð·Ð´Ð°ÑелÑм ÑвободнÑÑ
+ÑÑководÑÑв полÑÑаÑÑ Ð²ÑÐ³Ð¾Ð´Ñ Ð¾Ñ Ð¿Ñодажи
копий — ÑекÑÑÑ Ð´Ð»Ñ Ð¾Ð±Ð»Ð¾Ð¶ÐºÐ¸,
+напÑимеÑ. ÐÑобÑе пÑавила о “ÑазделаÑ
одобÑений” позволÑÑÑ
+пÑименÑÑÑ GFDL Ð´Ð»Ñ Ð¾ÑиÑиалÑного ÑÑандаÑÑа. Ð
ÑÑом ÑлÑÑае измененнÑе веÑÑии
+бÑли Ð±Ñ ÑазÑеÑенÑ, но иÑ
нелÑÐ·Ñ Ð±Ñло бÑ
оÑмеÑаÑÑ ÐºÐ°Ðº “ÑÑандаÑÑ”.</p>
+<p>
+ÐÑполÑзÑÑ GFDL, Ð¼Ñ ÑазÑеÑаем изменÑÑÑ ÑекÑÑ
ÑÑководÑÑва, коÑоÑÑй оÑноÑиÑÑÑ Ðº
+его ÑеÑ
ниÑеÑкой ÑÑоÑоне. Ðажно имеÑÑ
возможноÑÑÑ Ð¸Ð·Ð¼ÐµÐ½ÑÑÑ ÑеÑ
ниÑеÑкие ÑаÑÑи,
+поÑÐ¾Ð¼Ñ ÑÑо Ñе, кÑо изменÑÐµÑ Ð¿ÑогÑаммÑ,
Ð´Ð¾Ð»Ð¶Ð½Ñ ÑооÑвеÑÑÑвенно изменÑÑÑ
+докÑменÑаÑиÑ. Свобода делаÑÑ ÑÑо —
ÑÑиÑеÑкий импеÑаÑив.</p>
+<p>
+ÐаÑи ÑÑководÑÑва вклÑÑаÑÑ Ñакже ÑазделÑ,
коÑоÑÑе пÑовозглаÑаÑÑ Ð½Ð°ÑÑ
+полиÑиÑеÑкÑÑ Ð¿Ð¾Ð·Ð¸ÑÐ¸Ñ Ð² оÑноÑении
Ñвободного пÑогÑаммного обеÑпеÑениÑ. ÐÑ
+оÑмеÑаем иÑ
как “неизменнÑе”, Ñак ÑÑо
иÑ
нелÑÐ·Ñ Ð¼Ð¾Ð´Ð¸ÑиÑиÑоваÑÑ
+или ÑдалÑÑÑ. Ð GFDL ÑоздаÑÑÑÑ ÑÑÐ»Ð¾Ð²Ð¸Ñ Ð´Ð»Ñ
ÑакиÑ
“неизменнÑÑ
+Ñазделов”.
+</p></dd>
+
+
+<dt><a href="#FontException" name="FontException">ÐÑименима ли GPL
к
+ÑÑиÑÑам?</a></dt>
+
+<dd>
+ÐиÑензиÑование ÑÑиÑÑов — ÑложнÑй
вопÑоÑ, коÑоÑÑй ÑÑебÑеÑ
+ÑеÑÑезного ÑаÑÑмоÑÑениÑ. ÐÑ Ð¿Ñиводим
ÑкÑпеÑименÑалÑное, но одобÑенное длÑ
+обÑего пÑÐ¸Ð¼ÐµÐ½ÐµÐ½Ð¸Ñ Ð»Ð¸Ñензионное
иÑклÑÑение. ÐÑ Ð±Ñдем ÑÐ°Ð´Ñ Ð¿ÑедложениÑм на
ÑÑÑ
+ÑÐµÐ¼Ñ — пожалÑйÑÑа, пÑоÑÑиÑе ÑÑÐ¾Ñ <a
+href="http://www.fsf.org/blogs/licensing/20050425novalis";>ÑазÑÑÑниÑелÑнÑй
+оÑеÑк</a> и напиÑиÑе по адÑеÑÑ: <a
+href="mailto:address@hidden";><address@hidden></a>.
+
+<p>
+ЧÑÐ¾Ð±Ñ Ð¸ÑполÑзоваÑÑ ÑÑо иÑклÑÑение,
добавÑÑе ÑÑÐ¾Ñ ÑекÑÑ Ðº замеÑÐ°Ð½Ð¸Ñ Ð¾
+лиÑензии в каждÑй Ñайл пакеÑа (по
возможноÑÑи) в конÑе ÑекÑÑа, где говоÑиÑÑÑ
+о Ñом, ÑÑо Ñайл ÑаÑпÑоÑÑÑанÑеÑÑÑ Ð¿Ð¾ GNU GPL:</p>
+<p>
+Ðак оÑобое иÑклÑÑение, еÑли Ð²Ñ ÑоздаеÑе
докÑменÑ, коÑоÑÑй полÑзÑеÑÑÑ ÑÑим
+ÑÑиÑÑом, и вÑÑÑаиваеÑе ÑÑÐ¾Ñ ÑÑиÑÑ Ð¸Ð»Ð¸
неизмененнÑе ÑаÑÑи ÑÑого ÑÑиÑÑа в ÑÑоÑ
+докÑменÑ, ÑÑÐ¾Ñ ÑÑиÑÑ Ñам по Ñебе не
пÑÐ¸Ð²Ð¾Ð´Ð¸Ñ Ðº ÑомÑ, ÑÑо на полÑÑаÑÑийÑÑ Ð²
+ÑезÑлÑÑаÑе докÑÐ¼ÐµÐ½Ñ ÑаÑпÑоÑÑÑанÑеÑÑÑ
СÑандаÑÑÐ½Ð°Ñ Ð¾Ð±ÑеÑÑÐ²ÐµÐ½Ð½Ð°Ñ Ð»Ð¸ÑензиÑ
+GNU. ÐÑли Ð²Ñ Ð¸Ð·Ð¼ÐµÐ½ÑеÑе ÑÑÐ¾Ñ ÑÑиÑÑ, Ð²Ñ Ð¼Ð¾Ð¶ÐµÑе
ÑаÑпÑоÑÑÑаниÑÑ ÑÑо иÑклÑÑение
+на ваÑÑ Ð²ÐµÑÑÐ¸Ñ ÑÑиÑÑа, но Ð²Ñ Ð½Ðµ обÑÐ·Ð°Ð½Ñ ÑÑо
делаÑÑ. ÐÑли Ð²Ñ Ð½Ðµ желаеÑе
+делаÑÑ ÑÑо, ÑдалиÑе замеÑание об ÑÑом
иÑклÑÑении из ваÑей веÑÑии.
+</p></dd>
+
+
+<dt><a href="#TOCWMS" name="WMS">Я пиÑÑ ÑиÑÑÐµÐ¼Ñ Ð¿Ð¾Ð´Ð´ÐµÑжки
ÑайÑа</a> (назÑваемÑÑ
+некоÑоÑÑми “<a
href="/philosophy/words-to-avoid.html">ÑиÑÑемой
+ÑпÑÐ°Ð²Ð»ÐµÐ½Ð¸Ñ ÐºÐ¾Ð½ÑенÑом</a>”) или какое-Ñо
дÑÑгое пÑиложение, ÑоздаÑÑее
+ÑÑÑаниÑÑ Ð´Ð»Ñ ÑайÑа из Ñаблонов. ÐакÑÑ
лиÑÐµÐ½Ð·Ð¸Ñ Ð¼Ð½Ðµ иÑполÑзоваÑÑ Ð´Ð»Ñ ÑÑиÑ
+Ñаблонов?</dt>
+
+<dd>
+<p>ÐнаÑение Ñаблонов доÑÑаÑоÑно мало, ÑÑобÑ
не бÑло ÑмÑÑла пÑименÑÑÑ Ð°Ð²ÑоÑÑкое
+лево Ð´Ð»Ñ Ð¸Ñ
заÑиÑÑ. Ðак пÑавило, пÑименение
авÑоÑÑкого лева Ð´Ð»Ñ Ð½ÐµÐ±Ð¾Ð»ÑÑиÑ
+ÑÐ°Ð±Ð¾Ñ Ð±ÐµÐ·Ð²Ñедно, но ÑÐ°Ð±Ð»Ð¾Ð½Ñ — ÑлÑÑай
оÑобÑй, поÑÐ¾Ð¼Ñ ÑÑо они
+комбиниÑÑÑÑÑÑ Ñ Ð´Ð°Ð½Ð½Ñми, пÑедоÑÑавлÑемÑми
полÑзоваÑелем пÑиложениÑ, и
+ÑаÑпÑоÑÑÑанÑеÑÑÑ ÑÑа комбинаÑиÑ. ÐоÑÑомÑ
Ð¼Ñ ÑекомендÑем вам лиÑензиÑоваÑÑ
+Ñвои ÑÐ°Ð±Ð»Ð¾Ð½Ñ Ð½Ð° пÑоÑÑÑÑ
неогÑаниÑиÑелÑнÑÑ
ÑÑловиÑÑ
. </p>
+
+<p>Ðз некоÑоÑÑÑ
Ñаблонов вÑзÑваÑÑÑÑ
ÑÑнкÑии на ÑзÑке Javascript. ÐоÑколÑкÑ
+пÑогÑÐ°Ð¼Ð¼Ñ Ð½Ð° Javascript ÑаÑÑо неÑÑивиалÑнÑ, длÑ
ниÑ
Ð¸Ð¼ÐµÐµÑ ÑмÑÑл пÑименÑÑÑ
+авÑоÑÑкое лево. ÐоÑколÑÐºÑ ÑÐ°Ð±Ð»Ð¾Ð½Ñ Ð±ÑдÑÑ
комбиниÑоваÑÑÑÑ Ñ Ð´Ð°Ð½Ð½Ñми
+полÑзоваÑелÑ, возможно, ÑÑо
<em>ÑаблонÑ+даннÑе полÑзоваÑелÑ+Javascript</em>
+бÑдÑÑ ÑÑиÑаÑÑÑÑ ÐµÐ´Ð¸Ð½Ð¾Ð¹ ÑабоÑой Ñ ÑоÑки
зÑÐµÐ½Ð¸Ñ Ð°Ð²ÑоÑÑкого пÑава. ÐеобÑ
одимо
+пÑовеÑÑи ÑеÑÑÑ Ð¼ÐµÐ¶Ð´Ñ Ð¿ÑогÑаммами на Javascript
(Ñ Ð°Ð²ÑоÑÑким левом) и ÑекÑÑом
+полÑзоваÑÐµÐ»Ñ (обÑÑно под неÑовмеÑÑимÑми
ÑÑловиÑми). </p>
+
+<p><a href="/licenses/template-diagram.png"><img
src="/licenses/template-diagram.png" alt="СÑ
ема опиÑанного
вÑÑе" /></a></p>
+
+<p>ÐÐ¾Ñ Ð¸ÑклÑÑение Ð´Ð»Ñ Ð¿ÑогÑамм на Javascript,
коÑоÑое ÑÑо делаеÑ:</p>
+
+<blockquote><p>Ðак оÑобое иÑклÑÑение из GPL, лÑбой
Ñайл HTML, коÑоÑÑй пÑоÑÑо вÑзÑваеÑ
+ÑÑнкÑии из ÑÑой пÑогÑÐ°Ð¼Ð¼Ñ Ð¸ вклÑÑÐ°ÐµÑ ÐµÐµ в
ÑÑиÑ
ÑелÑÑ
поÑÑедÑÑвом ÑÑÑлки,
+должен ÑÑиÑаÑÑÑÑ Ð¾ÑделÑной ÑабоÑой Ñ
ÑоÑки зÑÐµÐ½Ð¸Ñ Ð°Ð²ÑоÑÑкого пÑава. Ð
+дополнение, пÑавообладаÑели ÑÑой
пÑогÑÐ°Ð¼Ð¼Ñ Ð´Ð°ÑÑ Ð²Ð°Ð¼ ÑазÑеÑение
комбиниÑоваÑÑ
+ÑекÑÑÑ ÑÑой пÑогÑÐ°Ð¼Ð¼Ñ Ñо ÑвободнÑми
библиоÑеками, вÑпÑÑкаемÑми под GNU
+LGPL. ÐÑ Ð¼Ð¾Ð¶ÐµÑе копиÑоваÑÑ Ð¸ ÑаÑпÑоÑÑÑанÑÑÑ
ÑакÑÑ ÑиÑÑемÑ, ÑледÑÑ
+ÑÑебованиÑм GNU GPL Ð´Ð»Ñ ÑекÑÑов ÑÑой
пÑогÑÐ°Ð¼Ð¼Ñ Ð¸ LGPL Ð´Ð»Ñ Ð±Ð¸Ð±Ð»Ð¸Ð¾Ñек. ÐÑли вÑ
+модиÑиÑиÑÑеÑе ÑÑÑ Ð¿ÑогÑаммÑ, Ð²Ñ Ð¼Ð¾Ð¶ÐµÑе
ÑаÑпÑоÑÑÑаниÑÑ ÑÑо иÑклÑÑение на ваÑÑ
+веÑÑÐ¸Ñ Ð¿ÑогÑаммÑ, но Ð²Ñ Ð½Ðµ обÑÐ·Ð°Ð½Ñ Ð´ÐµÐ»Ð°ÑÑ
ÑÑо. ÐÑли Ð²Ñ Ð½Ðµ желаеÑе ÑÑо
+делаÑÑ, ÑдалиÑе замеÑание об ÑÑом
иÑклÑÑении из Ñвоей веÑÑии.
+</p></blockquote>
+
+</dd>
+
+<dt><a href="#NonFreeTools" name="NonFreeTools">ÐÐ¾Ð³Ñ Ñ Ð²ÑпÑÑÑиÑÑ
пÑогÑаммÑ,
+коÑоÑÑÑ Ñ ÑазÑабоÑал Ñ Ð¿Ð¾Ð¼Ð¾ÑÑÑ Ð½ÐµÑвободнÑÑ
ÑÑедÑÑв, под GPL?</a></dt>
+
+<dd>
+То, Ñ Ð¿Ð¾Ð¼Ð¾ÑÑÑ ÐºÐ°ÐºÐ¸Ñ
пÑогÑамм Ð²Ñ Ð¿ÑивÑкли
ÑедакÑиÑоваÑÑ Ð¸ÑÑ
однÑй ÑекÑÑ,
+компилиÑоваÑÑ, иÑÑледоваÑÑ Ð¸Ð»Ð¸ запиÑÑваÑÑ
его, обÑÑно не Ð¸Ð¼ÐµÐµÑ Ð·Ð½Ð°ÑÐµÐ½Ð¸Ñ Ð´Ð»Ñ
+вопÑоÑов, ÑвÑзаннÑÑ
Ñ Ð»Ð¸ÑензиÑованием
ÑÑого иÑÑ
одного ÑекÑÑа.
+
+<p>
+Ðднако еÑли Ð²Ñ Ð¿Ð¾Ð´ÐºÐ»ÑÑаеÑе к иÑÑ
однÑм
ÑекÑÑам неÑвободнÑе библиоÑеки, ÑÑо
+бÑло Ð±Ñ Ð¿Ñоблемой, коÑоÑÑÑ Ð½ÐµÐ¾Ð±Ñ
одимо
ÑеÑиÑÑ. ÐÑо не иÑклÑÑÐ°ÐµÑ Ð²ÑпÑÑка
+иÑÑ
одного ÑекÑÑа под GPL, но еÑли библиоÑеки
не попадаÑÑ Ð¿Ð¾Ð´ иÑклÑÑение
+“ÑиÑÑемнÑÑ
библиоÑек”, вам нÑжно
добавиÑÑ Ñвное пÑимеÑание Ñ
+ÑазÑеÑением подклÑÑаÑÑ Ð¸Ñ
к ваÑей
пÑогÑамме. ФСÐÐ Ð¼Ð¾Ð¶ÐµÑ Ð²Ð°Ñ
+пÑоконÑÑлÑÑиÑоваÑÑ Ð¿Ð¾ ÑÑÐ¾Ð¼Ñ Ð²Ð¾Ð¿ÑоÑÑ.</p>
+</dd>
+
+
+<dt><a href="#GPLTranslations" name="GPLTranslations">СÑÑеÑÑвÑÑÑ
ли пеÑÐµÐ²Ð¾Ð´Ñ GPL
+на дÑÑгие ÑзÑки?</a></dt>
+
+<dd>
+ÐÑло Ð±Ñ Ð¿Ð¾Ð»ÐµÐ·Ð½Ð¾ имеÑÑ ÑекÑÑÑ GPL не ÑолÑко
на английÑком ÑзÑке. ÐеÑеводÑ
+даже делали и пÑиÑÑлали нам. Ðо Ð¼Ñ Ð½Ðµ
оÑмелилиÑÑ Ð¾Ð´Ð¾Ð±ÑиÑÑ Ð¸Ñ
как оÑиÑиалÑно
+дейÑÑвиÑелÑнÑе. ÐÑо ÑопÑÑжено Ñ ÑиÑком,
наÑÑолÑко болÑÑим, ÑÑо Ð¼Ñ Ð½Ðµ беÑем
+на ÑÐµÐ±Ñ ÑмелоÑÑÑ Ð¿ÑинÑÑÑ ÐµÐ³Ð¾.
+<p>
+ЮÑидиÑеÑкий докÑÐ¼ÐµÐ½Ñ Ð² некоÑоÑом ÑмÑÑле
подобен пÑогÑамме. ÐеÑевод его
+ÑÑ
оден Ñ Ð¿ÐµÑеводом пÑогÑÐ°Ð¼Ð¼Ñ Ñ Ð¾Ð´Ð½Ð¾Ð³Ð¾
ÑзÑка и опеÑаÑионной ÑиÑÑÐµÐ¼Ñ Ð½Ð°
+дÑÑгой. ÐÑо Ð¼Ð¾Ð¶ÐµÑ Ð´ÐµÐ»Ð°ÑÑ ÑолÑко ÑÑиÑÑ,
компеÑенÑнÑй в обоиÑ
+ÑзÑкаÑ
— и даже Ñогда еÑÑÑ Ð¾Ð¿Ð°ÑноÑÑÑ
внеÑÐµÐ½Ð¸Ñ Ð¾Ñибки.</p>
+<p>
+ÐÑли Ð±Ñ Ð¼Ñ ÑобиÑалиÑÑ Ð¾Ð´Ð¾Ð±ÑиÑÑ
(оÑиÑиалÑно) пеÑевод GPL, нам пÑиÑлоÑÑ Ð±Ñ
+пÑедоÑÑавиÑÑ Ð²Ñем ÑазÑеÑение на вÑе Ñо,
ÑÑо им ÑазÑеÑено в пеÑеводе. ÐÑли
+пеÑевод полноÑÑÑÑ ÑоÑен, ÑÑо не ÑÑÑаÑно. Ðо
еÑли в пеÑеводе еÑÑÑ Ð¾Ñибка,
+ÑезÑлÑÑаÑÑ Ð¼Ð¾Ð³Ð»Ð¸ Ð±Ñ Ð¿ÑивеÑÑи к каÑаÑÑÑоÑе,
поÑледÑÑвий коÑоÑой Ð¼Ñ Ð½Ðµ Ñмогли
+Ð±Ñ Ð¸ÑпÑавиÑÑ.</p>
+<p>
+ÐÑли в пÑогÑамме еÑÑÑ Ð¾Ñибка, Ð¼Ñ Ð¼Ð¾Ð¶ÐµÐ¼
вÑпÑÑÑиÑÑ Ð½Ð¾Ð²ÑÑ Ð²ÐµÑÑиÑ, и
+когда-нибÑÐ´Ñ ÑÑаÑÐ°Ñ Ð²ÐµÑÑÐ¸Ñ Ð±Ð¾Ð»ÐµÐµ или менее
иÑÑезнеÑ. Ðо поÑле Ñого, как мÑ
+дали вÑем ÑазÑеÑение дейÑÑвоваÑÑ Ð²
ÑооÑвеÑÑÑвии Ñ ÐºÐ¾Ð½ÐºÑеÑнÑм пеÑеводом, Ñ
+Ð½Ð°Ñ Ð½ÐµÑ ÑпоÑоба взÑÑÑ ÑазÑеÑение назад,
еÑли Ð¼Ñ Ð¾Ð±Ð½Ð°ÑÑжим, впоÑледÑÑвии, ÑÑо
+в нем бÑла оÑибка.</p>
+<p>
+ÐÑзÑвÑивÑе лÑди иногда пÑедлагаÑÑ
пÑоделаÑÑ ÑÑÑ ÑабоÑÑ Ð¿Ð¾ пеÑÐµÐ²Ð¾Ð´Ñ Ð´Ð»Ñ
+наÑ. ÐÑли Ð±Ñ Ð¿Ñоблема бÑла в Ñом, ÑÑобÑ
найÑи кого-нибÑдÑ, кÑо Ð±Ñ Ñделал
+ÑÑо, она бÑла Ð±Ñ ÑеÑена. Ðо в
дейÑÑвиÑелÑноÑÑи пÑоблема заклÑÑаеÑÑÑ Ð²
+возможноÑÑи оÑибки, и пÑедложение
пÑоделаÑÑ ÑÑÑ ÑабоÑÑ Ð½Ðµ ÑÐ½Ð¸Ð¼Ð°ÐµÑ ÑÑого
+ÑиÑка. ÐÑ Ð½Ðµ могли Ð±Ñ Ð¿ÑизнаÑÑ Ð¾ÑиÑиалÑнÑм
пеÑевод, ÑделаннÑй неÑÑиÑÑом.</p>
+<p>
+Таким обÑазом, в наÑÑоÑÑее вÑÐµÐ¼Ñ Ð¼Ñ Ð½Ðµ
обÑÑвлÑем пеÑеводов GPL глобалÑно
+дейÑÑвиÑелÑнÑми и обÑзÑваÑÑими. ÐмеÑÑо
ÑÑого Ð¼Ñ Ð´ÐµÐ»Ð°ÐµÐ¼ две веÑи:</p>
+<ul>
+<li> ÐÑÑÑлаем лÑдей к неоÑиÑиалÑнÑм
пеÑеводам. ÐÑо знаÑиÑ, ÑÑо Ð¼Ñ ÑазÑеÑаем
+делаÑÑ Ð¿ÐµÑÐµÐ²Ð¾Ð´Ñ GPL, но Ð¼Ñ Ð½Ðµ обÑÑвлÑем иÑ
ÑÑидиÑеÑки дейÑÑвиÑелÑнÑми и
+обÑзÑваÑÑими.
+<p>
+Такой пеÑевод не Ð¸Ð¼ÐµÐµÑ ÑÑидиÑеÑкой ÑилÑ, и
ÑÑо должно бÑÑÑ Ð² нем Ñвно
+Ñказано. Ðн должен бÑÑÑ Ð¿Ð¾Ð¼ÐµÑен Ñаким
обÑазом:</p>
+<pre>
+ ÐÑо неÑоÑмалÑнÑй пеÑевод GPL, он не бÑл
оÑиÑиалÑно одобÑен
+ Фондом Ñвободного пÑогÑаммного
обеÑпеÑÐµÐ½Ð¸Ñ ÐºÐ°Ðº дейÑÑвиÑелÑнÑй. ЧÑобÑ
+ полноÑÑÑÑ ÑдоÑÑовеÑиÑÑÑÑ Ð² Ñом, ÑÑо
ÑазÑеÑено, ÑвеÑÑÑеÑÑ
+ Ñ Ð¾ÑигиналÑнÑм ÑекÑÑом GPL (на английÑком).
+</pre>
+<p>
+Ðо неоÑиÑиалÑнÑй пеÑевод Ð¼Ð¾Ð¶ÐµÑ ÑлÑжиÑÑ
Ñказанием на Ñо, как ÑледÑÐµÑ Ð¿Ð¾Ð½Ð¸Ð¼Ð°ÑÑ
+английÑкÑÑ GPL. ÐÐ»Ñ Ð¼Ð½Ð¾Ð³Ð¸Ñ
полÑзоваÑелей
ÑÑого доÑÑаÑоÑно.</p>
+<p>
+Ðднако пÑедпÑиÑÑиÑ, пÑименÑÑÑие пÑогÑаммÑ
GNU в коммеÑÑеÑкой деÑÑелÑноÑÑи, и
+лÑди, занимаÑÑиеÑÑ Ð¿ÑблиÑнÑм
ÑаÑпÑоÑÑÑанением по FTP, Ð´Ð¾Ð»Ð¶Ð½Ñ Ð¾Ð±ÑзаÑелÑно
+ÑвеÑÑÑÑÑÑ Ñ Ð°Ð½Ð³Ð»Ð¸Ð¹Ñкой GPL, ÑÑÐ¾Ð±Ñ Ð±ÑÑÑ
ÑвеÑеннÑми в Ñом, ÑÑо именно она
+допÑÑкаеÑ.</p>
+</li>
+<li>
+ÐÑбликаÑÐ¸Ñ Ð¿ÐµÑеводов, дейÑÑвиÑелÑнÑÑ
ÑолÑко в одной ÑÑÑане.
+<p>
+ÐÑ Ð¾Ð±Ð´ÑмÑваем мÑÑÐ»Ñ Ð¾ пÑбликаÑии
пеÑеводов, коÑоÑÑе оÑиÑиалÑно
дейÑÑвиÑелÑнÑ
+ÑолÑко в одной ÑÑÑане. Таким обÑазом, еÑли
бÑÐ´ÐµÑ Ð¾Ñибка, ее поÑледÑÑвиÑ
+бÑдÑÑ Ð¾Ð³ÑаниÑÐµÐ½Ñ ÑÑой ÑÑÑаной, и ÑÑеÑб не
бÑÐ´ÐµÑ ÑлиÑком велик.</p>
+<p>
+Создание пеÑевода вÑе-Ñаки поÑÑебÑеÑ
знаÑиÑелÑного опÑÑа и ÑÑÑда
+ÑоÑÑвÑÑвÑÑÑего и ÑпоÑобного ÑÑиÑÑа, Ñак
ÑÑо Ð¼Ñ Ð½Ðµ можем обеÑаÑÑ ÑкоÑого
+поÑÐ²Ð»ÐµÐ½Ð¸Ñ ÑакиÑ
пеÑеводов.</p>
+</li>
+</ul>
+<p></p></dd>
+
+<dt><a href="#InterpreterIncompat" name="InterpreterIncompat">ÐÑли
лиÑензиÑ
+инÑеÑпÑеÑаÑоÑа ÑзÑка пÑогÑаммиÑованиÑ
неÑовмеÑÑима Ñ GPL, Ð¼Ð¾Ð³Ñ Ð»Ð¸ Ñ
+вÑполнÑÑÑ Ð½Ð° нем пÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL?</a></dt>
+
+<dd>
+Ðогда инÑеÑпÑеÑаÑÐ¾Ñ ÑолÑко
инÑеÑпÑеÑиÑÑÐµÑ ÑзÑк, оÑÐ²ÐµÑ Ð¿Ð¾Ð»Ð¾Ð¶Ð¸Ñелен. ÐлÑ
+инÑеÑпÑеÑаÑоÑа инÑеÑпÑеÑиÑÑемаÑ
пÑогÑамма — ÑÑо пÑоÑÑо даннÑе;
+GPL не огÑаниÑÐ¸Ð²Ð°ÐµÑ Ñого, какими ÑÑедÑÑвами
Ð²Ñ Ð¾Ð±ÑабаÑÑваеÑе пÑогÑаммÑ.
+<p>
+Ðднако когда инÑеÑпÑеÑаÑÐ¾Ñ ÑаÑÑиÑÑеÑÑÑ,
ÑÑÐ¾Ð±Ñ Ð¿ÑедоÑÑавиÑÑ
+“пÑивÑзки” к дÑÑгим ÑÑедÑÑвам (ÑаÑÑо,
но не обÑзаÑелÑно, ÑÑо
+библиоÑеки), Ñо инÑеÑпÑеÑиÑÑемаÑ
пÑогÑамма ÑакÑиÑеÑки ÑвÑзÑваеÑÑÑ Ñо
+ÑÑедÑÑвами, коÑоÑÑми она полÑзÑеÑÑÑ Ñ
помоÑÑÑ ÑÑиÑ
пÑивÑзок. JNI (Java
+Native Interface) — пÑÐ¸Ð¼ÐµÑ Ñакого ÑÑедÑÑва;
библиоÑеки, доÑÑÑп к
+коÑоÑÑм оÑÑÑеÑÑвлÑеÑÑÑ Ñаким обÑазом,
динамиÑеÑки ÑвÑзÑваÑÑÑÑ Ñ Ð¿ÑогÑаммами
+на Java, коÑоÑÑе вÑзÑваÑÑ Ð¸Ñ
пÑоÑедÑÑÑ.</p>
+<p>
+ÐÑак, еÑли ÑÑи ÑÑедÑÑва вÑпÑÑкаÑÑÑÑ Ð¿Ð¾
неÑовмеÑÑимой Ñ GPL лиÑензии,
+ÑиÑÑаÑÐ¸Ñ Ð¿Ð¾Ð´Ð¾Ð±Ð½Ð° ÑÐ¾ÐµÐ´Ð¸Ð½ÐµÐ½Ð¸Ñ Ð»ÑбÑм дÑÑгим
ÑпоÑобом Ñ Ð±Ð¸Ð±Ð»Ð¸Ð¾Ñекой,
+неÑовмеÑÑимой Ñ GPL. ÐÑо подÑазÑмеваеÑ,
ÑÑо:</p>
+<ol>
+ <li>ÐÑли Ð²Ñ Ð¿Ð¸ÑеÑе пÑогÑÐ°Ð¼Ð¼Ñ Ð¸ вÑпÑÑкаеÑе
ее под GPL, Ð²Ñ Ð¼Ð¾Ð¶ÐµÑе ÑÑоÑмÑлиÑоваÑÑ
+Ñвное иÑклÑÑение, даÑÑее ÑазÑеÑение
ÑоединÑÑÑ ÐµÐµ Ñ ÑÑими неÑовмеÑÑимÑми Ñ
+GPL ÑÑедÑÑвами.</li>
+
+ <li>ÐÑли Ð²Ñ Ð½Ð°Ð¿Ð¸Ñали и вÑпÑÑÑили пÑогÑаммÑ
по GPL, и Ð²Ñ ÑоÑÑавили ее ÑпеÑиалÑно
+Ð´Ð»Ñ ÑабоÑÑ Ñ ÑÑими ÑÑедÑÑвами, лÑди могÑÑ
пÑинÑÑÑ ÑÑо как неÑвное
+иÑклÑÑение, ÑазÑеÑаÑÑее им ÑвÑзÑваÑÑ
пÑогÑÐ°Ð¼Ð¼Ñ Ñ ÑÑими ÑÑедÑÑвами. Ðо еÑли
+ваÑе намеÑение Ñаково, лÑÑÑе вÑÑазиÑÑ ÑÑо
Ñвно.</li>
+
+ <li>ÐÑ Ð½Ðµ можеÑе ни взÑÑÑ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ ÐºÐ¾Ð³Ð¾-Ñо
дÑÑгого, вÑпÑÑеннÑе под GPL, ни
+добавлÑÑÑ Ðº ним Ñакие иÑклÑÑениÑ.
ÐÑклÑÑение могÑÑ Ð´Ð¾Ð±Ð°Ð²Ð¸ÑÑ ÑолÑко
+пÑавообладаÑели ÑÑиÑ
пÑогÑамм.</li>
+</ol>
+<p></p></dd>
+
+<dt><a href="#WhoHasThePower" name="WhoHasThePower">ÐÑо впÑаве
ÑÑебоваÑÑ
+ÑоблÑÐ´ÐµÐ½Ð¸Ñ GPL?</a></dt>
+
+<dd>
+ÐоÑколÑÐºÑ GPL — лиÑензионнÑй договоÑ
на иÑполÑзование обÑекÑов
+авÑоÑÑкого пÑава, Ñо пÑавообладаÑели
пÑогÑÐ°Ð¼Ð¼Ñ — ÑÑо Ñе, кÑо
+впÑаве ÑÑебоваÑÑ ÑоблÑÐ´ÐµÐ½Ð¸Ñ GPL. ÐÑли вÑ
видиÑе наÑÑÑение GPL, вам ÑледÑеÑ
+инÑоÑмиÑоваÑÑ ÑазÑабоÑÑиков пÑогÑаммÑ, в
оÑноÑении коÑоÑой оно допÑÑено. Ðни
+либо ÑвлÑÑÑÑÑ Ð¿ÑавообладаÑелÑми, либо
ÑвÑÐ·Ð°Ð½Ñ Ñ Ð½Ð¸Ð¼Ð¸. <a
+href="#ReportingViolation">ÐодÑобнее о Ñом, как ÑÑо
делаÑÑ, опиÑано в оÑвеÑе
+на дÑÑгой вопÑоÑ.</a>
+<p></p></dd>
+
+
+<dt><a href="#OOPLang" name="OOPLang">ÐÑли в Ñаком
обÑекÑно-оÑиенÑиÑованном
+ÑзÑке, как Java, Ñ Ð¸ÑполÑзÑÑ ÐºÐ»Ð°ÑÑ Ð¿Ð¾Ð´ GPL без
изменений и обÑазÑÑ Ð¸Ð· него
+подклаÑÑ, каким обÑазом GPL влиÑÐµÑ Ð½Ð° более
кÑÑпнÑÑ Ð¿ÑогÑаммÑ?</a></dt>
+
+<dd>
+ÐбÑазование подклаÑÑа ÑвлÑеÑÑÑ Ñозданием
пÑоизводного
+пÑоизведениÑ. СледоваÑелÑно, ÑÑÐ»Ð¾Ð²Ð¸Ñ GPL
ÑаÑпÑоÑÑÑанÑÑÑÑÑ Ð½Ð° вÑÑ Ð¿ÑогÑаммÑ,
+в коÑоÑой Ð²Ñ ÑоздаеÑе подклаÑÑ ÐºÐ»Ð°ÑÑа под
GPL.
+<p></p></dd>
+
+<dt><a href="#PortProgramToGL" name="PortProgramToGL">ÐÑли Ñ
пеÑеноÑÑ ÑвоÑ
+пÑогÑÐ°Ð¼Ð¼Ñ Ð½Ð° GNU/Linux, знаÑÐ¸Ñ Ð»Ð¸ ÑÑо, ÑÑо мне
необÑ
одимо вÑпÑÑÑиÑÑ ÐµÐµ как
+ÑвободнÑÑ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL или дÑÑгой
лиÑензией ÑвободнÑÑ
пÑогÑамм?</a></dt>
+
+<dd>
+ÐообÑе говоÑÑ, Ð½ÐµÑ — ÑÑо не ÑвлÑеÑÑÑ
ÑÑидиÑеÑким ÑÑебованием. Ð
+конкÑеÑном ÑлÑÑае ÑÑо завиÑÐ¸Ñ Ð¾Ñ Ñого,
какими библиоÑеками Ð²Ñ Ñ
оÑиÑе
+полÑзоваÑÑÑÑ Ð¸ ÐºÐ°ÐºÐ¾Ð²Ñ Ð¸Ñ
лиÑензии.
ÐолÑÑинÑÑво ÑиÑÑемнÑÑ
библиоÑек
+иÑполÑзÑÑÑ Ð»Ð¸Ð±Ð¾ <a href="/copyleft/lesser.html">ÐенÑÑÑÑ
GPL</a>, либо GNU
+GPL Ñ Ð¸ÑклÑÑением, ÑазÑеÑаÑÑим Ñоединение
библиоÑеки Ñ Ñем Ñгодно. ÐÑи
+библиоÑеки можно пÑименÑÑÑ Ð² неÑвободнÑÑ
пÑогÑаммаÑ
; но в ÑлÑÑае Ñ ÐенÑÑей
+GPL некоÑоÑÑе ÑÑÐµÐ±Ð¾Ð²Ð°Ð½Ð¸Ñ Ð² лиÑензии еÑÑÑ, и
Ð²Ñ Ð´Ð¾Ð»Ð¶Ð½Ñ Ð¸Ð¼ ÑледоваÑÑ.
+<p>
+ÐекоÑоÑÑе библиоÑеки вÑпÑÑкаÑÑÑÑ ÑолÑко
по GNU GPL; Ð²Ñ Ð´Ð¾Ð»Ð¶Ð½Ñ Ð¿Ð¾Ð»ÑзоваÑÑÑÑ
+лиÑензией, ÑовмеÑÑимой Ñ GPL, ÑÑобÑ
пÑименÑÑÑ ÑÑи библиоÑеки. Ðо ÑÑо, как
+пÑавило, более ÑпеÑиализиÑованнÑе
библиоÑеки, и на дÑÑгой плаÑÑоÑме Ñ Ð²Ð°Ñ Ð½Ðµ
+бÑло Ð±Ñ Ð½Ð¸Ñего оÑÐµÐ½Ñ Ð¿Ð¾Ñ
ожего на ниÑ
, Ñак
ÑÑо Ð²Ñ Ð²ÑÑд ли заÑ
оÑиÑе пÑименÑÑÑ
+ÑÑи библиоÑеки, когда пÑоÑÑо пеÑеноÑиÑе
пÑогÑаммÑ.</p>
+<p>
+ÐонеÑно, ваÑа пÑогÑамма не Ð¿Ð¾Ð¹Ð´ÐµÑ Ð½Ð°
полÑÐ·Ñ Ð½Ð°ÑÐµÐ¼Ñ ÑообÑеÑÑвÑ, еÑли она не
+Ñвободна, и кÑо ÑÐµÐ½Ð¸Ñ ÑÐ²Ð¾Ñ ÑвободÑ,
оÑкажеÑÑÑ Ð¾Ñ Ð¿Ð¾Ð»ÑÐ·Ð¾Ð²Ð°Ð½Ð¸Ñ ÐµÑ. ТолÑко ÑоÑ,
+кÑо гоÑов поконÑиÑÑ Ñо Ñвоей Ñвободой,
бÑÐ´ÐµÑ Ð¿Ð¾Ð»ÑзоваÑÑÑÑ Ð²Ð°Ñей пÑогÑаммой,
+а ÑÑо знаÑиÑ, ÑÑо она ÑакÑиÑеÑки бÑдеÑ
ÑÑнкÑиониÑоваÑÑ ÐºÐ°Ðº ÑÑимÑл Ð´Ð»Ñ Ð»Ñдей
+поÑеÑÑÑÑ ÑÐ²Ð¾Ñ ÑвободÑ.</p>
+<p>
+ÐÑли Ð²Ñ Ð½Ð°Ð´ÐµÐµÑеÑÑ ÐºÐ¾Ð³Ð´Ð°-нибÑÐ´Ñ Ð¾Ð³Ð»ÑнÑÑÑÑÑ
на Ñвой жизненнÑй пÑÑÑ Ð¸
+поÑÑвÑÑвоваÑÑ, ÑÑо Ð²Ñ Ñделали вклад в
ÑазвиÑие поÑÑдоÑного и Ñвободного
+обÑеÑÑва, Ñо Ñвои пÑогÑÐ°Ð¼Ð¼Ñ Ð²Ð°Ð¼ нÑжно
делаÑÑ ÑвободнÑми.
+</p></dd>
+
+<dt><a href="#CompanyGPLCostsMoney" name="CompanyGPLCostsMoney">Ðне
ÑолÑко ÑÑо
+ÑÑало извеÑÑно, ÑÑо Ñ Ð¾Ð´Ð½Ð¾Ð¹ компании еÑÑÑ
ÐºÐ¾Ð¿Ð¸Ñ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL, и ÑÑобÑ
+полÑÑиÑÑ ÐµÐµ, нÑжно плаÑиÑÑ Ð´ÐµÐ½Ñги. Ðе
наÑÑÑаÑÑ Ð»Ð¸ они GPL, не Ð´ÐµÐ»Ð°Ñ ÐµÐµ
+доÑÑÑпной по ÐнÑеÑнеÑÑ?</a></dt>
+
+<dd>
+ÐеÑ. GPL ни Ð¾Ñ ÐºÐ¾Ð³Ð¾ не ÑÑебÑеÑ, ÑÑÐ¾Ð±Ñ Ð´Ð»Ñ
ÑаÑпÑоÑÑÑÐ°Ð½ÐµÐ½Ð¸Ñ Ð¸ÑполÑзовалÑÑ
+ÐнÑеÑнеÑ. ÐиÑÐµÐ½Ð·Ð¸Ñ Ñакже не ÑÑебÑÐµÑ Ð½Ð¸ оÑ
кого конкÑеÑно занимаÑÑÑÑ
+ÑаÑпÑоÑÑÑанением пÑогÑаммÑ. Ð (кÑоме
одного оÑобого ÑлÑÑаÑ) даже еÑли кÑо-Ñо
+дейÑÑвиÑелÑно ÑеÑÐ¸Ñ ÐºÐ¾Ð³Ð´Ð°-Ñо пеÑедаÑÑ
пÑогÑаммÑ, в GPL не Ñказано, ÑÑо он
+должен пеÑедаÑÑ ÐºÐ¾Ð¿Ð¸Ñ ÐºÐ¾Ð½ÐºÑеÑно вам или
какомÑ-Ñо дÑÑÐ³Ð¾Ð¼Ñ ÐºÐ¾Ð½ÐºÑеÑÐ½Ð¾Ð¼Ñ Ð»Ð¸ÑÑ.
+<p>
+ЧÑо GPL ÑÑебÑÐµÑ — ÑÑо ÑÑÐ¾Ð±Ñ Ñ Ð½ÐµÐ³Ð¾ бÑла
Ñвобода пеÑедаÑÑ ÐºÐ¾Ð¿Ð¸Ñ
+вам <em>еÑли он ÑÑого пожелаеÑ</em>. Ðак ÑолÑко
пÑавообладаÑÐµÐ»Ñ ÐºÐ¾Ð¿Ð¸Ñ
+пÑогÑÐ°Ð¼Ð¼Ñ ÐºÐ¾Ð¼Ñ-Ñо пеÑедал, ÑÑÐ¾Ñ ÐºÑо-Ñо
Ð¼Ð¾Ð¶ÐµÑ Ð¿ÐµÑедаваÑÑ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð²Ð°Ð¼ или
+ÐºÐ¾Ð¼Ñ Ð±Ñ Ñо ни бÑло еÑе, как ÑолÑко он ÑоÑÑеÑ
нÑжнÑм.
+</p></dd>
+
+<dt><a href="#ReleaseNotOriginal" name="ReleaseNotOriginal">ÐÐ¾Ð³Ñ Ñ
вÑпÑÑкаÑÑ
+пÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ лиÑензией, в коÑоÑой
Ñказано, ÑÑо ее измененнÑе веÑÑии
+ÑаÑпÑоÑÑÑанÑÑÑ Ð¿Ð¾Ð´ GPL можно, а ÑамÑ
пеÑвонаÑалÑнÑÑ Ð²ÐµÑÑÐ¸Ñ —
+нелÑзÑ?</a></dt>
+
+<dd>
+ÐеÑ. Ð¢Ð°ÐºÐ°Ñ Ð»Ð¸ÑÐµÐ½Ð·Ð¸Ñ Ð¿ÑоÑивоÑеÑила Ð±Ñ Ñамой
Ñебе. ÐавайÑе поÑмоÑÑим, какие
+поÑледÑÑÐ²Ð¸Ñ ÑÑо имело Ð±Ñ Ð´Ð»Ñ Ð¼ÐµÐ½Ñ ÐºÐ°Ðº
полÑзоваÑелÑ.
+<p>
+ÐÑедположим, ÑÑо Ñ Ð½Ð°ÑÐ¸Ð½Ð°Ñ Ñ
пеÑвонаÑалÑной веÑÑии (назовем ее веÑÑией
Ð),
+добавлÑÑ Ð½ÐµÐºÐ¾ÑоÑÑй ÑекÑÑ (пÑедÑÑавим Ñебе,
ÑÑо ÑÑо 1000 ÑÑÑок) и
+вÑпÑÑÐºÐ°Ñ Ð¸Ð·Ð¼ÐµÐ½ÐµÐ½Ð½ÑÑ Ð²ÐµÑÑÐ¸Ñ (назовем ее Ð)
под GPL. Ð GPL Ñказано, ÑÑо вÑÑкий
+Ð¼Ð¾Ð¶ÐµÑ Ð¸Ð·Ð¼ÐµÐ½Ð¸ÑÑ Ð²ÐµÑÑÐ¸Ñ Ð Ð¸ вÑпÑÑÑиÑÑ
ÑезÑлÑÑÐ°Ñ Ð¿Ð¾Ð´ GPL. ÐÑак, Ñ (или кÑо-Ñо
+дÑÑгой) Ð¼Ð¾Ð¶ÐµÑ ÑдалиÑÑ ÑÑи 1000 ÑÑÑок,
полÑÑив веÑÑÐ¸Ñ Ð, ÑекÑÑ ÐºÐ¾ÑоÑой в
+ÑоÑноÑÑи ÑÐ¾Ð²Ð¿Ð°Ð´Ð°ÐµÑ Ñ ÑекÑÑом веÑÑии Ð, но
коÑоÑÐ°Ñ ÑаÑпÑоÑÑÑанÑеÑÑÑ Ð¿Ð¾ GPL.</p>
+<p>
+ÐÑли Ð²Ñ Ð¿ÑÑаеÑеÑÑ Ð·Ð°Ð±Ð»Ð¾ÐºÐ¸ÑоваÑÑ ÑÑÐ¾Ñ Ñ
од,
Ñвно ÑказÑÐ²Ð°Ñ Ð² лиÑензии, ÑÑо мне
+нелÑÐ·Ñ Ð²Ð¾ÑпÑоизводиÑÑ ÑÑо-Ñо иденÑиÑное
веÑÑии Рпод GPL, Ñдалив Ñе ÑÑÑоки
+из веÑÑии Ð, Ñо лиÑÐµÐ½Ð·Ð¸Ñ ÑакÑиÑеÑки
говоÑиÑ, ÑÑо Ñ Ð½Ðµ Ð¼Ð¾Ð³Ñ Ð¿Ð¾Ð»Ð½Ð¾ÑÑÑÑ
+иÑполÑзоваÑÑ Ð²ÐµÑÑÐ¸Ñ Ð Ð²Ñеми ÑпоÑобами,
ÑазÑеÑеннÑми GPL. ÐÑÑгими Ñловами,
+ÑÑа лиÑÐµÐ½Ð·Ð¸Ñ Ð² дейÑÑвиÑелÑноÑÑи не
позволÑÐµÑ Ð¿Ð¾Ð»ÑзоваÑÐµÐ»Ñ Ð²ÑпÑÑкаÑÑ
+модиÑиÑиÑованнÑÑ Ð²ÐµÑÑиÑ, ÑакÑÑ, как Ð, под
GPL.
+</p>
+</dd>
+
+<dt><a href="#DistributeSubsidiary"
name="DistributeSubsidiary">ЯвлÑеÑÑÑ Ð»Ð¸
+ÑаÑпÑоÑÑÑанением пеÑедаÑа копии в
конÑÑолиÑÑемое доÑеÑнее пÑедпÑиÑÑие?</a></dt>
+<dd>
+<p>
+ЯвлÑеÑÑÑ Ð»Ð¸ “ÑаÑпÑоÑÑÑанением”
пеÑедаÑа копии в Ñакое доÑеÑнее
+пÑедпÑиÑÑие или из него — вопÑоÑ,
коÑоÑÑй в каждом ÑлÑÑае ÑледÑеÑ
+ÑеÑаÑÑ Ð² ÑамкаÑ
авÑоÑÑкого пÑава
ÑооÑвеÑÑÑвÑÑÑей ÑÑиÑдикÑии. GPL не оÑменÑеÑ
+и не Ð¼Ð¾Ð¶ÐµÑ Ð¾ÑменÑÑÑ Ð¼ÐµÑÑнÑÑ
законов.
ÐозиÑÐ¸Ñ Ð°Ð²ÑоÑÑкого пÑава СШРна ÑÑоÑ
+ÑÑÐµÑ Ð½Ðµ вполне ÑÑна, но ÑакÑиÑеÑки ÑÑо не
ÑÑиÑаеÑÑÑ ÑаÑпÑоÑÑÑанением.
+</p><p>
+ÐÑли в какой-Ñо ÑÑÑане ÑÑо ÑÑиÑаеÑÑÑ
ÑаÑпÑоÑÑÑанением и доÑеÑнее пÑедпÑиÑÑие
+должно полÑÑиÑÑ Ð¿Ñаво пеÑеÑаÑпÑоÑÑÑанÑÑÑ
пÑогÑаммÑ, Ñо на пÑакÑике никакой
+ÑазниÑÑ Ð½Ðµ бÑдеÑ. ÐоÑеÑнее пÑедпÑиÑÑие
конÑÑолиÑÑеÑÑÑ ÑиÑмой-ÑÑÑедиÑелем;
+незавиÑимо Ð¾Ñ Ñого, еÑÑÑ Ñ Ð½ÐµÐµ пÑава или
неÑ, она не бÑÐ´ÐµÑ ÑаÑпÑоÑÑÑанÑÑÑ
+пÑогÑаммÑ, еÑли ÑолÑко ÑиÑма-ÑÑÑедиÑÐµÐ»Ñ Ð½Ðµ
заÑ
оÑÐµÑ ÑÑого.
+</p>
+</dd>
+
+<dt><a href="#ClickThrough" name="ClickThrough">Ðожно ли в
пÑогÑамме ÑÑÑановки
+пÑоÑиÑÑ Ð»Ñдей нажаÑÑ ÐºÐ½Ð¾Ð¿ÐºÑ Ð² знак
ÑоглаÑÐ¸Ñ Ñ GPL? ÐÑли Ñ Ð¿Ð¾Ð»ÑÑÐ°Ñ ÐºÐ°ÐºÑÑ-Ñо
+пÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾ GPL, ÑÑебÑеÑÑÑ Ð»Ð¸ Ð¾Ñ Ð¼ÐµÐ½Ñ
ÑоглаÑаÑÑÑÑ Ñ Ñем Ð±Ñ Ñо ни бÑло?</a></dt>
+<dd>
+<p>
+РнекоÑоÑÑÑ
ÑиÑÑемаÑ
пакеÑиÑованиÑ
пÑогÑамм еÑÑÑ Ð¼ÐµÑÑо, где Ð¾Ñ Ð²Ð°Ñ ÑÑебÑÑÑ
+нажаÑÑ Ð½Ð° ÐºÐ½Ð¾Ð¿ÐºÑ Ð¸Ð»Ð¸ каким-Ñо дÑÑгим
обÑазом изÑÑвиÑÑ ÑоглаÑие Ñ ÑÑловиÑми
+GPL. ÐÑо не ÑÑебÑеÑÑÑ, но и не запÑеÑено. Ð Ñ
нажаÑием, и без него пÑавила
+GPL оÑÑаÑÑÑÑ Ð¾Ð´Ð½Ð¸Ð¼Ð¸ и Ñеми же. </p>
+
+<p>
+ÐÑоÑÑое ÑоглаÑие Ñ GPL не Ð½Ð°Ð»Ð°Ð³Ð°ÐµÑ Ð½Ð° ваÑ
никакиÑ
обÑзаÑелÑÑÑв. ÐÑ Ð²Ð°Ñ Ð½Ðµ
+ÑÑебÑеÑÑÑ ÑоглаÑие Ñ Ñем Ð±Ñ Ñо ни бÑло длÑ
пÑоÑÑого полÑÐ·Ð¾Ð²Ð°Ð½Ð¸Ñ Ð¿ÑогÑаммой,
+коÑоÑÐ°Ñ Ð»Ð¸ÑензиÑована по GPL. ÐбÑзаÑелÑÑÑва
поÑвлÑÑÑÑÑ Ñ Ð²Ð°Ñ ÑолÑко в
+ÑлÑÑае, еÑли Ð²Ñ Ð¸Ð·Ð¼ÐµÐ½ÑеÑе или
ÑаÑпÑоÑÑÑанÑеÑе пÑогÑаммÑ. ÐÑли Ð²Ð°Ñ Ð½Ð°
Ñамом
+деле беÑÐ¿Ð¾ÐºÐ¾Ð¸Ñ Ð¿ÑоÑедÑÑа нажаÑиÑ, Ñо вам
ниÑÑо не меÑÐ°ÐµÑ Ð¿ÐµÑелаÑаÑÑ
+пÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL, ÑÑÐ¾Ð±Ñ Ð¾Ð±Ð¾Ð¹Ñи ÑÑо.
+</p>
+</dd>
+
+<dt><a href="#GPLCompatInstaller" name="GPLCompatInstaller">Ðне Ñ
оÑелоÑÑ Ð±Ñ
+обÑединиÑÑ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL Ñ Ð½ÐµÐºÐ¾ÑоÑого
Ñода пÑогÑаммой ÑÑÑановки. Ðолжна
+ли Ñ ÑÑой пÑогÑÐ°Ð¼Ð¼Ñ ÑÑÑановки бÑÑÑ
лиÑензиÑ, ÑовмеÑÑÐ¸Ð¼Ð°Ñ Ñ GPL?</a></dt>
+<dd>
+<p>ÐеÑ. ÐÑогÑамма ÑÑÑановки и ÑайлÑ, коÑоÑÑе
она ÑÑÑÐ°Ð½Ð°Ð²Ð»Ð¸Ð²Ð°ÐµÑ — ÑÑо
+ÑазделÑнÑе ÑабоÑÑ. ÐоÑÑÐ¾Ð¼Ñ ÑÑÐ»Ð¾Ð²Ð¸Ñ GPL не
ÑаÑпÑоÑÑÑанÑÑÑÑÑ Ð½Ð° пÑогÑаммÑ
+ÑÑÑановки.</p>
+</dd>
+
+</dl>
+
+
+<div style="font-size: small;">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
+ </div>
+</div>
+
+<!--#include virtual="/server/footer.ru.html" -->
+<div id="footer">
+<p>
+ÐожалÑйÑÑа, пÑиÑÑлайÑе запÑоÑÑ ÑÐ¾Ð½Ð´Ñ Ð¸ GNU
по адÑеÑÑ <a
+href="mailto:address@hidden";><address@hidden></a>. ÐÑÑÑ Ñакже <a
+href="/contact/">дÑÑгие ÑпоÑÐ¾Ð±Ñ ÑвÑзаÑÑÑÑ</a> Ñ
Ñондом.
+<br />
+ÐожалÑйÑÑа, пÑиÑÑлайÑе оÑÑеÑÑ Ð¾
неÑабоÑаÑÑиÑ
ÑÑÑлкаÑ
и дÑÑгие попÑавки или
+пÑÐµÐ´Ð»Ð¾Ð¶ÐµÐ½Ð¸Ñ Ð¿Ð¾ адÑеÑÑ <a
+href="mailto:address@hidden";><address@hidden></a>.
+</p>
+
+<p>
+Ð¡Ð²ÐµÐ´ÐµÐ½Ð¸Ñ Ð¿Ð¾ кооÑдинаÑии и пÑедложениÑм
пеÑеводов ÑÑой ÑÑаÑÑи Ñм. в <a
+href="/server/standards/README.translations.html">“Ð
ÑководÑÑве по
+пеÑеводам”</a>.
+</p>
+
+<p>
+Copyright © 2001, 2006, 2007, 2008, 2011 Free Software Foundation,
+Inc.,</p>
+<address>51 Franklin St, Fifth Floor, Boston, MA 02110, USA</address>
+<p>ÐÑо пÑоизведение доÑÑÑпно по <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/deed.ru";>лиÑензии
+Creative Commons Attribution-NoDerivs (<em>ÐÑÑибÑÑÐ¸Ñ —
Ðез
+пÑоизводнÑÑ
пÑоизведений</em>) 3.0 СШÐ</a>.
+</p>
+
+
+<div class="translators-credits">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
+ </div>
+
+
+ <p>
+<!-- timestamp start -->
+Ðбновлено:
+
+$Date: 2012/06/05 08:27:51 $
+
+<!-- timestamp end -->
+</p>
+</div>
+
+</div>
+</body>
+</html>
Index: licenses/old-licenses/po/gpl-2.0-faq.ru-en.html
===================================================================
RCS file: licenses/old-licenses/po/gpl-2.0-faq.ru-en.html
diff -N licenses/old-licenses/po/gpl-2.0-faq.ru-en.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ licenses/old-licenses/po/gpl-2.0-faq.ru-en.html 5 Jun 2012 08:28:04
-0000 1.1
@@ -0,0 +1,2524 @@
+<!--#include virtual="/server/header.html" -->
+
+<title>Frequently Asked Questions about the GNU GPL v2.0 - GNU Project - Free
Software Foundation (FSF)</title>
+
+<!--#include virtual="/server/banner.html" -->
+<!--#include virtual="/licenses/old-licenses/po/gpl-2.0-faq.translist" -->
+
+<h2>Frequently Asked Questions about version 2 of the GNU GPL</h2>
+
+<p>
+This page contains answers to commonly asked questions about the GNU General
+Public License (GPL), version 2. The FAQ for the current version of the GPL is
+<a href="/licenses/gpl-faq.html">here</a>. To learn more about the Free
+Software Foundation's other licenses, please see <a
+href="/licenses/licenses.html">our licenses page</a>.</p>
+
+<p>
+After you read this FAQ, <a href="/cgi-bin/license-quiz.cgi">you can
+test your knowledge of Free Software licensing with our quiz</a>.
+</p>
+
+<!-- Replace this list with the page's contents. -->
+<h4>Table of Contents</h4>
+
+ <h4>Basic questions about the GPL, the GNU Project, and the Free
+ Software Foundation</h4>
+
+ <ul>
+ <li><a href="#WhatDoesGPLStandFor" name="TOCWhatDoesGPLStandFor">What
+ does “GPL” stand for?</a></li>
+
+ <li><a href="#DoesFreeSoftwareMeanUsingTheGPL"
+ name="TOCDoesFreeSoftwareMeanUsingTheGPL">Does free software mean
+ using the GPL?</a></li>
+
+ <li><a href="#WhyUseGPL" name="TOCWhyUseGPL">Why should I use the GNU GPL
+ rather than other free software licenses?</a></li>
+
+ <li><a href="#DoesAllGNUSoftwareUseTheGNUGPLAsItsLicense"
+ name="TOCDoesAllGNUSoftwareUseTheGNUGPLAsItsLicense">Does all GNU
+ software use the GNU GPL as its license?</a></li>
+
+ <li><a href="#DoesUsingTheGPLForAProgramMakeItGNUSoftware"
+ name="TOCDoesUsingTheGPLForAProgramMakeItGNUSoftware">Does using the
+ GPL for a program make it GNU software?</a></li>
+
+ <li><a href="#GPLOtherThanSoftware" name="TOCGPLOtherThanSoftware">Can
+ I use the GPL for something other than software?</a></li>
+
+ <li><a href="#WhyNotGPLForManuals" name="TOCWhyNotGPLForManuals">Why
+ don't you use the GPL for manuals?</a></li>
+
+ <li><a href="#GPLTranslations" name="TOCGPLTranslations">Are there
+ translations of the GPL into other languages?</a></li>
+
+ <li><a href="#WhySomeGPLAndNotLGPL" name="TOCWhySomeGPLAndNotLGPL">Why
+ are some GNU libraries released under the ordinary GPL rather than the
+ Lesser GPL?</a></li>
+
+ <li><a href="#WhoHasThePower" name="TOCWhoHasThePower">Who has the
+ power to enforce the GPL?</a></li>
+
+ <li><a href="#AssignCopyright" name="TOCAssignCopyright">Why does the
+ FSF require that contributors to FSF-copyrighted programs assign
+ copyright to the FSF? If I hold copyright on a GPL'ed program, should
+ I do this, too? If so, how?</a></li>
+
+ <li><a href="#ModifyGPL" name="TOCModifyGPL">Can I modify the GPL
+ and make a modified license?</a></li>
+
+ </ul>
+
+ <h4>General understanding of the GPL</h4>
+
+ <ul>
+ <li><a href="#WhyDoesTheGPLPermitUsersToPublishTheirModifiedVersions"
+ name="TOCWhyDoesTheGPLPermitUsersToPublishTheirModifiedVersions">Why does
+ the GPL permit users to publish their modified versions?</a></li>
+
+ <li><a href="#GPLRequireSourcePostedPublic"
+ name="TOCGPLRequireSourcePostedPublic">Does
+ the GPL require that source code of modified versions be posted to the
public?</a></li>
+
+ <li><a href="#GPLAndNonfreeOnSameMachine"
+ name="TOCGPLAndNonfreeOnSameMachine"> Can I have a GPL-covered
+ program and an unrelated non-free program on the same
+ computer?</a></li>
+
+ <li><a href="#CanIDemandACopy" name="TOCCanIDemandACopy">If I know
+ someone has a copy of a GPL-covered program, can I demand he give
+ me a copy?</a></li>
+
+ <li><a href="#WhatDoesWrittenOfferValid"
+ name="TOCWhatDoesWrittenOfferValid">What does this “written
+ offer valid for any third party” mean? Does that mean
+ everyone in the world can get the source to any GPL'ed program no
+ matter what?</a></li>
+
+ <li><a href="#TheGPLSaysModifiedVersions"
+ name="TOCTheGPLSaysModifiedVersions">The GPL says that modified
+ versions, if released, must be “licensed … to all
+ third parties.” Who are these third parties?</a></li>
+
+ <li><a href="#DoesTheGPLAllowMoney" name="TOCDoesTheGPLAllowMoney">Does
+ the GPL allow me to sell copies of the program for money?</a></li>
+
+ <li><a href="#DoesTheGPLAllowDownloadFee"
+ name="TOCDoesTheGPLAllowDownloadFee"> Does the GPL allow me to
+ charge a fee for downloading the program from my site?</a></li>
+
+ <li><a href="#DoesTheGPLAllowRequireFee"
name="TOCDoesTheGPLAllowRequireFee">
+ Does the GPL allow me to require that anyone who receives the software
+ must pay me a fee and/or notify me?</a></li>
+
+ <li><a href="#DoesTheGPLRequireAvailabilityToPublic"
+ name="TOCDoesTheGPLRequireAvailabilityToPublic">If I distribute GPL'd
+ software for a fee, am I required to also make it available to the
+ public without a charge?</a></li>
+
+ <li><a href="#DoesTheGPLAllowNDA" name="TOCDoesTheGPLAllowNDA">Does
+ the GPL allow me to distribute a copy under a
+ nondisclosure agreement?</a></li>
+
+ <li><a href="#DoesTheGPLAllowModNDA" name="TOCDoesTheGPLAllowModNDA">Does
+ the GPL allow me to distribute a modified or beta version under a
+ nondisclosure agreement?</a></li>
+
+ <li><a href="#DevelopChangesUnderNDA" name="TOCDevelopChangesUnderNDA">Does
+ the GPL allow me to develop a modified version under a
+ nondisclosure agreement?</a></li>
+
+ <li><a href="#WhyMustIInclude" name="TOCWhyMustIInclude">Why does the GPL
+ require including a copy of the GPL with every copy of the
program?</a></li>
+
+ <li><a href="#WhatIfWorkIsShort" name="TOCWhatIfWorkIsShort">What
+ if the work is not much longer than the license itself?</a></li>
+
+ <li><a href="#RequiredToClaimCopyright"
+ name="TOCRequiredToClaimCopyright">Am I required to claim a copyright on
+ my modifications to a GPL-covered program?</a></li>
+
+ <li><a href="#CombinePublicDomainWithGPL"
+ name="TOCCombinePublicDomainWithGPL">If a program combines public-domain
+ code with GPL-covered code, can I take the public-domain part and use it
+ as public domain code?</a></li>
+
+ <li><a href="#IWantCredit" name="TOCIWantCredit">I want to get credit for
my work. I
+ want people to know what I wrote. Can I still get credit if I use the
GPL?</a></li>
+
+ <li><a href="#GPLOmitPreamble" name="TOCGPLOmitPreamble">Can I omit the
+ preamble of the GPL, or the instructions for how to use it on your own
+ programs, to save space?</a></li>
+
+ <li><a href="#WhatIsCompatible" name="TOCWhatIsCompatible">What does it
mean to
+ say that two licenses are “compatible”?</a></li>
+
+ <li><a href="#WhatDoesCompatMean"
+ name="TOCWhatDoesCompatMean">What does it mean to say a license is
+ “compatible with the GPL”?</a></li>
+
+ <li><a href="#OrigBSD" name="TOCOrigBSD">Why is the original BSD
+ license incompatible with the GPL?</a></li>
+
+ <li><a href="#MereAggregation" name="TOCMereAggregation">What is
+ the difference between “mere aggregation” and
+ “combining two modules into one program”?</a></li>
+
+ <li><a href="#AssignCopyright" name="TOCAssignCopyright">Why does the
+ FSF require that contributors to FSF-copyrighted programs assign
+ copyright to the FSF? If I hold copyright on a GPL'ed program, should
+ I do this, too? If so, how?</a></li>
+
+ <li><a href="#GPLCommercially" name="TOCGPLCommercially">If I use a
+ piece of software that has been obtained under the GNU GPL, am I
+ allowed to modify the original code into a new program, then
+ distribute and sell that new program commercially?</a></li>
+
+ <li><a href="#GPLOtherThanSoftware" name="TOCGPLOtherThanSoftware">Can
+ I use the GPL for something other than software?</a></li>
+
+ <li><a href="#LGPLJava" name="TOCLGPLJava">How does the LGPL
+ work with Java?</a></li>
+
+
+ </ul>
+
+ <h4>Using the GPL for your programs</h4>
+
+ <ul>
+
+ <li><a href="#CouldYouHelpApplyGPL" name="TOCCouldYouHelpApplyGPL">Could
+ you give me step by step instructions on how to apply the GPL to my
+ program?</a></li>
+
+ <li><a href="#WhyUseGPL" name="TOCWhyUseGPL">Why should I use the GNU GPL
+ rather than other free software licenses?</a></li>
+
+ <li><a href="#WhyMustIInclude" name="TOCWhyMustIInclude">Why does the GPL
+ require including a copy of the GPL with every copy of the
program?</a></li>
+
+ <li><a href="#WhatIfWorkIsShort" name="TOCWhatIfWorkIsShort">What
+ if the work is not much longer than the license itself?</a></li>
+
+ <li><a href="#GPLOmitPreamble" name="TOCGPLOmitPreamble">Can I omit the
+ preamble of the GPL, or the instructions for how to use it on your own
+ programs, to save space?</a></li>
+
+ <li><a href="#HowIGetCopyright" name="TOCHowIGetCopyright">How do I
+ get a copyright on my program in order to release it under the
+ GPL?</a></li>
+
+ <li><a href="#WhatIfSchool" name="TOCWhatIfSchool">What if my school
+ might want to make my program into its own proprietary software
+ product?</a></li>
+
+ <li><a href="#ReleaseUnderGPLAndNF" name="TOCReleaseUnderGPLAndNF">I
+ would like to release a program I wrote under the GNU GPL, but I would
+ like to use the same code in non-free programs.</a></li>
+
+ <li><a href="#CanDeveloperThirdParty"
+ name="TOCCanDeveloperThirdParty">Can the developer of a program who
+ distributed it under the GPL later license it to another party for
+ exclusive use?</a></li>
+
+ <li><a href="#GPLUSGov" name="TOCGPLUSGov">Can the US Government
+ release a program under the GNU GPL?</a></li>
+
+ <li><a href="#GPLUSGovAdd" name="TOCGPLUSGovAdd">Can the US Government
+ release improvements to a GPL-covered program?</a></li>
+
+ <li><a href="#VersionTwoOrLater" name="TOCVersionTwoOrLater">Why
+ should programs say “Version 2 of the GPL or any later
+ version”?</a></li>
+
+ <li><a href="#GPLOutput" name="TOCGPLOutput">Is there some way that I
+ can GPL the output people get from use of my program? For example, if
+ my program is used to develop hardware designs, can I require that
+ these designs must be free?</a></li>
+
+ <li><a href="#WhyNotGPLForManuals" name="TOCWhyNotGPLForManuals">Why
+ don't you use the GPL for manuals?</a></li>
+
+ <li><a href="#FontException" name="TOCFontException">How does the
+ GPL apply to fonts?</a></li>
+
+ <li><a href="#WMS" name="TOCWMS">What license should I use for
+ website maintenance system templates?</a></li>
+
+ <li><a href="#NonFreeTools" name="TOCNonFreeTools">Can I release
+ a program under the GPL which I developed using non-free tools?</a></li>
+ </ul>
+
+ <h4>Distribution of programs released under the GPL</h4>
+
+ <ul>
+
+ <li><a href="#ModifiedJustBinary"
+ name="TOCModifiedJustBinary">Can I release a modified
+ version of a GPL-covered program in binary form only?</a></li>
+
+ <li><a href="#UnchangedJustBinary" name="TOCUnchangedJustBinary">I
+ downloaded just the binary from the net. If I distribute copies,
+ do I have to get the source and distribute that too?</a></li>
+
+ <li><a href="#DistributeWithSourceOnInternet"
+ name="TOCDistributeWithSourceOnInternet">I want to distribute
+ binaries via physical media without accompanying sources. Can I
+ provide source code by FTP instead of by mail order?</a></li>
+
+ <li><a href="#RedistributedBinariesGetSource"
+ name="TOCRedistributedBinariesGetSource">My friend got a GPL-covered
+ binary with an offer to supply source, and made a copy for me.
+ Can I use the offer to obtain the source?</a></li>
+
+ <li><a href="#SourceAndBinaryOnDifferentSites"
+ name="TOCSourceAndBinaryOnDifferentSites">Can I put the binaries on my
+ Internet server and put the source on a different Internet site?</a></li>
+
+ <li><a href="#DistributeExtendedBinary"
+ name="TOCDistributeExtendedBinary">I want to distribute an extended
+ version of a GPL-covered program in binary form. Is it enough to
+ distribute the source for the original version?</a></li>
+
+ <li><a href="#DistributingSourceIsInconvenient"
+ name="TOCDistributingSourceIsInconvenient">I want to distribute
+ binaries, but distributing complete source is inconvenient. Is it
+ ok if I give users the diffs from the “standard”
+ version along with the binaries?</a></li>
+
+ <li><a href="#AnonFTPAndSendSources" name="TOCAnonFTPAndSendSources">I
+ want to make binaries available for anonymous FTP, but send sources
+ only to people who order them.</a></li>
+
+ <li><a href="#HowCanIMakeSureEachDownloadGetsSource"
+ name="TOCHowCanIMakeSureEachDownloadGetsSource">How can I make sure
+ each user who downloads the binaries also gets the source?</a></li>
+
+ <li><a href="#ReleaseNotOriginal" name="TOCReleaseNotOriginal"> Can
+ I release a program with a license which says that you can distribute
+ modified versions of it under the GPL but you can't distribute the
+ original itself under the GPL?</a></li>
+
+ <li><a href="#CompanyGPLCostsMoney" name="TOCCompanyGPLCostsMoney"> I
+ just found out that a company has a copy of a GPL'ed program, and it
+ costs money to get it. Aren't they violating the GPL by not making it
+ available on the Internet?</a></li>
+
+ <li><a href="#UnreleasedMods" name="TOCUnreleasedMods"> A company
+ is running a modified version of a GPL'ed program on a web site.
+ Does the GPL say they must release their modified sources?</a></li>
+
+ <li><a href="#InternalDistribution"
+ name="TOCInternalDistribution"> Is use within one organization or
+ company “distribution”?</a></li>
+
+ <li><a href="#StolenCopy" name="TOCStolenCopy">
+ If someone steals a CD containing a version of a GPL-covered
+ program, does the GPL give him the right to redistribute that
+ version?</a></li>
+
+ <li><a href="#TradeSecretRelease" name="TOCTradeSecretRelease">
+ What if a company distributes a copy as a trade secret?</a></li>
+
+ <li><a href="#GPLFairUse" name="TOCGPLFairUse">Do I have
+ “fair use” rights in using the source code of a
+ GPL-covered program?</a></li>
+
+ <li><a href="#DistributeSubsidiary" name="TOCDistributeSubsidiary">
+ Does moving a copy to a majority-owned, and controlled, subsidiary
+ constitute distribution?</a></li>
+
+ <li><a href="#ClickThrough" name="TOCClickThrough"> Can software
+ installers ask people to click to agree to the GPL? If I get some
+ software under the GPL, do I have to agree to anything?</a></li>
+
+ <li><a href="#GPLCompatInstaller" name="TOCGPLCompatInstaller">I would
+ like to bundle GPLed software with some sort of installation software.
+ Does that installer need to have a GPL-compatible license?</a></li>
+
+ </ul>
+
+ <h4>Using programs released under the GPL when writing other
+ programs</h4>
+
+ <ul>
+
+ <li><a href="#GPLAndNonfreeOnSameMachine"
+ name="TOCGPLAndNonfreeOnSameMachine"> Can I have a GPL-covered
+ program and an unrelated non-free program on the same
+ computer?</a></li>
+
+ <li><a href="#CanIUseGPLToolsForNF" name="TOCCanIUseGPLToolsForNF">Can
+ I use GPL-covered editors such as GNU Emacs to develop non-free
+ programs? Can I use GPL-covered tools such as GCC to compile
+ them?</a></li>
+
+ <li><a href="#GPLOutput" name="TOCGPLOutput">Is there some way that I
+ can GPL the output people get from use of my program? For example, if
+ my program is used to develop hardware designs, can I require that
+ these designs must be free?</a></li>
+
+ <li><a href="#WhatCaseIsOutputGPL" name="TOCWhatCaseIsOutputGPL">In
+ what cases is the output of a GPL program covered by the GPL too?</a></li>
+
+ <li><a href="#PortProgramToGL" name="TOCPortProgramToGL">If I port my
+ program to GNU/Linux, does that mean I have to release it as Free
+ Software under the GPL or some other Free Software license?</a></li>
+
+ <li><a href="#GPLInProprietarySystem"
+ name="TOCGPLInProprietarySystem">I'd like to incorporate GPL-covered
+ software in my proprietary system. Can I do this?</a></li>
+
+ <li><a href="#LibGCCException" name="TOCLibGCCException">Does the
+ libstdc++ exception permit dynamic linking?</a></li>
+
+ </ul>
+
+ <h4>Combining work with code released under the GPL</h4>
+
+ <ul>
+
+ <li><a href="#MereAggregation" name="TOCMereAggregation">What is
+ the difference between “mere aggregation” and
+ “combining two modules into one program”?</a></li>
+
+ <li><a href="#GPLFairUse" name="TOCGPLFairUse">Do I have
+ “fair use” rights in using the source code of a
+ GPL-covered program?</a></li>
+
+ <li><a href="#GPLUSGovAdd" name="TOCGPLUSGovAdd">Can the US Government
+ release improvements to a GPL-covered program?</a></li>
+
+ <li><a href="#IfLibraryIsGPL" name="TOCIfLibraryIsGPL">If a library is
+ released under the GPL (not the LGPL), does that mean that any program
+ which uses it has to be under the GPL?</a></li>
+
+ <li><a href="#LinkingWithGPL" name="TOCLinkingWithGPL">You have a
+ GPL'ed program that I'd like to link with my code to build a
+ proprietary program. Does the fact that I link with your program mean
+ I have to GPL my program?</a></li>
+
+ <li><a href="#SwitchToLGPL" name="TOCSwitchToLGPL">If so, is there any
+ chance I could get a license of your program under the Lesser GPL?</a></li>
+
+ <li><a href="#WillYouMakeAnException"
+ name="TOCWillYouMakeAnException">Using a certain GNU program under the
+ GPL does not fit our project to make proprietary software. Will you
+ make an exception for us? It would mean more users of that
+ program.</a></li>
+
+ <li><a href="#IfInterpreterIsGPL" name="TOCIfInterpreterIsGPL">If a
+ programming language interpreter is released under the GPL, does that
+ mean programs written to be interpreted by it must be under
+ GPL-compatible licenses?</a></li>
+
+ <li><a href="#InterpreterIncompat" name="TOCInterpreterIncompat">If a
+ programming language interpreter has a license that is incompatible
+ with the GPL, can I run GPL-covered programs on it?</a></li>
+
+ <li><a href="#GPLModuleLicense" name="TOCGPLModuleLicense">If I add a
+ module to a GPL-covered program, do I have to use the GPL as the
+ license for my module?</a></li>
+
+ <li><a href="#GPLAndPlugins" name="TOCGPLAndPlugins">If a program
+ released under the GPL uses plug-ins, what are the requirements for
+ the licenses of a plug-in?</a></li>
+
+ <li><a href="#GPLPluginsInNF" name="TOCGPLPluginsInNF">Can I apply the
+ GPL when writing a plug-in for a non-free program?</a></li>
+
+ <li><a href="#NFUseGPLPlugins" name="TOCNFUseGPLPlugins">Can I
+ release a non-free program that's designed to load a GPL-covered
+ plug-in?</a></li>
+
+ <li><a href="#GPLInProprietarySystem"
+ name="TOCGPLInProprietarySystem">I'd like to incorporate GPL-covered
+ software in my proprietary system. Can I do this?</a></li>
+
+ <li><a href="#GPLWrapper" name="TOCGPLWrapper">I'd like to
+ incorporate GPL-covered software in my proprietary system. Can I
+ do this by putting a “wrapper” module, under a
+ GPL-compatible lax permissive license (such as the X11 license) in
+ between the GPL-covered part and the proprietary part?</a></li>
+
+ <li><a href="#FSWithNFLibs" name="TOCFSWithNFLibs"> Can I write
+ free software that uses non-free libraries?</a></li>
+
+ <li><a href="#GPLIncompatibleLibs" name="TOCGPLIncompatibleLibs">
+ What legal issues come up if I use GPL-incompatible libraries with
+ GPL software?</a></li>
+
+ <li><a href="#WindowsRuntimeAndGPL" name="TOCWindowsRuntimeAndGPL">I'm
+ writing a Windows application with Microsoft Visual C++ and I will be
+ releasing it under the GPL. Is dynamically linking my program with
+ the Visual C++ run-time library permitted under the GPL?</a></li>
+
+ <li><a href="#MoneyGuzzlerInc" name="TOCMoneyGuzzlerInc">I'd like
+ to modify GPL-covered programs and link them with the portability
+ libraries from Money Guzzler Inc. I cannot distribute the source
+ code for these libraries, so any user who wanted to change these
+ versions would have to obtain those libraries separately. Why
+ doesn't the GPL permit this?</a></li>
+
+ <li><a href="#GPLIncompatibleAlone" name="TOCGPLIncompatibleAlone">If
+ license for a module Q has a requirement that's incompatible with the
+ GPL, but the requirement applies only when Q is distributed by itself,
+ not when Q is included in a larger program, does that make the license
+ GPL-compatible? Can I combine or link Q with a GPL-covered
+ program?</a></li>
+
+ <li><a href="#OOPLang" name="TOCOOPLANG"> In an object-oriented
+ language such as Java, if I use a class that is GPL'ed without
+ modifying, and subclass it, in what way does the GPL affect the larger
+ program?</a></li>
+
+ <li><a href="#LinkingOverControlledInterface"
+ name="TOCLinkingOverControlledInterface">How can I allow linking of
+ proprietary modules with my GPL-covered library under a controlled
+ interface only?</a></li>
+
+ <li><a href="#Consider" name="TOCConsider">Consider this situation:
+ 1. X releases V1 of a project under the GPL.
+ 2. Y contributes to the development of V2 with changes and new
code based on V1.
+ 3. X wants to convert V2 to a non-GPL license. Does X need Y's
permission?</a></li>
+
+ <li><a href="#ManyDifferentLicenses" name="TOCManyDifferentLicenses">I
+ have written an application that links with many different components,
+ that have different licenses. I am very confused as to what licensing
+ requirements are placed on my program. Can you please tell me what
+ licenses I may use?</a></li>
+
+ </ul>
+
+ <h4>Questions about violations of the GPL</h4>
+
+ <ul>
+
+ <li><a href="#ReportingViolation" name="TOCReportingViolation">What
+ should I do if I discover a possible violation of the GPL?</a></li>
+
+ <li><a href="#WhoHasThePower" name="TOCWhoHasThePower">Who has the
+ power to enforce the GPL?</a></li>
+
+ <li><a href="#HeardOtherLicense" name="TOCHeardOtherLicense">I heard
+ that someone got a copy of a GPL'ed program under another license. Is
+ this possible?</a></li>
+
+ <li><a href="#DeveloperViolate" name="TOCDeveloperViolate">Is the
+ developer of a GPL-covered program bound by the GPL? Could the
+ developer's actions ever be a violation of the GPL?</a></li>
+
+ <li><a href="#CompanyGPLCostsMoney" name="TOCCompanyGPLCostsMoney"> I
+ just found out that a company has a copy of a GPL'ed program, and it
+ costs money to get it. Aren't they violating the GPL by not making it
+ available on the Internet?</a></li>
+
+ </ul>
+
+<hr />
+
+<dl>
+
+<dt><b><a href="#TOCWhatDoesGPLStandFor"
+name="WhatDoesGPLStandFor">What does “GPL” stand
+for?</a></b></dt>
+
+<dd>“GPL” stands for “General Public License”.
+The most widespread such license is the GNU General Public License, or
+GNU GPL for short. This can be further shortened to
+“GPL”, when it is understood that the GNU GPL is the one
+intended.
+<p></p></dd>
+
+<dt><b><a href="#TOCDoesFreeSoftwareMeanUsingTheGPL"
name="DoesFreeSoftwareMeanUsingTheGPL">
+Does free software mean using the GPL?</a></b></dt>
+
+<dd>
+Not at all—there are many other free software licenses. We have an
+<a href="/licenses/license-list.html"> incomplete
+list</a>. Any license that provides the user <a
+href="/philosophy/free-sw.html">certain specific
+freedoms</a> is a free software license.
+<p></p></dd>
+
+<dt><b><a href="#TOCWhyUseGPL" name="WhyUseGPL">
+Why should I use the GNU GPL rather than other free software
licenses?</a></b></dt>
+
+<dd>
+Using the GNU GPL will require that all the <a
+href="/philosophy/pragmatic.html">released improved versions be free
+software</a>. This means you can avoid the risk of having to compete
+with a proprietary modified version of your own work. However, in
+some special situations it can be better to use a
+<a href="/licenses/why-not-lgpl.html"> more permissive license</a>.
+<p></p></dd>
+
+<dt><b><a href="#TOCDoesAllGNUSoftwareUseTheGNUGPLAsItsLicense"
name="DoesAllGNUSoftwareUseTheGNUGPLAsItsLicense">
+Does all GNU software use the GNU GPL as its license?</a></b></dt>
+
+<dd>
+Most GNU software packages use the GNU GPL, but there are a few
+GNU programs (and parts of programs) that use looser licenses, such as the
+Lesser GPL. When we do this, it is a matter of <a
+href="/licenses/why-not-lgpl.html"> strategy</a>.
+<p></p></dd>
+
+<dt><b><a href="#TOCDoesUsingTheGPLForAProgramMakeItGNUSoftware"
name="DoesUsingTheGPLForAProgramMakeItGNUSoftware">
+Does using the GPL for a program make it GNU software?</a></b></dt>
+
+<dd>
+Anyone can release a program under the GNU GPL but that does not
+make it a GNU package.
+<p>
+Making the program a GNU software package means explicitly
+contributing to the GNU Project. This happens when the program's
+developers and the GNU Project agree to do it. If you are interested
+in contributing a program to the GNU Project, please write to
+<a href="mailto:address@hidden";><address@hidden></a>.
+</p></dd>
+
+<dt><b><a href="#TOCReportingViolation" name="ReportingViolation">
+What should I do if I discover a possible violation of the GPL?</a></b></dt>
+
+<dd>
+You should <a href="/licenses/gpl-violation.html">report it</a>.
+First, check the facts as best you can. Then tell the publisher or
+copyright holder of the specific GPL-covered program. If that is the
+Free Software Foundation, write to <a
+href="mailto:address@hidden";><address@hidden></a>.
+Otherwise, the program's maintainer may be the copyright holder, or
+else could tell you how to contact the copyright holder, so report it
+to the maintainer.
+<p></p></dd>
+
+<dt><b><a href="#TOCWhyDoesTheGPLPermitUsersToPublishTheirModifiedVersions"
name="WhyDoesTheGPLPermitUsersToPublishTheirModifiedVersions">
+Why does the GPL permit users to publish their modified versions?</a></b></dt>
+
+<dd>
+A crucial aspect of free software is that users are free to cooperate.
+It is absolutely essential to permit users who wish to help each other
+to share their bug fixes and improvements with other users.
+<p>
+Some have proposed alternatives to the GPL that require modified
+versions to go through the original author. As long as the original
+author keeps up with the need for maintenance, this may work well in
+practice, but if the author stops (more or less) to do something else
+or does not attend to all the users' needs, this scheme falls down.
+Aside from the practical problems, this scheme does not allow users to
+help each other.</p>
+<p>
+Sometimes control over modified versions is proposed as a means of
+preventing confusion between various versions made by users. In our
+experience, this confusion is not a major problem. Many versions of
+Emacs have been made outside the GNU Project, but users can tell them
+apart. The GPL requires the maker of a version to place his or her
+name on it, to distinguish it from other versions and to protect the
+reputations of other maintainers.
+</p></dd>
+
+<dt><b><a href="#TOCGPLRequireSourcePostedPublic"
+ name="GPLRequireSourcePostedPublic">
+ Does the GPL require that source code of modified versions be
+ posted to the public?</a></b></dt>
+
+<dd>
+The GPL does not require you to release your modified version. You are
+free to make modifications and use them privately, without ever
+releasing them. This applies to organizations (including companies),
+too; an organization can make a modified version and use it internally
+without ever releasing it outside the organization.
+<p>
+But <em>if</em> you release the modified version to the public in some
+way, the GPL requires you to make the modified source code available
+to the program's users, under the GPL.</p>
+<p>
+Thus, the GPL gives permission to release the modified program in
+certain ways, and not in other ways; but the decision of whether to
+release it is up to you.
+</p></dd>
+
+<dt><b><a href="#TOCGPLAndNonfreeOnSameMachine"
name="GPLAndNonfreeOnSameMachine">
+ Can I have a GPL-covered program and an unrelated non-free program on
the same computer?</a></b></dt>
+<dd>
+Yes. The “mere aggregation” clause in the GPL makes this
+permission explicit, but that only reinforces what we believe would be
+true anyway.
+<p></p></dd>
+
+<dt><b><a href="#TOCCanIDemandACopy" name="CanIDemandACopy">If I know
+ someone has a copy of a GPL-covered program, can I demand he give
+ me a copy?</a></b></dt>
+
+<dd>
+No. The GPL gives him permission to make and redistribute copies of
+the program <em>if he chooses to do so</em>. He also has the right
+not to redistribute the program, if that is what he chooses.
+<p></p></dd>
+
+<dt><b><a href="#TOCWhatDoesWrittenOfferValid"
+ name="WhatDoesWrittenOfferValid"> What does this
+ “written offer valid for any third party” mean?
+ Does that mean everyone in the world can get the source to any
+ GPL'ed program no matter what?</a></b></dt>
+
+<dd>
+<p>If you choose to provide source through a written offer, then anybody
+who requests the source from you is entitled to receive it.</p>
+<p>
+If you commercially distribute binaries not accompanied with source
+code, the GPL says you must provide a written offer to distribute the
+source code later. When users non-commercially redistribute the
+binaries they received from you, they must pass along a copy of this
+written offer. This means that people who did not get the binaries
+directly from you can still receive copies of the source code, along with
+the written offer.</p>
+<p>
+The reason we require the offer to be valid for any third party
+is so that people who receive the binaries indirectly in that way
+can order the source code from you.
+</p></dd>
+
+<dt><b><a href="#TOCTheGPLSaysModifiedVersions"
+ name="TheGPLSaysModifiedVersions">The GPL says that modified
+ versions, if released, must be “licensed … to all
+ third parties.” Who are these third
+ parties?</a></b></dt>
+
+<dd>
+Section 2 says that modified versions you distribute must be licensed
+to all third parties under the GPL. “All third parties”
+means absolutely everyone—but this does not require you
+to <strong>do</strong> anything physically for them. It only means
+they have a license from you, under the GPL, for your version.
+<p></p></dd>
+
+<dt><b><a href="#TOCRequiredToClaimCopyright"
+ name="RequiredToClaimCopyright">Am I required to claim a copyright
+ on my modifications to a GPL-covered program?</a></b></dt>
+
+<dd>
+You are not required to claim a copyright on your changes. In most
+countries, however, that happens automatically by default, so you need to
+place your changes explicitly in the public domain if you do not want them
+to be copyrighted.
+<p>
+Whether you claim a copyright on your changes or not, either way you
+must release the modified version, as a whole, under the GPL. (<a
+href="#GPLRequireSourcePostedPublic">if you release your modified
+version at all</a>)
+</p></dd>
+
+
+<dt><b><a href="#TOCCombinePublicDomainWithGPL"
+ name="CombinePublicDomainWithGPL">If a program combines
+ public-domain code with GPL-covered code, can I take the
+ public-domain part and use it as public domain code?</a></b></dt>
+
+<dd>
+You can do that, if you can figure out which part is the public domain
+part and separate it from the rest. If code was put in the public
+domain by its developer, it is in the public domain no matter where it
+has been.
+<p></p></dd>
+
+<dt><b><a href="#TOCDoesTheGPLAllowMoney" name="DoesTheGPLAllowMoney">
+ Does the GPL allow me to sell copies of the program for
money?</a></b></dt>
+
+<dd>
+Yes, the GPL allows everyone to do this. The <a
+href="/philosophy/selling.html"> right to sell copies </a> is part of
+the definition of free software. Except in one special situation,
+there is no limit on what price you can charge. (The one exception is
+the required written offer to provide source code that must accompany
+binary-only release.)
+<p></p></dd>
+
+<dt><b><a href="#TOCDoesTheGPLAllowDownloadFee"
name="DoesTheGPLAllowDownloadFee">
+ Does the GPL allow me to
+ charge a fee for downloading the program from my site?</a></b></dt>
+
+<dd>
+Yes. You can charge any fee you wish for distributing a copy of the
+program. If you distribute binaries by download, you must provide
+“equivalent access” to download the
+source—therefore, the fee to download source may not be greater
+than the fee to download the binary.
+<p></p></dd>
+
+<dt><b><a href="#TOCDoesTheGPLAllowRequireFee"
name="DoesTheGPLAllowRequireFee">
+ Does the GPL allow me to require that anyone who receives the software
+ must pay me a fee and/or notify me?</a></b></dt>
+
+<dd>
+No. In fact, a requirement like that would make the program non-free.
+If people have to pay when they get a copy of a program, or if they
+have to notify anyone in particular, then the program is not free.
+See the <a href="/philosophy/free-sw.html">
+definition of free software</a>.
+<p>
+The GPL is a free software license, and therefore it permits people
+to use and even redistribute the software without being required to
+pay anyone a fee for doing so.
+</p></dd>
+
+<dt><b><a href="#TOCDoesTheGPLRequireAvailabilityToPublic"
+ name="DoesTheGPLRequireAvailabilityToPublic">If I
+ distribute GPL'd software for a fee, am I required to also make
+ it available to the public without a charge?</a></b></dt>
+
+<dd>
+No. However, if someone pays your fee and gets a copy, the GPL gives
+them the freedom to release it to the public, with or without a fee.
+For example, someone could pay your fee, and then put her copy on a
+web site for the general public.
+<p></p></dd>
+
+<dt><b><a href="#TOCDoesTheGPLAllowNDA" name="DoesTheGPLAllowNDA">
+ Does the GPL allow me to distribute copies under a
+ nondisclosure agreement?</a></b></dt>
+
+<dd>
+No. The GPL says that anyone who receives a copy from you has the
+right to redistribute copies, modified or not. You are not allowed to
+distribute the work on any more restrictive basis.
+<p>If someone asks you to sign an NDA for receiving GPL-covered software
+copyrighted by the FSF, please inform us immediately by writing to
+<a href="mailto:address@hidden";>address@hidden</a>.</p>
+<p>
+If the violation involves GPL-covered code that has some other copyright
+holder, please inform that copyright holder, just as you would
+for any other kind of violation of the GPL.
+</p></dd>
+
+
+<dt><b><a href="#TOCDoesTheGPLAllowModNDA" name="DoesTheGPLAllowModNDA">
+ Does the GPL allow me to distribute a modified or beta version under a
+ nondisclosure agreement?</a></b></dt>
+
+<dd>
+No. The GPL says that your modified versions must carry all the
+freedoms stated in the GPL. Thus, anyone who receives a copy of your
+version from you has the right to redistribute copies (modified or
+not) of that version. You may not distribute any version of the work
+on a more restrictive basis.
+<p></p></dd>
+
+<dt><b><a href="#TOCDevelopChangesUnderNDA" name="DevelopChangesUnderNDA">
+ Does the GPL allow me to develop a modified version under a
+ nondisclosure agreement?</a></b></dt>
+
+<dd>
+Yes. For instance, you can accept a contract to develop changes and
+agree not to release <em>your changes</em> until the client says ok.
+This is permitted because in this case no GPL-covered code is
+being distributed under an NDA.
+<p>
+You can also release your changes to the client under the GPL, but
+agree not to release them to anyone else unless the client says ok. In
+this case, too, no GPL-covered code is being distributed under an NDA,
+or under any additional restrictions.</p>
+<p>
+The GPL would give the client the right to redistribute your version.
+In this scenario, the client will probably choose not to exercise that right,
+but does <em>have</em> the right.
+</p></dd>
+
+<dt><b><a href="#TOCIWantCredit" name="IWantCredit">I want to get credit
+ for my work. I want people to know what I wrote. Can I still get
+ credit if I use the GPL?</a></b></dt>
+
+<dd>
+You can certainly get credit for the work. Part of releasing a
+program under the GPL is writing a copyright notice in your own name
+(assuming you are the copyright holder). The GPL requires all copies
+to carry an appropriate copyright notice.
+<p></p></dd>
+
+<dt><b><a href="#TOCWhyMustIInclude" name="WhyMustIInclude">Why does the GPL
+ require including a copy of the GPL with every copy of the
program?</a></b></dt>
+
+<dd>
+Including a copy of the license with the work is vital so that
+everyone who gets a copy of the program can know what his rights are.
+<p>
+It might be tempting to include a URL that refers to the license,
+instead of the license itself. But you cannot be sure that the URL
+will still be valid, five years or ten years from now. Twenty years
+from now, URLs as we know them today may no longer exist.</p>
+<p>
+The only way to make sure that people who have copies of the program
+will continue to be able to see the license, despite all the changes
+that will happen in the network, is to include a copy of the license in
+the program.
+</p></dd>
+
+<dt><b><a href="#TOCWhatIfWorkIsShort" name="WhatIfWorkIsShort">What
+ if the work is not much longer than the license itself?</a></b></dt>
+
+<dd>
+If a single program is that short, you may as well use a simple
+all-permissive license for it, rather than the GNU GPL.
+<p></p></dd>
+
+<dt><b><a href="#TOCGPLOmitPreamble"
+ name="GPLOmitPreamble">
+ Can I omit the preamble of the GPL, or the instructions
+ for how to use it on your own programs, to save space?</a></b></dt>
+<dd>
+The preamble and instructions are integral parts of the GNU GPL and
+may not be omitted. In fact, the GPL is copyrighted, and its license
+permits only verbatim copying of the entire GPL. (You can use the
+legal terms to make <a href="#ModifyGPL">another license</a> but it
+won't be the GNU GPL.)
+<p>
+The preamble and instructions add up to some 5000 characters, less
+than 1/3 of the GPL's total size. They will not make a substantial
+fractional change in the size of a software package unless the package
+itself is quite small. In that case, you may as well use a simple
+all-permissive license rather than the GNU GPL.
+</p></dd>
+
+<dt><b><a href="#TOCWhatIsCompatible" name="WhatIsCompatible">What
+ does it mean to say that two licenses are
+ “compatible”?</a></b></dt>
+
+<dd>
+In order to combine two programs (or substantial parts of them) into a
+larger work, you need to have permission to use both programs in this
+way. If the two programs' licenses permit this, they are compatible.
+If there is no way to satisfy both licenses at once, they are
+incompatible.
+<p>
+For some licenses, the way in which the combination is made may affect
+whether they are compatible—for instance, they may allow linking
+two modules together, but not allow merging their code into one
+module.</p>
+<p>
+Just to install two separate programs in the same system,
+it is not necessary that their licenses be compatible,
+because this does not combine them into a larger work.</p>
+</dd>
+
+<dt><b><a href="#TOCWhatDoesCompatMean" name="WhatDoesCompatMean">What
+does it mean to say a license is “compatible with the
+GPL”.</a></b></dt>
+
+<dd>
+It means that the other license and the GNU GPL are compatible;
+you can combine code released under the other license with code
+released under the GNU GPL in one larger program.
+<p>
+The GPL permits such a combination provided it is released under the
+GNU GPL. The other license is compatible with the GPL if it permits
+this too.
+</p></dd>
+
+
+<dt><b><a href="#TOCFSWithNFLibs" name="FSWithNFLibs">Can I write
+free software that uses non-free libraries?</a></b></dt>
+
+<dd>
+If you do this, your program won't be fully usable in a free
+environment. If your program depends on a non-free library to do a
+certain job, it cannot do that job in the Free World. If it depends on a
+non-free library to run at all, it cannot be part of a free operating
+system such as GNU; it is entirely off limits to the Free World.
+<p>
+So please consider: can you find a way to get the job done without using
+this library? Can you write a free replacement for that library?</p>
+<p>
+If the program is already written using the non-free library, perhaps it
+is too late to change the decision. You may as well release the program
+as it stands, rather than not release it. But please mention in the
+README that the need for the non-free library is a drawback, and suggest
+the task of changing the program so that it does the same job without
+the non-free library. Please suggest that anyone who thinks of doing
+substantial further work on the program first free it from dependence
+on the non-free library.</p>
+<p>
+Note that there may also be legal issues with combining certain non-free
+libraries with GPL-covered Free Software. Please see <a
+href="#GPLIncompatibleLibs">the question on GPL software with
+GPL-incompatible libraries</a> for more information.
+</p></dd>
+
+
+<dt><b><a href="#TOCGPLIncompatibleLibs" name="GPLIncompatibleLibs">What
+legal issues come up if I use GPL-incompatible libraries with GPL
+software?</a></b></dt>
+
+<dd>
+If the libraries that you link with fall within the following exception
+in the GPL:
+<blockquote><p>
+ However, as a special exception, the source code distributed need not
+ include anything that is normally distributed (in either source or
+ binary form) with the major components (compiler, kernel, and so on) of
+ the operating system on which the executable runs, unless that
+ component itself accompanies the executable.
+</p></blockquote>
+<p>
+then you don't have to do anything special to use them; the requirement
+to distribute source code for the whole program does not include those
+libraries, even if you distribute a linked executable containing them.
+Thus, if the libraries you need come with major parts of a proprietary
+operating system, the GPL says people can link your program with them
+without any conditions.
+</p><p>
+If you want your program to link against a library not covered by that
+exception, you need to add your own exception, wholly outside of the
+GPL. This copyright notice and license notice give permission to link
+with the program FOO:</p>
+
+<blockquote><p>
+ Copyright (C) yyyy <name of copyright holder>
+</p><p>
+ This program is free software; you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation; either version 2 of the License, or
+ (at your option) any later version.
+</p><p>
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+</p><p>
+ You should have received a copy of the GNU General Public License
+ along with this program; if not, write to the Free Software
+ Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
+</p>
+
+<p>Linking ABC statically or dynamically with other modules is making
+a combined work based on ABC. Thus, the terms and conditions of
+the GNU General Public License cover the whole combination.</p>
+
+<p>In addition, as a special exception, the copyright holders of ABC give
+you permission to combine ABC program with free software programs or
+libraries that are released under the GNU LGPL and with code included
+in the standard release of DEF under the XYZ license (or modified
+versions of such code, with unchanged license). You may copy and
+distribute such a system following the terms of the GNU GPL for ABC
+and the licenses of the other code concerned, provided that you
+include the source code of that other code when and as the GNU GPL
+requires distribution of source code.</p>
+
+<p>Note that people who make modified versions of ABC are not obligated
+to grant this special exception for their modified versions; it is
+their choice whether to do so. The GNU General Public License gives
+permission to release a modified version without this exception; this
+exception also makes it possible to release a modified version which
+carries forward this exception.</p>
+
+</blockquote>
+<p>
+You should put this text in each file to which the exception applies.
+</p><p>
+Only the copyright holders for the program can legally authorize this
+exception. If you wrote the whole program yourself, then assuming your
+employer or school does not claim the copyright, you are the copyright
+holder—so you can authorize the exception. But if you want to
+use parts of other GPL-covered programs by other authors in your code,
+you cannot authorize the exception for them. You have to get the
+approval of the copyright holders of those programs.
+</p><p>
+When other people modify the program, they do not have to make the same
+exception for their code—it is their choice whether to do so.
+</p><p>
+If the libraries you intend to link with are non-free, please also see
+<a href="#FSWithNFLibs">the section on writing Free Software which
+uses non-free libraries</a>.
+</p></dd>
+
+<dt><b><a href="#TOCHowIGetCopyright" name="HowIGetCopyright">How do I
+ get a copyright on my program in order to release it under the
+ GPL?</a></b></dt>
+
+<dd>
+Under the Berne Convention, everything written is automatically
+copyrighted from whenever it is put in fixed form. So you don't have
+to do anything to “get” the copyright on what you
+write—as long as nobody else can claim to own your work.
+<p>
+However, registering the copyright in the US is a very good idea. It
+will give you more clout in dealing with an infringer in the US.</p>
+<p>
+The case when someone else might possibly claim the copyright is if
+you are an employee or student; then the employer or the school might
+claim you did the job for them and that the copyright belongs to them.
+Whether they would have a valid claim would depend on circumstances
+such as the laws of the place where you live, and on your employment
+contract and what sort of work you do. It is best to consult a lawyer
+if there is any possible doubt.</p>
+<p>
+If you think that the employer or school might have a claim, you can
+resolve the problem clearly by getting a copyright disclaimer signed
+by a suitably authorized officer of the company or school. (Your
+immediate boss or a professor is usually NOT authorized to sign such a
+disclaimer.)
+</p></dd>
+
+<dt><b><a href="#TOCWhatIfSchool" name="WhatIfSchool">What if my school
+ might want to make my program into its own proprietary software
+ product?</a></b></dt>
+
+<dd>
+Many universities nowadays try to raise funds by restricting the use
+of the knowledge and information they develop, in effect behaving
+little different from commercial businesses. (See “The Kept
+University”, Atlantic Monthly, March 2000, for a general
+discussion of this problem and its effects.)
+<p>
+If you see any chance that your school might refuse to allow your
+program to be released as free software, it is best to raise the issue
+at the earliest possible stage. The closer the program is to working
+usefully, the more temptation the administration might feel to take it
+from you and finish it without you. At an earlier stage, you have
+more leverage.</p>
+<p>
+So we recommend that you approach them when the program is only
+half-done, saying, “If you will agree to releasing this as free
+software, I will finish it.” Don't think of this as a bluff. To
+prevail, you must have the courage to say, “My program will have
+liberty, or never be born.”
+</p></dd>
+
+<dt><b><a href="#TOCCouldYouHelpApplyGPL" name="CouldYouHelpApplyGPL">Could
+ you give me step by step instructions on how to apply the GPL to my
+ program?</a></b></dt>
+
+<dd>
+See the page of <a href="/licenses/gpl-howto.html">
+GPL instructions</a>.
+<p></p></dd>
+
+<dt><b><a href="#TOCHeardOtherLicense" name="HeardOtherLicense">I heard
+ that someone got a copy of a GPL'ed program under another license. Is
+ this possible?</a></b></dt>
+
+<dd>
+The GNU GPL does not give users permission to attach other licenses to
+the program. But the copyright holder for a program can release it
+under several different licenses in parallel. One of them may be the
+GNU GPL.
+<p>
+The license that comes in your copy, assuming it was put in by the
+copyright holder and that you got the copy legitimately, is the
+license that applies to your copy.
+</p></dd>
+
+<dt><b><a href="#TOCReleaseUnderGPLAndNF" name="ReleaseUnderGPLAndNF">I
+ would like to release a program I wrote under the GNU GPL, but I would
+ like to use the same code in non-free programs.</a></b></dt>
+
+<dd>
+To release a non-free program is always ethically tainted, but legally
+there is no obstacle to your doing this. If you are the copyright
+holder for the code, you can release it under various different
+non-exclusive licenses at various times.
+<p></p></dd>
+
+<dt><b><a href="#TOCDeveloperViolate" name="DeveloperViolate">Is the
+ developer of a GPL-covered program bound by the GPL? Could the
+ developer's actions ever be a violation of the GPL?</a></b></dt>
+
+<dd>
+Strictly speaking, the GPL is a license from the developer for others
+to use, distribute and change the program. The developer itself is
+not bound by it, so no matter what the developer does, this is not
+a “violation” of the GPL.
+<p>
+However, if the developer does something that would violate the GPL if
+done by someone else, the developer will surely lose moral standing in
+the community.
+</p></dd>
+
+<dt><b><a href="#TOCCanDeveloperThirdParty"
+ name="CanDeveloperThirdParty">Can the developer of a program who
+ distributed it under the GPL later license it to another party for
+ exclusive use?</a></b></dt>
+
+<dd>
+No, because the public already has the right to use the program under
+the GPL, and this right cannot be withdrawn.
+<p></p></dd>
+
+<dt><b><a href="#TOCCanIUseGPLToolsForNF"
+ name="CanIUseGPLToolsForNF">Can I use GPL-covered editors such as
+ GNU Emacs to develop non-free programs? Can I use GPL-covered tools
+ such as GCC to compile them?</a></b></dt>
+
+<dd>
+Yes, because the copyright on the editors and tools does not cover the
+code you write. Using them does not place any restrictions, legally,
+on the license you use for your code.
+<p>
+Some programs copy parts of themselves into the output for technical
+reasons—for example, Bison copies a standard parser program into
+its output file. In such cases, the copied text in the output is
+covered by the same license that covers it in the source code.
+Meanwhile, the part of the output which is derived from the program's
+input inherits the copyright status of the input.</p>
+<p>
+As it happens, Bison can also be used to develop non-free programs.
+This is because we decided to explicitly permit the use of the Bison
+standard parser program in Bison output files without restriction. We
+made the decision because there were other tools comparable to Bison
+which already permitted use for non-free programs.
+</p></dd>
+
+<dt><b><a href="#TOCGPLFairUse" name="GPLFairUse">Do I have
+ “fair use” rights in using the source code of a
+ GPL-covered program?</a></b></dt>
+
+<dd>
+Yes, you do. “Fair use” is use that is allowed without
+any special permission. Since you don't need the developers'
+permission for such use, you can do it regardless of what the
+developers said about it—in the license or elsewhere, whether
+that license be the GNU GPL or any other free software license.
+<p>
+Note, however, that there is no world-wide principle of fair use; what
+kinds of use are considered “fair” varies from country to
+country.
+</p></dd>
+
+<dt><b><a href="#TOCGPLUSGov" name="GPLUSGov">Can the US Government
+ release a program under the GNU GPL?</a></b></dt>
+<dd>
+If the program is written by US federal government employees in the
+course of their employment, it is in the public domain, which means it
+is not copyrighted. Since the GNU GPL is based on copyright, such a
+program cannot be released under the GNU GPL. (It can still be <a
+href="/philosophy/free-sw.html"> free software</a>, however; a public
+domain program is free.)
+<p>
+However, when a US federal government agency uses contractors to
+develop software, that is a different situation. The contract can
+require the contractor to release it under the GNU GPL. (GNU Ada was
+developed in this way.) Or the contract can assign the copyright to
+the government agency, which can then release the software under the
+GNU GPL. </p></dd>
+
+<dt><b><a href="#TOCGPLUSGovAdd" name="GPLUSGovAdd">Can the US Government
+ release improvements to a GPL-covered program?</a></b></dt>
+<dd>
+Yes. If the improvements are written by US government employees in
+the course of their employment, then the improvements are in the
+public domain. However, the improved version, as a whole, is still
+covered by the GNU GPL. There is no problem in this situation.
+<p>
+If the US government uses contractors to do the job, then the
+improvements themselves can be GPL-covered.
+</p></dd>
+
+<dt><b><a href="#TOCGPLOutput" name="GPLOutput">Is there some way that
+ I can GPL the output people get from use of my program? For example,
+ if my program is used to develop hardware designs, can I require that
+ these designs must be free?</a></b></dt>
+
+<dd>
+In general this is legally impossible; copyright law does not give you
+any say in the use of the output people make from their data using
+your program. If the user uses your program to enter or convert his
+own data, the copyright on the output belongs to him, not you. More
+generally, when a program translates its input into some other form,
+the copyright status of the output inherits that of the input it was
+generated from.
+<p>
+So the only way you have a say in the use of the output is if
+substantial parts of the output are copied (more or less) from text in
+your program. For instance, part of the output of Bison (see above)
+would be covered by the GNU GPL, if we had not made an exception in
+this specific case.</p>
+<p>
+You could artificially make a program copy certain text into its
+output even if there is no technical reason to do so. But if that
+copied text serves no practical purpose, the user could simply delete
+that text from the output and use only the rest. Then he would not
+have to obey the conditions on redistribution of the copied text.
+</p></dd>
+
+<dt><b><a href="#TOCWhatCaseIsOutputGPL" name="WhatCaseIsOutputGPL">In what
cases is the output of a GPL program covered by the GPL too?</a></b></dt>
+
+<dd>
+Only when the program copies part of itself into the output.
+<p></p></dd>
+
+<dt><b><a href="#TOCGPLModuleLicense" name="GPLModuleLicense">If I add
+ a module to a GPL-covered program, do I have to use the GPL as the
+ license for my module?</a></b></dt>
+
+<dd>
+The GPL says that the whole combined program has to be released under
+the GPL. So your module has to be available for use under the GPL.
+<p>
+But you can give additional permission for the use of your code. You
+can, if you wish, release your program under a license which is more
+lax than the GPL but compatible with the GPL. The
+<a href="/licenses/license-list.html">license
+list page</a> gives a partial list of GPL-compatible licenses.
+</p></dd>
+
+<dt><b><a href="#TOCIfLibraryIsGPL" name="IfLibraryIsGPL">If a library
+ is released under the GPL (not the LGPL), does that mean that any
+ program which uses it has to be under the GPL?</a></b></dt>
+
+<dd>
+Yes, because the program as it is actually run includes the library.
+<p></p></dd>
+
+<dt><b><a href="#TOCIfInterpreterIsGPL" name="IfInterpreterIsGPL">If a
+ programming language interpreter is released under the GPL, does that
+ mean programs written to be interpreted by it must be under
+ GPL-compatible licenses?</a></b></dt>
+
+<dd>
+When the interpreter just interprets a language, the answer is no. The
+interpreted program, to the interpreter, is just data; a free software
+license like the GPL, based on copyright law, cannot limit what data you
+use the interpreter on. You can run it on any data (interpreted program),
+any way you like, and there are no requirements about licensing that data
+to anyone.
+<p>However, when the interpreter is extended to provide
+“bindings” to other facilities (often, but not
+necessarily, libraries), the interpreted program is effectively linked
+to the facilities it uses through these bindings. So if these
+facilities are released under the GPL, the interpreted program that
+uses them must be released in a GPL-compatible way. The JNI or Java
+Native Interface is an example of such a binding mechanism; libraries
+that are accessed in this way are linked dynamically with the Java
+programs that call them. These libraries are also linked with the
+interpreter. If the interpreter is linked statically with these
+libraries, or if it is designed to
+<a href="#GPLPluginsInNF"> link dynamically with these specific
+libraries</a>, then it too needs to be released in a GPL-compatible
+way.</p>
+<p>
+Another similar and very common case is to provide libraries with the
+interpreter which are themselves interpreted. For instance, Perl
+comes with many Perl modules, and a Java implementation comes with
+many Java classes. These libraries and the programs that call them
+are always dynamically linked together.</p>
+<p>
+A consequence is that if you choose to use GPL'd Perl modules or Java
+classes in your program, you must release the program in a
+GPL-compatible way, regardless of the license used in the Perl or Java
+interpreter that the combined Perl or Java program will run on.
+</p></dd>
+
+<dt><b><a href="#TOCWindowsRuntimeAndGPL"
+ name="WindowsRuntimeAndGPL">I'm writing a Windows application with
+ Microsoft Visual C++ (or Visual Basic) and I will be releasing it
+ under the GPL. Is dynamically linking my program with the Visual
+ C++ (or Visual Basic) run-time library permitted under the
+ GPL?</a></b></dt>
+
+<dd>
+The GPL permits this because that run-time library normally
+accompanies the compiler or interpreter you are using. So it falls
+under the exception in GPL section 3.
+<p>
+That doesn't mean it is a good idea to write the program so that it
+only runs on Windows. Doing so results in a program that is free
+software
+but <a href="/philosophy/java-trap.html">“trapped”</a> (in
+this case, trapped by Windows instead of by Java, but the effect is
+the same). (Historical note: As of December 2006 Sun is in the middle
+of <a href="http://www.fsf.org/news/fsf-welcomes-gpl-java.html";>rereleasing
+its Java platform under GNU GPL</a>.)
+</p></dd>
+
+<dt><b><a href="#TOCOrigBSD" name="OrigBSD">Why is the original BSD
+license incompatible with the GPL?</a></b></dt>
+
+<dd>
+Because it imposes a specific requirement that is not in the GPL;
+namely, the requirement on advertisements of the program. The GPL
+states:
+<pre>
+ You may not impose any further restrictions on the recipients' exercise
+ of the rights granted herein.
+</pre>
+<p>
+The advertising clause provides just such a further restriction, and thus is
+GPL-incompatible.</p>
+<p>
+The revised BSD license does not have the advertising clause,
+which eliminates the problem.
+</p></dd>
+
+<dt><b><a href="#TOCGPLAndPlugins" name="GPLAndPlugins">If a program
+ released under the GPL uses plug-ins, what are the requirements for
+ the licenses of a plug-in?</a></b></dt>
+
+<dd>
+It depends on how the program invokes its plug-ins. If the program
+uses fork and exec to invoke plug-ins, then the plug-ins are separate
+programs, so the license for the main program makes no requirements
+for them.
+<p>
+If the program dynamically links plug-ins, and they make function
+calls to each other and share data structures, we believe they form a
+single program, which must be treated as an extension of both the main
+program and the plug-ins. This means the plug-ins must be released
+under the GPL or a GPL-compatible free software license, and that the
+terms of the GPL must be followed when those plug-ins are
+distributed.</p>
+<p>
+If the program dynamically links plug-ins, but the communication
+between them is limited to invoking the ‘main’ function of
+the plug-in with some options and waiting for it to return, that is a
+borderline case.
+</p></dd>
+
+<dt><b><a href="#TOCGPLPluginsInNF" name="GPLPluginsInNF">Can I apply the
+GPL when writing a plug-in for a non-free program?</a></b></dt>
+
+<dd>
+If the program uses fork and exec to invoke plug-ins, then the
+plug-ins are separate programs, so the license for the main program
+makes no requirements for them. So you can use the GPL for a plug-in,
+and there are no special requirements.
+<p>
+If the program dynamically links plug-ins, and they make function
+calls to each other and share data structures, we believe they form a
+single program, which must be treated as an extension of both the main
+program and the plug-ins. This means that combination of the
+GPL-covered plug-in with the non-free main program would violate the
+GPL. However, you can resolve that legal problem by adding an
+exception to your plug-in's license, giving permission to link it with
+the non-free main program.</p>
+<p>
+See also the question <a href="#FSWithNFLibs">I am
+writing free software that uses a non-free library.</a>
+</p></dd>
+
+<dt><b><a href="#TOCNFUseGPLPlugins" name="NFUseGPLPlugins">Can I
+release a non-free program that's designed to load a GPL-covered
+plug-in?</a></b></dt>
+
+<dd>
+It depends on how the program invokes its plug-ins.
+If the program uses fork and exec to invoke plug-ins, then the
+plug-ins are separate programs, so the license of the plug-in
+makes no requirements about the main program.
+<p>
+If the program dynamically links plug-ins, and they make function
+calls to each other and share data structures, we believe they form a
+single program, which must be treated as an extension of both the main
+program and the plug-ins. In order to use the GPL-covered plug-ins,
+the main program must be released under the GPL or a GPL-compatible
+free software license, and that the terms of the GPL must be followed
+when the main program is distributed for use with these plug-ins.</p>
+<p>
+If the program dynamically links plug-ins, but the communication
+between them is limited to invoking the ‘main’ function of
+the plug-in with some options and waiting for it to return, that is a
+borderline case.</p>
+<p>
+See also the question <a href="#FSWithNFLibs">I am
+writing free software that uses a non-free library.</a>
+</p></dd>
+
+<dt><b><a href="#TOCLinkingWithGPL" name="LinkingWithGPL">You have a
+ GPL'ed program that I'd like to link with my code to build a
+ proprietary program. Does the fact that I link with your program mean
+ I have to GPL my program?</a></b></dt>
+
+<dd>
+Yes.
+<p></p></dd>
+
+<dt><b><a href="#TOCSwitchToLGPL" name="SwitchToLGPL">If so, is there
+ any chance I could get a license of your program under the Lesser
+ GPL?</a></b></dt>
+
+<dd>
+You can ask, but most authors will stand firm and say no.
+The idea of the GPL is that if you want to include our code in your
+program, your program must also be free software. It is supposed
+to put pressure on you to release your program in a way that makes
+it part of our community.
+<p>
+You always have the legal alternative of not using our code.
+</p></dd>
+
+<dt><b><a href="#TOCLinkingOverControlledInterface"
+ name="LinkingOverControlledInterface">How can I allow linking of
+ proprietary modules with my GPL-covered library under a controlled
+ interface only?</a></b></dt>
+
+<dd>
+Add this text to the license notice of each file in the package, at
+the end of the text that says the file is distributed under the GNU
+GPL:
+<pre>
+
+Linking ABC statically or dynamically with other modules is making
+a combined work based on ABC. Thus, the terms and conditions of
+the GNU General Public License cover the whole combination.
+
+In addition, as a special exception, the copyright holders of ABC give
+you permission to combine ABC program with free software programs or
+libraries that are released under the GNU LGPL and with independent
+modules that communicate with ABC solely through the ABCDEF interface.
+You may copy and distribute such a system following the terms of the
+GNU GPL for ABC and the licenses of the other code concerned, provided
+that you include the source code of that other code when and as the
+GNU GPL requires distribution of source code.
+
+Note that people who make modified versions of ABC are not obligated
+to grant this special exception for their modified versions; it is
+their choice whether to do so. The GNU General Public License gives
+permission to release a modified version without this exception; this
+exception also makes it possible to release a modified version which
+carries forward this exception.
+
+</pre>
+<p>
+Only the copyright holders for the program can legally authorize this
+exception. If you wrote the whole program yourself, then assuming your
+employer or school does not claim the copyright, you are the copyright
+holder—so you can authorize the exception. But if you want to
+use parts of other GPL-covered programs by other authors in your code,
+you cannot authorize the exception for them. You have to get the
+approval of the copyright holders of those programs.
+</p><p></p></dd>
+
+<dt><b><a href="#TOCManyDifferentLicenses"
+ name="ManyDifferentLicenses">I have written an application that links
+ with many different components, that have different licenses. I am
+ very confused as to what licensing requirements are placed on my
+ program. Can you please tell me what licenses I may use?</a></b></dt>
+
+<dd>
+To answer this question, we would need to see a list of each component
+that your program uses, the license of that component, and a brief (a
+few sentences for each should suffice) describing how your library
+uses that component. Two examples would be:
+<ul>
+<li>To make my software work, it must be linked to the FOO library,
+ which is available under the Lesser GPL.</li>
+<li>My software makes a system call (with a command line that I built)
+ to run the BAR program, which is licensed under “the GPL,
+ with a special exception allowing for linking with
+ QUUX”.</li>
+</ul>
+<p></p></dd>
+
+<dt><b><a href="#TOCMereAggregation" name="MereAggregation">What is
+ the difference between “mere aggregation” and
+ “combining two modules into one program”?</a></b></dt>
+
+<dd>
+Mere aggregation of two programs means putting them side by side on
+the same CD-ROM or hard disk. We use this term in the case where they
+are separate programs, not parts of a single program. In this case,
+if one of the programs is covered by the GPL, it has no effect on the
+other program.
+<p>
+Combining two modules means connecting them together so that they form
+a single larger program. If either part is covered by the GPL, the
+whole combination must also be released under the GPL—if you
+can't, or won't, do that, you may not combine them.</p>
+<p>
+What constitutes combining two parts into one program? This is a
+legal question, which ultimately judges will decide. We believe that
+a proper criterion depends both on the mechanism of communication
+(exec, pipes, rpc, function calls within a shared address space, etc.)
+and the semantics of the communication (what kinds of information are
+interchanged).</p>
+<p>
+If the modules are included in the same executable file, they are
+definitely combined in one program. If modules are designed to run
+linked together in a shared address space, that almost surely means
+combining them into one program.</p>
+<p>
+By contrast, pipes, sockets and command-line arguments are
+communication mechanisms normally used between two separate programs.
+So when they are used for communication, the modules normally are
+separate programs. But if the semantics of the communication are
+intimate enough, exchanging complex internal data structures, that too
+could be a basis to consider the two parts as combined into a larger
+program.
+</p></dd>
+
+<dt><b><a href="#TOCAssignCopyright" name="AssignCopyright">Why does
+ the FSF require that contributors to FSF-copyrighted programs assign
+ copyright to the FSF? If I hold copyright on a GPL'ed program, should
+ I do this, too? If so, how?</a></b></dt>
+
+<dd>
+Our lawyers have told us that to be in the <a
href="/licenses/why-assign.html">best position to enforce
+the GPL</a> in court against violators, we should keep the copyright status
+of the program as simple as possible. We do this by asking each contributor
+to either assign the copyright on his contribution to the FSF, or disclaim
+copyright on it and thus put it in the public domain.
+<p>
+We also ask individual contributors to get copyright disclaimers from
+their employers (if any) so that we can be sure those employers won't
+claim to own the contributions.</p>
+<p>
+Of course, if all the contributors put their code in the public
+domain, there is no copyright with which to enforce the GPL. So we
+encourage people to assign copyright on large code contributions, and
+only put small changes in the public domain.</p>
+<p>
+If you want to make an effort to enforce the GPL on your program, it
+is probably a good idea for you to follow a similar policy. Please
+contact <a href="mailto:address@hidden";><address@hidden></a> if
+you want more information.
+</p></dd>
+
+<dt><b><a href="#TOCModifyGPL" name="ModifyGPL">Can I modify the GPL
+ and make a modified license?</a></b></dt>
+
+<dd>
+You can use the GPL terms (possibly modified) in another license
+provided that you call your license by another name and do not include
+the GPL preamble, and provided you modify the instructions-for-use at
+the end enough to make it clearly different in wording and not mention
+GNU (though the actual procedure you describe may be similar).
+<p>
+If you want to use our preamble in a modified license, please write
+to <a href="mailto:address@hidden";><address@hidden></a>
+for permission. For this purpose we would want to check the actual
+license requirements to see if we approve of them.</p>
+<p>
+Although we will not raise legal objections to your making a modified
+license in this way, we hope you will think twice and not do it. Such
+a modified license is almost certainly <a href="#WhatIsCompatible">
+incompatible with the GNU GPL</a>, and that incompatibility blocks
+useful combinations of modules. The mere proliferation of different
+free software licenses is a burden in and of itself.
+</p></dd>
+
+<dt><b><a href="#TOCGPLCommercially" name="GPLCommercially">If I use a
+ piece of software that has been obtained under the GNU GPL, am I
+ allowed to modify the original code into a new program, then
+ distribute and sell that new program commercially?</a></b></dt>
+
+<dd>
+You are allowed to sell copies of the modified program commercially,
+but only under the terms of the GNU GPL. Thus, for instance, you must
+make the source code available to the users of the program as
+described in the GPL, and they must be allowed to redistribute and
+modify it as described in the GPL.
+<p>
+These requirements are the condition for including the GPL-covered
+code you received in a program of your own.
+</p></dd>
+
+
+<dt><b><a href="#TOCGPLOtherThanSoftware"
+name="GPLOtherThanSoftware">Can I use the GPL for something other than
+software?</a></b></dt>
+
+<dd>
+You can apply the GPL to any kind of work, as long as it is clear what
+constitutes the “source code” for the work. The GPL
+defines this as the preferred form of the work for making changes in
+it.
+<p>
+However, for manuals and textbooks, or more generally any sort of work
+that is meant to teach a subject, we recommend using the GFDL rather
+than the GPL.
+</p></dd>
+
+
+<dt><b><a href="#TOCLGPLJava"
+name="LGPLJava">How does the LGPL
+ work with Java?</a></b></dt>
+
+<dd>
+
+<p><a href="/licenses/lgpl-java.html">See this article for details.</a> It
works as designed, intended, and expected.
+</p></dd>
+
+<dt><b><a href="#TOCConsider" name="Consider">Consider this situation:
+ 1. X releases V1 of a project under the GPL.
+ 2. Y contributes to the development of V2 with changes and new code
based on V1.
+ 3. X wants to convert V2 to a non-GPL license. Does X need Y's
permission?</a></b></dt>
+
+<dd>
+Yes. Y was required to release its version under the GNU GPL, as a
+consequence of basing it on X's version V1. Nothing required Y to
+agree to any other license for its code. Therefore, X must get Y's
+permission before releasing that code under another license.
+<p></p></dd>
+
+
+<dt><b><a href="#TOCGPLInProprietarySystem"
+ name="GPLInProprietarySystem">I'd like to incorporate GPL-covered
+ software in my proprietary system. Can I do this?</a></b></dt>
+
+<dd>
+You cannot incorporate GPL-covered software in a proprietary system.
+The goal of the GPL is to grant everyone the freedom to copy,
+redistribute, understand, and modify a program. If you could
+incorporate GPL-covered software into a non-free system, it would have
+the effect of making the GPL-covered software non-free too.
+<p>
+A system incorporating a GPL-covered program is an extended version of
+that program. The GPL says that any extended version of the program
+must be released under the GPL if it is released at all. This is for
+two reasons: to make sure that users who get the software get the
+freedom they should have, and to encourage people to give back
+improvements that they make.</p>
+<p>
+However, in many cases you can distribute the GPL-covered software
+alongside your proprietary system. To do this validly, you must make
+sure that the free and non-free programs communicate at arms length,
+that they are not combined in a way that would make them
+effectively a single program.</p>
+<p>
+The difference between this and “incorporating” the
+GPL-covered software is partly a matter of substance and partly form.
+The substantive part is this: if the two programs are combined so that
+they become effectively two parts of one program, then you can't treat
+them as two separate programs. So the GPL has to cover the whole
+thing.</p>
+<p>
+If the two programs remain well separated, like the compiler and the
+kernel, or like an editor and a shell, then you can treat them as two
+separate programs—but you have to do it properly. The issue is
+simply one of form: how you describe what you are doing. Why do we
+care about this? Because we want to make sure the users clearly
+understand the free status of the GPL-covered software in the
+collection.</p>
+<p>
+If people were to distribute GPL-covered software calling it
+“part of” a system that users know is partly proprietary,
+users might be uncertain of their rights regarding the GPL-covered
+software. But if they know that what they have received is a free
+program plus another program, side by side, their rights will be
+clear.
+</p></dd>
+
+<dt><b><a href="#TOCGPLWrapper" name="GPLWrapper"> I'd like to
+incorporate GPL-covered software in my proprietary system. Can I do
+this by putting a “wrapper” module, under a GPL-compatible
+lax permissive license (such as the X11 license) in between the
+GPL-covered part and the proprietary part?</a></b></dt>
+
+<dd><p>No. The X11 license is compatible with the GPL, so you can add
+a module to the GPL-covered program and put it under the X11 license.
+But if you were to incorporate them both in a larger program, that
+whole would include the GPL-covered part, so it would have to be
+licensed <em> as a whole </em> under the GNU GPL.</p>
+
+<p>The fact that proprietary module A communicates with GPL-covered
+module C only through X11-licensed module B is legally irrelevant;
+what matters is the fact that module C is included in the whole.
+</p></dd>
+
+<dt><b><a href="#TOCLibGCCException" name="LibGCCException"> Does the
+libstdc++ exception permit dynamic linking?</a></b></dt>
+
+<dd><p>Yes. The intent of the exception is to allow people to compile
+proprietary software using gcc.</p></dd>
+
+<dt><b><a href="#TOCMoneyGuzzlerInc" name="MoneyGuzzlerInc">I'd like to
+ modify GPL-covered programs and link them with the portability
+ libraries from Money Guzzler Inc. I cannot distribute the source code
+ for these libraries, so any user who wanted to change these versions
+ would have to obtained those libraries separately. Why doesn't the
+ GPL permit this?</a></b></dt>
+
+<dd>
+There are two reasons for this.
+<p>
+First, a general one. If we permitted company A to make a proprietary
+file, and company B to distribute GPL-covered software linked with
+that file, the effect would be to make a hole in the GPL big enough to
+drive a truck through. This would be carte blanche for withholding
+the source code for all sorts of modifications and extensions to
+GPL-covered software.</p>
+<p>
+Giving all users access to the source code is one of our main goals,
+so this consequence is definitely something we want to avoid.</p>
+<p>
+More concretely, the versions of the programs linked with the Money
+Guzzler libraries would not really be free software as we understand
+the term—they would not come with full source code that enables
+users to change and recompile the program.
+</p></dd>
+
+<dt><b><a href="#TOCGPLIncompatibleAlone" name="GPLIncompatibleAlone">If
+license for a module Q has a requirement that's incompatible with the GPL,
+but the requirement applies only when Q is distributed by itself, not when
+Q is included in a larger program, does that make the license
+GPL-compatible? Can I combine or link Q with a GPL-covered
+program?</a></b></dt>
+
+<dd>
+If a program P is released under the GPL that means <strong>any and
+every part of it</strong> can be used under the GPL. If you integrate
+module Q, and release the combined program P+Q under the GPL, that
+means any part of P+Q can be used under the GPL. One part of P+Q is
+Q. So releasing P+Q under the GPL says that Q any part of it can be
+used under the GPL. Putting it in other words, a user who obtains P+Q
+under the GPL can delete P, so that just Q remains, still under the
+GPL.
+<p>
+If the license of module Q permits you to give permission for that,
+then it is GPL-compatible. Otherwise, it is not GPL-compatible.</p>
+<p>
+If the license for Q says in no uncertain terms that you must do certain
+things (not compatible with the GPL) when you redistribute Q on its own,
+then it does not permit you to distribute Q under the GPL. It follows that
+you can't release P+Q under the GPL either. So you cannot link or combine
+P with Q.
+</p></dd>
+
+<dt><b><a href="#TOCModifiedJustBinary"
+ name="ModifiedJustBinary">Can I release a modified
+ version of a GPL-covered program in binary form only?</a></b></dt>
+<dd>
+No. The whole point of the GPL is that all modified versions must
+be <a href="/philosophy/free-sw.html"> free software</a>—which
+means, in particular, that the source code of the modified version is
+available to the users.
+<p></p></dd>
+
+
+<dt><b><a href="#TOCUnchangedJustBinary"
+ name="UnchangedJustBinary">I
+ downloaded just the binary from the net. If I distribute copies,
+ do I have to get the source and distribute that too?</a></b></dt>
+<dd>
+Yes. The general rule is, if you distribute binaries, you must distribute
+the complete corresponding source code too. The exception for the case
+where you received a written offer for source code is quite limited.
+<p></p></dd>
+
+<dt><b><a href="#TOCDistributeWithSourceOnInternet"
+ name="DistributeWithSourceOnInternet">I want to distribute binaries
+ via physical media without accompanying sources. Can I provide
+ source code by FTP instead of by mail order?</a></b></dt>
+
+<dd>
+You're supposed to provide the source code by mail-order on a physical
+medium, if someone orders it. You are welcome to offer people a way
+to copy the corresponding source code by FTP, in addition to the
+mail-order option, but FTP access to the source is not sufficient to
+satisfy section 3 of the GPL.
+<p>
+When a user orders the source, you have to make sure to get the source
+to that user. If a particular user can conveniently get the source
+from you by anonymous FTP, fine—that does the job. But not
+every user can do such a download. The rest of the users are just as
+entitled to get the source code from you, which means you must be
+prepared to send it to them by post.</p>
+<p>
+If the FTP access is convenient enough, perhaps no one will choose to
+mail-order a copy. If so, you will never have to ship one. But you
+cannot assume that.</p>
+<p>
+Of course, it's easiest to just send the source with the binary in the
+first place.
+</p>
+<p>If you distribute binaries via FTP, <a
+href="#AnonFTPAndSendSource">you should distribute source via FTP.</a></p>
+
+</dd>
+
+<dt><b><a href="#TOCRedistributedBinariesGetSource"
+ name="RedistributedBinariesGetSource">My friend got a GPL-covered
+ binary with an offer to supply source, and made a copy for me.
+ Can I use the offer myself to obtain the source?</a></b></dt>
+
+<dd>
+Yes, you can. The offer must be open to everyone who has a copy of
+the binary that it accompanies. This is why the GPL says your friend
+must give you a copy of the offer along with a copy of the
+binary—so you can take advantage of it.
+<p></p></dd>
+
+<dt><b><a href="#TOCSourceAndBinaryOnDifferentSites"
+ name="SourceAndBinaryOnDifferentSites">Can I put the binaries on my
+ Internet server and put the source on a different Internet
+ site?</a></b></dt>
+
+<dd>
+The GPL says you must offer access to copy the source code “from
+the same place”; that is, next to the binaries. However, if you
+make arrangements with another site to keep the necessary source code
+available, and put a link or cross-reference to the source code next
+to the binaries, we think that qualifies as “from the same
+place”.
+<p>
+Note, however, that it is not enough to find some site that happens to
+have the appropriate source code today, and tell people to look there.
+Tomorrow that site may have deleted that source code, or simply
+replaced it with a newer version of the same program. Then you would
+no longer be complying with the GPL requirements. To make a
+reasonable effort to comply, you need to make a positive arrangement
+with the other site, and thus ensure that the source will be available
+there for as long as you keep the binaries available.
+</p></dd>
+
+<dt><b><a href="#TOCDistributeExtendedBinary"
+ name="DistributeExtendedBinary">I want to distribute an extended
+ version of a GPL-covered program in binary form. Is it enough to
+ distribute the source for the original version?</a></b></dt>
+
+<dd>
+No, you must supply the source code that corresponds to the binary.
+Corresponding source means the source from which users can rebuild the
+same binary.
+<p>
+Part of the idea of free software is that users should have access to
+the source code for <strong>the programs they use</strong>. Those
+using your version should have access to the source code for your
+version.</p>
+<p>
+A major goal of the GPL is to build up the Free World by making sure
+that improvement to a free program are themselves free. If you
+release an improved version of a GPL-covered program, you must release
+the improved source code under the GPL.
+</p></dd>
+
+<dt><b><a href="#TOCDistributingSourceIsInconvenient"
+ name="DistributingSourceIsInconvenient">I want to distribute
+ binaries, but distributing complete source is inconvenient. Is it
+ ok if I give users the diffs from the “standard” version
+ along with the binaries?</a></b></dt>
+
+<dd>
+This is a well-meaning request, but this method of providing the
+source doesn't really do the job.
+<p>
+A user that wants the source a year from now may be unable to get the
+proper version from another site at that time. The standard
+distribution site may have a newer version, but the same diffs
+probably won't work with that version.</p>
+<p>
+So you need to provide complete sources, not just diffs, with
+the binaries.
+</p></dd>
+
+<dt><b><a href="#TOCAnonFTPAndSendSource"
+ name="AnonFTPAndSendSources">I want to make binaries available for
+ anonymous FTP, but send sources only to people who order them.</a></b></dt>
+
+<dd>
+<p>If you want to distribute binaries by anonymous FTP, you still have
+to provide source through one of the options listed in section 3.
+This should not be hard. You can provide a written offer for source
+if you want; section 3(b) allows this. But if you can find a site to
+distribute your program, you can surely find one that has room for the
+sources.
+</p><p>No matter how you distribute the source, the sources you
+provide must correspond exactly to the binaries. In particular, you
+must make sure they are for the same version of the program—not
+an older version and not a newer version.</p>
+<p>
+You can make the sources and binaries available on different machines,
+provided they are equally easy to get to, and provided that you have
+information next to the binaries saying where to find the sources.
+</p></dd>
+
+<dt><b><a href="#TOCHowCanIMakeSureEachDownloadGetsSource"
+ name="HowCanIMakeSureEachDownloadGetsSource">How can I make sure each
+ user who downloads the binaries also gets the source?</a></b></dt>
+
+<dd>
+You don't have to make sure of this. As long as you make the source
+and binaries available so that the users can see what's available and
+take what they want, you have done what is required of you. It is up
+to the user whether to download the source.
+<p>
+Our requirements for redistributors are intended to make sure the
+users can get the source code, not to force users to download the
+source code even if they don't want it.
+</p></dd>
+
+<dt><b><a href="#TOCUnreleasedMods" name="UnreleasedMods">A company
+ is running a modified version of a GPL'ed program on a web site.
+ Does the GPL say they must release their modified
+ sources?</a></b></dt>
+
+<dd>
+The GPL permits anyone to make a modified version and use it without
+ever distributing it to others. What this company is doing is a
+special case of that. Therefore, the company does not have to release
+the modified sources.
+<p>
+It is essential for people to have the freedom to make modifications
+and use them privately, without ever publishing those modifications.
+However, putting the program on a server machine for the public to
+talk to is hardly “private” use, so it would be legitimate
+to require release of the source code in that special case. We are
+thinking about doing something like this in GPL version 3, but we
+don't have precise wording in mind yet.</p>
+<p>
+In the mean time, you might want to use the <a
+href="http://www.affero.org/oagpl.html";>Affero GPL</a> for programs
+designed for network server use.
+</p></dd>
+
+<dt><b><a href="#TOCInternalDistribution"
+ name="InternalDistribution">Is making and using multiple copies
+ within one organization or company
+ “distribution”?</a></b></dt>
+
+<dd>
+No, in that case the organization is just making the copies for
+itself. As a consequence, a company or other organization can develop
+a modified version and install that version through its own
+facilities, without giving the staff permission to release that
+modified version to outsiders.
+<p>
+However, when the organization transfers copies to other organizations
+or individuals, that is distribution. In particular, providing copies
+to contractors for use off-site is distribution.
+</p></dd>
+
+
+<dt><b><a href="#TOCStolenCopy" name="StolenCopy"> If someone steals
+ a CD containing a version of a GPL-covered program, does the GPL
+ give him the right to redistribute that version?</a></b></dt>
+
+<dd>
+If the version has been released elsewhere, then the thief probably
+does have the right to make copies and redistribute them under the GPL,
+but if he is imprisoned for stealing the CD he may have to wait until
+his release before doing so.
+<p>
+If the version in question is unpublished and considered by a company
+to be its trade secret, then publishing it may be a violation of trade
+secret law, depending on other circumstances. The GPL does not change
+that. If the company tried to release its version and still treat it
+as a trade secret, that would violate the GPL, but if the company
+hasn't released this version, no such violation has occurred.
+</p></dd>
+
+<dt><b><a href="#TOCTradeSecretRelease"
+ name="TradeSecretRelease">What if a company distributes a copy as
+ a trade secret?</a></b></dt>
+<dd>
+If a company distributes a copy to you and claims it is a trade
+secret, the company has violated the GPL and will have to cease
+distribution. Note how this differs from the theft case above; the
+company does not intentionally distribute a copy when a copy is
+stolen, so in that case the company has not violated the GPL.
+<p></p></dd>
+
+<dt><b><a href="#TOCWhySomeGPLAndNotLGPL"
+ name="WhySomeGPLAndNotLGPL">Why are some GNU libraries released under
+ the ordinary GPL rather than the Lesser GPL?</a></b></dt>
+
+<dd>
+Using the Lesser GPL for any particular library constitutes a retreat
+for free software. It means we partially abandon the attempt to
+defend the users' freedom, and some of the requirements to share what
+is built on top of GPL-covered software. In themselves, those are
+changes for the worse.
+<p>
+Sometimes a localized retreat is a good strategy. Sometimes, using
+the LGPL for a library might lead to wider use of that library, and
+thus to more improvement for it, wider support for free software, and
+so on. This could be good for free software if it happens to a large
+extent. But how much will this happen? We can only speculate.</p>
+<p>
+It would be nice to try out the LGPL on each library for a while, see
+whether it helps, and change back to the GPL if the LGPL didn't help.
+But this is not feasible. Once we use the LGPL for a particular
+library, changing back would be difficult.</p>
+<p>
+So we decide which license to use for each library on a case-by-case
+basis. There is a <a href="/licenses/why-not-lgpl.html">
+long explanation</a> of how we judge the question.
+</p></dd>
+
+<dt><b><a href="#TOCWillYouMakeAnException"
+ name="WillYouMakeAnException">Using a certain GNU program under the
+ GPL does not fit our project to make proprietary software. Will you
+ make an exception for us? It would mean more users of that
+ program.</a></b></dt>
+
+<dd>
+Sorry, we don't make such exceptions. It would not be right.
+<p>
+Maximizing the number of users is not our aim. Rather, we are trying
+to give the crucial freedoms to as many users as possible. In
+general, proprietary software projects hinder rather than help the
+cause of freedom.</p>
+<p>
+We do occasionally make license exceptions to assist a project which
+is producing free software under a license other than the GPL.
+However, we have to see a good reason why this will advance the cause
+of free software.</p>
+<p>
+We also do sometimes change the distribution terms of a package, when
+that seems clearly the right way to serve the cause of free software;
+but we are very cautious about this, so you will have to show us very
+convincing reasons.
+</p></dd>
+
+<dt><b><a href="#TOCVersionTwoOrLater" name="VersionTwoOrLater">Why
+should programs say “Version 2 of the GPL or any later
+version”?</a></b></dt>
+
+<dd>
+From time to time, at intervals of years, we change the
+GPL—sometimes to clarify it, sometimes to permit certain kinds
+of use not previously permitted, and sometimes to tighten up a
+requirement. (The last change was in 1991.) Using this
+“indirect pointer” in each program makes it possible for
+us to change the distribution terms on the entire collection of GNU
+software, when we update the GPL.
+<p>
+If each program lacked the indirect pointer, we would be forced to
+discuss the change at length with numerous copyright holders, which
+would be a virtual impossibility. In practice, the chance of having
+uniform distribution terms for GNU software would be nil.</p>
+<p>
+Suppose a program says “Version 2 of the GPL or any later
+version” and a new version of the GPL is released. If the new
+GPL version gives additional permission, that permission will be
+available immediately to all the users of the program. But if the new
+GPL version has a tighter requirement, it will not restrict use of the
+current version of the program, because it can still be used under GPL
+version 2. When a program says “Version 2 of the GPL or any
+later version”, users will always be permitted to use it, and
+even change it, according to the terms of GPL version 2—even
+after later versions of the GPL are available.</p>
+<p>
+If a tighter requirement in a new version of the GPL need not be
+obeyed for existing software, how is it useful? Once GPL version 3 is
+available, the developers of most GPL-covered programs will release
+subsequent versions of their programs specifying “Version 3 of
+the GPL or any later version”. Then users will have to follow
+the tighter requirements in GPL version 3, for subsequent versions of
+the program.</p>
+<p>
+However, developers are not obligated to do this; developers can
+continue allowing use of the previous version of the GPL, if that is
+their preference.
+</p></dd>
+
+
+<dt><b><a href="#TOCWhyNotGPLForManuals" name="WhyNotGPLForManuals">Why
+don't you use the GPL for manuals?</a></b></dt>
+
+<dd>
+It is possible to use the GPL for a manual, but the GNU Free
+Documentation License (GFDL) is much better for manuals.
+<p>
+The GPL was designed for programs; it contains lots of complex clauses
+that are crucial for programs, but that would be cumbersome and
+unnecessary for a book or manual. For instance, anyone publishing the
+book on paper would have to either include machine-readable
+“source code” of the book along with each printed copy, or
+provide a written offer to send the “source code”
+later.</p>
+<p>
+Meanwhile, the GFDL has clauses that help publishers of free manuals
+make a profit from selling copies—cover texts, for instance.
+The special rules for Endorsements sections make it possible to use
+the GFDL for an official standard. This would permit modified
+versions, but they could not be labeled as “the
+standard”.</p>
+<p>
+Using the GFDL, we permit changes in the text of a manual that covers
+its technical topic. It is important to be able to change the
+technical parts, because people who change a program ought to change
+the documentation to correspond. The freedom to do this is an
+ethical imperative.</p>
+<p>
+Our manuals also include sections that state our political position
+about free software. We mark these as “invariant”, so
+that they cannot be changed or removed. The GFDL makes provisions for
+these “invariant sections”.
+</p></dd>
+
+
+<dt><b><a href="#TOCFontException" name="FontException">How does the
+GPL apply to fonts?</a></b></dt>
+
+<dd>
+Font licensing is a complex issue which needs serious consideration.
+The following license exception is experimental but approved for
+general use. We welcome suggestions on this subject—please see
+this <a href="http://www.fsf.org/blogs/licensing/20050425novalis";>explanatory
+essay</a> and write to
+<a href="mailto:address@hidden";><address@hidden></a>.
+
+<p>
+To use this exception, add this text to the license notice of each
+file in the package (to the extent possible), at the end of the text
+that says the file is distributed under the GNU GPL:</p>
+<p>
+<tt>
+As a special exception, if you create a document which uses
+this font, and embed this font or unaltered portions of this font into
+the document, this font does not by itself cause the resulting
+document to be covered by the GNU General Public License. This
+exception does not however invalidate any other reasons why the
+document might be covered by the GNU General Public License. If you
+modify this font, you may extend this exception to your version of the
+font, but you are not obligated to do so. If you do not wish to do so,
+delete this exception statement from your version.
+</tt>
+</p></dd>
+
+
+<dt><b><a href="#TOCWMS" name="WMS"> I am writing a website
+maintenance system</a> (called a
+“<a href="/philosophy/words-to-avoid.html">content management
+system</a>” by some), or some other application which generates
+web pages from templates. What license should I use for those
+templates?</b></dt>
+
+<dd>
+<p>Templates are minor enough that it is not worth using copyleft to
+protect them. It is normally harmless to use copyleft on minor works,
+but templates are a special case, because they are combined with data
+provided by users of the application and the combination is
+distributed. So, we recommend that you license your templates under
+simple permissive terms. </p>
+
+<p>Some templates make calls into Javascript functions. Since
+Javascript is often non-trivial, it is worth copylefting. Because the
+templates will be combined with user data, it's possible that
+template+user data+Javascript would be considered one work under
+copyright law. A line needs to be drawn between the Javascript
+(copylefted), and the user code
+(usually under incompatible terms). </p>
+
+<p><a href="/licenses/template-diagram.png"><img
src="/licenses/template-diagram.png" alt="A diagram of the above content"
/></a></p>
+
+<p>Here's an exception for Javascript code that does this:</p>
+
+<blockquote><p>As a special exception to GPL, any HTML file which merely makes
+function calls to this code, and for that purpose includes it by
+reference shall be deemed a separate work for copyright law purposes.
+In addition, the copyright holders of this code give you permission to
+combine this code with free software libraries that are released under
+the GNU LGPL. You may copy and distribute such a system following the
+terms of the GNU GPL for this code and the LGPL for the libraries. If
+you modify this code, you may extend this exception to your version of
+the code, but you are not obligated to do so. If you do not wish to do
+so, delete this exception statement from your version.
+</p></blockquote>
+
+</dd>
+
+<dt><b><a href="#TOCNonFreeTools" name="NonFreeTools">Can I release
+ a program under the GPL which I developed using non-free
tools?</a></b></dt>
+
+<dd>
+Which programs you used to edit the source code, or to compile it, or
+study it, or record it, usually makes no difference for issues
+concerning the licensing of that source code.
+
+<p>
+However, if you link non-free libraries with the source code, that
+would be an issue you need to deal with. It does not preclude
+releasing the source code under the GPL, but if the libraries don't
+fit under the “system library” exception, you should affix
+an explicit notice giving permission to link your program with them.
+The FSF can give you advice on doing this.</p>
+</dd>
+
+
+<dt><b><a href="#TOCGPLTranslations" name="GPLTranslations">Are there
+translations of the GPL into other languages?</a></b></dt>
+
+<dd>
+It would be useful to have translations of the GPL into languages
+other than English. People have even written translations and sent
+them to us. But we have not dared to approve them as officially
+valid. That carries a risk so great we do not dare accept it.
+<p>
+A legal document is in some ways like a program. Translating it is
+like translating a program from one language and operating system to
+another. Only a lawyer skilled in both languages can do it—and
+even then, there is a risk of introducing a bug.</p>
+<p>
+If we were to approve, officially, a translation of the GPL, we would
+be giving everyone permission to do whatever the translation says they
+can do. If it is a completely accurate translation, that is fine.
+But if there is an error in the translation, the results could be a
+disaster which we could not fix.</p>
+<p>
+If a program has a bug, we can release a new version, and eventually
+the old version will more or less disappear. But once we have given
+everyone permission to act according to a particular translation, we
+have no way of taking back that permission if we find, later on, that
+it had a bug.</p>
+<p>
+Helpful people sometimes offer to do the work of translation for us.
+If the problem were a matter of finding someone to do the work, this
+would solve it. But the actual problem is the risk of error, and
+offering to do the work does not avoid the risk. We could not
+possibly authorize a translation written by a non-lawyer.</p>
+<p>
+Therefore, for the time being, we are not approving translations
+of the GPL as globally valid and binding. Instead, we are doing two
+things:</p>
+<ul>
+<li> Referring people to unofficial translations.
+This means that we permit people to write translations of the GPL, but
+we don't approve them as legally valid and binding.
+<p>
+An unapproved translation has no legal force, and it should say so
+explicitly. It should be marked as follows:</p>
+<pre>
+ This translation of the GPL is informal, and not officially approved
+ by the Free Software Foundation as valid. To be completely sure of
+ what is permitted, refer to the original GPL (in English).
+</pre>
+<p>
+But the unapproved translation can serve as a hint for how to
+understand the English GPL. For many users, that is sufficient.</p>
+<p>
+However, businesses using GNU software in commercial activity, and
+people doing public ftp distribution, should need to check the real
+English GPL to make sure of what it permits.</p>
+</li>
+<li>
+Publishing translations valid for a single country only.
+<p>
+We are considering the idea of publishing translations which are
+officially valid only for one country. This way, if there is a
+mistake, it will be limited to that country, and the damage will not
+be too great.</p>
+<p>
+It will still take considerable expertise and effort from a sympathetic
+and capable lawyer to make a translation, so we cannot promise any
+such translations soon.</p>
+</li>
+</ul>
+<p></p></dd>
+
+<dt><b><a href="#TOCInterpreterIncompat" name="InterpreterIncompat">If
+a programming language interpreter has a license that is incompatible
+with the GPL, can I run GPL-covered programs on it?</a></b></dt>
+
+<dd>
+When the interpreter just interprets a language, the answer is yes.
+The interpreted program, to the interpreter, is just data; the GPL
+doesn't restrict what tools you process the program with.
+<p>
+However, when the interpreter is extended to provide
+“bindings” to other facilities (often, but not
+necessarily, libraries), the interpreted program is effectively linked
+to the facilities it uses through these bindings. The JNI or Java
+Native Interface is an example of such a facility; libraries that are
+accessed in this way are linked dynamically with the Java programs
+that call them.</p>
+<p>
+So if these facilities are released under a GPL-incompatible license,
+the situation is like linking in any other way with a GPL-incompatible
+library. Which implies that:</p>
+<ol>
+ <li>If you are writing code and releasing it under the GPL, you can
+ state an explicit exception giving permission to link it with those
+ GPL-incompatible facilities.</li>
+
+ <li>If you wrote and released the program under the GPL, and you
+ designed it specifically to work with those facilities, people can
+ take that as an implicit exception permitting them to link it with
+ those facilities. But if that is what you intend, it is better
+ to say so explicitly.</li>
+
+ <li>You can't take someone else's GPL-covered code and use it that
+ way, or add such exceptions to it. Only the copyright holders of that
+ code can add the exception.</li>
+</ol>
+<p></p></dd>
+
+<dt><b><a href="#TOCWhoHasThePower" name="WhoHasThePower">Who has the
+power to enforce the GPL?</a></b></dt>
+
+<dd>
+Since the GPL is a copyright license, the copyright holders of the
+software are the ones who have the power to enforce the GPL. If you
+see a violation of the GPL, you should inform the developers of the
+GPL-covered software involved. They either are the copyright holders,
+or are connected with the copyright holders. <a
+href="http://www.fsf.org/licenses/gpl-faq.html#ReportingViolation";>Learn
+more about reporting GPL violations.</a>
+<p></p></dd>
+
+
+<dt><b><a href="#TOCOOPLang" name="OOPLang"> In an object-oriented
+language such as Java, if I use a class that is GPL'ed without
+modifying, and subclass it, in what way does the GPL affect the larger
+program?</a></b></dt>
+
+<dd>
+Subclassing is creating a derivative work. Therefore, the terms of the
+GPL affect the whole program where you create a subclass of a GPL'ed
+class.
+<p></p></dd>
+
+<dt><b><a href="#TOCPortProgramToGL" name="PortProgramToGL">If I port
+my program to GNU/Linux, does that mean I have to release it as Free
+Software under the GPL or some other Free Software license?</a></b></dt>
+
+<dd>
+In general, the answer is no—this is not a legal requirement.
+In specific, the answer depends on which libraries you want to use and
+what their licenses are. Most system libraries either use
+the <a href="/copyleft/lesser.html">GNU Lesser GPL</a>, or use the GNU
+GPL plus an exception permitting linking the library with anything.
+These libraries can be used in non-free programs; but in the case of
+the Lesser GPL, it does have some requirements you must follow.
+<p>
+Some libraries are released under the GNU GPL alone; you must use a
+GPL-compatible license to use those libraries. But these are normally
+the more specialized libraries, and you would not have had anything much
+like them on another platform, so you probably won't find yourself
+wanting to use these libraries for simple porting.</p>
+<p>
+Of course, your software is not a contribution to our community if it is
+not free, and people who value their freedom will refuse to use it.
+Only people willing to give up their freedom will use your software,
+which means that it will effectively function as an inducement for people
+to lose their freedom.</p>
+<p>
+If you hope some day to look back on your career and feel that
+it has contributed to the growth of a good and free society, you
+need to make your software free.
+</p></dd>
+
+<dt><b><a href="#TOCCompanyGPLCostsMoney" name="CompanyGPLCostsMoney">
+I just found out that a company has a copy of a GPL'ed program, and it
+costs money to get it. Aren't they violating the GPL by not making it
+available on the Internet?</a></b></dt>
+
+<dd>
+No. The GPL does not require anyone to use the Internet for
+distribution. It also does not require anyone in particular to
+redistribute the program. And (outside of one special case), even if
+someone does decide to redistribute the program sometimes, the GPL
+doesn't say he has to distribute a copy to you in particular, or any
+other person in particular.
+<p>
+What the GPL requires is that he must have the freedom to distribute a
+copy to you <em>if he wishes to</em>. Once the copyright holder does
+distribute a copy program to someone, that someone can then redistribute
+the program to you, or to anyone else, as he sees fit.
+</p></dd>
+
+<dt><b><a href="#TOCReleaseNotOriginal" name="ReleaseNotOriginal"> Can
+I release a program with a license which says that you can distribute
+modified versions of it under the GPL but you can't distribute the
+original itself under the GPL?</a></b></dt>
+
+<dd>
+No. Such a license would be self-contradictory. Let's look at its
+implications for me as a user.
+<p>
+Suppose I start with the original version (call it version A), add
+some code (let's imagine it is 1000 lines), and release that modified
+version (call it B) under the GPL. The GPL says anyone can change
+version B again and release the result under the GPL. So I (or
+someone else) can delete those 1000 lines, producing version C which
+has the same code as version A but is under the GPL.</p>
+<p>
+If you try to block that path, by saying explicitly in the license that
+I'm not allowed to reproduce something identical to version A under
+the GPL by deleting those lines from version B, in effect the license
+now says that I can't fully use version B in all the ways that the GPL
+permits. In other words, the license does not in fact allow a user to
+release a modified version such as B under the GPL.
+</p>
+</dd>
+
+<dt><b><a href="#TOCDistributeSubsidiary" name="DistributeSubsidiary"> Does
moving a copy to a
+majority-owned, and controlled, subsidiary constitute
+distribution?</a></b></dt>
+<dd>
+<p>
+Whether moving a copy to or from this subsidiary constitutes
+'distribution' is a matter to be decided in each case under the
+copyright law of the appropriate jurisdiction. The GPL does not
+and cannot override local laws. US copyright law is not entirely
+clear on the point, but appears not to consider this distribution.
+</p><p>
+If, in some country, this is considered distribution, and the
+subsidiary must receive the right to redistribute the program,
+that will not make a practical difference. The subsidiary is
+controlled by the parent company; rights or no rights, it won't
+redistribute the program unless the parent company decides to do
+so.
+</p>
+</dd>
+
+<dt><b><a href="#TOCClickThrough" name="ClickThrough"> Can software installers
ask people
+ to click to agree to the GPL? If I get some software under the GPL,
+ do I have to agree to anything?</a></b></dt>
+<dd>
+<p>
+Some software packaging systems have a place which requires you to
+click through or otherwise indicate assent to the terms of the GPL.
+This is neither required nor forbidden. With or without a click
+through, the GPL's rules remain the same. </p>
+
+<p>
+Merely agreeing to the GPL doesn't place any obligations on you. You
+are not required to agree to anything to merely use software which is
+licensed under the GPL. You only have obligations if you modify or
+distribute the software. If it really bothers you to click through
+the GPL, nothing stops you from hacking the GPLed software to bypass this.
+</p>
+</dd>
+
+<dt><b><a href="#TOCGPLCompatInstaller" name="GPLCompatInstaller">I would
+ like to bundle GPLed software with some sort of installation software.
+ Does that installer need to have a GPL-compatible license?</a></b></dt>
+<dd>
+<p>No. The installer and the files it installs are separate works. As a
+result, the terms of the GPL do not apply to the installation software.</p>
+</dd>
+
+</dl>
+
+</div>
+
+<!--#include virtual="/server/footer.html" -->
+
+<div id="footer">
+<p>
+Please send FSF & GNU inquiries to
+<a href="mailto:address@hidden";><em>address@hidden</em></a>.
+There are also <a href="/contact/">other ways to contact</a>
+the FSF.
+<br />
+Please send broken links and other corrections or suggestions to
+<a href="mailto:address@hidden";><em>address@hidden</em></a>.
+</p>
+
+<p>
+Please see the
+<a href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting
+translations of this article.
+</p>
+
+<p>
+Copyright © 2001, 2006, 2007, 2008 Free Software Foundation,
+Inc.,</p>
+<address>51 Franklin St, Fifth Floor, Boston, MA 02110, USA</address>
+<p>This page is licensed under a <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/";>Creative
+Commons Attribution-NoDerivs 3.0 United States License</a>.
+</p>
+
+<p>
+Updated:
+<!-- timestamp start -->
+$Date: 2012/06/05 08:28:04 $
+<!-- timestamp end -->
+</p>
+</div>
+
+</div>
+</body>
+</html>