[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www licenses/gpl-faq.it.html licenses/gpl-viola...
|
From: |
GNUN |
|
Subject: |
www licenses/gpl-faq.it.html licenses/gpl-viola... |
|
Date: |
Sun, 26 Mar 2017 15:00:36 -0400 (EDT) |
CVSROOT: /web/www
Module name: www
Changes by: GNUN <gnun> 17/03/26 15:00:34
Modified files:
licenses : gpl-faq.it.html gpl-violation.it.html
license-list.it.html
licenses/old-licenses: gpl-2.0-faq.it.html
licenses/old-licenses/po: gpl-2.0-faq.it-en.html
gpl-2.0-faq.it.po
licenses/po : gpl-faq.it-en.html gpl-violation.it-en.html
gpl-violation.it.po license-list.it-en.html
license-list.it.po
philosophy : javascript-trap.it.html not-ipr.it.html
selling.it.html words-to-avoid.it.html
philosophy/po : javascript-trap.it-en.html
javascript-trap.it.po not-ipr.it-en.html
not-ipr.it.po selling.it-en.html selling.it.po
words-to-avoid.it-en.html words-to-avoid.it.po
proprietary : malware-apple.it.html
proprietary-censorship.it.html
proprietary/po : malware-amazon.it-diff.html
malware-amazon.it.po malware-apple.it-diff.html
malware-apple.it.po malware-microsoft.it.po
malware-mobiles.it-diff.html
malware-mobiles.it.po
proprietary-back-doors.it-diff.html
proprietary-back-doors.it.po
proprietary-censorship.it-diff.html
proprietary-censorship.it.po
proprietary-drm.it-diff.html
proprietary-drm.it.po
proprietary-insecurity.it.po
proprietary-sabotage.it-diff.html
proprietary-sabotage.it.po
proprietary-surveillance.it-diff.html
proprietary-surveillance.it.po
proprietary-tyrants.it-diff.html
proprietary-tyrants.it.po
proprietary.it-diff.html proprietary.it.po
server/po : sitemap.it-en.html sitemap.it.po
Log message:
Automatic update by GNUnited Nations.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/gpl-faq.it.html?cvsroot=www&r1=1.19&r2=1.20
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/gpl-violation.it.html?cvsroot=www&r1=1.22&r2=1.23
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/license-list.it.html?cvsroot=www&r1=1.106&r2=1.107
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/old-licenses/gpl-2.0-faq.it.html?cvsroot=www&r1=1.24&r2=1.25
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/old-licenses/po/gpl-2.0-faq.it-en.html?cvsroot=www&r1=1.19&r2=1.20
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/old-licenses/po/gpl-2.0-faq.it.po?cvsroot=www&r1=1.39&r2=1.40
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gpl-faq.it-en.html?cvsroot=www&r1=1.7&r2=1.8
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gpl-violation.it-en.html?cvsroot=www&r1=1.10&r2=1.11
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gpl-violation.it.po?cvsroot=www&r1=1.12&r2=1.13
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/license-list.it-en.html?cvsroot=www&r1=1.84&r2=1.85
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/license-list.it.po?cvsroot=www&r1=1.275&r2=1.276
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/javascript-trap.it.html?cvsroot=www&r1=1.6&r2=1.7
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/not-ipr.it.html?cvsroot=www&r1=1.38&r2=1.39
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/selling.it.html?cvsroot=www&r1=1.28&r2=1.29
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/words-to-avoid.it.html?cvsroot=www&r1=1.90&r2=1.91
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/javascript-trap.it-en.html?cvsroot=www&r1=1.6&r2=1.7
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/javascript-trap.it.po?cvsroot=www&r1=1.22&r2=1.23
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/not-ipr.it-en.html?cvsroot=www&r1=1.20&r2=1.21
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/not-ipr.it.po?cvsroot=www&r1=1.54&r2=1.55
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/selling.it-en.html?cvsroot=www&r1=1.20&r2=1.21
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/selling.it.po?cvsroot=www&r1=1.27&r2=1.28
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/words-to-avoid.it-en.html?cvsroot=www&r1=1.80&r2=1.81
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/words-to-avoid.it.po?cvsroot=www&r1=1.220&r2=1.221
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/malware-apple.it.html?cvsroot=www&r1=1.20&r2=1.21
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/proprietary-censorship.it.html?cvsroot=www&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/malware-amazon.it-diff.html?cvsroot=www&r1=1.3&r2=1.4
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/malware-amazon.it.po?cvsroot=www&r1=1.5&r2=1.6
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/malware-apple.it-diff.html?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/malware-apple.it.po?cvsroot=www&r1=1.75&r2=1.76
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/malware-microsoft.it.po?cvsroot=www&r1=1.94&r2=1.95
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/malware-mobiles.it-diff.html?cvsroot=www&r1=1.5&r2=1.6
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/malware-mobiles.it.po?cvsroot=www&r1=1.31&r2=1.32
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/proprietary-back-doors.it-diff.html?cvsroot=www&r1=1.3&r2=1.4
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/proprietary-back-doors.it.po?cvsroot=www&r1=1.72&r2=1.73
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/proprietary-censorship.it-diff.html?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/proprietary-censorship.it.po?cvsroot=www&r1=1.35&r2=1.36
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/proprietary-drm.it-diff.html?cvsroot=www&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/proprietary-drm.it.po?cvsroot=www&r1=1.25&r2=1.26
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/proprietary-insecurity.it.po?cvsroot=www&r1=1.83&r2=1.84
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/proprietary-sabotage.it-diff.html?cvsroot=www&r1=1.3&r2=1.4
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/proprietary-sabotage.it.po?cvsroot=www&r1=1.67&r2=1.68
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/proprietary-surveillance.it-diff.html?cvsroot=www&r1=1.16&r2=1.17
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/proprietary-surveillance.it.po?cvsroot=www&r1=1.144&r2=1.145
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/proprietary-tyrants.it-diff.html?cvsroot=www&r1=1.2&r2=1.3
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/proprietary-tyrants.it.po?cvsroot=www&r1=1.29&r2=1.30
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/proprietary.it-diff.html?cvsroot=www&r1=1.2&r2=1.3
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/proprietary.it.po?cvsroot=www&r1=1.37&r2=1.38
http://web.cvs.savannah.gnu.org/viewcvs/www/server/po/sitemap.it-en.html?cvsroot=www&r1=1.38&r2=1.39
http://web.cvs.savannah.gnu.org/viewcvs/www/server/po/sitemap.it.po?cvsroot=www&r1=1.130&r2=1.131
Patches:
Index: licenses/gpl-faq.it.html
===================================================================
RCS file: /web/www/www/licenses/gpl-faq.it.html,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -b -r1.19 -r1.20
--- licenses/gpl-faq.it.html 5 Mar 2017 14:29:32 -0000 1.19
+++ licenses/gpl-faq.it.html 26 Mar 2017 19:00:32 -0000 1.20
@@ -571,6 +571,9 @@
<li><a href="#GPLModuleLicense">Se aggiungo un modulo ad un altro coperto
dalla
GPL, devo usare la GPL come licenza per il mio modulo?</a></li>
+ <li><a href="#GPLPlugins">Quando un programma e i suoi plugin sono
considerati
+un unico programma combinato? </a></li>
+
<li><a href="#GPLAndPlugins">Se scrivo un plug-in per un programma
protetto da
GPL, quali requisiti sono imposti alle licenze che posso usare per
distribuire il mio programma?</a></li>
@@ -1719,47 +1722,57 @@
problema.</p></dd>
+<dt id="GPLPlugins">Quando un programma e i suoi plugin sono considerati un
unico programma
+combinato? <span class="anchor-reference-id">(<a
+href="#GPLPlugins"></a>)</span></dt>
+<dd><p>
+ Dipende da come il programma principale chiama i plugin. Se il programma
+principale usa fork e exec per chiamarli, e se tra loro c'è una
+comunicazione profonda che li porta a condividere strutture dati complesse,
+o a passarsi strutture dati complesse, allora è possibile considerarli come
+un unico programma combinato. Invece, se un programma principale usa
+semplicemente fork e exec per chiamare i plugin e non viene stabilita una
+comunicazione profonda allora i plugin si possono considerare programmi
+separati.</p>
+
+<p> Se il programma principale è collegato dinamicamente ai plug-in, ed essi
+effettuano reciproche chiamate a funzione e condividono delle strutture
+dati, allora si considerano i due come parti di un unico programma
+combinato. Se il programma principale è collegato dinamicamente ai plug-in,
+ma la comunicazione è limitata alla chiamata della funzione "main" del
+plugin con determinate optioni e all'attesa di una risposta, questo è un
+caso limite.</p>
+
+<p>Usare memoria condivisa per comunicare con strutture di dati complesse è
+pressoché equivalente a linkare dinamicamente.</p></dd>
+
+
<dt id="GPLAndPlugins">Se scrivo un plug-in per un programma protetto da GPL,
quali requisiti sono
imposti alle licenze che posso usare per distribuire il mio programma? <span
class="anchor-reference-id">(<a href="#GPLAndPlugins"
>#GPLAndPlugins</a>)</span></dt>
<dd><p>
-Dipende da come il programma invoca i suoi plug-in. Se il programma usa fork
-ed exec per invocare i plug-in, allora i plug-in sono programmi separati, e
-quindi la licenza del programma principale non impone nessun requisito per
-essi.</p>
+Si veda questa domanda per capire <a href="#GPLPlugins">quando i plugin e un
+programma principale sono da considerare programmi diversi e quando no</a>.</p>
-<p>Se il programma invece è linkato dinamicamente ai plug-in, ed essi
-effettuano reciproche chiamate a funzione e condividono delle strutture
-dati, allora si considerano i due come parti di un unico programma, e così i
-plug-in devono essere trattati come estensioni al programma
-principale. Questo significa che essi devono essere rilasciati sotto la GPL
-o sotto una licenza ad essa compatibile.</p>
-
-<p>Un caso ambiguo si ha quando il programma linka dinamicamente i plug-in, ma
-la comunicazione tra i due è limitata all'invocazione della funzione
-'principale' del plug-in con alcune opzioni ed all'attesa che questa
-termini.</p></dd>
+<p> Se il programma e i plugin sono un unico programma combinato, i plug-in
+devono essere rilasciati sotto la GPL o sotto una licenza ad essa
+compatibile, e che quando si distribuiscono i plug-in si devono rispettare
+le condizioni della GPL. Invece un programma principale separato dai plugin
+non impone alcun requisito su questi ultimi. </p></dd>
<dt id="GPLPluginsInNF">Posso usare la GPL per un plug-in destinato ad un
programma non libero?
<span class="anchor-reference-id">(<a href="#GPLPluginsInNF"
>#GPLPluginsInNF</a>)</span></dt>
<dd><p>
-Se il programma usa fork ed exec per invocare i plug-in, questi sono da
-considerarsi programmi separati, e quindi la licenza del programma
-principale non pone restrizioni alle licenze dei plug-in. Così, è possibile
-usare la GPL per un plug-in, e non ci sono requisiti particolari da
-soddisfare.</p>
-
-<p>Se invece il programma effettua un link dinamico dei plug-in, ed essi (il
-programma e i plug-in) effettuano delle reciproche chiamate a funzione e/o
-condividono delle strutture dati, allora li si considera formare un unico
-programma, e così i plug-in devono essere trattati come estensioni al
-programma principale. Ciò significa che linkare il plug-in GPL col programma
-principale sarebbe una violazione della GPL. Comunque, è possibile risolvere
-questo problema legale aggiungendo un'eccezione alla licenza del plug-in, la
-quale permetta di linkarlo col programma non libero in questione.</p>
+ Si veda questa domanda per capire <a href="#GPLPlugins">quando i plugin e un
+programma principale sono da considerare programmi diversi e quando no</a>.</p>
+<p> Se formano un unico programma combinato, collegare il plug-in GPL col
+programma principale non libero sarebbe una violazione della GPL. Comunque,
+è possibile risolvere questo problema legale aggiungendo un'eccezione alla
+licenza del plug-in, la quale permetta il collegamento col programma non
+libero in questione.</p>
<p>Per ulteriori dettagli, si veda la domanda <a href="#FSWithNFLibs">Se scrivo
programmi che fanno uso di librerie non libere</a>.</p></dd>
@@ -1768,28 +1781,18 @@
<dt id="NFUseGPLPlugins">Posso rilasciare un programma non libero che è
progettato per caricare un
plug-in coperto da GPL? <span class="anchor-reference-id">(<a
href="#NFUseGPLPlugins" >#NFUseGPLPlugins</a>)</span></dt>
+
<dd><p>
-Dipende da come il programma invoca i suoi plug-in. Per esempio, se il
-programma usa <em>solo</em> fork ed exec per invocare e comunicare con i
-plug-in, allora i plug-in sono programmi separati, e quindi la licenza del
-programma principale non impone nessun requisito per essi.</p>
-
-<p>Se il programma è linkato dinamicamente ai plug-in, ed essi effettuano
-reciproche chiamate a funzione e condividono delle strutture dati, allora si
-considerano i due come parti di un unico programma, e così i plug-in devono
-essere trattati come estensioni al programma principale. Per poter usare i
-plug-in protetti da GPL, il programma principale deve anch'esso essere
-rilasciato sotto la GPL o una licenza per software libero compatibile, ed i
-termini di licenza della GPL devono essere rispettati quando il programma
-viene distribuito per essere usato con questi plug-in.</p>
-
-<p>Un caso ambiguo si ha quando il programma linka dinamicamente i plug-in, ma
-la comunicazione tra i due è limitata all'invocazione della funzione
-'principale' del plug-in con alcune opzioni ed all'attesa che questa
-termini.</p>
+ Si veda questa domanda per capire <a href="#GPLPlugins">quando i plugin e un
+programma principale sono da considerare programmi diversi e quando no</a>.</p>
+<p>
+Se formano un unico programma combinato, il programma principale deve essere
+rilasciato sotto la GPL o sotto una licenza ad essa compatibile, e quando
+si distribuisce il programma principale per l'uso con questo plugin si
+devono rispettare le condizioni della GPL.</p>
-<p>Usare memoria condivisa per comunicare con strutture di dati complesse è
-pressoché equivalente a linkare dinamicamente.</p>
+<p>Tuttavia se sono programmi separati allora la licenza del plugin non impone
+alcun requisito sul programma principale.</p>
<p>Per ulteriori dettagli, si veda la domanda <a href="#FSWithNFLibs">Se scrivo
programmi che fanno uso di librerie non libere</a>.</p></dd>
@@ -3877,7 +3880,7 @@
<p class="unprintable"><!-- timestamp start -->
Ultimo aggiornamento:
-$Date: 2017/03/05 14:29:32 $
+$Date: 2017/03/26 19:00:32 $
<!-- timestamp end -->
</p>
Index: licenses/gpl-violation.it.html
===================================================================
RCS file: /web/www/www/licenses/gpl-violation.it.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -b -r1.22 -r1.23
--- licenses/gpl-violation.it.html 5 Jul 2014 05:28:58 -0000 1.22
+++ licenses/gpl-violation.it.html 26 Mar 2017 19:00:32 -0000 1.23
@@ -76,7 +76,12 @@
informazioni riguardo alla violazione del prodotto. Quindi, se usate un
indirizzo e-mail anonimo, per favore indicate comunque un modo per
ricontattarvi. Se desiderate criptare la vostra corrispondenza, inviate
-semplicemente una breve e-mail spiegandolo, provvederemo di conseguenza.</p>
+semplicemente una breve e-mail spiegandolo, provvederemo di
+conseguenza. Dato che la FSF sostiene <a
+href="https://www.fsf.org/licensing/enforcement-principles";>i principi di
+un'applicazione della GPL orientata alla comunità </a>, si può essere sicuri
+che le segnalazioni saranno usate per informare i violatori e non per
+punirli.</p>
<p>
Si noti che la GPL, come le altre licenze copyleft, sono licenze con
@@ -138,7 +143,7 @@
<!-- Regarding copyright, in general, standalone pages (as opposed to
files generated as part of manuals) on the GNU web server should
- be under CC BY-ND 3.0 US. Please do NOT change or remove this
+ be under CC BY-ND 4.0. 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
@@ -152,13 +157,12 @@
There is more detail about copyright years in the GNU Maintainers
Information document, www.gnu.org/prep/maintain. -->
-<p>Copyright © 1999, 2001, 2007, 2008, 2013, 2014 Free Software
+<p>Copyright © 1999, 2001, 2007, 2008, 2013, 2014, 2017 Free Software
Foundation, Inc.</p>
<p>Questa pagina è distribuita secondo i termini della licenza <a
rel="license"
-href="http://creativecommons.org/licenses/by-nd/3.0/us/deed.it";>Creative
-Commons Attribuzione - Non opere derivate 3.0 Stati Uniti</a> (CC BY-ND
-3.0).</p>
+href="http://creativecommons.org/licenses/by-nd/4.0/";>Creative Commons
+Attribuzione - Non opere derivate 4.0 internazionale</a> (CC BY-ND 4.0).</p>
<!--#include virtual="/server/bottom-notes.it.html" -->
<div class="translators-credits">
@@ -170,7 +174,7 @@
<p class="unprintable"><!-- timestamp start -->
Ultimo aggiornamento:
-$Date: 2014/07/05 05:28:58 $
+$Date: 2017/03/26 19:00:32 $
<!-- timestamp end -->
</p>
Index: licenses/license-list.it.html
===================================================================
RCS file: /web/www/www/licenses/license-list.it.html,v
retrieving revision 1.106
retrieving revision 1.107
diff -u -b -r1.106 -r1.107
--- licenses/license-list.it.html 18 Nov 2016 07:32:36 -0000 1.106
+++ licenses/license-list.it.html 26 Mar 2017 19:00:32 -0000 1.107
@@ -510,7 +510,7 @@
href="#Eiffel">#Eiffel</a>)</span></dt>
<dd>
<p>Questa è una licenza di software libero, compatibile con la GNU GPL. <a
-href="http://www.eiffel-nice.org/license/forum.txt";>Le versioni
+href="https://opensource.org/licenses/ver1_eiffel";>Le versioni
precedenti</a> della licenza Eiffel non sono compatibili con la GPL.</p></dd>
@@ -1984,9 +1984,9 @@
<dt><a id="Sybase"></a> <a id="Watcom"
-href="http://www.openwatcom.org/index.php/Open_Watcom_Public_License";>
-Sybase Open Watcom Public License, versione 1.0</a> <span
-class="anchor-reference-id"> (<a href="#Watcom">#Watcom</a>)</span></dt>
+href="ftp://ftp.openwatcom.org/install/license.txt";> Sybase Open Watcom
+Public License, versione 1.0</a> <span class="anchor-reference-id"> (<a
+href="#Watcom">#Watcom</a>)</span></dt>
<dd>
<p>Questa non è una licenza di software libero. Obbliga a pubblicare il codice
sorgente ogni volta che si rientra nei casi che licenza definisce col
@@ -2555,7 +2555,7 @@
href="/server/standards/README.translations.html">Guida alle
traduzioni</a>.</p>
</div>
-<p>Copyright © 2014, 2015, 2016 Free Software Foundation, Inc.</p>
+<p>Copyright © 2014, 2015, 2016, 2017 Free Software Foundation, Inc.</p>
<p>Questa pagina è distribuita secondo i termini della licenza <a
rel="license"
href="http://creativecommons.org/licenses/by-nd/4.0/";>Creative Commons
@@ -2571,7 +2571,7 @@
<p class="unprintable"><!-- timestamp start -->
Ultimo aggiornamento:
-$Date: 2016/11/18 07:32:36 $
+$Date: 2017/03/26 19:00:32 $
<!-- timestamp end -->
</p>
Index: licenses/old-licenses/gpl-2.0-faq.it.html
===================================================================
RCS file: /web/www/www/licenses/old-licenses/gpl-2.0-faq.it.html,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -b -r1.24 -r1.25
--- licenses/old-licenses/gpl-2.0-faq.it.html 5 Mar 2017 14:29:32 -0000
1.24
+++ licenses/old-licenses/gpl-2.0-faq.it.html 26 Mar 2017 19:00:32 -0000
1.25
@@ -300,10 +300,9 @@
<ul>
- <li><a href="#CanIUseGPLToolsForNF" name="TOCCanIUseGPLToolsForNF">Posso
-usare editor di testo protetti da GPL, come GNU Emacs, per sviluppare
-programmi non liberi? Posso usare strumenti protetti da GPL per
-compilarli?</a></li>
+ <li><a href="#CanIUseGPLToolsForNF" name="TOCCanIUseGPLToolsForNF">Posso
usare
+editor di testo protetti da GPL, come GNU Emacs, per sviluppare programmi
+non liberi? Posso usare strumenti protetti da GPL per compilarli?</a></li>
<li><a href="#GPLOutput" name="TOCGPLOutput">C'è qualche maniera per poter
proteggere con la GPL l'output che gli utenti ottengono usando il mio
@@ -370,6 +369,9 @@
ad un altro coperto dalla GPL, devo usare la GPL come licenza per il mio
modulo?</a></li>
+ <li><a href="#GPLPluginsInNF" name="TOCGPLPluginsInNF">Posso usare la GPL
per un
+plug-in destinato ad un programma non libero?</a></li>
+
<li><a href="#GPLAndPlugins" name="TOCGPLAndPlugins">Se un programma
rilasciato
sotto la GPL fa uso di plug-in, quali sono i requisiti da includere nelle
licenze di questi plug-in?</a></li>
@@ -475,7 +477,7 @@
Generica). La GPL più diffusa è la GNU General Public License, in breve
GNU GPL. L'ultimo acronimo può ancora essere abbreviato in "GPL", se dal
contesto si capisce che ci si sta riferendo alla GNU GPL.
-<p></p></dd>
+</dd>
<dt><b><a href="#TOCDoesFreeSoftwareMeanUsingTheGPL"
name="DoesFreeSoftwareMeanUsingTheGPL"> Scrivere software libero significa
@@ -487,7 +489,7 @@
incompleta). Una qualsiasi licenza che garantisca all'utente <a href=
"/philosophy/free-sw.html">alcune ben determinate libertà </a> è una
licenza per software libero.
-<p></p></dd>
+</dd>
<dt><b><a href="#TOCWhyUseGPL" name="WhyUseGPL"> Perché è meglio la GNU GPL
piuttosto che altre licenze per il software libero?</a></b></dt>
@@ -500,7 +502,7 @@
proprietaria. Tuttavia, in alcune situazioni particolari, può essere
preferibile l'uso di <a href="/licenses/why-not-lgpl.html">una licenza
più lasca</a>.
-<p></p></dd>
+</dd>
<dt><b><a href="#TOCDoesAllGNUSoftwareUseTheGNUGPLAsItsLicense"
name="DoesAllGNUSoftwareUseTheGNUGPLAsItsLicense"> Tutto il software GNU usa
@@ -511,7 +513,7 @@
programmi GNU (e parti di programmi) che usano licenze più lasche, come
la Lesser GPL (LGPL, GPL Attenuata). Quando questo accade, è una
questione di <a href= "/licenses/why-not-lgpl.html">strategia</a>.
-<p></p></dd>
+</dd>
<dt><b><a href="#TOCDoesUsingTheGPLForAProgramMakeItGNUSoftware"
name="DoesUsingTheGPLForAProgramMakeItGNUSoftware"> L'uso della GPL per un
@@ -541,7 +543,7 @@
Altrimenti, potrebbe essere chi si preoccupa della manutenzione del
programma a detenere il copyright, o essere in grado di dire dove
rivolgersi, quindi si può segnalare la cosa al manutentore del programma.
-<p></p></dd>
+</dd>
<dt><b><a href="#TOCWhyDoesTheGPLPermitUsersToPublishTheirModifiedVersions"
name="WhyDoesTheGPLPermitUsersToPublishTheirModifiedVersions"> Perché la GPL
@@ -605,7 +607,7 @@
Sì. La clausola di semplice aggregazione (“mere aggregation”)
della GPL esplicita questo permesso, ma pensiamo che il principio sarebbe
stato comunque valido, anche se non lo avessimo esplicitato.
-<p></p></dd>
+</dd>
<dt><b><a href="#TOCCanIDemandACopy" name="CanIDemandACopy">Se si sa che
qualcuno ha una copia di un programma con licenza GPL, è possibile
@@ -614,7 +616,7 @@
<dd>
No. La GPL dà il permesso di fare e ridistribuire copie del programma <em>se
e quando si desidera farlo</em>. Chi possiede una copia di un programma ha
-anche il diritto di non ridistribuirlo, se preferisce fare così.<p></p></dd>
+anche il diritto di non ridistribuirlo, se preferisce fare così.</dd>
<dt><b><a href="#TOCWhatDoesWrittenOfferValid"
name="WhatDoesWrittenOfferValid">
Che significa "written offer valid for any third party"? Vuol dire che
@@ -650,7 +652,7 @@
versione modificata <strong>faccia</strong> materialmente qualcosa per
queste persone. Significa soltanto che essi hanno la licenza dall'autore,
secondo la GPL, per la versione modificata.
-<p></p></dd>
+</dd>
<dt><b><a href="#TOCRequiredToClaimCopyright"
name="RequiredToClaimCopyright">Sono costretto ad applicare il copyright
@@ -679,7 +681,7 @@
e a separarla dal resto. Se il codice è stato classificato come di
pubblico dominio dal suo sviluppatore, rimane tale indipendentemente da
dove si trovi.
-<p></p></dd>
+</dd>
<dt><b><a href="#TOCDoesTheGPLAllowMoney" name="DoesTheGPLAllowMoney"> La GPL
mi
permette di vendere copie del programma a scopo di lucro?</a></b></dt>
@@ -691,7 +693,7 @@
restrizioni sul prezzo applicabile (lo specifico caso è l'offerta scritta
per ottenere il codice sorgente che è obbligatoria nel caso di distribuzioni
della sola forma eseguibile).
-<p></p></dd>
+</dd>
<dt><b><a href="#TOCDoesTheGPLAllowDownloadFee"
name="DoesTheGPLAllowDownloadFee"> La GPL mi permette di richiedere un
@@ -703,7 +705,7 @@
"accesso equivalente" per scaricare i sorgenti--quindi il pagamento
richiesto per scaricare i sorgenti non può essere maggiore di quello per
scaricare i binari.
-<p></p></dd>
+</dd>
<dt><b><a href="#TOCDoesTheGPLAllowRequireFee"
name="DoesTheGPLAllowRequireFee">
La GPL mi permette di richiedere che tutti quelli che ricevono il software
@@ -735,7 +737,7 @@
libertà di renderlo pubblico, a pagamento o gratuitamente. Per esempio,
qualcuno potrebbe pagarlo e poi metterne una copia su un sito web,
rendendolo pubblico.
-<p></p></dd>
+</dd>
<dt><b><a href="#TOCDoesTheGPLAllowNDA" name="DoesTheGPLAllowNDA"> La GPL mi
permette di distribuire una copia soggetta ad una clausola di non
@@ -764,7 +766,7 @@
elencate nella GPL. Quindi chiunque riceva una copia modificata ha
diritto di redistribuirne copie (modificate o meno). La GPL non dà il
diritto di redistribuire l'opera con termini più restrittivi.
-<p></p></dd>
+</dd>
<dt><b><a href="#TOCDevelopChangesUnderNDA" name="DevelopChangesUnderNDA"> La
GPL mi permette di sviluppare una versione modificata soggetta ad una
@@ -796,7 +798,7 @@
copyright al programma, copyright che va sotto il nome di chi lo rilascia
(se detentore del diritto d'autore). La GPL richiede che tutte le copie
del programma siano corredate di un'appropriata nota di copyright.
-<p></p></dd>
+</dd>
<dt><b><a href="#TOCWhyMustIInclude" name="WhyMustIInclude">Perché la GPL
richiede che ogni copia del programma sia corredata di una copia della
@@ -826,7 +828,7 @@
Se un singolo programma fosse così corto, si potrebbe anche usare una
semplice licenza che non ponga nessuna restrizione d'uso, piuttosto che
la GNU GPL.
-<p></p></dd>
+</dd>
<dt><b><a href="#TOCGPLOmitPreamble" name="GPLOmitPreamble"> Ã possibile
omettere, allo scopo di risparmiare spazio, il preambolo della GPL? O
@@ -1074,7 +1076,7 @@
<dd>
Si veda la pagina delle <a href= "/licenses/gpl-howto.html">GPL
instructions</a>.
-<p></p></dd>
+</dd>
<dt><b><a href="#TOCHeardOtherLicense" name="HeardOtherLicense">Ho sentito dire
che qualcuno ha ottenuto una copia di un programma coperto dalla GPL, ma
@@ -1101,7 +1103,7 @@
corretta, non ci sono di certo ostacoli legali se lo si vuol fare. Se si
possiede il copyright del codice, lo si può rilasciare sotto varie e non
esclusive licenze, in momenti differenti.
-<p></p></dd>
+</dd>
<dt><b><a href="#TOCDeveloperViolate" name="DeveloperViolate">Lo sviluppatore
di
un programma protetto da GPL è da essa vincolato? Lo sviluppatore potrebbe
@@ -1126,7 +1128,7 @@
<dd>
No, perché gli utenti hanno già ricevuto il diritto di usare il programma
sotto la GPL, e questo diritto non può essere ritirato.
-<p></p></dd>
+</dd>
<dt><b><a href="#TOCCanIUseGPLToolsForNF" name="CanIUseGPLToolsForNF">Posso
usare editor di testo protetti da GPL, come GNU Emacs, per sviluppare
@@ -1234,7 +1236,7 @@
<dd>
Solamente quando il programma copia parti di se stesso nel suo output.
-<p></p></dd>
+</dd>
<dt><b><a href="#TOCGPLModuleLicense" name="GPLModuleLicense">Se aggiungo un
modulo ad un altro coperto dalla GPL, devo usare la GPL come licenza per il
@@ -1345,81 +1347,80 @@
problema.
</p></dd>
+<dt><b><a href="#TOCGPLPlugins" name="GPLPlugins"> Quando un programma e i suoi
+plugin sono considerati un unico programma combinato? </a></b></dt>
+<dd>
+ Dipende da come il programma principale chiama i plugin. Se il programma
+principale usa fork e exec per chiamarli, e se tra loro c'è una
+comunicazione profonda che li porta a condividere strutture dati complesse,
+o a passarsi strutture dati complesse, allora è possibile considerarli come
+un unico programma combinato. Invece, se un programma principale usa
+semplicemente fork e exec per chiamare i plugin e non viene stabilita una
+comunicazione profonda allora i plugin si possono considerare programmi
+separati.
+
+<p> Se il programma principale è collegato dinamicamente ai plug-in, ed essi
+effettuano reciproche chiamate a funzione e condividono delle strutture
+dati, allora si considerano i due come parti di un unico programma
+combinato. Se il programma principale è collegato dinamicamente ai plug-in,
+ma la comunicazione è limitata alla chiamata della funzione "main" del
+plugin con determinate optioni e all'attesa di una risposta, questo è un
+caso limite.</p>
+
+<p>Usare memoria condivisa per comunicare con strutture dati complesse è molto
+simile al link dinamico.</p></dd>
+
+
<dt><b><a href="#TOCGPLAndPlugins" name="GPLAndPlugins">Se un programma
rilasciato sotto la GPL fa uso di plug-in, quali sono i requisiti da
includere nelle licenze di questi plug-in?</a></b></dt>
<dd>
-Dipende da come il programma fa girare i suoi plug-in. Se il programma
-usa fork ed exec per invocare i plug-in, allora i plug-in sono programmi
-separati, e quindi la licenza del programma principale non impone nessun
-requisito per essi.
-<p>
-Se il programma invece è collegato dinamicamente ai plug-in, ed essi
-effettuano reciproche chiamate a funzione e condividono delle strutture
-dati, allora si considerano i due come parti di un unico programma, e così
-i plug-in devono essere trattati come estensioni al programma
-principale. Questo significa che essi devono essere rilasciati sotto la GPL
-o sotto una licenza ad essa compatibile, e che quando si distribuiscono i
-plug-in si devono rispettare le condizioni della GPL.</p>
-<p>
-Un caso ambiguo si ha quando il programma collega dinamicamente i plug-in,
-ma la comunicazione tra i due è limitata all'invocazione della funzione
-'principale' del plug-in con alcune opzioni ed all'attesa che questa
-termini.
-</p></dd>
+Si veda questa domanda per capire <a href="#GPLPlugins">quando i plugin e un
+programma principale sono da considerare programmi diversi e quando no</a>.
+
+<p> Se il programma e i plugin sono un unico programma combinato, i plug-in
+devono essere rilasciati sotto la GPL o sotto una licenza ad essa
+compatibile, e che quando si distribuiscono i plug-in si devono rispettare
+le condizioni della GPL. Invece un programma principale separato dai plugin
+non impone alcun requitio su questi ultimi. </p></dd>
+
<dt><b><a href="#TOCGPLPluginsInNF" name="GPLPluginsInNF">Posso usare la GPL
per
un plug-in destinato ad un programma non libero?</a></b></dt>
<dd>
-Se il programma usa <em>fork</em> ed <em>exec</em> per invocare i
-plug-in, questi sono da considerarsi programmi separati, e quindi la
-licenza del programma principale non pone restrizioni alle licenze dei
-plug-in. Così, è possibile usare la GPL per un plug-in, e non ci sono
-requisiti particolari da soddisfare.
-<p>
-Se invece il programma effettua un collegamento dinamico dei plug-in, ed
-essi (il programma e i plug-in) effettuano delle reciproche chiamate a
-funzione e condividono delle strutture dati, allora li si considera formare
-un unico programma, che deve essere trattato come estensione del programma
-principale e dei plug-in. Ciò significa che collegare il plug-in GPL col
+ Si veda questa domanda per capire <a href="#GPLPlugins">quando i plugin e un
+programma principale sono da considerare programmi diversi e quando no</a>.
+<p> Se formano un unico programma combinato, collegare il plug-in GPL col
programma principale non libero sarebbe una violazione della GPL. Comunque,
è possibile risolvere questo problema legale aggiungendo un'eccezione alla
licenza del plug-in, la quale permetta il collegamento col programma non
libero in questione.</p>
-<p>
-Vedere anche "<a href="#FSWithNFLibs">Posso scrivere programmi liberi che
-fanno uso di librerie non libere?</a>".
-</p></dd>
+
+<p>Vedere anche "<a href="#FSWithNFLibs">Posso scrivere programmi liberi che
+fanno uso di librerie non libere?</a>".</p></dd>
+
<dt><b><a href="#TOCNFUseGPLPlugins" name="NFUseGPLPlugins">Posso rilasciare un
programma non libero che ha come scopo quello di caricare un plug-in coperto
da GPL?</a></b></dt>
<dd>
-Dipende da come il programma fa girare i suoi plug-in. Se il programma
-usa fork ed exec per invocare i plug-in, allora i plug-in sono programmi
-separati, e quindi la licenza del programma principale non impone nessun
-requisito per essi.
-<p>
-Se invece il programma effettua un collegamento dinamico dei plug-in, ed
-essi (il programma e i plug-in) effettuano delle reciproche chiamate a
-funzione e condividono delle strutture dati, allora li si considera formare
-un unico programma, che deve essere trattato come estensione del programma
-principale e dei plug-in. Quindi per usare il plug-in GPL il programma
-principale deve avere licenza GPL o compatibile, e si deve rispettare la GPL
-quando si distribuisce il programma principale per l'utilizzo con questi
-plug-in.</p>
-<p>
-Un caso ambiguo si ha quando il programma collega dinamicamente i plug-in,
-ma la comunicazione tra i due è limitata all'invocazione della funzione
-'principale' del plug-in con alcune opzioni ed all'attesa che questa
-termini.</p>
+ Si veda questa domanda per capire <a href="#GPLPlugins">quando i plugin e un
+programma principale sono da considerare programmi diversi e quando no</a>.
<p>
-Vedere anche "<a href="#FSWithNFLibs">Posso scrivere programmi liberi che
-fanno uso di librerie non libere?</a>".
-</p></dd>
+Se formano un unico programma combinato, il programma principale deve essere
+rilasciato sotto la GPL o sotto una licenza ad essa compatibile, e quando
+si distribuisce il programma principale for l'uso con questo plugin si
+devono rispettare le condizioni della GPL.</p>
+
+<p>Tuttavia se sono programmi separati allora la licenza del plugin non impone
+alcun requisito sul programma principale.</p>
+
+<p>Vedere anche "<a href="#FSWithNFLibs">Posso scrivere programmi liberi che
+fanno uso di librerie non libere?</a>".</p></dd>
+
<dt><b><a href="#TOCLinkingWithGPL" name="LinkingWithGPL">Tu hai un programma
sotto GPL a cui vorrei collegare del mio codice per costruire un programma
@@ -1428,7 +1429,7 @@
<dd>
Sì.
-<p></p></dd>
+</dd>
<dt><b><a href="#TOCSwitchToLGPL" name="SwitchToLGPL">Se è così, c'è qualche
speranza che io possa ottenere una licenza del tuo programma sotto Lesser
@@ -1486,7 +1487,7 @@
di altri programmi protetti dalla GPL nel proprio codice, non è possibile
autorizzare l'eccezione per quelle parti: bisogna ottenere l'assenso dai
detentori dei diritti d'autore del programma.
-</p><p></p></dd>
+</p></dd>
<dt><b><a href="#TOCManyDifferentLicenses" name="ManyDifferentLicenses">Ho
scritto una applicazione che è collegata ad altro software con licenze
@@ -1505,7 +1506,7 @@
che ho scritto io) per far funzionare il programma BAR, che è sotto
licenza "GPL ma con il permesso speciale di collegarlo con QUUX".</li>
</ul>
-<p></p></dd>
+</dd>
<dt><b><a href="#TOCMereAggregation" name="MereAggregation">Qual è la
differenza
tra "semplice aggregazione" e "fondere due moduli in un
programma"?</a></b></dt>
@@ -1632,9 +1633,9 @@
<dd>
-<p>Per i dettagli <a href="/licenses/lgpl-java.html">vedere questo
+Per i dettagli <a href="/licenses/lgpl-java.html">vedere questo
articolo</a>. Funziona come previsto e desiderato.
-</p></dd>
+</dd>
<dt><b><a href="#TOCConsider" name="Consider">Prendiamo in esame questa
situazione: 1. X rilascia la versione 1 di un progetto sotto GPL. 2. Y
@@ -1648,7 +1649,7 @@
basandosi sulla prima versione di X. Nessuno può obbligare Y a accettare
altre licenze per il suo codice. Quindi, X deve avere il permesso di Y
per rilasciare il codice sotto un'altra licenza.
-<p></p></dd>
+</dd>
<dt><b><a href="#TOCGPLInProprietarySystem" name="GPLInProprietarySystem">Mi
@@ -1707,11 +1708,11 @@
la licenza di X11) tra la parte coperta da GPL e la parte
proprietaria?</a></b></dt>
-<dd><p>No. La licenza di X11 è compatibile con la GPL, quindi si può
aggiungere un
+<dd>No. La licenza di X11 è compatibile con la GPL, quindi si può aggiungere
un
modulo al programma coperto da GPL e mettere questo modulo sotto la licenza
di X11. Ma se si volesse incorporare il tutto in un programma più grande,
allora la presenza di una parte protetta da GPL implicherebbe che <em>
-tutto quanto </em> debba essere protetto con licenza GPL.</p>
+tutto quanto </em> debba essere protetto con licenza GPL.
<p>Il fatto che il modulo proprietario A comunichi con il modulo C (protetto da
GPL) solo attraverso il modulo B (distribuito con la licenza di X11) è
@@ -1722,8 +1723,8 @@
<dt><b><a href="#TOCLibGCCException" name="LibGCCException"> L'eccezione
libstdc++ permette il linking dinamico?</a></b></dt>
-<dd><p>Sì. Scopo di questa eccezione è quello di permettere di compilare
software
-proprietario con gcc.</p></dd>
+<dd>Sì. Scopo di questa eccezione è quello di permettere di compilare
software
+proprietario con gcc.</dd>
<dt><b><a href="#TOCMoneyGuzzlerInc" name="MoneyGuzzlerInc">Vorrei modificare
dei programmi coperti da licenza GPL e linkare i medesimi con le librerie
@@ -1786,7 +1787,7 @@
versioni modificate siano <a href="/philosophy/free-sw.html"> software
libero</a>, e in particolare che il codice sorgente delle versioni
modificate sia disponibile agli utenti.
-<p></p></dd>
+</dd>
<dt><b><a href="#TOCUnchangedJustBinary" name="UnchangedJustBinary">Ho
scaricato
@@ -1797,7 +1798,7 @@
distribuire anche il corrispondente codice sorgente. Fa eccezione il caso,
poco diffuso, in cui si sia ricevuta un'offerta scritta per il codice
sorgente.
-<p></p></dd>
+</dd>
<dt><b><a href="#TOCDistributeWithSourceOnInternet"
name="DistributeWithSourceOnInternet">Voglio distribuire i binari di un
@@ -1841,7 +1842,7 @@
infatti la GPL impone che il vostro amico vi passi anche una copia
dell'offerta insieme a una copia dei binari, proprio perché possiate usarla
se volete.
-<p></p></dd>
+</dd>
<dt><b><a href="#TOCSourceAndBinaryOnDifferentSites"
name="SourceAndBinaryOnDifferentSites">Posso mettere i binari sul mio
@@ -2012,7 +2013,7 @@
distribuzione. Si tratta di un caso diverso da quello del furto sopra
esaminato: nel caso del furto la distribuzione non è intenzionale e quindi
l'azienda non ha violato la GPL.
-<p></p></dd>
+</dd>
<dt><b><a href="#TOCWhySomeGPLAndNotLGPL" name="WhySomeGPLAndNotLGPL">Per
quale motivo alcune librerie GNU sono rilasciate sotto la normale licenza
@@ -2305,7 +2306,7 @@
tipo di traduzioni.</p>
</li>
</ul>
-<p></p></dd>
+</dd>
<dt><b><a href="#TOCInterpreterIncompat" name="InterpreterIncompat">Se
l'interprete di un linguaggio di programmazione ha una licenza che lo rende
@@ -2343,7 +2344,7 @@
questo modo, o aggiungervi la suddetta eccezione. Soltanto i detentori
dei diritti d'autore di quel codice possono aggiungere l'eccezione.</li>
</ol>
-<p></p></dd>
+</dd>
<dt><b><a href="#TOCWhoHasThePower" name="WhoHasThePower">Chi ha il potere di
far valere la GPL?</a></b></dt>
@@ -2356,7 +2357,7 @@
raggiungere i detentori dei diritti d'autore. <a
href="http://www.fsf.org/licenses/gpl-faq.html#ReportingViolation";>Altre
informazioni su come trattare le violazioni della GPL</a>.
-<p></p></dd>
+</dd>
<dt><b><a href="#TOCOOPLang" name="OOPLang"> In un linguaggio orientato agli
@@ -2368,7 +2369,7 @@
Creare una sottoclasse si configura come lavoro derivato: di conseguenza
i termini della GPL si applicano a tutto il programma risultante dalla
creazione di una classe figlia della classe coperta da GPL.
-<p></p></dd>
+</dd>
<dt><b><a href="#TOCPortProgramToGL" name="PortProgramToGL">Se porto il mio
programma su GNU/Linux, devo rilasciarlo come software libero coperto dalla
@@ -2560,7 +2561,7 @@
<p class="unprintable"><!-- timestamp start -->
Ultimo aggiornamento:
-$Date: 2017/03/05 14:29:32 $
+$Date: 2017/03/26 19:00:32 $
<!-- timestamp end -->
</p>
Index: licenses/old-licenses/po/gpl-2.0-faq.it-en.html
===================================================================
RCS file: /web/www/www/licenses/old-licenses/po/gpl-2.0-faq.it-en.html,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -b -r1.19 -r1.20
--- licenses/old-licenses/po/gpl-2.0-faq.it-en.html 5 Mar 2017 14:29:32
-0000 1.19
+++ licenses/old-licenses/po/gpl-2.0-faq.it-en.html 26 Mar 2017 19:00:32
-0000 1.20
@@ -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/03/05 14:29:32 $
+$Date: 2017/03/26 19:00:32 $
<!-- timestamp end -->
</p>
</div>
Index: licenses/old-licenses/po/gpl-2.0-faq.it.po
===================================================================
RCS file: /web/www/www/licenses/old-licenses/po/gpl-2.0-faq.it.po,v
retrieving revision 1.39
retrieving revision 1.40
diff -u -b -r1.39 -r1.40
--- licenses/old-licenses/po/gpl-2.0-faq.it.po 26 Mar 2017 13:57:50 -0000
1.39
+++ licenses/old-licenses/po/gpl-2.0-faq.it.po 26 Mar 2017 19:00:32 -0000
1.40
@@ -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"
"X-Generator: Poedit 1.5.4\n"
#. type: Content of: <title>
@@ -183,14 +182,7 @@
"\"TOCGPLRequireSourcePostedPublic\">La GPL richiede che il codice sorgente "
"delle versioni modificate di un programma sia reso pubblico?</a>"
-# | <a href=\"#GPLAndNonfreeOnSameMachine\"
-# | name=\"TOCGPLAndNonfreeOnSameMachine\"> Can I have a GPL-covered program
-# | and an unrelated non[---]free program on the same computer?</a>
-#. type: Content of: <ul><li>
-#| msgid ""
-#| "<a href=\"#GPLAndNonfreeOnSameMachine\" name="
-#| "\"TOCGPLAndNonfreeOnSameMachine\"> Can I have a GPL-covered program and "
-#| "an unrelated non-free program on the same computer?</a>"
+#. type: Content of: <ul><li>
msgid ""
"<a href=\"#GPLAndNonfreeOnSameMachine\" name=\"TOCGPLAndNonfreeOnSameMachine"
"\"> Can I have a GPL-covered program and an unrelated nonfree program on the "
@@ -442,14 +434,7 @@
"caso che la mia scuola avesse intenzione di fare di un mio programma un "
"suo software proprietario?</a>"
-# | <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>
-#. type: Content of: <ul><li>
-#| 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>"
+#. type: Content of: <ul><li>
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 "
@@ -502,12 +487,7 @@
"<a href=\"#WMS\" name=\"TOCWMS\">Qual è la licenza più opportuna per i "
"modelli da usare in sistemi di gestione dei siti web?</a>"
-# | <a href=\"#NonFreeTools\" name=\"TOCNonFreeTools\">Can I release a program
-# | under the GPL which I developed using non[---]free tools?</a>
#. type: Content of: <ul><li>
-#| 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>"
@@ -702,14 +682,7 @@
msgid "Using programs released under the GPL when writing other programs"
msgstr "Usare programma coperti da GPL quando si scrivono altri programmi"
-# | <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>
-#. type: Content of: <ul><li>
-#| 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>"
+#. type: Content of: <ul><li>
msgid ""
"<a href=\"#CanIUseGPLToolsForNF\" name=\"TOCCanIUseGPLToolsForNF\">Can I use "
"GPL-covered editors such as GNU Emacs to develop nonfree programs? Can I use "
@@ -868,14 +841,7 @@
"modulo ad un altro coperto dalla GPL, devo usare la GPL come licenza per "
"il mio modulo?</a>"
-# | <a [-href=\"#GPLPluginsInNF\" name=\"TOCGPLPluginsInNF\">Can I apply the
-# | GPL when writing-] {+href=\"#GPLPlugins\" name=\"TOCGPLPlugins\"> When
-# | are+} a [-plug-in for-] {+program and its plug-ins considered+} a
-# | [-non-free-] {+single combined+} program?</a>
-#. type: Content of: <ul><li>
-#| msgid ""
-#| "<a href=\"#GPLPluginsInNF\" name=\"TOCGPLPluginsInNF\">Can I apply the "
-#| "GPL when writing a plug-in for a non-free program?</a>"
+#. type: Content of: <ul><li>
msgid ""
"<a href=\"#GPLPlugins\" name=\"TOCGPLPlugins\"> When are a program and its "
"plug-ins considered a single combined program?</a>"
@@ -893,12 +859,7 @@
"rilasciato sotto la GPL fa uso di plug-in, quali sono i requisiti da "
"includere nelle licenze di questi plug-in?</a>"
-# | <a href=\"#GPLPluginsInNF\" name=\"TOCGPLPluginsInNF\">Can I apply the GPL
-# | when writing a plug-in for a non[---]free program?</a>
#. type: Content of: <ul><li>
-#| 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>"
@@ -906,12 +867,7 @@
"<a href=\"#GPLPluginsInNF\" name=\"TOCGPLPluginsInNF\">Posso usare la GPL "
"per un plug-in destinato ad un programma non libero?</a>"
-# | <a href=\"#NFUseGPLPlugins\" name=\"TOCNFUseGPLPlugins\">Can I release a
-# | non[---]free program that's designed to load a GPL-covered plug-in?</a>
#. type: Content of: <ul><li>
-#| 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>"
@@ -943,12 +899,7 @@
"wrapper”, con licenza permissiva compatibile con la GPL (come la "
"licenza di X11) tra la parte coperta da GPL e la parte proprietaria?</a>"
-# | <a href=\"#FSWithNFLibs\" name=\"TOCFSWithNFLibs\"> Can I write free
-# | software that uses non[---]free libraries?</a>
#. type: Content of: <ul><li>
-#| 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>"
@@ -1362,14 +1313,7 @@
"modificato, e solo a certe condizioni; ma la decisione riguardo a <em>se</"
"em> pubblicare o no il software rimane a chi ha effettuato le modifiche."
-# | <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>
-#. type: Content of: <dl><dt>
-#| 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>"
+#. type: Content of: <dl><dt>
msgid ""
"<b><a href=\"#TOCGPLAndNonfreeOnSameMachine\" name="
"\"GPLAndNonfreeOnSameMachine\"> Can I have a GPL-covered program and an "
@@ -1596,16 +1540,7 @@
"\"> La GPL mi permette di richiedere che tutti quelli che ricevono il "
"software debbano pagarmi una somma di denaro e/o farmelo sapere?</a></b>"
-# | 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>.
-#. type: Content of: <dl><dd>
-#| 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>."
+#. type: Content of: <dl><dd>
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 "
@@ -1961,12 +1896,7 @@
"sia rilasciato sotto la GNU GPL. L'altra licenza è compatibile con la GPL "
"se permette la stessa cosa."
-# | <b><a href=\"#TOCFSWithNFLibs\" name=\"FSWithNFLibs\">Can I write free
-# | software that uses non[---]free libraries?</a></b>
#. type: Content of: <dl><dt>
-#| 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>"
@@ -1974,18 +1904,7 @@
"<b><a href=\"#TOCFSWithNFLibs\" name=\"FSWithNFLibs\">Posso scrivere "
"programmi liberi che fanno uso di librerie non libere?</a></b>"
-# | 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.
-#. type: Content of: <dl><dd>
-#| 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."
+#. type: Content of: <dl><dd>
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 "
@@ -2010,24 +1929,7 @@
"un modo di realizzare il programma senza usare questa libreria? Ã possibile
"
"scrivere un'alternativa a questa libreria che sia libera?"
-# | 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.
-#. type: Content of: <dl><dd><p>
-#| 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."
+#. type: Content of: <dl><dd><p>
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 "
@@ -2047,16 +1949,7 @@
"la libreria in questione, e di suggerire questo come obiettivo primario per "
"chiunque intenda apportare modifiche sostanziali al programma."
-# | 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.
-#. type: Content of: <dl><dd><p>
-#| 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."
+#. type: Content of: <dl><dd><p>
msgid ""
"Note that there may also be legal issues with combining certain nonfree "
"libraries with GPL-covered Free Software. Please see <a href="
@@ -2246,14 +2139,7 @@
"eccezione, queste non sono obbligate ad autorizzare la stessa cosa per il "
"loro lavoro -- possono scegliere di farlo o di non farlo."
-# | 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>.
-#. type: Content of: <dl><dd><p>
-#| 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>."
+#. type: Content of: <dl><dd><p>
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 "
@@ -2432,14 +2318,7 @@
"ottenuto la copia in modo legittimo, è la licenza che si applica alla "
"suddetta copia."
-# | <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>
-#. type: Content of: <dl><dt>
-#| 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>"
+#. type: Content of: <dl><dt>
msgid ""
"<b><a href=\"#TOCReleaseUnderGPLAndNF\" name=\"ReleaseUnderGPLAndNF\">I "
"would like to release a program I wrote under the GNU GPL, but I would like "
@@ -2449,16 +2328,7 @@
"\">Vorrei rilasciare un programma che ho scritto sotto la GNU GPL, ma mi "
"piacerebbe anche usare lo stesso codice in programmi non liberi.</a></b>"
-# | 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.
-#. type: Content of: <dl><dd>
-#| 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."
+#. type: Content of: <dl><dd>
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 "
@@ -2521,14 +2391,7 @@
"No, perché gli utenti hanno già ricevuto il diritto di usare il
programma "
"sotto la GPL, e questo diritto non può essere ritirato."
-# | <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>
-#. type: Content of: <dl><dt>
-#| 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>"
+#. type: Content of: <dl><dt>
msgid ""
"<b><a href=\"#TOCCanIUseGPLToolsForNF\" name=\"CanIUseGPLToolsForNF\">Can I "
"use GPL-covered editors such as GNU Emacs to develop nonfree programs? Can I "
@@ -2566,18 +2429,7 @@
"la parte dell'output derivata dall'input del programma eredita lo stato di "
"copyright dell'input."
-# | 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.
-#. type: Content of: <dl><dd><p>
-#| 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."
+#. type: Content of: <dl><dd><p>
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 "
@@ -2991,14 +2843,7 @@
"La licenza BSD rivisitata non contiene questa clausola, il che elimina il "
"problema."
-# | <b><a [-href=\"#TOCGPLPluginsInNF\" name=\"GPLPluginsInNF\">Can I apply
-# | the GPL when writing-] {+href=\"#TOCGPLPlugins\" name=\"GPLPlugins\"> When
-# | are+} a [-plug-in for-] {+program and its plug-ins considered+} a
-# | [-non-free program?</a></b>-] {+single combined program? </a></b>+}
-#. type: Content of: <dl><dt>
-#| msgid ""
-#| "<b><a href=\"#TOCGPLPluginsInNF\" name=\"GPLPluginsInNF\">Can I apply the "
-#| "GPL when writing a plug-in for a non-free program?</a></b>"
+#. type: Content of: <dl><dt>
msgid ""
"<b><a href=\"#TOCGPLPlugins\" name=\"GPLPlugins\"> When are a program and "
"its plug-ins considered a single combined program? </a></b>"
@@ -3025,24 +2870,7 @@
"comunicazione profonda allora i plugin si possono considerare programmi "
"separati."
-# | 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. [-This means-] {+If+} the [-plug-ins
-# | must be released under-] {+main program dynamically links plug-ins, but+}
-# | the [-GPL or a GPL-compatible free software license, and that-]
-# | {+communication between them is limited to invoking+} the [-terms-]
-# | {+‘main’ function+} of the [-GPL must be followed when those
-# | plug-ins are distributed.-] {+plug-in with some options and waiting for it
-# | to return, that is a borderline case.+}
-#. type: Content of: <dl><dd><p>
-#| msgid ""
-#| "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."
+#. type: Content of: <dl><dd><p>
msgid ""
"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 "
@@ -3088,25 +2916,7 @@
"un programma principale sono da considerare programmi diversi e quando no</"
"a>."
-# | 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-]
-# | {+plugins are a single combined+} program {+then this means you+} must
-# | [-be released-] {+license the plug-in+} under the GPL or a GPL-compatible
-# | free software license[-,-] and [-that the terms of the GPL must be
-# | followed when the-] {+distribute it with source code in a GPL-compliant
-# | way. A+} main program {+that+} is [-distributed-] {+separate from its
-# | plug-ins makes no requirements+} for [-use with these-] {+the+} plug-ins.
-#. type: Content of: <dl><dd><p>
-#| msgid ""
-#| "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."
+#. type: Content of: <dl><dd><p>
msgid ""
"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 "
@@ -3120,12 +2930,7 @@
"le condizioni della GPL. Invece un programma principale separato dai plugin "
"non impone alcun requitio su questi ultimi."
-# | <b><a href=\"#TOCGPLPluginsInNF\" name=\"GPLPluginsInNF\">Can I apply the
-# | GPL when writing a plug-in for a non[---]free program?</a></b>
#. type: Content of: <dl><dt>
-#| 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>"
@@ -3143,23 +2948,7 @@
"un programma principale sono da considerare programmi diversi e quando no</"
"a>."
-# | 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-]
-# | {+combined+} program [-and the plug-ins. This-] {+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.
-#. type: Content of: <dl><dd><p>
-#| msgid ""
-#| "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."
+#. type: Content of: <dl><dd><p>
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. "
@@ -3173,12 +2962,7 @@
"licenza del plug-in, la quale permetta il collegamento col programma non "
"libero in questione."
-# | See also the question <a href=\"#FSWithNFLibs\">I am writing free software
-# | that uses a non[---]free library.</a>
#. type: Content of: <dl><dd><p>
-#| 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>"
@@ -3186,13 +2970,7 @@
"Vedere anche \"<a href=\"#FSWithNFLibs\">Posso scrivere programmi liberi "
"che fanno uso di librerie non libere?</a>\"."
-# | <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>
-#. type: Content of: <dl><dt>
-#| 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>"
+#. type: Content of: <dl><dt>
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>"
@@ -3201,23 +2979,7 @@
"un programma non libero che ha come scopo quello di caricare un plug-in "
"coperto da GPL?</a></b>"
-# | 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-]
-# | {+combined+} program [-and the plug-ins. In order to use the GPL-covered
-# | plug-ins,-] {+then+} 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.
-#. type: Content of: <dl><dd><p>
-#| msgid ""
-#| "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."
+#. type: Content of: <dl><dd><p>
msgid ""
"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 "
@@ -3229,16 +2991,7 @@
"si distribuisce il programma principale for l'uso con questo plugin si "
"devono rispettare le condizioni della GPL."
-# | [-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-]{+However, if they+}
-# | are separate [-programs, so-] {+works then+} the license of the plug-in
-# | makes no requirements about the main program.
-#. type: Content of: <dl><dd><p>
-#| msgid ""
-#| "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."
+#. type: Content of: <dl><dd><p>
msgid ""
"However, if they are separate works then the license of the plug-in makes no "
"requirements about the main program."
@@ -3702,18 +3455,7 @@
"\">Mi piacerebbe incorporare del software coperto dalla GPL nel mio "
"sistema proprietario. Lo posso fare?</a></b>"
-# | 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.
-#. type: Content of: <dl><dd>
-#| 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."
+#. type: Content of: <dl><dd>
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, "
@@ -3744,18 +3486,7 @@
"hanno diritto, e per incoraggiare le persone a redistribuire i "
"miglioramenti che dovessero apportare."
-# | 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.
-#. type: Content of: <dl><dd><p>
-#| 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."
+#. type: Content of: <dl><dd><p>
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 "
@@ -4886,12 +4617,7 @@
"to do so. If you do not wish to do so, delete this exception statement from "
"your version."
-# | <b><a href=\"#TOCNonFreeTools\" name=\"NonFreeTools\">Can I release a
-# | program under the GPL which I developed using non[---]free tools?</a></b>
#. type: Content of: <dl><dt>
-#| 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>"
@@ -4910,20 +4636,7 @@
"programmi si sono utilizzati per modificare, compilare, studiare o "
"registrare il codice stesso."
-# | 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.
-#. type: Content of: <dl><dd><p>
-#| 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."
+#. type: Content of: <dl><dd><p>
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 "
@@ -5232,22 +4945,7 @@
"programma su GNU/Linux, devo rilasciarlo come software libero coperto dalla "
"GPL o da qualche altra licenza libera?</a></b>"
-# | 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.
-#. type: Content of: <dl><dd>
-#| 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."
+#. type: Content of: <dl><dd>
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 "
Index: licenses/po/gpl-faq.it-en.html
===================================================================
RCS file: /web/www/www/licenses/po/gpl-faq.it-en.html,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -b -r1.7 -r1.8
--- licenses/po/gpl-faq.it-en.html 5 Mar 2017 14:29:33 -0000 1.7
+++ licenses/po/gpl-faq.it-en.html 26 Mar 2017 19:00:33 -0000 1.8
@@ -101,7 +101,7 @@
public?</a></li>
<li><a href="#GPLAndNonfreeOnSameMachine">Can I have a GPL-covered
- program and an unrelated non-free program on the same computer?</a></li>
+ program and an unrelated nonfree program on the same computer?</a></li>
<li><a href="#CanIDemandACopy">If I know someone has a copy of a
GPL-covered program, can I demand they give me a copy?</a></li>
@@ -304,7 +304,7 @@
<li><a href="#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></li>
+ code in nonfree programs.</a></li>
<li><a href="#CanDeveloperThirdParty">Can the developer of a program
who distributed it under the GPL later license it to another party
@@ -339,7 +339,7 @@
system templates?</a></li>
<li><a href="#NonFreeTools">Can I release a program under the GPL
- which I developed using non-free tools?</a></li>
+ which I developed using nonfree tools?</a></li>
<li><a href="#GiveUpKeys">I use public key cryptography to sign my
code to assure its authenticity. Is it true that GPLv3 forces me to
@@ -488,11 +488,11 @@
<ul>
<li><a href="#GPLAndNonfreeOnSameMachine">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="#CanIUseGPLToolsForNF">Can I use GPL-covered editors
- such as GNU Emacs to develop non-free programs? Can I use
+ such as GNU Emacs to develop nonfree programs? Can I use
GPL-covered tools such as GCC to compile them?</a></li>
<li><a href="#GPLOutput">Is there some way that I can GPL the output
@@ -587,14 +587,17 @@
program, do I have to use the GPL as the license for my
module?</a></li>
+ <li><a href="#GPLPlugins">When are a program and its plug-ins
+ considered a single combined program?</a></li>
+
<li><a href="#GPLAndPlugins">If I write a plug-in to use with
a GPL-covered program, what requirements does that impose
on the licenses I can use for distributing my plug-in?</a></li>
<li><a href="#GPLPluginsInNF">Can I apply the GPL when writing a
- plug-in for a non-free program?</a></li>
+ plug-in for a nonfree program?</a></li>
- <li><a href="#NFUseGPLPlugins">Can I release a non-free program
+ <li><a href="#NFUseGPLPlugins">Can I release a nonfree program
that's designed to load a GPL-covered plug-in?</a></li>
<li><a href="#GPLInProprietarySystem">I'd like to incorporate
@@ -609,7 +612,7 @@
and the proprietary part?</a></li>
<li><a href="#FSWithNFLibs">Can I write free software that uses
- non-free libraries?</a></li>
+ nonfree libraries?</a></li>
<li><a href="#SystemLibraryException">Can I link a GPL program with
a proprietary system library?</a></li>
@@ -830,7 +833,7 @@
<dt id="GPLAndNonfreeOnSameMachine">Can I have a GPL-covered
- program and an unrelated non-free program on the same computer?
+ program and an unrelated nonfree program on the same computer?
<span class="anchor-reference-id">(<a href="#GPLAndNonfreeOnSameMachine"
>#GPLAndNonfreeOnSameMachine</a>)</span></dt>
<dd><p>Yes.</p></dd>
@@ -949,7 +952,7 @@
<span class="anchor-reference-id">(<a href="#DoesTheGPLAllowRequireFee"
>#DoesTheGPLAllowRequireFee</a>)</span></dt>
<dd><p>
-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">
@@ -1199,29 +1202,29 @@
<dt id="FSWithNFLibs">Can I write
- free software that uses non-free libraries?
+ free software that uses nonfree libraries?
<span class="anchor-reference-id">(<a href="#FSWithNFLibs"
>#FSWithNFLibs</a>)</span></dt>
<dd><p>
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>
<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
+<p>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
+<p>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.</p></dd>
@@ -1267,9 +1270,9 @@
<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
+<p>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>.</p>
+nonfree libraries</a>.</p>
<p>If you're using GPLv3, you can accomplish this goal by granting an
additional permission under section 7. The following license notice will
@@ -1435,11 +1438,11 @@
<dt id="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.
+ like to use the same code in nonfree programs.
<span class="anchor-reference-id">(<a href="#ReleaseUnderGPLAndNF"
>#ReleaseUnderGPLAndNF</a>)</span></dt>
<dd><p>
-To release a non-free program is always ethically tainted, but
+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></dd>
@@ -1471,7 +1474,7 @@
<dt id="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?
<span class="anchor-reference-id">(<a href="#CanIUseGPLToolsForNF"
>#CanIUseGPLToolsForNF</a>)</span></dt>
@@ -1487,11 +1490,11 @@
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.
+<p>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.</p></dd>
+which already permitted use for nonfree programs.</p></dd>
<dt id="GPLFairUse">Do I have “fair use”
@@ -1751,82 +1754,87 @@
eliminates the problem.</p></dd>
+<dt id="GPLPlugins">When are a program and its plug-ins considered a single
combined program?
+ <span class="anchor-reference-id">(<a href="#GPLPlugins"
+ >#GPLPlugins</a>)</span></dt>
+<dd><p>
+ 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>
+
+<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 id="GPLAndPlugins">If I write a plug-in to use with a GPL-covered
program, what requirements does that impose on the licenses I can
use for distributing my plug-in?
<span class="anchor-reference-id">(<a href="#GPLAndPlugins"
>#GPLAndPlugins</a>)</span></dt>
<dd><p>
-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>
-
-<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 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.</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>
+
+<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 id="GPLPluginsInNF">Can I apply the
- GPL when writing a plug-in for a non-free program?
+ GPL when writing a plug-in for a nonfree program?
<span class="anchor-reference-id">(<a href="#GPLPluginsInNF"
>#GPLPluginsInNF</a>)</span></dt>
<dd><p>
-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>
-
-<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>
+ 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>
+<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 non-free library.</a></p></dd>
+writing free software that uses a nonfree library.</a></p></dd>
-<dt id="NFUseGPLPlugins">Can I release a non-free program
+<dt id="NFUseGPLPlugins">Can I release a nonfree program
that's designed to load a GPL-covered plug-in?
<span class="anchor-reference-id">(<a href="#NFUseGPLPlugins"
>#NFUseGPLPlugins</a>)</span></dt>
-<dd><p>
-It depends on how the program invokes its plug-ins. For instance, if
-the program uses <em>only</em> simple fork and exec to invoke and
-communicate with plug-ins, then the plug-ins are separate programs, so
-the license of the plug-in makes no requirements about the main
-program.</p>
-<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>
+<dd><p>
+ 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>
+<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>Using shared memory to communicate with complex data structures
-is pretty much equivalent to dynamic linking.</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 non-free library.</a></p></dd>
+writing free software that uses a nonfree library.</a></p></dd>
<dt id="LinkingWithGPL">You have a GPL'ed program that I'd like
@@ -1950,7 +1958,7 @@
An “aggregate” consists of a number of separate programs,
distributed together on the same CD-ROM or other media. The GPL permits
you to create and distribute an aggregate, even when the licenses of the
-other software are non-free or GPL-incompatible. The only condition is
+other software are nonfree or GPL-incompatible. The only condition is
that you cannot release the aggregate under a license that prohibits users
from exercising rights that each program's individual license would
grant them.</p>
@@ -2102,8 +2110,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.</p>
+incorporate GPL-covered software into a nonfree system, it would have
+the effect of making the GPL-covered software nonfree too.</p>
<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
@@ -2114,7 +2122,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>
@@ -2666,7 +2674,7 @@
<dt id="NonFreeTools">Can I release
- a program under the GPL which I developed using non-free tools?
+ a program under the GPL which I developed using nonfree tools?
<span class="anchor-reference-id">(<a href="#NonFreeTools"
>#NonFreeTools</a>)</span></dt>
<dd><p>
@@ -2674,7 +2682,7 @@
study it, or record it, usually makes no difference for issues
concerning the licensing of that source code.</p>
-<p>However, if you link non-free libraries with the source code, that
+<p>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
@@ -2829,7 +2837,7 @@
their licenses are. Most system libraries either use the <a
href="/licenses/lgpl.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
+can be used in nonfree programs; but in the case of the Lesser GPL, it
does have some requirements you must follow.</p>
<p>Some libraries are released under the GNU GPL alone; you must use a
@@ -3888,7 +3896,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2017/03/05 14:29:33 $
+$Date: 2017/03/26 19:00:33 $
<!-- timestamp end -->
</p>
</div>
Index: licenses/po/gpl-violation.it-en.html
===================================================================
RCS file: /web/www/www/licenses/po/gpl-violation.it-en.html,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
--- licenses/po/gpl-violation.it-en.html 26 Jun 2014 20:28:32 -0000
1.10
+++ licenses/po/gpl-violation.it-en.html 26 Mar 2017 19:00:33 -0000
1.11
@@ -72,9 +72,14 @@
href="mailto:address@hidden";><address@hidden></a>.
It's important that we be able to write back to you to get more
information about the violation or product. So, if you use an
-anonymous remailer, please provide a return path of some sort. If you'd
-like to encrypt your correspondence, just send a brief mail saying so, and
-we'll make appropriate arrangements.</p>
+anonymous remailer, please provide a return path of some sort. If
+you'd like to encrypt your correspondence, just send a brief mail
+saying so, and we'll make appropriate arrangements. Because the FSF
+endorsed <a
+href="https://www.fsf.org/licensing/enforcement-principles";>the
+Principles of Community-Oriented GPL Enforcement</a>, you can rest
+assured that your report will help to educate the violator rather than
+punish them for their mistake.</p>
<p>
Note that the GPL, and other copyleft licenses, are copyright licenses.
@@ -120,7 +125,7 @@
<!-- Regarding copyright, in general, standalone pages (as opposed to
files generated as part of manuals) on the GNU web server should
- be under CC BY-ND 3.0 US. Please do NOT change or remove this
+ be under CC BY-ND 4.0. 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
@@ -135,18 +140,18 @@
There is more detail about copyright years in the GNU Maintainers
Information document, www.gnu.org/prep/maintain. -->
-<p>Copyright © 1999, 2001, 2007, 2008, 2013, 2014
+<p>Copyright © 1999, 2001, 2007, 2008, 2013, 2014, 2017
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
-Commons Attribution-NoDerivs 3.0 United States License</a>.</p>
+href="http://creativecommons.org/licenses/by-nd/4.0/";>Creative
+Commons Attribution-NoDerivatives 4.0 International License</a>.</p>
<!--#include virtual="/server/bottom-notes.html" -->
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2014/06/26 20:28:32 $
+$Date: 2017/03/26 19:00:33 $
<!-- timestamp end -->
</p>
</div>
Index: licenses/po/gpl-violation.it.po
===================================================================
RCS file: /web/www/www/licenses/po/gpl-violation.it.po,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -b -r1.12 -r1.13
--- licenses/po/gpl-violation.it.po 26 Mar 2017 13:57:51 -0000 1.12
+++ licenses/po/gpl-violation.it.po 26 Mar 2017 19:00:33 -0000 1.13
@@ -17,7 +17,6 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-"X-Outdated-Since: 2017-03-02 20:25+0000\n"
"X-Generator: Poedit 1.5.4\n"
#. type: Content of: <title>
@@ -156,27 +155,7 @@
"impropriamente. à il titolare del copyright colui il quale ha l'autorità "
"legale per intentare una causa per validare e rafforzarela licenza."
-# | If the copyright holder <strong>is</strong> the Free Software Foundation,
-# | please send the report to <a
-# | href=\"mailto:address@hidden";><address@hidden></a>.
-# | It's important that we be able to write back to you to get more
-# | information about the violation or product. So, if you use an anonymous
-# | remailer, please provide a return path of some sort. If you'd like to
-# | encrypt your correspondence, just send a brief mail saying so, and we'll
-# | make appropriate arrangements. {+Because the FSF endorsed <a
-# | href=\"https://www.fsf.org/licensing/enforcement-principles\";>the
-# | Principles of Community-Oriented GPL Enforcement</a>, you can rest assured
-# | that your report will help to educate the violator rather than punish them
-# | for their mistake.+}
#. type: Content of: <p>
-#| msgid ""
-#| "If the copyright holder <strong>is</strong> the Free Software Foundation, "
-#| "please send the report to <a href=\"mailto:address@hidden";
-#| "\"><address@hidden></a>. It's important that we be able "
-#| "to write back to you to get more information about the violation or "
-#| "product. So, if you use an anonymous remailer, please provide a return "
-#| "path of some sort. If you'd like to encrypt your correspondence, just "
-#| "send a brief mail saying so, and we'll make appropriate arrangements."
msgid ""
"If the copyright holder <strong>is</strong> the Free Software Foundation, "
"please send the report to <a href=\"mailto:address@hidden";><"
@@ -275,12 +254,7 @@
"<a href=\"/server/standards/README.translations.html\">Guida alle "
"traduzioni</a>."
-# | Copyright © 1999, 2001, 2007, 2008, 2013, [-2014-] {+2014, 2017+}
-# | Free Software Foundation, Inc.
#. type: Content of: <div><p>
-#| msgid ""
-#| "Copyright © 1999, 2001, 2007, 2008, 2013, 2014 Free Software "
-#| "Foundation, Inc."
msgid ""
"Copyright © 1999, 2001, 2007, 2008, 2013, 2014, 2017 Free Software "
"Foundation, Inc."
@@ -288,12 +262,7 @@
"Copyright © 1999, 2001, 2007, 2008, 2013, 2014, 2017 Free Software "
"Foundation, Inc."
-# || No change detected. The change might only be in amounts of spaces.
#. type: Content of: <div><p>
-#| msgid ""
-#| "This page is licensed under a <a rel=\"license\" href=\"http://";
-#| "creativecommons.org/licenses/by-nd/4.0/\">Creative Commons Attribution-"
-#| "NoDerivatives 4.0 International License</a>."
msgid ""
"This page is licensed under a <a rel=\"license\" href=\"http://";
"creativecommons.org/licenses/by-nd/4.0/\">Creative Commons Attribution-"
Index: licenses/po/license-list.it-en.html
===================================================================
RCS file: /web/www/www/licenses/po/license-list.it-en.html,v
retrieving revision 1.84
retrieving revision 1.85
diff -u -b -r1.84 -r1.85
--- licenses/po/license-list.it-en.html 18 Nov 2016 07:32:40 -0000 1.84
+++ licenses/po/license-list.it-en.html 26 Mar 2017 19:00:33 -0000 1.85
@@ -522,7 +522,7 @@
(<a href="#Eiffel">#Eiffel</a>)</span></dt>
<dd>
<p>This is a free software license, compatible with the GNU GPL. <a
-href="http://www.eiffel-nice.org/license/forum.txt";>Previous
+href="https://opensource.org/licenses/ver1_eiffel";>Previous
releases</a> of the Eiffel license are not compatible with the
GPL.</p></dd>
@@ -2079,7 +2079,7 @@
<dt><a id="Sybase"></a>
- <a id="Watcom"
href="http://www.openwatcom.org/index.php/Open_Watcom_Public_License";>
+ <a id="Watcom" href="ftp://ftp.openwatcom.org/install/license.txt";>
Sybase Open Watcom Public License version 1.0</a>
<span class="anchor-reference-id">
(<a href="#Watcom">#Watcom</a>)</span></dt>
@@ -2663,7 +2663,7 @@
information on coordinating and submitting translations of this article.</p>
</div>
-<p>Copyright © 2014, 2015, 2016 Free Software Foundation, Inc.</p>
+<p>Copyright © 2014, 2015, 2016, 2017 Free Software Foundation, Inc.</p>
<p>This page is licensed under a <a rel="license"
href="http://creativecommons.org/licenses/by-nd/4.0/";>Creative
@@ -2673,7 +2673,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2016/11/18 07:32:40 $
+$Date: 2017/03/26 19:00:33 $
<!-- timestamp end -->
</p>
</div>
Index: licenses/po/license-list.it.po
===================================================================
RCS file: /web/www/www/licenses/po/license-list.it.po,v
retrieving revision 1.275
retrieving revision 1.276
diff -u -b -r1.275 -r1.276
--- licenses/po/license-list.it.po 26 Mar 2017 13:57:51 -0000 1.275
+++ licenses/po/license-list.it.po 26 Mar 2017 19:00:33 -0000 1.276
@@ -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-05 20:55+0000\n"
"X-Generator: Poedit 1.5.4\n"
# type: Content of: <title>
@@ -952,15 +951,7 @@
"(<a href=\"#Eiffel\">#Eiffel</a>)</span>"
# type: Content of: <dl><dd><p>
-# | This is a free software license, compatible with the GNU GPL. <a
-# | [-href=\"http://www.eiffel-nice.org/license/forum.txt\";>Previous-]
-# | {+href=\"https://opensource.org/licenses/ver1_eiffel\";>Previous+}
-# | releases</a> of the Eiffel license are not compatible with the GPL.
-#. type: Content of: <dl><dd><p>
-#| msgid ""
-#| "This is a free software license, compatible with the GNU GPL. <a href="
-#| "\"http://www.eiffel-nice.org/license/forum.txt\";>Previous releases</a> of "
-#| "the Eiffel license are not compatible with the GPL."
+#. type: Content of: <dl><dd><p>
msgid ""
"This is a free software license, compatible with the GNU GPL. <a href="
"\"https://opensource.org/licenses/ver1_eiffel\";>Previous releases</a> of the "
@@ -1134,8 +1125,8 @@
"href=\"#ijg\">#ijg</a>)</span>"
msgstr ""
"<a id=\"ijg\" href=\"http://directory.fsf.org/wiki?title=License:JPEG\";> "
-"Licenza di Independent JPEG Group</a> <span class=\"anchor-reference-id"
-"\">(<a href=\"#ijg\">#ijg</a>)</span>"
+"Licenza di Independent JPEG Group</a> <span class=\"anchor-reference-id\">"
+"(<a href=\"#ijg\">#ijg</a>)</span>"
# type: Content of: <dl><dd><p>
#. type: Content of: <dl><dd><p>
@@ -1151,8 +1142,8 @@
#. type: Content of: <dl><dt>
msgid ""
-"<a id=\"informal\"> Informal license</a> <span class=\"anchor-reference-id"
-"\">(<a href=\"#informal\">#informal</a>)</span>"
+"<a id=\"informal\"> Informal license</a> <span class=\"anchor-reference-id\">"
+"(<a href=\"#informal\">#informal</a>)</span>"
msgstr ""
"<a id=\"informal\"> Licenza informale</a> <span class=\"anchor-reference-id"
"\">(<a href=\"#informal\">#informal</a>)</span>"
@@ -1581,8 +1572,8 @@
#. type: Content of: <dl><dt>
msgid ""
"<a id=\"Ruby\" href=\"http://directory.fsf.org/wiki/License:Ruby\";> License "
-"of Ruby</a> <span class=\"anchor-reference-id\">(<a href=\"#Ruby\">#Ruby</"
-"a>)</span>"
+"of Ruby</a> <span class=\"anchor-reference-id\">(<a href=\"#Ruby\">#Ruby</a>)"
+"</span>"
msgstr ""
"<a id=\"Ruby\" href=\"http://directory.fsf.org/wiki/License:Ruby\";> La "
"licenza di Ruby</a> <span class=\"anchor-reference-id\">(<a href=\"#Ruby"
@@ -1792,8 +1783,8 @@
"href=\"#Vim\">#Vim</a>)</span>"
msgstr ""
"<a id=\"Vim\" href=\"http://directory.fsf.org/wiki/License:Vim7.2\";> Licenza "
-"di Vim, versione 6.1 o successiva</a> <span class=\"anchor-reference-id"
-"\">(<a href=\"#Vim\">#Vim</a>)</span>"
+"di Vim, versione 6.1 o successiva</a> <span class=\"anchor-reference-id\">"
+"(<a href=\"#Vim\">#Vim</a>)</span>"
# type: Content of: <dl><dd><p>
#. type: Content of: <dl><dd><p>
@@ -1820,12 +1811,12 @@
#. type: Content of: <dl><dt>
msgid ""
"<a id=\"WebM\" href=\"http://directory.fsf.org/wiki/License:WebM\";> License "
-"of WebM</a> <span class=\"anchor-reference-id\">(<a href=\"#WebM\">#WebM</"
-"a>)</span>"
+"of WebM</a> <span class=\"anchor-reference-id\">(<a href=\"#WebM\">#WebM</a>)"
+"</span>"
msgstr ""
"<a id=\"WebM\" href=\"http://directory.fsf.org/wiki/License:WebM\";> Licenza "
-"di WebM</a> <span class=\"anchor-reference-id\">(<a href=\"#WebM\">#WebM</"
-"a>)</span>"
+"di WebM</a> <span class=\"anchor-reference-id\">(<a href=\"#WebM\">#WebM</a>)"
+"</span>"
#. type: Content of: <dl><dd><p>
msgid ""
@@ -1886,8 +1877,8 @@
"<a id=\"Wx\"></a>WxWidgets License <span class=\"anchor-reference-id\">(<a "
"href=\"#Wx\">#Wx</a>)</span>"
msgstr ""
-"<a id=\"Wx\"></a>La licenza di WxWidgets <span class=\"anchor-reference-id"
-"\">(<a href=\"#Wx\">#Wx</a>)</span>"
+"<a id=\"Wx\"></a>La licenza di WxWidgets <span class=\"anchor-reference-id\">"
+"(<a href=\"#Wx\">#Wx</a>)</span>"
#. type: Content of: <dl><dd><p>
msgid ""
@@ -2000,12 +1991,12 @@
#. type: Content of: <dl><dt>
msgid ""
"<a id=\"ZLib\" href=\"http://directory.fsf.org/wiki/License:Zlib\";> License "
-"of ZLib</a> <span class=\"anchor-reference-id\">(<a href=\"#ZLib\">#ZLib</"
-"a>)</span>"
+"of ZLib</a> <span class=\"anchor-reference-id\">(<a href=\"#ZLib\">#ZLib</a>)"
+"</span>"
msgstr ""
"<a id=\"ZLib\" href=\"http://directory.fsf.org/wiki/License:Zlib\";> Licenza "
-"di ZLib</a> <span class=\"anchor-reference-id\">(<a href=\"#ZLib\">#ZLib</"
-"a>)</span>"
+"di ZLib</a> <span class=\"anchor-reference-id\">(<a href=\"#ZLib\">#ZLib</a>)"
+"</span>"
# type: Content of: <dl><dd><p>
#. type: Content of: <dl><dd><p>
@@ -2413,8 +2404,8 @@
#. type: Content of: <dl><dt>
msgid ""
"<a id=\"EPL\" href=\"http://directory.fsf.org/wiki/License:EPLv1.0\";> "
-"Eclipse Public License Version 1.0</a> <span class=\"anchor-reference-id"
-"\">(<a href=\"#EPL\">#EPL</a>)</span>"
+"Eclipse Public License Version 1.0</a> <span class=\"anchor-reference-id\">"
+"(<a href=\"#EPL\">#EPL</a>)</span>"
msgstr ""
"<a id=\"EPL\" href=\"http://directory.fsf.org/wiki/License:EPLv1.0\";> "
"Licenza pubblica Eclipse, versione 1.0</a> <span class=\"anchor-reference-id"
@@ -2708,13 +2699,13 @@
msgid ""
"<a id=\"lucent102\" href=\"http://directory.fsf.org/wiki/License:";
"LucentPLv1.02\"> Lucent Public License Version 1.02 (Plan 9 license)</a> "
-"<span class=\"anchor-reference-id\"> (<a href=\"#lucent102\">#lucent102</"
-"a>)</span>"
+"<span class=\"anchor-reference-id\"> (<a href=\"#lucent102\">#lucent102</a>)"
+"</span>"
msgstr ""
"<a id=\"lucent102\" href=\"http://directory.fsf.org/wiki/License:";
"LucentPLv1.02\"> Lucent Public License Version 1.02 (Plan 9 license)</a> "
-"<span class=\"anchor-reference-id\"> (<a href=\"#lucent102\">#lucent102</"
-"a>)</span>"
+"<span class=\"anchor-reference-id\"> (<a href=\"#lucent102\">#lucent102</a>)"
+"</span>"
# type: Content of: <dl><dd><p>
#. type: Content of: <dl><dd><p>
@@ -2755,12 +2746,12 @@
#. type: Content of: <dl><dt>
msgid ""
"<a id=\"ms-rl\" href=\"http://directory.fsf.org/wiki/License:MsRL\";> "
-"Microsoft Reciprocal License (Ms-RL)</a> <span class=\"anchor-reference-id"
-"\">(<a href=\"#ms-rl\">#ms-rl</a>)</span>"
+"Microsoft Reciprocal License (Ms-RL)</a> <span class=\"anchor-reference-id\">"
+"(<a href=\"#ms-rl\">#ms-rl</a>)</span>"
msgstr ""
"<a id=\"ms-rl\" href=\"http://directory.fsf.org/wiki/License:MsRL\";> "
-"Microsoft Reciprocal License (Ms-RL)</a> <span class=\"anchor-reference-id"
-"\">(<a href=\"#ms-rl\">#ms-rl</a>)</span>"
+"Microsoft Reciprocal License (Ms-RL)</a> <span class=\"anchor-reference-id\">"
+"(<a href=\"#ms-rl\">#ms-rl</a>)</span>"
# type: Content of: <dl><dd><p>
#. type: Content of: <dl><dd><p>
@@ -3109,12 +3100,12 @@
#. type: Content of: <dl><dt>
msgid ""
"<a id=\"QPL\" href=\"http://directory.fsf.org/wiki/License:QPLv1.0\";> Q "
-"Public License (QPL), Version 1.0</a> <span class=\"anchor-reference-id"
-"\">(<a href=\"#QPL\">#QPL</a>)</span>"
+"Public License (QPL), Version 1.0</a> <span class=\"anchor-reference-id\">"
+"(<a href=\"#QPL\">#QPL</a>)</span>"
msgstr ""
"<a id=\"QPL\" href=\"http://directory.fsf.org/wiki/License:QPLv1.0\";> Q "
-"Public License (QPL), versione 1.0</a> <span class=\"anchor-reference-id"
-"\">(<a href=\"#QPL\">#QPL</a>)</span>"
+"Public License (QPL), versione 1.0</a> <span class=\"anchor-reference-id\">"
+"(<a href=\"#QPL\">#QPL</a>)</span>"
# type: Content of: <dl><dd><p>
#. type: Content of: <dl><dd><p>
@@ -3882,12 +3873,12 @@
#. type: Content of: <dl><dt>
msgid ""
"<a id=\"JSON\" href=\"http://directory.fsf.org/wiki/License:JSON\";> The JSON "
-"License</a> <span class=\"anchor-reference-id\">(<a href=\"#JSON\">#JSON</"
-"a>)</span>"
+"License</a> <span class=\"anchor-reference-id\">(<a href=\"#JSON\">#JSON</a>)"
+"</span>"
msgstr ""
"<a id=\"JSON\" href=\"http://directory.fsf.org/wiki/License:JSON\";> Licenza "
-"di JSON</a> <span class=\"anchor-reference-id\">(<a href=\"#JSON\">#JSON</"
-"a>)</span>"
+"di JSON</a> <span class=\"anchor-reference-id\">(<a href=\"#JSON\">#JSON</a>)"
+"</span>"
#. type: Content of: <dl><dd><p>
msgid ""
@@ -3908,8 +3899,8 @@
#. type: Content of: <dl><dt>
msgid ""
-"<a id=\"ksh93\">Old license of ksh93</a> <span class=\"anchor-reference-id"
-"\">(<a href=\"#ksh93\">#ksh93</a>)</span>"
+"<a id=\"ksh93\">Old license of ksh93</a> <span class=\"anchor-reference-id\">"
+"(<a href=\"#ksh93\">#ksh93</a>)</span>"
msgstr ""
"<a id=\"ksh93\">Vecchia licenza di ksh93</a> <span class=\"anchor-reference-"
"id\">(<a href=\"#ksh93\">#ksh93</a>)</span>"
@@ -4127,12 +4118,12 @@
#. type: Content of: <dl><dt>
msgid ""
"<a id=\"PINE\" href=\"http://directory.fsf.org/wiki/License:PINE\";>License "
-"of PINE</a> <span class=\"anchor-reference-id\">(<a href=\"#PINE\">#PINE</"
-"a>)</span>"
+"of PINE</a> <span class=\"anchor-reference-id\">(<a href=\"#PINE\">#PINE</a>)"
+"</span>"
msgstr ""
"<a id=\"PINE\" href=\"http://directory.fsf.org/wiki/License:PINE\";>Licenza "
-"di PINE</a> <span class=\"anchor-reference-id\">(<a href=\"#PINE\">#PINE</"
-"a>)</span>"
+"di PINE</a> <span class=\"anchor-reference-id\">(<a href=\"#PINE\">#PINE</a>)"
+"</span>"
# type: Content of: <dl><dd><p>
#. type: Content of: <dl><dd><p>
@@ -4157,8 +4148,8 @@
#. type: Content of: <dl><dt>
msgid ""
-"<a id=\"Plan9\">Old Plan 9 license</a> <span class=\"anchor-reference-id"
-"\">(<a href=\"#Plan9\">#Plan9</a>)</span>"
+"<a id=\"Plan9\">Old Plan 9 license</a> <span class=\"anchor-reference-id\">"
+"(<a href=\"#Plan9\">#Plan9</a>)</span>"
msgstr ""
"<a id=\"Plan9\">Vecchia licenza di Plan 9</a> <span class=\"anchor-reference-"
"id\">(<a href=\"#Plan9\">#Plan9</a>)</span>"
@@ -4401,17 +4392,7 @@
"revocata. "
# type: Content of: <dl><dt>
-# | <a id=\"Sybase\"></a> <a id=\"Watcom\"
-# |
[-href=\"http://www.openwatcom.org/index.php/Open_Watcom_Public_License\";>-]
-# | {+href=\"ftp://ftp.openwatcom.org/install/license.txt\";>+} Sybase Open
-# | Watcom Public License version 1.0</a> <span class=\"anchor-reference-id\">
-# | (<a href=\"#Watcom\">#Watcom</a>)</span>
-#. type: Content of: <dl><dt>
-#| msgid ""
-#| "<a id=\"Sybase\"></a> <a id=\"Watcom\" href=\"http://www.openwatcom.org/";
-#| "index.php/Open_Watcom_Public_License\"> Sybase Open Watcom Public License "
-#| "version 1.0</a> <span class=\"anchor-reference-id\"> (<a href=\"#Watcom"
-#| "\">#Watcom</a>)</span>"
+#. type: Content of: <dl><dt>
msgid ""
"<a id=\"Sybase\"></a> <a id=\"Watcom\" href=\"ftp://ftp.openwatcom.org/";
"install/license.txt\"> Sybase Open Watcom Public License version 1.0</a> "
@@ -4572,8 +4553,8 @@
"<a id=\"YaST\"> YaST License</a> <span class=\"anchor-reference-id\">(<a "
"href=\"#YaST\">#YaST</a>)</span>"
msgstr ""
-"<a id=\"YaST\"> La Licenza di YaST</a> <span class=\"anchor-reference-id"
-"\">(<a href=\"#YaST\">#YaST</a>)</span>"
+"<a id=\"YaST\"> La Licenza di YaST</a> <span class=\"anchor-reference-id\">"
+"(<a href=\"#YaST\">#YaST</a>)</span>"
# type: Content of: <dl><dd><p>
#. type: Content of: <dl><dd><p>
@@ -4892,8 +4873,8 @@
#. type: Content of: <dl><dt>
msgid ""
"<a id=\"CC-BY-ND\" href=\"?\">Creative Commons Noderivatives, any version</"
-"a> <span class=\"anchor-reference-id\"> (<a href=\"#CC-BY-ND\">#CC-BY-ND</"
-"a>)</span>"
+"a> <span class=\"anchor-reference-id\"> (<a href=\"#CC-BY-ND\">#CC-BY-ND</a>)"
+"</span>"
msgstr ""
"<a id=\"CC-BY-ND\" href=\"?\">Creative Commons Noderivatives, qualsiasi "
"versione</a> <span class=\"anchor-reference-id\"> (<a href=\"#CC-BY-ND\">#CC-"
@@ -4931,8 +4912,8 @@
#. type: Content of: <dl><dt>
msgid ""
"<a id=\"GPLOther\" href=\"/licenses/gpl.html\"> GNU General Public License</"
-"a> <span class=\"anchor-reference-id\"> (<a href=\"#GPLOther\">#GPLOther</"
-"a>)</span>"
+"a> <span class=\"anchor-reference-id\"> (<a href=\"#GPLOther\">#GPLOther</a>)"
+"</span>"
msgstr ""
"<a id=\"GPLOther\" href=\"/licenses/gpl.html\"> La Licenza Pubblica Generica "
"GNU (GNU General Public License, GNU GPL)</a> <span class=\"anchor-reference-"
@@ -5215,8 +5196,8 @@
#. type: Content of: <dl><dt>
msgid ""
"<a id=\"GPLFonts\" href=\"/licenses/gpl.html\"> GNU General Public License</"
-"a> <span class=\"anchor-reference-id\"> (<a href=\"#GPLFonts\">#GPLFonts</"
-"a>)</span>"
+"a> <span class=\"anchor-reference-id\"> (<a href=\"#GPLFonts\">#GPLFonts</a>)"
+"</span>"
msgstr ""
"<a id=\"GPLFonts\" href=\"/licenses/gpl.html\"> La Licenza Pubblica Generica "
"GNU (GNU General Public License, GNU GPL)</a> <span class=\"anchor-reference-"
@@ -5265,8 +5246,8 @@
#. type: Content of: <dl><dt>
msgid ""
"<a id=\"ecfonts\" href=\"http://directory.fsf.org/wiki/License:LaTeX_ecfonts";
-"\">License of the ec fonts for LaTeX</a> <span class=\"anchor-reference-id"
-"\">(<a href=\"#ecfonts\">#ecfonts</a>)</span>"
+"\">License of the ec fonts for LaTeX</a> <span class=\"anchor-reference-id\">"
+"(<a href=\"#ecfonts\">#ecfonts</a>)</span>"
msgstr ""
"<a id=\"ecfonts\" href=\"http://directory.fsf.org/wiki/License:LaTeX_ecfonts";
"\">Licenza dei font ec per LaTeX</a> <span class=\"anchor-reference-id\">(<a "
@@ -5549,10 +5530,7 @@
"<a href=\"/server/standards/README.translations.html\">Guida alle "
"traduzioni</a>."
-# || No change detected. The change might only be in amounts of spaces.
#. type: Content of: <div><p>
-#| msgid ""
-#| "Copyright © 2014, 2015, 2016, 2017 Free Software Foundation, Inc."
msgid "Copyright © 2014, 2015, 2016, 2017 Free Software Foundation, Inc."
msgstr "Copyright © 2014, 2015, 2016, 2017 Free Software Foundation, Inc."
Index: philosophy/javascript-trap.it.html
===================================================================
RCS file: /web/www/www/philosophy/javascript-trap.it.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -b -r1.6 -r1.7
--- philosophy/javascript-trap.it.html 18 Nov 2016 07:32:45 -0000 1.6
+++ philosophy/javascript-trap.it.html 26 Mar 2017 19:00:33 -0000 1.7
@@ -15,24 +15,31 @@
<p><strong>Forse ogni giorno eseguite software non libero senza rendervene
conto, attraverso il vostro web browser.</strong></p>
+<!-- any links that used to point to the appendices should point to
+ free-your-javascript.html instead. -->
+<blockquote>
+<p>Per i webmaster: ci sono <a
+href="/software/librejs/free-your-javascript.html">molti modi</a> di
+indicare la licenza dei programmi JavaScript in un sito.</p>
+</blockquote>
+
<p>Nella comunità del software libero, l'idea che i programmi non liberi
-maltrattino i propri utenti è familiare. Alcuni di noi si rifiutano
-categoricamente di installare software proprietario e molti altri
-considerano la non-libertà un punto negativo per il programma. Molti utenti
-sono a conoscenza del fatto che questo problema si applica ai plug-in che i
-browser offrono di installare, visto che possono essere sia liberi che non
-liberi.</p>
-
-<p>Ma i browser eseguono altri programmi non liberi per i quali non vi chiedono
-il permesso o vi avvisano: i programmi che le pagine web contengono o
-includono da altri siti. Questi programmi sono spesso scritti in JavaScript,
-anche se alle volte sono scritti in altri linguaggi.</p>
+maltrattino i propri utenti è familiare. Alcuni di noi difendono la libertÃ
+rifiutandosi categoricamente di installare software proprietario; molti
+altri considerano la non-libertà un punto negativo per il programma.</p>
+
+<p>Molti utenti sono a conoscenza del fatto che questo problema si applica ai
+plug-in che i browser offrono di installare, visto che possono essere sia
+liberi che non liberi. Ma i browser eseguono altri programmi non liberi per
+i quali non vi chiedono il permesso o vi avvisano: i programmi che le pagine
+web contengono o includono da altri siti. Questi programmi sono spesso
+scritti in JavaScript, anche se alle volte sono scritti in altri linguaggi.</p>
<p>JavaScript (ufficialmente ma raramente chiamato ECMAScript) era usato un
tempo per vari fronzoli non essenziali nelle pagine web come effetti visuali
di navigazione. Era quindi accettabile considerare questi come una mera
-estensione del linguaggio HTML più che come software vero e proprio; il loro
-uso non costituiva un problema significante.</p>
+estensione del linguaggio HTML più che come software vero e proprio, e così
+ignorare il problema.</p>
<p>Molti siti continuano ad usare JavaScript in quella maniera, mentre altri lo
usano per grandi programmi che svolgono grandi operazioni. Per esempio,
@@ -183,85 +190,21 @@
di non esitare ad abilitare JavaScript temporaneamente per questo
scopo—non dimenticate di disattivarlo una volta finito.</p>
+<!-- any links that used to point to the appendices should point to
+ free-your-javascript.html instead. -->
+<blockquote>
+<p>Per i webmaster: ci sono <a
+href="/software/librejs/free-your-javascript.html">molti modi</a> di
+indicare la licenza dei programmi JavaScript in un sito.</p>
+</blockquote>
+
<p><strong>Grazie a <a href="/people/people.html#mattlee">Matt Lee</a> e <a
href="http://ejohn.org";>John Resig</a> per il loro aiuto nel definire il
criterio da noi proposto ed a David Parunakian per avermi messo a conoscenza
del problema.</strong></p>
-<h3 id="AppendixA">Appendice A: una convenzione per il rilascio di programmi
JavaScript liberi</h3>
-
-<p>Per riferimenti al codice sorgente corrispondente, raccomandiamo</p>
-<pre dir="ltr">
-
- // @source:
-
-</pre>
-
-<p>seguito dall'indirizzo web. Questo soddisfa il requisito della GNU GPL di
-distribuire il codice sorgente. Se il codice è su un sito esterno, dovete <a
-href="/licenses/gpl-faq.it.html#TOCSourceAndBinaryOnDifferentSites">agire di
-conseguenza</a>. Il codice sorgente è necessario perché un programma sia
-libero.
-</p>
-
-<p>Per indicare la licenza del codice JavaScript contenuto in una pagina,
-raccomandiamo di inserire l'avviso di licenza tra due note di questo tipo: </p>
-<pre dir="ltr">
-<!--TRANSLATORS: Do not translate these license notices. The <pre>
-
- elements have dir="ltr" explicitly set to cater for RTL languages.-->
-
- @licstart The following is the entire license notice for the
- JavaScript code in this page.
- ...
- @licend The above is the entire license notice
- for the JavaScript code in this page.
-
-</pre>
-<p>Questo testo dovrebbe essere contenuto in un commento multi-linea.</p>
-
-<p>La <a href="/licenses/gpl.html">GNU GPL</a>, come altre licenze libere,
-richiede la distribuzione di una copia della licenza con sia il codice
-sorgente che con i file binari del programma. Ma essendo la GNU GPL troppo
-lunga per essere inclusa senza impaccio in un programma JavaScript, potrete
-fare a meno di includerla per intero tramite l'uso di un avviso di licenza
-come questo:</p>
-<pre dir="ltr">
-
- Copyright (C) YYYY Developer
-
- The JavaScript code in this page is free software: you can
- redistribute it and/or modify it under the terms of the GNU
- General Public License (GNU GPL) as published by the Free Software
- Foundation, either version 3 of the License, or (at your option)
- any later version. The code is distributed WITHOUT ANY WARRANTY;
- without even the implied warranty of MERCHANTABILITY or FITNESS
- FOR A PARTICULAR PURPOSE. See the GNU GPL for more details.
-
- As additional permission under GNU GPL version 3 section 7, you
- may distribute non-source (e.g., minimized or compacted) forms of
- that code without the copy of the GNU GPL normally required by
- section 4, provided you include this license notice and a URL
- through which recipients can access the Corresponding Source.
-
-</pre>
-
<p>Ringrazio Jaffar Rumith per avere portato la questione alla mia
attenzione.</p>
-<h3 id="AppendixB">Appendice B: Pubblicare programmi Javascript liberi come
webmaster</h3>
-
-<p>Se siete dei webmaster che rilasciano programmi in JavaScript liberi sul
-vostro sito, pubblicare chiaramente e coerentemente le informazioni circa le
-licenze di questi aiuta i vostri visitatori ad accertarsi che il software
-che stanno eseguendo sia libero ed aiuta voi ad essere certi di soddisfare
-le condizioni di licenza.</p>
-
-<p>Un metodo per comunicare le licenze è quello descritto qui sopra, nell'<a
-href="#AppendixA">Appendice A</a>. Un secondo metodo, le <a
-href="/licenses/javascript-labels.html"> etichette web di licenza
-JavaScript</a>, può risultare più comodo per le librerie di JavaScript
-minificato, specialmente quando non siete stati voi a scriverle.</p>
-
<div class="translators-notes">
<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
@@ -322,7 +265,7 @@
There is more detail about copyright years in the GNU Maintainers
Information document, www.gnu.org/prep/maintain. -->
-<p>Copyright © 2009-2013, 2016 Richard Stallman</p>
+<p>Copyright © 2009-2013, 2016, 2017 Richard Stallman</p>
<p>Questa pagina è distribuita secondo i termini della licenza <a
rel="license"
href="http://creativecommons.org/licenses/by-nd/4.0/";>Creative Commons
@@ -338,7 +281,7 @@
<p class="unprintable"><!-- timestamp start -->
Ultimo Aggiornamento:
-$Date: 2016/11/18 07:32:45 $
+$Date: 2017/03/26 19:00:33 $
<!-- timestamp end -->
</p>
Index: philosophy/not-ipr.it.html
===================================================================
RCS file: /web/www/www/philosophy/not-ipr.it.html,v
retrieving revision 1.38
retrieving revision 1.39
diff -u -b -r1.38 -r1.39
--- philosophy/not-ipr.it.html 11 Nov 2016 08:58:51 -0000 1.38
+++ philosophy/not-ipr.it.html 26 Mar 2017 19:00:33 -0000 1.39
@@ -32,7 +32,7 @@
fatto rappresenta gli interessi dei detentori dei copyright, dei brevetti e
dei marchi commerciali. L'uso diffuso del termine "proprietà intellettuale"
comincia <a
-href="http://ngrams.googlelabs.com/graph?content=intellectual+property&year_start=1800&year_end=2008&corpus=0&smoothing=1";>dal
+href="https://books.google.com/ngrams/graph?content=intellectual+property&year_start=1800&year_end=2008&corpus=15&smoothing=1&share=&direct_url=t1%3B%2Cintellectual%20property%3B%2Cc0";>dal
1990 circa</a> (<a href="/graphics/seductivemirage.png">copia locale
dell'immagine</a>).
</p>
@@ -223,6 +223,16 @@
</p>
<p>
+Respingere il termine “proprietà intellettuale” non è una pura
+questione filosofica, perché quel termine produce danni concreti. Apple lo
+usò per <a
+href="https://www.theguardian.com/us-news/2017/mar/11/nebraska-farmers-right-to-repair-bill-stalls-apple";>distorcere
+il dibattito sulla legge sul "diritto di riparare" in Nebraska</a>. In
+questo modo Apple fu nelle condizioni di presentare la sua preferenza per la
+segretezza, che va in conflitto con i diritti dei clienti, come una sorta di
+principio che i clienti e lo stato devono rispettare.</p>
+
+<p>
Se volete riflettere con chiarezza sui problemi sollevati dai brevetti, o
dal copyright, o dai marchi di fabbrica, o da altre leggi diverse, il primo
passo è dimenticare l'idea di mescolarle assieme, e trattarle invece come
@@ -323,7 +333,8 @@
There is more detail about copyright years in the GNU Maintainers
Information document, www.gnu.org/prep/maintain. -->
-<p>Copyright © 2004, 2006, 2010, 2013, 2015, 2016 Richard M. Stallman</p>
+<p>Copyright © 2004, 2006, 2010, 2013, 2015, 2016, 2017 Richard
+M. Stallman</p>
<p>Questa pagina è distribuita secondo i termini della licenza <a
rel="license"
href="http://creativecommons.org/licenses/by-nd/4.0/";>Creative Commons
@@ -339,7 +350,7 @@
<p class="unprintable"><!-- timestamp start -->
Ultimo aggiornamento:
-$Date: 2016/11/11 08:58:51 $
+$Date: 2017/03/26 19:00:33 $
<!-- timestamp end -->
</p>
Index: philosophy/selling.it.html
===================================================================
RCS file: /web/www/www/philosophy/selling.it.html,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -b -r1.28 -r1.29
--- philosophy/selling.it.html 18 Nov 2016 07:32:47 -0000 1.28
+++ philosophy/selling.it.html 26 Mar 2017 19:00:33 -0000 1.29
@@ -33,7 +33,8 @@
software'', parliamo di libertà , non di prezzo. Si pensi all'espressione
"free speech" (libertà di parola) piuttosto che all'espressione "free beer"
(birra gratis). In particolare, significa che l'utente è libero di eseguire
-il programma, modificarlo, e ridistribuirlo con o senza modifiche. </p>
+il programma, studiarlo e modificarlo, e ridistribuirlo con o senza
+modifiche. </p>
<p>
I programmi liberi sono talvolta distribuiti gratuitamente, e talvolta ad un
@@ -246,8 +247,8 @@
There is more detail about copyright years in the GNU Maintainers
Information document, www.gnu.org/prep/maintain. -->
-<p>Copyright © 1996, 1997, 1998, 2001, 2007, 2015, 2016 Free Software
-Foundation, Inc.</p>
+<p>Copyright © 1996, 1997, 1998, 2001, 2007, 2015, 2016, 2017 Free
+Software Foundation, Inc.</p>
<p>Questa pagina è distribuita secondo i termini della licenza <a
rel="license"
href="http://creativecommons.org/licenses/by-nd/4.0/";>Creative Commons
@@ -263,7 +264,7 @@
<p class="unprintable"><!-- timestamp start -->
Ultimo aggiornamento:
-$Date: 2016/11/18 07:32:47 $
+$Date: 2017/03/26 19:00:33 $
<!-- timestamp end -->
</p>
Index: philosophy/words-to-avoid.it.html
===================================================================
RCS file: /web/www/www/philosophy/words-to-avoid.it.html,v
retrieving revision 1.90
retrieving revision 1.91
diff -u -b -r1.90 -r1.91
--- philosophy/words-to-avoid.it.html 5 Mar 2017 13:59:48 -0000 1.90
+++ philosophy/words-to-avoid.it.html 26 Mar 2017 19:00:33 -0000 1.91
@@ -702,8 +702,9 @@
ricerca su Internet”, o quando opportuno semplicemente
“cercare” e sforzatevi di usare un motore di ricerca che
rispetti la vostra privacy: ad esempio <a
-href="https://duckduckgo.com/";>DuckDuckGo</a> garantisce (anche se noi non
-possiamo verificarlo in prima persona) di non tracciare i propri utenti.</p>
+href="https://duckduckgo.com/";>DuckDuckGo</a> garantisce di non tracciare i
+propri utenti, anche se nessuno dall'esterno può verificarlo in prima
+persona.</p>
<!-- GNUN-SORT-NEXT-ITEM -->
<!-- GNUN-SORT-BEGIN-KEY -->
@@ -1275,7 +1276,7 @@
There is more detail about copyright years in the GNU Maintainers
Information document, www.gnu.org/prep/maintain. -->
<p>Copyright © 1996, 1997, 1998, 1999, 2001, 2002, 2003, 2004, 2007, 2008,
-2009, 2010, 2011, 2012, 2015, 2016 Free Software Foundation, Inc.</p>
+2009, 2010, 2011, 2012, 2015, 2016, 2017 Free Software Foundation, Inc.</p>
<p>Questa pagina è distribuita secondo i termini della licenza <a
rel="license"
href="http://creativecommons.org/licenses/by-nd/4.0/";>Creative Commons
@@ -1292,7 +1293,7 @@
<p class="unprintable"><!-- timestamp start -->
Ultimo aggiornamento:
-$Date: 2017/03/05 13:59:48 $
+$Date: 2017/03/26 19:00:33 $
<!-- timestamp end -->
</p>
Index: philosophy/po/javascript-trap.it-en.html
===================================================================
RCS file: /web/www/www/philosophy/po/javascript-trap.it-en.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -b -r1.6 -r1.7
--- philosophy/po/javascript-trap.it-en.html 18 Nov 2016 07:32:58 -0000
1.6
+++ philosophy/po/javascript-trap.it-en.html 26 Mar 2017 19:00:33 -0000
1.7
@@ -11,23 +11,32 @@
<p><strong>You may be running nonfree programs on your computer every
day without realizing it—through your web browser.</strong></p>
+<!-- any links that used to point to the appendices should point to
+ free-your-javascript.html instead. -->
+
+<blockquote>
+<p>Webmasters: there are
+<a href="/software/librejs/free-your-javascript.html">several ways</a>
+to indicate the license of JavaScript programs in a web site.</p>
+</blockquote>
+
<p>In the free software community, the idea that nonfree programs
-mistreat their users is familiar. Some of us refuse entirely to
-install proprietary software, and many others consider nonfreedom a
-strike against the program. Many users are aware that this issue
-applies to the plug-ins that browsers offer to install, since they can
-be free or nonfree.</p>
-
-<p>But browsers run other nonfree programs which they don't ask you
-about or even tell you about—programs that web pages contain or
-link to. These programs are most often written in JavaScript, though
-other languages are also used.</p>
-
-<p>JavaScript (officially called ECMAScript, but few use that name) was
-once used for minor frills in web pages, such as cute but inessential
-navigation and display features. It was acceptable to consider these
-as mere extensions of HTML markup, rather than as true software; they
-did not constitute a significant issue.</p>
+mistreat their users is familiar. Some of us defend our freedom by
+rejecting all proprietary software on our computers. Many others
+recognize nonfreeness as a strike against the program.</p>
+
+<p>Many users are aware that this issue applies to the plug-ins that
+browsers offer to install, since they can be free or nonfree. But
+browsers run other nonfree programs which they don't ask you about, or
+even tell you about—programs that web pages contain or link to.
+These programs are most often written in JavaScript, though other
+languages are also used.</p>
+
+<p>JavaScript (officially called ECMAScript, but few use that name)
+was once used for minor frills in web pages, such as cute but
+inessential navigation and display features. It was acceptable to
+consider these as mere extensions of HTML markup, rather than as true
+software, and disregard the issue.</p>
<p>Many sites still use JavaScript that way, but some use it for major
programs that do large jobs. For instance, Google Docs tries to download into
@@ -180,85 +189,22 @@
site. Please don't hesitate to enable JavaScript temporarily to do
that—but remember to disable it again afterwards.</p>
+<!-- any links that used to point to the appendices should point to
+ free-your-javascript.html instead. -->
+
+<blockquote>
+<p>Webmasters: there are
+<a href="/software/librejs/free-your-javascript.html">several ways</a>
+to indicate the license of JavaScript programs in a web site.</p>
+</blockquote>
+
<p><strong>Thank you to <a href="/people/people.html#mattlee">Matt Lee</a>
and <a href="http://ejohn.org";>John Resig</a> for their help in
defining our proposed criterion, and to David Parunakian for
helping to make me aware of the problem.</strong></p>
-<h3 id="AppendixA">Appendix A: a convention for releasing free JavaScript
programs</h3>
-
-<p>For references to corresponding source code, we recommend</p>
-<pre dir="ltr">
-
- // @source:
-
-</pre>
-
-<p>followed by the URL. This satisfies the GNU GPL's requirement to
-distribute source code. If the source is on a different site, you
-must take care
-to <a href="/licenses/gpl-faq.html#SourceAndBinaryOnDifferentSites">
-handle that properly</a>. Source code is necessary for the program to
-be free.
-</p>
-
-<p>To indicate the license of the JavaScript code embedded in a page, we
-recommend putting the license notice between two notes of this form:</p>
-<pre dir="ltr">
-<!--TRANSLATORS: Do not translate these license notices. The <pre>
- elements have dir="ltr" explicitly set to cater for RTL languages.-->
- @licstart The following is the entire license notice for the
- JavaScript code in this page.
- ...
- @licend The above is the entire license notice
- for the JavaScript code in this page.
-
-</pre>
-<p>Of course, all of this should be contained in a multiline comment.</p>
-
-<p>The <a href="/licenses/gpl.html">GNU GPL</a>, like many other free
-software licenses, requires distribution of a copy of the license with
-both source and binary forms of the program. However, the GNU GPL is
-long enough that including it in a page with a JavaScript program can
-be inconvenient. You can remove that requirement, for code that you
-have the copyright on, with a license notice like this:</p>
-<pre dir="ltr">
-
- Copyright (C) YYYY Developer
-
- The JavaScript code in this page is free software: you can
- redistribute it and/or modify it under the terms of the GNU
- General Public License (GNU GPL) as published by the Free Software
- Foundation, either version 3 of the License, or (at your option)
- any later version. The code is distributed WITHOUT ANY WARRANTY;
- without even the implied warranty of MERCHANTABILITY or FITNESS
- FOR A PARTICULAR PURPOSE. See the GNU GPL for more details.
-
- As additional permission under GNU GPL version 3 section 7, you
- may distribute non-source (e.g., minimized or compacted) forms of
- that code without the copy of the GNU GPL normally required by
- section 4, provided you include this license notice and a URL
- through which recipients can access the Corresponding Source.
-
-</pre>
-
<p>I thank Jaffar Rumith for bringing this issue to my attention.</p>
-<h3 id="AppendixB">Appendix B: Publishing free JavaScript programs as
- a webmaster</h3>
-
-<p>If you're a webmaster deploying free JavaScript software
- on your site, clearly and consistently publishing information about
- those files' licenses and source code helps your visitors make
- sure that they're running free software, and help you comply with
- license conditions.</p>
-
-<p>One method of stating the licenses is the one described above in
- <a href="#AppendixA">Appendix A</a>. A second
- method, <a href="/licenses/javascript-labels.html"> JavaScript
- license web labels</a>, can be more convenient for libraries of
- minified JavaScript code, especially when you didn't write them.</p>
-
</div><!-- for id="content", starts in the include above -->
<!--#include virtual="/server/footer.html" -->
<div id="footer">
@@ -306,7 +252,7 @@
There is more detail about copyright years in the GNU Maintainers
Information document, www.gnu.org/prep/maintain. -->
-<p>Copyright © 2009-2013, 2016 Richard Stallman</p>
+<p>Copyright © 2009-2013, 2016, 2017 Richard Stallman</p>
<p>This page is licensed under a <a rel="license"
href="http://creativecommons.org/licenses/by-nd/4.0/";>Creative
@@ -316,7 +262,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2016/11/18 07:32:58 $
+$Date: 2017/03/26 19:00:33 $
<!-- timestamp end -->
</p>
</div>
Index: philosophy/po/javascript-trap.it.po
===================================================================
RCS file: /web/www/www/philosophy/po/javascript-trap.it.po,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -b -r1.22 -r1.23
--- philosophy/po/javascript-trap.it.po 26 Mar 2017 13:57:51 -0000 1.22
+++ philosophy/po/javascript-trap.it.po 26 Mar 2017 19:00:33 -0000 1.23
@@ -15,7 +15,6 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
-"X-Outdated-Since: 2017-03-20 14:26+0000\n"
"X-Generator: Poedit 1.5.4\n"
#. type: Content of: <h2>
@@ -44,21 +43,7 @@
"html\">molti modi</a> di indicare la licenza dei programmi JavaScript in un "
"sito."
-# | In the free software community, the idea that nonfree programs mistreat
-# | their users is familiar. Some of us [-refuse entirely to install-]
-# | {+defend our freedom by rejecting all+} proprietary [-software, and many-]
-# | {+software on our computers. Many+} others [-consider nonfreedom-]
-# | {+recognize nonfreeness as+} a strike against the program. [-Many users
-# | are aware that this issue applies to the plug-ins that browsers offer to
-# | install, since they can be free or nonfree.-]
-#. type: Content of: <p>
-#| msgid ""
-#| "In the free software community, the idea that nonfree programs mistreat "
-#| "their users is familiar. Some of us refuse entirely to install "
-#| "proprietary software, and many others consider nonfreedom a strike "
-#| "against the program. Many users are aware that this issue applies to the "
-#| "plug-ins that browsers offer to install, since they can be free or "
-#| "nonfree."
+#. type: Content of: <p>
msgid ""
"In the free software community, the idea that nonfree programs mistreat "
"their users is familiar. Some of us defend our freedom by rejecting all "
@@ -70,18 +55,7 @@
"rifiutandosi categoricamente di installare software proprietario; molti "
"altri considerano la non-libertà un punto negativo per il programma."
-# | {+Many users are aware that this issue applies to the plug-ins that
-# | browsers offer to install, since they can be free or nonfree.+} But
-# | browsers run other nonfree programs which they don't ask you about{+,+} or
-# | even tell you about—programs that web pages contain or link to.
-# | These programs are most often written in JavaScript, though other
-# | languages are also used.
-#. type: Content of: <p>
-#| msgid ""
-#| "But browsers run other nonfree programs which they don't ask you about or "
-#| "even tell you about—programs that web pages contain or link to. "
-#| "These programs are most often written in JavaScript, though other "
-#| "languages are also used."
+#. type: Content of: <p>
msgid ""
"Many users are aware that this issue applies to the plug-ins that browsers "
"offer to install, since they can be free or nonfree. But browsers run other "
@@ -96,18 +70,7 @@
"web contengono o includono da altri siti. Questi programmi sono spesso "
"scritti in JavaScript, anche se alle volte sono scritti in altri linguaggi."
-# | JavaScript (officially called ECMAScript, but few use that name) was once
-# | used for minor frills in web pages, such as cute but inessential
-# | navigation and display features. It was acceptable to consider these as
-# | mere extensions of HTML markup, rather than as true [-software; they did
-# | not constitute a significant-] {+software, and disregard the+} issue.
-#. type: Content of: <p>
-#| msgid ""
-#| "JavaScript (officially called ECMAScript, but few use that name) was once "
-#| "used for minor frills in web pages, such as cute but inessential "
-#| "navigation and display features. It was acceptable to consider these as "
-#| "mere extensions of HTML markup, rather than as true software; they did "
-#| "not constitute a significant issue."
+#. type: Content of: <p>
msgid ""
"JavaScript (officially called ECMAScript, but few use that name) was once "
"used for minor frills in web pages, such as cute but inessential navigation "
@@ -516,9 +479,7 @@
"<a href=\"/server/standards/README.translations.html\">Guida alle "
"traduzioni</a>."
-# | Copyright © 2009-2013, [-2016-] {+2016, 2017+} Richard Stallman
#. type: Content of: <div><p>
-#| msgid "Copyright © 2009-2013, 2016 Richard Stallman"
msgid "Copyright © 2009-2013, 2016, 2017 Richard Stallman"
msgstr "Copyright © 2009-2013, 2016, 2017 Richard Stallman"
Index: philosophy/po/not-ipr.it-en.html
===================================================================
RCS file: /web/www/www/philosophy/po/not-ipr.it-en.html,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -b -r1.20 -r1.21
--- philosophy/po/not-ipr.it-en.html 11 Nov 2016 08:58:52 -0000 1.20
+++ philosophy/po/not-ipr.it-en.html 26 Mar 2017 19:00:33 -0000 1.21
@@ -25,7 +25,7 @@
Property” Organization (WIPO), and only became really common in recent
years. (WIPO is formally a UN organization, but in fact represents the
interests of the holders of copyrights, patents, and trademarks.) Wide use
dates from
-<a
href="http://ngrams.googlelabs.com/graph?content=intellectual+property&year_start=1800&year_end=2008&corpus=0&smoothing=1";>around
+<a
href="https://books.google.com/ngrams/graph?content=intellectual+property&year_start=1800&year_end=2008&corpus=15&smoothing=1&share=&direct_url=t1%3B%2Cintellectual%20property%3B%2Cc0";>around
1990</a>. (<a href="/graphics/seductivemirage.png">Local image copy</a>)
</p>
@@ -207,6 +207,15 @@
</p>
<p>
+Rejection of “intellectual property” is not mere
+philosophical recreation. The term does real harm. Apple used it
+to <a
href="https://www.theguardian.com/us-news/2017/mar/11/nebraska-farmers-right-to-repair-bill-stalls-apple";>warp
debate about Nebraska's
+“right to repair” bill</a>. The bogus concept gave
+Apple a way to dress up its preference for secrecy, which conficts
+with its customers' rights, as a supposed principle that customers
+and the state must yield to.</p>
+
+<p>
If you want to think clearly about the issues raised by patents, or
copyrights, or trademarks, or various other different laws, the first
step is to
@@ -293,7 +302,7 @@
There is more detail about copyright years in the GNU Maintainers
Information document, www.gnu.org/prep/maintain. -->
-<p>Copyright © 2004, 2006, 2010, 2013, 2015, 2016 Richard M. Stallman</p>
+<p>Copyright © 2004, 2006, 2010, 2013, 2015, 2016, 2017 Richard M.
Stallman</p>
<p>This page is licensed under a <a rel="license"
href="http://creativecommons.org/licenses/by-nd/4.0/";>Creative
@@ -303,7 +312,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2016/11/11 08:58:52 $
+$Date: 2017/03/26 19:00:33 $
<!-- timestamp end -->
</p>
</div>
Index: philosophy/po/not-ipr.it.po
===================================================================
RCS file: /web/www/www/philosophy/po/not-ipr.it.po,v
retrieving revision 1.54
retrieving revision 1.55
diff -u -b -r1.54 -r1.55
--- philosophy/po/not-ipr.it.po 26 Mar 2017 13:57:51 -0000 1.54
+++ philosophy/po/not-ipr.it.po 26 Mar 2017 19:00:33 -0000 1.55
@@ -13,7 +13,6 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
-"X-Outdated-Since: 2017-03-05 21:26+0000\n"
"X-Generator: Poedit 1.5.4\n"
# type: Content of: <title>
@@ -55,28 +54,7 @@
"su queste entità farebbe bene ad evitare accuratamente questo termine. "
# type: Content of: <p>
-# | According to Professor Mark Lemley, now of the Stanford Law School, the
-# | widespread use of the term “intellectual property” is a
-# | fashion that followed the 1967 founding of the World “Intellectual
-# | Property” Organization (WIPO), and only became really common in
-# | recent years. (WIPO is formally a UN organization, but in fact represents
-# | the interests of the holders of copyrights, patents, and trademarks.) Wide
-# | use dates from <a
-# |
[-href=\"http://ngrams.googlelabs.com/graph?content=intellectual+property&year_start=1800&year_end=2008&corpus=0&smoothing=1\";>around-]
-# |
{+href=\"https://books.google.com/ngrams/graph?content=intellectual+property&year_start=1800&year_end=2008&corpus=15&smoothing=1&share=&direct_url=t1%3B%2Cintellectual%20property%3B%2Cc0\";>around+}
-# | 1990</a>. (<a href=\"/graphics/seductivemirage.png\">Local image copy</a>)
-#. type: Content of: <p>
-#| msgid ""
-#| "According to Professor Mark Lemley, now of the Stanford Law School, the "
-#| "widespread use of the term “intellectual property” is a "
-#| "fashion that followed the 1967 founding of the World “Intellectual "
-#| "Property” Organization (WIPO), and only became really common in "
-#| "recent years. (WIPO is formally a UN organization, but in fact represents "
-#| "the interests of the holders of copyrights, patents, and trademarks.) "
-#| "Wide use dates from <a href=\"http://ngrams.googlelabs.com/graph?";
-#| "content=intellectual+property&year_start=1800&year_end=2008&"
-#| "corpus=0&smoothing=1\">around 1990</a>. (<a href=\"/graphics/"
-#| "seductivemirage.png\">Local image copy</a>)"
+#. type: Content of: <p>
msgid ""
"According to Professor Mark Lemley, now of the Stanford Law School, the "
"widespread use of the term “intellectual property” is a fashion "
@@ -580,11 +558,7 @@
"<a href=\"/server/standards/README.translations.html\">Guida alle "
"traduzioni</a>."
-# | Copyright © 2004, 2006, 2010, 2013, 2015, [-2016-] {+2016, 2017+}
-# | Richard M. Stallman
#. type: Content of: <div><p>
-#| msgid ""
-#| "Copyright © 2004, 2006, 2010, 2013, 2015, 2016 Richard M. Stallman"
msgid ""
"Copyright © 2004, 2006, 2010, 2013, 2015, 2016, 2017 Richard M. Stallman"
msgstr ""
Index: philosophy/po/selling.it-en.html
===================================================================
RCS file: /web/www/www/philosophy/po/selling.it-en.html,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -b -r1.20 -r1.21
--- philosophy/po/selling.it-en.html 18 Nov 2016 07:33:02 -0000 1.20
+++ philosophy/po/selling.it-en.html 26 Mar 2017 19:00:33 -0000 1.21
@@ -28,7 +28,7 @@
either to freedom or to price. When we speak of “free software”,
we're talking about freedom, not price. (Think of “free speech”,
not “free beer”.) Specifically, it means that a user is free to
run
-the program, change the program, and redistribute the program with or
+the program, study and change the program, and redistribute the program with or
without changes.</p>
<p>
@@ -228,7 +228,7 @@
There is more detail about copyright years in the GNU Maintainers
Information document, www.gnu.org/prep/maintain. -->
-<p>Copyright © 1996, 1997, 1998, 2001, 2007, 2015, 2016
+<p>Copyright © 1996, 1997, 1998, 2001, 2007, 2015, 2016, 2017
Free Software Foundation, Inc.</p>
<p>This page is licensed under a <a rel="license"
@@ -239,7 +239,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2016/11/18 07:33:02 $
+$Date: 2017/03/26 19:00:33 $
<!-- timestamp end -->
</p>
</div>
Index: philosophy/po/selling.it.po
===================================================================
RCS file: /web/www/www/philosophy/po/selling.it.po,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -b -r1.27 -r1.28
--- philosophy/po/selling.it.po 26 Mar 2017 13:57:51 -0000 1.27
+++ philosophy/po/selling.it.po 26 Mar 2017 19:00:33 -0000 1.28
@@ -13,7 +13,6 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-"X-Outdated-Since: 2017-03-20 14:26+0000\n"
"X-Generator: Poedit 1.5.4\n"
#. type: Content of: <title>
@@ -58,20 +57,7 @@
"che non permette agli utenti di fare copie e rivenderle non è libera. Se vi "
"sembra sorprendente, per favore continuate a leggere."
-# | The word “free” has two legitimate general meanings; it can
-# | refer either to freedom or to price. When we speak of “free
-# | software”, we're talking about freedom, not price. (Think of
-# | “free speech”, not “free beer”.) Specifically, it
-# | means that a user is free to run the program, {+study and+} change the
-# | program, and redistribute the program with or without changes.
-#. type: Content of: <p>
-#| msgid ""
-#| "The word “free” has two legitimate general meanings; it can "
-#| "refer either to freedom or to price. When we speak of “free "
-#| "software”, we're talking about freedom, not price. (Think of "
-#| "“free speech”, not “free beer”.) Specifically, "
-#| "it means that a user is free to run the program, change the program, and "
-#| "redistribute the program with or without changes."
+#. type: Content of: <p>
msgid ""
"The word “free” has two legitimate general meanings; it can "
"refer either to freedom or to price. When we speak of “free "
@@ -416,12 +402,7 @@
"<a href=\"/server/standards/README.translations.html\">Guida alle "
"traduzioni</a>."
-# | Copyright © 1996, 1997, 1998, 2001, 2007, 2015, [-2016-] {+2016,
-# | 2017+} Free Software Foundation, Inc.
#. type: Content of: <div><p>
-#| msgid ""
-#| "Copyright © 1996, 1997, 1998, 2001, 2007, 2015, 2016 Free Software "
-#| "Foundation, Inc."
msgid ""
"Copyright © 1996, 1997, 1998, 2001, 2007, 2015, 2016, 2017 Free "
"Software Foundation, Inc."
Index: philosophy/po/words-to-avoid.it-en.html
===================================================================
RCS file: /web/www/www/philosophy/po/words-to-avoid.it-en.html,v
retrieving revision 1.80
retrieving revision 1.81
diff -u -b -r1.80 -r1.81
--- philosophy/po/words-to-avoid.it-en.html 5 Mar 2017 13:59:49 -0000
1.80
+++ philosophy/po/words-to-avoid.it-en.html 26 Mar 2017 19:00:33 -0000
1.81
@@ -744,8 +744,9 @@
name of one particular search engine among others. We suggest to use
the term “search the web” or (in some contexts) just
“search”. Try to use a search engine that respects your
-privacy; <a href="https://duckduckgo.com/";>DuckDuckGo</a> claims not
-to track its users, although we cannot confirm.</p>
+privacy; for instance, <a href="https://duckduckgo.com/";>DuckDuckGo</a>
+claims not to track its users. (There is no way for outsiders to
+verify claims of that kind.)</p>
<!-- GNUN-SORT-NEXT-ITEM -->
<!-- GNUN-SORT-BEGIN-KEY -->
@@ -1270,7 +1271,7 @@
Information document, www.gnu.org/prep/maintain. -->
<p>Copyright © 1996, 1997, 1998, 1999, 2001, 2002, 2003, 2004, 2007,
-2008, 2009, 2010, 2011, 2012, 2015, 2016 Free Software Foundation, Inc.</p>
+2008, 2009, 2010, 2011, 2012, 2015, 2016, 2017 Free Software Foundation,
Inc.</p>
<p>This page is licensed under a <a rel="license"
href="http://creativecommons.org/licenses/by-nd/4.0/";>Creative
@@ -1280,7 +1281,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2017/03/05 13:59:49 $
+$Date: 2017/03/26 19:00:33 $
<!-- timestamp end -->
</p>
</div>
Index: philosophy/po/words-to-avoid.it.po
===================================================================
RCS file: /web/www/www/philosophy/po/words-to-avoid.it.po,v
retrieving revision 1.220
retrieving revision 1.221
diff -u -b -r1.220 -r1.221
--- philosophy/po/words-to-avoid.it.po 26 Mar 2017 13:57:51 -0000 1.220
+++ philosophy/po/words-to-avoid.it.po 26 Mar 2017 19:00:33 -0000 1.221
@@ -18,7 +18,6 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
-"X-Outdated-Since: 2017-03-20 14:26+0000\n"
"X-Generator: Poedit 1.5.4\n"
#. type: Content of: <title>
@@ -277,8 +276,8 @@
#. type: Content of: <p>
msgid "“<a href=\"#SharingEconomy\">Sharing economy</a>” |"
msgstr ""
-"“<a href=\"#SharingEconomy\">Economia di condivisione (Sharing "
-"economy)</a>” |"
+"“<a href=\"#SharingEconomy\">Economia di condivisione (Sharing economy)"
+"</a>” |"
#. GNUN-SORT-NEXT-ITEM
#. type: Content of: <p>
@@ -1425,24 +1424,7 @@
msgid "“Google”"
msgstr "“Googlare”"
-# | Please avoid using the term “google” as a verb, meaning to
-# | search for something on the internet. “Google” is just the
-# | name of one particular search engine among others. We suggest to use the
-# | term “search the web” or (in some contexts) just
-# | “search”. Try to use a search engine that respects your
-# | privacy; {+for instance,+} <a
-# | href=\"https://duckduckgo.com/\";>DuckDuckGo</a> claims not to track its
-# | [-users, although we cannot confirm.-] {+users. (There is no way for
-# | outsiders to verify claims of that kind.)+}
-#. type: Content of: <p>
-#| msgid ""
-#| "Please avoid using the term “google” as a verb, meaning to "
-#| "search for something on the internet. “Google” is just the "
-#| "name of one particular search engine among others. We suggest to use the "
-#| "term “search the web” or (in some contexts) just “"
-#| "search”. Try to use a search engine that respects your privacy; <a "
-#| "href=\"https://duckduckgo.com/\";>DuckDuckGo</a> claims not to track its "
-#| "users, although we cannot confirm."
+#. type: Content of: <p>
msgid ""
"Please avoid using the term “google” as a verb, meaning to "
"search for something on the internet. “Google” is just the name "
@@ -2084,9 +2066,9 @@
"your privacy, try one of the <a href=\"https://libreplanet.org/wiki/Group:";
"Skype_Replacement\"> numerous free Skype replacements</a>."
msgstr ""
-"Non usate il neologismo “skypare” per indicare una "
-"(video)chiamata via Internet. Skype è solo uno dei tanti programmi per "
-"questo scopo, e per di più è software proprietario e <a href=\"/philosophy/"
+"Non usate il neologismo “skypare” per indicare una (video)"
+"chiamata via Internet. Skype è solo uno dei tanti programmi per questo "
+"scopo, e per di più è software proprietario e <a href=\"/philosophy/"
"proprietary/proprietary-surveillance.html#SpywareInSkype\"> spia i propri "
"utenti</a>. Per effettuare (video)chiamate via Internet in un modo che "
"rispetti la vostra libertà e la vostra privacy, usate uno dei tanti <a href="
@@ -2344,13 +2326,7 @@
"<a href=\"/server/standards/README.translations.html\">Guida alle "
"traduzioni</a>."
-# | Copyright © 1996, 1997, 1998, 1999, 2001, 2002, 2003, 2004, 2007,
-# | 2008, 2009, 2010, 2011, 2012, 2015, [-2016-] {+2016, 2017+} Free Software
-# | Foundation, Inc.
#. type: Content of: <div><p>
-#| msgid ""
-#| "Copyright © 1996, 1997, 1998, 1999, 2001, 2002, 2003, 2004, 2007, "
-#| "2008, 2009, 2010, 2011, 2012, 2015, 2016 Free Software Foundation, Inc."
msgid ""
"Copyright © 1996, 1997, 1998, 1999, 2001, 2002, 2003, 2004, 2007, 2008, "
"2009, 2010, 2011, 2012, 2015, 2016, 2017 Free Software Foundation, Inc."
Index: proprietary/malware-apple.it.html
===================================================================
RCS file: /web/www/www/proprietary/malware-apple.it.html,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -b -r1.20 -r1.21
--- proprietary/malware-apple.it.html 26 Mar 2017 03:59:47 -0000 1.20
+++ proprietary/malware-apple.it.html 26 Mar 2017 19:00:33 -0000 1.21
@@ -3,7 +3,7 @@
https://www.gnu.org/proprietary/po/malware-apple.it.po</a>'
--><!--#set var="ORIGINAL_FILE" value="/proprietary/malware-apple.html"
--><!--#set var="DIFF_FILE" value="/proprietary/po/malware-apple.it-diff.html"
- --><!--#set var="OUTDATED_SINCE" value="2017-01-25" --><!--#set
var="ENGLISH_PAGE" value="/proprietary/malware-apple.en.html" -->
+ --><!--#set var="OUTDATED_SINCE" value="2017-01-25" -->
<!--#include virtual="/server/header.it.html" -->
<!-- Parent-Version: 1.79 -->
@@ -505,7 +505,7 @@
<p class="unprintable"><!-- timestamp start -->
Ultimo aggiornamento:
-$Date: 2017/03/26 03:59:47 $
+$Date: 2017/03/26 19:00:33 $
<!-- timestamp end -->
</p>
Index: proprietary/proprietary-censorship.it.html
===================================================================
RCS file: /web/www/www/proprietary/proprietary-censorship.it.html,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- proprietary/proprietary-censorship.it.html 26 Mar 2017 03:59:47 -0000
1.11
+++ proprietary/proprietary-censorship.it.html 26 Mar 2017 19:00:33 -0000
1.12
@@ -3,7 +3,7 @@
https://www.gnu.org/proprietary/po/proprietary-censorship.it.po</a>'
--><!--#set var="ORIGINAL_FILE"
value="/proprietary/proprietary-censorship.html"
--><!--#set var="DIFF_FILE"
value="/proprietary/po/proprietary-censorship.it-diff.html"
- --><!--#set var="OUTDATED_SINCE" value="2017-01-25" --><!--#set
var="ENGLISH_PAGE" value="/proprietary/proprietary-censorship.en.html" -->
+ --><!--#set var="OUTDATED_SINCE" value="2017-01-25" -->
<!--#include virtual="/server/header.it.html" -->
<!-- Parent-Version: 1.79 -->
@@ -170,7 +170,7 @@
<p class="unprintable"><!-- timestamp start -->
Ultimo aggiornamento:
-$Date: 2017/03/26 03:59:47 $
+$Date: 2017/03/26 19:00:33 $
<!-- timestamp end -->
</p>
Index: proprietary/po/malware-amazon.it-diff.html
===================================================================
RCS file: /web/www/www/proprietary/po/malware-amazon.it-diff.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- proprietary/po/malware-amazon.it-diff.html 18 Mar 2017 13:00:16 -0000
1.3
+++ proprietary/po/malware-amazon.it-diff.html 26 Mar 2017 19:00:33 -0000
1.4
@@ -214,7 +214,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2017/03/18 13:00:16 $
+$Date: 2017/03/26 19:00:33 $
<!-- timestamp end -->
</p>
</div>
Index: proprietary/po/malware-amazon.it.po
===================================================================
RCS file: /web/www/www/proprietary/po/malware-amazon.it.po,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -b -r1.5 -r1.6
--- proprietary/po/malware-amazon.it.po 26 Mar 2017 13:57:52 -0000 1.5
+++ proprietary/po/malware-amazon.it.po 26 Mar 2017 19:00:34 -0000 1.6
@@ -18,9 +18,9 @@
"X-Outdated-Since: 2016-12-31 16:55+0000\n"
"X-Generator: Poedit 1.5.4\n"
+#. type: Content of: <title>
# | {+Amazon's Software Is+} Malware [-in the Kindle Swindle-] - GNU Project -
# | Free Software Foundation
-#. type: Content of: <title>
#, fuzzy
#| msgid ""
#| "Malware in the Kindle Swindle - GNU Project - Free Software Foundation"
@@ -60,23 +60,23 @@
"sviluppatori, consapevoli dell'impossibilità da parte degli utenti di "
"riparare eventuali funzionalità malevole, sono tentati ad imporne."
-# | [-<strong>Type of malware</strong>-]{+Type of product:+}
#. type: Content of: <div><h3>
+# | [-<strong>Type of malware</strong>-]{+Type of product:+}
#, fuzzy
#| msgid "<strong>Type of malware</strong>"
msgid "Type of product:"
msgstr "<strong>Typo di malware</strong>"
+#. type: Content of: <div><ul><li>
# | [-Malware in the Kindle Swindle-]{+<a
# | href=\"#swindle\">Kindle Swindle</a>+}
-#. type: Content of: <div><ul><li>
#, fuzzy
#| msgid "Malware in the Kindle Swindle"
msgid "<a href=\"#swindle\">Kindle Swindle</a>"
msgstr "Malware nel Kindle Swindle"
-# | <a [-href=\"#back-doors\">Back doors</a>-] {+href=\"#echo\">Echo</a>+}
#. type: Content of: <div><ul><li>
+# | <a [-href=\"#back-doors\">Back doors</a>-] {+href=\"#echo\">Echo</a>+}
#, fuzzy
#| msgid "<a href=\"#back-doors\">Back doors</a>"
msgid "<a href=\"#echo\">Echo</a>"
@@ -100,15 +100,15 @@
"\"gestione delle restrizioni digitali\")</a> ed <a href=\"/philosophy/ebooks."
"html\">altre funzionalità malevole</a>."
-# | [-<strong>Type of malware</strong>-]{+Type of malware+}
#. type: Content of: <div><h3>
+# | [-<strong>Type of malware</strong>-]{+Type of malware+}
#, fuzzy
#| msgid "<strong>Type of malware</strong>"
msgid "Type of malware"
msgstr "<strong>Typo di malware</strong>"
-# || No change detected. The change might only be in amounts of spaces.
#. type: Content of: <div><ul><li>
+# || No change detected. The change might only be in amounts of spaces.
#, fuzzy
#| msgid "<a href=\"#back-doors\">Back doors</a>"
msgid "<a href=\"#back-doors\">Back doors</a>"
@@ -133,12 +133,12 @@
msgid "Amazon Kindle Swindle Back Doors"
msgstr "Backdoor di Amazon Kindle \"Swindle\""
+#. type: Content of: <ul><li><p>
# | The Amazon [-Kindle-] {+Kindle-Swindle+} has a back door that has been
# | used to <a
# |
href=\"http://pogue.blogs.nytimes.com/2009/07/17/some-e-books-are-more-equal-than-others/\";>
# | remotely erase books</a>. {+One of the books erased was 1984, by George
# | Orwell.+}
-#. type: Content of: <ul><li><p>
#, fuzzy
#| msgid ""
#| "The Amazon Kindle has a back door that has been used to <a href=\"http://";
@@ -219,15 +219,15 @@
"l'opinione pubblica a favore del DRM. Ciò nonostante, l'articolo rimane una "
"cronaca dei fatti."
-# | Malware in the [-Kindle Swindle-] {+Echo+}
#. type: Content of: <h2>
+# | Malware in the [-Kindle Swindle-] {+Echo+}
#, fuzzy
#| msgid "Malware in the Kindle Swindle"
msgid "Malware in the Echo"
msgstr "Malware nel Kindle Swindle"
-# | Amazon [-Kindle Swindle-] {+Echo+} Back Doors
#. type: Content of: <h3>
+# | Amazon [-Kindle Swindle-] {+Echo+} Back Doors
#, fuzzy
#| msgid "Amazon Kindle Swindle Back Doors"
msgid "Amazon Echo Back Doors"
@@ -293,9 +293,9 @@
"<a href=\"/server/standards/README.translations.html\">Guida alle "
"traduzioni</a>."
+#. type: Content of: <div><p>
# | Copyright © 2014, 2015, [-2016-] {+2016, 2017+} Free Software
# | Foundation, Inc.
-#. type: Content of: <div><p>
#, fuzzy
#| msgid "Copyright © 2014, 2015, 2016 Free Software Foundation, Inc."
msgid "Copyright © 2014, 2015, 2016, 2017 Free Software Foundation, Inc."
Index: proprietary/po/malware-apple.it-diff.html
===================================================================
RCS file: /web/www/www/proprietary/po/malware-apple.it-diff.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- proprietary/po/malware-apple.it-diff.html 26 Mar 2017 03:59:47 -0000
1.1
+++ proprietary/po/malware-apple.it-diff.html 26 Mar 2017 19:00:34 -0000
1.2
@@ -488,7 +488,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2017/03/26 03:59:47 $
+$Date: 2017/03/26 19:00:34 $
<!-- timestamp end -->
</p>
</div>
Index: proprietary/po/malware-apple.it.po
===================================================================
RCS file: /web/www/www/proprietary/po/malware-apple.it.po,v
retrieving revision 1.75
retrieving revision 1.76
diff -u -b -r1.75 -r1.76
--- proprietary/po/malware-apple.it.po 26 Mar 2017 13:57:52 -0000 1.75
+++ proprietary/po/malware-apple.it.po 26 Mar 2017 19:00:34 -0000 1.76
@@ -69,8 +69,8 @@
"sviluppatori, consapevoli dell'impossibilità da parte degli utenti di "
"riparare eventuali funzionalità malevole, sono tentati ad imporne."
-# | [-<strong>Type of malware</strong>-]{+Type of malware+}
#. type: Content of: <div><h3>
+# | [-<strong>Type of malware</strong>-]{+Type of malware+}
#, fuzzy
#| msgid "<strong>Type of malware</strong>"
msgid "Type of malware"
@@ -627,11 +627,11 @@
"iOS_Backdoors_Attack_Points_Surveillance_Mechanisms_Moved.pdf"
"\">presentazione tecnica</a>."
+#. type: Content of: <ul><li><p>
# | The <a {+class=\"not-a-duplicate\"+}
# |
href=\"http://finance.yahoo.com/blogs/the-exchange/privacy-advocates-worry-over-new-apple-iphone-tracking-feature-161836223.html\";>
# | iBeacon</a> lets stores determine exactly where the iThing is, and get
# | other info too.
-#. type: Content of: <ul><li><p>
#, fuzzy
#| msgid ""
#| "The <a href=\"http://finance.yahoo.com/blogs/the-exchange/privacy-";
@@ -890,9 +890,9 @@
"<a href=\"/server/standards/README.translations.html\">Guida alle "
"traduzioni</a>."
+#. type: Content of: <div><p>
# | Copyright © [-2014,-] 2015, [-2016-] {+2016, 2017+} Free Software
# | Foundation, Inc.
-#. type: Content of: <div><p>
#, fuzzy
#| msgid "Copyright © 2014, 2015, 2016 Free Software Foundation, Inc."
msgid "Copyright © 2015, 2016, 2017 Free Software Foundation, Inc."
Index: proprietary/po/malware-microsoft.it.po
===================================================================
RCS file: /web/www/www/proprietary/po/malware-microsoft.it.po,v
retrieving revision 1.94
retrieving revision 1.95
diff -u -b -r1.94 -r1.95
--- proprietary/po/malware-microsoft.it.po 26 Mar 2017 13:57:52 -0000
1.94
+++ proprietary/po/malware-microsoft.it.po 26 Mar 2017 19:00:34 -0000
1.95
@@ -66,8 +66,8 @@
"sviluppatori, consapevoli dell'impossibilità da parte degli utenti di "
"riparare eventuali funzionalità malevole, sono tentati ad imporne."
-# | [-<strong>Type of malware</strong>-]{+Type of malware+}
#. type: Content of: <div><h3>
+# | [-<strong>Type of malware</strong>-]{+Type of malware+}
#, fuzzy
#| msgid "<strong>Type of malware</strong>"
msgid "Type of malware"
@@ -134,11 +134,11 @@
"computer-microsoft-probably-has-your-encryption-key/\"> Microsoft ha già "
"inserito una backdoor nel suo sistema di cifratura dei dischi</a>."
+#. type: Content of: <ul><li><p>
# | Microsoft Windows has a universal back door through which <a
# |
[-href=\"http://www.informationweek.com/news/showArticle.jhtml?articleID=201806263\";>-]
# |
{+href=\"http://www.informationweek.com/microsoft-updates-windows-without-user-permission-apologizes/d/d-id/1059183\";>+}
# | any change whatsoever can be imposed on the users</a>.
-#. type: Content of: <ul><li><p>
#, fuzzy
#| msgid ""
#| "Microsoft Windows has a universal back door through which <a href="
@@ -199,6 +199,7 @@
"programmi, e si dovrebbe avere il diritto di decidere in chi (ammesso che ci "
"sia qualcuno) riporre questa fiducia."
+#. type: Content of: <ul><li><p>
# | {+German government <a
# |
href=\"https://web.archive.org/web/20160310201616/http://drleonardcoldwell.com/2013/08/23/leaked-german-government-warns-key-entities-not-to-use-windows-8-linked-to-nsa/\";>veers
# | away from+} Windows [-8's-] {+8 computers with TPM 2.0 due to potential+}
@@ -206,7 +207,6 @@
# |
href=\"https://web.archive.org/web/20160310201616/http://drleonardcoldwell.com/2013/08/23/leaked-german-government-warns-key-entities-not-to-use-windows-8-linked-to-nsa/\";>-]
# | {+door capabilities of+} the [-German government has decided it can't be
# | trusted</a>.-] {+TPM 2.0 chip</a>.+}
-#. type: Content of: <ul><li><p>
#, fuzzy
#| msgid ""
#| "Windows 8's back doors are so gaping that <a href=\"https://web.archive.";
@@ -794,6 +794,7 @@
msgid "Microsoft Tyrants"
msgstr "Tiranni di Microsoft"
+#. type: Content of: <ul><li><p>
# | Microsoft accidentally left a way for users to install GNU/Linux on
# | Windows RT tablets, but now it has <a
# |
href=\"http://www.securitynewspaper.com/2016/07/15/microsoft-silently-kills-dev-backdoor-boots-linux-locked-windows-rt-slabs/\";>
@@ -802,7 +803,6 @@
# | the users. The article talks of installing “Linux”, but the
# | context shows it is really <a
# | href=\"/gnu/linux-and-gnu.html\">GNU/Linux</a> that users install.
-#. type: Content of: <ul><li><p>
#, fuzzy
#| msgid ""
#| "Microsoft accidentally left a way for users to install GNU/Linux on "
@@ -894,8 +894,8 @@
"<a href=\"/server/standards/README.translations.html\">Guida alle "
"traduzioni</a>."
-# || No change detected. The change might only be in amounts of spaces.
#. type: Content of: <div><p>
+# || No change detected. The change might only be in amounts of spaces.
#, fuzzy
#| msgid ""
#| "Copyright © 2014, 2015, 2016, 2017 Free Software Foundation, Inc."
Index: proprietary/po/malware-mobiles.it-diff.html
===================================================================
RCS file: /web/www/www/proprietary/po/malware-mobiles.it-diff.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -b -r1.5 -r1.6
--- proprietary/po/malware-mobiles.it-diff.html 18 Mar 2017 10:32:29 -0000
1.5
+++ proprietary/po/malware-mobiles.it-diff.html 26 Mar 2017 19:00:34 -0000
1.6
@@ -323,7 +323,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2017/03/18 10:32:29 $
+$Date: 2017/03/26 19:00:34 $
<!-- timestamp end -->
</p>
</div>
Index: proprietary/po/malware-mobiles.it.po
===================================================================
RCS file: /web/www/www/proprietary/po/malware-mobiles.it.po,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -b -r1.31 -r1.32
--- proprietary/po/malware-mobiles.it.po 26 Mar 2017 13:57:52 -0000
1.31
+++ proprietary/po/malware-mobiles.it.po 26 Mar 2017 19:00:34 -0000
1.32
@@ -74,8 +74,8 @@
"del malware di Apple</a> per funzionalità malevole specifiche ai vari "
"iGadget di Apple."
-# | [-<strong>Type of malware</strong>-]{+Type of malware+}
#. type: Content of: <div><h3>
+# | [-<strong>Type of malware</strong>-]{+Type of malware+}
#, fuzzy
#| msgid "<strong>Type of malware</strong>"
msgid "Type of malware"
@@ -450,8 +450,8 @@
"applicazione riescono a ottenere un “Sì, acconsento” da parte "
"degli utenti."
-# | Mobile [-Jails-] {+DRM+}
#. type: Content of: <h3>
+# | Mobile [-Jails-] {+DRM+}
#, fuzzy
#| msgid "Mobile Jails"
msgid "Mobile DRM"
@@ -542,8 +542,8 @@
"<a href=\"/server/standards/README.translations.html\">Guida alle "
"traduzioni</a>."
-# || No change detected. The change might only be in amounts of spaces.
#. type: Content of: <div><p>
+# || No change detected. The change might only be in amounts of spaces.
#, fuzzy
#| msgid ""
#| "Copyright © 2014, 2015, 2016, 2017 Free Software Foundation, Inc."
Index: proprietary/po/proprietary-back-doors.it-diff.html
===================================================================
RCS file: /web/www/www/proprietary/po/proprietary-back-doors.it-diff.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- proprietary/po/proprietary-back-doors.it-diff.html 10 Mar 2017 00:59:31
-0000 1.3
+++ proprietary/po/proprietary-back-doors.it-diff.html 26 Mar 2017 19:00:34
-0000 1.4
@@ -399,7 +399,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2017/03/10 00:59:31 $
+$Date: 2017/03/26 19:00:34 $
<!-- timestamp end -->
</p>
</div>
Index: proprietary/po/proprietary-back-doors.it.po
===================================================================
RCS file: /web/www/www/proprietary/po/proprietary-back-doors.it.po,v
retrieving revision 1.72
retrieving revision 1.73
diff -u -b -r1.72 -r1.73
--- proprietary/po/proprietary-back-doors.it.po 26 Mar 2017 13:57:52 -0000
1.72
+++ proprietary/po/proprietary-back-doors.it.po 26 Mar 2017 19:00:34 -0000
1.73
@@ -342,11 +342,11 @@
"backdoor universale nel chip del modem. Perché quindi Coolpad ha deciso di "
"introdurne un'altra? Perché questa è controllata da Coolpad."
+#. type: Content of: <ul><li><p>
# | Microsoft Windows has a universal back door through which <a
# |
[-href=\"http://www.informationweek.com/news/showArticle.jhtml?articleID=201806263\";>-]
# |
{+href=\"https://web.archive.org/web/20071011010707/http://informationweek.com/news/showArticle.jhtml?articleID=201806263\";>+}
# | any change whatsoever can be imposed on the users</a>.
-#. type: Content of: <ul><li><p>
#, fuzzy
#| msgid ""
#| "Microsoft Windows has a universal back door through which <a href="
@@ -384,6 +384,7 @@
"technology/2015/07/windows-10-updates-to-be-automatic-and-mandatory-for-home-"
"users\">forzati e immediati</a>."
+#. type: Content of: <ul><li><p>
# | {+German government <a
# |
href=\"https://web.archive.org/web/20160310201616/http://drleonardcoldwell.com/2013/08/23/leaked-german-government-warns-key-entities-not-to-use-windows-8-linked-to-nsa/\";>veers
# | away from+} Windows [-8's-] {+8 computers with TPM 2.0 due to potential+}
@@ -391,7 +392,6 @@
# |
href=\"https://web.archive.org/web/20160310201616/http://drleonardcoldwell.com/2013/08/23/leaked-german-government-warns-key-entities-not-to-use-windows-8-linked-to-nsa/\";>-]
# | {+door capabilities of+} the [-German government has decided it can't be
# | trusted</a>.-] {+TPM 2.0 chip</a>.+}
-#. type: Content of: <ul><li><p>
#, fuzzy
#| msgid ""
#| "Windows 8's back doors are so gaping that <a href=\"https://web.archive.";
@@ -546,12 +546,12 @@
"Galaxy che eseguono versioni proprietarie di Android hanno annessa una "
"backdoor</a> che fornisce accesso remoto ai file contenuti nel dispositivo."
+#. type: Content of: <ul><li><p>
# | The Amazon [-Kindle-] {+Kindle-Swindle+} has a back door that has been
# | used to <a
# |
href=\"http://pogue.blogs.nytimes.com/2009/07/17/some-e-books-are-more-equal-than-others/\";>
# | remotely erase books</a>. {+One of the books erased was 1984, by George
# | Orwell.+}
-#. type: Content of: <ul><li><p>
#, fuzzy
#| msgid ""
#| "The Amazon Kindle has a back door that has been used to <a href=\"http://";
@@ -576,10 +576,10 @@
"her kafkaesque “explanations.”"
msgstr ""
+#. type: Content of: <ul><li><p>
# | The [-Kindle-] {+Kindle-Swindle+} also has a <a
# |
href=\"http://www.amazon.com/gp/help/customer/display.html?nodeId=200774090\";>
# | universal back door</a>.
-#. type: Content of: <ul><li><p>
#, fuzzy
#| msgid ""
#| "The Kindle also has a <a href=\"http://www.amazon.com/gp/help/customer/";
@@ -737,8 +737,8 @@
"<a href=\"/server/standards/README.translations.html\">Guida alle "
"traduzioni</a>."
-# | Copyright © 2014-201[-6-]{+7+} Free Software Foundation, Inc.
#. type: Content of: <div><p>
+# | Copyright © 2014-201[-6-]{+7+} Free Software Foundation, Inc.
#, fuzzy
#| msgid "Copyright © 2014-2016 Free Software Foundation, Inc."
msgid "Copyright © 2014-2017 Free Software Foundation, Inc."
Index: proprietary/po/proprietary-censorship.it-diff.html
===================================================================
RCS file: /web/www/www/proprietary/po/proprietary-censorship.it-diff.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- proprietary/po/proprietary-censorship.it-diff.html 26 Mar 2017 03:59:48
-0000 1.1
+++ proprietary/po/proprietary-censorship.it-diff.html 26 Mar 2017 19:00:34
-0000 1.2
@@ -175,7 +175,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2017/03/26 03:59:48 $
+$Date: 2017/03/26 19:00:34 $
<!-- timestamp end -->
</p>
</div>
Index: proprietary/po/proprietary-censorship.it.po
===================================================================
RCS file: /web/www/www/proprietary/po/proprietary-censorship.it.po,v
retrieving revision 1.35
retrieving revision 1.36
diff -u -b -r1.35 -r1.36
--- proprietary/po/proprietary-censorship.it.po 26 Mar 2017 13:57:52 -0000
1.35
+++ proprietary/po/proprietary-censorship.it.po 26 Mar 2017 19:00:34 -0000
1.36
@@ -246,9 +246,9 @@
"<a href=\"/server/standards/README.translations.html\">Guida alle "
"traduzioni</a>."
+#. type: Content of: <div><p>
# | Copyright © 2014, 2015, [-2016-] {+2016, 2017+} Free Software
# | Foundation, Inc.
-#. type: Content of: <div><p>
#, fuzzy
#| msgid "Copyright © 2014, 2015, 2016 Free Software Foundation, Inc."
msgid "Copyright © 2014, 2015, 2016, 2017 Free Software Foundation, Inc."
Index: proprietary/po/proprietary-drm.it-diff.html
===================================================================
RCS file: /web/www/www/proprietary/po/proprietary-drm.it-diff.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- proprietary/po/proprietary-drm.it-diff.html 5 Mar 2017 13:59:49 -0000
1.4
+++ proprietary/po/proprietary-drm.it-diff.html 26 Mar 2017 19:00:34 -0000
1.5
@@ -239,7 +239,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2017/03/05 13:59:49 $
+$Date: 2017/03/26 19:00:34 $
<!-- timestamp end -->
</p>
</div>
Index: proprietary/po/proprietary-drm.it.po
===================================================================
RCS file: /web/www/www/proprietary/po/proprietary-drm.it.po,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -b -r1.25 -r1.26
--- proprietary/po/proprietary-drm.it.po 26 Mar 2017 13:57:52 -0000
1.25
+++ proprietary/po/proprietary-drm.it.po 26 Mar 2017 19:00:34 -0000
1.26
@@ -371,8 +371,8 @@
"<a href=\"/server/standards/README.translations.html\">Guida alle "
"traduzioni</a>."
-# || No change detected. The change might only be in amounts of spaces.
#. type: Content of: <div><p>
+# || No change detected. The change might only be in amounts of spaces.
#, fuzzy
#| msgid ""
#| "Copyright © 2014, 2015, 2016, 2017 Free Software Foundation, Inc."
Index: proprietary/po/proprietary-insecurity.it.po
===================================================================
RCS file: /web/www/www/proprietary/po/proprietary-insecurity.it.po,v
retrieving revision 1.83
retrieving revision 1.84
diff -u -b -r1.83 -r1.84
--- proprietary/po/proprietary-insecurity.it.po 26 Mar 2017 13:57:52 -0000
1.83
+++ proprietary/po/proprietary-insecurity.it.po 26 Mar 2017 19:00:34 -0000
1.84
@@ -665,9 +665,9 @@
"<a href=\"/server/standards/README.translations.html\">Guida alle "
"traduzioni</a>."
+#. type: Content of: <div><p>
# | Copyright © 201[-4-]{+3+}, 2015, 2016, 2017 Free Software Foundation,
# | Inc.
-#. type: Content of: <div><p>
#, fuzzy
#| msgid ""
#| "Copyright © 2014, 2015, 2016, 2017 Free Software Foundation, Inc."
Index: proprietary/po/proprietary-sabotage.it-diff.html
===================================================================
RCS file: /web/www/www/proprietary/po/proprietary-sabotage.it-diff.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- proprietary/po/proprietary-sabotage.it-diff.html 21 Mar 2017 03:01:54
-0000 1.3
+++ proprietary/po/proprietary-sabotage.it-diff.html 26 Mar 2017 19:00:34
-0000 1.4
@@ -319,7 +319,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2017/03/21 03:01:54 $
+$Date: 2017/03/26 19:00:34 $
<!-- timestamp end -->
</p>
</div>
Index: proprietary/po/proprietary-sabotage.it.po
===================================================================
RCS file: /web/www/www/proprietary/po/proprietary-sabotage.it.po,v
retrieving revision 1.67
retrieving revision 1.68
diff -u -b -r1.67 -r1.68
--- proprietary/po/proprietary-sabotage.it.po 26 Mar 2017 13:57:52 -0000
1.67
+++ proprietary/po/proprietary-sabotage.it.po 26 Mar 2017 19:00:34 -0000
1.68
@@ -566,9 +566,9 @@
"<a href=\"/server/standards/README.translations.html\">Guida alle "
"traduzioni</a>."
+#. type: Content of: <div><p>
# | Copyright © 201[-4-]{+3+}, 2015, 2016, 2017 Free Software Foundation,
# | Inc.
-#. type: Content of: <div><p>
#, fuzzy
#| msgid ""
#| "Copyright © 2014, 2015, 2016, 2017 Free Software Foundation, Inc."
Index: proprietary/po/proprietary-surveillance.it-diff.html
===================================================================
RCS file: /web/www/www/proprietary/po/proprietary-surveillance.it-diff.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- proprietary/po/proprietary-surveillance.it-diff.html 18 Mar 2017
16:30:13 -0000 1.16
+++ proprietary/po/proprietary-surveillance.it-diff.html 26 Mar 2017
19:00:34 -0000 1.17
@@ -1248,7 +1248,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2017/03/18 16:30:13 $
+$Date: 2017/03/26 19:00:34 $
<!-- timestamp end -->
</p>
</div>
Index: proprietary/po/proprietary-surveillance.it.po
===================================================================
RCS file: /web/www/www/proprietary/po/proprietary-surveillance.it.po,v
retrieving revision 1.144
retrieving revision 1.145
diff -u -b -r1.144 -r1.145
--- proprietary/po/proprietary-surveillance.it.po 26 Mar 2017 13:57:52
-0000 1.144
+++ proprietary/po/proprietary-surveillance.it.po 26 Mar 2017 19:00:34
-0000 1.145
@@ -188,9 +188,9 @@
msgid "<a href=\"#SpywareEverywhere\">Spyware Everywhere</a>"
msgstr "<a href=\"#SpywareEverywhere\">Spyware dappertutto</a>"
+#. type: Content of: <div><div><ul><li>
# | <a [-href=\"#SpywareInToys\">Spyware in Toys</a>-]
# | {+href=\"#SpywareInVR\">Spyware In VR</a>+}
-#. type: Content of: <div><div><ul><li>
#, fuzzy
#| msgid "<a href=\"#SpywareInToys\">Spyware in Toys</a>"
msgid "<a href=\"#SpywareInVR\">Spyware In VR</a>"
@@ -788,10 +788,10 @@
"a>) senza dare un indirizzo e-mail valido e convalidarlo tramite un codice "
"che Apple invia a tale indirizzo."
+#. type: Content of: <ul><li><p>
# | Around 47% of the most popular iOS apps <a {+class=\"not-a-duplicate\"+}
# | href=\"http://jots.pub/a/2015103001/index.php\";>share personal, behavioral
# | and location information</a> of their users with third parties.
-#. type: Content of: <ul><li><p>
#, fuzzy
#| msgid ""
#| "Around 47% of the most popular iOS apps <a href=\"http://jots.pub/";
@@ -864,11 +864,11 @@
"la NSA ha accesso a tutto tramite <a href=\"/philosophy/surveillance-vs-"
"democracy.html#digitalcash\">PRISM</a>."
+#. type: Content of: <ul><li><p>
# | Spyware in iThings: the <a {+class=\"not-a-duplicate\"+}
# |
href=\"http://finance.yahoo.com/blogs/the-exchange/privacy-advocates-worry-over-new-apple-iphone-tracking-feature-161836223.html\";>
# | iBeacon</a> lets stores determine exactly where the iThing is, and get
# | other info too.
-#. type: Content of: <ul><li><p>
#, fuzzy
#| msgid ""
#| "Spyware in iThings: the <a href=\"http://finance.yahoo.com/blogs/the-";
@@ -1319,11 +1319,11 @@
"<span class=\"anchor-reference-id\">(<a href=\"#SpywareInToys"
"\">#SpywareInToys</a>)</span>"
+#. type: Content of: <ul><li><p>
# | A computerized vibrator <a
# |
[-href=\"https://www.theguardian.com/technology/2016/aug/10/vibrator-phone-app-we-vibe-4-plus-bluetooth-hack\";>snoops-]
# |
{+href=\"https://www.theguardian.com/technology/2016/aug/10/vibrator-phone-app-we-vibe-4-plus-bluetooth-hack\";>
# | was snooping+} on its users through the proprietary control app</a>.
-#. type: Content of: <ul><li><p>
#, fuzzy
#| msgid ""
#| "A computerized vibrator <a href=\"https://www.theguardian.com/";
@@ -1338,10 +1338,10 @@
"technology/2016/aug/10/vibrator-phone-app-we-vibe-4-plus-bluetooth-hack"
"\">spia gli utenti attraverso l'applicazione che lo controlla</a>."
+#. type: Content of: <ul><li><p>
# | The app [-reports-] {+was reporting+} the temperature of the vibrator
# | minute by minute (thus, indirectly, whether it [-is-] {+was+} surrounded
# | by a person's body), [-and-] {+as well as+} the vibration frequency.
-#. type: Content of: <ul><li><p>
#, fuzzy
#| msgid ""
#| "The app reports the temperature of the vibrator minute by minute (thus, "
@@ -1356,11 +1356,11 @@
"sapere se l'oggetto è all'interno di un corpo umano) e la frequenza di "
"vibrazione."
+#. type: Content of: <ul><li><p>
# | Note the totally inadequate proposed response: a labeling standard with
# | which manufacturers would make statements about their products, rather
# | than free software which users [-can check-] {+could have checked+} and
# | change{+d+}.
-#. type: Content of: <ul><li><p>
#, fuzzy
#| msgid ""
#| "Note the totally inadequate proposed response: a labeling standard with "
@@ -1375,6 +1375,7 @@
"che impegni i produttori a dare garanzie sui loro prodotti invece che "
"consigliare l'utilizzo di software libero."
+#. type: Content of: <ul><li><p>
# | [-A-]{+The+} company that [-makes internet-controlled vibrators-] {+made
# | the vibrator+} <a
# |
[-href=\"https://www.theguardian.com/us-news/2016/sep/14/wevibe-sex-toy-data-collection-chicago-lawsuit\";>is
@@ -1382,7 +1383,6 @@
# |
{+href=\"https://www.theguardian.com/us-news/2016/sep/14/wevibe-sex-toy-data-collection-chicago-lawsuit\";>
# | was+} sued for collecting lots of personal information about how people
# | use{+d+} it</a>.
-#. type: Content of: <ul><li><p>
#, fuzzy
#| msgid ""
#| "A company that makes internet-controlled vibrators <a href=\"https://www.";
@@ -1399,11 +1399,11 @@
"chicago-lawsuit\">è stata portata in tribunale per la raccolta di molte "
"informazioni personali su come gli utenti usano il prodotto</a>."
+#. type: Content of: <ul><li><p>
# | The company's statement that it [-anonymizes-] {+was anonymizing+} the
# | data may be true, but it doesn't really matter. If it [-sells-] {+had
# | sold+} the data to a data broker, the data broker [-can-] {+would have
# | been able to+} figure out who the user [-is.-] {+was.+}
-#. type: Content of: <ul><li><p>
#, fuzzy
#| msgid ""
#| "The company's statement that it anonymizes the data may be true, but it "
@@ -1442,10 +1442,10 @@
"unacceptable by itself."
msgstr ""
+#. type: Content of: <ul><li><p>
# | Barbie <a
# |
href=\"http://www.mirror.co.uk/news/technology-science/technology/wi-fi-spy-barbie-records-childrens-5177673\";>is
# | going to spy on children and adults[-.-]</a>.
-#. type: Content of: <ul><li><p>
#, fuzzy
#| msgid ""
#| "Barbie <a href=\"http://www.mirror.co.uk/news/technology-science/";
@@ -2299,17 +2299,17 @@
"dispositivi Intel potranno ascoltare i discorsi sempre, anche quando saranno "
"apparentemente spenti</a>."
-# | Spyware [-in Toys-] {+In VR+}
#. type: Content of: <div><h3>
+# | Spyware [-in Toys-] {+In VR+}
#, fuzzy
#| msgid "Spyware in Toys"
msgid "Spyware In VR"
msgstr "Spyware nei giocattoli"
+#. type: Content of: <div>
# | <span class=\"anchor-reference-id\">(<a
# | [-href=\"#SpywareInTVSets\">#SpywareInTVSets</a>)</span>-]
# | {+href=\"#SpywareInVR\">#SpywareInVR</a>)</span>+}
-#. type: Content of: <div>
#, fuzzy
#| msgid ""
#| "<span class=\"anchor-reference-id\">(<a href=\"#SpywareInTVSets"
@@ -2383,9 +2383,9 @@
"<a href=\"/server/standards/README.translations.html\">Guida alle "
"traduzioni</a>."
+#. type: Content of: <div><p>
# | Copyright © [-2014,-] 2015, [-2016-] {+2016, 2017+} Free Software
# | Foundation, Inc.
-#. type: Content of: <div><p>
#, fuzzy
#| msgid "Copyright © 2014, 2015, 2016 Free Software Foundation, Inc."
msgid "Copyright © 2015, 2016, 2017 Free Software Foundation, Inc."
Index: proprietary/po/proprietary-tyrants.it-diff.html
===================================================================
RCS file: /web/www/www/proprietary/po/proprietary-tyrants.it-diff.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- proprietary/po/proprietary-tyrants.it-diff.html 5 Mar 2017 13:59:50
-0000 1.2
+++ proprietary/po/proprietary-tyrants.it-diff.html 26 Mar 2017 19:00:34
-0000 1.3
@@ -158,7 +158,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2017/03/05 13:59:50 $
+$Date: 2017/03/26 19:00:34 $
<!-- timestamp end -->
</p>
</div>
Index: proprietary/po/proprietary-tyrants.it.po
===================================================================
RCS file: /web/www/www/proprietary/po/proprietary-tyrants.it.po,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -b -r1.29 -r1.30
--- proprietary/po/proprietary-tyrants.it.po 26 Mar 2017 13:57:52 -0000
1.29
+++ proprietary/po/proprietary-tyrants.it.po 26 Mar 2017 19:00:34 -0000
1.30
@@ -69,6 +69,7 @@
"\">are tyrants</a>."
msgstr ""
+#. type: Content of: <ul><li>
# | <a
# |
href=\"http://wiki.samygo.tv/index.php5/SamyGO_for_DUMMIES#What_are_Restricted_Firmwares.3F\";>
# | Samsung “Smart” TVs have turned Linux into the base for a
@@ -76,7 +77,6 @@
# | that Linux is released under GNU GPL version 2, <a
# | href=\"/licenses/rms-why-gplv3.html\">not version 3</a>, together with a
# | we[-e-]{+a+}k interpretation of GPL version 2.
-#. type: Content of: <ul><li>
#, fuzzy
#| msgid ""
#| "<a href=\"http://wiki.samygo.tv/index.php5/";
@@ -155,6 +155,7 @@
"<a href=\"http://soylentnews.org/article.pl?sid=14/03/15/1912255\";>I "
"processori Intel avranno del software tiranno preinstallato</a>."
+#. type: Content of: <ul><li><p>
# | Microsoft accidentally left a way for users to install GNU/Linux on
# | Windows RT tablets, but now it has <a
# |
href=\"http://www.securitynewspaper.com/2016/07/15/microsoft-silently-kills-dev-backdoor-boots-linux-locked-windows-rt-slabs/\";>
@@ -163,7 +164,6 @@
# | the users. The article talks of installing “Linux”, but the
# | context shows it is really <a
# | href=\"/gnu/linux-and-gnu.html\">GNU/Linux</a> that users install.
-#. type: Content of: <ul><li><p>
#, fuzzy
#| msgid ""
#| "Microsoft accidentally left a way for users to install GNU/Linux on "
@@ -237,9 +237,9 @@
"<a href=\"/server/standards/README.translations.html\">Guida alle "
"traduzioni</a>."
+#. type: Content of: <div><p>
# | Copyright © 2014, 2015, [-2016-] {+2016, 2017+} Free Software
# | Foundation, Inc.
-#. type: Content of: <div><p>
#, fuzzy
#| msgid "Copyright © 2014, 2015, 2016 Free Software Foundation, Inc."
msgid "Copyright © 2014, 2015, 2016, 2017 Free Software Foundation, Inc."
Index: proprietary/po/proprietary.it-diff.html
===================================================================
RCS file: /web/www/www/proprietary/po/proprietary.it-diff.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- proprietary/po/proprietary.it-diff.html 18 Mar 2017 13:00:18 -0000
1.2
+++ proprietary/po/proprietary.it-diff.html 26 Mar 2017 19:00:34 -0000
1.3
@@ -171,7 +171,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2017/03/18 13:00:18 $
+$Date: 2017/03/26 19:00:34 $
<!-- timestamp end -->
</p>
</div>
Index: proprietary/po/proprietary.it.po
===================================================================
RCS file: /web/www/www/proprietary/po/proprietary.it.po,v
retrieving revision 1.37
retrieving revision 1.38
diff -u -b -r1.37 -r1.38
--- proprietary/po/proprietary.it.po 26 Mar 2017 13:57:52 -0000 1.37
+++ proprietary/po/proprietary.it.po 26 Mar 2017 19:00:34 -0000 1.38
@@ -24,8 +24,6 @@
#
#
-# | div.companies { float: right; margin-bottom: .5em; }\\ndiv.malfunctions {
-# | max-width: 27em; [-}\\n\\n-] {+}\\n+}
#. div.toc h3 {
#. text-align: left;
#. font-size: 1.2em;
@@ -35,6 +33,8 @@
#. div.toc li { list-style: none; margin-bottom: 1em; }
#. div.toc { margin-top: 1em; }
#. type: Content of: <style>
+# | div.companies { float: right; margin-bottom: .5em; }\\ndiv.malfunctions {
+# | max-width: 27em; [-}\\n\\n-] {+}\\n+}
#, fuzzy, no-wrap
#| msgid ""
#| "div.companies { float: right; margin-bottom: .5em; }\n"
@@ -106,8 +106,8 @@
"know about."
msgstr ""
-# | [-<strong>Company-]{+Company+} or type of [-product</strong>-] {+product+}
#. type: Content of: <div><div><h3>
+# | [-<strong>Company-]{+Company+} or type of [-product</strong>-] {+product+}
#, fuzzy
#| msgid "<strong>Company or type of product</strong>"
msgid "Company or type of product"
@@ -126,9 +126,9 @@
msgid "<a href=\"/proprietary/malware-adobe.html\">Adobe Malware</a>"
msgstr "<a href=\"/proprietary/malware-adobe.html\">Malware di Adobe</a>"
+#. type: Content of: <div><div><ul><li>
# | <a [-href=\"/proprietary/malware-adobe.html\">Adobe-]
# | {+href=\"/proprietary/malware-amazon.html\">Amazon+} Malware</a>
-#. type: Content of: <div><div><ul><li>
#, fuzzy
#| msgid "<a href=\"/proprietary/malware-adobe.html\">Adobe Malware</a>"
msgid "<a href=\"/proprietary/malware-amazon.html\">Amazon Malware</a>"
@@ -152,8 +152,8 @@
"<a href=\"/proprietary/malware-appliances.html\">Malware negli "
"elettrodomestici</a>"
-# | [-<strong>Type of malware</strong>-]{+Type of malware+}
#. type: Content of: <div><div><h3>
+# | [-<strong>Type of malware</strong>-]{+Type of malware+}
#, fuzzy
#| msgid "<strong>Type of malware</strong>"
msgid "Type of malware"
@@ -167,9 +167,9 @@
msgid "<a href=\"/proprietary/proprietary-censorship.html\">Censorship</a>"
msgstr "<a href=\"/proprietary/proprietary-censorship.html\">Censura</a>"
+#. type: Content of: <div><div><ul><li>
# | <a [-href=\"/proprietary/proprietary-censorship.html\">Censorship</a>-]
# | {+href=\"/proprietary/proprietary-coverups.html\">Coverups</a>+}
-#. type: Content of: <div><div><ul><li>
#, fuzzy
#| msgid "<a href=\"/proprietary/proprietary-censorship.html\">Censorship</a>"
msgid "<a href=\"/proprietary/proprietary-coverups.html\">Coverups</a>"
@@ -299,9 +299,9 @@
"<a href=\"/server/standards/README.translations.html\">Guida alle "
"traduzioni</a>."
+#. type: Content of: <div><p>
# | Copyright © 2013, 2014, 2015, [-2016-] {+2016, 2017+} Free Software
# | Foundation, Inc.
-#. type: Content of: <div><p>
#, fuzzy
#| msgid ""
#| "Copyright © 2013, 2014, 2015, 2016 Free Software Foundation, Inc."
Index: server/po/sitemap.it-en.html
===================================================================
RCS file: /web/www/www/server/po/sitemap.it-en.html,v
retrieving revision 1.38
retrieving revision 1.39
diff -u -b -r1.38 -r1.39
--- server/po/sitemap.it-en.html 5 Mar 2017 13:59:50 -0000 1.38
+++ server/po/sitemap.it-en.html 26 Mar 2017 19:00:34 -0000 1.39
@@ -1623,6 +1623,8 @@
<dd>Malware in Appliances</dd>
<dt><a href="/proprietary/malware-games.html">malware-games.html</a></dt>
<dd>Malware in Games</dd>
+ <dt><a href="/proprietary/malware-google.html">malware-google.html</a></dt>
+ <dd>Google's Software is Malware</dd>
<dt><a
href="/proprietary/malware-microsoft.html">malware-microsoft.html</a></dt>
<dd>Microsoft's Software is Malware</dd>
<dt><a href="/proprietary/malware-mobiles.html">malware-mobiles.html</a></dt>
@@ -1946,7 +1948,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2017/03/05 13:59:50 $
+$Date: 2017/03/26 19:00:34 $
<!-- timestamp end -->
</p>
</div>
Index: server/po/sitemap.it.po
===================================================================
RCS file: /web/www/www/server/po/sitemap.it.po,v
retrieving revision 1.130
retrieving revision 1.131
diff -u -b -r1.130 -r1.131
--- server/po/sitemap.it.po 26 Mar 2017 13:57:51 -0000 1.130
+++ server/po/sitemap.it.po 26 Mar 2017 19:00:34 -0000 1.131
@@ -14,7 +14,6 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-"X-Outdated-Since: 2017-03-08 17:57+0000\n"
"X-Generator: Poedit 1.5.4\n"
#. type: Content of: <title>
@@ -5637,9 +5636,7 @@
msgid "<a href=\"/proprietary/malware-google.html\">malware-google.html</a>"
msgstr "<a href=\"/proprietary/malware-google.html\">malware-google.html</a>"
-# | [-Adobe's-]{+Google's+} Software is Malware
#. type: Content of: <div><dl><dd><dl><dd>
-#| msgid "Adobe's Software is Malware"
msgid "Google's Software is Malware"
msgstr "Google's Software is Malware"
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- www licenses/gpl-faq.it.html licenses/gpl-viola...,
GNUN <=