[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www licenses/old-licenses/po/gpl-2.0-faq.de.po ...
|
From: |
GNUN |
|
Subject: |
www licenses/old-licenses/po/gpl-2.0-faq.de.po ... |
|
Date: |
Fri, 10 Mar 2017 14:30:54 -0500 (EST) |
CVSROOT: /web/www
Module name: www
Changes by: GNUN <gnun> 17/03/10 14:30:53
Modified files:
licenses/old-licenses/po: gpl-2.0-faq.de.po gpl-2.0-faq.es.po
gpl-2.0-faq.fr.po gpl-2.0-faq.it.po
gpl-2.0-faq.ja.po gpl-2.0-faq.pot
gpl-2.0-faq.ru.po
licenses/po : gpl-faq.es.po gpl-faq.fr.po gpl-faq.it.po
gpl-faq.ja.po gpl-faq.ru.po gpl-faq.ta.po
proprietary/po : malware-apple.de.po malware-apple.es.po
malware-apple.fr.po malware-apple.it.po
malware-apple.ja.po malware-apple.nl.po
malware-apple.pot malware-apple.ru.po
proprietary-surveillance.de.po
proprietary-surveillance.fr.po
proprietary-surveillance.it-diff.html
proprietary-surveillance.it.po
proprietary-surveillance.ja.po
proprietary-surveillance.pot
proprietary-surveillance.ru.po
Log message:
Automatic update by GNUnited Nations.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/old-licenses/po/gpl-2.0-faq.de.po?cvsroot=www&r1=1.63&r2=1.64
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/old-licenses/po/gpl-2.0-faq.es.po?cvsroot=www&r1=1.29&r2=1.30
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/old-licenses/po/gpl-2.0-faq.fr.po?cvsroot=www&r1=1.82&r2=1.83
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/old-licenses/po/gpl-2.0-faq.it.po?cvsroot=www&r1=1.35&r2=1.36
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/old-licenses/po/gpl-2.0-faq.ja.po?cvsroot=www&r1=1.35&r2=1.36
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/old-licenses/po/gpl-2.0-faq.pot?cvsroot=www&r1=1.24&r2=1.25
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/old-licenses/po/gpl-2.0-faq.ru.po?cvsroot=www&r1=1.42&r2=1.43
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gpl-faq.es.po?cvsroot=www&r1=1.76&r2=1.77
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gpl-faq.fr.po?cvsroot=www&r1=1.178&r2=1.179
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gpl-faq.it.po?cvsroot=www&r1=1.28&r2=1.29
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gpl-faq.ja.po?cvsroot=www&r1=1.79&r2=1.80
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gpl-faq.ru.po?cvsroot=www&r1=1.123&r2=1.124
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gpl-faq.ta.po?cvsroot=www&r1=1.63&r2=1.64
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/malware-apple.de.po?cvsroot=www&r1=1.65&r2=1.66
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/malware-apple.es.po?cvsroot=www&r1=1.65&r2=1.66
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/malware-apple.fr.po?cvsroot=www&r1=1.62&r2=1.63
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/malware-apple.it.po?cvsroot=www&r1=1.69&r2=1.70
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/malware-apple.ja.po?cvsroot=www&r1=1.63&r2=1.64
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/malware-apple.nl.po?cvsroot=www&r1=1.19&r2=1.20
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/malware-apple.pot?cvsroot=www&r1=1.31&r2=1.32
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/malware-apple.ru.po?cvsroot=www&r1=1.87&r2=1.88
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/proprietary-surveillance.de.po?cvsroot=www&r1=1.114&r2=1.115
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/proprietary-surveillance.fr.po?cvsroot=www&r1=1.146&r2=1.147
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/proprietary-surveillance.it-diff.html?cvsroot=www&r1=1.5&r2=1.6
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/proprietary-surveillance.it.po?cvsroot=www&r1=1.132&r2=1.133
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/proprietary-surveillance.ja.po?cvsroot=www&r1=1.127&r2=1.128
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/proprietary-surveillance.pot?cvsroot=www&r1=1.76&r2=1.77
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/proprietary-surveillance.ru.po?cvsroot=www&r1=1.184&r2=1.185
Patches:
Index: licenses/old-licenses/po/gpl-2.0-faq.de.po
===================================================================
RCS file: /web/www/www/licenses/old-licenses/po/gpl-2.0-faq.de.po,v
retrieving revision 1.63
retrieving revision 1.64
diff -u -b -r1.63 -r1.64
--- licenses/old-licenses/po/gpl-2.0-faq.de.po 17 Feb 2017 05:30:47 -0000
1.63
+++ licenses/old-licenses/po/gpl-2.0-faq.de.po 10 Mar 2017 19:30:51 -0000
1.64
@@ -7,7 +7,7 @@
msgstr ""
"Project-Id-Version: gpl-2.0-faq.html\n"
"Report-Msgid-Bugs-To: Webmasters <address@hidden>\n"
-"POT-Creation-Date: 2017-02-17 05:26+0000\n"
+"POT-Creation-Date: 2017-03-10 19:26+0000\n"
"PO-Revision-Date: 2016-08-09 22:00+0200\n"
"Last-Translator: Jоегg Kоhпе <joeko (AT) online [PUNKT] de>\n"
"Language-Team: Deutsch <www-de <address@hidden>\n"
@@ -855,6 +855,22 @@
"Lizenz für dieses Modul verwendet werden?</a>"
#. type: Content of: <ul><li>
+# | <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>
+#, fuzzy
+#| 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=\"#GPLPlugins\" name=\"TOCGPLPlugins\"> When are a program and its "
+"plug-ins considered a single combined program?</a>"
+msgstr ""
+"<a href=\"#GPLPluginsInNF\" id=\"TOCGPLPluginsInNF\">Kann die GPL angewendet "
+"werden, wenn ein Plug-in für ein unfreies Programm geschrieben wird?</a>"
+
+#. type: Content of: <ul><li>
msgid ""
"<a href=\"#GPLAndPlugins\" name=\"TOCGPLAndPlugins\">If a program released "
"under the GPL uses plug-ins, what are the requirements for the licenses of a "
@@ -2692,34 +2708,60 @@
"beseitigt."
#. type: Content of: <dl><dt>
+# | <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>+}
+#, fuzzy
+#| 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=\"#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>"
+"<b><a href=\"#TOCGPLPlugins\" name=\"GPLPlugins\"> When are a program and "
+"its plug-ins considered a single combined program? </a></b>"
msgstr ""
-"<b><a href=\"#TOCGPLAndPlugins\" id=\"GPLAndPlugins\">Wenn ein unter GPL "
-"freigegebenes Programm-Plug-ins verwendet, was sind die Voraussetzungen für "
-"die Lizenzen eines Plug-in?</a></b>"
+"<b><a href=\"#TOCGPLPluginsInNF\" id=\"GPLPluginsInNF\">Kann die GPL "
+"angewendet werden, wenn ein Plug-in für ein unfreies Programm geschrieben "
+"wird?</a></b>"
#. type: Content of: <dl><dd>
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 for the main program makes no requirements for them."
-msgstr ""
-"Das hängt davon ab, wie das Programm seine Plug-ins aufruft. Wenn das "
-"Programm <i>fork()</i> und <i>exec()</i> nutzt um Plug-ins aufzurufen, dann "
-"sind die Plug-ins separate Programme, so dass die Lizenz für das "
-"Hauptprogramm keinerlei Anforderungen für sie darstellt."
+"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."
+msgstr ""
#. 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."
+# | 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.+}
+#, fuzzy
+#| 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."
+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 "
+"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."
msgstr ""
"Wenn das Programm dynamisch-Plug-ins verbindet und sie gegenseitig "
"Funktionsaufrufe und Datenstrukturen teilen, nehmen wir an, dass sie ein "
@@ -2731,14 +2773,35 @@
#. type: Content of: <dl><dd><p>
msgid ""
-"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."
-msgstr ""
-"Wenn das Programm Plug-ins dynamisch verbindet, aber die Kommunikation "
-"zwischen beiden darauf beschränkt ist die <em>Haupt</em>funktion des Plug-"
-"ins mit einigen Optionen aufzurufen und auf die Rückgabe zu warten, ist das "
-"ein Grenzfall."
+"Using shared memory to communicate with complex data structures is pretty "
+"much equivalent to dynamic linking."
+msgstr ""
+
+#. type: Content of: <dl><dt>
+msgid ""
+"<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>"
+msgstr ""
+"<b><a href=\"#TOCGPLAndPlugins\" id=\"GPLAndPlugins\">Wenn ein unter GPL "
+"freigegebenes Programm-Plug-ins verwendet, was sind die Voraussetzungen für "
+"die Lizenzen eines Plug-in?</a></b>"
+
+#. type: Content of: <dl><dd>
+msgid ""
+"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 considered are separate works</a>."
+msgstr ""
+
+#. 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 "
+"software license and distribute it with source code in a GPL-compliant way. "
+"A main program that is a seperate from its plug-ins makes no requirements "
+"for the plug-ins."
+msgstr ""
#. type: Content of: <dl><dt>
msgid ""
@@ -2751,21 +2814,18 @@
#. type: Content of: <dl><dd>
msgid ""
-"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."
+"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>."
msgstr ""
#. 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."
+"If they form a single combined program this means that combination of the "
+"GPL-covered plug-in with the non-free main program would violate the GPL. "
+"However, you can resolve that legal problem by adding an exception to your "
+"plug-in's license, giving permission to link it with the non-free main "
+"program."
msgstr ""
#. type: Content of: <dl><dd><p>
@@ -2785,11 +2845,51 @@
"Programm freigegeben werden, dass entworfen wurde, um ein GPL lizenziertes "
"Plug-in zu laden?</a></b>"
-#. type: Content of: <dl><dd>
+#. type: Content of: <dl><dd><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-] {+combined
+# | program then+} 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.-] {+the main program is distributed for
+# | use with these plug-ins.+}
+#, fuzzy
+#| 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."
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."
+"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 that "
+"the terms of the GPL must be followed when the main program is distributed "
+"for use with these plug-ins."
+msgstr ""
+"Wenn das Programm dynamisch-Plug-ins verbindet und sie gegenseitig "
+"Funktionsaufrufe und Datenstrukturen teilen, nehmen wir an, dass sie ein "
+"einzelnes Programm bilden, das sowohl als verlängerter Arm des "
+"Hauptprogramms und des Plug-ins behandelt werden muss. Das bedeutet, dass "
+"die Plug-ins unter der GPL oder einer mit der GPL vereinbaren Lizenz "
+"freigegeben werden muss und das die Bedingungen der GPL beachtet werden "
+"müssen wenn diese Plug-ins verbreitet werden."
+
+#. type: Content of: <dl><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-]{+However, if they+}
+# | are separate [-programs, so-] {+works then+} the license of the plug-in
+# | makes no requirements about the main program.
+#, fuzzy
+#| 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."
+msgid ""
+"However, if they are separate works then the license of the plug-in makes no "
+"requirements about the main program."
msgstr ""
"Das hängt davon ab, wie das Programm seine Plug-ins aufruft. Sollte das "
"Programm <span class=\"teletype\">fork()</span> und <span class=\"teletype"
@@ -2797,17 +2897,6 @@
"separate Programme, demnach stellt die Lizenz des Plug-ins keine Bedingungen "
"über das Hauptprogramm."
-#. 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."
-msgstr ""
-
#. type: Content of: <dl><dt>
msgid ""
"<b><a href=\"#TOCLinkingWithGPL\" name=\"LinkingWithGPL\">You have a GPL'ed "
@@ -3178,7 +3267,7 @@
"<b><a href=\"#TOCLGPLJava\" id=\"LGPLJava\">Wie funktioniert die LGPL mit "
"Java?</a></b>"
-#. type: Content of: <dl><dd><p>
+#. type: Content of: <dl><dd>
msgid ""
"<a href=\"/licenses/lgpl-java.html\">See this article for details.</a> It "
"works as designed, intended, and expected."
@@ -3292,7 +3381,7 @@
"permissiven Lizenz (wie der X11-Lizenz) zwischen dem GPL unterliegenden und "
"dem proprietären Teil stellt?</a></b>"
-#. type: Content of: <dl><dd><p>
+#. type: Content of: <dl><dd>
msgid ""
"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 "
@@ -3316,7 +3405,7 @@
"<b><a href=\"#TOCLibGCCException\" id=\"LibGCCException\">Erlaubt die "
"libstdc-Ausnahme die dynamische Verbindung?</a></b>"
-#. type: Content of: <dl><dd><p>
+#. type: Content of: <dl><dd>
msgid ""
"Yes. The intent of the exception is to allow people to compile proprietary "
"software using gcc."
@@ -4791,6 +4880,28 @@
msgid "Updated:"
msgstr "Letzte Ãnderung:"
+#~ 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 for the main program makes no requirements for "
+#~ "them."
+#~ msgstr ""
+#~ "Das hängt davon ab, wie das Programm seine Plug-ins aufruft. Wenn das "
+#~ "Programm <i>fork()</i> und <i>exec()</i> nutzt um Plug-ins aufzurufen, "
+#~ "dann sind die Plug-ins separate Programme, so dass die Lizenz für das "
+#~ "Hauptprogramm keinerlei Anforderungen für sie darstellt."
+
+#~ msgid ""
+#~ "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."
+#~ msgstr ""
+#~ "Wenn das Programm Plug-ins dynamisch verbindet, aber die Kommunikation "
+#~ "zwischen beiden darauf beschränkt ist die <em>Haupt</em>funktion des
Plug-"
+#~ "ins mit einigen Optionen aufzurufen und auf die Rückgabe zu warten, ist "
+#~ "das ein Grenzfall."
+
#~ msgid "Yes, because the program as it is actually run includes the library."
#~ msgstr ""
#~ "Ja, denn das Programm, so wie es tatsächlich ausgeführt wird, enthält
die "
Index: licenses/old-licenses/po/gpl-2.0-faq.es.po
===================================================================
RCS file: /web/www/www/licenses/old-licenses/po/gpl-2.0-faq.es.po,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -b -r1.29 -r1.30
--- licenses/old-licenses/po/gpl-2.0-faq.es.po 21 Feb 2017 10:59:40 -0000
1.29
+++ licenses/old-licenses/po/gpl-2.0-faq.es.po 10 Mar 2017 19:30:51 -0000
1.30
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: gpl-2.0-faq.html\n"
-"POT-Creation-Date: 2017-02-17 05:26+0000\n"
+"POT-Creation-Date: 2017-03-10 19:26+0000\n"
"PO-Revision-Date: 2017-02-21 11:06+0100\n"
"Last-Translator: Javier Fdez. Retenaga <address@hidden>\n"
"Language-Team: Spanish <address@hidden>\n"
@@ -15,6 +15,7 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"X-Outdated-Since: 2017-03-10 19:26+0000\n"
"Plural-Forms: nplurals=2; plural=(n!=1);\n"
"X-Generator: Poedit 1.6.10\n"
@@ -842,6 +843,22 @@
"licencia para mi módulo?</a>"
#. type: Content of: <ul><li>
+# | <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>
+#, fuzzy
+#| 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=\"#GPLPlugins\" name=\"TOCGPLPlugins\"> When are a program and its "
+"plug-ins considered a single combined program?</a>"
+msgstr ""
+"<a href=\"#GPLPluginsInNF\" name=\"TOCGPLPluginsInNF\">¿Puedo utilizar la "
+"GPL al escribir un accesorio para un programa que no es libre?</a>"
+
+#. type: Content of: <ul><li>
msgid ""
"<a href=\"#GPLAndPlugins\" name=\"TOCGPLAndPlugins\">If a program released "
"under the GPL uses plug-ins, what are the requirements for the licenses of a "
@@ -2812,34 +2829,59 @@
"problema."
#. type: Content of: <dl><dt>
+# | <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>+}
+#, fuzzy
+#| 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=\"#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>"
+"<b><a href=\"#TOCGPLPlugins\" name=\"GPLPlugins\"> When are a program and "
+"its plug-ins considered a single combined program? </a></b>"
msgstr ""
-"<b><a href=\"#TOCGPLAndPlugins\" name=\"GPLAndPlugins\">Si un programa "
-"publicado bajo la GPL utiliza accesorios [<cite>plug-ins</cite>], ¿cuáles "
-"son los requisitos para las licencias de un accesorio?</a></b>"
+"<b><a href=\"#TOCGPLPluginsInNF\" name=\"GPLPluginsInNF\">¿Puedo utilizar la
"
+"GPL al escribir un accesorio para un programa que no es libre?</a></b>"
#. type: Content of: <dl><dd>
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 for the main program makes no requirements for them."
-msgstr ""
-"Depende de la manera en que el programa invoque sus accesorios. Si el "
-"programa utiliza <em>fork</em> y <em>exec</em> para invocar los accesorios, "
-"entonces los accesorios son programas separados, de modo que la licencia del "
-"programa principal no plantea ninguna exigencia con relación a ellos."
+"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."
+msgstr ""
#. 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."
+# | 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.+}
+#, fuzzy
+#| 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."
+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 "
+"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."
msgstr ""
"Si el programa enlaza dinámicamente con los accesorios, llama a funciones de
"
"estos y viceversa, y comparten estructuras de datos, consideramos que forman "
@@ -2851,13 +2893,35 @@
#. type: Content of: <dl><dd><p>
msgid ""
-"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."
-msgstr ""
-"Si el programa enlaza dinámicamente con los accesorios pero la comunicación
"
-"entre ellos se limita a invocar la función «principal» del accesorio con "
-"algunas opciones, y a esperar su respuesta, estaremos ante un caso lÃmite."
+"Using shared memory to communicate with complex data structures is pretty "
+"much equivalent to dynamic linking."
+msgstr ""
+
+#. type: Content of: <dl><dt>
+msgid ""
+"<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>"
+msgstr ""
+"<b><a href=\"#TOCGPLAndPlugins\" name=\"GPLAndPlugins\">Si un programa "
+"publicado bajo la GPL utiliza accesorios [<cite>plug-ins</cite>], ¿cuáles "
+"son los requisitos para las licencias de un accesorio?</a></b>"
+
+#. type: Content of: <dl><dd>
+msgid ""
+"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 considered are separate works</a>."
+msgstr ""
+
+#. 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 "
+"software license and distribute it with source code in a GPL-compliant way. "
+"A main program that is a seperate from its plug-ins makes no requirements "
+"for the plug-ins."
+msgstr ""
#. type: Content of: <dl><dt>
msgid ""
@@ -2869,26 +2933,35 @@
#. type: Content of: <dl><dd>
msgid ""
-"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."
-msgstr ""
-"Si el programa utiliza <i>fork</i> y <i>exec</i> para invocar los "
-"accesorios, entonces los accesorios son programas separados, de modo que la "
-"licencia del programa principal no plantea ninguna exigencia con respecto a "
-"ellos. De manera que puede utilizar la GPL para los accesorios, y no "
-"existen requisitos especiales."
+"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>."
+msgstr ""
#. 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."
+# | 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.
+#, fuzzy
+#| 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."
+msgid ""
+"If they form a single combined program this means that combination of the "
+"GPL-covered plug-in with the non-free main program would violate the GPL. "
+"However, you can resolve that legal problem by adding an exception to your "
+"plug-in's license, giving permission to link it with the non-free main "
+"program."
msgstr ""
"Si el programa enlaza dinámicamente con los accesorios, llama a funciones de
"
"estos y viceversa, y comparten estructuras de datos, consideramos que "
@@ -2916,23 +2989,26 @@
"un programa privativo que está diseñado para cargar un accesorio cubierto "
"por la GPL?</a></b>"
-#. type: Content of: <dl><dd>
-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."
-msgstr ""
-"Depende del modo en que el programa invoque su accesorio. Si el programa "
-"utiliza <i>fork</i> y <i>exec</i> para invocar los accesorios, entonces los "
-"accesorios son programas separados, de modo que la licencia del accesorio no "
-"plantea ninguna exigencia con relación al programa principal."
-
#. type: Content of: <dl><dd><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-]
+# | {+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.
+#, fuzzy
+#| 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."
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 "
+"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 that "
"the terms of the GPL must be followed when the main program is distributed "
"for use with these plug-ins."
@@ -2946,6 +3022,26 @@
"principal se distribuye para ser usado con esos accesorios, los términos de "
"la GPL deben ser respetados."
+#. type: Content of: <dl><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-]{+However, if they+}
+# | are separate [-programs, so-] {+works then+} the license of the plug-in
+# | makes no requirements about the main program.
+#, fuzzy
+#| 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."
+msgid ""
+"However, if they are separate works then the license of the plug-in makes no "
+"requirements about the main program."
+msgstr ""
+"Depende del modo en que el programa invoque su accesorio. Si el programa "
+"utiliza <i>fork</i> y <i>exec</i> para invocar los accesorios, entonces los "
+"accesorios son programas separados, de modo que la licencia del accesorio no "
+"plantea ninguna exigencia con relación al programa principal."
+
#. type: Content of: <dl><dt>
msgid ""
"<b><a href=\"#TOCLinkingWithGPL\" name=\"LinkingWithGPL\">You have a GPL'ed "
@@ -3362,7 +3458,7 @@
"<b><a href=\"#TOCLGPLJava\" name=\"LGPLJava\">¿Cómo funciona la LGPL con "
"Java?</a></b>"
-#. type: Content of: <dl><dd><p>
+#. type: Content of: <dl><dd>
msgid ""
"<a href=\"/licenses/lgpl-java.html\">See this article for details.</a> It "
"works as designed, intended, and expected."
@@ -3510,7 +3606,7 @@
"permisiva (como la licencia X11), entre la parte cubierta por la GPL y la "
"parte privativa?</a></b>"
-#. type: Content of: <dl><dd><p>
+#. type: Content of: <dl><dd>
msgid ""
"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 "
@@ -3543,7 +3639,7 @@
"<b><a href=\"#TOCLibGCCException\" name=\"LibGCCException\">¿La excepción
de "
"<i>libstdc++</i> permite los enlaces dinámicos?</a></b>"
-#. type: Content of: <dl><dd><p>
+#. type: Content of: <dl><dd>
msgid ""
"Yes. The intent of the exception is to allow people to compile proprietary "
"software using gcc."
@@ -5292,5 +5388,40 @@
msgid "Updated:"
msgstr "Ãltima actualización:"
+#~ 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 for the main program makes no requirements for "
+#~ "them."
+#~ msgstr ""
+#~ "Depende de la manera en que el programa invoque sus accesorios. Si el "
+#~ "programa utiliza <em>fork</em> y <em>exec</em> para invocar los "
+#~ "accesorios, entonces los accesorios son programas separados, de modo que "
+#~ "la licencia del programa principal no plantea ninguna exigencia con "
+#~ "relación a ellos."
+
+#~ msgid ""
+#~ "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."
+#~ msgstr ""
+#~ "Si el programa enlaza dinámicamente con los accesorios pero la "
+#~ "comunicación entre ellos se limita a invocar la función «principal»
del "
+#~ "accesorio con algunas opciones, y a esperar su respuesta, estaremos ante "
+#~ "un caso lÃmite."
+
+#~ msgid ""
+#~ "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."
+#~ msgstr ""
+#~ "Si el programa utiliza <i>fork</i> y <i>exec</i> para invocar los "
+#~ "accesorios, entonces los accesorios son programas separados, de modo que "
+#~ "la licencia del programa principal no plantea ninguna exigencia con "
+#~ "respecto a ellos. De manera que puede utilizar la GPL para los "
+#~ "accesorios, y no existen requisitos especiales."
+
#~ msgid "Yes, because the program as it is actually run includes the library."
#~ msgstr "SÃ, porque el programa utiliza la biblioteca en su funcionamiento."
Index: licenses/old-licenses/po/gpl-2.0-faq.fr.po
===================================================================
RCS file: /web/www/www/licenses/old-licenses/po/gpl-2.0-faq.fr.po,v
retrieving revision 1.82
retrieving revision 1.83
diff -u -b -r1.82 -r1.83
--- licenses/old-licenses/po/gpl-2.0-faq.fr.po 17 Feb 2017 12:00:24 -0000
1.82
+++ licenses/old-licenses/po/gpl-2.0-faq.fr.po 10 Mar 2017 19:30:51 -0000
1.83
@@ -9,7 +9,7 @@
msgid ""
msgstr ""
"Project-Id-Version: gpl-2.0-faq.html\n"
-"POT-Creation-Date: 2017-02-17 05:26+0000\n"
+"POT-Creation-Date: 2017-03-10 19:26+0000\n"
"PO-Revision-Date: 2017-02-17 12:34+0100\n"
"Last-Translator: Thérèse Godefroy <godef.th AT free.fr>\n"
"Language-Team: French <address@hidden>\n"
@@ -17,6 +17,7 @@
"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"
"Plural-Forms: \n"
"X-Generator: Gtranslator 2.91.5\n"
@@ -849,6 +850,22 @@
"pour mon module ?</a>"
#. type: Content of: <ul><li>
+# | <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>
+#, fuzzy
+#| 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=\"#GPLPlugins\" name=\"TOCGPLPlugins\"> When are a program and its "
+"plug-ins considered a single combined program?</a>"
+msgstr ""
+"<a href=\"#GPLPluginsInNF\" name=\"TOCGPLPluginsInNF\">Puis-je utiliser la "
+"GPL pour un greffon dans un programme non libre ?</a>"
+
+#. type: Content of: <ul><li>
msgid ""
"<a href=\"#GPLAndPlugins\" name=\"TOCGPLAndPlugins\">If a program released "
"under the GPL uses plug-ins, what are the requirements for the licenses of a "
@@ -2827,35 +2844,59 @@
"qui élimine le problème."
#. type: Content of: <dl><dt>
+# | <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>+}
+#, fuzzy
+#| 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=\"#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>"
+"<b><a href=\"#TOCGPLPlugins\" name=\"GPLPlugins\"> When are a program and "
+"its plug-ins considered a single combined program? </a></b>"
msgstr ""
-"<b><a href=\"#TOCGPLAndPlugins\" name=\"GPLAndPlugins\">Si j'écris un "
-"greffon pour un programme publié sous GPL, quelles contraintes cela
impose-t-"
-"il aux licences qu'il m'est possible d'utiliser pour distribuer mon greffonÂ
?"
-"</a></b>"
+"<b><a href=\"#TOCGPLPluginsInNF\" name=\"GPLPluginsInNF\">Puis-je utiliser "
+"la GPL pour un greffon dans un programme non libre ?</a></b>"
#. type: Content of: <dl><dd>
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 for the main program makes no requirements for them."
-msgstr ""
-"Cela dépend de la façon dont le programme invoque ses greffons. S'il
utilise "
-"<code>fork</code> et <code>exec</code> pour les invoquer, alors les greffons "
-"sont des programmes séparés, donc la licence du programme principal
n'impose "
-"aucune exigence les concernant."
+"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."
+msgstr ""
#. 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."
+# | 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.+}
+#, fuzzy
+#| 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."
+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 "
+"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."
msgstr ""
"Si le programme est lié dynamiquement avec les greffons, et qu'ils font des "
"appels de fonction mutuels et partagent des structures de données, nous "
@@ -2867,14 +2908,36 @@
#. type: Content of: <dl><dd><p>
msgid ""
-"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."
-msgstr ""
-"Si le programme est lié dynamiquement avec les greffons, mais que la "
-"communication entre eux se limite à invoquer la fonction « main » du
greffon "
-"avec quelques options puis à attendre que le greffon renvoie le résultat, "
-"nous nous trouvons dans un cas limite."
+"Using shared memory to communicate with complex data structures is pretty "
+"much equivalent to dynamic linking."
+msgstr ""
+
+#. type: Content of: <dl><dt>
+msgid ""
+"<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>"
+msgstr ""
+"<b><a href=\"#TOCGPLAndPlugins\" name=\"GPLAndPlugins\">Si j'écris un "
+"greffon pour un programme publié sous GPL, quelles contraintes cela
impose-t-"
+"il aux licences qu'il m'est possible d'utiliser pour distribuer mon greffonÂ
?"
+"</a></b>"
+
+#. type: Content of: <dl><dd>
+msgid ""
+"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 considered are separate works</a>."
+msgstr ""
+
+#. 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 "
+"software license and distribute it with source code in a GPL-compliant way. "
+"A main program that is a seperate from its plug-ins makes no requirements "
+"for the plug-ins."
+msgstr ""
#. type: Content of: <dl><dt>
msgid ""
@@ -2886,26 +2949,35 @@
#. type: Content of: <dl><dd>
msgid ""
-"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."
-msgstr ""
-"Si le programme utilise <code>fork</code> et <code>exec</code> pour invoquer "
-"les greffons, alors les greffons sont des programmes séparés, aussi la "
-"licence pour le programme principal n'impose aucune exigence les concernant. "
-"Vous pouvez donc utiliser la GPL pour un greffon, il n'y a pas d'exigence "
-"spéciale."
+"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>."
+msgstr ""
#. 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."
+# | 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.
+#, fuzzy
+#| 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."
+msgid ""
+"If they form a single combined program this means that combination of the "
+"GPL-covered plug-in with the non-free main program would violate the GPL. "
+"However, you can resolve that legal problem by adding an exception to your "
+"plug-in's license, giving permission to link it with the non-free main "
+"program."
msgstr ""
"Si le programme est lié dynamiquement avec les greffons, et qu'ils font des "
"appels de fonction mutuels et partagent des structures de données, nous "
@@ -2932,24 +3004,26 @@
"<b><a href=\"#TOCNFUseGPLPlugins\" name=\"NFUseGPLPlugins\">Puis-je faire un "
"programme non libre conçu pour charger un greffon régi par la GPLÂ
?</a></b>"
-#. type: Content of: <dl><dd>
-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."
-msgstr ""
-"Cela dépend de la façon dont le programme invoque ses greffons. Par
exemple, "
-"si le programme utilise <em>seulement</em> de simples instructions "
-"<code>fork</code> et <code>exec</code> pour invoquer les greffons et "
-"communiquer avec eux, alors ces derniers sont des programmes séparés, et la
"
-"licence du greffon n'a pas d'exigence concernant le programme principal."
-
#. type: Content of: <dl><dd><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-]
+# | {+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.
+#, fuzzy
+#| 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."
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 "
+"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 that "
"the terms of the GPL must be followed when the main program is distributed "
"for use with these plug-ins."
@@ -2963,6 +3037,27 @@
"de la GPL doivent être respectés quand le programme principal est
distribué "
"pour utiliser ces greffons."
+#. type: Content of: <dl><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-]{+However, if they+}
+# | are separate [-programs, so-] {+works then+} the license of the plug-in
+# | makes no requirements about the main program.
+#, fuzzy
+#| 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."
+msgid ""
+"However, if they are separate works then the license of the plug-in makes no "
+"requirements about the main program."
+msgstr ""
+"Cela dépend de la façon dont le programme invoque ses greffons. Par
exemple, "
+"si le programme utilise <em>seulement</em> de simples instructions "
+"<code>fork</code> et <code>exec</code> pour invoquer les greffons et "
+"communiquer avec eux, alors ces derniers sont des programmes séparés, et la
"
+"licence du greffon n'a pas d'exigence concernant le programme principal."
+
#. type: Content of: <dl><dt>
msgid ""
"<b><a href=\"#TOCLinkingWithGPL\" name=\"LinkingWithGPL\">You have a GPL'ed "
@@ -3385,7 +3480,7 @@
"<b><a href=\"#TOCLGPLJava\" name=\"LGPLJava\">Comment la LGPL fonctionne-t-"
"elle avec Java ?</a></b>"
-#. type: Content of: <dl><dd><p>
+#. type: Content of: <dl><dd>
msgid ""
"<a href=\"/licenses/lgpl-java.html\">See this article for details.</a> It "
"works as designed, intended, and expected."
@@ -3531,7 +3626,7 @@
"compatible avec la GPL (la licence X11, par exemple) entre la partie régie "
"par la GPL et la partie privatrice ?</a></b>"
-#. type: Content of: <dl><dd><p>
+#. type: Content of: <dl><dd>
msgid ""
"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 "
@@ -3564,7 +3659,7 @@
"<b><a href=\"#TOCLibGCCException\" name=\"LibGCCException\">Est-ce que "
"l'exception de libstdc++ permet les liaisons dynamiques ?</a></b>"
-#. type: Content of: <dl><dd><p>
+#. type: Content of: <dl><dd>
msgid ""
"Yes. The intent of the exception is to allow people to compile proprietary "
"software using gcc."
@@ -5359,3 +5454,37 @@
#. type: Content of: <div><p>
msgid "Updated:"
msgstr "Dernière mise à jour :"
+
+#~ 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 for the main program makes no requirements for "
+#~ "them."
+#~ msgstr ""
+#~ "Cela dépend de la façon dont le programme invoque ses greffons. S'il "
+#~ "utilise <code>fork</code> et <code>exec</code> pour les invoquer, alors "
+#~ "les greffons sont des programmes séparés, donc la licence du programme "
+#~ "principal n'impose aucune exigence les concernant."
+
+#~ msgid ""
+#~ "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."
+#~ msgstr ""
+#~ "Si le programme est lié dynamiquement avec les greffons, mais que la "
+#~ "communication entre eux se limite à invoquer la fonction « main » du "
+#~ "greffon avec quelques options puis à attendre que le greffon renvoie le "
+#~ "résultat, nous nous trouvons dans un cas limite."
+
+#~ msgid ""
+#~ "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."
+#~ msgstr ""
+#~ "Si le programme utilise <code>fork</code> et <code>exec</code> pour "
+#~ "invoquer les greffons, alors les greffons sont des programmes séparés, "
+#~ "aussi la licence pour le programme principal n'impose aucune exigence les "
+#~ "concernant. Vous pouvez donc utiliser la GPL pour un greffon, il n'y a "
+#~ "pas d'exigence spéciale."
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.35
retrieving revision 1.36
diff -u -b -r1.35 -r1.36
--- licenses/old-licenses/po/gpl-2.0-faq.it.po 5 Mar 2017 14:29:33 -0000
1.35
+++ licenses/old-licenses/po/gpl-2.0-faq.it.po 10 Mar 2017 19:30:51 -0000
1.36
@@ -8,7 +8,7 @@
msgid ""
msgstr ""
"Project-Id-Version: gpl-2.0-faq.html\n"
-"POT-Creation-Date: 2017-02-17 05:26+0000\n"
+"POT-Creation-Date: 2017-03-10 19:26+0000\n"
"PO-Revision-Date: 2017-03-05 14:23+0100\n"
"Last-Translator: Andrea Pescetti <address@hidden>\n"
"Language-Team: Italian\n"
@@ -16,6 +16,7 @@
"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>
@@ -842,6 +843,22 @@
"il mio modulo?</a>"
#. type: Content of: <ul><li>
+# | <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>
+#, fuzzy
+#| 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=\"#GPLPlugins\" name=\"TOCGPLPlugins\"> When are a program and its "
+"plug-ins considered a single combined program?</a>"
+msgstr ""
+"<a href=\"#GPLPluginsInNF\" name=\"TOCGPLPluginsInNF\">Posso usare la GPL "
+"per un plug-in destinato ad un programma non libero?</a>"
+
+#. type: Content of: <ul><li>
msgid ""
"<a href=\"#GPLAndPlugins\" name=\"TOCGPLAndPlugins\">If a program released "
"under the GPL uses plug-ins, what are the requirements for the licenses of a "
@@ -2836,34 +2853,59 @@
"problema."
#. type: Content of: <dl><dt>
+# | <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>+}
+#, fuzzy
+#| 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=\"#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>"
+"<b><a href=\"#TOCGPLPlugins\" name=\"GPLPlugins\"> When are a program and "
+"its plug-ins considered a single combined program? </a></b>"
msgstr ""
-"<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>"
+"<b><a href=\"#TOCGPLPluginsInNF\" name=\"GPLPluginsInNF\">Posso usare la GPL "
+"per un plug-in destinato ad un programma non libero?</a></b>"
#. type: Content of: <dl><dd>
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 for the main program makes no requirements for them."
+"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."
msgstr ""
-"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."
#. 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."
+# | 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.+}
+#, fuzzy
+#| 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."
+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 "
+"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."
msgstr ""
"Se il programma invece è collegato dinamicamente ai plug-in, ed essi "
"effettuano reciproche chiamate a funzione e condividono delle strutture "
@@ -2875,14 +2917,35 @@
#. type: Content of: <dl><dd><p>
msgid ""
-"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."
-msgstr ""
-"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."
+"Using shared memory to communicate with complex data structures is pretty "
+"much equivalent to dynamic linking."
+msgstr ""
+
+#. type: Content of: <dl><dt>
+msgid ""
+"<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>"
+msgstr ""
+"<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>"
+
+#. type: Content of: <dl><dd>
+msgid ""
+"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 considered are separate works</a>."
+msgstr ""
+
+#. 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 "
+"software license and distribute it with source code in a GPL-compliant way. "
+"A main program that is a seperate from its plug-ins makes no requirements "
+"for the plug-ins."
+msgstr ""
#. type: Content of: <dl><dt>
msgid ""
@@ -2894,26 +2957,35 @@
#. type: Content of: <dl><dd>
msgid ""
-"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."
-msgstr ""
-"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."
+"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>."
+msgstr ""
#. 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."
+# | 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.
+#, fuzzy
+#| 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."
+msgid ""
+"If they form a single combined program this means that combination of the "
+"GPL-covered plug-in with the non-free main program would violate the GPL. "
+"However, you can resolve that legal problem by adding an exception to your "
+"plug-in's license, giving permission to link it with the non-free main "
+"program."
msgstr ""
"Se invece il programma effettua un collegamento dinamico dei plug-in, ed "
"essi (il programma e i plug-in) effettuano delle reciproche chiamate a "
@@ -2942,23 +3014,26 @@
"un programma non libero che ha come scopo quello di caricare un plug-in "
"coperto da GPL?</a></b>"
-#. type: Content of: <dl><dd>
-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."
-msgstr ""
-"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."
-
#. type: Content of: <dl><dd><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-]
+# | {+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.
+#, fuzzy
+#| 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."
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 "
+"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 that "
"the terms of the GPL must be followed when the main program is distributed "
"for use with these plug-ins."
@@ -2972,6 +3047,26 @@
"quando si distribuisce il programma principale per l'utilizzo con questi "
"plug-in."
+#. type: Content of: <dl><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-]{+However, if they+}
+# | are separate [-programs, so-] {+works then+} the license of the plug-in
+# | makes no requirements about the main program.
+#, fuzzy
+#| 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."
+msgid ""
+"However, if they are separate works then the license of the plug-in makes no "
+"requirements about the main program."
+msgstr ""
+"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."
+
#. type: Content of: <dl><dt>
msgid ""
"<b><a href=\"#TOCLinkingWithGPL\" name=\"LinkingWithGPL\">You have a GPL'ed "
@@ -3384,7 +3479,7 @@
"<b><a href=\"#TOCLGPLJava\" name=\"LGPLJava\">Come funziona la LGPL nel caso "
"di Java?</a></b>"
-#. type: Content of: <dl><dd><p>
+#. type: Content of: <dl><dd>
msgid ""
"<a href=\"/licenses/lgpl-java.html\">See this article for details.</a> It "
"works as designed, intended, and expected."
@@ -3534,7 +3629,7 @@
"(come la licenza di X11) tra la parte coperta da GPL e la parte proprietaria?"
"</a></b>"
-#. type: Content of: <dl><dd><p>
+#. type: Content of: <dl><dd>
msgid ""
"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 "
@@ -3567,7 +3662,7 @@
"<b><a href=\"#TOCLibGCCException\" name=\"LibGCCException\"> L'eccezione "
"libstdc++ permette il linking dinamico?</a></b>"
-#. type: Content of: <dl><dd><p>
+#. type: Content of: <dl><dd>
msgid ""
"Yes. The intent of the exception is to allow people to compile proprietary "
"software using gcc."
@@ -5238,6 +5333,40 @@
msgid "Updated:"
msgstr "Ultimo aggiornamento:"
+#~ 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 for the main program makes no requirements for "
+#~ "them."
+#~ msgstr ""
+#~ "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."
+
+#~ msgid ""
+#~ "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."
+#~ msgstr ""
+#~ "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."
+
+#~ msgid ""
+#~ "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."
+#~ msgstr ""
+#~ "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."
+
#~ msgid "Yes, because the program as it is actually run includes the library."
#~ msgstr ""
#~ "Sì, perché il programma per come è effettivamente eseguito include
la "
Index: licenses/old-licenses/po/gpl-2.0-faq.ja.po
===================================================================
RCS file: /web/www/www/licenses/old-licenses/po/gpl-2.0-faq.ja.po,v
retrieving revision 1.35
retrieving revision 1.36
diff -u -b -r1.35 -r1.36
--- licenses/old-licenses/po/gpl-2.0-faq.ja.po 17 Feb 2017 05:30:47 -0000
1.35
+++ licenses/old-licenses/po/gpl-2.0-faq.ja.po 10 Mar 2017 19:30:51 -0000
1.36
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: gpl-2.0-faq.html\n"
-"POT-Creation-Date: 2017-02-17 05:26+0000\n"
+"POT-Creation-Date: 2017-03-10 19:26+0000\n"
"PO-Revision-Date: 2015-09-18 08:45+0900\n"
"Last-Translator: NIIBE Yutaka <address@hidden>\n"
"Language-Team: Japanese <address@hidden>\n"
@@ -823,6 +823,18 @@
"ã¦GPLãé©ç¨ããªããã°ãªãã¾ããã?</a>"
#. type: Content of: <ul><li>
+#, fuzzy
+#| 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=\"#GPLPlugins\" name=\"TOCGPLPlugins\"> When are a program and its "
+"plug-ins considered a single combined program?</a>"
+msgstr ""
+"<a href=\"#GPLPluginsInNF\"
name=\"TOCGPLPluginsInNF\">èªç±ã§ãªãããã°ã©ã å"
+"ãã®ãã©ã°ã¤ã³ã«GPLãé©ç¨ãããã¨ã¯ã§ãã¾ãã?</a>"
+
+#. type: Content of: <ul><li>
msgid ""
"<a href=\"#GPLAndPlugins\" name=\"TOCGPLAndPlugins\">If a program released "
"under the GPL uses plug-ins, what are the requirements for the licenses of a "
@@ -2771,33 +2783,45 @@
msgstr "æ¹è¨BSDã©ã¤ã»ã³ã¹ã«ã¯å®£ä¼æ¡é
ãããã¾ãããããåé¡ããªããªãã¾ããã"
#. type: Content of: <dl><dt>
+#, fuzzy
+#| 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=\"#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>"
+"<b><a href=\"#TOCGPLPlugins\" name=\"GPLPlugins\"> When are a program and "
+"its plug-ins considered a single combined program? </a></b>"
msgstr ""
-"<b><a href=\"#TOCGPLAndPlugins\"
name=\"GPLAndPlugins\">GPLã®ãã¨ã§ãªãªã¼ã¹ã"
-"ãã¦ããããã°ã©ã
ããã©ã°ã¤ã³ã使ãã¨ãã¦ããã©ã°ã¤ã³ã®ã©ã¤ã»ã³ã¹ã«ã¯ã©ã®ã"
-"ããªæ¡ä»¶ãããã¾ãã?</a></b>"
+"<b><a href=\"#TOCGPLPluginsInNF\"
name=\"GPLPluginsInNF\">èªç±ã§ãªãããã°ã©"
+"ã
åãã®ãã©ã°ã¤ã³ã«GPLãé©ç¨ãããã¨ã¯ã§ãã¾ãã?</a></b>"
#. type: Content of: <dl><dd>
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 for the main program makes no requirements for them."
+"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."
msgstr ""
-"ããã¯ããã°ã©ã
ãã©ã®ããã«ãã©ã°ã¤ã³ãå¼ã³åºããã«ä¾ãã¾ããããã°ã©ã
ã"
-"forkãexecã§ãã©ã°ã¤ã³ãå¼ã³åºããªãã°ããã©ã°ã¤ã³ã¯å¥ã®ããã°ã©ã
ã§ãããã¡"
-"ã¤ã³ããã°ã©ã
ã®ã©ã¤ã»ã³ã¹ã¯ãããã«ã¯ãªãã®æ¡ä»¶ã課ãã¾ããã"
#. 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."
+#, fuzzy
+#| 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."
+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 "
+"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."
msgstr ""
"ããããã°ã©ã
ããã©ã°ã¤ã³ã¨åçã«ãªã³ã¯ããã¦ããããäºãã«ãã¡ã³ã¯ã·ã§ã³"
"ã³ã¼ã«ã使ã£ã¦ãã¼ã¿æ§é ãå
±æãã¦ããå
´åããããã¯åä¸ã®ããã°ã©ã ãå½¢æã"
@@ -2808,13 +2832,35 @@
#. type: Content of: <dl><dd><p>
msgid ""
-"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."
-msgstr ""
-"ããã°ã©ã
ããã©ã°ã¤ã³ã¨åçã«ãªã³ã¯ããã¦ãããããããã®éã®ã³ãã¥ãã±ã¼"
-"ã·ã§ã³ã¯ããã¤ãã®ãªãã·ã§ã³ã¨ã¨ãã«ãã©ã°ã¤ã³ã®ãmainãé¢æ°ãå¼ã³åºãã¦è¿å¤"
-"ãå¾
ã¤ã ãã¨ããå
´åã¯ãå¢çç·ä¸ã§å¾®å¦ãªã±ã¼ã¹ã¨ãªãã¾ãã"
+"Using shared memory to communicate with complex data structures is pretty "
+"much equivalent to dynamic linking."
+msgstr ""
+
+#. type: Content of: <dl><dt>
+msgid ""
+"<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>"
+msgstr ""
+"<b><a href=\"#TOCGPLAndPlugins\"
name=\"GPLAndPlugins\">GPLã®ãã¨ã§ãªãªã¼ã¹ã"
+"ãã¦ããããã°ã©ã
ããã©ã°ã¤ã³ã使ãã¨ãã¦ããã©ã°ã¤ã³ã®ã©ã¤ã»ã³ã¹ã«ã¯ã©ã®ã"
+"ããªæ¡ä»¶ãããã¾ãã?</a></b>"
+
+#. type: Content of: <dl><dd>
+msgid ""
+"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 considered are separate works</a>."
+msgstr ""
+
+#. 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 "
+"software license and distribute it with source code in a GPL-compliant way. "
+"A main program that is a seperate from its plug-ins makes no requirements "
+"for the plug-ins."
+msgstr ""
#. type: Content of: <dl><dt>
msgid ""
@@ -2826,24 +2872,27 @@
#. type: Content of: <dl><dd>
msgid ""
-"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."
-msgstr ""
-"ããããã°ã©ã
ãforkãexecã§ãã©ã°ã¤ã³ãå¼ã³åºããªãã°ããã©ã°ã¤ã³ã¯å¥ã®ãã"
-"ã°ã©ã ã§ããããã¡ã¤ã³ããã°ã©ã
ã®ã©ã¤ã»ã³ã¹ã¯ä½ã®æ¡ä»¶ã課ãã¾ãããã§ããã"
-"ããªãã¯ãã©ã°ã¤ã³ã«GPLãé©ç¨ã§ãã¾ãããç¹å¥ãªè¦ä»¶ã¯ããã¾ããã"
+"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>."
+msgstr ""
#. 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."
+#, fuzzy
+#| 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."
+msgid ""
+"If they form a single combined program this means that combination of the "
+"GPL-covered plug-in with the non-free main program would violate the GPL. "
+"However, you can resolve that legal problem by adding an exception to your "
+"plug-in's license, giving permission to link it with the non-free main "
+"program."
msgstr ""
"ããã°ã©ã
ããã©ã°ã¤ã³ã¨åçã«ãªã³ã¯ããããäºãã«ãã¡ã³ã¯ã·ã§ã³ã³ã¼ã«ã使ã£"
"ã¦ãã¼ã¿æ§é ãå
±æãã¦ããå
´åããããã¯åä¸ã®ããã°ã©ã ãå½¢æãã¦ããã¨è¦ãª"
@@ -2870,22 +2919,18 @@
"ã³ããã¼ãããããã«è¨è¨ãããä¸èªç±ãªããã°ã©ã
ããªãªã¼ã¹ãããã¨ã¯ã§ããã§"
"ãããã?</a></b>"
-#. type: Content of: <dl><dd>
-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."
-msgstr ""
-"ããã¯ããã°ã©ã
ãã©ã®ããã«ãã©ã°ã¤ã³ãå¼ã³åºããã«ããã¾ããããã°ã©ã
ã"
-"forkãexecã§ãã©ã°ã¤ã³ãå¼ã³åºããªãã°ããã©ã°ã¤ã³ã¯å¥ã®ããã°ã©ã
ã§ãããã¡"
-"ã¤ã³ããã°ã©ã
ã®ã©ã¤ã»ã³ã¹ã¯ãããã«ã¯ãªãã®æ¡ä»¶ã課ãã¾ããã"
-
#. type: Content of: <dl><dd><p>
+#, fuzzy
+#| 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."
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 "
+"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 that "
"the terms of the GPL must be followed when the main program is distributed "
"for use with these plug-ins."
@@ -2898,6 +2943,21 @@
"ã§ãªãªã¼ã¹ãããªããã°ãªãããã¡ã¤ã³ããã°ã©ã
ããããã®ãã©ã°ã¤ã³ã®ä½¿ç¨ã®ã"
"ãã«é
å¸ãããæã«ã¯ãGPLã®æ¡é
ã«å¾ããªããã°ãªããªãã¨ãããã¨ã§ãã"
+#. type: Content of: <dl><dd><p>
+#, fuzzy
+#| 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."
+msgid ""
+"However, if they are separate works then the license of the plug-in makes no "
+"requirements about the main program."
+msgstr ""
+"ããã¯ããã°ã©ã
ãã©ã®ããã«ãã©ã°ã¤ã³ãå¼ã³åºããã«ããã¾ããããã°ã©ã
ã"
+"forkãexecã§ãã©ã°ã¤ã³ãå¼ã³åºããªãã°ããã©ã°ã¤ã³ã¯å¥ã®ããã°ã©ã
ã§ãããã¡"
+"ã¤ã³ããã°ã©ã
ã®ã©ã¤ã»ã³ã¹ã¯ãããã«ã¯ãªãã®æ¡ä»¶ã課ãã¾ããã"
+
#. type: Content of: <dl><dt>
msgid ""
"<b><a href=\"#TOCLinkingWithGPL\" name=\"LinkingWithGPL\">You have a GPL'ed "
@@ -3299,7 +3359,7 @@
"<b><a href=\"#TOCLGPLJava\"
name=\"LGPLJava\">LGPLã¯Javaã«ã©ãåãã¾ãã?</"
"a></b>"
-#. type: Content of: <dl><dd><p>
+#. type: Content of: <dl><dd>
msgid ""
"<a href=\"/licenses/lgpl-java.html\">See this article for details.</a> It "
"works as designed, intended, and expected."
@@ -3443,7 +3503,7 @@
"ã®ãããª)ã®ãã©ããã¼ãã¢ã¸ã¥ã¼ã«ãã¯ãããã¨ã«ãããããã¯å¯è½ã§ãã?</a></"
"b>"
-#. type: Content of: <dl><dd><p>
+#. type: Content of: <dl><dd>
msgid ""
"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 "
@@ -3475,7 +3535,7 @@
"<b><a href=\"#TOCLibGCCException\"
name=\"LibGCCException\">libstdc++ä¾å¤ã¯å"
"çãªã³ã¯ã許å¯ãã¾ãã?</a></b>"
-#. type: Content of: <dl><dd><p>
+#. type: Content of: <dl><dd>
msgid ""
"Yes. The intent of the exception is to allow people to compile proprietary "
"software using gcc."
@@ -5109,6 +5169,36 @@
msgid "Updated:"
msgstr "æçµæ´æ°:"
+#~ 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 for the main program makes no requirements for "
+#~ "them."
+#~ msgstr ""
+#~ "ããã¯ããã°ã©ã
ãã©ã®ããã«ãã©ã°ã¤ã³ãå¼ã³åºããã«ä¾ãã¾ããããã°ã©ã
ã"
+#~
"forkãexecã§ãã©ã°ã¤ã³ãå¼ã³åºããªãã°ããã©ã°ã¤ã³ã¯å¥ã®ããã°ã©ã
ã§ããã"
+#~ "ã¡ã¤ã³ããã°ã©ã
ã®ã©ã¤ã»ã³ã¹ã¯ãããã«ã¯ãªãã®æ¡ä»¶ã課ãã¾ããã"
+
+#~ msgid ""
+#~ "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."
+#~ msgstr ""
+#~ "ããã°ã©ã
ããã©ã°ã¤ã³ã¨åçã«ãªã³ã¯ããã¦ãããããããã®éã®ã³ãã¥ãã±ã¼"
+#~
"ã·ã§ã³ã¯ããã¤ãã®ãªãã·ã§ã³ã¨ã¨ãã«ãã©ã°ã¤ã³ã®ãmainãé¢æ°ãå¼ã³åºãã¦è¿"
+#~ "å¤ãå¾
ã¤ã ãã¨ããå
´åã¯ãå¢çç·ä¸ã§å¾®å¦ãªã±ã¼ã¹ã¨ãªãã¾ãã"
+
+#~ msgid ""
+#~ "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."
+#~ msgstr ""
+#~ "ããããã°ã©ã
ãforkãexecã§ãã©ã°ã¤ã³ãå¼ã³åºããªãã°ããã©ã°ã¤ã³ã¯å¥ã®ã"
+#~ "ãã°ã©ã ã§ããããã¡ã¤ã³ããã°ã©ã
ã®ã©ã¤ã»ã³ã¹ã¯ä½ã®æ¡ä»¶ã課ãã¾ãããã§ã"
+#~
"ããããªãã¯ãã©ã°ã¤ã³ã«GPLãé©ç¨ã§ãã¾ãããç¹å¥ãªè¦ä»¶ã¯ããã¾ããã"
+
#~ msgid "Yes, because the program as it is actually run includes the library."
#~ msgstr ""
#~ "ã¯ãããªããªããå®éã«å®è¡ãããããã°ã©ã
ã¯ã©ã¤ãã©ãªãå«ãã§ããããã§"
Index: licenses/old-licenses/po/gpl-2.0-faq.pot
===================================================================
RCS file: /web/www/www/licenses/old-licenses/po/gpl-2.0-faq.pot,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -b -r1.24 -r1.25
--- licenses/old-licenses/po/gpl-2.0-faq.pot 17 Feb 2017 05:30:48 -0000
1.24
+++ licenses/old-licenses/po/gpl-2.0-faq.pot 10 Mar 2017 19:30:51 -0000
1.25
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: gpl-2.0-faq.html\n"
-"POT-Creation-Date: 2017-02-17 05:26+0000\n"
+"POT-Creation-Date: 2017-03-10 19:26+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <address@hidden>\n"
"Language-Team: LANGUAGE <address@hidden>\n"
@@ -596,6 +596,12 @@
#. 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>"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
"<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>"
@@ -1904,33 +1910,59 @@
#. type: Content of: <dl><dt>
msgid ""
-"<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>"
+"<b><a href=\"#TOCGPLPlugins\" name=\"GPLPlugins\"> When are a program and "
+"its plug-ins considered a single combined program? </a></b>"
msgstr ""
#. type: Content of: <dl><dd>
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 for the main program makes no requirements for them."
+"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."
msgstr ""
#. 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."
+"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."
msgstr ""
#. type: Content of: <dl><dd><p>
msgid ""
-"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."
+"Using shared memory to communicate with complex data structures is pretty "
+"much equivalent to dynamic linking."
+msgstr ""
+
+#. type: Content of: <dl><dt>
+msgid ""
+"<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>"
+msgstr ""
+
+#. type: Content of: <dl><dd>
+msgid ""
+"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 considered are separate works</a>."
+msgstr ""
+
+#. 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 "
+"software license and distribute it with source code in a GPL-compliant "
+"way. A main program that is a seperate from its plug-ins makes no "
+"requirements for the plug-ins."
msgstr ""
#. type: Content of: <dl><dt>
@@ -1941,21 +1973,18 @@
#. type: Content of: <dl><dd>
msgid ""
-"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."
+"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>."
msgstr ""
#. 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."
+"If they form a single combined program this means that combination of the "
+"GPL-covered plug-in with the non-free main program would violate the "
+"GPL. However, you can resolve that legal problem by adding an exception to "
+"your plug-in's license, giving permission to link it with the non-free main "
+"program."
msgstr ""
#. type: Content of: <dl><dd><p>
@@ -1970,22 +1999,18 @@
"non-free program that's designed to load a GPL-covered plug-in?</a></b>"
msgstr ""
-#. type: Content of: <dl><dd>
+#. 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."
+"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 that "
+"the terms of the GPL must be followed when the main program is distributed "
+"for use with these plug-ins."
msgstr ""
#. 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."
+"However, if they are separate works then the license of the plug-in makes no "
+"requirements about the main program."
msgstr ""
#. type: Content of: <dl><dt>
@@ -2260,7 +2285,7 @@
"Java?</a></b>"
msgstr ""
-#. type: Content of: <dl><dd><p>
+#. type: Content of: <dl><dd>
msgid ""
"<a href=\"/licenses/lgpl-java.html\">See this article for details.</a> It "
"works as designed, intended, and expected."
@@ -2352,7 +2377,7 @@
"proprietary part?</a></b>"
msgstr ""
-#. type: Content of: <dl><dd><p>
+#. type: Content of: <dl><dd>
msgid ""
"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 "
@@ -2374,7 +2399,7 @@
"libstdc++ exception permit dynamic linking?</a></b>"
msgstr ""
-#. type: Content of: <dl><dd><p>
+#. type: Content of: <dl><dd>
msgid ""
"Yes. The intent of the exception is to allow people to compile proprietary "
"software using gcc."
Index: licenses/old-licenses/po/gpl-2.0-faq.ru.po
===================================================================
RCS file: /web/www/www/licenses/old-licenses/po/gpl-2.0-faq.ru.po,v
retrieving revision 1.42
retrieving revision 1.43
diff -u -b -r1.42 -r1.43
--- licenses/old-licenses/po/gpl-2.0-faq.ru.po 17 Feb 2017 06:30:24 -0000
1.42
+++ licenses/old-licenses/po/gpl-2.0-faq.ru.po 10 Mar 2017 19:30:51 -0000
1.43
@@ -8,7 +8,7 @@
msgid ""
msgstr ""
"Project-Id-Version: gpl-2.0-faq.html\n"
-"POT-Creation-Date: 2017-02-17 05:26+0000\n"
+"POT-Creation-Date: 2017-03-10 19:26+0000\n"
"PO-Revision-Date: 2017-01-03 17:17+0000\n"
"Last-Translator: Ineiev <address@hidden>\n"
"Language-Team: Russian <address@hidden>\n"
@@ -16,6 +16,7 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"X-Outdated-Since: 2017-03-10 19:26+0000\n"
#. type: Content of: <title>
msgid ""
@@ -833,6 +834,22 @@
"каÑеÑÑве лиÑензии Ð´Ð»Ñ Ð¼Ð¾ÐµÐ³Ð¾ модÑлÑ?</a>"
#. type: Content of: <ul><li>
+# | <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>
+#, fuzzy
+#| 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=\"#GPLPlugins\" name=\"TOCGPLPlugins\"> When are a program and its "
+"plug-ins considered a single combined program?</a>"
+msgstr ""
+"<a href=\"#GPLPluginsInNF\" name=\"TOCGPLPluginsInNF\">ÐÐ¾Ð³Ñ Ñ
пÑименÑÑÑ GPL, "
+"когда пиÑÑ Ð²Ð½ÐµÑний модÑÐ»Ñ Ðº неÑвободной
пÑогÑамме?</a>"
+
+#. type: Content of: <ul><li>
msgid ""
"<a href=\"#GPLAndPlugins\" name=\"TOCGPLAndPlugins\">If a program released "
"under the GPL uses plug-ins, what are the requirements for the licenses of a "
@@ -2797,34 +2814,59 @@
"РпеÑеÑмоÑÑенной лиÑензии BSD пÑнкÑа о
Ñекламе неÑ, ÑÑо ÑÑÑÑанÑÐµÑ Ð¿ÑоблемÑ."
#. type: Content of: <dl><dt>
+# | <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>+}
+#, fuzzy
+#| 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=\"#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>"
+"<b><a href=\"#TOCGPLPlugins\" name=\"GPLPlugins\"> When are a program and "
+"its plug-ins considered a single combined program? </a></b>"
msgstr ""
-"<a href=\"#TOCGPLAndPlugins\" name=\"GPLAndPlugins\">ÐÑли
пÑогÑамма, "
-"вÑпÑÑÐµÐ½Ð½Ð°Ñ Ð¿Ð¾Ð´ GPL, полÑзÑеÑÑÑ Ð²Ð½ÐµÑними
модÑлÑми, ÐºÐ°ÐºÐ¾Ð²Ñ ÑÑÐµÐ±Ð¾Ð²Ð°Ð½Ð¸Ñ Ðº "
-"лиÑензиÑм модÑлÑ?</a>"
+"<a href=\"#TOCGPLPluginsInNF\" name=\"GPLPluginsInNF\">ÐÐ¾Ð³Ñ Ñ
пÑименÑÑÑ GPL, "
+"когда пиÑÑ Ð²Ð½ÐµÑний модÑÐ»Ñ Ðº неÑвободной
пÑогÑамме?</a>"
#. type: Content of: <dl><dd>
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 for the main program makes no requirements for them."
+"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."
msgstr ""
-"ÐÑо завиÑÐ¸Ñ Ð¾Ñ Ñого, как пÑогÑамма
задейÑÑвÑÐµÑ Ñвои внеÑние модÑли. ÐÑли "
-"пÑогÑамма полÑзÑеÑÑÑ Ð´Ð»Ñ ÑÑого вÑзовами
<em>fork</em> или <em>exec</em>, Ñо "
-"модÑли — ÑÑо оÑделÑнÑе пÑогÑаммÑ,
Ñак ÑÑо лиÑÐµÐ½Ð·Ð¸Ñ Ð³Ð»Ð°Ð²Ð½Ð¾Ð¹ "
-"пÑогÑÐ°Ð¼Ð¼Ñ Ð½Ðµ пÑедÑÑвлÑÐµÑ Ðº ним никакиÑ
ÑÑебований."
#. 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."
+# | 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.+}
+#, fuzzy
+#| 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."
+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 "
+"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."
msgstr ""
"ÐÑли пÑогÑамма динамиÑеÑки компонÑеÑÑÑ Ñ
модÑлÑми и они вÑзÑваÑÑ ÑÑнкÑии "
"дÑÑг из дÑÑга и ÑазделÑÑÑ Ð¾Ð±Ñие ÑÑÑÑкÑÑÑÑ
даннÑÑ
, Ð¼Ñ ÑбежденÑ, ÑÑо они "
@@ -2835,14 +2877,35 @@
#. type: Content of: <dl><dd><p>
msgid ""
-"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."
-msgstr ""
-"Ðак пÑеделÑнÑй Ð¼Ð¾Ð¶ÐµÑ ÑаÑÑмаÑÑиваÑÑÑÑ
ÑлÑÑай, когда пÑогÑамма динамиÑеÑки "
-"компонÑеÑÑÑ Ñ Ð¼Ð¾Ð´ÑлÑми, но ÑообÑение
Ð¼ÐµÐ¶Ð´Ñ Ð½Ð¸Ð¼Ð¸ огÑаниÑиваеÑÑÑ Ð²Ñзовом "
-"“главной” ÑÑнкÑии модÑÐ»Ñ Ñ
некоÑоÑÑми аÑгÑменÑами и ожиданием, "
-"когда пÑÐ¾Ð¸Ð·Ð¾Ð¹Ð´ÐµÑ Ð²Ð¾Ð·Ð²ÑÐ°Ñ Ð¸Ð· ÑÑнкÑии."
+"Using shared memory to communicate with complex data structures is pretty "
+"much equivalent to dynamic linking."
+msgstr ""
+
+#. type: Content of: <dl><dt>
+msgid ""
+"<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>"
+msgstr ""
+"<a href=\"#TOCGPLAndPlugins\" name=\"GPLAndPlugins\">ÐÑли
пÑогÑамма, "
+"вÑпÑÑÐµÐ½Ð½Ð°Ñ Ð¿Ð¾Ð´ GPL, полÑзÑеÑÑÑ Ð²Ð½ÐµÑними
модÑлÑми, ÐºÐ°ÐºÐ¾Ð²Ñ ÑÑÐµÐ±Ð¾Ð²Ð°Ð½Ð¸Ñ Ðº "
+"лиÑензиÑм модÑлÑ?</a>"
+
+#. type: Content of: <dl><dd>
+msgid ""
+"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 considered are separate works</a>."
+msgstr ""
+
+#. 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 "
+"software license and distribute it with source code in a GPL-compliant way. "
+"A main program that is a seperate from its plug-ins makes no requirements "
+"for the plug-ins."
+msgstr ""
#. type: Content of: <dl><dt>
msgid ""
@@ -2854,25 +2917,35 @@
#. type: Content of: <dl><dd>
msgid ""
-"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."
-msgstr ""
-"ÐÑли пÑогÑамма полÑзÑеÑÑÑ Ð²Ñзовами
<em>fork</em> и <em>exec</em> Ð´Ð»Ñ Ñого, "
-"ÑÑÐ¾Ð±Ñ Ð·Ð°Ð´ÐµÐ¹ÑÑвоваÑÑ Ð¼Ð¾Ð´ÑлÑ, Ñо модÑли
ÑвлÑÑÑÑÑ Ð¾ÑделÑнÑми пÑогÑаммами, Ñак "
-"ÑÑо лиÑÐµÐ½Ð·Ð¸Ñ Ð³Ð»Ð°Ð²Ð½Ð¾Ð¹ пÑогÑÐ°Ð¼Ð¼Ñ Ð½Ðµ
пÑедÑÑвлÑÐµÑ Ðº ним никакиÑ
ÑÑебований. Так "
-"ÑÑо Ð²Ñ Ð¼Ð¾Ð¶ÐµÑе пÑименÑÑÑ GPL Ð´Ð»Ñ Ð¼Ð¾Ð´ÑÐ»Ñ Ð¸
никакиÑ
оÑобÑÑ
ÑÑебований неÑ."
+"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>."
+msgstr ""
#. 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."
+# | 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.
+#, fuzzy
+#| 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."
+msgid ""
+"If they form a single combined program this means that combination of the "
+"GPL-covered plug-in with the non-free main program would violate the GPL. "
+"However, you can resolve that legal problem by adding an exception to your "
+"plug-in's license, giving permission to link it with the non-free main "
+"program."
msgstr ""
"ÐÑли пÑогÑамма динамиÑеÑки компонÑеÑÑÑ Ñ
модÑлÑми и они вÑзÑваÑÑ ÑÑнкÑии "
"дÑÑг из дÑÑга и ÑазделÑÑÑ Ð¾Ð±Ñие ÑÑÑÑкÑÑÑÑ
даннÑÑ
, Ð¼Ñ ÑбежденÑ, ÑÑо они "
@@ -2899,23 +2972,26 @@
"неÑвободнÑÑ Ð¿ÑогÑаммÑ, ÑоÑÑавленнÑÑ Ñак,
ÑÑÐ¾Ð±Ñ Ð¿Ð¾Ð´Ð³ÑÑжаÑÑ Ð²Ð½ÐµÑний модÑÐ»Ñ Ð¿Ð¾Ð´ "
"GPL?</a>"
-#. type: Content of: <dl><dd>
-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."
-msgstr ""
-"ÐÑо завиÑÐ¸Ñ Ð¾Ñ Ñого, как пÑогÑамма
задейÑÑвÑÐµÑ Ñвои внеÑние модÑли. ÐÑли "
-"пÑогÑамма иÑполÑзÑÐµÑ Ð²ÑÐ·Ð¾Ð²Ñ <em>fork</em> и
<em>exec</em> Ð´Ð»Ñ Ð·Ð°Ð³ÑÑзки "
-"модÑлей, Ñо ÑÑи модÑли ÑвлÑÑÑÑÑ
оÑделÑнÑми пÑогÑаммами, Ñак ÑÑо лиÑÐµÐ½Ð·Ð¸Ñ "
-"модÑÐ»Ñ Ð½Ðµ пÑедÑÑвлÑÐµÑ ÑÑебований к
главной пÑогÑамме."
-
#. type: Content of: <dl><dd><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-]
+# | {+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.
+#, fuzzy
+#| 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."
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 "
+"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 that "
"the terms of the GPL must be followed when the main program is distributed "
"for use with these plug-ins."
@@ -2928,6 +3004,26 @@
"ÑвободнÑÑ
пÑогÑамм и ÑÑÐ»Ð¾Ð²Ð¸Ñ GPL должнÑ
ÑоблÑдаÑÑÑÑ, когда Ð³Ð»Ð°Ð²Ð½Ð°Ñ Ð¿ÑогÑамма "
"ÑаÑпÑоÑÑÑанÑеÑÑÑ Ð´Ð»Ñ Ð¸ÑполÑÐ·Ð¾Ð²Ð°Ð½Ð¸Ñ Ñ
ÑÑими модÑлÑми."
+#. type: Content of: <dl><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-]{+However, if they+}
+# | are separate [-programs, so-] {+works then+} the license of the plug-in
+# | makes no requirements about the main program.
+#, fuzzy
+#| 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."
+msgid ""
+"However, if they are separate works then the license of the plug-in makes no "
+"requirements about the main program."
+msgstr ""
+"ÐÑо завиÑÐ¸Ñ Ð¾Ñ Ñого, как пÑогÑамма
задейÑÑвÑÐµÑ Ñвои внеÑние модÑли. ÐÑли "
+"пÑогÑамма иÑполÑзÑÐµÑ Ð²ÑÐ·Ð¾Ð²Ñ <em>fork</em> и
<em>exec</em> Ð´Ð»Ñ Ð·Ð°Ð³ÑÑзки "
+"модÑлей, Ñо ÑÑи модÑли ÑвлÑÑÑÑÑ
оÑделÑнÑми пÑогÑаммами, Ñак ÑÑо лиÑÐµÐ½Ð·Ð¸Ñ "
+"модÑÐ»Ñ Ð½Ðµ пÑедÑÑвлÑÐµÑ ÑÑебований к
главной пÑогÑамме."
+
#. type: Content of: <dl><dt>
msgid ""
"<b><a href=\"#TOCLinkingWithGPL\" name=\"LinkingWithGPL\">You have a GPL'ed "
@@ -3344,7 +3440,7 @@
"Java?</a></b>"
msgstr "<a name=\"LGPLJava\">Ðак LGPL ÑабоÑÐ°ÐµÑ Ñ Java?</a>"
-#. type: Content of: <dl><dd><p>
+#. type: Content of: <dl><dd>
msgid ""
"<a href=\"/licenses/lgpl-java.html\">See this article for details.</a> It "
"works as designed, intended, and expected."
@@ -3492,7 +3588,7 @@
"лиÑензией (как, напÑимеÑ, лиÑÐµÐ½Ð·Ð¸Ñ X11)
Ð¼ÐµÐ¶Ð´Ñ ÑаÑÑÑÑ, ÑаÑпÑоÑÑÑанÑемой по "
"GPL, и неÑвободной ÑаÑÑÑÑ?</a>"
-#. type: Content of: <dl><dd><p>
+#. type: Content of: <dl><dd>
msgid ""
"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 "
@@ -3525,7 +3621,7 @@
"<a href=\"#TOCLibGCCException\" name=\"LibGCCException\"> ÐопÑÑкаеÑ
ли "
"иÑклÑÑение libstdc++ динамиÑеÑкое
ÑвÑзÑвание?</a>"
-#. type: Content of: <dl><dd><p>
+#. type: Content of: <dl><dd>
msgid ""
"Yes. The intent of the exception is to allow people to compile proprietary "
"software using gcc."
@@ -5158,6 +5254,40 @@
msgid "Updated:"
msgstr "Ðбновлено:"
+#~ 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 for the main program makes no requirements for "
+#~ "them."
+#~ msgstr ""
+#~ "ÐÑо завиÑÐ¸Ñ Ð¾Ñ Ñого, как пÑогÑамма
задейÑÑвÑÐµÑ Ñвои внеÑние модÑли. ÐÑли "
+#~ "пÑогÑамма полÑзÑеÑÑÑ Ð´Ð»Ñ ÑÑого вÑзовами
<em>fork</em> или <em>exec</em>, "
+#~ "Ñо модÑли — ÑÑо оÑделÑнÑе
пÑогÑаммÑ, Ñак ÑÑо лиÑÐµÐ½Ð·Ð¸Ñ Ð³Ð»Ð°Ð²Ð½Ð¾Ð¹ "
+#~ "пÑогÑÐ°Ð¼Ð¼Ñ Ð½Ðµ пÑедÑÑвлÑÐµÑ Ðº ним никакиÑ
ÑÑебований."
+
+#~ msgid ""
+#~ "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."
+#~ msgstr ""
+#~ "Ðак пÑеделÑнÑй Ð¼Ð¾Ð¶ÐµÑ ÑаÑÑмаÑÑиваÑÑÑÑ
ÑлÑÑай, когда пÑогÑамма динамиÑеÑки "
+#~ "компонÑеÑÑÑ Ñ Ð¼Ð¾Ð´ÑлÑми, но ÑообÑение
Ð¼ÐµÐ¶Ð´Ñ Ð½Ð¸Ð¼Ð¸ огÑаниÑиваеÑÑÑ Ð²Ñзовом "
+#~ "“главной” ÑÑнкÑии модÑÐ»Ñ Ñ
некоÑоÑÑми аÑгÑменÑами и "
+#~ "ожиданием, когда пÑÐ¾Ð¸Ð·Ð¾Ð¹Ð´ÐµÑ Ð²Ð¾Ð·Ð²ÑÐ°Ñ Ð¸Ð·
ÑÑнкÑии."
+
+#~ msgid ""
+#~ "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."
+#~ msgstr ""
+#~ "ÐÑли пÑогÑамма полÑзÑеÑÑÑ Ð²Ñзовами
<em>fork</em> и <em>exec</em> Ð´Ð»Ñ "
+#~ "Ñого, ÑÑÐ¾Ð±Ñ Ð·Ð°Ð´ÐµÐ¹ÑÑвоваÑÑ Ð¼Ð¾Ð´ÑлÑ, Ñо
модÑли ÑвлÑÑÑÑÑ Ð¾ÑделÑнÑми "
+#~ "пÑогÑаммами, Ñак ÑÑо лиÑÐµÐ½Ð·Ð¸Ñ Ð³Ð»Ð°Ð²Ð½Ð¾Ð¹
пÑогÑÐ°Ð¼Ð¼Ñ Ð½Ðµ пÑедÑÑвлÑÐµÑ Ðº ним "
+#~ "никакиÑ
ÑÑебований. Так ÑÑо Ð²Ñ Ð¼Ð¾Ð¶ÐµÑе
пÑименÑÑÑ GPL Ð´Ð»Ñ Ð¼Ð¾Ð´ÑÐ»Ñ Ð¸ никакиÑ
"
+#~ "оÑобÑÑ
ÑÑебований неÑ."
+
#~ msgid "Yes, because the program as it is actually run includes the library."
#~ msgstr ""
#~ "Ðа, поÑÐ¾Ð¼Ñ ÑÑо пÑогÑамма, коÑоÑÐ°Ñ Ð½Ð°
Ñамом деле вÑполнÑеÑÑÑ, вклÑÑÐ°ÐµÑ Ð² "
Index: licenses/po/gpl-faq.es.po
===================================================================
RCS file: /web/www/www/licenses/po/gpl-faq.es.po,v
retrieving revision 1.76
retrieving revision 1.77
diff -u -b -r1.76 -r1.77
--- licenses/po/gpl-faq.es.po 21 Feb 2017 10:59:41 -0000 1.76
+++ licenses/po/gpl-faq.es.po 10 Mar 2017 19:30:52 -0000 1.77
@@ -8,7 +8,7 @@
msgid ""
msgstr ""
"Project-Id-Version: gpl-faq.html\n"
-"POT-Creation-Date: 2017-02-17 05:26+0000\n"
+"POT-Creation-Date: 2017-03-10 15:56+0000\n"
"PO-Revision-Date: 2017-02-21 11:00+0100\n"
"Last-Translator: Javier Fdez. Retenaga <address@hidden>\n"
"Language-Team: Spanish <address@hidden>\n"
@@ -16,6 +16,7 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"X-Outdated-Since: 2017-03-10 15:56+0000\n"
"Plural-Forms: nplurals=2; plural=(n!=1);\n"
"X-Generator: Poedit 1.6.10\n"
@@ -1196,6 +1197,21 @@
"la GPL, ¿tengo que usar la GPL como licencia para mi módulo?</a>"
#. type: Content of: <ul><li>
+# | <a [-href=\"#GPLPluginsInNF\">Can I apply the GPL when writing-]
+# | {+href=\"#GPLPlugins\">When are+} a [-plug-in for-] {+program and its
+# | plug-ins considered+} a [-non-free-] {+single combined+} program?</a>
+#, fuzzy
+#| msgid ""
+#| "<a href=\"#GPLPluginsInNF\">Can I apply the GPL when writing a plug-in "
+#| "for a non-free program?</a>"
+msgid ""
+"<a href=\"#GPLPlugins\">When are a program and its plug-ins considered a "
+"single combined program?</a>"
+msgstr ""
+"<a href=\"#GPLPluginsInNF\">¿Puedo utilizar la GPL si escribo un accesorio "
+"para un programa que no es libre?</a>"
+
+#. type: Content of: <ul><li>
msgid ""
"<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 "
@@ -3610,6 +3626,81 @@
"problema."
#. type: Content of: <dl><dt>
+# | [-Can I apply the GPL when writing-]{+When are+} a [-plug-in for-]
+# | {+program and its plug-ins considered+} a [-non-free-] {+single combined+}
+# | program? <span class=\"anchor-reference-id\">(<a
+# | [-href=\"#GPLPluginsInNF\" >#GPLPluginsInNF</a>)</span>-]
+# | {+href=\"#GPLPlugins\" >#GPLPlugins</a>)</span>+}
+#, fuzzy
+#| msgid ""
+#| "Can I apply the GPL when writing a plug-in for a non-free program? <span "
+#| "class=\"anchor-reference-id\">(<a href=\"#GPLPluginsInNF\" "
+#| ">#GPLPluginsInNF</a>)</span>"
+msgid ""
+"When are a program and its plug-ins considered a single combined program? "
+"<span class=\"anchor-reference-id\">(<a href=\"#GPLPlugins\" >#GPLPlugins</"
+"a>)</span>"
+msgstr ""
+"¿Puedo utilizar la GPL si escribo un accesorio para un programa que no es "
+"libre? <span class=\"anchor-reference-id\">(<a href=\"#GPLPluginsInNF\" "
+">#GPLPluginsInNF</a>)</span>"
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"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."
+msgstr ""
+
+#. type: Content of: <dl><dd><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. [-This means you must license-] {+If+}
+# | the [-plug-in under-] {+main program dynamically links plug-ins, but+} the
+# | [-GPL or a GPL-compatible free software license-] {+communication between
+# | them is limited to invoking the ‘main’ function of the plug-in
+# | with some options+} and [-distribute-] {+waiting for+} it [-with source
+# | code in-] {+to return, that is+} a [-GPL-compliant way.-] {+borderline
+# | case.+}
+#, fuzzy
+#| 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 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."
+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 "
+"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."
+msgstr ""
+"Si el programa enlaza dinámicamente con los accesorios, si se producen "
+"recÃprocas llamadas a funciones y comparten estructuras de datos, "
+"consideramos que forman un único programa y debe tratarse como una "
+"ampliación de ambos: programa principal y accesorios. Esto significa que el "
+"accesorio debe publicarse bajo la GPL u otra licencia de software libre "
+"compatible con la GPL, y que debe distribuirse junto al código fuente "
+"respetando los términos de la GPL."
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"Using shared memory to communicate with complex data structures is pretty "
+"much equivalent to dynamic linking."
+msgstr ""
+"Utilizar memoria compartida para la comunicación con estructuras de datos "
+"complejas es más o menos equivalente al enlazado dinámico."
+
+#. type: Content of: <dl><dt>
msgid ""
"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? "
@@ -3623,23 +3714,34 @@
#. 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 for the main program makes no requirements for them."
-msgstr ""
-"Depende de la manera en que el programa invoque los accesorios. Si el "
-"programa utiliza <cite>fork</cite> y <cite>exec</cite> para invocarlos, "
-"entonces los accesorios son programas separados, de modo que la licencia del "
-"programa principal no plantea ninguna exigencia con relación a ellos."
+"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 considered are separate works</a>."
+msgstr ""
#. 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 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."
+# | If the {+main+} program [-dynamically links plug-ins, and they make
+# | function calls to each other-] and [-share data structures, we believe
+# | they form-] {+the plugins are+} a single [-program, which must be treated
+# | as an extension of both the main-] {+combined+} program [-and the
+# | plug-ins. This-] {+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 a seperate
+# | from its plug-ins makes no requirements for the plug-ins.+}
+#, fuzzy
+#| 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 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."
+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 "
+"software license and distribute it with source code in a GPL-compliant way. "
+"A main program that is a seperate from its plug-ins makes no requirements "
+"for the plug-ins."
msgstr ""
"Si el programa enlaza dinámicamente con los accesorios, si se producen "
"recÃprocas llamadas a funciones y comparten estructuras de datos, "
@@ -3649,16 +3751,6 @@
"compatible con la GPL, y que debe distribuirse junto al código fuente "
"respetando los términos de la GPL."
-#. type: Content of: <dl><dd><p>
-msgid ""
-"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."
-msgstr ""
-"Si el programa enlaza dinámicamente con los accesorios, pero la
comunicación "
-"entre ellos se limita a invocar la función «principal» del accesorio con "
-"algunas opciones y a esperar su respuesta, estaremos ante un caso lÃmite."
-
#. type: Content of: <dl><dt>
msgid ""
"Can I apply the GPL when writing a plug-in for a non-free program? <span "
@@ -3671,26 +3763,35 @@
#. type: Content of: <dl><dd><p>
msgid ""
-"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."
-msgstr ""
-"Si el programa utiliza <cite>fork</cite> y <cite>exec</cite> para invocar "
-"los accesorios, entonces los accesorios son programas separados, de modo que "
-"la licencia del programa principal no plantea ninguna exigencia con relación
"
-"a ellos. Por tanto puede utilizar la GPL para el accesorio; no existen "
-"requisitos especiales."
+"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>."
+msgstr ""
#. 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."
+# | 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.
+#, fuzzy
+#| 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."
+msgid ""
+"If they form a single combined program this means that combination of the "
+"GPL-covered plug-in with the non-free main program would violate the GPL. "
+"However, you can resolve that legal problem by adding an exception to your "
+"plug-in's license, giving permission to link it with the non-free main "
+"program."
msgstr ""
"Si el programa enlaza dinámicamente con los accesorios, se producen "
"recÃprocas llamadas a funciones y comparten estructuras de datos, "
@@ -3720,24 +3821,25 @@
"\"#NFUseGPLPlugins\" >#NFUseGPLPlugins</a>)</span>"
#. type: Content of: <dl><dd><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-]
+# | {+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.
+#, fuzzy
+#| 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."
msgid ""
-"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."
-msgstr ""
-"Depende del modo en que el programa invoque su accesorio. Por ejemplo, si el "
-"programa no utiliza más que un sencillo <cite>fork</cite> y <cite>exec</"
-"cite> para invocar los accesorios, entonces los accesorios son programas "
-"separados, de modo que la licencia del accesorio no plantea ninguna "
-"exigencia con relación al programa principal."
-
-#. 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 "
+"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 that "
"the terms of the GPL must be followed when the main program is distributed "
"for use with these plug-ins."
@@ -3753,11 +3855,9 @@
#. type: Content of: <dl><dd><p>
msgid ""
-"Using shared memory to communicate with complex data structures is pretty "
-"much equivalent to dynamic linking."
+"However, if they are separate works then the license of the plug-in makes no "
+"requirements about the main program."
msgstr ""
-"Utilizar memoria compartida para la comunicación con estructuras de datos "
-"complejas es más o menos equivalente al enlazado dinámico."
#. type: Content of: <dl><dt>
msgid ""
@@ -8012,6 +8112,52 @@
msgstr "Ãltima actualización:"
#~ 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 for the main program makes no requirements for "
+#~ "them."
+#~ msgstr ""
+#~ "Depende de la manera en que el programa invoque los accesorios. Si el "
+#~ "programa utiliza <cite>fork</cite> y <cite>exec</cite> para invocarlos, "
+#~ "entonces los accesorios son programas separados, de modo que la licencia "
+#~ "del programa principal no plantea ninguna exigencia con relación a ellos."
+
+#~ msgid ""
+#~ "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."
+#~ msgstr ""
+#~ "Si el programa enlaza dinámicamente con los accesorios, pero la "
+#~ "comunicación entre ellos se limita a invocar la función «principal»
del "
+#~ "accesorio con algunas opciones y a esperar su respuesta, estaremos ante "
+#~ "un caso lÃmite."
+
+#~ msgid ""
+#~ "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."
+#~ msgstr ""
+#~ "Si el programa utiliza <cite>fork</cite> y <cite>exec</cite> para invocar "
+#~ "los accesorios, entonces los accesorios son programas separados, de modo "
+#~ "que la licencia del programa principal no plantea ninguna exigencia con "
+#~ "relación a ellos. Por tanto puede utilizar la GPL para el accesorio; no "
+#~ "existen requisitos especiales."
+
+#~ msgid ""
+#~ "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."
+#~ msgstr ""
+#~ "Depende del modo en que el programa invoque su accesorio. Por ejemplo, si "
+#~ "el programa no utiliza más que un sencillo <cite>fork</cite> y "
+#~ "<cite>exec</cite> para invocar los accesorios, entonces los accesorios "
+#~ "son programas separados, de modo que la licencia del accesorio no plantea "
+#~ "ninguna exigencia con relación al programa principal."
+
+#~ msgid ""
#~ "Yes, because the software as it is actually run includes the library."
#~ msgstr "SÃ, porque el programa utiliza la biblioteca en su funcionamiento."
Index: licenses/po/gpl-faq.fr.po
===================================================================
RCS file: /web/www/www/licenses/po/gpl-faq.fr.po,v
retrieving revision 1.178
retrieving revision 1.179
diff -u -b -r1.178 -r1.179
--- licenses/po/gpl-faq.fr.po 17 Feb 2017 12:00:24 -0000 1.178
+++ licenses/po/gpl-faq.fr.po 10 Mar 2017 19:30:52 -0000 1.179
@@ -10,7 +10,7 @@
msgid ""
msgstr ""
"Project-Id-Version: gpl-faq.html\n"
-"POT-Creation-Date: 2017-02-17 05:26+0000\n"
+"POT-Creation-Date: 2017-03-10 15:56+0000\n"
"PO-Revision-Date: 2017-02-17 12:34+0100\n"
"Last-Translator: Thérèse Godefroy <godef.th AT free.fr>\n"
"Language-Team: French <address@hidden>\n"
@@ -18,6 +18,7 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"X-Outdated-Since: 2017-03-10 15:56+0000\n"
"Plural-Forms: \n"
"X-Generator: Gtranslator 2.91.5\n"
@@ -1205,6 +1206,21 @@
"GPL, dois-je utiliser la GPL comme licence pour mon module ?</a>"
#. type: Content of: <ul><li>
+# | <a [-href=\"#GPLPluginsInNF\">Can I apply the GPL when writing-]
+# | {+href=\"#GPLPlugins\">When are+} a [-plug-in for-] {+program and its
+# | plug-ins considered+} a [-non-free-] {+single combined+} program?</a>
+#, fuzzy
+#| msgid ""
+#| "<a href=\"#GPLPluginsInNF\">Can I apply the GPL when writing a plug-in "
+#| "for a non-free program?</a>"
+msgid ""
+"<a href=\"#GPLPlugins\">When are a program and its plug-ins considered a "
+"single combined program?</a>"
+msgstr ""
+"<a href=\"#GPLPluginsInNF\">Puis-je utiliser la GPL pour un greffon dans un "
+"programme non libre ?</a>"
+
+#. type: Content of: <ul><li>
msgid ""
"<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 "
@@ -3632,6 +3648,81 @@
"qui élimine le problème."
#. type: Content of: <dl><dt>
+# | [-Can I apply the GPL when writing-]{+When are+} a [-plug-in for-]
+# | {+program and its plug-ins considered+} a [-non-free-] {+single combined+}
+# | program? <span class=\"anchor-reference-id\">(<a
+# | [-href=\"#GPLPluginsInNF\" >#GPLPluginsInNF</a>)</span>-]
+# | {+href=\"#GPLPlugins\" >#GPLPlugins</a>)</span>+}
+#, fuzzy
+#| msgid ""
+#| "Can I apply the GPL when writing a plug-in for a non-free program? <span "
+#| "class=\"anchor-reference-id\">(<a href=\"#GPLPluginsInNF\" "
+#| ">#GPLPluginsInNF</a>)</span>"
+msgid ""
+"When are a program and its plug-ins considered a single combined program? "
+"<span class=\"anchor-reference-id\">(<a href=\"#GPLPlugins\" >#GPLPlugins</"
+"a>)</span>"
+msgstr ""
+"Puis-je utiliser la GPL pour un greffon dans un programme non libre ? <span "
+"class=\"anchor-reference-id\">(<a href=\"#GPLPluginsInNF\" >#GPLPluginsInNF</"
+"a>)</span>"
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"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."
+msgstr ""
+
+#. type: Content of: <dl><dd><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. [-This means you must license-] {+If+}
+# | the [-plug-in under-] {+main program dynamically links plug-ins, but+} the
+# | [-GPL or a GPL-compatible free software license-] {+communication between
+# | them is limited to invoking the ‘main’ function of the plug-in
+# | with some options+} and [-distribute-] {+waiting for+} it [-with source
+# | code in-] {+to return, that is+} a [-GPL-compliant way.-] {+borderline
+# | case.+}
+#, fuzzy
+#| 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 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."
+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 "
+"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."
+msgstr ""
+"Si le programme est lié dynamiquement avec les greffons, et qu'ils font des "
+"appels de fonction mutuels en partageant des structures de données, nous "
+"pensons qu'ils forment un seul et même programme, qui doit être traité
comme "
+"une extension à la fois du programme principal et des greffons. Cela "
+"signifie que vous devez publier votre greffon sous la GPL ou sous une "
+"licence de logiciel libre compatible avec la GPL, et le distribuer avec le "
+"code source en respectant les termes de la GPL."
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"Using shared memory to communicate with complex data structures is pretty "
+"much equivalent to dynamic linking."
+msgstr ""
+"L'utilisation de mémoire partagée pour communiquer avec des structures de "
+"données complexes est pratiquement équivalente à une liaison dynamique."
+
+#. type: Content of: <dl><dt>
msgid ""
"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? "
@@ -3645,23 +3736,34 @@
#. 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 for the main program makes no requirements for them."
-msgstr ""
-"Cela dépend de la façon dont le programme invoque ses greffons. S'il
utilise "
-"<code>fork</code> et <code>exec</code> pour les invoquer, alors les greffons "
-"sont des programmes séparés, donc la licence du programme principal
n'impose "
-"aucune exigence les concernant."
+"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 considered are separate works</a>."
+msgstr ""
#. 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 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."
+# | If the {+main+} program [-dynamically links plug-ins, and they make
+# | function calls to each other-] and [-share data structures, we believe
+# | they form-] {+the plugins are+} a single [-program, which must be treated
+# | as an extension of both the main-] {+combined+} program [-and the
+# | plug-ins. This-] {+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 a seperate
+# | from its plug-ins makes no requirements for the plug-ins.+}
+#, fuzzy
+#| 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 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."
+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 "
+"software license and distribute it with source code in a GPL-compliant way. "
+"A main program that is a seperate from its plug-ins makes no requirements "
+"for the plug-ins."
msgstr ""
"Si le programme est lié dynamiquement avec les greffons, et qu'ils font des "
"appels de fonction mutuels en partageant des structures de données, nous "
@@ -3671,17 +3773,6 @@
"licence de logiciel libre compatible avec la GPL, et le distribuer avec le "
"code source en respectant les termes de la GPL."
-#. type: Content of: <dl><dd><p>
-msgid ""
-"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."
-msgstr ""
-"Si le programme est lié dynamiquement avec les greffons, mais que la "
-"communication entre eux se limite à invoquer la fonction « main » du
greffon "
-"avec quelques options puis à attendre que le greffon renvoie le résultat, "
-"nous nous trouvons dans un cas limite."
-
#. type: Content of: <dl><dt>
msgid ""
"Can I apply the GPL when writing a plug-in for a non-free program? <span "
@@ -3694,26 +3785,35 @@
#. type: Content of: <dl><dd><p>
msgid ""
-"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."
-msgstr ""
-"Si le programme utilise <code>fork</code> et <code>exec</code> pour invoquer "
-"les greffons, alors ces derniers sont des programmes séparés, aussi la "
-"licence du programme principal n'impose aucune exigence les concernant. Vous "
-"pouvez donc utiliser la GPL pour un greffon, il n'y a pas d'exigence "
-"spéciale."
+"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>."
+msgstr ""
#. 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."
+# | 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.
+#, fuzzy
+#| 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."
+msgid ""
+"If they form a single combined program this means that combination of the "
+"GPL-covered plug-in with the non-free main program would violate the GPL. "
+"However, you can resolve that legal problem by adding an exception to your "
+"plug-in's license, giving permission to link it with the non-free main "
+"program."
msgstr ""
"Si le programme est lié dynamiquement avec les greffons, et qu'ils font des "
"appels de fonction mutuels et partagent des structures de données, nous "
@@ -3743,24 +3843,25 @@
">#NFUseGPLPlugins</a>)</span>"
#. type: Content of: <dl><dd><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-]
+# | {+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.
+#, fuzzy
+#| 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."
msgid ""
-"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."
-msgstr ""
-"Cela dépend de la façon dont le programme invoque ses greffons. Par
exemple, "
-"si le programme utilise <em>seulement</em> de simples instructions "
-"<code>fork</code> et <code>exec</code> pour invoquer les greffons et "
-"communiquer avec eux, alors ces derniers sont des programmes séparés, et la
"
-"licence du greffon n'a pas d'exigence concernant le programme principal."
-
-#. 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 "
+"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 that "
"the terms of the GPL must be followed when the main program is distributed "
"for use with these plug-ins."
@@ -3776,11 +3877,9 @@
#. type: Content of: <dl><dd><p>
msgid ""
-"Using shared memory to communicate with complex data structures is pretty "
-"much equivalent to dynamic linking."
+"However, if they are separate works then the license of the plug-in makes no "
+"requirements about the main program."
msgstr ""
-"L'utilisation de mémoire partagée pour communiquer avec des structures de "
-"données complexes est pratiquement équivalente à une liaison dynamique."
#. type: Content of: <dl><dt>
msgid ""
@@ -8086,6 +8185,53 @@
msgstr "Dernière mise à jour :"
#~ 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 for the main program makes no requirements for "
+#~ "them."
+#~ msgstr ""
+#~ "Cela dépend de la façon dont le programme invoque ses greffons. S'il "
+#~ "utilise <code>fork</code> et <code>exec</code> pour les invoquer, alors "
+#~ "les greffons sont des programmes séparés, donc la licence du programme "
+#~ "principal n'impose aucune exigence les concernant."
+
+#~ msgid ""
+#~ "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."
+#~ msgstr ""
+#~ "Si le programme est lié dynamiquement avec les greffons, mais que la "
+#~ "communication entre eux se limite à invoquer la fonction « main » du "
+#~ "greffon avec quelques options puis à attendre que le greffon renvoie le "
+#~ "résultat, nous nous trouvons dans un cas limite."
+
+#~ msgid ""
+#~ "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."
+#~ msgstr ""
+#~ "Si le programme utilise <code>fork</code> et <code>exec</code> pour "
+#~ "invoquer les greffons, alors ces derniers sont des programmes séparés, "
+#~ "aussi la licence du programme principal n'impose aucune exigence les "
+#~ "concernant. Vous pouvez donc utiliser la GPL pour un greffon, il n'y a "
+#~ "pas d'exigence spéciale."
+
+#~ msgid ""
+#~ "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."
+#~ msgstr ""
+#~ "Cela dépend de la façon dont le programme invoque ses greffons. Par "
+#~ "exemple, si le programme utilise <em>seulement</em> de simples "
+#~ "instructions <code>fork</code> et <code>exec</code> pour invoquer les "
+#~ "greffons et communiquer avec eux, alors ces derniers sont des programmes "
+#~ "séparés, et la licence du greffon n'a pas d'exigence concernant le "
+#~ "programme principal."
+
+#~ msgid ""
#~ "Yes, because the software as it is actually run includes the library."
#~ msgstr ""
#~ "Oui, parce que le programme tel qu'il est effectivement exécuté inclut
la "
Index: licenses/po/gpl-faq.it.po
===================================================================
RCS file: /web/www/www/licenses/po/gpl-faq.it.po,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -b -r1.28 -r1.29
--- licenses/po/gpl-faq.it.po 5 Mar 2017 14:29:33 -0000 1.28
+++ licenses/po/gpl-faq.it.po 10 Mar 2017 19:30:52 -0000 1.29
@@ -10,7 +10,7 @@
msgid ""
msgstr ""
"Project-Id-Version: gpl-faq.html\n"
-"POT-Creation-Date: 2017-02-17 05:26+0000\n"
+"POT-Creation-Date: 2017-03-10 15:56+0000\n"
"PO-Revision-Date: 2017-03-05 14:30+0100\n"
"Last-Translator: Andrea Pescetti <address@hidden>\n"
"Language-Team: Italian <address@hidden>\n"
@@ -18,6 +18,7 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"X-Outdated-Since: 2017-03-10 15:56+0000\n"
"X-Generator: Poedit 1.5.4\n"
#. type: Content of: <title>
@@ -1187,6 +1188,21 @@
"dalla GPL, devo usare la GPL come licenza per il mio modulo?</a>"
#. type: Content of: <ul><li>
+# | <a [-href=\"#GPLPluginsInNF\">Can I apply the GPL when writing-]
+# | {+href=\"#GPLPlugins\">When are+} a [-plug-in for-] {+program and its
+# | plug-ins considered+} a [-non-free-] {+single combined+} program?</a>
+#, fuzzy
+#| msgid ""
+#| "<a href=\"#GPLPluginsInNF\">Can I apply the GPL when writing a plug-in "
+#| "for a non-free program?</a>"
+msgid ""
+"<a href=\"#GPLPlugins\">When are a program and its plug-ins considered a "
+"single combined program?</a>"
+msgstr ""
+"<a href=\"#GPLPluginsInNF\">Posso usare la GPL per un plug-in destinato ad "
+"un programma non libero?</a>"
+
+#. type: Content of: <ul><li>
msgid ""
"<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 "
@@ -3603,6 +3619,80 @@
"problema."
#. type: Content of: <dl><dt>
+# | [-Can I apply the GPL when writing-]{+When are+} a [-plug-in for-]
+# | {+program and its plug-ins considered+} a [-non-free-] {+single combined+}
+# | program? <span class=\"anchor-reference-id\">(<a
+# | [-href=\"#GPLPluginsInNF\" >#GPLPluginsInNF</a>)</span>-]
+# | {+href=\"#GPLPlugins\" >#GPLPlugins</a>)</span>+}
+#, fuzzy
+#| msgid ""
+#| "Can I apply the GPL when writing a plug-in for a non-free program? <span "
+#| "class=\"anchor-reference-id\">(<a href=\"#GPLPluginsInNF\" "
+#| ">#GPLPluginsInNF</a>)</span>"
+msgid ""
+"When are a program and its plug-ins considered a single combined program? "
+"<span class=\"anchor-reference-id\">(<a href=\"#GPLPlugins\" >#GPLPlugins</"
+"a>)</span>"
+msgstr ""
+"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>"
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"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."
+msgstr ""
+
+#. type: Content of: <dl><dd><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. [-This means you must license-] {+If+}
+# | the [-plug-in under-] {+main program dynamically links plug-ins, but+} the
+# | [-GPL or a GPL-compatible free software license-] {+communication between
+# | them is limited to invoking the ‘main’ function of the plug-in
+# | with some options+} and [-distribute-] {+waiting for+} it [-with source
+# | code in-] {+to return, that is+} a [-GPL-compliant way.-] {+borderline
+# | case.+}
+#, fuzzy
+#| 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 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."
+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 "
+"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."
+msgstr ""
+"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."
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"Using shared memory to communicate with complex data structures is pretty "
+"much equivalent to dynamic linking."
+msgstr ""
+"Usare memoria condivisa per comunicare con strutture di dati complesse è "
+"pressoché equivalente a linkare dinamicamente."
+
+#. type: Content of: <dl><dt>
msgid ""
"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? "
@@ -3616,23 +3706,34 @@
#. 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 for the main program makes no requirements for them."
-msgstr ""
-"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."
+"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 considered are separate works</a>."
+msgstr ""
#. 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 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."
+# | If the {+main+} program [-dynamically links plug-ins, and they make
+# | function calls to each other-] and [-share data structures, we believe
+# | they form-] {+the plugins are+} a single [-program, which must be treated
+# | as an extension of both the main-] {+combined+} program [-and the
+# | plug-ins. This-] {+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 a seperate
+# | from its plug-ins makes no requirements for the plug-ins.+}
+#, fuzzy
+#| 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 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."
+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 "
+"software license and distribute it with source code in a GPL-compliant way. "
+"A main program that is a seperate from its plug-ins makes no requirements "
+"for the plug-ins."
msgstr ""
"Se il programma invece è linkato dinamicamente ai plug-in, ed essi "
"effettuano reciproche chiamate a funzione e condividono delle strutture "
@@ -3641,16 +3742,6 @@
"Questo significa che essi devono essere rilasciati sotto la GPL o sotto una "
"licenza ad essa compatibile."
-#. type: Content of: <dl><dd><p>
-msgid ""
-"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."
-msgstr ""
-"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."
-
#. type: Content of: <dl><dt>
msgid ""
"Can I apply the GPL when writing a plug-in for a non-free program? <span "
@@ -3663,26 +3754,35 @@
#. type: Content of: <dl><dd><p>
msgid ""
-"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."
-msgstr ""
-"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."
+"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>."
+msgstr ""
#. 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."
+# | 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.
+#, fuzzy
+#| 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."
+msgid ""
+"If they form a single combined program this means that combination of the "
+"GPL-covered plug-in with the non-free main program would violate the GPL. "
+"However, you can resolve that legal problem by adding an exception to your "
+"plug-in's license, giving permission to link it with the non-free main "
+"program."
msgstr ""
"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 "
@@ -3712,23 +3812,25 @@
"\"#NFUseGPLPlugins\" >#NFUseGPLPlugins</a>)</span>"
#. type: Content of: <dl><dd><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-]
+# | {+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.
+#, fuzzy
+#| 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."
msgid ""
-"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."
-msgstr ""
-"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."
-
-#. 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 "
+"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 that "
"the terms of the GPL must be followed when the main program is distributed "
"for use with these plug-ins."
@@ -3744,11 +3846,9 @@
#. type: Content of: <dl><dd><p>
msgid ""
-"Using shared memory to communicate with complex data structures is pretty "
-"much equivalent to dynamic linking."
+"However, if they are separate works then the license of the plug-in makes no "
+"requirements about the main program."
msgstr ""
-"Usare memoria condivisa per comunicare con strutture di dati complesse è "
-"pressoché equivalente a linkare dinamicamente."
#. type: Content of: <dl><dt>
msgid ""
@@ -7908,6 +8008,51 @@
msgstr "Ultimo aggiornamento:"
#~ 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 for the main program makes no requirements for "
+#~ "them."
+#~ msgstr ""
+#~ "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."
+
+#~ msgid ""
+#~ "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."
+#~ msgstr ""
+#~ "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."
+
+#~ msgid ""
+#~ "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."
+#~ msgstr ""
+#~ "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."
+
+#~ msgid ""
+#~ "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."
+#~ msgstr ""
+#~ "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."
+
+#~ msgid ""
#~ "Yes, because the software as it is actually run includes the library."
#~ msgstr ""
#~ "Sì, perché il programma per come è effettivamente eseguito include la "
Index: licenses/po/gpl-faq.ja.po
===================================================================
RCS file: /web/www/www/licenses/po/gpl-faq.ja.po,v
retrieving revision 1.79
retrieving revision 1.80
diff -u -b -r1.79 -r1.80
--- licenses/po/gpl-faq.ja.po 17 Feb 2017 05:30:48 -0000 1.79
+++ licenses/po/gpl-faq.ja.po 10 Mar 2017 19:30:52 -0000 1.80
@@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: gpl-faq.html\n"
-"POT-Creation-Date: 2017-02-17 05:26+0000\n"
+"POT-Creation-Date: 2017-03-10 15:56+0000\n"
"PO-Revision-Date: 2017-01-11 09:42+0900\n"
"Last-Translator: NIIBE Yutaka <address@hidden>\n"
"Language-Team: Japanese <address@hidden>\n"
@@ -1165,6 +1165,18 @@
"ã?</a>"
#. type: Content of: <ul><li>
+#, fuzzy
+#| msgid ""
+#| "<a href=\"#GPLPluginsInNF\">Can I apply the GPL when writing a plug-in "
+#| "for a non-free program?</a>"
+msgid ""
+"<a href=\"#GPLPlugins\">When are a program and its plug-ins considered a "
+"single combined program?</a>"
+msgstr ""
+"<a href=\"#GPLPluginsInNF\">èªç±ã§ãªãããã°ã©ã
åãã®ãã©ã°ã¤ã³ã«GPLãé©ç¨ã"
+"ããã¨ã¯ã§ãã¾ãã?</a>"
+
+#. type: Content of: <ul><li>
msgid ""
"<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 "
@@ -3540,6 +3552,65 @@
msgstr "æ¹è¨BSDã©ã¤ã»ã³ã¹ã«ã¯å®£ä¼æ¡é
ãããã¾ãããããåé¡ããªããªãã¾ããã"
#. type: Content of: <dl><dt>
+#, fuzzy
+#| msgid ""
+#| "Can I apply the GPL when writing a plug-in for a non-free program? <span "
+#| "class=\"anchor-reference-id\">(<a href=\"#GPLPluginsInNF\" "
+#| ">#GPLPluginsInNF</a>)</span>"
+msgid ""
+"When are a program and its plug-ins considered a single combined program? "
+"<span class=\"anchor-reference-id\">(<a href=\"#GPLPlugins\" >#GPLPlugins</"
+"a>)</span>"
+msgstr ""
+"èªç±ã§ãªãããã°ã©ã
åãã®ãã©ã°ã¤ã³ã«GPLãé©ç¨ãããã¨ã¯ã§ãã¾ãã? <span "
+"class=\"anchor-reference-id\">(<a href=\"#GPLPluginsInNF\" >#GPLPluginsInNF</"
+"a>)</span>"
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"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."
+msgstr ""
+
+#. type: Content of: <dl><dd><p>
+#, fuzzy
+#| 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 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."
+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 "
+"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."
+msgstr ""
+"ããããã°ã©ã
ããã©ã°ã¤ã³ã¨åçã«ãªã³ã¯ããã¦ããããäºãã«ãã¡ã³ã¯ã·ã§ã³"
+"ã³ã¼ã«ã使ã£ã¦ãã¼ã¿æ§é ãå
±æãã¦ããå
´åããããã¯åä¸ã®ããã°ã©ã ãå½¢æã"
+"ã¦ããã¨ã¿ãªããã¾ãã®ã§ããã®åä¸ããã°ã©ã
ã¯ãã¡ã¤ã³ããã°ã©ã ã¨ãã©ã°ã¤ã³"
+"ã®ä¸¡æ¹ã®æ¡å¼µé¨åã¨ãã¦æ±ãããªããã°ãªãã¾ãããããªãã¯ãã©ã°ã¤ã³ãGPLãGPL"
+"ã¨ä¸¡ç«ããèªç±ã½ããã¦ã§ã¢ã»ã©ã¤ã»ã³ã¹ã§ã©ã¤ã»ã³ã¹ããªããã°ãªãããGPLã®æ¡é
"
+"ã«å¾ã£ã¦ã½ã¼ã¹ã³ã¼ãã¨ã¨ãã«é
å¸ããå¿
è¦ãããã¾ãã"
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"Using shared memory to communicate with complex data structures is pretty "
+"much equivalent to dynamic linking."
+msgstr ""
+"å
±æã¡ã¢ãªã使ããè¤éãªãã¼ã¿æ§é
ã§éä¿¡ãããã¨ã¯ãåçãªãªã³ã¯ã¨ã»ã¨ãã©å"
+"çã§ãã"
+
+#. type: Content of: <dl><dt>
msgid ""
"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? "
@@ -3553,22 +3624,26 @@
#. 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 for the main program makes no requirements for them."
-msgstr ""
-"ããã¯ããã°ã©ã
ãã©ã®ããã«ãã©ã°ã¤ã³ãå¼ã³åºããã«ä¾ãã¾ããããã°ã©ã
ã"
-"forkãexecã§ãã©ã°ã¤ã³ãå¼ã³åºããªãã°ããã©ã°ã¤ã³ã¯å¥ã®ããã°ã©ã
ã§ãããã¡"
-"ã¤ã³ããã°ã©ã
ã®ã©ã¤ã»ã³ã¹ã¯ãããã«ã¯ãªãã®æ¡ä»¶ã課ãã¾ããã"
+"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 considered are separate works</a>."
+msgstr ""
#. 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 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."
+#, fuzzy
+#| 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 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."
+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 "
+"software license and distribute it with source code in a GPL-compliant way. "
+"A main program that is a seperate from its plug-ins makes no requirements "
+"for the plug-ins."
msgstr ""
"ããããã°ã©ã
ããã©ã°ã¤ã³ã¨åçã«ãªã³ã¯ããã¦ããããäºãã«ãã¡ã³ã¯ã·ã§ã³"
"ã³ã¼ã«ã使ã£ã¦ãã¼ã¿æ§é ãå
±æãã¦ããå
´åããããã¯åä¸ã®ããã°ã©ã ãå½¢æã"
@@ -3577,16 +3652,6 @@
"ã¨ä¸¡ç«ããèªç±ã½ããã¦ã§ã¢ã»ã©ã¤ã»ã³ã¹ã§ã©ã¤ã»ã³ã¹ããªããã°ãªãããGPLã®æ¡é
"
"ã«å¾ã£ã¦ã½ã¼ã¹ã³ã¼ãã¨ã¨ãã«é
å¸ããå¿
è¦ãããã¾ãã"
-#. type: Content of: <dl><dd><p>
-msgid ""
-"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."
-msgstr ""
-"ããã°ã©ã
ããã©ã°ã¤ã³ã¨åçã«ãªã³ã¯ããã¦ãããããããã®éã®ã³ãã¥ãã±ã¼"
-"ã·ã§ã³ã¯ããã¤ãã®ãªãã·ã§ã³ã¨ã¨ãã«ãã©ã°ã¤ã³ã®ãmainãé¢æ°ãå¼ã³åºãã¦è¿å¤"
-"ãå¾
ã¤ã ãã¨ããå
´åã¯ãå¢çç·ä¸ã§å¾®å¦ãªã±ã¼ã¹ã¨ãªãã¾ãã"
-
#. type: Content of: <dl><dt>
msgid ""
"Can I apply the GPL when writing a plug-in for a non-free program? <span "
@@ -3599,24 +3664,27 @@
#. type: Content of: <dl><dd><p>
msgid ""
-"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."
-msgstr ""
-"ããããã°ã©ã
ãforkãexecã§ãã©ã°ã¤ã³ãå¼ã³åºããªãã°ããã©ã°ã¤ã³ã¯å¥ã®ãã"
-"ã°ã©ã ã§ããããã¡ã¤ã³ããã°ã©ã
ã®ã©ã¤ã»ã³ã¹ã¯ä½ã®æ¡ä»¶ã課ãã¾ãããã§ããã"
-"ããªãã¯ãã©ã°ã¤ã³ã«GPLãé©ç¨ã§ãã¾ãããç¹å¥ãªè¦ä»¶ã¯ããã¾ããã"
+"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>."
+msgstr ""
#. 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."
+#, fuzzy
+#| 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."
+msgid ""
+"If they form a single combined program this means that combination of the "
+"GPL-covered plug-in with the non-free main program would violate the GPL. "
+"However, you can resolve that legal problem by adding an exception to your "
+"plug-in's license, giving permission to link it with the non-free main "
+"program."
msgstr ""
"ããã°ã©ã
ããã©ã°ã¤ã³ã¨åçã«ãªã³ã¯ããããäºãã«ãã¡ã³ã¯ã·ã§ã³ã³ã¼ã«ã使ã£"
"ã¦ãã¼ã¿æ§é ãå
±æãã¦ããå
´åããããã¯åä¸ã®ããã°ã©ã ãå½¢æãã¦ããã¨è¦ãª"
@@ -3645,23 +3713,17 @@
"\"#NFUseGPLPlugins\" >#NFUseGPLPlugins</a>)</span>"
#. type: Content of: <dl><dd><p>
+#, fuzzy
+#| 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."
msgid ""
-"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."
-msgstr ""
-"ããã¯ããã°ã©ã
ãã©ã®ããã«ãã©ã°ã¤ã³ãå¼ã³åºããã«ããã¾ãããã¨ãã°ããã"
-"ã°ã©ã
ãåç´ãªforkã¨execã§ãã©ã°ã¤ã³ãèµ·åããéä¿¡ãã<em>ã
ã</em>ãªãã°ãã"
-"ã©ã°ã¤ã³ã¯å¥ã®ããã°ã©ã
ã§ããããã©ã°ã¤ã³ã®ã©ã¤ã»ã³ã¹ã¯ã¡ã¤ã³ããã°ã©ã ã«ãª"
-"ãã®è¦æ±ããã¾ããã"
-
-#. 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 "
+"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 that "
"the terms of the GPL must be followed when the main program is distributed "
"for use with these plug-ins."
@@ -3676,11 +3738,9 @@
#. type: Content of: <dl><dd><p>
msgid ""
-"Using shared memory to communicate with complex data structures is pretty "
-"much equivalent to dynamic linking."
+"However, if they are separate works then the license of the plug-in makes no "
+"requirements about the main program."
msgstr ""
-"å
±æã¡ã¢ãªã使ããè¤éãªãã¼ã¿æ§é
ã§éä¿¡ãããã¨ã¯ãåçãªãªã³ã¯ã¨ã»ã¨ãã©å"
-"çã§ãã"
#. type: Content of: <dl><dt>
msgid ""
@@ -7692,6 +7752,47 @@
msgstr "æçµæ´æ°:"
#~ 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 for the main program makes no requirements for "
+#~ "them."
+#~ msgstr ""
+#~ "ããã¯ããã°ã©ã
ãã©ã®ããã«ãã©ã°ã¤ã³ãå¼ã³åºããã«ä¾ãã¾ããããã°ã©ã
ã"
+#~
"forkãexecã§ãã©ã°ã¤ã³ãå¼ã³åºããªãã°ããã©ã°ã¤ã³ã¯å¥ã®ããã°ã©ã
ã§ããã"
+#~ "ã¡ã¤ã³ããã°ã©ã
ã®ã©ã¤ã»ã³ã¹ã¯ãããã«ã¯ãªãã®æ¡ä»¶ã課ãã¾ããã"
+
+#~ msgid ""
+#~ "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."
+#~ msgstr ""
+#~ "ããã°ã©ã
ããã©ã°ã¤ã³ã¨åçã«ãªã³ã¯ããã¦ãããããããã®éã®ã³ãã¥ãã±ã¼"
+#~
"ã·ã§ã³ã¯ããã¤ãã®ãªãã·ã§ã³ã¨ã¨ãã«ãã©ã°ã¤ã³ã®ãmainãé¢æ°ãå¼ã³åºãã¦è¿"
+#~ "å¤ãå¾
ã¤ã ãã¨ããå
´åã¯ãå¢çç·ä¸ã§å¾®å¦ãªã±ã¼ã¹ã¨ãªãã¾ãã"
+
+#~ msgid ""
+#~ "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."
+#~ msgstr ""
+#~ "ããããã°ã©ã
ãforkãexecã§ãã©ã°ã¤ã³ãå¼ã³åºããªãã°ããã©ã°ã¤ã³ã¯å¥ã®ã"
+#~ "ãã°ã©ã ã§ããããã¡ã¤ã³ããã°ã©ã
ã®ã©ã¤ã»ã³ã¹ã¯ä½ã®æ¡ä»¶ã課ãã¾ãããã§ã"
+#~
"ããããªãã¯ãã©ã°ã¤ã³ã«GPLãé©ç¨ã§ãã¾ãããç¹å¥ãªè¦ä»¶ã¯ããã¾ããã"
+
+#~ msgid ""
+#~ "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."
+#~ msgstr ""
+#~ "ããã¯ããã°ã©ã
ãã©ã®ããã«ãã©ã°ã¤ã³ãå¼ã³åºããã«ããã¾ãããã¨ãã°ãã"
+#~ "ãã°ã©ã
ãåç´ãªforkã¨execã§ãã©ã°ã¤ã³ãèµ·åããéä¿¡ãã<em>ã
ã</em>ãªã"
+#~ "ã°ããã©ã°ã¤ã³ã¯å¥ã®ããã°ã©ã
ã§ããããã©ã°ã¤ã³ã®ã©ã¤ã»ã³ã¹ã¯ã¡ã¤ã³ããã°"
+#~ "ã©ã ã«ãªãã®è¦æ±ããã¾ããã"
+
+#~ msgid ""
#~ "Yes, because the software as it is actually run includes the library."
#~ msgstr ""
#~ "ã¯ãããªããªããå®éã«å®è¡ãããããã°ã©ã
ã¯ã©ã¤ãã©ãªãå«ãã§ããããã§"
Index: licenses/po/gpl-faq.ru.po
===================================================================
RCS file: /web/www/www/licenses/po/gpl-faq.ru.po,v
retrieving revision 1.123
retrieving revision 1.124
diff -u -b -r1.123 -r1.124
--- licenses/po/gpl-faq.ru.po 28 Feb 2017 06:30:56 -0000 1.123
+++ licenses/po/gpl-faq.ru.po 10 Mar 2017 19:30:52 -0000 1.124
@@ -11,7 +11,7 @@
msgid ""
msgstr ""
"Project-Id-Version: gpl-faq.html\n"
-"POT-Creation-Date: 2017-02-17 05:26+0000\n"
+"POT-Creation-Date: 2017-03-10 15:56+0000\n"
"PO-Revision-Date: 2017-02-28 17:17+0000\n"
"Last-Translator: Ineiev <address@hidden>\n"
"Language-Team: Russian <address@hidden>\n"
@@ -19,6 +19,7 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"X-Outdated-Since: 2017-03-10 15:56+0000\n"
#. type: Content of: <title>
msgid ""
@@ -1190,6 +1191,21 @@
"</a>"
#. type: Content of: <ul><li>
+# | <a [-href=\"#GPLPluginsInNF\">Can I apply the GPL when writing-]
+# | {+href=\"#GPLPlugins\">When are+} a [-plug-in for-] {+program and its
+# | plug-ins considered+} a [-non-free-] {+single combined+} program?</a>
+#, fuzzy
+#| msgid ""
+#| "<a href=\"#GPLPluginsInNF\">Can I apply the GPL when writing a plug-in "
+#| "for a non-free program?</a>"
+msgid ""
+"<a href=\"#GPLPlugins\">When are a program and its plug-ins considered a "
+"single combined program?</a>"
+msgstr ""
+"<a href=\"#GPLPluginsInNF\">ÐÐ¾Ð³Ñ Ñ Ð¿ÑименÑÑÑ GPL, когда
пиÑÑ Ð²Ð½ÐµÑний модÑÐ»Ñ "
+"к неÑвободной пÑогÑамме?</a>"
+
+#. type: Content of: <ul><li>
msgid ""
"<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 "
@@ -3598,6 +3614,80 @@
"РпеÑеÑмоÑÑенной лиÑензии BSD пÑнкÑа о
Ñекламе неÑ, ÑÑо ÑÑÑÑанÑÐµÑ Ð¿ÑоблемÑ."
#. type: Content of: <dl><dt>
+# | [-Can I apply the GPL when writing-]{+When are+} a [-plug-in for-]
+# | {+program and its plug-ins considered+} a [-non-free-] {+single combined+}
+# | program? <span class=\"anchor-reference-id\">(<a
+# | [-href=\"#GPLPluginsInNF\" >#GPLPluginsInNF</a>)</span>-]
+# | {+href=\"#GPLPlugins\" >#GPLPlugins</a>)</span>+}
+#, fuzzy
+#| msgid ""
+#| "Can I apply the GPL when writing a plug-in for a non-free program? <span "
+#| "class=\"anchor-reference-id\">(<a href=\"#GPLPluginsInNF\" "
+#| ">#GPLPluginsInNF</a>)</span>"
+msgid ""
+"When are a program and its plug-ins considered a single combined program? "
+"<span class=\"anchor-reference-id\">(<a href=\"#GPLPlugins\" >#GPLPlugins</"
+"a>)</span>"
+msgstr ""
+"ÐÐ¾Ð³Ñ Ñ Ð¿ÑименÑÑÑ GPL, когда пиÑÑ Ð²Ð½ÐµÑний
модÑÐ»Ñ Ðº неÑвободной пÑогÑамме? "
+"<span class=\"anchor-reference-id\">(<a href=\"#GPLPluginsInNF\" "
+">#GPLPluginsInNF</a>)</span>"
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"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."
+msgstr ""
+
+#. type: Content of: <dl><dd><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. [-This means you must license-] {+If+}
+# | the [-plug-in under-] {+main program dynamically links plug-ins, but+} the
+# | [-GPL or a GPL-compatible free software license-] {+communication between
+# | them is limited to invoking the ‘main’ function of the plug-in
+# | with some options+} and [-distribute-] {+waiting for+} it [-with source
+# | code in-] {+to return, that is+} a [-GPL-compliant way.-] {+borderline
+# | case.+}
+#, fuzzy
+#| 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 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."
+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 "
+"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."
+msgstr ""
+"ÐÑли пÑогÑамма динамиÑеÑки компонÑеÑÑÑ Ñ
модÑлÑми и они вÑзÑваÑÑ ÑÑнкÑии "
+"дÑÑг из дÑÑга и ÑазделÑÑÑ Ð¾Ð±Ñие ÑÑÑÑкÑÑÑÑ
даннÑÑ
, Ð¼Ñ ÑбежденÑ, ÑÑо они "
+"ÑоÑмиÑÑÑÑ ÐµÐ´Ð¸Ð½ÑÑ Ð¿ÑогÑаммÑ, коÑоÑаÑ
должна ÑаÑÑмаÑÑиваÑÑÑÑ ÐºÐ°Ðº ÑаÑÑиÑение и "
+"главной пÑогÑаммÑ, и модÑлей. ÐÑо знаÑиÑ,
ÑÑо Ð²Ñ Ð´Ð¾Ð»Ð¶Ð½Ñ Ð²ÑпÑÑкаÑÑ Ð¼Ð¾Ð´ÑÐ»Ñ Ð¿Ð¾Ð´ "
+"GPL или ÑовмеÑÑимой Ñ Ð½ÐµÐ¹ лиÑензией
ÑвободнÑÑ
пÑогÑамм и ÑаÑпÑоÑÑÑанÑÑÑ ÐµÐ³Ð¾ "
+"Ñ Ð¸ÑÑ
однÑм ÑекÑÑом Ñак, ÑÑÐ¾Ð±Ñ ÑÑо бÑло
ÑовмеÑÑимо Ñ GPL."
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"Using shared memory to communicate with complex data structures is pretty "
+"much equivalent to dynamic linking."
+msgstr ""
+"ÐÑименение обÑей памÑÑи Ð´Ð»Ñ Ð¾Ð±Ð¼ÐµÐ½Ð°
ÑложнÑми ÑÑÑÑкÑÑÑами даннÑÑ
вполне "
+"ÑквиваленÑно динамиÑеÑÐºÐ¾Ð¼Ñ ÑвÑзÑваниÑ."
+
+#. type: Content of: <dl><dt>
msgid ""
"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? "
@@ -3611,23 +3701,34 @@
#. 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 for the main program makes no requirements for them."
-msgstr ""
-"ÐÑо завиÑÐ¸Ñ Ð¾Ñ Ñого, как пÑогÑамма
задейÑÑвÑÐµÑ Ñвои внеÑние модÑли. ÐÑли "
-"пÑогÑамма полÑзÑеÑÑÑ Ð´Ð»Ñ ÑÑого вÑзовами
<em>fork</em> или <em>exec</em>, Ñо "
-"модÑли — ÑÑо оÑделÑнÑе пÑогÑаммÑ,
Ñак ÑÑо лиÑÐµÐ½Ð·Ð¸Ñ Ð³Ð»Ð°Ð²Ð½Ð¾Ð¹ "
-"пÑогÑÐ°Ð¼Ð¼Ñ Ð½Ðµ пÑедÑÑвлÑÐµÑ Ðº ним никакиÑ
ÑÑебований."
+"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 considered are separate works</a>."
+msgstr ""
#. 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 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."
+# | If the {+main+} program [-dynamically links plug-ins, and they make
+# | function calls to each other-] and [-share data structures, we believe
+# | they form-] {+the plugins are+} a single [-program, which must be treated
+# | as an extension of both the main-] {+combined+} program [-and the
+# | plug-ins. This-] {+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 a seperate
+# | from its plug-ins makes no requirements for the plug-ins.+}
+#, fuzzy
+#| 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 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."
+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 "
+"software license and distribute it with source code in a GPL-compliant way. "
+"A main program that is a seperate from its plug-ins makes no requirements "
+"for the plug-ins."
msgstr ""
"ÐÑли пÑогÑамма динамиÑеÑки компонÑеÑÑÑ Ñ
модÑлÑми и они вÑзÑваÑÑ ÑÑнкÑии "
"дÑÑг из дÑÑга и ÑазделÑÑÑ Ð¾Ð±Ñие ÑÑÑÑкÑÑÑÑ
даннÑÑ
, Ð¼Ñ ÑбежденÑ, ÑÑо они "
@@ -3636,17 +3737,6 @@
"GPL или ÑовмеÑÑимой Ñ Ð½ÐµÐ¹ лиÑензией
ÑвободнÑÑ
пÑогÑамм и ÑаÑпÑоÑÑÑанÑÑÑ ÐµÐ³Ð¾ "
"Ñ Ð¸ÑÑ
однÑм ÑекÑÑом Ñак, ÑÑÐ¾Ð±Ñ ÑÑо бÑло
ÑовмеÑÑимо Ñ GPL."
-#. type: Content of: <dl><dd><p>
-msgid ""
-"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."
-msgstr ""
-"Ðак пÑеделÑнÑй Ð¼Ð¾Ð¶ÐµÑ ÑаÑÑмаÑÑиваÑÑÑÑ
ÑлÑÑай, когда пÑогÑамма динамиÑеÑки "
-"компонÑеÑÑÑ Ñ Ð¼Ð¾Ð´ÑлÑми, но ÑообÑение
Ð¼ÐµÐ¶Ð´Ñ Ð½Ð¸Ð¼Ð¸ огÑаниÑиваеÑÑÑ Ð²Ñзовом "
-"“главной” ÑÑнкÑии модÑÐ»Ñ Ñ
некоÑоÑÑми аÑгÑменÑами и ожиданием, "
-"когда пÑÐ¾Ð¸Ð·Ð¾Ð¹Ð´ÐµÑ Ð²Ð¾Ð·Ð²ÑÐ°Ñ Ð¸Ð· ÑÑнкÑии."
-
#. type: Content of: <dl><dt>
msgid ""
"Can I apply the GPL when writing a plug-in for a non-free program? <span "
@@ -3659,25 +3749,35 @@
#. type: Content of: <dl><dd><p>
msgid ""
-"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."
-msgstr ""
-"ÐÑли пÑогÑамма полÑзÑеÑÑÑ Ð²Ñзовами
<em>fork</em> и <em>exec</em> Ð´Ð»Ñ Ñого, "
-"ÑÑÐ¾Ð±Ñ Ð·Ð°Ð´ÐµÐ¹ÑÑвоваÑÑ Ð¼Ð¾Ð´ÑлÑ, Ñо модÑли
ÑвлÑÑÑÑÑ Ð¾ÑделÑнÑми пÑогÑаммами, Ñак "
-"ÑÑо лиÑÐµÐ½Ð·Ð¸Ñ Ð³Ð»Ð°Ð²Ð½Ð¾Ð¹ пÑогÑÐ°Ð¼Ð¼Ñ Ð½Ðµ
пÑедÑÑвлÑÐµÑ Ðº ним никакиÑ
ÑÑебований. Так "
-"ÑÑо Ð²Ñ Ð¼Ð¾Ð¶ÐµÑе пÑименÑÑÑ GPL Ð´Ð»Ñ Ð¼Ð¾Ð´ÑÐ»Ñ Ð¸
никакиÑ
оÑобÑÑ
ÑÑебований неÑ."
+"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>."
+msgstr ""
#. 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."
+# | 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.
+#, fuzzy
+#| 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."
+msgid ""
+"If they form a single combined program this means that combination of the "
+"GPL-covered plug-in with the non-free main program would violate the GPL. "
+"However, you can resolve that legal problem by adding an exception to your "
+"plug-in's license, giving permission to link it with the non-free main "
+"program."
msgstr ""
"ÐÑли пÑогÑамма динамиÑеÑки компонÑеÑÑÑ Ñ
модÑлÑми и они вÑзÑваÑÑ ÑÑнкÑии "
"дÑÑг из дÑÑга и ÑазделÑÑÑ Ð¾Ð±Ñие ÑÑÑÑкÑÑÑÑ
даннÑÑ
, Ð¼Ñ ÑбежденÑ, ÑÑо они "
@@ -3706,24 +3806,25 @@
"\"#NFUseGPLPlugins\" >#NFUseGPLPlugins</a>)</span>"
#. type: Content of: <dl><dd><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-]
+# | {+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.
+#, fuzzy
+#| 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."
msgid ""
-"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."
-msgstr ""
-"ÐÑо завиÑÐ¸Ñ Ð¾Ñ Ñого, как пÑогÑамма
задейÑÑвÑÐµÑ Ñвои внеÑние модÑли. "
-"ÐапÑимеÑ, еÑли пÑогÑамма иÑполÑзÑеÑ
<em>ÑолÑко</em> пÑоÑÑÑе вÑÐ·Ð¾Ð²Ñ <em>fork</"
-"em> и <em>exec</em> Ð´Ð»Ñ Ð·Ð°Ð³ÑÑзки и ÑвÑзи Ñ
модÑлÑми, Ñо ÑÑи модÑли ÑвлÑÑÑÑÑ "
-"оÑделÑнÑми пÑогÑаммами, Ñак ÑÑо лиÑензиÑ
модÑÐ»Ñ Ð½Ðµ пÑедÑÑвлÑÐµÑ ÑÑебований к "
-"главной пÑогÑамме."
-
-#. 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 "
+"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 that "
"the terms of the GPL must be followed when the main program is distributed "
"for use with these plug-ins."
@@ -3738,11 +3839,9 @@
#. type: Content of: <dl><dd><p>
msgid ""
-"Using shared memory to communicate with complex data structures is pretty "
-"much equivalent to dynamic linking."
+"However, if they are separate works then the license of the plug-in makes no "
+"requirements about the main program."
msgstr ""
-"ÐÑименение обÑей памÑÑи Ð´Ð»Ñ Ð¾Ð±Ð¼ÐµÐ½Ð°
ÑложнÑми ÑÑÑÑкÑÑÑами даннÑÑ
вполне "
-"ÑквиваленÑно динамиÑеÑÐºÐ¾Ð¼Ñ ÑвÑзÑваниÑ."
#. type: Content of: <dl><dt>
msgid ""
@@ -7881,6 +7980,52 @@
msgstr "Ðбновлено:"
#~ 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 for the main program makes no requirements for "
+#~ "them."
+#~ msgstr ""
+#~ "ÐÑо завиÑÐ¸Ñ Ð¾Ñ Ñого, как пÑогÑамма
задейÑÑвÑÐµÑ Ñвои внеÑние модÑли. ÐÑли "
+#~ "пÑогÑамма полÑзÑеÑÑÑ Ð´Ð»Ñ ÑÑого вÑзовами
<em>fork</em> или <em>exec</em>, "
+#~ "Ñо модÑли — ÑÑо оÑделÑнÑе
пÑогÑаммÑ, Ñак ÑÑо лиÑÐµÐ½Ð·Ð¸Ñ Ð³Ð»Ð°Ð²Ð½Ð¾Ð¹ "
+#~ "пÑогÑÐ°Ð¼Ð¼Ñ Ð½Ðµ пÑедÑÑвлÑÐµÑ Ðº ним никакиÑ
ÑÑебований."
+
+#~ msgid ""
+#~ "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."
+#~ msgstr ""
+#~ "Ðак пÑеделÑнÑй Ð¼Ð¾Ð¶ÐµÑ ÑаÑÑмаÑÑиваÑÑÑÑ
ÑлÑÑай, когда пÑогÑамма динамиÑеÑки "
+#~ "компонÑеÑÑÑ Ñ Ð¼Ð¾Ð´ÑлÑми, но ÑообÑение
Ð¼ÐµÐ¶Ð´Ñ Ð½Ð¸Ð¼Ð¸ огÑаниÑиваеÑÑÑ Ð²Ñзовом "
+#~ "“главной” ÑÑнкÑии модÑÐ»Ñ Ñ
некоÑоÑÑми аÑгÑменÑами и "
+#~ "ожиданием, когда пÑÐ¾Ð¸Ð·Ð¾Ð¹Ð´ÐµÑ Ð²Ð¾Ð·Ð²ÑÐ°Ñ Ð¸Ð·
ÑÑнкÑии."
+
+#~ msgid ""
+#~ "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."
+#~ msgstr ""
+#~ "ÐÑли пÑогÑамма полÑзÑеÑÑÑ Ð²Ñзовами
<em>fork</em> и <em>exec</em> Ð´Ð»Ñ "
+#~ "Ñого, ÑÑÐ¾Ð±Ñ Ð·Ð°Ð´ÐµÐ¹ÑÑвоваÑÑ Ð¼Ð¾Ð´ÑлÑ, Ñо
модÑли ÑвлÑÑÑÑÑ Ð¾ÑделÑнÑми "
+#~ "пÑогÑаммами, Ñак ÑÑо лиÑÐµÐ½Ð·Ð¸Ñ Ð³Ð»Ð°Ð²Ð½Ð¾Ð¹
пÑогÑÐ°Ð¼Ð¼Ñ Ð½Ðµ пÑедÑÑвлÑÐµÑ Ðº ним "
+#~ "никакиÑ
ÑÑебований. Так ÑÑо Ð²Ñ Ð¼Ð¾Ð¶ÐµÑе
пÑименÑÑÑ GPL Ð´Ð»Ñ Ð¼Ð¾Ð´ÑÐ»Ñ Ð¸ никакиÑ
"
+#~ "оÑобÑÑ
ÑÑебований неÑ."
+
+#~ msgid ""
+#~ "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."
+#~ msgstr ""
+#~ "ÐÑо завиÑÐ¸Ñ Ð¾Ñ Ñого, как пÑогÑамма
задейÑÑвÑÐµÑ Ñвои внеÑние модÑли. "
+#~ "ÐапÑимеÑ, еÑли пÑогÑамма иÑполÑзÑеÑ
<em>ÑолÑко</em> пÑоÑÑÑе вÑÐ·Ð¾Ð²Ñ "
+#~ "<em>fork</em> и <em>exec</em> Ð´Ð»Ñ Ð·Ð°Ð³ÑÑзки и ÑвÑзи Ñ
модÑлÑми, Ñо ÑÑи "
+#~ "модÑли ÑвлÑÑÑÑÑ Ð¾ÑделÑнÑми пÑогÑаммами,
Ñак ÑÑо лиÑÐµÐ½Ð·Ð¸Ñ Ð¼Ð¾Ð´ÑÐ»Ñ Ð½Ðµ "
+#~ "пÑедÑÑвлÑÐµÑ ÑÑебований к главной
пÑогÑамме."
+
+#~ msgid ""
#~ "Yes, because the software as it is actually run includes the library."
#~ msgstr ""
#~ "Ðа, поÑÐ¾Ð¼Ñ ÑÑо пÑогÑамма, коÑоÑÐ°Ñ Ð½Ð°
Ñамом деле вÑполнÑеÑÑÑ, вклÑÑÐ°ÐµÑ Ð² "
Index: licenses/po/gpl-faq.ta.po
===================================================================
RCS file: /web/www/www/licenses/po/gpl-faq.ta.po,v
retrieving revision 1.63
retrieving revision 1.64
diff -u -b -r1.63 -r1.64
--- licenses/po/gpl-faq.ta.po 17 Feb 2017 05:30:48 -0000 1.63
+++ licenses/po/gpl-faq.ta.po 10 Mar 2017 19:30:52 -0000 1.64
@@ -9,7 +9,7 @@
msgid ""
msgstr ""
"Project-Id-Version: gpl-faq.html\n"
-"POT-Creation-Date: 2017-02-17 05:26+0000\n"
+"POT-Creation-Date: 2017-03-10 15:56+0000\n"
"PO-Revision-Date: 2010-06-20 15:55+0530\n"
"Last-Translator: Amachu <address@hidden>\n"
"Language-Team: Tamil <address@hidden>\n"
@@ -883,6 +883,12 @@
#. type: Content of: <ul><li>
msgid ""
+"<a href=\"#GPLPlugins\">When are a program and its plug-ins considered a "
+"single combined program?</a>"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
"<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>"
@@ -2470,35 +2476,69 @@
msgstr ""
#. type: Content of: <dl><dt>
+#, fuzzy
+#| msgid ""
+#| "Are there translations of the GPL into other languages? <span class="
+#| "\"anchor-reference-id\">(<a href=\"#GPLTranslations\" >#GPLTranslations</"
+#| "a>)</span>"
msgid ""
-"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>"
+"When are a program and its plug-ins considered a single combined program? "
+"<span class=\"anchor-reference-id\">(<a href=\"#GPLPlugins\" >#GPLPlugins</"
+"a>)</span>"
msgstr ""
+"GPLà®à®©à¯ à®®à¯à®´à®¿à®ªà¯à®¯à®°à¯à®ªà¯à®ªà¯à®à®³à¯ பிற
à®®à¯à®´à®¿à®à®³à®¿à®²à¯ à®à®¿à®à¯à®à¯à®à®¿à®±à®¤à®¾? <span
class=\"anchor-reference-"
+"id\">(<a href=\"#GPLTranslations\" >#GPLTranslations</a>)</span>"
#. 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 for the main program makes no requirements for them."
+"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."
msgstr ""
#. 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 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."
+"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."
msgstr ""
#. type: Content of: <dl><dd><p>
msgid ""
-"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."
+"Using shared memory to communicate with complex data structures is pretty "
+"much equivalent to dynamic linking."
+msgstr ""
+
+#. type: Content of: <dl><dt>
+msgid ""
+"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>"
+msgstr ""
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"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 considered are separate works</a>."
+msgstr ""
+
+#. 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 "
+"software license and distribute it with source code in a GPL-compliant way. "
+"A main program that is a seperate from its plug-ins makes no requirements "
+"for the plug-ins."
msgstr ""
#. type: Content of: <dl><dt>
@@ -2510,21 +2550,18 @@
#. type: Content of: <dl><dd><p>
msgid ""
-"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."
+"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>."
msgstr ""
#. 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."
+"If they form a single combined program this means that combination of the "
+"GPL-covered plug-in with the non-free main program would violate the GPL. "
+"However, you can resolve that legal problem by adding an exception to your "
+"plug-in's license, giving permission to link it with the non-free main "
+"program."
msgstr ""
#. type: Content of: <dl><dd><p>
@@ -2542,18 +2579,7 @@
#. type: Content of: <dl><dd><p>
msgid ""
-"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."
-msgstr ""
-
-#. 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 "
+"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 that "
"the terms of the GPL must be followed when the main program is distributed "
"for use with these plug-ins."
@@ -2561,8 +2587,8 @@
#. type: Content of: <dl><dd><p>
msgid ""
-"Using shared memory to communicate with complex data structures is pretty "
-"much equivalent to dynamic linking."
+"However, if they are separate works then the license of the plug-in makes no "
+"requirements about the main program."
msgstr ""
#. type: Content of: <dl><dt>
Index: proprietary/po/malware-apple.de.po
===================================================================
RCS file: /web/www/www/proprietary/po/malware-apple.de.po,v
retrieving revision 1.65
retrieving revision 1.66
diff -u -b -r1.65 -r1.66
--- proprietary/po/malware-apple.de.po 1 Feb 2017 06:59:54 -0000 1.65
+++ proprietary/po/malware-apple.de.po 10 Mar 2017 19:30:52 -0000 1.66
@@ -7,7 +7,7 @@
msgstr ""
"Project-Id-Version: malware-apple.html\n"
"Report-Msgid-Bugs-To: Webmasters <address@hidden>\n"
-"POT-Creation-Date: 2017-02-01 06:56+0000\n"
+"POT-Creation-Date: 2017-03-10 19:26+0000\n"
"PO-Revision-Date: 2017-01-25 22:00+0100\n"
"Last-Translator: Jоегg Kоhпе <joeko (AT) online [PUNKT] de>\n"
"Language-Team: German <address@hidden>\n"
@@ -494,6 +494,15 @@
#. type: Content of: <ul><li><p>
msgid ""
+"Apple proposes <a href=\"https://www.theguardian.com/technology/2017/feb/15/";
+"apple-removing-iphone-home-button-fingerprint-scanning-\\ screen\">a "
+"fingerprint-scanning touch screen</a> — which would mean no way to use "
+"it without having your fingerprints taken. Users would have no way to tell "
+"whether the phone is snooping on them."
+msgstr ""
+
+#. type: Content of: <ul><li><p>
+msgid ""
"iPhones <a href=\"https://theintercept.com/2016/11/17/iphones-secretly-send-";
"call-history-to-apple-security-firm-says\">send lots of personal data to "
"Apple's servers</a>. Big Brother can get them from there."
Index: proprietary/po/malware-apple.es.po
===================================================================
RCS file: /web/www/www/proprietary/po/malware-apple.es.po,v
retrieving revision 1.65
retrieving revision 1.66
diff -u -b -r1.65 -r1.66
--- proprietary/po/malware-apple.es.po 2 Feb 2017 09:42:15 -0000 1.65
+++ proprietary/po/malware-apple.es.po 10 Mar 2017 19:30:52 -0000 1.66
@@ -8,7 +8,7 @@
msgid ""
msgstr ""
"Project-Id-Version: malware-apple.html\n"
-"POT-Creation-Date: 2017-02-02 10:41+0100\n"
+"POT-Creation-Date: 2017-03-10 19:26+0000\n"
"PO-Revision-Date: \n"
"Last-Translator: Javier Fdez. Retenaga <address@hidden>\n"
"Language-Team: Spanish <address@hidden>\n"
@@ -16,6 +16,7 @@
"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.6.10\n"
"Plural-Forms: nplurals=2; plural=(n!=1);\n"
@@ -457,6 +458,15 @@
#. type: Content of: <ul><li><p>
msgid ""
+"Apple proposes <a href=\"https://www.theguardian.com/technology/2017/feb/15/";
+"apple-removing-iphone-home-button-fingerprint-scanning-\\ screen\">a "
+"fingerprint-scanning touch screen</a> — which would mean no way to use "
+"it without having your fingerprints taken. Users would have no way to tell "
+"whether the phone is snooping on them."
+msgstr ""
+
+#. type: Content of: <ul><li><p>
+msgid ""
"iPhones <a href=\"https://theintercept.com/2016/11/17/iphones-secretly-send-";
"call-history-to-apple-security-firm-says\">send lots of personal data to "
"Apple's servers</a>. Big Brother can get them from there."
Index: proprietary/po/malware-apple.fr.po
===================================================================
RCS file: /web/www/www/proprietary/po/malware-apple.fr.po,v
retrieving revision 1.62
retrieving revision 1.63
diff -u -b -r1.62 -r1.63
--- proprietary/po/malware-apple.fr.po 1 Feb 2017 11:23:37 -0000 1.62
+++ proprietary/po/malware-apple.fr.po 10 Mar 2017 19:30:52 -0000 1.63
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: malware-apple.html\n"
-"POT-Creation-Date: 2017-02-01 06:56+0000\n"
+"POT-Creation-Date: 2017-03-10 19:26+0000\n"
"PO-Revision-Date: 2017-02-01 12:21+0100\n"
"Last-Translator: Sébastien Poher <sbphr @T volted.net>\n"
"Language-Team: French <address@hidden>\n"
@@ -15,6 +15,7 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"X-Outdated-Since: 2017-03-10 19:26+0000\n"
"X-Generator: Gtranslator 2.91.5\n"
"Plural-Forms: \n"
@@ -454,6 +455,15 @@
#. type: Content of: <ul><li><p>
msgid ""
+"Apple proposes <a href=\"https://www.theguardian.com/technology/2017/feb/15/";
+"apple-removing-iphone-home-button-fingerprint-scanning-\\ screen\">a "
+"fingerprint-scanning touch screen</a> — which would mean no way to use "
+"it without having your fingerprints taken. Users would have no way to tell "
+"whether the phone is snooping on them."
+msgstr ""
+
+#. type: Content of: <ul><li><p>
+msgid ""
"iPhones <a href=\"https://theintercept.com/2016/11/17/iphones-secretly-send-";
"call-history-to-apple-security-firm-says\">send lots of personal data to "
"Apple's servers</a>. Big Brother can get them from there."
Index: proprietary/po/malware-apple.it.po
===================================================================
RCS file: /web/www/www/proprietary/po/malware-apple.it.po,v
retrieving revision 1.69
retrieving revision 1.70
diff -u -b -r1.69 -r1.70
--- proprietary/po/malware-apple.it.po 5 Mar 2017 13:59:49 -0000 1.69
+++ proprietary/po/malware-apple.it.po 10 Mar 2017 19:30:52 -0000 1.70
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: malware-apple.html\n"
-"POT-Creation-Date: 2017-02-01 06:56+0000\n"
+"POT-Creation-Date: 2017-03-10 19:26+0000\n"
"PO-Revision-Date: 2016-12-08 21:48+0100\n"
"Last-Translator: Andrea Pescetti <address@hidden>\n"
"Language-Team: Italian <address@hidden>\n"
@@ -436,6 +436,15 @@
#. type: Content of: <ul><li><p>
msgid ""
+"Apple proposes <a href=\"https://www.theguardian.com/technology/2017/feb/15/";
+"apple-removing-iphone-home-button-fingerprint-scanning-\\ screen\">a "
+"fingerprint-scanning touch screen</a> — which would mean no way to use "
+"it without having your fingerprints taken. Users would have no way to tell "
+"whether the phone is snooping on them."
+msgstr ""
+
+#. type: Content of: <ul><li><p>
+msgid ""
"iPhones <a href=\"https://theintercept.com/2016/11/17/iphones-secretly-send-";
"call-history-to-apple-security-firm-says\">send lots of personal data to "
"Apple's servers</a>. Big Brother can get them from there."
Index: proprietary/po/malware-apple.ja.po
===================================================================
RCS file: /web/www/www/proprietary/po/malware-apple.ja.po,v
retrieving revision 1.63
retrieving revision 1.64
diff -u -b -r1.63 -r1.64
--- proprietary/po/malware-apple.ja.po 1 Feb 2017 06:59:54 -0000 1.63
+++ proprietary/po/malware-apple.ja.po 10 Mar 2017 19:30:52 -0000 1.64
@@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: malware-apple.html\n"
-"POT-Creation-Date: 2017-02-01 06:56+0000\n"
+"POT-Creation-Date: 2017-03-10 19:26+0000\n"
"PO-Revision-Date: 2016-12-20 14:42+0900\n"
"Last-Translator: NIIBE Yutaka <address@hidden>\n"
"Language-Team: Japanese <address@hidden>\n"
@@ -426,6 +426,15 @@
#. type: Content of: <ul><li><p>
msgid ""
+"Apple proposes <a href=\"https://www.theguardian.com/technology/2017/feb/15/";
+"apple-removing-iphone-home-button-fingerprint-scanning-\\ screen\">a "
+"fingerprint-scanning touch screen</a> — which would mean no way to use "
+"it without having your fingerprints taken. Users would have no way to tell "
+"whether the phone is snooping on them."
+msgstr ""
+
+#. type: Content of: <ul><li><p>
+msgid ""
"iPhones <a href=\"https://theintercept.com/2016/11/17/iphones-secretly-send-";
"call-history-to-apple-security-firm-says\">send lots of personal data to "
"Apple's servers</a>. Big Brother can get them from there."
Index: proprietary/po/malware-apple.nl.po
===================================================================
RCS file: /web/www/www/proprietary/po/malware-apple.nl.po,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -b -r1.19 -r1.20
--- proprietary/po/malware-apple.nl.po 1 Feb 2017 06:59:54 -0000 1.19
+++ proprietary/po/malware-apple.nl.po 10 Mar 2017 19:30:52 -0000 1.20
@@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: malware-apple.html\n"
-"POT-Creation-Date: 2017-02-01 06:56+0000\n"
+"POT-Creation-Date: 2017-03-10 19:26+0000\n"
"PO-Revision-Date: 2017-01-10 22:15+0100\n"
"Last-Translator: Justin van Steijn <address@hidden>\n"
"Language-Team: Dutch <address@hidden>\n"
@@ -439,6 +439,15 @@
#. type: Content of: <ul><li><p>
msgid ""
+"Apple proposes <a href=\"https://www.theguardian.com/technology/2017/feb/15/";
+"apple-removing-iphone-home-button-fingerprint-scanning-\\ screen\">a "
+"fingerprint-scanning touch screen</a> — which would mean no way to use "
+"it without having your fingerprints taken. Users would have no way to tell "
+"whether the phone is snooping on them."
+msgstr ""
+
+#. type: Content of: <ul><li><p>
+msgid ""
"iPhones <a href=\"https://theintercept.com/2016/11/17/iphones-secretly-send-";
"call-history-to-apple-security-firm-says\">send lots of personal data to "
"Apple's servers</a>. Big Brother can get them from there."
Index: proprietary/po/malware-apple.pot
===================================================================
RCS file: /web/www/www/proprietary/po/malware-apple.pot,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -b -r1.31 -r1.32
--- proprietary/po/malware-apple.pot 1 Feb 2017 06:59:54 -0000 1.31
+++ proprietary/po/malware-apple.pot 10 Mar 2017 19:30:52 -0000 1.32
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: malware-apple.html\n"
-"POT-Creation-Date: 2017-02-01 06:56+0000\n"
+"POT-Creation-Date: 2017-03-10 19:26+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <address@hidden>\n"
"Language-Team: LANGUAGE <address@hidden>\n"
@@ -329,6 +329,15 @@
#. type: Content of: <ul><li><p>
msgid ""
+"Apple proposes <a "
+"href=\"https://www.theguardian.com/technology/2017/feb/15/apple-removing-iphone-home-button-fingerprint-scanning-\\
"
+"screen\">a fingerprint-scanning touch screen</a> — which would mean no "
+"way to use it without having your fingerprints taken. Users would have no "
+"way to tell whether the phone is snooping on them."
+msgstr ""
+
+#. type: Content of: <ul><li><p>
+msgid ""
"iPhones <a "
"href=\"https://theintercept.com/2016/11/17/iphones-secretly-send-call-history-to-apple-security-firm-says\";>send
"
"lots of personal data to Apple's servers</a>. Big Brother can get them from "
Index: proprietary/po/malware-apple.ru.po
===================================================================
RCS file: /web/www/www/proprietary/po/malware-apple.ru.po,v
retrieving revision 1.87
retrieving revision 1.88
diff -u -b -r1.87 -r1.88
--- proprietary/po/malware-apple.ru.po 1 Feb 2017 12:01:17 -0000 1.87
+++ proprietary/po/malware-apple.ru.po 10 Mar 2017 19:30:52 -0000 1.88
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: malware-apple.html\n"
-"POT-Creation-Date: 2017-02-01 06:56+0000\n"
+"POT-Creation-Date: 2017-03-10 19:26+0000\n"
"PO-Revision-Date: 2017-02-01 17:51+0000\n"
"Last-Translator: Ineiev <address@hidden>\n"
"Language-Team: Russian <address@hidden>\n"
@@ -15,6 +15,7 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"X-Outdated-Since: 2017-03-10 19:26+0000\n"
#. type: Content of: <title>
msgid ""
@@ -447,6 +448,15 @@
#. type: Content of: <ul><li><p>
msgid ""
+"Apple proposes <a href=\"https://www.theguardian.com/technology/2017/feb/15/";
+"apple-removing-iphone-home-button-fingerprint-scanning-\\ screen\">a "
+"fingerprint-scanning touch screen</a> — which would mean no way to use "
+"it without having your fingerprints taken. Users would have no way to tell "
+"whether the phone is snooping on them."
+msgstr ""
+
+#. type: Content of: <ul><li><p>
+msgid ""
"iPhones <a href=\"https://theintercept.com/2016/11/17/iphones-secretly-send-";
"call-history-to-apple-security-firm-says\">send lots of personal data to "
"Apple's servers</a>. Big Brother can get them from there."
Index: proprietary/po/proprietary-surveillance.de.po
===================================================================
RCS file: /web/www/www/proprietary/po/proprietary-surveillance.de.po,v
retrieving revision 1.114
retrieving revision 1.115
diff -u -b -r1.114 -r1.115
--- proprietary/po/proprietary-surveillance.de.po 9 Mar 2017 23:59:32
-0000 1.114
+++ proprietary/po/proprietary-surveillance.de.po 10 Mar 2017 19:30:53
-0000 1.115
@@ -7,7 +7,7 @@
msgstr ""
"Project-Id-Version: proprietary-surveillance.html\n"
"Report-Msgid-Bugs-To: Webmasters <address@hidden>\n"
-"POT-Creation-Date: 2017-03-09 23:56+0000\n"
+"POT-Creation-Date: 2017-03-10 19:26+0000\n"
"PO-Revision-Date: 2017-01-25 22:00+0100\n"
"Last-Translator: Jоегg Kоhпе <joeko (AT) online [PUNKT] de>\n"
"Language-Team: German <address@hidden>\n"
@@ -1003,6 +1003,15 @@
#. type: Content of: <ul><li><p>
msgid ""
+"Apple proposes <a href=\"https://www.theguardian.com/technology/2017/feb/15/";
+"apple-removing-iphone-home-button-fingerprint-scanning-screen\">a "
+"fingerprint-scanning touch screen</a> — which would mean no way to use "
+"it without having your fingerprints taken. Users would have no way to tell "
+"whether the phone is snooping on them."
+msgstr ""
+
+#. type: Content of: <ul><li><p>
+msgid ""
"Samsung phones come with <a href=\"http://arstechnica.com/gadgets/2015/07/";
"samsung-sued-for-loading-devices-with-unremovable-crapware-in-china/\">apps "
"that users can't delete</a>, and they send so much data that their "
Index: proprietary/po/proprietary-surveillance.fr.po
===================================================================
RCS file: /web/www/www/proprietary/po/proprietary-surveillance.fr.po,v
retrieving revision 1.146
retrieving revision 1.147
diff -u -b -r1.146 -r1.147
--- proprietary/po/proprietary-surveillance.fr.po 10 Mar 2017 10:04:15
-0000 1.146
+++ proprietary/po/proprietary-surveillance.fr.po 10 Mar 2017 19:30:53
-0000 1.147
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: proprietary-surveillance.html\n"
-"POT-Creation-Date: 2017-03-09 23:56+0000\n"
+"POT-Creation-Date: 2017-03-10 19:26+0000\n"
"PO-Revision-Date: 2017-03-10 10:55+0100\n"
"Last-Translator: Félicien Pillot <felicien AT gnu.org>\n"
"Language-Team: French <address@hidden>\n"
@@ -15,6 +15,7 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"X-Outdated-Since: 2017-03-10 19:26+0000\n"
"Plural-Forms: \n"
"X-Generator: Gtranslator 2.91.5\n"
@@ -962,6 +963,15 @@
#. type: Content of: <ul><li><p>
msgid ""
+"Apple proposes <a href=\"https://www.theguardian.com/technology/2017/feb/15/";
+"apple-removing-iphone-home-button-fingerprint-scanning-screen\">a "
+"fingerprint-scanning touch screen</a> — which would mean no way to use "
+"it without having your fingerprints taken. Users would have no way to tell "
+"whether the phone is snooping on them."
+msgstr ""
+
+#. type: Content of: <ul><li><p>
+msgid ""
"Samsung phones come with <a href=\"http://arstechnica.com/gadgets/2015/07/";
"samsung-sued-for-loading-devices-with-unremovable-crapware-in-china/\">apps "
"that users can't delete</a>, and they send so much data that their "
Index: proprietary/po/proprietary-surveillance.it-diff.html
===================================================================
RCS file: /web/www/www/proprietary/po/proprietary-surveillance.it-diff.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -b -r1.5 -r1.6
--- proprietary/po/proprietary-surveillance.it-diff.html 9 Mar 2017
23:59:32 -0000 1.5
+++ proprietary/po/proprietary-surveillance.it-diff.html 10 Mar 2017
19:30:53 -0000 1.6
@@ -490,6 +490,12 @@
disguise itself from investigation.</p>
</li>
+ <span class="inserted"><ins><em><li><p>Apple proposes
+ <a
href="https://www.theguardian.com/technology/2017/feb/15/apple-removing-iphone-home-button-fingerprint-scanning-screen">a
fingerprint-scanning touch screen</a>
+ — which would mean no way to use it without having your
fingerprints
+ taken. Users would have no way to tell whether the phone is snooping on
+ them.</p></li></em></ins></span>
+
<li><p>Samsung phones come with
<a
href="http://arstechnica.com/gadgets/2015/07/samsung-sued-for-loading-devices-with-unremovable-crapware-in-china/">apps
that users can't delete</a>,
and they send so much data that their transmission is a
@@ -1213,7 +1219,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2017/03/09 23:59:32 $
+$Date: 2017/03/10 19:30:53 $
<!-- 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.132
retrieving revision 1.133
diff -u -b -r1.132 -r1.133
--- proprietary/po/proprietary-surveillance.it.po 9 Mar 2017 23:59:32
-0000 1.132
+++ proprietary/po/proprietary-surveillance.it.po 10 Mar 2017 19:30:53
-0000 1.133
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: proprietary-surveillance.html\n"
-"POT-Creation-Date: 2017-03-09 23:56+0000\n"
+"POT-Creation-Date: 2017-03-10 19:26+0000\n"
"PO-Revision-Date: 2016-12-08 21:52+0100\n"
"Last-Translator: Andrea Pescetti <address@hidden>\n"
"Language-Team: Italian <address@hidden>\n"
@@ -950,6 +950,15 @@
#. type: Content of: <ul><li><p>
msgid ""
+"Apple proposes <a href=\"https://www.theguardian.com/technology/2017/feb/15/";
+"apple-removing-iphone-home-button-fingerprint-scanning-screen\">a "
+"fingerprint-scanning touch screen</a> — which would mean no way to use "
+"it without having your fingerprints taken. Users would have no way to tell "
+"whether the phone is snooping on them."
+msgstr ""
+
+#. type: Content of: <ul><li><p>
+msgid ""
"Samsung phones come with <a href=\"http://arstechnica.com/gadgets/2015/07/";
"samsung-sued-for-loading-devices-with-unremovable-crapware-in-china/\">apps "
"that users can't delete</a>, and they send so much data that their "
Index: proprietary/po/proprietary-surveillance.ja.po
===================================================================
RCS file: /web/www/www/proprietary/po/proprietary-surveillance.ja.po,v
retrieving revision 1.127
retrieving revision 1.128
diff -u -b -r1.127 -r1.128
--- proprietary/po/proprietary-surveillance.ja.po 9 Mar 2017 23:59:32
-0000 1.127
+++ proprietary/po/proprietary-surveillance.ja.po 10 Mar 2017 19:30:53
-0000 1.128
@@ -6,7 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: proprietary-surveillance.html\n"
-"POT-Creation-Date: 2017-03-09 23:56+0000\n"
+"POT-Creation-Date: 2017-03-10 19:26+0000\n"
"PO-Revision-Date: 2017-01-24 12:16+0900\n"
"Last-Translator: NIIBE Yutaka <address@hidden>\n"
"Language-Team: Japanese <address@hidden>\n"
@@ -921,6 +921,15 @@
#. type: Content of: <ul><li><p>
msgid ""
+"Apple proposes <a href=\"https://www.theguardian.com/technology/2017/feb/15/";
+"apple-removing-iphone-home-button-fingerprint-scanning-screen\">a "
+"fingerprint-scanning touch screen</a> — which would mean no way to use "
+"it without having your fingerprints taken. Users would have no way to tell "
+"whether the phone is snooping on them."
+msgstr ""
+
+#. type: Content of: <ul><li><p>
+msgid ""
"Samsung phones come with <a href=\"http://arstechnica.com/gadgets/2015/07/";
"samsung-sued-for-loading-devices-with-unremovable-crapware-in-china/\">apps "
"that users can't delete</a>, and they send so much data that their "
Index: proprietary/po/proprietary-surveillance.pot
===================================================================
RCS file: /web/www/www/proprietary/po/proprietary-surveillance.pot,v
retrieving revision 1.76
retrieving revision 1.77
diff -u -b -r1.76 -r1.77
--- proprietary/po/proprietary-surveillance.pot 9 Mar 2017 23:59:32 -0000
1.76
+++ proprietary/po/proprietary-surveillance.pot 10 Mar 2017 19:30:53 -0000
1.77
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: proprietary-surveillance.html\n"
-"POT-Creation-Date: 2017-03-09 23:56+0000\n"
+"POT-Creation-Date: 2017-03-10 19:26+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <address@hidden>\n"
"Language-Team: LANGUAGE <address@hidden>\n"
@@ -702,6 +702,15 @@
#. type: Content of: <ul><li><p>
msgid ""
+"Apple proposes <a "
+"href=\"https://www.theguardian.com/technology/2017/feb/15/apple-removing-iphone-home-button-fingerprint-scanning-screen\";>a
"
+"fingerprint-scanning touch screen</a> — which would mean no way to use "
+"it without having your fingerprints taken. Users would have no way to tell "
+"whether the phone is snooping on them."
+msgstr ""
+
+#. type: Content of: <ul><li><p>
+msgid ""
"Samsung phones come with <a "
"href=\"http://arstechnica.com/gadgets/2015/07/samsung-sued-for-loading-devices-with-unremovable-crapware-in-china/\";>apps
"
"that users can't delete</a>, and they send so much data that their "
Index: proprietary/po/proprietary-surveillance.ru.po
===================================================================
RCS file: /web/www/www/proprietary/po/proprietary-surveillance.ru.po,v
retrieving revision 1.184
retrieving revision 1.185
diff -u -b -r1.184 -r1.185
--- proprietary/po/proprietary-surveillance.ru.po 10 Mar 2017 06:30:54
-0000 1.184
+++ proprietary/po/proprietary-surveillance.ru.po 10 Mar 2017 19:30:53
-0000 1.185
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: proprietary-surveillance.html\n"
-"POT-Creation-Date: 2017-03-09 23:56+0000\n"
+"POT-Creation-Date: 2017-03-10 19:26+0000\n"
"PO-Revision-Date: 2017-03-10 16:09+0000\n"
"Last-Translator: Ineiev <address@hidden>\n"
"Language-Team: Russian <address@hidden>\n"
@@ -15,6 +15,7 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"X-Outdated-Since: 2017-03-10 19:26+0000\n"
#. type: Content of: <title>
msgid "Proprietary Surveillance - GNU Project - Free Software Foundation"
@@ -953,6 +954,15 @@
#. type: Content of: <ul><li><p>
msgid ""
+"Apple proposes <a href=\"https://www.theguardian.com/technology/2017/feb/15/";
+"apple-removing-iphone-home-button-fingerprint-scanning-screen\">a "
+"fingerprint-scanning touch screen</a> — which would mean no way to use "
+"it without having your fingerprints taken. Users would have no way to tell "
+"whether the phone is snooping on them."
+msgstr ""
+
+#. type: Content of: <ul><li><p>
+msgid ""
"Samsung phones come with <a href=\"http://arstechnica.com/gadgets/2015/07/";
"samsung-sued-for-loading-devices-with-unremovable-crapware-in-china/\">apps "
"that users can't delete</a>, and they send so much data that their "
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- www licenses/old-licenses/po/gpl-2.0-faq.de.po ...,
GNUN <=