[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www/licenses/old-licenses gpl-2.0-faq.ru.html p...
From: |
GNUN |
Subject: |
www/licenses/old-licenses gpl-2.0-faq.ru.html p... |
Date: |
Sat, 11 Mar 2017 05:59:58 -0500 (EST) |
CVSROOT: /web/www
Module name: www
Changes by: GNUN <gnun> 17/03/11 05:59:58
Modified files:
licenses/old-licenses: gpl-2.0-faq.ru.html
licenses/old-licenses/po: gpl-2.0-faq.ru-en.html
gpl-2.0-faq.ru.po
Log message:
Automatic update by GNUnited Nations.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/old-licenses/gpl-2.0-faq.ru.html?cvsroot=www&r1=1.40&r2=1.41
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/old-licenses/po/gpl-2.0-faq.ru-en.html?cvsroot=www&r1=1.31&r2=1.32
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/old-licenses/po/gpl-2.0-faq.ru.po?cvsroot=www&r1=1.47&r2=1.48
Patches:
Index: gpl-2.0-faq.ru.html
===================================================================
RCS file: /web/www/www/licenses/old-licenses/gpl-2.0-faq.ru.html,v
retrieving revision 1.40
retrieving revision 1.41
diff -u -b -r1.40 -r1.41
--- gpl-2.0-faq.ru.html 17 Feb 2017 06:30:23 -0000 1.40
+++ gpl-2.0-faq.ru.html 11 Mar 2017 10:59:57 -0000 1.41
@@ -368,6 +368,9 @@
модÑÐ»Ñ Ðº пÑогÑамме под GPL, ÑÑебÑеÑÑÑ Ð»Ð¸ оÑ
Ð¼ÐµÐ½Ñ Ð¸ÑполÑзование GPL в
каÑеÑÑве лиÑензии Ð´Ð»Ñ Ð¼Ð¾ÐµÐ³Ð¾ модÑлÑ?</a></li>
+ <li><a href="#GPLPlugins" name="TOCGPLPlugins"> Ðогда
пÑогÑамма и ее внеÑние
+модÑли ÑÑиÑаÑÑÑÑ ÐµÐ´Ð¸Ð½Ð¾Ð¹ комбиниÑованной
пÑогÑаммой?</a></li>
+
<li><a href="#GPLAndPlugins" name="TOCGPLAndPlugins">ÐÑли
пÑогÑамма, вÑпÑÑеннаÑ
под GPL, полÑзÑеÑÑÑ Ð²Ð½ÐµÑними модÑлÑми,
ÐºÐ°ÐºÐ¾Ð²Ñ ÑÑÐµÐ±Ð¾Ð²Ð°Ð½Ð¸Ñ Ðº лиÑензиÑм
модÑлÑ?</a></li>
@@ -474,7 +477,7 @@
лиÑензий ÑаÑпÑоÑÑÑанена СÑандаÑÑнаÑ
обÑеÑÑÐ²ÐµÐ½Ð½Ð°Ñ Ð»Ð¸ÑÐµÐ½Ð·Ð¸Ñ GNU, коÑоÑко
обознаÑÐ°ÐµÐ¼Ð°Ñ ÐºÐ°Ðº “GNU GPL”. ÐÑо
вÑÑажение можно далÑÑе ÑокÑаÑиÑÑ
до “GPL”, когда ÑÑно, ÑÑо имееÑÑÑ Ð² видÑ
именно GNU GPL.
-<p></p></dd>
+</dd>
<dt><a href="#TOCDoesFreeSoftwareMeanUsingTheGPL"
name="DoesFreeSoftwareMeanUsingTheGPL">ÐодÑазÑÐ¼ÐµÐ²Ð°ÐµÑ Ð»Ð¸
вÑÑажение
@@ -486,7 +489,7 @@
лиÑензиÑ, коÑоÑÐ°Ñ Ð¿ÑедоÑÑавлÑеÑ
полÑзоваÑÐµÐ»Ñ <a
href="/philosophy/free-sw.html">опÑеделеннÑе оÑобÑе
ÑвободÑ</a>, ÑвлÑеÑÑÑ
лиÑензией ÑвободнÑÑ
пÑогÑамм.
-<p></p></dd>
+</dd>
<dt><a href="#TOCWhyUseGPL" name="WhyUseGPL">ÐоÑÐµÐ¼Ñ Ð¼Ð½Ðµ
ÑледÑÐµÑ Ð¿ÑименÑÑÑ GNU
GPL, а не дÑÑгие лиÑензии ÑвободнÑÑ
пÑогÑамм?</a></dt>
@@ -498,7 +501,7 @@
ваÑей ÑобÑÑвенной ÑабоÑÑ. Ðднако в
некоÑоÑÑÑ
оÑобÑÑ
ÑиÑÑаÑиÑÑ
Ð¼Ð¾Ð¶ÐµÑ Ð±ÑÑÑ
лÑÑÑе полÑзоваÑÑÑÑ <a
href="/licenses/why-not-lgpl.html">более либеÑалÑной
лиÑензией</a>.
-<p></p></dd>
+</dd>
<dt><a href="#TOCDoesAllGNUSoftwareUseTheGNUGPLAsItsLicense"
name="DoesAllGNUSoftwareUseTheGNUGPLAsItsLicense">ÐÑе ли
пÑогÑÐ°Ð¼Ð¼Ñ GNU
@@ -509,7 +512,7 @@
пÑогÑамм GNU (и ÑаÑÑей пÑогÑамм), коÑоÑÑе
полÑзÑÑÑÑÑ Ð¼ÐµÐ½ÐµÐµ ÑлабÑми
лиÑензиÑми, Ñакими, как ÐенÑÑÐ°Ñ GPL. Ðогда мÑ
Ñак поÑÑÑпаем, ÑÑо вопÑÐ¾Ñ <a
href="/licenses/why-not-lgpl.html">ÑÑÑаÑегии</a>.
-<p></p></dd>
+</dd>
<dt><a href="#TOCDoesUsingTheGPLForAProgramMakeItGNUSoftware"
name="DoesUsingTheGPLForAProgramMakeItGNUSoftware">ÐÑли длÑ
пÑогÑаммÑ
@@ -538,7 +541,7 @@
РпÑоÑивном ÑлÑÑае ÑоÑ, кÑо поддеÑживаеÑ
пÑогÑаммÑ, Ð¼Ð¾Ð¶ÐµÑ Ð±ÑÑÑ
пÑавообладаÑелем или знаÑÑ, как Ñ Ð½Ð¸Ð¼
ÑвÑзаÑÑÑÑ, Ñак ÑÑо пÑиÑлиÑе оÑÑеÑ
ÑомÑ, кÑо поддеÑÐ¶Ð¸Ð²Ð°ÐµÑ Ð¿ÑогÑаммÑ.
-<p></p></dd>
+</dd>
<dt><a href="#TOCWhyDoesTheGPLPermitUsersToPublishTheirModifiedVersions"
name="WhyDoesTheGPLPermitUsersToPublishTheirModifiedVersions">ÐоÑÐµÐ¼Ñ GPL
@@ -592,7 +595,7 @@
Ðа. ÐÑÐ½ÐºÑ GPL о “пÑоÑÑом ÑазмеÑении”
Ð´ÐµÐ»Ð°ÐµÑ ÑÑо ÑазÑеÑение
ÑвнÑм, но ÑÑо ÑолÑко подÑвеÑÐ¶Ð´Ð°ÐµÑ Ñо, ÑÑо,
по наÑÐµÐ¼Ñ ÑбеждениÑ, бÑло бÑ
веÑно в лÑбом ÑлÑÑае.
-<p></p></dd>
+</dd>
<dt><a href="#TOCCanIDemandACopy" name="CanIDemandACopy">ÐÑли Ñ Ð·Ð½Ð°Ñ,
ÑÑо Ñ
кого-Ñо еÑÑÑ ÐºÐ¾Ð¿Ð¸Ñ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL, Ð¼Ð¾Ð³Ñ Ð»Ð¸
Ñ ÑÑебоваÑÑ, ÑÑÐ¾Ð±Ñ Ð¾Ð½ дал мне
@@ -601,7 +604,7 @@
<dd>
ÐеÑ. GPL Ð´Ð°ÐµÑ ÐµÐ¼Ñ ÑазÑеÑение ÑоздаваÑÑ Ð¸
ÑаÑпÑоÑÑÑанÑÑÑ ÐºÐ¾Ð¿Ð¸Ð¸ пÑогÑаммÑ,
<em>еÑли он ÑеÑÐ¸Ñ ÑÑо делаÑÑ</em>. У него еÑÑÑ
Ñакже пÑаво не ÑаÑпÑоÑÑÑанÑÑÑ
-пÑогÑаммÑ, еÑли Ñаково его ÑеÑение.<p></p></dd>
+пÑогÑаммÑ, еÑли Ñаково его ÑеÑение.</dd>
<dt><a href="#TOCWhatDoesWrittenOfferValid"
name="WhatDoesWrittenOfferValid">ЧÑо
ознаÑÐ°ÐµÑ Ð² GPL веÑÑии 2 “пиÑÑменное
пÑедложение, дейÑÑвиÑелÑное
@@ -637,7 +640,7 @@
ÑÑеÑÑи ÑÑоÑонє ознаÑаÑÑ Ð°Ð±ÑолÑÑно вÑеÑ
— но ÑÑо не ÑÑебÑеÑ
Ð¾Ñ Ð²Ð°Ñ <strong>делаÑÑ</strong> Ð´Ð»Ñ Ð½Ð¸Ñ
ÑÑо-Ñо
ÑизиÑеÑки. ÐÑо ÑолÑко знаÑиÑ,
ÑÑо Ð²Ñ Ð´Ð°Ð»Ð¸ им ÑазÑеÑение пÑименÑÑÑ Ð²Ð°ÑÑ
веÑÑÐ¸Ñ Ð¿Ð¾ GPL.
-<p></p></dd>
+</dd>
<dt><a href="#TOCRequiredToClaimCopyright"
name="RequiredToClaimCopyright">ТÑебÑеÑÑÑ Ð»Ð¸ Ð¾Ñ Ð¼ÐµÐ½Ñ
заÑвление авÑоÑÑкиÑ
@@ -667,7 +670,7 @@
обÑеÑÑÐ²ÐµÐ½Ð½Ð¾Ð¼Ñ Ð´Ð¾ÑÑоÑниÑ, и оÑделиÑÑ ÐµÐµ оÑ
оÑÑалÑного. ÐÑли ÑекÑÑ Ð¿Ð¾Ð¼ÐµÑен в
обÑеÑÑвенное доÑÑоÑние его ÑазÑабоÑÑиком,
он оÑÑаеÑÑÑ Ð² обÑеÑÑвенном
доÑÑоÑнии незавиÑимо Ð¾Ñ Ñого, где он
побÑвал.
-<p></p></dd>
+</dd>
<dt><a href="#TOCDoesTheGPLAllowMoney"
name="DoesTheGPLAllowMoney">ÐозволÑÐµÑ Ð»Ð¸
мне GPL пÑодаваÑÑ ÐºÐ¾Ð¿Ð¸Ð¸ пÑогÑÐ°Ð¼Ð¼Ñ Ð·Ð°
денÑги?</a></dt>
@@ -679,7 +682,7 @@
не налагаеÑÑÑ Ð¾Ð³ÑаниÑений (ÑÑо
единÑÑвенное иÑклÑÑение —
обÑзаÑелÑное пиÑÑменное пÑедложение
поÑÑавки иÑÑ
одного ÑекÑÑа, коÑоÑое
должно ÑопÑовождаÑÑ Ð²ÑпÑÑк ÑолÑко
двоиÑнÑÑ
Ñайлов).
-<p></p></dd>
+</dd>
<dt><a href="#TOCDoesTheGPLAllowDownloadFee"
name="DoesTheGPLAllowDownloadFee">ÐозволÑÐµÑ Ð»Ð¸ мне GPL
бÑаÑÑ Ð¿Ð»Ð°ÑÑ Ð·Ð°
@@ -691,7 +694,7 @@
пÑедоÑÑавиÑÑ “ÑквиваленÑнÑй доÑÑÑп”
Ð´Ð»Ñ Ð¿Ð¾Ð»ÑÑÐµÐ½Ð¸Ñ Ð¸ÑÑ
одного
ÑекÑÑа — ÑледоваÑелÑно, плаÑа за
полÑÑение по ÑеÑи иÑÑ
одного
ÑекÑÑа не должна бÑÑÑ Ð±Ð¾Ð»ÑÑе, Ñем плаÑа за
полÑÑение двоиÑнÑÑ
Ñайлов.
-<p></p></dd>
+</dd>
<dt><a href="#TOCDoesTheGPLAllowRequireFee"
name="DoesTheGPLAllowRequireFee">ÐозволÑÐµÑ Ð»Ð¸ мне GPL
ÑÑебоваÑÑ, ÑÑобÑ
@@ -721,7 +724,7 @@
ÐеÑ. Ðднако еÑли кÑо-Ñо заплаÑил вам и
полÑÑил копиÑ, GPL Ð´Ð°ÐµÑ ÐµÐ¼Ñ ÑвободÑ
вÑпÑÑкаÑÑ ÐµÐµ в обÑеÑÑве, за денÑги или
беÑплаÑно. ÐапÑимеÑ, кÑо-нибÑÐ´Ñ Ð¼Ð¾Ð³
Ð±Ñ Ð²Ð°Ð¼ заплаÑиÑÑ, а заÑем ÑазмеÑÑиÑÑ ÑвоÑ
ÐºÐ¾Ð¿Ð¸Ñ Ð½Ð° ÑайÑе в обÑем доÑÑÑпе.
-<p></p></dd>
+</dd>
<dt><a href="#TOCDoesTheGPLAllowNDA"
name="DoesTheGPLAllowNDA">ÐозволÑÐµÑ Ð»Ð¸ мне
GPL ÑаÑпÑоÑÑÑанÑÑÑ ÐºÐ¾Ð¿Ð¸Ð¸ по договоÑÑ Ð¾
неÑазглаÑении?</a></dt>
@@ -752,7 +755,7 @@
веÑÑии, впÑаве ÑаÑпÑоÑÑÑанÑÑÑ ÐºÐ¾Ð¿Ð¸Ð¸ (Ñ
изменениÑми или без ниÑ
) ÑÑой
веÑÑии. ÐÑ Ð½Ðµ можеÑе ÑаÑпÑоÑÑÑанÑÑÑ ÐºÐ°ÐºÑÑ
Ð±Ñ Ñо ни бÑло веÑÑÐ¸Ñ ÑабоÑÑ Ð½Ð°
более огÑаниÑиÑелÑной оÑнове.
-<p></p></dd>
+</dd>
<dt><a href="#TOCDevelopChangesUnderNDA"
name="DevelopChangesUnderNDA">ÐозволÑеÑ
ли мне GPL ÑазÑабаÑÑваÑÑ Ð¸Ð·Ð¼ÐµÐ½ÐµÐ½Ð½ÑÑ Ð²ÐµÑÑиÑ
по договоÑÑ Ð¾ неÑазглаÑении?</a></dt>
@@ -783,7 +786,7 @@
Ñ Ð²Ð°Ñим именем (пÑедполагаеÑÑÑ, ÑÑо
Ð²Ñ — пÑавообладаÑелÑ). GPL
ÑÑебÑеÑ, ÑÑÐ¾Ð±Ñ Ð²Ñе копии неÑли
ÑооÑвеÑÑÑвÑÑÑее пÑимеÑание об авÑоÑÑкиÑ
пÑаваÑ
.
-<p></p></dd>
+</dd>
<dt><a href="#TOCWhyMustIInclude" name="WhyMustIInclude">ÐоÑÐµÐ¼Ñ GPL
ÑÑебÑеÑ
пеÑедаÑи копии GPL в каждой копии
пÑогÑаммÑ?</a></dt>
@@ -810,7 +813,7 @@
<dd>
ÐÑли оÑделÑÐ½Ð°Ñ Ð¿ÑогÑамма наÑÑолÑко
коÑоÑка, Ð²Ñ Ð¼Ð¾Ð¶ÐµÑе иÑполÑзоваÑÑ Ð´Ð»Ñ Ð½ÐµÐµ и
пÑоÑÑÑÑ Ð²ÑеÑазÑеÑаÑÑÑÑ Ð»Ð¸ÑензиÑ, а не GNU GPL.
-<p></p></dd>
+</dd>
<dt><a href="#TOCGPLOmitPreamble" name="GPLOmitPreamble">ÐÐ¾Ð³Ñ Ñ
опÑÑÑиÑÑ
пÑеамбÑÐ»Ñ GPL или инÑÑÑÑкÑии по пÑименениÑ
ее Ð´Ð»Ñ ÑобÑÑвеннÑÑ
пÑогÑамм,
@@ -1043,7 +1046,7 @@
<dd>
См. ÑÑÑаниÑÑ Ñ <a
href="/licenses/gpl-howto.html">ÑказаниÑми по GPL</a>.
-<p></p></dd>
+</dd>
<dt><a href="#TOCHeardOtherLicense" name="HeardOtherLicense">Ðне
говоÑили, ÑÑо
кÑо-Ñо полÑÑил ÐºÐ¾Ð¿Ð¸Ñ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL по
дÑÑгой лиÑензии. Ðозможно ли
@@ -1068,7 +1071,7 @@
ÑÑÐ¾Ð¼Ñ Ð½ÐµÑ Ð½Ð¸ÐºÐ°ÐºÐ¸Ñ
пÑепÑÑÑÑвий. ÐÑли
Ð²Ñ — пÑавообладаÑелÑ
пÑогÑаммÑ, Ð²Ñ Ð¼Ð¾Ð¶ÐµÑе вÑпÑÑкаÑÑ ÐµÐµ под
ÑазнÑми неиÑклÑÑиÑелÑнÑми лиÑензиÑми в
ÑазнÑÑ
ÑлÑÑаÑÑ
.
-<p></p></dd>
+</dd>
<dt><a href="#TOCDeveloperViolate" name="DeveloperViolate">СвÑзан ли
ÑазÑабоÑÑик
пÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL ÑекÑÑом лиÑензии? ÐогÑÑ Ð»Ð¸
бÑÑÑ Ð´ÐµÐ¹ÑÑÐ²Ð¸Ñ ÑазÑабоÑÑика
@@ -1092,7 +1095,7 @@
<dd>
ÐеÑ, поÑÐ¾Ð¼Ñ ÑÑо обÑеÑÑво Ñже полÑÑило
пÑаво полÑзоваÑÑÑÑ Ð¿ÑогÑаммой на
ÑÑловиÑÑ
GPL и ÑÑо пÑаво не Ð¼Ð¾Ð¶ÐµÑ Ð±ÑÑÑ
оÑозвано.
-<p></p></dd>
+</dd>
<dt><a href="#TOCCanIUseGPLToolsForNF" name="CanIUseGPLToolsForNF">Ðожно
мне
полÑзоваÑÑÑÑ ÑедакÑоÑами под GPL, Ñакими,
как GNU Emacs, Ð´Ð»Ñ ÑазÑабоÑки
@@ -1202,7 +1205,7 @@
<dd>
ТолÑко когда пÑогÑамма копиÑÑÐµÑ ÑаÑÑÑ
Ñамой ÑÐµÐ±Ñ Ð² вÑÑ
однÑе даннÑе.
-<p></p></dd>
+</dd>
<dt><a href="#TOCGPLModuleLicense" name="GPLModuleLicense">ÐÑли Ñ
добавлÑÑ
модÑÐ»Ñ Ðº пÑогÑамме под GPL, ÑÑебÑеÑÑÑ Ð»Ð¸ оÑ
Ð¼ÐµÐ½Ñ Ð¸ÑполÑзование GPL в
@@ -1315,76 +1318,82 @@
РпеÑеÑмоÑÑенной лиÑензии BSD пÑнкÑа о
Ñекламе неÑ, ÑÑо ÑÑÑÑанÑÐµÑ Ð¿ÑоблемÑ.
</p></dd>
+<dt><a href="#TOCGPLPlugins" name="GPLPlugins"> Ðогда пÑогÑамма
и ее внеÑние
+модÑли ÑÑиÑаÑÑÑÑ ÐµÐ´Ð¸Ð½Ð¾Ð¹ комбиниÑованной
пÑогÑаммой?</a></dt>
+<dd>
+ ÐÑо завиÑÐ¸Ñ Ð¾Ñ Ñого, как главнаÑ
пÑогÑамма вÑзÑÐ²Ð°ÐµÑ Ñвои внеÑние
+модÑли. ÐÑли Ð³Ð»Ð°Ð²Ð½Ð°Ñ Ð¿ÑогÑамма иÑполÑзÑеÑ
Ð´Ð»Ñ ÑÑого fork и exec и они
+завÑзÑваÑÑ ÑеÑное обÑение ÑеÑез ÑложнÑе
ÑÑÑÑкÑÑÑÑ Ð´Ð°Ð½Ð½ÑÑ
, обÑие или
+пеÑедаваемÑе ÑÑда и обÑаÑно, Ñо они
ÑÑановÑÑÑÑ ÐµÐ´Ð¸Ð½Ð¾Ð¹ комбиниÑованной
+пÑогÑаммой. Ðогда Ð³Ð»Ð°Ð²Ð½Ð°Ñ Ð¿ÑогÑамма
иÑполÑзÑÐµÑ Ð´Ð»Ñ Ð²Ñзова внеÑниÑ
модÑлей
+пÑоÑÑо fork и exec, не завÑзÑÐ²Ð°Ñ ÑеÑного
обÑÐµÐ½Ð¸Ñ Ñ Ð½Ð¸Ð¼Ð¸, внеÑние модÑли
+оÑÑаÑÑÑÑ Ð¾ÑделÑнÑми пÑогÑаммами.
+
+<p> ÐÑли Ð³Ð»Ð°Ð²Ð½Ð°Ñ Ð¿ÑогÑамма динамиÑеÑки
компонÑеÑÑÑ Ñ Ð¼Ð¾Ð´ÑлÑми и они вÑзÑваÑÑ
+ÑÑнкÑии дÑÑг из дÑÑга и ÑазделÑÑÑ Ð¾Ð±Ñие
ÑÑÑÑкÑÑÑÑ Ð´Ð°Ð½Ð½ÑÑ
, Ð¼Ñ ÑбежденÑ, ÑÑо
+они ÑоÑмиÑÑÑÑ ÐµÐ´Ð¸Ð½ÑÑ ÐºÐ¾Ð¼Ð±Ð¸Ð½Ð¸ÑованнÑÑ
пÑогÑаммÑ, коÑоÑÐ°Ñ Ð´Ð¾Ð»Ð¶Ð½Ð°
+ÑаÑÑмаÑÑиваÑÑÑÑ ÐºÐ°Ðº ÑаÑÑиÑение и главной
пÑогÑаммÑ, и модÑлей. ÐÑли главнаÑ
+пÑогÑамма динамиÑеÑки компонÑеÑÑÑ Ñ
модÑлÑми, но взаимодейÑÑвие Ð¼ÐµÐ¶Ð´Ñ Ð½Ð¸Ð¼Ð¸
+огÑаниÑено вÑзовом “главной”
пÑоÑедÑÑÑ Ð¼Ð¾Ð´ÑÐ»Ñ Ñ ÐºÐ°ÐºÐ¸Ð¼Ð¸-Ñо
+паÑамеÑÑами и ожиданием ÑезÑлÑÑаÑа, Ñо ÑÑо
пÑеделÑнÑй ÑлÑÑай.</p>
+
+<p>ÐÑименение обÑей памÑÑи Ð´Ð»Ñ Ð¾Ð±Ð¼ÐµÐ½Ð°
ÑложнÑми ÑÑÑÑкÑÑÑами даннÑÑ
вполне
+ÑквиваленÑно динамиÑеÑкомÑ
ÑвÑзÑваниÑ.</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>
+См. Ñакже оÑделÑнÑй вопÑÐ¾Ñ <a href="#GPLPlugins">длÑ
опÑÐµÐ´ÐµÐ»ÐµÐ½Ð¸Ñ Ñого,
+ÑÑиÑаÑÑÑÑ Ð»Ð¸ модÑли и Ð³Ð»Ð°Ð²Ð½Ð°Ñ Ð¿ÑогÑамма
единой комбиниÑованной пÑогÑаммой
+или ÑазделÑнÑми пÑоизведениÑми</a>.
+
+<p> ÐÑли Ð³Ð»Ð°Ð²Ð½Ð°Ñ Ð¿ÑогÑамма и модÑли
ÑоÑÑавлÑÑÑ ÐºÐ¾Ð¼Ð±Ð¸Ð½Ð¸ÑованнÑÑ Ð¿ÑогÑаммÑ, Ñо
ÑÑо
+знаÑиÑ, ÑÑо Ð²Ñ Ð´Ð¾Ð»Ð¶Ð½Ñ Ð²ÑпÑÑкаÑÑ Ð¼Ð¾Ð´ÑÐ»Ñ Ð¿Ð¾Ð´
GPL или ÑовмеÑÑимой Ñ Ð½ÐµÐ¹
+лиÑензией ÑвободнÑÑ
пÑогÑамм и
ÑаÑпÑоÑÑÑанÑÑÑ ÐµÐ³Ð¾ Ñ Ð¸ÑÑ
однÑм ÑекÑÑом Ñак,
+ÑÑÐ¾Ð±Ñ ÑÑо бÑло ÑовмеÑÑимо Ñ GPL. ÐÑли
Ð³Ð»Ð°Ð²Ð½Ð°Ñ Ð¿ÑогÑамма оÑделÑна Ð¾Ñ Ð²Ð½ÐµÑниÑ
+модÑлей, Ñо ÑÑо не Ð½Ð°Ð»Ð°Ð³Ð°ÐµÑ ÑÑебований на
внеÑние модÑли. </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>
+ См. Ñакже оÑделÑнÑй вопÑÐ¾Ñ <a href="#GPLPlugins">длÑ
опÑÐµÐ´ÐµÐ»ÐµÐ½Ð¸Ñ Ñого,
+ÑÑиÑаÑÑÑÑ Ð»Ð¸ модÑли и Ð³Ð»Ð°Ð²Ð½Ð°Ñ Ð¿ÑогÑамма
единой комбиниÑованной пÑогÑаммой
+или ÑазделÑнÑми пÑогÑаммами</a>.
+<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>
+ См. Ñакже оÑделÑнÑй вопÑÐ¾Ñ <a href="#GPLPlugins">длÑ
опÑÐµÐ´ÐµÐ»ÐµÐ½Ð¸Ñ Ñого,
+ÑÑиÑаÑÑÑÑ Ð»Ð¸ модÑли и Ð³Ð»Ð°Ð²Ð½Ð°Ñ Ð¿ÑогÑамма
единой комбиниÑованной пÑогÑаммой
+или ÑазделÑнÑми пÑогÑаммами</a>.
+<p>
+ÐÑли они ÑоÑмиÑÑÑÑ ÐµÐ´Ð¸Ð½ÑÑ ÐºÐ¾Ð¼Ð±Ð¸Ð½Ð¸ÑованнÑÑ
пÑогÑаммÑ, Ñо Ð³Ð»Ð°Ð²Ð½Ð°Ñ Ð¿ÑогÑамма
+должна вÑпÑÑкаÑÑÑÑ Ð¿Ð¾Ð´ GPL или ÑовмеÑÑимой
Ñ Ð½ÐµÐ¹ лиÑензией ÑвободнÑÑ
+пÑогÑамм, и пÑи ÑаÑпÑоÑÑÑанении главной
пÑогÑÐ°Ð¼Ð¼Ñ Ð´Ð»Ñ Ð¿Ð¾Ð»ÑÐ·Ð¾Ð²Ð°Ð½Ð¸Ñ Ñ ÑÑими
+модÑлÑми Ð´Ð¾Ð»Ð¶Ð½Ñ ÑоблÑдаÑÑÑÑ ÑÑÐ»Ð¾Ð²Ð¸Ñ GPL.</p>
+
+<p>Ðднако еÑли ÑÑо ÑазделÑнÑе пÑоизведениÑ,
Ñо лиÑÐµÐ½Ð·Ð¸Ñ Ð½Ð° модÑли не налагаеÑ
+ÑÑебований на главнÑÑ Ð¿ÑогÑаммÑ.</p>
+
+<p>См. Ñакже оÑÐ²ÐµÑ Ð½Ð° вопÑÐ¾Ñ <a href="#FSWithNFLibs">о
напиÑании ÑвободнÑÑ
+пÑогÑамм Ñ Ð¸ÑполÑзованием неÑвободнÑÑ
библиоÑек</a>.</p></dd>
+
<dt><a href="#TOCLinkingWithGPL" name="LinkingWithGPL">У Ð²Ð°Ñ ÐµÑÑÑ
пÑогÑамма под
GPL, коÑоÑÑÑ Ð¼Ð½Ðµ Ñ
оÑелоÑÑ Ð±Ñ ÑкомпоноваÑÑ Ñ
моими пÑогÑаммами, ÑÑобÑ
@@ -1393,7 +1402,7 @@
<dd>
Ðа.
-<p></p></dd>
+</dd>
<dt><a href="#TOCSwitchToLGPL" name="SwitchToLGPL">Ð Ñаком ÑлÑÑае,
еÑÑÑ Ð»Ð¸ Ñ
Ð¼ÐµÐ½Ñ Ñ
оÑÑ ÐºÐ°ÐºÐ°Ñ-Ñо надежда на полÑÑение оÑ
Ð²Ð°Ñ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð½Ð° ÑÑловиÑÑ
ÐенÑÑей
@@ -1451,7 +1460,7 @@
GPL, напиÑаннÑÑ
дÑÑгими авÑоÑами, в Ñвоей
пÑогÑамме, Ð²Ñ Ð½Ðµ можеÑе
ÑанкÑиониÑоваÑÑ ÑÑо иÑклÑÑение за ниÑ
. ÐÑ
Ð´Ð¾Ð»Ð¶Ð½Ñ Ð¿Ð¾Ð»ÑÑиÑÑ ÑоглаÑие оÑ
пÑавообладаÑелей ÑÑиÑ
пÑогÑамм.
-</p><p></p></dd>
+</p></dd>
<dt><a href="#TOCManyDifferentLicenses" name="ManyDifferentLicenses">Ðной
напиÑано пÑиложение, коÑоÑое компонÑеÑÑÑ
Ñ Ð±Ð¾Ð»ÑÑим ÑиÑлом ÑазнÑÑ
@@ -1471,7 +1480,7 @@
ÑоÑÑавлÑÑ), ÑÑÐ¾Ð±Ñ Ð·Ð°Ð¿ÑÑÑиÑÑ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ ÐÐÐ,
коÑоÑÐ°Ñ Ð»Ð¸ÑензиÑÑеÑÑÑ Ð¿Ð¾
“GPL Ñ Ð¾ÑобÑм иÑклÑÑением, позволÑÑÑим
компоноваÑÑ Ñ QUUX”.</li>
</ul>
-<p></p></dd>
+</dd>
<dt><a href="#TOCMereAggregation" name="MereAggregation">Ðакова
ÑазниÑа междÑ
“пÑоÑÑÑм ÑазмеÑением на одном
ноÑиÑеле” и “комбиниÑованием
@@ -1602,10 +1611,10 @@
<dd>
-<p>Ðна ÑабоÑÐ°ÐµÑ Ð² ÑооÑвеÑÑÑвии Ñ Ñем, как
она ÑоÑÑавлена, Ð´Ð»Ñ Ñего
+Ðна ÑабоÑÐ°ÐµÑ Ð² ÑооÑвеÑÑÑвии Ñ Ñем, как она
ÑоÑÑавлена, Ð´Ð»Ñ Ñего
пÑедназнаÑена и Ñак, как ÑÑо задÑмано.
ÐодÑобноÑÑи Ñм. в <a
href="/licenses/lgpl-java.html">оÑделÑной ÑÑаÑÑе</a>.
-</p></dd>
+</dd>
<dt><a href="#TOCConsider" name="Consider">РаÑÑмоÑÑим
ÑиÑÑаÑиÑ: 1) X вÑпÑÑкаеÑ
веÑÑÐ¸Ñ V1 пÑоекÑа под GPL. 2) Y вноÑиÑ
доÑабоÑки в веÑÑÐ¸Ñ V2, коÑоÑÑе
@@ -1618,7 +1627,7 @@
ÑоглаÑиÑÑÑÑ Ð½Ð° лÑбÑÑ Ð´ÑÑгÑÑ Ð»Ð¸ÑÐµÐ½Ð·Ð¸Ñ Ð´Ð»Ñ
ÑекÑÑов Y. СледоваÑелÑно, X должен
полÑÑиÑÑ ÑазÑеÑение Y пеÑед Ñем, как
вÑпÑÑÑиÑÑ ÑÑи пÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ дÑÑгой
лиÑензией.
-<p></p></dd>
+</dd>
<dt><a href="#TOCGPLInProprietarySystem" name="GPLInProprietarySystem">Ðне
@@ -1674,11 +1683,11 @@
лиÑензией (как, напÑимеÑ, лиÑÐµÐ½Ð·Ð¸Ñ X11) междÑ
ÑаÑÑÑÑ, ÑаÑпÑоÑÑÑанÑемой по
GPL, и неÑвободной ÑаÑÑÑÑ?</a></dt>
-<dd><p>ÐеÑ. ÐиÑÐµÐ½Ð·Ð¸Ñ X11 ÑовмеÑÑима Ñ GPL, Ñак ÑÑо
Ð²Ñ Ð¼Ð¾Ð¶ÐµÑе добавлÑÑÑ Ð¼Ð¾Ð´ÑÐ»Ñ Ð²
+<dd>ÐеÑ. ÐиÑÐµÐ½Ð·Ð¸Ñ X11 ÑовмеÑÑима Ñ GPL, Ñак ÑÑо
Ð²Ñ Ð¼Ð¾Ð¶ÐµÑе добавлÑÑÑ Ð¼Ð¾Ð´ÑÐ»Ñ Ð²
пÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL и помеÑаÑÑ ÐµÐ³Ð¾ под
лиÑÐµÐ½Ð·Ð¸Ñ X11. Ðо еÑли Ð±Ñ Ð²Ñ ÑобиÑалиÑÑ
вÑÑÑаиваÑÑ Ð¾Ð±Ðµ ÑаÑÑи в более кÑÑпнÑÑ
пÑогÑаммÑ, Ñо вÑе ÑÑо в Ñелом вклÑÑало
Ð±Ñ ÑаÑÑÑ, ÑаÑпÑоÑÑÑанÑемÑÑ Ð¿Ð¾ GPL, Ñак ÑÑо
ÑÑо нÑжно бÑло Ð±Ñ Ð»Ð¸ÑензиÑоваÑÑ
-<em>в Ñелом</em> по GNU GPL.</p>
+<em>в Ñелом</em> по GNU GPL.
<p>Ð¢Ð¾Ñ ÑакÑ, ÑÑо неÑвободнÑй модÑÐ»Ñ Ð
ÑоединÑеÑÑÑ Ñ Ð¼Ð¾Ð´Ñлем Ð, ÑаÑпÑоÑÑÑанÑемÑм
по GPL, ÑолÑко ÑеÑез модÑÐ»Ñ Ð,
ÑаÑпÑоÑÑÑанÑемÑй по лиÑензии X11, Ñ ÑоÑки
@@ -1689,8 +1698,8 @@
<dt><a href="#TOCLibGCCException" name="LibGCCException"> ÐопÑÑкаеÑ
ли
иÑклÑÑение libstdc++ динамиÑеÑкое
ÑвÑзÑвание?</a></dt>
-<dd><p>Ðа. ÐÑклÑÑение пÑедназнаÑено Ð´Ð»Ñ Ñого,
ÑÑÐ¾Ð±Ñ Ð¿Ð¾Ð·Ð²Ð¾Ð»Ð¸ÑÑ Ð»ÑдÑм компилиÑоваÑÑ
-неÑвободнÑе пÑогÑÐ°Ð¼Ð¼Ñ Ñ Ð¿Ð¾Ð¼Ð¾ÑÑÑ gcc.</p></dd>
+<dd>Ðа. ÐÑклÑÑение пÑедназнаÑено Ð´Ð»Ñ Ñого,
ÑÑÐ¾Ð±Ñ Ð¿Ð¾Ð·Ð²Ð¾Ð»Ð¸ÑÑ Ð»ÑдÑм компилиÑоваÑÑ
+неÑвободнÑе пÑогÑÐ°Ð¼Ð¼Ñ Ñ Ð¿Ð¾Ð¼Ð¾ÑÑÑ gcc.</dd>
<dt><a href="#TOCMoneyGuzzlerInc" name="MoneyGuzzlerInc">Ðне Ñ
оÑелоÑÑ Ð±Ñ
измениÑÑ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GPL и ÑвÑзаÑÑ Ð¸Ñ
Ñ
библиоÑеками пеÑеноÑимоÑÑи ÐÐÐ
@@ -1750,7 +1759,7 @@
Ð´Ð¾Ð»Ð¶Ð½Ñ Ð±ÑÑÑ <a href="/philosophy/free-sw.html">ÑвободнÑми
пÑогÑаммами</a> — ÑÑо ознаÑаеÑ, в
ÑаÑÑноÑÑи, ÑÑо иÑÑ
однÑй ÑекÑÑ
модиÑиÑиÑованной веÑÑии доÑÑÑпен
полÑзоваÑелÑм.
-<p></p></dd>
+</dd>
<dt><a href="#TOCUnchangedJustBinary" name="UnchangedJustBinary">Я взÑл
по ÑеÑи
@@ -1760,7 +1769,7 @@
Ðа. ÐбÑее пÑавило Ñаково: еÑли вÑ
ÑаÑпÑоÑÑÑанÑеÑе двоиÑнÑе ÑайлÑ, Ð²Ñ Ð´Ð¾Ð»Ð¶Ð½Ñ
ÑаÑпÑоÑÑÑанÑÑÑ Ð¸ полнÑй иÑÑ
однÑй ÑекÑÑ.
ÐÑклÑÑение Ð´Ð»Ñ ÑлÑÑаÑ, когда вÑ
полÑÑили пиÑÑменное пÑедложение иÑÑ
одного ÑекÑÑа, веÑÑма огÑаниÑено.
-<p></p></dd>
+</dd>
<dt><a href="#TOCDistributeWithSourceOnInternet"
name="DistributeWithSourceOnInternet">Я Ñ
оÑÑ ÑаÑпÑоÑÑÑанÑÑÑ
двоиÑнÑе ÑайлÑ
@@ -1805,7 +1814,7 @@
ÐºÐ¾Ð¿Ð¸Ñ Ð´Ð²Ð¾Ð¸Ñного Ñайла, коÑоÑÑй оно
ÑопÑовождаеÑ. ÐÐ¾Ñ Ð¿Ð¾ÑÐµÐ¼Ñ Ð² GPL Ñказано,
ÑÑо Ð²Ð°Ñ Ð·Ð½Ð°ÐºÐ¾Ð¼Ñй должен даÑÑ Ð²Ð°Ð¼ копиÑ
пÑÐµÐ´Ð»Ð¾Ð¶ÐµÐ½Ð¸Ñ Ð²Ð¼ÐµÑÑе Ñ ÐºÐ¾Ð¿Ð¸ÐµÐ¹ двоиÑного
Ñайла — Ñак ÑÑо Ð²Ñ Ð¼Ð¾Ð¶ÐµÑе им
воÑполÑзоваÑÑÑÑ.
-<p></p></dd>
+</dd>
<dt><a href="#TOCSourceAndBinaryOnDifferentSites"
name="SourceAndBinaryOnDifferentSites">ÐÐ¾Ð³Ñ Ñ ÑазмеÑÑиÑÑ
двоиÑнÑе ÑÐ°Ð¹Ð»Ñ Ð½Ð°
@@ -1969,7 +1978,7 @@
ÑаÑпÑоÑÑÑанение. ÐбÑаÑиÑе внимание, ÑÑо
ÑÑо оÑлиÑаеÑÑÑ Ð¾Ñ Ð¿ÑедÑдÑÑего ÑлÑÑаÑ
Ñ ÐºÑажей: пÑедпÑиÑÑие не ÑаÑпÑоÑÑÑанÑеÑ
ÐºÐ¾Ð¿Ð¸Ñ Ð¿ÑеднамеÑенно, когда ее
кÑадÑÑ, Ñак ÑÑо в ÑÑом ÑлÑÑае пÑедпÑиÑÑие
не наÑÑÑÐ°ÐµÑ GPL.
-<p></p></dd>
+</dd>
<dt><a name="WhySomeGPLAndNotLGPL">ÐоÑÐµÐ¼Ñ Ð½ÐµÐºÐ¾ÑоÑÑе
библиоÑеки GNU вÑпÑÑкаÑÑÑÑ
по обÑÑной GPL, а не по ÐенÑÑей GPL?</a></dt>
@@ -2251,7 +2260,7 @@
поÑÐ²Ð»ÐµÐ½Ð¸Ñ ÑакиÑ
пеÑеводов.</p>
</li>
</ul>
-<p></p></dd>
+</dd>
<dt><a name="InterpreterIncompat">ÐÑли лиÑензиÑ
инÑеÑпÑеÑаÑоÑа ÑзÑка
пÑогÑаммиÑÐ¾Ð²Ð°Ð½Ð¸Ñ Ð½ÐµÑовмеÑÑима Ñ GPL, могÑ
ли Ñ Ð²ÑполнÑÑÑ Ð½Ð° нем пÑогÑаммÑ
@@ -2287,7 +2296,7 @@
добавлÑÑÑ Ðº ним Ñакие иÑклÑÑениÑ.
ÐÑклÑÑение могÑÑ Ð´Ð¾Ð±Ð°Ð²Ð¸ÑÑ ÑолÑко
пÑавообладаÑели ÑÑиÑ
пÑогÑамм.</li>
</ol>
-<p></p></dd>
+</dd>
<dt><a name="WhoHasThePower">ÐÑо впÑаве ÑÑебоваÑÑ
ÑоблÑÐ´ÐµÐ½Ð¸Ñ GPL?</a></dt>
@@ -2299,7 +2308,7 @@
либо ÑвлÑÑÑÑÑ Ð¿ÑавообладаÑелÑми, либо
ÑвÑÐ·Ð°Ð½Ñ Ñ Ð½Ð¸Ð¼Ð¸. <a
href="#ReportingViolation">ÐодÑобнее о Ñом, как ÑÑо
делаÑÑ, опиÑано в оÑвеÑе
на дÑÑгой вопÑоÑ.</a>
-<p></p></dd>
+</dd>
<dt><a name="OOPLang">ÐÑли в Ñаком
обÑекÑно-оÑиенÑиÑованном ÑзÑке, как Java, Ñ
@@ -2310,7 +2319,7 @@
ÐбÑазование подклаÑÑа ÑвлÑеÑÑÑ Ñозданием
пÑоизводного
пÑоизведениÑ. СледоваÑелÑно, ÑÑÐ»Ð¾Ð²Ð¸Ñ GPL
ÑаÑпÑоÑÑÑанÑÑÑÑÑ Ð½Ð° вÑÑ Ð¿ÑогÑаммÑ,
в коÑоÑой Ð²Ñ ÑоздаеÑе подклаÑÑ ÐºÐ»Ð°ÑÑа под
GPL.
-<p></p></dd>
+</dd>
<dt><a name="PortProgramToGL">ÐÑли Ñ Ð¿ÐµÑеноÑÑ ÑвоÑ
пÑогÑÐ°Ð¼Ð¼Ñ Ð½Ð° GNU/Linux,
знаÑÐ¸Ñ Ð»Ð¸ ÑÑо, ÑÑо мне необÑ
одимо
вÑпÑÑÑиÑÑ ÐµÐµ как ÑвободнÑÑ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´
@@ -2489,7 +2498,7 @@
<p class="unprintable"><!-- timestamp start -->
Ðбновлено:
-$Date: 2017/02/17 06:30:23 $
+$Date: 2017/03/11 10:59:57 $
<!-- timestamp end -->
</p>
Index: po/gpl-2.0-faq.ru-en.html
===================================================================
RCS file: /web/www/www/licenses/old-licenses/po/gpl-2.0-faq.ru-en.html,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -b -r1.31 -r1.32
--- po/gpl-2.0-faq.ru-en.html 17 Feb 2017 06:30:24 -0000 1.31
+++ po/gpl-2.0-faq.ru-en.html 11 Mar 2017 10:59:58 -0000 1.32
@@ -77,7 +77,7 @@
<li><a href="#GPLAndNonfreeOnSameMachine"
name="TOCGPLAndNonfreeOnSameMachine"> Can I have a GPL-covered
- program and an unrelated non-free program on the same
+ program and an unrelated nonfree program on the same
computer?</a></li>
<li><a href="#CanIDemandACopy" name="TOCCanIDemandACopy">If I know
@@ -188,7 +188,7 @@
<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>
+ like to use the same code in nonfree programs.</a></li>
<li><a href="#CanDeveloperThirdParty"
name="TOCCanDeveloperThirdParty">Can the developer of a program who
@@ -209,7 +209,7 @@
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>
+ a program under the GPL which I developed using nonfree tools?</a></li>
</ul>
<h4>Distribution of programs released under the GPL</h4>
@@ -298,7 +298,7 @@
<ul>
<li><a href="#CanIUseGPLToolsForNF" name="TOCCanIUseGPLToolsForNF">Can
- I use GPL-covered editors such as GNU Emacs to develop non-free
+ I use GPL-covered editors such as GNU Emacs to develop nonfree
programs? Can I use GPL-covered tools such as GCC to compile
them?</a></li>
@@ -365,15 +365,19 @@
module to a GPL-covered program, do I have to use the GPL as the
license for my module?</a></li>
+ <li><a href="#GPLPlugins" name="TOCGPLPlugins">
+ When are a program and its plug-ins
+ considered a single combined program?</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>
+ GPL when writing a plug-in for a nonfree program?</a></li>
<li><a href="#NFUseGPLPlugins" name="TOCNFUseGPLPlugins">Can I
- release a non-free program that's designed to load a GPL-covered
+ release a nonfree program that's designed to load a GPL-covered
plug-in?</a></li>
<li><a href="#GPLInProprietarySystem"
@@ -387,7 +391,7 @@
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>
+ free software that uses nonfree libraries?</a></li>
<li><a href="#GPLIncompatibleLibs" name="TOCGPLIncompatibleLibs">
What legal issues come up if I use GPL-incompatible libraries with
@@ -473,7 +477,7 @@
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>
+</dd>
<dt><b><a href="#TOCDoesFreeSoftwareMeanUsingTheGPL"
name="DoesFreeSoftwareMeanUsingTheGPL">
Does free software mean using the GPL?</a></b></dt>
@@ -484,7 +488,7 @@
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>
+</dd>
<dt><b><a href="#TOCWhyUseGPL" name="WhyUseGPL">
Why should I use the GNU GPL rather than other free software
licenses?</a></b></dt>
@@ -496,7 +500,7 @@
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>
+</dd>
<dt><b><a href="#TOCDoesAllGNUSoftwareUseTheGNUGPLAsItsLicense"
name="DoesAllGNUSoftwareUseTheGNUGPLAsItsLicense">
Does all GNU software use the GNU GPL as its license?</a></b></dt>
@@ -506,7 +510,7 @@
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>
+</dd>
<dt><b><a href="#TOCDoesUsingTheGPLForAProgramMakeItGNUSoftware"
name="DoesUsingTheGPLForAProgramMakeItGNUSoftware">
Does using the GPL for a program make it GNU software?</a></b></dt>
@@ -534,7 +538,7 @@
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>
+</dd>
<dt><b><a href="#TOCWhyDoesTheGPLPermitUsersToPublishTheirModifiedVersions"
name="WhyDoesTheGPLPermitUsersToPublishTheirModifiedVersions">
Why does the GPL permit users to publish their modified versions?</a></b></dt>
@@ -583,12 +587,12 @@
</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>
+ Can I have a GPL-covered program and an unrelated nonfree 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>
+</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
@@ -598,7 +602,7 @@
No. The GPL gives him permission to make and redistribute copies of
the program <em>if and when he chooses to do so</em>. He also has the
right not to redistribute the program, when that is what he
-chooses.<p></p></dd>
+chooses.</dd>
<dt><b><a href="#TOCWhatDoesWrittenOfferValid"
name="WhatDoesWrittenOfferValid"> What does this
@@ -635,7 +639,7 @@
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>
+</dd>
<dt><b><a href="#TOCRequiredToClaimCopyright"
name="RequiredToClaimCopyright">Am I required to claim a copyright
@@ -664,7 +668,7 @@
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>
+</dd>
<dt><b><a href="#TOCDoesTheGPLAllowMoney" name="DoesTheGPLAllowMoney">
Does the GPL allow me to sell copies of the program for
money?</a></b></dt>
@@ -676,7 +680,7 @@
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>
+</dd>
<dt><b><a href="#TOCDoesTheGPLAllowDownloadFee"
name="DoesTheGPLAllowDownloadFee">
Does the GPL allow me to
@@ -688,14 +692,14 @@
“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>
+</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.
+No. In fact, a requirement like that would make the program nonfree.
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">
@@ -720,7 +724,7 @@
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>
+</dd>
<dt><b><a href="#TOCDoesTheGPLAllowNDA" name="DoesTheGPLAllowNDA">
Does the GPL allow me to distribute copies under a
@@ -750,7 +754,7 @@
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>
+</dd>
<dt><b><a href="#TOCDevelopChangesUnderNDA" name="DevelopChangesUnderNDA">
Does the GPL allow me to develop a modified version under a
@@ -781,7 +785,7 @@
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>
+</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>
@@ -807,7 +811,7 @@
<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>
+</dd>
<dt><b><a href="#TOCGPLOmitPreamble"
name="GPLOmitPreamble">
@@ -864,28 +868,28 @@
<dt><b><a href="#TOCFSWithNFLibs" name="FSWithNFLibs">Can I write
-free software that uses non-free libraries?</a></b></dt>
+free software that uses nonfree 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
+environment. If your program depends on a nonfree 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
+nonfree 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
+If the program is already written using the nonfree 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
+README that the need for the nonfree 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
+the nonfree 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>
+on the nonfree library.</p>
<p>
-Note that there may also be legal issues with combining certain non-free
+Note that there may also be legal issues with combining certain nonfree
libraries with GPL-covered Free Software. Please see <a
href="#GPLIncompatibleLibs">the question on GPL software with
GPL-incompatible libraries</a> for more information.
@@ -973,9 +977,9 @@
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
+If the libraries you intend to link with are nonfree, please also see
<a href="#FSWithNFLibs">the section on writing Free Software which
-uses non-free libraries</a>.
+uses nonfree libraries</a>.
</p></dd>
<dt><b><a href="#TOCHowIGetCopyright" name="HowIGetCopyright">How do I
@@ -1038,7 +1042,7 @@
<dd>
See the page of <a href="/licenses/gpl-howto.html">
GPL instructions</a>.
-<p></p></dd>
+</dd>
<dt><b><a href="#TOCHeardOtherLicense" name="HeardOtherLicense">I heard
that someone got a copy of a GPL'ed program under another license. Is
@@ -1057,14 +1061,14 @@
<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>
+ like to use the same code in nonfree programs.</a></b></dt>
<dd>
-To release a non-free program is always ethically tainted, but legally
+To release a nonfree 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>
+</dd>
<dt><b><a href="#TOCDeveloperViolate" name="DeveloperViolate">Is the
developer of a GPL-covered program bound by the GPL? Could the
@@ -1089,11 +1093,11 @@
<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>
+</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
+ GNU Emacs to develop nonfree programs? Can I use GPL-covered tools
such as GCC to compile them?</a></b></dt>
<dd>
@@ -1108,11 +1112,11 @@
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.
+As it happens, Bison can also be used to develop nonfree 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.
+which already permitted use for nonfree programs.
</p></dd>
<dt><b><a href="#TOCGPLFairUse" name="GPLFairUse">Do I have
@@ -1191,7 +1195,7 @@
<dd>
Only when the program copies part of itself into the output.
-<p></p></dd>
+</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
@@ -1300,78 +1304,85 @@
which eliminates the problem.
</p></dd>
+<dt><b><a href="#TOCGPLPlugins" name="GPLPlugins">
+When are a program and its plug-ins considered a single combined program?
+</a></b></dt>
+<dd>
+ It depends on how the main program invokes its plug-ins. If the
+main program uses fork and exec to invoke plug-ins, and they establish
+intimate communication by sharing complex data structures, or shipping
+complex data structures back and forth, that can make them one single
+combined program. A main program that uses simple fork and exec to
+invoke plug-ins and does not establish intimate communication between
+them results in the plug-ins being a separate program.
+
+<p> If the main program dynamically links plug-ins, and they make
+function calls to each other and share data structures, we believe
+they form a single combined program, which must be treated as an
+extension of both the main program and the plug-ins. If the main
+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>Using shared memory to communicate with complex data structures is
+pretty much equivalent to dynamic linking.</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>
+Please see this question <a href="#GPLPlugins">for determining when
+plug-ins and a main program are considered a single combined program
+and when they are considered separate works</a>.
+
+<p> If the main program and the plugins are a single combined program then
this means
+you must license the plug-in under the GPL or a GPL-compatible free
+software license and distribute it with source code in a GPL-compliant
+way. A main program that is separate from its plug-ins makes no
+requirements for the plug-ins. </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>
+GPL when writing a plug-in for a nonfree 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>
+ Please see this question <a href="#GPLPlugins">for determining when
+plug-ins and a main program are considered a single combined program
+and when they are considered separate programs</a>.
+<p> If they form a
+single combined program this means that combination of the GPL-covered
+plug-in with the nonfree 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 nonfree main
+program.</p>
+
+<p>See also the question <a href="#FSWithNFLibs">I am
+writing free software that uses a nonfree 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
+release a nonfree 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>
+ Please see this question <a href="#GPLPlugins">for determining when
+plug-ins and a main program are considered a single combined program
+and when they are considered separate programs</a>.
+<p>
+If they form a single combined program then the
+main program must be released under the GPL or a GPL-compatible free
+software license, and the terms of the GPL must be followed when
+the main program is distributed for use with these plug-ins.</p>
+
+<p>However, if they are separate works then the license of the plug-in
+makes no requirements about the main program.</p>
+
+<p>See also the question <a href="#FSWithNFLibs">I am
+writing free software that uses a nonfree 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
@@ -1380,7 +1391,7 @@
<dd>
Yes.
-<p></p></dd>
+</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
@@ -1436,7 +1447,7 @@
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>
+</p></dd>
<dt><b><a href="#TOCManyDifferentLicenses"
name="ManyDifferentLicenses">I have written an application that links
@@ -1457,7 +1468,7 @@
with a special exception allowing for linking with
QUUX”.</li>
</ul>
-<p></p></dd>
+</dd>
<dt><b><a href="#TOCMereAggregation" name="MereAggregation">What is
the difference between “mere aggregation” and
@@ -1585,8 +1596,8 @@
<dd>
-<p><a href="/licenses/lgpl-java.html">See this article for details.</a> It
works as designed, intended, and expected.
-</p></dd>
+<a href="/licenses/lgpl-java.html">See this article for details.</a> It works
as designed, intended, and expected.
+</dd>
<dt><b><a href="#TOCConsider" name="Consider">Consider this situation:
1. X releases V1 of a project under the GPL.
@@ -1598,7 +1609,7 @@
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>
+</dd>
<dt><b><a href="#TOCGPLInProprietarySystem"
@@ -1609,8 +1620,8 @@
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.
+incorporate GPL-covered software into a nonfree system, it would have
+the effect of making the GPL-covered software nonfree 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
@@ -1621,7 +1632,7 @@
<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,
+sure that the free and nonfree programs communicate at arms length,
that they are not combined in a way that would make them
effectively a single program.</p>
<p>
@@ -1654,11 +1665,11 @@
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
+<dd>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>
+licensed <em> as a whole </em> under the GNU GPL.
<p>The fact that proprietary module A communicates with GPL-covered
module C only through X11-licensed module B is legally irrelevant;
@@ -1668,8 +1679,8 @@
<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>
+<dd>Yes. The intent of the exception is to allow people to compile
+proprietary software using gcc.</dd>
<dt><b><a href="#TOCMoneyGuzzlerInc" name="MoneyGuzzlerInc">I'd like to
modify GPL-covered programs and link them with the portability
@@ -1732,7 +1743,7 @@
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>
+</dd>
<dt><b><a href="#TOCUnchangedJustBinary"
@@ -1743,7 +1754,7 @@
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>
+</dd>
<dt><b><a href="#TOCDistributeWithSourceOnInternet"
name="DistributeWithSourceOnInternet">I want to distribute binaries
@@ -1786,7 +1797,7 @@
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>
+</dd>
<dt><b><a href="#TOCSourceAndBinaryOnDifferentSites"
name="SourceAndBinaryOnDifferentSites">Can I put the binaries on my
@@ -1956,7 +1967,7 @@
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>
+</dd>
<dt><b><a href="#TOCWhySomeGPLAndNotLGPL"
name="WhySomeGPLAndNotLGPL">Why are some GNU libraries released under
@@ -2161,7 +2172,7 @@
</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>
+ a program under the GPL which I developed using nonfree tools?</a></b></dt>
<dd>
Which programs you used to edit the source code, or to compile it, or
@@ -2169,7 +2180,7 @@
concerning the licensing of that source code.
<p>
-However, if you link non-free libraries with the source code, that
+However, if you link nonfree 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
@@ -2246,7 +2257,7 @@
such translations soon.</p>
</li>
</ul>
-<p></p></dd>
+</dd>
<dt><b><a href="#TOCInterpreterIncompat" name="InterpreterIncompat">If
a programming language interpreter has a license that is incompatible
@@ -2283,7 +2294,7 @@
way, or add such exceptions to it. Only the copyright holders of that
code can add the exception.</li>
</ol>
-<p></p></dd>
+</dd>
<dt><b><a href="#TOCWhoHasThePower" name="WhoHasThePower">Who has the
power to enforce the GPL?</a></b></dt>
@@ -2296,7 +2307,7 @@
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>
+</dd>
<dt><b><a href="#TOCOOPLang" name="OOPLang"> In an object-oriented
@@ -2308,7 +2319,7 @@
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>
+</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
@@ -2320,7 +2331,7 @@
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
+These libraries can be used in nonfree 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
@@ -2471,7 +2482,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2017/02/17 06:30:24 $
+$Date: 2017/03/11 10:59:58 $
<!-- timestamp end -->
</p>
</div>
Index: po/gpl-2.0-faq.ru.po
===================================================================
RCS file: /web/www/www/licenses/old-licenses/po/gpl-2.0-faq.ru.po,v
retrieving revision 1.47
retrieving revision 1.48
diff -u -b -r1.47 -r1.48
--- po/gpl-2.0-faq.ru.po 11 Mar 2017 10:42:57 -0000 1.47
+++ po/gpl-2.0-faq.ru.po 11 Mar 2017 10:59:58 -0000 1.48
@@ -16,7 +16,6 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-"X-Outdated-Since: 2017-03-10 19:26+0000\n"
#. type: Content of: <title>
msgid ""
@@ -183,13 +182,6 @@
"измененнÑÑ
веÑÑий вÑÑÑавлÑлÑÑ Ð½Ð°
вÑеобÑее обозÑение?</a>"
#. type: Content of: <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>
-#| msgid ""
-#| "<a href=\"#GPLAndNonfreeOnSameMachine\" name="
-#| "\"TOCGPLAndNonfreeOnSameMachine\"> Can I have a GPL-covered program and "
-#| "an unrelated non-free program on the same computer?</a>"
msgid ""
"<a href=\"#GPLAndNonfreeOnSameMachine\" name=\"TOCGPLAndNonfreeOnSameMachine"
"\"> Can I have a GPL-covered program and an unrelated nonfree program on the "
@@ -439,13 +431,6 @@
"пÑодÑкÑ?</a>"
#. type: Content of: <ul><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>
-#| msgid ""
-#| "<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>"
msgid ""
"<a href=\"#ReleaseUnderGPLAndNF\" name=\"TOCReleaseUnderGPLAndNF\">I would "
"like to release a program I wrote under the GNU GPL, but I would like to use "
@@ -499,11 +484,6 @@
"Ñаблонов ÑиÑÑÐµÐ¼Ñ Ð¿Ð¾Ð´Ð´ÐµÑжки ÑайÑа?</a>"
#. type: Content of: <ul><li>
-# | <a href=\"#NonFreeTools\" name=\"TOCNonFreeTools\">Can I release a program
-# | under the GPL which I developed using non[---]free tools?</a>
-#| msgid ""
-#| "<a href=\"#NonFreeTools\" name=\"TOCNonFreeTools\">Can I release a "
-#| "program under the GPL which I developed using non-free tools?</a>"
msgid ""
"<a href=\"#NonFreeTools\" name=\"TOCNonFreeTools\">Can I release a program "
"under the GPL which I developed using nonfree tools?</a>"
@@ -698,13 +678,6 @@
"пÑогÑамм"
#. type: Content of: <ul><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>
-#| msgid ""
-#| "<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>"
msgid ""
"<a href=\"#CanIUseGPLToolsForNF\" name=\"TOCCanIUseGPLToolsForNF\">Can I use "
"GPL-covered editors such as GNU Emacs to develop nonfree programs? Can I use "
@@ -878,11 +851,6 @@
"лиÑензиÑм модÑлÑ?</a>"
#. type: Content of: <ul><li>
-# | <a href=\"#GPLPluginsInNF\" name=\"TOCGPLPluginsInNF\">Can I apply the GPL
-# | when writing a plug-in for a non[---]free program?</a>
-#| msgid ""
-#| "<a href=\"#GPLPluginsInNF\" name=\"TOCGPLPluginsInNF\">Can I apply the "
-#| "GPL when writing a plug-in for a non-free program?</a>"
msgid ""
"<a href=\"#GPLPluginsInNF\" name=\"TOCGPLPluginsInNF\">Can I apply the GPL "
"when writing a plug-in for a nonfree program?</a>"
@@ -891,11 +859,6 @@
"когда пиÑÑ Ð²Ð½ÐµÑний модÑÐ»Ñ Ðº неÑвободной
пÑогÑамме?</a>"
#. type: Content of: <ul><li>
-# | <a href=\"#NFUseGPLPlugins\" name=\"TOCNFUseGPLPlugins\">Can I release a
-# | non[---]free program that's designed to load a GPL-covered plug-in?</a>
-#| msgid ""
-#| "<a href=\"#NFUseGPLPlugins\" name=\"TOCNFUseGPLPlugins\">Can I release a "
-#| "non-free program that's designed to load a GPL-covered plug-in?</a>"
msgid ""
"<a href=\"#NFUseGPLPlugins\" name=\"TOCNFUseGPLPlugins\">Can I release a "
"nonfree program that's designed to load a GPL-covered plug-in?</a>"
@@ -929,11 +892,6 @@
"GPL, и неÑвободной ÑаÑÑÑÑ?</a>"
#. type: Content of: <ul><li>
-# | <a href=\"#FSWithNFLibs\" name=\"TOCFSWithNFLibs\"> Can I write free
-# | software that uses non[---]free libraries?</a>
-#| msgid ""
-#| "<a href=\"#FSWithNFLibs\" name=\"TOCFSWithNFLibs\"> Can I write free "
-#| "software that uses non-free libraries?</a>"
msgid ""
"<a href=\"#FSWithNFLibs\" name=\"TOCFSWithNFLibs\"> Can I write free "
"software that uses nonfree libraries?</a>"
@@ -1340,13 +1298,6 @@
"опÑеделеннÑми ÑпоÑобами; но Ð²Ñ Ð²Ð¿Ð¾Ð»Ð½Ðµ
можеÑе ÑеÑаÑÑ, вÑпÑÑкаÑÑ ÐµÐµ или неÑ."
#. type: Content of: <dl><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>
-#| msgid ""
-#| "<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>"
msgid ""
"<b><a href=\"#TOCGPLAndNonfreeOnSameMachine\" name="
"\"GPLAndNonfreeOnSameMachine\"> Can I have a GPL-covered program and an "
@@ -1574,15 +1525,6 @@
"плаÑил мне или извеÑал менÑ?</a>"
#. type: Content of: <dl><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>.
-#| msgid ""
-#| "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>."
msgid ""
"No. In fact, a requirement like that would make the program nonfree. If "
"people have to pay when they get a copy of a program, or if they have to "
@@ -1927,11 +1869,6 @@
"по GNU GPL. ÐÑÑÐ³Ð°Ñ Ð»Ð¸ÑÐµÐ½Ð·Ð¸Ñ ÑовмеÑÑима Ñ GPL,
еÑли она Ñоже ÑазÑеÑÐ°ÐµÑ ÑÑо."
#. type: Content of: <dl><dt>
-# | <b><a href=\"#TOCFSWithNFLibs\" name=\"FSWithNFLibs\">Can I write free
-# | software that uses non[---]free libraries?</a></b>
-#| msgid ""
-#| "<b><a href=\"#TOCFSWithNFLibs\" name=\"FSWithNFLibs\">Can I write free "
-#| "software that uses non-free libraries?</a></b>"
msgid ""
"<b><a href=\"#TOCFSWithNFLibs\" name=\"FSWithNFLibs\">Can I write free "
"software that uses nonfree libraries?</a></b>"
@@ -1940,17 +1877,6 @@
"ÑвободнÑÑ Ð¿ÑогÑаммÑ, коÑоÑÐ°Ñ Ð¿Ð¾Ð»ÑзÑеÑÑÑ
неÑвободнÑми библиоÑеками?</a>"
#. type: Content of: <dl><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.
-#| msgid ""
-#| "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."
msgid ""
"If you do this, your program won't be fully usable in a free environment. If "
"your program depends on a nonfree library to do a certain job, it cannot do "
@@ -1975,23 +1901,6 @@
"библиоÑеки?"
#. type: Content of: <dl><dd><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.
-#| msgid ""
-#| "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."
msgid ""
"If the program is already written using the nonfree library, perhaps it is "
"too late to change the decision. You may as well release the program as it "
@@ -2011,15 +1920,6 @@
"ÑабоÑÑ Ð½Ð°Ð´ пÑогÑаммой, пÑежде вÑего
оÑвободиÑÑ ÐµÐµ Ð¾Ñ ÑÑой завиÑимоÑÑи."
#. type: Content of: <dl><dd><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.
-#| msgid ""
-#| "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."
msgid ""
"Note that there may also be legal issues with combining certain nonfree "
"libraries with GPL-covered Free Software. Please see <a href="
@@ -2211,13 +2111,6 @@
"Ð´Ð»Ñ ÑвоиÑ
ÑекÑÑов — они Ñами ÑеÑаÑÑ,
ÑделаÑÑ Ð»Ð¸ ÑÑо."
#. type: Content of: <dl><dd><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>.
-#| msgid ""
-#| "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>."
msgid ""
"If the libraries you intend to link with are nonfree, please also see <a "
"href=\"#FSWithNFLibs\">the section on writing Free Software which uses "
@@ -2388,13 +2281,6 @@
"ÑвлÑеÑÑÑ Ð»Ð¸Ñензией, коÑоÑаÑ
ÑаÑпÑоÑÑÑанÑеÑÑÑ Ð½Ð° ваÑÑ ÐºÐ¾Ð¿Ð¸Ñ."
#. type: Content of: <dl><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>
-#| msgid ""
-#| "<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>"
msgid ""
"<b><a href=\"#TOCReleaseUnderGPLAndNF\" name=\"ReleaseUnderGPLAndNF\">I "
"would like to release a program I wrote under the GNU GPL, but I would like "
@@ -2405,15 +2291,6 @@
"иÑполÑзоваÑÑ Ñе же иÑÑ
однÑе ÑекÑÑÑ Ð²
неÑвободнÑÑ
пÑогÑаммаÑ
.</a>"
#. type: Content of: <dl><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.
-#| msgid ""
-#| "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."
msgid ""
"To release a nonfree program is always ethically tainted, but legally there "
"is no obstacle to your doing this. If you are the copyright holder for the "
@@ -2476,13 +2353,6 @@
"ÑÑловиÑÑ
GPL и ÑÑо пÑаво не Ð¼Ð¾Ð¶ÐµÑ Ð±ÑÑÑ
оÑозвано."
#. type: Content of: <dl><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>
-#| msgid ""
-#| "<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>"
msgid ""
"<b><a href=\"#TOCCanIUseGPLToolsForNF\" name=\"CanIUseGPLToolsForNF\">Can I "
"use GPL-covered editors such as GNU Emacs to develop nonfree programs? Can I "
@@ -2522,17 +2392,6 @@
"авÑоÑÑко-пÑавовой ÑÑаÑÑÑ Ð²Ñ
однÑÑ
даннÑÑ
."
#. type: Content of: <dl><dd><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.
-#| msgid ""
-#| "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."
msgid ""
"As it happens, Bison can also be used to develop nonfree programs. This is "
"because we decided to explicitly permit the use of the Bison standard parser "
@@ -3032,11 +2891,6 @@
"модÑлей, Ñо ÑÑо не Ð½Ð°Ð»Ð°Ð³Ð°ÐµÑ ÑÑебований на
внеÑние модÑли."
#. type: Content of: <dl><dt>
-# | <b><a href=\"#TOCGPLPluginsInNF\" name=\"GPLPluginsInNF\">Can I apply the
-# | GPL when writing a plug-in for a non[---]free program?</a></b>
-#| msgid ""
-#| "<b><a href=\"#TOCGPLPluginsInNF\" name=\"GPLPluginsInNF\">Can I apply the "
-#| "GPL when writing a plug-in for a non-free program?</a></b>"
msgid ""
"<b><a href=\"#TOCGPLPluginsInNF\" name=\"GPLPluginsInNF\">Can I apply the "
"GPL when writing a plug-in for a nonfree program?</a></b>"
@@ -3055,17 +2909,6 @@
"или ÑазделÑнÑми пÑогÑаммами</a>."
#. type: Content of: <dl><dd><p>
-# | If they form a single combined program 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.
-#| msgid ""
-#| "If they form a single combined program 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."
msgid ""
"If they form a single combined program this means that combination of the "
"GPL-covered plug-in with the nonfree main program would violate the GPL. "
@@ -3080,11 +2923,6 @@
"главной пÑогÑаммой."
#. type: Content of: <dl><dd><p>
-# | See also the question <a href=\"#FSWithNFLibs\">I am writing free software
-# | that uses a non[---]free library.</a>
-#| msgid ""
-#| "See also the question <a href=\"#FSWithNFLibs\">I am writing free "
-#| "software that uses a non-free library.</a>"
msgid ""
"See also the question <a href=\"#FSWithNFLibs\">I am writing free software "
"that uses a nonfree library.</a>"
@@ -3093,12 +2931,6 @@
"пÑогÑамм Ñ Ð¸ÑполÑзованием неÑвободнÑÑ
библиоÑек</a>."
#. type: Content of: <dl><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>
-#| msgid ""
-#| "<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>"
msgid ""
"<b><a href=\"#TOCNFUseGPLPlugins\" name=\"NFUseGPLPlugins\">Can I release a "
"nonfree program that's designed to load a GPL-covered plug-in?</a></b>"
@@ -3589,17 +3421,6 @@
"ÑиÑÑемÑ. Ðожно мне ÑÑо делаÑÑ?</a>"
#. type: Content of: <dl><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.
-#| msgid ""
-#| "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."
msgid ""
"You cannot incorporate GPL-covered software in a proprietary system. The "
"goal of the GPL is to grant everyone the freedom to copy, redistribute, "
@@ -3629,17 +3450,6 @@
"вÑоÑÑÑ
, ÑÑÐ¾Ð±Ñ Ð¿Ð¾Ð¾ÑÑиÑÑ Ð»Ñдей возвÑаÑаÑÑ
ÑлÑÑÑениÑ, коÑоÑÑе они делаÑÑ."
#. type: Content of: <dl><dd><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.
-#| msgid ""
-#| "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."
msgid ""
"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 "
@@ -4751,11 +4561,6 @@
"ÑдалиÑе замеÑание об ÑÑом иÑклÑÑении из
Ñвоей веÑÑии."
#. type: Content of: <dl><dt>
-# | <b><a href=\"#TOCNonFreeTools\" name=\"NonFreeTools\">Can I release a
-# | program under the GPL which I developed using non[---]free tools?</a></b>
-#| msgid ""
-#| "<b><a href=\"#TOCNonFreeTools\" name=\"NonFreeTools\">Can I release a "
-#| "program under the GPL which I developed using non-free tools?</a></b>"
msgid ""
"<b><a href=\"#TOCNonFreeTools\" name=\"NonFreeTools\">Can I release a "
"program under the GPL which I developed using nonfree tools?</a></b>"
@@ -4774,19 +4579,6 @@
"вопÑоÑов, ÑвÑзаннÑÑ
Ñ Ð»Ð¸ÑензиÑованием
ÑÑого иÑÑ
одного ÑекÑÑа."
#. type: Content of: <dl><dd><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.
-#| msgid ""
-#| "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."
msgid ""
"However, if you link nonfree libraries with the source code, that would be "
"an issue you need to deal with. It does not preclude releasing the source "
@@ -5087,21 +4879,6 @@
"GPL или дÑÑгой лиÑензией ÑвободнÑÑ
пÑогÑамм?</a>"
#. type: Content of: <dl><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.
-#| msgid ""
-#| "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."
msgid ""
"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 "
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- www/licenses/old-licenses gpl-2.0-faq.ru.html p...,
GNUN <=