www-commits
[Top][All Lists]
Advanced

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

www licenses/gpl-faq.ru.html licenses/po/gpl-fa...


From: GNUN
Subject: www licenses/gpl-faq.ru.html licenses/po/gpl-fa...
Date: Wed, 1 Mar 2023 13:30:48 -0500 (EST)

CVSROOT:        /web/www
Module name:    www
Changes by:     GNUN <gnun>     23/03/01 13:30:48

Modified files:
        licenses       : gpl-faq.ru.html 
        licenses/po    : gpl-faq.es.po gpl-faq.fr.po 
                         gpl-faq.it-diff.html gpl-faq.it.po 
                         gpl-faq.ja-diff.html gpl-faq.ja.po 
                         gpl-faq.pl.po gpl-faq.pot gpl-faq.ru-en.html 
                         gpl-faq.ru.po gpl-faq.ta.po gpl-faq.tr.po 
                         gpl-faq.zh-cn.po 
        software       : recent-releases-include.ru.html 
        software/po    : recent-releases-include.ru.po 

Log message:
        Automatic update by GNUnited Nations.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/gpl-faq.ru.html?cvsroot=www&r1=1.103&r2=1.104
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gpl-faq.es.po?cvsroot=www&r1=1.147&r2=1.148
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gpl-faq.fr.po?cvsroot=www&r1=1.250&r2=1.251
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gpl-faq.it-diff.html?cvsroot=www&r1=1.25&r2=1.26
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gpl-faq.it.po?cvsroot=www&r1=1.81&r2=1.82
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gpl-faq.ja-diff.html?cvsroot=www&r1=1.41&r2=1.42
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gpl-faq.ja.po?cvsroot=www&r1=1.117&r2=1.118
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gpl-faq.pl.po?cvsroot=www&r1=1.20&r2=1.21
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gpl-faq.pot?cvsroot=www&r1=1.100&r2=1.101
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gpl-faq.ru-en.html?cvsroot=www&r1=1.82&r2=1.83
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gpl-faq.ru.po?cvsroot=www&r1=1.199&r2=1.200
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gpl-faq.ta.po?cvsroot=www&r1=1.91&r2=1.92
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gpl-faq.tr.po?cvsroot=www&r1=1.31&r2=1.32
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gpl-faq.zh-cn.po?cvsroot=www&r1=1.39&r2=1.40
http://web.cvs.savannah.gnu.org/viewcvs/www/software/recent-releases-include.ru.html?cvsroot=www&r1=1.2576&r2=1.2577
http://web.cvs.savannah.gnu.org/viewcvs/www/software/po/recent-releases-include.ru.po?cvsroot=www&r1=1.3644&r2=1.3645

Patches:
Index: licenses/gpl-faq.ru.html
===================================================================
RCS file: /web/www/www/licenses/gpl-faq.ru.html,v
retrieving revision 1.103
retrieving revision 1.104
diff -u -b -r1.103 -r1.104
--- licenses/gpl-faq.ru.html    25 Feb 2023 14:34:00 -0000      1.103
+++ licenses/gpl-faq.ru.html    1 Mar 2023 18:30:46 -0000       1.104
@@ -675,14 +675,8 @@
     <li><a href="#SystemLibraryException">Могу ли я 
компоновать программу под GPL с
 несвободной системной библиотекой?</a></li>
 
-    <li><a href="#AGPLPL">Могу ли я компоновать модули 
под GPLv3 с модулями под
-AGPLv3 в одном исполнимом файле?</a></li>
-
-    <li><a href="#AGPLLibrary">Могу ли я компоновать 
программу под GPLv3 с
-библиотекой под AGPLv3?</a></li>
-
-    <li><a href="#AGPANDGPLLLibrary">Могу ли я компоновать 
программу под AGPLv3 с
-библиотекой под GPLv3?</a></li>
+    <li><a href="#AGPLGPL">Могу ли я компоновать или 
комбинировать программы под
+AGPLv3 с программами под GPLv3?</a></li>
 
     <li><a href="#GPLIncompatibleLibs">Какие юридические 
проблемы возникают, если я
 применяю несовместимые с GPL библиотеки с 
программами под GPL?</a></li>
@@ -1303,33 +1297,16 @@
 решается по-другому, в конце раздела&nbsp;3.</p>
 </dd>
 
-<dt id="AGPLGPL">Могу ли я компоновать модули под 
GPLv3 и модули под AGPLv3 в одном
-исполнимом файле? <span class="anchor-reference-id">(<a
+<dt id="AGPLGPL">Каким образом я могу компоновать 
или комбинировать программы под AGPLv3 и
+под GPLv3? <span class="anchor-reference-id">(<a
 href="#AGPLGPL">#AGPLGPL</a>)</span></dt>
 <dd><p>
-Вы всегда можете компоновать подули под 
GPLv3 с модулями под AGPLv3. Дело в
-том, что каждая из этих лицензий явно 
разрешает компоновку с программами под
-другой.</p>
-</dd>
-
-<dt id="AGPLLibrary">Могу ли я компоновать 
программу под GPLv3 с библиотекой под AGPLv3? <span
-class="anchor-reference-id">(<a 
href="#AGPLLibrary">#AGPLLibrary</a>)</span></dt>
-<dd><p>
-Вы всегда можете <a href="#AGPLGPL">компоновать 
модули под GPLv3 с модулями
-под AGPLv3</a>.  Это верно независимо от того, 
являются ли какие-то из этих
-модулей библиотеками.</p>
+Каждая из этих лицензий явным образом 
разрешает компоновку с программами под
+другой лицензией. Вы всегда можете 
компоновать модули под GPLv3 c модулями
+под AGPLv3 и наоборот. Это верно независимо от 
того, являются ли некоторые
+из модулей библиотеками или нет.</p>
 </dd>
 
-<dt id="AGPLAndGPLLibrary">Могу ли я компоновать 
программу под AGPLv3 с библиотекой под GPLv3? <span
-class="anchor-reference-id">(<a
-href="#AGPLAndGPLLibrary">#AGPLAndGPLLibrary</a>)</span></dt>
-<dd><p>
-Вы всегда можете <a href="#AGPLGPL">компоновать 
модули под GPLv3 с модулями
-под AGPLv3</a>.  Это верно независимо от того, 
являются ли какие-то из этих
-модулей библиотеками.</p>
-</dd>
-
-
 <dt id="GPLIncompatibleLibs">Какие юридические 
проблемы возникают, если я применяю 
несовместимые с GPL
 библиотеки с программами под GPL? <span 
class="anchor-reference-id">(<a
 href="#GPLIncompatibleLibs" >#GPLIncompatibleLibs</a>)</span></dt>
@@ -4018,7 +3995,7 @@
 <p class="unprintable"><!-- timestamp start -->
 Обновлено:
 
-$Date: 2023/02/25 14:34:00 $
+$Date: 2023/03/01 18:30:46 $
 
 <!-- timestamp end -->
 </p>

Index: licenses/po/gpl-faq.es.po
===================================================================
RCS file: /web/www/www/licenses/po/gpl-faq.es.po,v
retrieving revision 1.147
retrieving revision 1.148
diff -u -b -r1.147 -r1.148
--- licenses/po/gpl-faq.es.po   1 Mar 2023 17:00:03 -0000       1.147
+++ licenses/po/gpl-faq.es.po   1 Mar 2023 18:30:46 -0000       1.148
@@ -8,7 +8,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: gpl-faq.html\n"
-"POT-Creation-Date: 2023-03-01 16:55+0000\n"
+"POT-Creation-Date: 2023-03-01 18:25+0000\n"
 "PO-Revision-Date: 2023-03-01 11:38+0100\n"
 "Last-Translator: Javier Fdez. Retenaga <jfrtnaga@gnu.org>\n"
 "Language-Team: Spanish <www-es-general@gnu.org>\n"
@@ -2653,10 +2653,10 @@
 
 #. type: Content of: <dl><dd><p>
 # | {+Each of these licenses explicitly permits linking with code under the
-# | other license.+}  You can always [-<a href=\"#AGPLGPL\">link
-# | GPLv3-covered-] {+link GPL3-covered+} modules with [-AGPLv3-covered
-# | modules</a>.-] {+AGPL3-covered modules, and vice versa.+}  That is true
-# | regardless of whether some of the modules are libraries.
+# | other license.+}  You can always [-<a href=\"#AGPLGPL\">link-] {+link+}
+# | GPLv3-covered modules with AGPLv3-covered [-modules</a>.-] {+modules, and
+# | vice versa.+}  That is true regardless of whether some of the modules are
+# | libraries.
 #, fuzzy
 #| msgid ""
 #| "You can always <a href=\"#AGPLGPL\">link GPLv3-covered modules with "
@@ -2664,7 +2664,7 @@
 #| "the modules are libraries."
 msgid ""
 "Each of these licenses explicitly permits linking with code under the other "
-"license.  You can always link GPL3-covered modules with AGPL3-covered "
+"license.  You can always link GPLv3-covered modules with AGPLv3-covered "
 "modules, and vice versa.  That is true regardless of whether some of the "
 "modules are libraries."
 msgstr ""

Index: licenses/po/gpl-faq.fr.po
===================================================================
RCS file: /web/www/www/licenses/po/gpl-faq.fr.po,v
retrieving revision 1.250
retrieving revision 1.251
diff -u -b -r1.250 -r1.251
--- licenses/po/gpl-faq.fr.po   1 Mar 2023 17:21:46 -0000       1.250
+++ licenses/po/gpl-faq.fr.po   1 Mar 2023 18:30:46 -0000       1.251
@@ -10,7 +10,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: gpl-faq.html\n"
-"POT-Creation-Date: 2023-03-01 16:55+0000\n"
+"POT-Creation-Date: 2023-03-01 18:25+0000\n"
 "PO-Revision-Date: 2023-03-01 18:17+0100\n"
 "Last-Translator: Thérèse Godefroy <godef.th AT free.fr>\n"
 "Language-Team: French <trad-gnu@april.org>\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: 2023-03-01 18:25+0000\n"
 
 #. type: Content of: <title>
 msgid ""
@@ -2651,9 +2652,19 @@
 "\">#AGPLGPL</a>)</span>"
 
 #. type: Content of: <dl><dd><p>
+# | Each of these licenses explicitly permits linking with code under the
+# | other license.  You can always link GPL{+v+}3-covered modules with
+# | AGPL{+v+}3-covered modules, and vice versa.  That is true regardless of
+# | whether some of the modules are libraries.
+#, fuzzy
+#| msgid ""
+#| "Each of these licenses explicitly permits linking with code under the "
+#| "other license.  You can always link GPL3-covered modules with AGPL3-"
+#| "covered modules, and vice versa.  That is true regardless of whether some "
+#| "of the modules are libraries."
 msgid ""
 "Each of these licenses explicitly permits linking with code under the other "
-"license.  You can always link GPL3-covered modules with AGPL3-covered "
+"license.  You can always link GPLv3-covered modules with AGPLv3-covered "
 "modules, and vice versa.  That is true regardless of whether some of the "
 "modules are libraries."
 msgstr ""

Index: licenses/po/gpl-faq.it-diff.html
===================================================================
RCS file: /web/www/www/licenses/po/gpl-faq.it-diff.html,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -b -r1.25 -r1.26
--- licenses/po/gpl-faq.it-diff.html    1 Mar 2023 17:30:36 -0000       1.25
+++ licenses/po/gpl-faq.it-diff.html    1 Mar 2023 18:30:47 -0000       1.26
@@ -76,7 +76,9 @@
 Project, the Free Software Foundation, and its licenses&lt;span 
class="gnun-split"&gt;&lt;/span&gt;&lt;!--#echo
 encoding='none' var='CLOSE' --&gt;&lt;/li&gt;
   &lt;li&gt;&lt;!--#set var='ANCHOR' value='&lt;a 
href="#understanding"&gt;&lt;b&gt;' --&gt;&lt;!--#echo
-encoding='none' var='ANCHOR' --&gt;&lt;span 
class="gnun-split"&gt;&lt;/span&gt;General understanding of the GNU
+encoding='none' var='ANCHOR' --&gt;&lt;span 
class="gnun-split"&gt;&lt;/span&gt;General understanding</em></ins></span> of 
<span class="removed"><del><strong>Contents&lt;/h3&gt;
+
+  &lt;h4&gt;Basic</strong></del></span> <span class="inserted"><ins><em>the GNU
 licenses&lt;span class="gnun-split"&gt;&lt;/span&gt;&lt;!--#echo
 encoding='none' var='CLOSE' --&gt;&lt;/li&gt;
   &lt;li&gt;&lt;!--#set var='ANCHOR' value='&lt;a 
href="#licensing"&gt;&lt;b&gt;' --&gt;&lt;!--#echo
@@ -95,9 +97,7 @@
 released under the GNU licenses&lt;span 
class="gnun-split"&gt;&lt;/span&gt;&lt;!--#echo
 encoding='none' var='CLOSE' --&gt;&lt;/li&gt;
   &lt;li&gt;&lt;!--#set var='ANCHOR' value='&lt;a 
href="#violations"&gt;&lt;b&gt;' --&gt;&lt;!--#echo
-encoding='none' var='ANCHOR' --&gt;&lt;span 
class="gnun-split"&gt;&lt;/span&gt;Questions about violations</em></ins></span> 
of <span class="removed"><del><strong>Contents&lt;/h3&gt;
-
-  &lt;h4&gt;Basic</strong></del></span> <span class="inserted"><ins><em>the
+encoding='none' var='ANCHOR' --&gt;&lt;span 
class="gnun-split"&gt;&lt;/span&gt;Questions about violations of the
 GNU licenses&lt;span class="gnun-split"&gt;&lt;/span&gt;&lt;!--#echo
 encoding='none' var='CLOSE' --&gt;&lt;/li&gt;
 &lt;/ul&gt;
@@ -1361,8 +1361,8 @@
 href="#AGPLGPL"&gt;#AGPLGPL&lt;/a&gt;)&lt;/span&gt;&lt;/dt&gt;
 &lt;dd&gt;&lt;p&gt;
 Each of these licenses explicitly permits linking with code under the
-other license.  You can always link GPL3-covered modules with
-AGPL3-covered modules, and vice versa.  That is true regardless of
+other license.  You can always link GPLv3-covered modules with
+AGPLv3-covered modules, and vice versa.  That is true regardless of
 whether some of the modules are libraries.&lt;/p&gt;
 &lt;/dd&gt;
 
@@ -4075,7 +4075,7 @@
 
 &lt;p class="unprintable"&gt;Updated:
 &lt;!-- timestamp start --&gt;
-$Date: 2023/03/01 17:30:36 $
+$Date: 2023/03/01 18:30:47 $
 &lt;!-- timestamp end --&gt;
 &lt;/p&gt;
 &lt;/div&gt;

Index: licenses/po/gpl-faq.it.po
===================================================================
RCS file: /web/www/www/licenses/po/gpl-faq.it.po,v
retrieving revision 1.81
retrieving revision 1.82
diff -u -b -r1.81 -r1.82
--- licenses/po/gpl-faq.it.po   1 Mar 2023 17:00:03 -0000       1.81
+++ licenses/po/gpl-faq.it.po   1 Mar 2023 18:30:47 -0000       1.82
@@ -11,7 +11,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: gpl-faq.html\n"
-"POT-Creation-Date: 2023-03-01 16:55+0000\n"
+"POT-Creation-Date: 2023-03-01 18:25+0000\n"
 "PO-Revision-Date: 2018-11-19 17:42+0100\n"
 "Last-Translator: Andrea Pescetti <pescetti@gnu.org>\n"
 "Language-Team: Italian <www-it-traduzioni@gnu.org>\n"
@@ -2789,7 +2789,7 @@
 #. type: Content of: <dl><dd><p>
 msgid ""
 "Each of these licenses explicitly permits linking with code under the other "
-"license.  You can always link GPL3-covered modules with AGPL3-covered "
+"license.  You can always link GPLv3-covered modules with AGPLv3-covered "
 "modules, and vice versa.  That is true regardless of whether some of the "
 "modules are libraries."
 msgstr ""

Index: licenses/po/gpl-faq.ja-diff.html
===================================================================
RCS file: /web/www/www/licenses/po/gpl-faq.ja-diff.html,v
retrieving revision 1.41
retrieving revision 1.42
diff -u -b -r1.41 -r1.42
--- licenses/po/gpl-faq.ja-diff.html    1 Mar 2023 17:30:36 -0000       1.41
+++ licenses/po/gpl-faq.ja-diff.html    1 Mar 2023 18:30:47 -0000       1.42
@@ -1363,8 +1363,8 @@
 href="#AGPLGPL"&gt;#AGPLGPL&lt;/a&gt;)&lt;/span&gt;&lt;/dt&gt;
 &lt;dd&gt;&lt;p&gt;
 Each of these licenses explicitly permits linking with code under the
-other license.  You can always link GPL3-covered modules with
-AGPL3-covered modules, and vice versa.  That is true regardless of
+other license.  You can always link GPLv3-covered modules with
+AGPLv3-covered modules, and vice versa.  That is true regardless of
 whether some of the modules are libraries.&lt;/p&gt;
 &lt;/dd&gt;
 
@@ -4120,7 +4120,7 @@
 
 &lt;p class="unprintable"&gt;Updated:
 &lt;!-- timestamp start --&gt;
-$Date: 2023/03/01 17:30:36 $
+$Date: 2023/03/01 18:30:47 $
 &lt;!-- timestamp end --&gt;
 &lt;/p&gt;
 &lt;/div&gt;

Index: licenses/po/gpl-faq.ja.po
===================================================================
RCS file: /web/www/www/licenses/po/gpl-faq.ja.po,v
retrieving revision 1.117
retrieving revision 1.118
diff -u -b -r1.117 -r1.118
--- licenses/po/gpl-faq.ja.po   1 Mar 2023 17:00:04 -0000       1.117
+++ licenses/po/gpl-faq.ja.po   1 Mar 2023 18:30:47 -0000       1.118
@@ -6,7 +6,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: gpl-faq.html\n"
-"POT-Creation-Date: 2023-03-01 16:55+0000\n"
+"POT-Creation-Date: 2023-03-01 18:25+0000\n"
 "PO-Revision-Date: 2022-07-01 16:52+0900\n"
 "Last-Translator: NIIBE Yutaka <gniibe@fsij.org>\n"
 "Language-Team: Japanese <web-translators-ja@gnu.org>\n"
@@ -2578,7 +2578,7 @@
 #. type: Content of: <dl><dd><p>
 msgid ""
 "Each of these licenses explicitly permits linking with code under the other "
-"license.  You can always link GPL3-covered modules with AGPL3-covered "
+"license.  You can always link GPLv3-covered modules with AGPLv3-covered "
 "modules, and vice versa.  That is true regardless of whether some of the "
 "modules are libraries."
 msgstr ""

Index: licenses/po/gpl-faq.pl.po
===================================================================
RCS file: /web/www/www/licenses/po/gpl-faq.pl.po,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -b -r1.20 -r1.21
--- licenses/po/gpl-faq.pl.po   1 Mar 2023 17:00:04 -0000       1.20
+++ licenses/po/gpl-faq.pl.po   1 Mar 2023 18:30:47 -0000       1.21
@@ -8,7 +8,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: gpl-faq.html\n"
-"POT-Creation-Date: 2023-03-01 16:55+0000\n"
+"POT-Creation-Date: 2023-03-01 18:25+0000\n"
 "PO-Revision-Date: 2022-07-03 20:30-0600\n"
 "Last-Translator: Jan Owoc <jsowoc AT gmail DOT com>\n"
 "Language-Team: Polish <www-pl-trans@gnu.org>\n"
@@ -2672,7 +2672,7 @@
 #. type: Content of: <dl><dd><p>
 msgid ""
 "Each of these licenses explicitly permits linking with code under the other "
-"license.  You can always link GPL3-covered modules with AGPL3-covered "
+"license.  You can always link GPLv3-covered modules with AGPLv3-covered "
 "modules, and vice versa.  That is true regardless of whether some of the "
 "modules are libraries."
 msgstr ""

Index: licenses/po/gpl-faq.pot
===================================================================
RCS file: /web/www/www/licenses/po/gpl-faq.pot,v
retrieving revision 1.100
retrieving revision 1.101
diff -u -b -r1.100 -r1.101
--- licenses/po/gpl-faq.pot     1 Mar 2023 17:00:04 -0000       1.100
+++ licenses/po/gpl-faq.pot     1 Mar 2023 18:30:47 -0000       1.101
@@ -7,7 +7,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: gpl-faq.html\n"
-"POT-Creation-Date: 2023-03-01 16:55+0000\n"
+"POT-Creation-Date: 2023-03-01 18:25+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -1816,7 +1816,7 @@
 #. type: Content of: <dl><dd><p>
 msgid ""
 "Each of these licenses explicitly permits linking with code under the other "
-"license.  You can always link GPL3-covered modules with AGPL3-covered "
+"license.  You can always link GPLv3-covered modules with AGPLv3-covered "
 "modules, and vice versa.  That is true regardless of whether some of the "
 "modules are libraries."
 msgstr ""

Index: licenses/po/gpl-faq.ru-en.html
===================================================================
RCS file: /web/www/www/licenses/po/gpl-faq.ru-en.html,v
retrieving revision 1.82
retrieving revision 1.83
diff -u -b -r1.82 -r1.83
--- licenses/po/gpl-faq.ru-en.html      25 Feb 2023 14:34:01 -0000      1.82
+++ licenses/po/gpl-faq.ru-en.html      1 Mar 2023 18:30:47 -0000       1.83
@@ -668,14 +668,8 @@
     <li><a href="#SystemLibraryException">Can I link a GPL program with
     a proprietary system library?</a></li>
 
-    <li><a href="#AGPLPL">Can I link GPLv3-covered modules and
-    AGPLv3-covered modules into one executable?</a></li>
-
-    <li><a href="#AGPLLibrary">Can I link a GPLv3-covered program with
-    an AGPLv3-covered library?</a></li>
-
-    <li><a href="#AGPLAndGPLLibrary">Can I link an AGPLv3-covered program with
-    a GPLv3-covered library?</a></li>
+    <li><a href="#AGPLGPL">In what ways can I link or
+    combine AGPLv3-covered and GPLv3-covered code?</a></li>
 
     <li><a href="#GPLIncompatibleLibs">What legal issues come up if I
     use GPL-incompatible libraries with GPL software?</a></li>
@@ -1323,37 +1317,17 @@
 issue slightly differently, near the end of section 3.</p>
 </dd>
 
-<dt id="AGPLGPL">Can I link GPLv3-covered modules and
-    AGPLv3-covered modules into one executable?
+<dt id="AGPLGPL">In what ways can I link or combine
+AGPLv3-covered and GPLv3-covered code?
  <span class="anchor-reference-id">(<a
 href="#AGPLGPL">#AGPLGPL</a>)</span></dt>
 <dd><p>
-You can always link GPLv3-covered modules with AGPLv3-covered modules.
-That is because each of these licenses explicitly permits linking with
-code under the other license.</p>
-</dd>
-
-<dt id="AGPLLibrary">Can I link a GPLv3-covered program with
-    an AGPLv3-covered library?
- <span class="anchor-reference-id">(<a
-href="#AGPLLibrary">#AGPLLibrary</a>)</span></dt>
-<dd><p>
-You can always <a href="#AGPLGPL">link GPLv3-covered modules with
-AGPLv3-covered modules</a>.  That is true regardless of whether some of
-the modules are libraries.</p>
+Each of these licenses explicitly permits linking with code under the
+other license.  You can always link GPLv3-covered modules with
+AGPLv3-covered modules, and vice versa.  That is true regardless of
+whether some of the modules are libraries.</p>
 </dd>
 
-<dt id="AGPLAndGPLLibrary">Can I link an AGPLv3-covered program with
-    a GPLv3-covered library?
- <span class="anchor-reference-id">(<a
-href="#AGPLAndGPLLibrary">#AGPLAndGPLLibrary</a>)</span></dt>
-<dd><p>
-You can always <a href="#AGPLGPL">link GPLv3-covered modules with
-AGPLv3-covered modules</a>.  That is true regardless of whether some of
-the modules are libraries.</p>
-</dd>
-
-
 <dt id="GPLIncompatibleLibs">What legal issues
     come up if I use GPL-incompatible libraries with GPL software?
  <span class="anchor-reference-id">(<a href="#GPLIncompatibleLibs"
@@ -4044,7 +4018,7 @@
 
 <p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2023/02/25 14:34:01 $
+$Date: 2023/03/01 18:30:47 $
 <!-- timestamp end -->
 </p>
 </div>

Index: licenses/po/gpl-faq.ru.po
===================================================================
RCS file: /web/www/www/licenses/po/gpl-faq.ru.po,v
retrieving revision 1.199
retrieving revision 1.200
diff -u -b -r1.199 -r1.200
--- licenses/po/gpl-faq.ru.po   1 Mar 2023 18:16:58 -0000       1.199
+++ licenses/po/gpl-faq.ru.po   1 Mar 2023 18:30:47 -0000       1.200
@@ -12,7 +12,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: gpl-faq.html\n"
-"POT-Creation-Date: 2023-03-01 16:55+0000\n"
+"POT-Creation-Date: 2023-03-01 18:25+0000\n"
 "PO-Revision-Date: 2023-03-01 17:17+0000\n"
 "Last-Translator: Ineiev <ineiev@gnu.org>\n"
 "Language-Team: Russian <www-ru-list@gnu.org>\n"
@@ -20,7 +20,6 @@
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"X-Outdated-Since: 2023-03-01 16:55+0000\n"
 
 #. type: Content of: <title>
 msgid ""
@@ -1288,18 +1287,12 @@
 "с несвободной системной библиотекой?</a>"
 
 #. type: Content of: <div><ul><li>
-# | <a [-href=\"#AGPLAndGPLLibrary\">Can-] {+href=\"#AGPLGPL\">In what ways
-# | can+} I link [-an-] {+or combine+} AGPLv3-covered [-program with a-]
-# | {+and+} GPLv3-covered [-library?</a>-] {+code?</a>+}
-#| msgid ""
-#| "<a href=\"#AGPLAndGPLLibrary\">Can I link an AGPLv3-covered program with "
-#| "a GPLv3-covered library?</a>"
 msgid ""
 "<a href=\"#AGPLGPL\">In what ways can I link or combine AGPLv3-covered and "
 "GPLv3-covered code?</a>"
 msgstr ""
-"<a href=\"#AGPLGPL\">Могу ли я компоновать или 
комбинировать программы под AGPLv3 с "
-"программами под GPLv3?</a>"
+"<a href=\"#AGPLGPL\">Могу ли я компоновать или 
комбинировать программы под "
+"AGPLv3 с программами под GPLv3?</a>"
 
 #. type: Content of: <div><ul><li>
 msgid ""
@@ -2618,41 +2611,24 @@
 "другому, в конце раздела&nbsp;3."
 
 #. type: Content of: <dl><dt>
-# | [-Can-]{+In what ways can+} I link [-GPLv3-covered modules and-] {+or
-# | combine+} AGPLv3-covered [-modules into one executable?-] {+and
-# | GPLv3-covered code?+} <span class=\"anchor-reference-id\">(<a
-# | href=\"#AGPLGPL\">#AGPLGPL</a>)</span>
-#| msgid ""
-#| "Can I link GPLv3-covered modules and AGPLv3-covered modules into one "
-#| "executable? <span class=\"anchor-reference-id\">(<a href=\"#AGPLGPL"
-#| "\">#AGPLGPL</a>)</span>"
 msgid ""
 "In what ways can I link or combine AGPLv3-covered and GPLv3-covered code? "
 "<span class=\"anchor-reference-id\">(<a href=\"#AGPLGPL\">#AGPLGPL</a>)</"
 "span>"
 msgstr ""
-"Каким образом я могу компоновать или 
комбинировать программы под AGPLv3 и под "
-"GPLv3? <span class=\"anchor-reference-id\">(<a href=\"#AGPLGPL"
+"Каким образом я могу компоновать или 
комбинировать программы под AGPLv3 и "
+"под GPLv3? <span class=\"anchor-reference-id\">(<a href=\"#AGPLGPL"
 "\">#AGPLGPL</a>)</span>"
 
 #. type: Content of: <dl><dd><p>
-# | {+Each of these licenses explicitly permits linking with code under the
-# | other license.+}  You can always [-<a href=\"#AGPLGPL\">link
-# | GPLv3-covered-] {+link GPL3-covered+} modules with [-AGPLv3-covered
-# | modules</a>.-] {+AGPL3-covered modules, and vice versa.+}  That is true
-# | regardless of whether some of the modules are libraries.
-#| msgid ""
-#| "You can always <a href=\"#AGPLGPL\">link GPLv3-covered modules with "
-#| "AGPLv3-covered modules</a>.  That is true regardless of whether some of "
-#| "the modules are libraries."
 msgid ""
 "Each of these licenses explicitly permits linking with code under the other "
 "license.  You can always link GPLv3-covered modules with AGPLv3-covered "
 "modules, and vice versa.  That is true regardless of whether some of the "
 "modules are libraries."
 msgstr ""
-"Каждая из этих лицензий явным образом 
разрешает компоновку с программами "
-"под другой лицензией. Вы всегда можете 
компоновать модули под GPLv3 c модулями "
+"Каждая из этих лицензий явным образом 
разрешает компоновку с программами под "
+"другой лицензией. Вы всегда можете 
компоновать модули под GPLv3 c модулями "
 "под AGPLv3 и наоборот. Это верно независимо 
от того, являются ли некоторые "
 "из модулей библиотеками или нет."
 

Index: licenses/po/gpl-faq.ta.po
===================================================================
RCS file: /web/www/www/licenses/po/gpl-faq.ta.po,v
retrieving revision 1.91
retrieving revision 1.92
diff -u -b -r1.91 -r1.92
--- licenses/po/gpl-faq.ta.po   1 Mar 2023 17:00:04 -0000       1.91
+++ licenses/po/gpl-faq.ta.po   1 Mar 2023 18:30:47 -0000       1.92
@@ -9,7 +9,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: gpl-faq.html\n"
-"POT-Creation-Date: 2023-03-01 16:55+0000\n"
+"POT-Creation-Date: 2023-03-01 18:25+0000\n"
 "PO-Revision-Date: 2010-06-20 15:55+0530\n"
 "Last-Translator: Amachu <amachu@amachu.net>\n"
 "Language-Team: Tamil <web-translators@gnu.org>\n"
@@ -1927,7 +1927,7 @@
 #. type: Content of: <dl><dd><p>
 msgid ""
 "Each of these licenses explicitly permits linking with code under the other "
-"license.  You can always link GPL3-covered modules with AGPL3-covered "
+"license.  You can always link GPLv3-covered modules with AGPLv3-covered "
 "modules, and vice versa.  That is true regardless of whether some of the "
 "modules are libraries."
 msgstr ""

Index: licenses/po/gpl-faq.tr.po
===================================================================
RCS file: /web/www/www/licenses/po/gpl-faq.tr.po,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -b -r1.31 -r1.32
--- licenses/po/gpl-faq.tr.po   1 Mar 2023 17:00:04 -0000       1.31
+++ licenses/po/gpl-faq.tr.po   1 Mar 2023 18:30:47 -0000       1.32
@@ -7,7 +7,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: gpl-faq.html\n"
-"POT-Creation-Date: 2023-03-01 16:55+0000\n"
+"POT-Creation-Date: 2023-03-01 18:25+0000\n"
 "PO-Revision-Date: 2021-11-24 16:48+0100\n"
 "Last-Translator: T. E. Kalayci <tekrei@member.fsf.org>\n"
 "Language-Team: Turkish <www-tr-comm@gnu.org>\n"
@@ -2601,7 +2601,7 @@
 #. type: Content of: <dl><dd><p>
 msgid ""
 "Each of these licenses explicitly permits linking with code under the other "
-"license.  You can always link GPL3-covered modules with AGPL3-covered "
+"license.  You can always link GPLv3-covered modules with AGPLv3-covered "
 "modules, and vice versa.  That is true regardless of whether some of the "
 "modules are libraries."
 msgstr ""

Index: licenses/po/gpl-faq.zh-cn.po
===================================================================
RCS file: /web/www/www/licenses/po/gpl-faq.zh-cn.po,v
retrieving revision 1.39
retrieving revision 1.40
diff -u -b -r1.39 -r1.40
--- licenses/po/gpl-faq.zh-cn.po        1 Mar 2023 17:00:06 -0000       1.39
+++ licenses/po/gpl-faq.zh-cn.po        1 Mar 2023 18:30:47 -0000       1.40
@@ -6,7 +6,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: gpl-faq.html\n"
-"POT-Creation-Date: 2023-03-01 16:55+0000\n"
+"POT-Creation-Date: 2023-03-01 18:25+0000\n"
 "PO-Revision-Date: 2023-02-27 21:11+0800\n"
 "Last-Translator: Wensheng Xie <wxie@member.fsf.org>\n"
 "Language-Team: Chinese <www-zh-cn-translators@gnu.org>\n"
@@ -2330,7 +2330,7 @@
 #| "the modules are libraries."
 msgid ""
 "Each of these licenses explicitly permits linking with code under the other "
-"license.  You can always link GPL3-covered modules with AGPL3-covered "
+"license.  You can always link GPLv3-covered modules with AGPLv3-covered "
 "modules, and vice versa.  That is true regardless of whether some of the "
 "modules are libraries."
 msgstr ""

Index: software/recent-releases-include.ru.html
===================================================================
RCS file: /web/www/www/software/recent-releases-include.ru.html,v
retrieving revision 1.2576
retrieving revision 1.2577
diff -u -b -r1.2576 -r1.2577
--- software/recent-releases-include.ru.html    1 Mar 2023 14:59:55 -0000       
1.2576
+++ software/recent-releases-include.ru.html    1 Mar 2023 18:30:47 -0000       
1.2577
@@ -1,13 +1,13 @@
 
 <!--#set var="LINK_CLOSE" value="</a>, <i>" -->
 <ul>
-<li><strong>March 01, 2023</strong>
+<li><strong>01 марта 2023</strong>
 <ul>
 <li><!--#set var="LINK" 
 value='<a href="//lists.gnu.org/archive/html/info-gnu/2023-03/msg00000.html">' 
-->
 <!--#echo 
 encoding="none" var="LINK" -->
-GNU Guile-CV 0.4.0 release<!--#echo 
+Выпущен GNU Guile-CV 0.4.0<!--#echo 
 encoding="none" var="LINK_CLOSE" -->
 Давид Пиротт<!--#set 
 var="TIME" value="</i>, 09:34" -->

Index: software/po/recent-releases-include.ru.po
===================================================================
RCS file: /web/www/www/software/po/recent-releases-include.ru.po,v
retrieving revision 1.3644
retrieving revision 1.3645
diff -u -b -r1.3644 -r1.3645
--- software/po/recent-releases-include.ru.po   1 Mar 2023 18:16:58 -0000       
1.3644
+++ software/po/recent-releases-include.ru.po   1 Mar 2023 18:30:47 -0000       
1.3645
@@ -14,11 +14,8 @@
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"X-Outdated-Since: 2023-03-01 14:56+0000\n"
 
 #. type: Content of: <ul><li>
-# | <strong>March [-21, 2022</strong>-] {+01, 2023</strong>+}
-#| msgid "<strong>March 21, 2022</strong>"
 msgid "<strong>March 01, 2023</strong>"
 msgstr "<strong>01 марта 2023</strong>"
 
@@ -27,8 +24,6 @@
 #. #echo 
 #. encoding="none" var="LINK" 
 #. type: Content of: <ul><li><ul><li>
-# | GNU [-Guix 1.4.0 released-] {+Guile-CV 0.4.0 release+}
-#| msgid "GNU Guix 1.4.0 released"
 msgid "GNU Guile-CV 0.4.0 release"
 msgstr "Выпущен GNU Guile-CV 0.4.0"
 



reply via email to

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