www/licenses/po gpl-faq.pot

[GNUN]

CVSROOT:        /web/www
Module name:    www
Changes by:     GNUN <gnun>     17/03/10 10:56:49

Modified files:
        licenses/po    : gpl-faq.pot 

Log message:
        Automatic update by GNUnited Nations.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gpl-faq.pot?cvsroot=www&r1=1.73&r2=1.74

Patches:
Index: gpl-faq.pot
===================================================================
RCS file: /web/www/www/licenses/po/gpl-faq.pot,v
retrieving revision 1.73
retrieving revision 1.74
diff -u -b -r1.73 -r1.74
--- gpl-faq.pot 17 Feb 2017 05:30:48 -0000      1.73
+++ gpl-faq.pot 10 Mar 2017 15:56:49 -0000      1.74
@@ -7,7 +7,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: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <address@hidden>\n"
 "Language-Team: LANGUAGE <address@hidden>\n"
@@ -853,6 +853,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>"
@@ -2444,34 +2450,61 @@
 
 #. 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>"
+"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 ""
 
 #. 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 "
+"&lsquo;main&rsquo; 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 &lsquo;main&rsquo; 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>
@@ -2483,21 +2516,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>
@@ -2515,27 +2545,16 @@
 
 #. 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 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."
+"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 ""
-"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>