www-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

www/licenses/po gpl-faq.es.po gpl-faq.fr.po gpl...


From: GNUN
Subject: www/licenses/po gpl-faq.es.po gpl-faq.fr.po gpl...
Date: Mon, 10 Jun 2013 21:28:35 +0000

CVSROOT:        /web/www
Module name:    www
Changes by:     GNUN <gnun>     13/06/10 21:28:35

Modified files:
        licenses/po    : gpl-faq.es.po gpl-faq.fr.po gpl-faq.ja.po 
                         gpl-faq.pot gpl-faq.ru.po gpl-faq.ta.po 

Log message:
        Automatic update by GNUnited Nations.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gpl-faq.es.po?cvsroot=www&r1=1.17&r2=1.18
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gpl-faq.fr.po?cvsroot=www&r1=1.101&r2=1.102
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gpl-faq.ja.po?cvsroot=www&r1=1.17&r2=1.18
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gpl-faq.pot?cvsroot=www&r1=1.44&r2=1.45
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gpl-faq.ru.po?cvsroot=www&r1=1.50&r2=1.51
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gpl-faq.ta.po?cvsroot=www&r1=1.31&r2=1.32

Patches:
Index: gpl-faq.es.po
===================================================================
RCS file: /web/www/www/licenses/po/gpl-faq.es.po,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -b -r1.17 -r1.18
--- gpl-faq.es.po       10 Apr 2013 18:13:32 -0000      1.17
+++ gpl-faq.es.po       10 Jun 2013 21:28:33 -0000      1.18
@@ -7,7 +7,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: gpl-faq.html\n"
-"POT-Creation-Date: 2013-04-10 19:58+0300\n"
+"POT-Creation-Date: 2013-06-10 21:25+0000\n"
 "PO-Revision-Date: 2013-04-10 19:55+0100\n"
 "Last-Translator: Dora Scilipoti <dora AT gnu DOT org>\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"
+"Outdated-Since: 2013-06-10 21:25+0000\n"
 "Plural-Forms: nplurals=2; plural=(n!=1);\n"
 "X-Poedit-Language: Spanish\n"
 
@@ -1063,6 +1064,18 @@
 
 #. type: Content of: <ul><li>
 msgid ""
+"<a href=\"#GPLStaticVsDynamic\">Does the GPL have different requirements for "
+"statically vs dynamically linked modules with a covered work?</a>"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"<a href=\"#LGPLStaticVsDynamic\">Does the LGPL have different requirements "
+"for statically vs dynamically linked modules with a covered work?</a>"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
 "<a href=\"#IfLibraryIsGPL\">If a library is released under the GPL (not the "
 "LGPL), does that mean that any software which uses it has to be under the "
 "GPL or a GPL-compatible license?</a>"
@@ -2929,6 +2942,94 @@
 "también las mejoras mismas pueden estar cubiertas por la GPL."
 
 #. type: Content of: <dl><dt>
+# | [-Do I have &ldquo;fair use&rdquo; rights in using-]{+Does+} the [-source
+# | code of-] {+GPL have different requirements for statically vs dynamically
+# | linked modules with+} a [-GPL-covered program?-] {+covered work?+} <span
+# | class=\"anchor-reference-id\">(<a [-href=\"#GPLFairUse\"
+# | >#GPLFairUse</a>)</span>-] {+href=\"#GPLStaticVsDynamic\"
+# | >#GPLStaticVsDynamic</a>)</span>+}
+#, fuzzy
+#| msgid ""
+#| "Do I have &ldquo;fair use&rdquo; rights in using the source code of a GPL-"
+#| "covered program? <span class=\"anchor-reference-id\">(<a href="
+#| "\"#GPLFairUse\" >#GPLFairUse</a>)</span>"
+msgid ""
+"Does the GPL have different requirements for statically vs dynamically "
+"linked modules with a covered work? <span class=\"anchor-reference-id\">(<a "
+"href=\"#GPLStaticVsDynamic\" >#GPLStaticVsDynamic</a>)</span>"
+msgstr ""
+"¿Tengo derechos de «uso legítimo» (<cite>fair use</cite>) para utilizar 
el "
+"código fuente de un programa cubierto por la GPL? <span class=\"anchor-"
+"reference-id\">(<a href=\"#GPLFairUse\" >#GPLFairUse</a>)</span>"
+
+#. type: Content of: <dl><dd><p>
+# | {+No.+} Linking [-ABC-] {+a GPL covered work+} statically or dynamically
+# | with other modules is making a combined work based on [-ABC.-] {+the GPL
+# | covered work.+} Thus, the terms and conditions of the GNU General Public
+# | License cover the whole combination. {+See also <a
+# | href=\"#GPLIncompatibleLibs\">What legal issues come up if I use
+# | GPL-incompatible libraries with GPL software?</a>+}
+#, fuzzy
+#| msgid ""
+#| "Linking ABC statically or dynamically with other modules is making a "
+#| "combined work based on ABC.  Thus, the terms and conditions of the GNU "
+#| "General Public License cover the whole combination."
+msgid ""
+"No. Linking a GPL covered work statically or dynamically with other modules "
+"is making a combined work based on the GPL covered work. Thus, the terms and "
+"conditions of the GNU General Public License cover the whole combination. "
+"See also <a href=\"#GPLIncompatibleLibs\">What legal issues come up if I use "
+"GPL-incompatible libraries with GPL software?</a>"
+msgstr ""
+"Linking ABC statically or dynamically with other modules is making a "
+"combined work based on ABC.  Thus, the terms and conditions of the GNU "
+"General Public License cover the whole combination."
+
+#. type: Content of: <dl><dt>
+# | [-Do I have &ldquo;fair use&rdquo; rights in using-]{+Does+} the [-source
+# | code of-] {+LGPL have different requirements for statically vs dynamically
+# | linked modules with+} a [-GPL-covered program?-] {+covered work?+} <span
+# | class=\"anchor-reference-id\">(<a [-href=\"#GPLFairUse\"
+# | >#GPLFairUse</a>)</span>-] {+href=\"#LGPLStaticVsDynamic\"
+# | >#LGPLStaticVsDynamic</a>)</span>+}
+#, fuzzy
+#| msgid ""
+#| "Do I have &ldquo;fair use&rdquo; rights in using the source code of a GPL-"
+#| "covered program? <span class=\"anchor-reference-id\">(<a href="
+#| "\"#GPLFairUse\" >#GPLFairUse</a>)</span>"
+msgid ""
+"Does the LGPL have different requirements for statically vs dynamically "
+"linked modules with a covered work? <span class=\"anchor-reference-id\">(<a "
+"href=\"#LGPLStaticVsDynamic\" >#LGPLStaticVsDynamic</a>)</span>"
+msgstr ""
+"¿Tengo derechos de «uso legítimo» (<cite>fair use</cite>) para utilizar 
el "
+"código fuente de un programa cubierto por la GPL? <span class=\"anchor-"
+"reference-id\">(<a href=\"#GPLFairUse\" >#GPLFairUse</a>)</span>"
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"For the purpose of complying with the LGPL (any extant version: v2, v2.1 or "
+"v3):"
+msgstr ""
+
+#. type: Content of: <dl><dd><blockquote><p>
+msgid ""
+"(1) If you statically link against an LGPL'd library, you must also provide "
+"your application in an object (not necessarily source)  format, so that a "
+"user has the opportunity to modify the library and relink the application."
+msgstr ""
+
+#. type: Content of: <dl><dd><blockquote><p>
+msgid ""
+"(2) If you dynamically link against an LGPL'd library <em>already present on "
+"the user's computer</em>, you need not convey the library's source. On the "
+"other hand, if you yourself convey the executable LGPL'd library along with "
+"your application, whether linked with statically or dynamically, you must "
+"also convey the library's sources, in one of the ways for which the LGPL "
+"provides."
+msgstr ""
+
+#. type: Content of: <dl><dt>
 msgid ""
 "Is there some way that I can GPL the output people get from use of my "
 "program? For example, if my program is used to develop hardware designs, can "

Index: gpl-faq.fr.po
===================================================================
RCS file: /web/www/www/licenses/po/gpl-faq.fr.po,v
retrieving revision 1.101
retrieving revision 1.102
diff -u -b -r1.101 -r1.102
--- gpl-faq.fr.po       13 Apr 2013 09:10:15 -0000      1.101
+++ gpl-faq.fr.po       10 Jun 2013 21:28:33 -0000      1.102
@@ -9,7 +9,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: gpl-faq.html\n"
-"POT-Creation-Date: 2013-04-09 02:57-0300\n"
+"POT-Creation-Date: 2013-06-10 21:25+0000\n"
 "PO-Revision-Date: 2013-04-11 16:21+0200\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"
+"Outdated-Since: 2013-06-10 21:25+0000\n"
 "Plural-Forms: \n"
 "X-Generator: Gtranslator 2.91.5\n"
 
@@ -1070,6 +1071,18 @@
 
 #. type: Content of: <ul><li>
 msgid ""
+"<a href=\"#GPLStaticVsDynamic\">Does the GPL have different requirements for "
+"statically vs dynamically linked modules with a covered work?</a>"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"<a href=\"#LGPLStaticVsDynamic\">Does the LGPL have different requirements "
+"for statically vs dynamically linked modules with a covered work?</a>"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
 "<a href=\"#IfLibraryIsGPL\">If a library is released under the GPL (not the "
 "LGPL), does that mean that any software which uses it has to be under the "
 "GPL or a GPL-compatible license?</a>"
@@ -2950,6 +2963,96 @@
 "les améliorations elles-mêmes peuvent être régies par la GPL."
 
 #. type: Content of: <dl><dt>
+# | [-Do I have &ldquo;fair use&rdquo; rights in using-]{+Does+} the [-source
+# | code of-] {+GPL have different requirements for statically vs dynamically
+# | linked modules with+} a [-GPL-covered program?-] {+covered work?+} <span
+# | class=\"anchor-reference-id\">(<a [-href=\"#GPLFairUse\"
+# | >#GPLFairUse</a>)</span>-] {+href=\"#GPLStaticVsDynamic\"
+# | >#GPLStaticVsDynamic</a>)</span>+}
+#, fuzzy
+#| msgid ""
+#| "Do I have &ldquo;fair use&rdquo; rights in using the source code of a GPL-"
+#| "covered program? <span class=\"anchor-reference-id\">(<a href="
+#| "\"#GPLFairUse\" >#GPLFairUse</a>)</span>"
+msgid ""
+"Does the GPL have different requirements for statically vs dynamically "
+"linked modules with a covered work? <span class=\"anchor-reference-id\">(<a "
+"href=\"#GPLStaticVsDynamic\" >#GPLStaticVsDynamic</a>)</span>"
+msgstr ""
+"Ai-je des droits de <cite>fair use</cite><a href=\"#TransNote5\" id="
+"\"TransNote5-rev\"><sup>e</sup></a> pour l'utilisation du code source d'un "
+"programme régi par la GPL ? <span class=\"anchor-reference-id\">(<a href="
+"\"#GPLFairUse\" >#GPLFairUse</a>)</span>"
+
+#. type: Content of: <dl><dd><p>
+# | {+No.+} Linking [-ABC-] {+a GPL covered work+} statically or dynamically
+# | with other modules is making a combined work based on [-ABC.-] {+the GPL
+# | covered work.+} Thus, the terms and conditions of the GNU General Public
+# | License cover the whole combination. {+See also <a
+# | href=\"#GPLIncompatibleLibs\">What legal issues come up if I use
+# | GPL-incompatible libraries with GPL software?</a>+}
+#, fuzzy
+#| msgid ""
+#| "Linking ABC statically or dynamically with other modules is making a "
+#| "combined work based on ABC.  Thus, the terms and conditions of the GNU "
+#| "General Public License cover the whole combination."
+msgid ""
+"No. Linking a GPL covered work statically or dynamically with other modules "
+"is making a combined work based on the GPL covered work. Thus, the terms and "
+"conditions of the GNU General Public License cover the whole combination. "
+"See also <a href=\"#GPLIncompatibleLibs\">What legal issues come up if I use "
+"GPL-incompatible libraries with GPL software?</a>"
+msgstr ""
+"Linking ABC statically or dynamically with other modules is making a "
+"combined work based on ABC.  Thus, the terms and conditions of the GNU "
+"General Public License cover the whole combination."
+
+#. type: Content of: <dl><dt>
+# | [-Do I have &ldquo;fair use&rdquo; rights in using-]{+Does+} the [-source
+# | code of-] {+LGPL have different requirements for statically vs dynamically
+# | linked modules with+} a [-GPL-covered program?-] {+covered work?+} <span
+# | class=\"anchor-reference-id\">(<a [-href=\"#GPLFairUse\"
+# | >#GPLFairUse</a>)</span>-] {+href=\"#LGPLStaticVsDynamic\"
+# | >#LGPLStaticVsDynamic</a>)</span>+}
+#, fuzzy
+#| msgid ""
+#| "Do I have &ldquo;fair use&rdquo; rights in using the source code of a GPL-"
+#| "covered program? <span class=\"anchor-reference-id\">(<a href="
+#| "\"#GPLFairUse\" >#GPLFairUse</a>)</span>"
+msgid ""
+"Does the LGPL have different requirements for statically vs dynamically "
+"linked modules with a covered work? <span class=\"anchor-reference-id\">(<a "
+"href=\"#LGPLStaticVsDynamic\" >#LGPLStaticVsDynamic</a>)</span>"
+msgstr ""
+"Ai-je des droits de <cite>fair use</cite><a href=\"#TransNote5\" id="
+"\"TransNote5-rev\"><sup>e</sup></a> pour l'utilisation du code source d'un "
+"programme régi par la GPL ? <span class=\"anchor-reference-id\">(<a href="
+"\"#GPLFairUse\" >#GPLFairUse</a>)</span>"
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"For the purpose of complying with the LGPL (any extant version: v2, v2.1 or "
+"v3):"
+msgstr ""
+
+#. type: Content of: <dl><dd><blockquote><p>
+msgid ""
+"(1) If you statically link against an LGPL'd library, you must also provide "
+"your application in an object (not necessarily source)  format, so that a "
+"user has the opportunity to modify the library and relink the application."
+msgstr ""
+
+#. type: Content of: <dl><dd><blockquote><p>
+msgid ""
+"(2) If you dynamically link against an LGPL'd library <em>already present on "
+"the user's computer</em>, you need not convey the library's source. On the "
+"other hand, if you yourself convey the executable LGPL'd library along with "
+"your application, whether linked with statically or dynamically, you must "
+"also convey the library's sources, in one of the ways for which the LGPL "
+"provides."
+msgstr ""
+
+#. type: Content of: <dl><dt>
 msgid ""
 "Is there some way that I can GPL the output people get from use of my "
 "program? For example, if my program is used to develop hardware designs, can "

Index: gpl-faq.ja.po
===================================================================
RCS file: /web/www/www/licenses/po/gpl-faq.ja.po,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -b -r1.17 -r1.18
--- gpl-faq.ja.po       30 Apr 2013 00:20:28 -0000      1.17
+++ gpl-faq.ja.po       10 Jun 2013 21:28:34 -0000      1.18
@@ -6,7 +6,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: gpl-faq.html\n"
-"POT-Creation-Date: 2013-04-09 02:57-0300\n"
+"POT-Creation-Date: 2013-06-10 21:25+0000\n"
 "PO-Revision-Date: 2013-04-30 09:10+0900\n"
 "Last-Translator: NIIBE Yutaka <address@hidden>\n"
 "Language-Team: Japanese <address@hidden>\n"
@@ -14,6 +14,7 @@
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=utf-8\n"
 "Content-Transfer-Encoding: 8bit\n"
+"Outdated-Since: 2013-06-10 21:25+0000\n"
 
 #. type: Content of: <title>
 msgid ""
@@ -1034,6 +1035,18 @@
 
 #. type: Content of: <ul><li>
 msgid ""
+"<a href=\"#GPLStaticVsDynamic\">Does the GPL have different requirements for "
+"statically vs dynamically linked modules with a covered work?</a>"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"<a href=\"#LGPLStaticVsDynamic\">Does the LGPL have different requirements "
+"for statically vs dynamically linked modules with a covered work?</a>"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
 "<a href=\"#IfLibraryIsGPL\">If a library is released under the GPL (not the "
 "LGPL), does that mean that any software which uses it has to be under the "
 "GPL or a GPL-compatible license?</a>"
@@ -2897,6 +2910,79 @@
 "が及ぶようにすることができます。"
 
 #. type: Content of: <dl><dt>
+#, fuzzy
+#| msgid ""
+#| "Do I have &ldquo;fair use&rdquo; rights in using the source code of a GPL-"
+#| "covered program? <span class=\"anchor-reference-id\">(<a href="
+#| "\"#GPLFairUse\" >#GPLFairUse</a>)</span>"
+msgid ""
+"Does the GPL have different requirements for statically vs dynamically "
+"linked modules with a covered work? <span class=\"anchor-reference-id\">(<a "
+"href=\"#GPLStaticVsDynamic\" >#GPLStaticVsDynamic</a>)</span>"
+msgstr ""
+"GPLの及ぶプログラムのソースコードを「公正使用(fair 
use)」する権利はあります"
+"か? <span class=\"anchor-reference-id\">(<a href=\"#GPLFairUse\" "
+">#GPLFairUse</a>)</span>"
+
+#. type: Content of: <dl><dd><p>
+#, fuzzy
+#| msgid ""
+#| "Linking ABC statically or dynamically with other modules is making a "
+#| "combined work based on ABC.  Thus, the terms and conditions of the GNU "
+#| "General Public License cover the whole combination."
+msgid ""
+"No. Linking a GPL covered work statically or dynamically with other modules "
+"is making a combined work based on the GPL covered work. Thus, the terms and "
+"conditions of the GNU General Public License cover the whole combination. "
+"See also <a href=\"#GPLIncompatibleLibs\">What legal issues come up if I use "
+"GPL-incompatible libraries with GPL software?</a>"
+msgstr ""
+"Linking ABC statically or dynamically with other modules is making a "
+"combined work based on ABC.  Thus, the terms and conditions of the GNU "
+"General Public License cover the whole combination.\n"
+"日本語訳: 
ABCを静的もしくは動的にほかのモジュールとリンクすることは、ABCをも"
+"とにして結合著作物を作成することです。ですから、å…
¨ä½“として、GNU一般公衆ライセ"
+"ンスの条項が適用されます。"
+
+#. type: Content of: <dl><dt>
+#, fuzzy
+#| msgid ""
+#| "Do I have &ldquo;fair use&rdquo; rights in using the source code of a GPL-"
+#| "covered program? <span class=\"anchor-reference-id\">(<a href="
+#| "\"#GPLFairUse\" >#GPLFairUse</a>)</span>"
+msgid ""
+"Does the LGPL have different requirements for statically vs dynamically "
+"linked modules with a covered work? <span class=\"anchor-reference-id\">(<a "
+"href=\"#LGPLStaticVsDynamic\" >#LGPLStaticVsDynamic</a>)</span>"
+msgstr ""
+"GPLの及ぶプログラムのソースコードを「公正使用(fair 
use)」する権利はあります"
+"か? <span class=\"anchor-reference-id\">(<a href=\"#GPLFairUse\" "
+">#GPLFairUse</a>)</span>"
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"For the purpose of complying with the LGPL (any extant version: v2, v2.1 or "
+"v3):"
+msgstr ""
+
+#. type: Content of: <dl><dd><blockquote><p>
+msgid ""
+"(1) If you statically link against an LGPL'd library, you must also provide "
+"your application in an object (not necessarily source)  format, so that a "
+"user has the opportunity to modify the library and relink the application."
+msgstr ""
+
+#. type: Content of: <dl><dd><blockquote><p>
+msgid ""
+"(2) If you dynamically link against an LGPL'd library <em>already present on "
+"the user's computer</em>, you need not convey the library's source. On the "
+"other hand, if you yourself convey the executable LGPL'd library along with "
+"your application, whether linked with statically or dynamically, you must "
+"also convey the library's sources, in one of the ways for which the LGPL "
+"provides."
+msgstr ""
+
+#. type: Content of: <dl><dt>
 msgid ""
 "Is there some way that I can GPL the output people get from use of my "
 "program? For example, if my program is used to develop hardware designs, can "

Index: gpl-faq.pot
===================================================================
RCS file: /web/www/www/licenses/po/gpl-faq.pot,v
retrieving revision 1.44
retrieving revision 1.45
diff -u -b -r1.44 -r1.45
--- gpl-faq.pot 9 Apr 2013 07:02:30 -0000       1.44
+++ gpl-faq.pot 10 Jun 2013 21:28:34 -0000      1.45
@@ -7,7 +7,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: gpl-faq.html\n"
-"POT-Creation-Date: 2013-04-09 02:57-0300\n"
+"POT-Creation-Date: 2013-06-10 21:25+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"
@@ -776,6 +776,18 @@
 
 #. type: Content of: <ul><li>
 msgid ""
+"<a href=\"#GPLStaticVsDynamic\">Does the GPL have different requirements for "
+"statically vs dynamically linked modules with a covered work?</a>"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"<a href=\"#LGPLStaticVsDynamic\">Does the LGPL have different requirements "
+"for statically vs dynamically linked modules with a covered work?</a>"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
 "<a href=\"#IfLibraryIsGPL\">If a library is released under the GPL (not the "
 "LGPL), does that mean that any software which uses it has to be under the "
 "GPL or a GPL-compatible license?</a>"
@@ -2028,6 +2040,52 @@
 
 #. type: Content of: <dl><dt>
 msgid ""
+"Does the GPL have different requirements for statically vs dynamically "
+"linked modules with a covered work? <span class=\"anchor-reference-id\">(<a "
+"href=\"#GPLStaticVsDynamic\" >#GPLStaticVsDynamic</a>)</span>"
+msgstr ""
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"No. Linking a GPL covered work statically or dynamically with other modules "
+"is making a combined work based on the GPL covered work. Thus, the terms and "
+"conditions of the GNU General Public License cover the whole "
+"combination. See also <a href=\"#GPLIncompatibleLibs\">What legal issues "
+"come up if I use GPL-incompatible libraries with GPL software?</a>"
+msgstr ""
+
+#. type: Content of: <dl><dt>
+msgid ""
+"Does the LGPL have different requirements for statically vs dynamically "
+"linked modules with a covered work? <span class=\"anchor-reference-id\">(<a "
+"href=\"#LGPLStaticVsDynamic\" >#LGPLStaticVsDynamic</a>)</span>"
+msgstr ""
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"For the purpose of complying with the LGPL (any extant version: v2, v2.1 or "
+"v3):"
+msgstr ""
+
+#. type: Content of: <dl><dd><blockquote><p>
+msgid ""
+"(1) If you statically link against an LGPL'd library, you must also provide "
+"your application in an object (not necessarily source)  format, so that a "
+"user has the opportunity to modify the library and relink the application."
+msgstr ""
+
+#. type: Content of: <dl><dd><blockquote><p>
+msgid ""
+"(2) If you dynamically link against an LGPL'd library <em>already present on "
+"the user's computer</em>, you need not convey the library's source. On the "
+"other hand, if you yourself convey the executable LGPL'd library along with "
+"your application, whether linked with statically or dynamically, you must "
+"also convey the library's sources, in one of the ways for which the LGPL "
+"provides."
+msgstr ""
+
+#. type: Content of: <dl><dt>
+msgid ""
 "Is there some way that I can GPL the output people get from use of my "
 "program? For example, if my program is used to develop hardware designs, can "
 "I require that these designs must be free? <span "

Index: gpl-faq.ru.po
===================================================================
RCS file: /web/www/www/licenses/po/gpl-faq.ru.po,v
retrieving revision 1.50
retrieving revision 1.51
diff -u -b -r1.50 -r1.51
--- gpl-faq.ru.po       9 Apr 2013 08:06:26 -0000       1.50
+++ gpl-faq.ru.po       10 Jun 2013 21:28:34 -0000      1.51
@@ -11,7 +11,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: gpl-faq.html\n"
-"POT-Creation-Date: 2013-04-09 02:57-0300\n"
+"POT-Creation-Date: 2013-06-10 21:25+0000\n"
 "PO-Revision-Date: 2013-04-09 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"
+"Outdated-Since: 2013-06-10 21:25+0000\n"
 
 #. type: Content of: <title>
 msgid ""
@@ -1058,6 +1059,18 @@
 
 #. type: Content of: <ul><li>
 msgid ""
+"<a href=\"#GPLStaticVsDynamic\">Does the GPL have different requirements for "
+"statically vs dynamically linked modules with a covered work?</a>"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"<a href=\"#LGPLStaticVsDynamic\">Does the LGPL have different requirements "
+"for statically vs dynamically linked modules with a covered work?</a>"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
 "<a href=\"#IfLibraryIsGPL\">If a library is released under the GPL (not the "
 "LGPL), does that mean that any software which uses it has to be under the "
 "GPL or a GPL-compatible license?</a>"
@@ -2927,6 +2940,95 @@
 "улучшения могут распространяться условия 
GPL."
 
 #. type: Content of: <dl><dt>
+# | [-Do I have &ldquo;fair use&rdquo; rights in using-]{+Does+} the [-source
+# | code of-] {+GPL have different requirements for statically vs dynamically
+# | linked modules with+} a [-GPL-covered program?-] {+covered work?+} <span
+# | class=\"anchor-reference-id\">(<a [-href=\"#GPLFairUse\"
+# | >#GPLFairUse</a>)</span>-] {+href=\"#GPLStaticVsDynamic\"
+# | >#GPLStaticVsDynamic</a>)</span>+}
+#, fuzzy
+#| msgid ""
+#| "Do I have &ldquo;fair use&rdquo; rights in using the source code of a GPL-"
+#| "covered program? <span class=\"anchor-reference-id\">(<a href="
+#| "\"#GPLFairUse\" >#GPLFairUse</a>)</span>"
+msgid ""
+"Does the GPL have different requirements for statically vs dynamically "
+"linked modules with a covered work? <span class=\"anchor-reference-id\">(<a "
+"href=\"#GPLStaticVsDynamic\" >#GPLStaticVsDynamic</a>)</span>"
+msgstr ""
+"Есть ли у меня право на &ldquo;добросовестное 
использование&rdquo; исходного "
+"текста программы под GPL? <span 
class=\"anchor-reference-id\">(<a href="
+"\"#GPLFairUse\" >#GPLFairUse</a>)</span>"
+
+#. type: Content of: <dl><dd><p>
+# | {+No.+} Linking [-ABC-] {+a GPL covered work+} statically or dynamically
+# | with other modules is making a combined work based on [-ABC.-] {+the GPL
+# | covered work.+} Thus, the terms and conditions of the GNU General Public
+# | License cover the whole combination. {+See also <a
+# | href=\"#GPLIncompatibleLibs\">What legal issues come up if I use
+# | GPL-incompatible libraries with GPL software?</a>+}
+#, fuzzy
+#| msgid ""
+#| "Linking ABC statically or dynamically with other modules is making a "
+#| "combined work based on ABC.  Thus, the terms and conditions of the GNU "
+#| "General Public License cover the whole combination."
+msgid ""
+"No. Linking a GPL covered work statically or dynamically with other modules "
+"is making a combined work based on the GPL covered work. Thus, the terms and "
+"conditions of the GNU General Public License cover the whole combination. "
+"See also <a href=\"#GPLIncompatibleLibs\">What legal issues come up if I use "
+"GPL-incompatible libraries with GPL software?</a>"
+msgstr ""
+"В результате Динамической или 
статической компоновки АБВ с другими 
модулями "
+"получается произведение, производное от 
АБВ. Таким образом, условия и "
+"требования Стандартной общественной 
лицензии GNU распространяются на "
+"комбинацию в целом."
+
+#. type: Content of: <dl><dt>
+# | [-Do I have &ldquo;fair use&rdquo; rights in using-]{+Does+} the [-source
+# | code of-] {+LGPL have different requirements for statically vs dynamically
+# | linked modules with+} a [-GPL-covered program?-] {+covered work?+} <span
+# | class=\"anchor-reference-id\">(<a [-href=\"#GPLFairUse\"
+# | >#GPLFairUse</a>)</span>-] {+href=\"#LGPLStaticVsDynamic\"
+# | >#LGPLStaticVsDynamic</a>)</span>+}
+#, fuzzy
+#| msgid ""
+#| "Do I have &ldquo;fair use&rdquo; rights in using the source code of a GPL-"
+#| "covered program? <span class=\"anchor-reference-id\">(<a href="
+#| "\"#GPLFairUse\" >#GPLFairUse</a>)</span>"
+msgid ""
+"Does the LGPL have different requirements for statically vs dynamically "
+"linked modules with a covered work? <span class=\"anchor-reference-id\">(<a "
+"href=\"#LGPLStaticVsDynamic\" >#LGPLStaticVsDynamic</a>)</span>"
+msgstr ""
+"Есть ли у меня право на &ldquo;добросовестное 
использование&rdquo; исходного "
+"текста программы под GPL? <span 
class=\"anchor-reference-id\">(<a href="
+"\"#GPLFairUse\" >#GPLFairUse</a>)</span>"
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"For the purpose of complying with the LGPL (any extant version: v2, v2.1 or "
+"v3):"
+msgstr ""
+
+#. type: Content of: <dl><dd><blockquote><p>
+msgid ""
+"(1) If you statically link against an LGPL'd library, you must also provide "
+"your application in an object (not necessarily source)  format, so that a "
+"user has the opportunity to modify the library and relink the application."
+msgstr ""
+
+#. type: Content of: <dl><dd><blockquote><p>
+msgid ""
+"(2) If you dynamically link against an LGPL'd library <em>already present on "
+"the user's computer</em>, you need not convey the library's source. On the "
+"other hand, if you yourself convey the executable LGPL'd library along with "
+"your application, whether linked with statically or dynamically, you must "
+"also convey the library's sources, in one of the ways for which the LGPL "
+"provides."
+msgstr ""
+
+#. type: Content of: <dl><dt>
 msgid ""
 "Is there some way that I can GPL the output people get from use of my "
 "program? For example, if my program is used to develop hardware designs, can "

Index: gpl-faq.ta.po
===================================================================
RCS file: /web/www/www/licenses/po/gpl-faq.ta.po,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -b -r1.31 -r1.32
--- gpl-faq.ta.po       9 Apr 2013 07:02:31 -0000       1.31
+++ gpl-faq.ta.po       10 Jun 2013 21:28:34 -0000      1.32
@@ -5,7 +5,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: \n"
-"POT-Creation-Date: 2013-04-09 02:57-0300\n"
+"POT-Creation-Date: 2013-06-10 21:25+0000\n"
 "PO-Revision-Date: 2010-06-20 15:55+0530\n"
 "Last-Translator: Amachu <address@hidden>\n"
 "Language-Team: Tamil <>\n"
@@ -917,6 +917,18 @@
 
 #. type: Content of: <ul><li>
 msgid ""
+"<a href=\"#GPLStaticVsDynamic\">Does the GPL have different requirements for "
+"statically vs dynamically linked modules with a covered work?</a>"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
+"<a href=\"#LGPLStaticVsDynamic\">Does the LGPL have different requirements "
+"for statically vs dynamically linked modules with a covered work?</a>"
+msgstr ""
+
+#. type: Content of: <ul><li>
+msgid ""
 "<a href=\"#IfLibraryIsGPL\">If a library is released under the GPL (not the "
 "LGPL), does that mean that any software which uses it has to be under the "
 "GPL or a GPL-compatible license?</a>"
@@ -2295,6 +2307,52 @@
 
 #. type: Content of: <dl><dt>
 msgid ""
+"Does the GPL have different requirements for statically vs dynamically "
+"linked modules with a covered work? <span class=\"anchor-reference-id\">(<a "
+"href=\"#GPLStaticVsDynamic\" >#GPLStaticVsDynamic</a>)</span>"
+msgstr ""
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"No. Linking a GPL covered work statically or dynamically with other modules "
+"is making a combined work based on the GPL covered work. Thus, the terms and "
+"conditions of the GNU General Public License cover the whole combination. "
+"See also <a href=\"#GPLIncompatibleLibs\">What legal issues come up if I use "
+"GPL-incompatible libraries with GPL software?</a>"
+msgstr ""
+
+#. type: Content of: <dl><dt>
+msgid ""
+"Does the LGPL have different requirements for statically vs dynamically "
+"linked modules with a covered work? <span class=\"anchor-reference-id\">(<a "
+"href=\"#LGPLStaticVsDynamic\" >#LGPLStaticVsDynamic</a>)</span>"
+msgstr ""
+
+#. type: Content of: <dl><dd><p>
+msgid ""
+"For the purpose of complying with the LGPL (any extant version: v2, v2.1 or "
+"v3):"
+msgstr ""
+
+#. type: Content of: <dl><dd><blockquote><p>
+msgid ""
+"(1) If you statically link against an LGPL'd library, you must also provide "
+"your application in an object (not necessarily source)  format, so that a "
+"user has the opportunity to modify the library and relink the application."
+msgstr ""
+
+#. type: Content of: <dl><dd><blockquote><p>
+msgid ""
+"(2) If you dynamically link against an LGPL'd library <em>already present on "
+"the user's computer</em>, you need not convey the library's source. On the "
+"other hand, if you yourself convey the executable LGPL'd library along with "
+"your application, whether linked with statically or dynamically, you must "
+"also convey the library's sources, in one of the ways for which the LGPL "
+"provides."
+msgstr ""
+
+#. type: Content of: <dl><dt>
+msgid ""
 "Is there some way that I can GPL the output people get from use of my "
 "program? For example, if my program is used to develop hardware designs, can "
 "I require that these designs must be free? <span class=\"anchor-reference-id"



reply via email to

[Prev in Thread] Current Thread [Next in Thread]