www/licenses po/why-affero-gpl.translist why-af...

[GNUN]

CVSROOT:        /web/www
Module name:    www
Changes by:     GNUN <gnun>     18/08/26 01:27:37

Modified files:
        licenses/po    : why-affero-gpl.translist 
Added files:
        licenses       : why-affero-gpl.zh-cn.html 
        licenses/po    : why-affero-gpl.zh-cn-en.html 

Log message:
        Automatic update by GNUnited Nations.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/why-affero-gpl.zh-cn.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/why-affero-gpl.translist?cvsroot=www&r1=1.19&r2=1.20
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/why-affero-gpl.zh-cn-en.html?cvsroot=www&rev=1.1

Patches:
Index: po/why-affero-gpl.translist
===================================================================
RCS file: /web/www/www/licenses/po/why-affero-gpl.translist,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -b -r1.19 -r1.20
--- po/why-affero-gpl.translist 30 May 2018 20:30:51 -0000      1.19
+++ po/why-affero-gpl.translist 26 Aug 2018 05:27:36 -0000      1.20
@@ -13,6 +13,7 @@
 <span dir="ltr"><a lang="ko" hreflang="ko" 
href="/licenses/why-affero-gpl.ko.html">한국어</a>&nbsp;[ko]</span> &nbsp;
 <span dir="ltr"><a lang="pt-br" hreflang="pt-br" 
href="/licenses/why-affero-gpl.pt-br.html">português&nbsp;do&nbsp;Brasil</a>&nbsp;[pt-br]</span>
 &nbsp;
 <span dir="ltr"><a lang="ru" hreflang="ru" 
href="/licenses/why-affero-gpl.ru.html">русский</a>&nbsp;[ru]</span> 
&nbsp;
+<span dir="ltr"><a lang="zh-cn" hreflang="zh-cn" 
href="/licenses/why-affero-gpl.zh-cn.html">简体中文</a>&nbsp;[zh-cn]</span> 
&nbsp;
 </p>
 </div>' -->
 <link rel="alternate" type="text/html" href="/licenses/why-affero-gpl.html" 
hreflang="x-default" />
@@ -27,4 +28,5 @@
 <link rel="alternate" type="text/html" lang="ko" hreflang="ko" 
href="/licenses/why-affero-gpl.ko.html" title="한국어" />
 <link rel="alternate" type="text/html" lang="pt-br" hreflang="pt-br" 
href="/licenses/why-affero-gpl.pt-br.html" title="português do Brasil" />
 <link rel="alternate" type="text/html" lang="ru" hreflang="ru" 
href="/licenses/why-affero-gpl.ru.html" title="русский" />
+<link rel="alternate" type="text/html" lang="zh-cn" hreflang="zh-cn" 
href="/licenses/why-affero-gpl.zh-cn.html" title="简体中文" />
 <!-- end translist file -->

Index: why-affero-gpl.zh-cn.html
===================================================================
RCS file: why-affero-gpl.zh-cn.html
diff -N why-affero-gpl.zh-cn.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ why-affero-gpl.zh-cn.html   26 Aug 2018 05:27:36 -0000      1.1
@@ -0,0 +1,127 @@
+<!--#set var="ENGLISH_PAGE" value="/licenses/why-affero-gpl.en.html" -->
+
+<!--#include virtual="/server/header.zh-cn.html" -->
+<!-- Parent-Version: 1.77 -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>为什么要使用 GNU Affero GPL - GNU工程 - 
自由软件基金会</title>
+
+<!--#include virtual="/licenses/po/why-affero-gpl.translist" -->
+<!--#include virtual="/server/banner.zh-cn.html" -->
+<h2>为什么要使用GNU Affero GPL</h2>
+
+<p>GNU Affero<sup><a href="#TransNote1">1</a></sup>通用公å…
±è®¸å¯è¯æ˜¯ç”±æ™®é€šçš„ GNU
+公å…
±è®¸å¯è¯ç¬¬ä¸‰ç‰ˆçš„修改版。它有一个额外要求：如果您在服务器上运行一个由
 GNU AGPL
+许可的修改版的软件，并且让å…
¶ä»–用户与这个软件通信，那么这个服务器也必须å…
è®¸ä»–ä»¬ä¸‹è½½è¿™ä¸ªæ­£åœ¨è¿è¡Œçš„ä¿®æ”¹ç‰ˆæœ¬ç›¸å¯¹åº”çš„æºä»£ç ã€‚</p>
+
+<p>GNU Affero GPL 的用途是避å…
é‚£äº›å½±å“å¸¸ç”¨åœ¨æœåŠ¡å™¨ä¸Šçš„自由软件的开发人员的问题。</p>
+
+<p>假设您在普通的 GNU GPL 下开发和发布程序，如果开发人员 
D 修改了程序并且发布了它，那么 GPL 会要求他在 GPL
+ä¸‹å‘å¸ƒä»–çš„ç‰ˆæœ¬ã€‚å› 
此，如果您获得了他的修改版本，您可以自由地将他的部分或å
…¨éƒ¨æ›´æ”¹åˆå¹¶åˆ°æ‚¨è‡ªå·±çš„版本中。</p>
+
+<p>但是假如这个程序主要是在服务器上有用，当 D
+修改程序时，他很有可能会在自己的服务器上运行它而不发布副本。然后，您将永远得不到他的版本的源代ç
 å‰¯æœ¬ï¼Œæ‰€ä»¥æ‚¨æ°¸è¿œæ— 法将他的修改包
å«è¿›æ‚¨çš„ç‰ˆæœ¬ï¼Œæ‚¨å¯èƒ½ä¸ä¼šå–œæ¬¢è¿™æ ·çš„ç»“æžœã€‚</p>
+
+<p>使用 GNU Affero 通用公共许可证就避免了这种结果。如果 D
+在每个人都可以使用的服务器上运行他的版本，那么您也可以也可以使用它。假如他遵守许可证要求，让服务器的用户下载他的版本的源代ç
 ï¼Œé‚£ä¹ˆæ‚¨ä¹Ÿå¯ä»¥è¿™æ 
·åšï¼Œç„¶åŽæ‚¨å¯ä»¥å°†ä»–的修改合并到您的版本中。（如果他没有遵守，您可让您的律师向他投诉。）</p>
+
+<p>普通的 GNU 通用公共许可证第3版和 <tt>GNU Affero GPL</tt><sup><a
+href="#TransNote1"></a></sup> 都有å…
è®¸æ‚¨åœ¨ä¸€ä¸ªç¨‹åºä¸­å°†è¿™ä¸¤ä¸ªè®¸å¯è¯ä¸‹çš„模块链接在一起的文本。</p>
+
+<p>GNU Affero GPL 并没有解决<a
+href="/philosophy/who-does-that-server-really-serve.html">“服务作为软件替代品(SaaSS)”</a>的问题。</p>
+
+<p>SaaSS 的意思是，用户使用其他人的 web
+服务器来完成用户自己的计算。这要求他们将数据发送到服务器，服务器为他们进行计算，并将结果发送回给他们。SaaSS
+æ˜¯ä¸å…¬æ­£çš„ï¼Œå› ä¸ºç”¨æˆ·æ— æ³•æŽ§åˆ¶å…¶è®¡ç®—è¿‡ç¨‹ã€‚</p>
+
+<p>如果这个服务器上的某个程序是在 GNU Affero GPL
+下发布的，那么服务器就需要为用户提供相应的源代ç 
ã€‚这很好，但是拥有这个源代ç 
å¹¶ä¸ä¼šè®©ç”¨æˆ·æŽ§åˆ¶æœåŠ¡å™¨ä¸Šçš„计算。它也不会告诉用户，有什么å
…
¶å®ƒä»¥åˆ«çš„方式检查或更改用户数据的软件可能也运行在同一服务器。</p>
+
+<p>我们没有看到任何合理的方法在特定程序上用许可证条款来解决
 SaaSS 问题。甚至写一条区分使用 SaaSS
+与否的法律条款也是一种挑战，并且即使我们有这æ 
·çš„许可证，我们也不会看到程序许可证会对能解决 SaaSS 
固有问题的 SaaSS
+æ¡ˆä¾‹ä½œä»»ä½•è¦æ±‚ã€‚å› æ­¤ï¼Œæˆ‘ä»¬å¯¹ SaaSS 
问题的解决方案很简单：拒绝使用SaaSS服务。</p>
+
+<p>如果一个程序是专门针对 SaaSS çš„ï¼Œä½ 
不应该写它。但是许多程序对于各种各æ 
·çš„服务是有用的，包括 SaaSS 的和非 SaaSS
+的。编写和发行这些程序是很有用的（最好是在 AGPL 
ä¸‹ï¼‰ï¼Œè¿™æ ·äººä»¬å°±å¯ä»¥ç”¨å®ƒä»¬å»ºç«‹éž SaaSS 服务。</p>
+
+<div class="translators-notes">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
+<h3>译注</h3>
+<ol>
+<li id="TransNote1">æ ¹æ® GNU 官方的说明，Affero 通用公å…
±è®¸å¯è¯ç¬¬ 1 版不是一个 GNU è®¸å¯è¯ï¼Œä½†å®ƒè®¾è®¡çš„ç›®æ ‡ä¸Ž
+GNU AGPL 类似。</li>
+</ol></div>
+</div>
+
+<!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.zh-cn.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>请将有å…
³è‡ªç”±è½¯ä»¶åŸºé‡‘会（FSF）&amp;GNU的一般性问题发送到<a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>。也可以通过<a
+href="/contact/">å…
¶ä»–联系方法</a>联系自由软件基金会(FSF)ã€‚è¯·å°†æ— æ•ˆé“¾æŽ¥ï¼Œå…
¶ä»–错误或建议发送给<a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>。</p>
+
+<p>
+<!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to <a href="mailto:address@hidden";>
+
+        &lt;address@hidden&gt;</a>.</p>
+
+        <p>For information on coordinating and submitting translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+若您想翻译本文，请参看<a 
href="/server/standards/README.translations.html">翻译须知</a>。</p>
+</div>
+
+<!-- Regarding copyright, in general, standalone pages (as opposed to
+     files generated as part of manuals) on the GNU web server should
+     be under CC BY-ND 3.0 US.  Please do NOT change or remove this
+     without talking with the webmasters or licensing team first.
+     Please make sure the copyright date is consistent with the
+     document.  For web pages, it is ok to list just the latest year the
+     document was modified, or published.
+     
+     If you wish to list earlier years, that is ok too.
+     Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+     years, as long as each year in the range is in fact a copyrightable
+     year, i.e., a year in which the document was published (including
+     being publicly visible on the web or in a revision control system).
+     
+     There is more detail about copyright years in the GNU Maintainers
+     Information document, www.gnu.org/prep/maintain. -->
+<p>Copyright &copy; 2010, 2013, 2014, 2015 Free Software Foundation, Inc.</p>
+
+<p>本页面使用<a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/";>Creative Commons
+Attribution-NoDerivs 3.0 United States License</a>授权。</p>
+
+<!--#include virtual="/server/bottom-notes.zh-cn.html" -->
+<div class="translators-credits">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
+<b>翻译</b>：<a
+href="mailto:address@hidden";>&lt;IFRFSX&gt;</a>，2018。<br></br>
+<b>翻译团队</b>：<a rel="team"
+href="https://savannah.gnu.org/projects/www-zh-cn/";>&lt;CTT&gt;</a>，2018。</div>
+
+<p class="unprintable"><!-- timestamp start -->
+最后更新：
+
+$Date: 2018/08/26 05:27:36 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>

Index: po/why-affero-gpl.zh-cn-en.html
===================================================================
RCS file: po/why-affero-gpl.zh-cn-en.html
diff -N po/why-affero-gpl.zh-cn-en.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ po/why-affero-gpl.zh-cn-en.html     26 Aug 2018 05:27:36 -0000      1.1
@@ -0,0 +1,138 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.77 -->
+<title>Why the GNU Affero GPL
+- GNU Project - Free Software Foundation</title>
+<!--#include virtual="/licenses/po/why-affero-gpl.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>Why the Affero GPL</h2>
+
+<p>The GNU Affero General Public License is a modified version of the
+ordinary GNU GPL version 3.  It has one added requirement: if you run
+a modified program on a server and let other users communicate with it
+there, your server must also allow them to download the source code
+corresponding to the modified version running there.</p>
+
+<p>The purpose of the GNU Affero GPL is to prevent a problem that
+affects developers of free programs that are often used on
+servers.</p>
+
+<p>Suppose you develop and release a free program under the ordinary
+GNU GPL.  If developer D modifies the program and releases it, the GPL
+requires him to distribute his version under the GPL too.  Thus, if
+you get a copy of his version, you are free to incorporate some or all
+of his changes into your own version.</p>
+
+<p>But suppose the program is mainly useful on servers.  When D
+modifies the program, he might very likely run it on his own server
+and never release copies.  Then you would never get a copy of the
+source code of his version, so you would never have the chance to
+include his changes in your version.  You may not like that
+outcome.</p>
+
+<p>Using the GNU Affero GPL avoids that outcome.  If D runs his
+version on a server that everyone can use, you too can use it.
+Assuming he has followed the license requirement to let the server's
+users download the source code of his version, you can do so, and then
+you can incorporate his changes into your version.  (If he hasn't
+followed it, you have your lawyer complain to him.)</p>
+
+<p>Both the ordinary GNU GPL, version 3, and the GNU Affero GPL have
+text allowing you to link together modules under these two licenses in
+one program.</p>
+
+<p>The GNU Affero GPL does not address the problem
+of <a href="/philosophy/who-does-that-server-really-serve.html">
+Service as a Software Substitute (SaaSS)</a>.</p>
+
+<p>SaaSS means that users use someone else's web server to do their
+own computing.  This requires them to send their data to the server,
+which does their computing for them and sends the results back to
+them.  SaaSS is an injustice because the users cannot control their
+computing when it's done that way.</p>
+
+<p>If some program on this server is released under the GNU Affero
+GPL, the server is required to offer the users the corresponding
+source of that program.  That is good, but having this source code
+does not give them control over the computing done on that server.  It
+also does not tell them what other software may be running on that
+server, examining or changing their data in other ways.</p>
+
+<p>We don't see any sensible way to address the SaaSS problem with
+license conditions on particular programs.  Even to write a legal
+condition to distinguish between SaaSS use and non-SaaSS use would be
+a challenge, and if we had that, we don't see anything that the
+program's license might require in the SaaSS case that would correct
+the inherent wrong of SaaSS.  Thus, our solution to the problem of
+SaaSS is simple: refuse to use services that are SaaSS.</p>
+
+<p>If a program is meant specifically and only for SaaSS, you
+shouldn't write it.  But many programs are useful for a variety of
+kinds of services, including some that are SaaSS and some that are
+not.  It's useful to write and release these programs so people can
+set up non-SaaSS services with them, and good to release them under
+the AGPL.</p>
+
+</div><!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>Please send general FSF &amp; GNU inquiries to
+<a href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.
+There are also <a href="/contact/">other ways to contact</a>
+the FSF.  Broken links and other corrections or suggestions can be sent
+to <a href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.</p>
+
+<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to <a href="mailto:address@hidden";>
+        &lt;address@hidden&gt;</a>.</p>
+
+        <p>For information on coordinating and submitting translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+Please see the <a
+href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting translations
+of this article.</p>
+</div>
+
+<!-- Regarding copyright, in general, standalone pages (as opposed to
+     files generated as part of manuals) on the GNU web server should
+     be under CC BY-ND 3.0 US.  Please do NOT change or remove this
+     without talking with the webmasters or licensing team first.
+     Please make sure the copyright date is consistent with the
+     document.  For web pages, it is ok to list just the latest year the
+     document was modified, or published.
+     
+     If you wish to list earlier years, that is ok too.
+     Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+     years, as long as each year in the range is in fact a copyrightable
+     year, i.e., a year in which the document was published (including
+     being publicly visible on the web or in a revision control system).
+     
+     There is more detail about copyright years in the GNU Maintainers
+     Information document, www.gnu.org/prep/maintain. -->
+
+<p>Copyright &copy; 2010, 2013, 2014, 2015 Free Software Foundation, Inc.</p>
+
+<p>This page is licensed under a <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/";>Creative
+Commons Attribution-NoDerivs 3.0 United States License</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2018/08/26 05:27:36 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>