www-commits
[Top][All Lists]
Advanced

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

www/licenses rms-why-gplv3.zh-cn.html po/rms-wh...


From: GNUN
Subject: www/licenses rms-why-gplv3.zh-cn.html po/rms-wh...
Date: Thu, 6 Jan 2022 04:09:40 -0500 (EST)

CVSROOT:        /web/www
Module name:    www
Changes by:     GNUN <gnun>     22/01/06 04:09:40

Modified files:
        licenses       : rms-why-gplv3.zh-cn.html 
        licenses/po    : rms-why-gplv3.zh-cn-en.html 
                         rms-why-gplv3.zh-cn.po 

Log message:
        Automatic update by GNUnited Nations.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/rms-why-gplv3.zh-cn.html?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/rms-why-gplv3.zh-cn-en.html?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/rms-why-gplv3.zh-cn.po?cvsroot=www&r1=1.5&r2=1.6

Patches:
Index: rms-why-gplv3.zh-cn.html
===================================================================
RCS file: /web/www/www/licenses/rms-why-gplv3.zh-cn.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- rms-why-gplv3.zh-cn.html    26 May 2020 08:32:08 -0000      1.1
+++ rms-why-gplv3.zh-cn.html    6 Jan 2022 09:09:40 -0000       1.2
@@ -1,16 +1,18 @@
 <!--#set var="ENGLISH_PAGE" value="/licenses/rms-why-gplv3.en.html" -->
 
 <!--#include virtual="/server/header.zh-cn.html" -->
-<!-- Parent-Version: 1.77 -->
+<!-- Parent-Version: 1.97 -->
+<!-- This page is derived from /server/standards/boilerplate.html -->
 
 <!-- This file is automatically generated by GNUnited Nations! -->
 <title>为什么要升级到 GPLv3 - GNU 工程 - 自由软件基金会</title>
 
 <!--#include virtual="/licenses/po/rms-why-gplv3.translist" -->
 <!--#include virtual="/server/banner.zh-cn.html" -->
+<div class="article reduced-width">
 <h2>为什么要升级到 GPLv3</h2>
 
-<p><strong>Richard Stallman</strong> 著</p>
+<address class="byline">Richard Stallman 著</address>
 
 <p><a href="/licenses/gpl.html">GNU 通用公共许可证第三版</a>(GNU 
GPL)发布了,它使自由软件包可以从 GPL
 版本 2 升级到版本 
3。本文解释为什么这次许可证升级是重要的。</p>
@@ -43,9 +45,8 @@
 <p id="drm">
 在数字限制管理(DRM)&mdash;&mdash;这是限制你
使用自己电脑上的数据的恶劣功能&mdash;&mdash;等严é…
·çš„领域,竞争没有用,因为相å…
³çš„竞争被禁止了。在诸如数字千禧版权法案之类的法律中,在美国和许多å
…¶ä»–国家,如果你没有按照“DVD
 阴谋”的官方规则(网站 <a
-href="http://www.dvdcca.org/";>http://www.dvdcca.org/</a>,但是规则看来并没有放上去)发布限制用户的
-DVD 播放器,那么你是非法的。公众无法通过购买非 DRM 
的播放器来拒绝
-DRM,因为没有这样的播放器。无论有多少种产品供你
选择,它们都是带有数字枷锁的。</p>
+href="https://www.dvdcca.org/";>www.dvdcca.org/</a>,但是规则看来并没有放上去)发布限制用户的
 DVD
+播放器,那么你是非法的。公众无法通过购买非 DRM 
的播放器来拒绝 DRM,因为没有这样的播放器。无
论有多少种产品供你选择,它们都是带有数字枷锁的。</p>
 
 <p>GPLv3 保证你有删除枷锁的自由。它不禁止
 DRM,也不禁止任何功能。它不限制你为程序添加或删
除重大的功能。反过来,它保证你有同样的自由发布删
除差劲功能的版本和添加差劲功能的版本。Tivoization
@@ -89,6 +90,7 @@
 其中一个方法是让程序按照 &ldquo;GPL 版本 3 
或任何以后版本&rdquo; 发布。另一个方法是程序的所有贡献者
声明一个能够决定升级 GPL
 将来版本的代理。第三个方法是所有贡献者
将版权转让给一个指定的版权持有者,该版权持有者
将处理许可证版本升级的问题。无
论采取哪一种方法,程序都应该提供应对将来版本的
 GPL 许可证的灵活性。</p>
+</div>
 
 <div class="translators-notes">
 
@@ -98,7 +100,7 @@
 
 <!-- for id="content", starts in the include above -->
 <!--#include virtual="/server/footer.zh-cn.html" -->
-<div id="footer">
+<div id="footer" role="contentinfo">
 <div class="unprintable">
 
 <p>请将有关自由软件基金会(FSF) &amp; 
GNU的一般性问题发送到<a
@@ -117,18 +119,18 @@
 
         &lt;web-translators@gnu.org&gt;</a>.</p>
 
-        <p>For information on coordinating and submitting translations of
+        <p>For information on coordinating and contributing translations of
         our web pages, see <a
         href="/server/standards/README.translations.html">Translations
         README</a>. -->
 我们尽最大努力来提供精准和高质量的翻译,但难å…
ä¼šå­˜åœ¨é”™è¯¯å’Œä¸è¶³ã€‚如果您在这方面有评论或一般性的建议,请发送至
 <a
 
href="mailto:web-translators@gnu.org";>&lt;web-translators@gnu.org&gt;</a>。</p><p>å
…³äºŽè¿›è¡Œåè°ƒä¸Žæäº¤ç¿»è¯‘的更多信息参见
-<a href="/server/standards/README.translators.html">《译者
指南》</a>。</p>
+<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
+     be under CC BY-ND 4.0.  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
@@ -142,27 +144,28 @@
      
      There is more detail about copyright years in the GNU Maintainers
      Information document, www.gnu.org/prep/maintain. -->
-<p>Copyright &copy; 2007, 2009, 2014 Richard Stallman</p>
+<p>Copyright &copy; 2007, 2009, 2022 Richard Stallman</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>
+href="http://creativecommons.org/licenses/by-nd/4.0/";>Creative Commons
+Attribution-NoDerivatives 4.0 International 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 rel="team"
-href="https://savannah.gnu.org/projects/www-zh-cn/";>&lt;CTT&gt;</a>,2020。</div>
+href="https://savannah.gnu.org/projects/www-zh-cn/";>&lt;CTT&gt;</a>,2020,2022。</div>
 
 <p class="unprintable"><!-- timestamp start -->
 最后更新:
 
-$Date: 2020/05/26 08:32:08 $
+$Date: 2022/01/06 09:09:40 $
 
 <!-- timestamp end -->
 </p>
 </div>
 </div>
+<!-- for class="inner", starts in the banner include -->
 </body>
 </html>

Index: po/rms-why-gplv3.zh-cn-en.html
===================================================================
RCS file: /web/www/www/licenses/po/rms-why-gplv3.zh-cn-en.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- po/rms-why-gplv3.zh-cn-en.html      26 May 2020 08:32:08 -0000      1.1
+++ po/rms-why-gplv3.zh-cn-en.html      6 Jan 2022 09:09:40 -0000       1.2
@@ -1,12 +1,14 @@
 <!--#include virtual="/server/header.html" -->
-<!-- Parent-Version: 1.77 -->
+<!-- Parent-Version: 1.97 -->
+<!-- This page is derived from /server/standards/boilerplate.html -->
 <title>Why Upgrade to GPLv3
 - GNU Project - Free Software Foundation</title>
 <!--#include virtual="/licenses/po/rms-why-gplv3.translist" -->
 <!--#include virtual="/server/banner.html" -->
+<div class="article reduced-width">
 <h2>Why Upgrade to GPLv3</h2>
 
-<p>by <strong>Richard Stallman</strong></p>
+<address class="byline">by Richard Stallman</address>
 
 <p><a href="/licenses/gpl.html">Version 3 of the GNU General Public
 License</a> (GNU GPL) has been released, enabling free software packages to
@@ -56,19 +58,20 @@
 <p>Some argue that competition between appliances in a free market should
 suffice to keep nasty features to a low level.  Perhaps competition
 alone would avoid arbitrary, pointless misfeatures like &ldquo;Must shut
-down between 1pm and 5pm every Tuesday&rdquo;, but even so, a choice of
+down between 1pm and 5pm every Tuesday,&rdquo; but even so, a choice of
 masters isn't freedom.  Freedom means <em>you</em> control what your software
 does, not merely that you can beg or threaten someone else who decides
 for you.</p>
 
 <p id="drm">
-In the crucial area of Digital Restrictions Management (DRM)&mdash;nasty 
features
-designed to restrict your use of the data in your
+In the crucial area of Digital Restrictions Management (DRM)&mdash;nasty
+features designed to restrict your use of the data in your
 computer&mdash;competition is no help, because relevant competition is
 forbidden.  Under the Digital Millennium Copyright Act and similar
 laws, it is illegal, in the US and many other countries, to distribute
 DVD players unless they restrict the user according to the official
-rules of the DVD conspiracy (its web site is <a 
href="http://www.dvdcca.org/";>http://www.dvdcca.org/</a>,
+rules of the DVD conspiracy (its web site is <a
+href="https://www.dvdcca.org/";>www.dvdcca.org/</a>,
 but the rules do not seem to be published there).  The public can't
 reject DRM by buying non-DRM players because none are available.  No
 matter how many products you can choose from, they all have equivalent
@@ -82,7 +85,8 @@
 deny you that freedom; to protect your freedom, GPLv3 forbids
 tivoization.</p>
 
-<p>The ban on tivoization applies to any product whose use by consumers is to 
be expected, even occasionally.  GPLv3 tolerates tivoization
+<p>The ban on tivoization applies to any product whose use by consumers
+is to be expected, even occasionally.  GPLv3 tolerates tivoization
 only for products that are almost exclusively meant for businesses and
 organizations.</p>
 
@@ -100,7 +104,7 @@
 
 <p>Microsoft's lawyers are not stupid, and next time they may manage to
 avoid those mistakes.  GPLv3 therefore says they don't get a &ldquo;next
-time&rdquo;.  Releasing a program under GPL version 3 protects it from
+time.&rdquo;  Releasing a program under GPL version 3 protects it from
 Microsoft's future attempts to make redistributors collect Microsoft
 royalties from the program's users.</p>
 
@@ -138,14 +142,12 @@
 explicit patent license of GPLv3 makes sure companies that use the GPL
 to give users the four freedoms cannot turn around and use their
 patents to tell some users, &ldquo;That doesn't include you.&rdquo;
-It also stops
-them from colluding with other patent holders to do this.</p>
+It also stops them from colluding with other patent holders to do this.</p>
 
 <p id="further-advantages">
 Further advantages of GPLv3 include better internationalization, gentler
 termination, support for BitTorrent, and compatibility with the Apache
-license.  All in all, plenty of
-reason to upgrade.</p>
+license.  All in all, plenty of reason to upgrade.</p>
 
 <p id="gpl4">
 Change is unlikely to cease once GPLv3 is released.  If new threats to
@@ -155,16 +157,17 @@
 
 <p id="future-proofing">
 One way to do this is to release a program under &ldquo;GPL version 3 or any
-later version&rdquo;.  Another way is for all the contributors to a program
+later version.&rdquo;  Another way is for all the contributors to a program
 to state a proxy who can decide on upgrading to future GPL versions.
 The third way is for all the contributors to assign copyright to one
 designated copyright holder, who will be in a position to upgrade the
 license version.  One way or another, programs should provide this
 flexibility for future GPL versions.</p>
+</div>
 
 </div><!-- for id="content", starts in the include above -->
 <!--#include virtual="/server/footer.html" -->
-<div id="footer">
+<div id="footer" role="contentinfo">
 <div class="unprintable">
 
 <p>Please send general FSF &amp; GNU inquiries to
@@ -182,19 +185,19 @@
         to <a href="mailto:web-translators@gnu.org";>
         &lt;web-translators@gnu.org&gt;</a>.</p>
 
-        <p>For information on coordinating and submitting translations of
+        <p>For information on coordinating and contributing 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
+README</a> for information on coordinating and contributing 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
+     be under CC BY-ND 4.0.  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
@@ -209,20 +212,20 @@
      There is more detail about copyright years in the GNU Maintainers
      Information document, www.gnu.org/prep/maintain. -->
 
-<p>Copyright &copy; 2007, 2009, 2014 Richard Stallman</p>
+<p>Copyright &copy; 2007, 2009, 2022 Richard Stallman</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>
+href="http://creativecommons.org/licenses/by-nd/4.0/";>Creative
+Commons Attribution-NoDerivatives 4.0 International License</a>.</p>
 
 <!--#include virtual="/server/bottom-notes.html" -->
 
 <p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2020/05/26 08:32:08 $
+$Date: 2022/01/06 09:09:40 $
 <!-- timestamp end -->
 </p>
 </div>
-</div>
+</div><!-- for class="inner", starts in the banner include -->
 </body>
 </html>

Index: po/rms-why-gplv3.zh-cn.po
===================================================================
RCS file: /web/www/www/licenses/po/rms-why-gplv3.zh-cn.po,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -b -r1.5 -r1.6
--- po/rms-why-gplv3.zh-cn.po   6 Jan 2022 08:30:03 -0000       1.5
+++ po/rms-why-gplv3.zh-cn.po   6 Jan 2022 09:09:40 -0000       1.6
@@ -14,7 +14,6 @@
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"X-Outdated-Since: 2022-01-02 17:25+0000\n"
 
 #. type: Content of: <title>
 msgid "Why Upgrade to GPLv3 - GNU Project - Free Software Foundation"



reply via email to

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