www-commits
[Top][All Lists]
Advanced

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

www licenses/gplv3-the-program.zh-cn.html licen...


From: GNUN
Subject: www licenses/gplv3-the-program.zh-cn.html licen...
Date: Mon, 20 Dec 2021 20:30:17 -0500 (EST)

CVSROOT:        /web/www
Module name:    www
Changes by:     GNUN <gnun>     21/12/20 20:30:17

Modified files:
        licenses       : gplv3-the-program.zh-cn.html 
        licenses/po    : gplv3-the-program.zh-cn-en.html 
                         gplv3-the-program.zh-cn.po 
        proprietary    : proprietary.zh-cn.html 
        proprietary/po : proprietary.zh-cn-en.html proprietary.zh-cn.po 
                         zh-cn.po 

Log message:
        Automatic update by GNUnited Nations.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/gplv3-the-program.zh-cn.html?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gplv3-the-program.zh-cn-en.html?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gplv3-the-program.zh-cn.po?cvsroot=www&r1=1.7&r2=1.8
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/proprietary.zh-cn.html?cvsroot=www&r1=1.71&r2=1.72
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/proprietary.zh-cn-en.html?cvsroot=www&r1=1.72&r2=1.73
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/proprietary.zh-cn.po?cvsroot=www&r1=1.290&r2=1.291
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/zh-cn.po?cvsroot=www&r1=1.251&r2=1.252

Patches:
Index: licenses/gplv3-the-program.zh-cn.html
===================================================================
RCS file: /web/www/www/licenses/gplv3-the-program.zh-cn.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- licenses/gplv3-the-program.zh-cn.html       28 Jul 2019 08:29:49 -0000      
1.1
+++ licenses/gplv3-the-program.zh-cn.html       21 Dec 2021 01:30:16 -0000      
1.2
@@ -1,22 +1,25 @@
 <!--#set var="ENGLISH_PAGE" value="/licenses/gplv3-the-program.en.html" -->
 
 <!--#include virtual="/server/header.zh-cn.html" -->
-<!-- Parent-Version: 1.77 -->
+<!-- Parent-Version: 1.96 -->
+<!-- This page is derived from /server/standards/boilerplate.html -->
 
 <!-- This file is automatically generated by GNUnited Nations! -->
-<title>GPLv3 的 &quot;程序&quot; 指的是什么? - GNU 工程 - 
自由软件基金会</title>
+<title>GPLv3 的 &ldquo;程序&rdquo; 指的是什么? - GNU 工程 - 
自由软件基金会</title>
 
 <!--#include virtual="/licenses/po/gplv3-the-program.translist" -->
 <!--#include virtual="/server/banner.zh-cn.html" -->
-<h2>GPLv3 的 &quot;程序&quot; 指的是什么?</h2>
+<div class="article reduced-width">
+<h2>GPLv3 的 &ldquo;程序&rdquo; 指的是什么?</h2>
+<div class="thin"></div>
 
 <h3>总结</h3>
 
-<p>在 GNU 通用公共许可证的第三版(GPLv3),&quot;程序&quot; 
一词表示一个具体的按照 GPLv3
+<p>在 GNU 通用公共许可证的第三版(GPLv3),&ldquo;程序&rdquo; 
一词表示一个具体的按照 GPLv3
 
授权的作品,该作品已由某个被授权方从上游的授权方或发行è€
…处接收。程序就是你按照一个 GPLv3 
许可证的实例接收到的一个具体的软件作品。</p>
 
-<p>&quot;程序&quot; 不可能是指 &quot;所有按照 GPLv3 
授权的作品&quot;;这种解释毫无意义,因为 &quot;程序&quot;
-是单一的:那么多的不同程序并不组成一个单独的程序。</p>
+<p>&ldquo;程序&rdquo; 不可能是指 &ldquo;所有按照 GPLv3 
授权的作品&rdquo;;这种解释毫无意义,因为
+&ldquo;程序&rdquo; 
是单一的:那么多的不同程序并不组成一个单独的程序。</p>
 
 <p>具体来说,这个解释符合 GPLv3 第 10 节第 3 段的陈述:</p>
 
@@ -31,57 +34,57 @@
 
 <h3>进一步分析</h3>
 
-<p>GPLv3 这样定义 &quot;程序&quot;:</p>
+<p>GPLv3 这样定义 &ldquo;程序&rdquo;:</p>
 
-<blockquote><p>&quot;程序&quot; 
是指任何使用此许可证授权的版权作品。</p></blockquote>
+<blockquote><p>&ldquo;程序&rdquo; 
是指任何使用此许可证授权的版权作品。</p></blockquote>
 
 <p>有些人认为在给定的授权上下文中,这个定义可以按ç…
§æ˜¯æŒ‡æ‰€æœ‰ GPLv3 作品,而不是按照由接受者收到的单个 GPLv3 
作品来解读。这些读者表达了对
 GPLv3 中新的专利规定带来后果的特别担忧,尤其是对第 10 
节第 3 段中专利中止条件和第 11 节第 3
-段中由上游发行者作出的快速专利授权。这种对 
&quot;程序&quot; 的过度宽泛的解读是错误的,这违背我们作为 
GPLv3 起草者的意图。</p>
+段中由上游发行者作出的快速专利授权。这种对 
&ldquo;程序&rdquo; 
的过度宽泛的解读是错误的,这违背我们作为 GPLv3 起草者
的意图。</p>
 
-<p>&quot;任何&quot;一词在英语中有多个、微妙的意义。在某些语境中,&quot;任何&quot;意味着&quot;每一个&quot;或è€
…&quot;全部&quot;;在其他情况,包括在
+<p>&ldquo;任何&rdquo;一词在英语中有多个、微妙的意义。在某些语境中,&ldquo;任何&rdquo;意味着&ldquo;每一个&rdquo;或è€
…&ldquo;全部&rdquo;;在其他情况,包括在
 GPLv3
-的&quot;程序&quot;的定义中,它是指&quot;许多可能性中选出的一个特定案例&quot;。这种解释å¿
…须在特定的语境中得以澄清。语境可以澄清
,但是也需要认真思考。</p>
+的&ldquo;程序&rdquo;的定义中,它是指&ldquo;许多可能性中选出的一个特定案例&rdquo;。这种解释å¿
…须在特定的语境中得以澄清。语境可以澄清
,但是也需要认真思考。</p>
 
-<p>我们可以对 &quot;程序&quot; 
的定义使用不同的措辞,比如使用 &quot;一个特定&quot; 代替
-&quot;任何&quot;,但是这并不能消除多种思考。&quot;按ç…
§è¯¥è®¸å¯è¯æŽˆæƒçš„一个特定作品&quot;这个说法,就隔离而言,并不一定表示
 *该*
-特定作品在某个特定的授权活动中被特定的 &quot;你&quot;
+<p>我们可以对 &ldquo;程序&rdquo; 
的定义使用不同的措辞,比如使用 &ldquo;一个特定&rdquo; 代替
+&ldquo;任何&rdquo;,但是这并不能消除多种思考。&ldquo;按ç…
§è¯¥è®¸å¯è¯æŽˆæƒçš„一个特定作品&rdquo;这个说法,就隔离而言,并不一定表示
+*该* 特定作品在某个特定的授权活动中被特定的 &ldquo;你
&rdquo;
 接收。我们对å…
¶ä»–自由软件许可证的审查也揭示了类似的解读问题,都是å…
³äºŽä¸ºä¿ƒè¿›è®¸å¯è¯å¤ç”¨è€Œä½¿ç”¨å¸¸è§„词汇的问题。</p>
 
-<p>既然我们不能明确地拒绝所有的解释,&quot;任何&quot;就有一定的优势。在某种程度上,它比å
…¶ä»–的词汇更不正式并且更少在法律层面使用,是开发者阅
读和应用许可证的合适词汇。另外,&quot;任何&quot;的用法,既然是在多个可能性中作出的选择,那么它就有强调
+<p>既然我们不能明确地拒绝所有的解释,&ldquo;任何&rdquo;就有一定的优势。在某种程度上,它比å
…¶ä»–的词汇更不正式并且更少在法律层面使用,是开发者阅
读和应用许可证的合适词汇。另外,&ldquo;任何&rdquo;的用法,既然是在多个可能性中作出的选择,那么它就有强调
 GPLv3 对多个软件作品和在多重许可证条件下å…
·æœ‰å¯é‡ç”¨æ€§çš„效果。GNU GPL 就是要让许多开发者
在他们的程序中使用,我们必须清楚这一点。</p>
 
-<p>GPLv3 中 &quot;任何&quot; 的用法引起的担忧在 GPLv2 中也一æ 
·å­˜åœ¨ã€‚GPLv2 的第 0 节说:</p>
+<p>GPLv3 中 &ldquo;任何&rdquo; 的用法引起的担忧在 GPLv2 中也一æ 
·å­˜åœ¨ã€‚GPLv2 的第 0 节说:</p>
 
-<blockquote><p>本许可证适用于所有程序或作品,只要该程序或作品的版权持有è€
…在程序或作品中声明它可以按照该公å…
±é€šç”¨è®¸å¯è¯æ¥å‘布。以下的 &quot;程序&quot;
-一词,是指这种程序或作品,以及 
&quot;基于这种程序的作品&quot;,即该程序或任何å…
¶ç‰ˆæƒæ³•æ„ä¹‰ä¸‹çš„衍生作品&hellip;</p></blockquote>
+<blockquote><p>本许可证适用于所有程序或作品,只要该程序或作品的版权持有è€
…在程序或作品中声明它可以按照该公å…
±é€šç”¨è®¸å¯è¯æ¥å‘布。以下的 &ldquo;程序&rdquo;
+一词,是指这种程序或作品,以及 
&ldquo;基于这种程序的作品&rdquo;,即该程序或任何å…
¶ç‰ˆæƒæ³•æ„ä¹‰ä¸‹çš„衍生作品&hellip;</p></blockquote>
 
-<p>然而,正如 FSF 和其他使用 GPL 的社区所一直理解的那æ 
·ï¼Œ &quot;程序&quot; 在 GPLv2 中的意思是特指你收到的 GPL
-作品,在你作出任何修改之前的作品。GPLv3 中 
&quot;程序&quot; 还是要保留这个定义。</p>
+<p>然而,正如 FSF 和其他使用 GPL 的社区所一直理解的那æ 
·ï¼Œ &ldquo;程序&rdquo; 在 GPLv2 中的意思是特指你收到的 GPL
+作品,在你作出任何修改之前的作品。GPLv3 中 
&ldquo;程序&rdquo; 还是要保留这个定义。</p>
 
-<p>在 GPLv3 中并没有任何条款可以使 &quot;程序&quot;(及其
-&quot;涵盖作品&quot;)的更广泛的延伸意义显得有道理或者
有实际效果,这些都和条款的措辞与修订历史保持一致。GPLv3
+<p>在 GPLv3 中并没有任何条款可以使 &ldquo;程序&rdquo;(及其
+&ldquo;涵盖作品&rdquo;)的更广泛的延伸意义显得有道理或者
有实际效果,这些都和条款的措辞与修订历史保持一致。GPLv3
 的专利条款正是一个恰当的例子。</p>
 
 <p>第 11 节的第三段说:</p>
 
 <blockquote><p>每个贡献者都按照其基本专利主张授权你
拥有非独占的、全球性的、无版税的专利许可,你可以制造
、使用、销售、出售、进口和运行、修改以及传
播这些贡献者版本的内容。</p></blockquote>
 
-<p>&quot;贡献者&quot; 的定义是 
&quot;授权该程序或基于该程序的作品按ç…
§æ­¤è®¸å¯è¯ä½¿ç”¨çš„版权持有者。</p>
+<p>&ldquo;贡献者&rdquo; 的定义是 
&ldquo;授权该程序或基于该程序的作品按ç…
§æ­¤è®¸å¯è¯ä½¿ç”¨çš„版权持有者。&rdquo;</p>
 
-<p>对 &quot;程序&quot; 
的宽泛解读,正如建议,把专利许可授权提高到了一个不合理的广度。原å›
 æ˜¯ï¼Œå¯¹ä¸€ä¸ªç»™å®šçš„ GPLv3
+<p>对 &ldquo;程序&rdquo; 
的宽泛解读,正如建议,把专利许可授权提高到了一个不合理的广度。原å›
 æ˜¯ï¼Œå¯¹ä¸€ä¸ªç»™å®šçš„ GPLv3
 许可证接受方来说,授权专利许可证的贡献者的集合变成å…
¨ä¸–界的全部 GPLv3 作品的全部 GPLv3
 
授权方,而不只是针对特定许可证接受方的特定作品的授权方。</p>
 
 <p>不过,仔细ç 
”究专利许可证授权的措辞,并不能找到这些担
忧。为了实践专利许可证授权,GPLv3 许可证接受方必须拥有
-&quot;贡献者版本的内容&quot;。如果是这æ 
·ï¼Œé‚£ä¹ˆä»–就是一个内容接收方,按照 GPLv3 
许可证被授权。</p>
+&ldquo;贡献者版本的内容&rdquo;。如果是这æ 
·ï¼Œé‚£ä¹ˆä»–就是一个内容接收方,按照 GPLv3 
许可证被授权。</p>
 
 <p>因此,贡献者一直是专利许可授权资料的实际
版权授权方。从专利许可授权获益的用户最后是直接从这些贡献è€
…收到这些资料。如果不是这æ 
·ï¼Œé‚£ä¹ˆä¸“利许可授权就变得毫无意义,因
为授权活动要和贡献者的
-&quot;实际版本&quot; 绑定的。贡献者和第 11 
节中的专利许可证有直接或间接的发布关系。所以,第 11 
节第 3
+&ldquo;实际版本&rdquo; 绑定的。贡献者和第 11 
节中的专利许可证有直接或间接的发布关系。所以,第 11 
节第 3
 段并不要求你
授予专利许可证给那些不同时是版权接受方的人。(非贡献è€
…类的发布者仍然受制于专利许可证条款和第 11 节第 6 段中å…
·ä½“çš„
-&quot;自动扩展&quot; 条款。)</p>
+&ldquo;自动扩展&rdquo; 条款。)</p>
 
-<p>当人们考虑第 10 节第 3 段中的专利相关条款时,同æ 
·ä¹Ÿæ²¡æœ‰å¯¹ &quot;程序&quot; 
进行广义理解的基础。该条款说:</p>
+<p>当人们考虑第 10 节第 3 段中的专利相关条款时,同æ 
·ä¹Ÿæ²¡æœ‰å¯¹ &ldquo;程序&rdquo; 
进行广义理解的基础。该条款说:</p>
 
 <blockquote><p>ä½ 
不能声称由于制作、使用、销售、提供或引进该程序或å…
¶æŸéƒ¨åˆ†è€Œå¯¼è‡´æŸä¸ªä¸“利侵权,并由此发起诉讼(包
括交叉诉讼或反诉讼)。</p></blockquote>
 
@@ -92,7 +95,7 @@
 GPLv3 中引入专利报复条款非常谨慎,而且第 10 节第 3 
段里的条款是有意做得比一些知名许可证中的专利报复条款更局限,å
…¶ä¸­åŒ…括著名的
 Mozilla 公共许可证版本 1.1,针对å…
¶ä¸­çš„专利许可证中止条款而言。</p>
 
-<p>如果把 &quot;程序&quot; 的建议解释应用到第 10 节第 3
+<p>如果把 &ldquo;程序&rdquo; 的建议解释应用到第 10 节第 3
 段的条款上,那么å…
¶ç»“果就会和许可证前面对专利报复的陈述和政策大相径庭,这明显不是我们的意思。</p>
 
 <p>GPL 版本 3 的政策也是一样。第 10 
节的专利报复条款是为替换草案 2 的 7(b)(5) 条款而引入草案 
3 的。7(b)(5) 条款允许
@@ -108,10 +111,11 @@
 中把宽泛专利报复排除在 GPL 兼容性之外。</p>
 
 <p>我们通过用第 10 节替换 7(b)(5) 达到这一目的,因为å…
¶ä¸­æˆ‘们只保留了和第 2 类专利中止相关的内容。第 1 
类专利中止的内容因此在草案 3
-中变成 GPL 不兼容的 &quot;进一步限制&quot;,在实际公开的 
GPL v3 中也是如此。
+中变成 GPL 不兼容的 &ldquo;进一步限制&rdquo;,在实际公开的 
GPL v3 中也是如此。
 </p>
 
-<p><a href="/licenses/gpl-faq.html">返回问答</a></p>
+<p class="back"><a href="/licenses/gpl-faq.html">返回问答</a></p>
+</div>
 
 <div class="translators-notes">
 
@@ -121,7 +125,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
@@ -140,18 +144,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
@@ -165,12 +169,11 @@
      
      There is more detail about copyright years in the GNU Maintainers
      Information document, www.gnu.org/prep/maintain. -->
-<p>Copyright &copy; 2007, 2008, 2014 Free Software Foundation, Inc.</p>
+<p>Copyright &copy; 2007, 2021 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>
+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">
@@ -182,11 +185,12 @@
 <p class="unprintable"><!-- timestamp start -->
 最后更新:
 
-$Date: 2019/07/28 08:29:49 $
+$Date: 2021/12/21 01:30:16 $
 
 <!-- timestamp end -->
 </p>
 </div>
 </div>
+<!-- for class="inner", starts in the banner include -->
 </body>
 </html>

Index: licenses/po/gplv3-the-program.zh-cn-en.html
===================================================================
RCS file: /web/www/www/licenses/po/gplv3-the-program.zh-cn-en.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- licenses/po/gplv3-the-program.zh-cn-en.html 28 Jul 2019 08:29:49 -0000      
1.1
+++ licenses/po/gplv3-the-program.zh-cn-en.html 21 Dec 2021 01:30:16 -0000      
1.2
@@ -1,26 +1,29 @@
 <!--#include virtual="/server/header.html" -->
-<!-- Parent-Version: 1.77 -->
-<title>What does &quot;the Program&quot; mean in GPLv3?
+<!-- Parent-Version: 1.96 -->
+<!-- This page is derived from /server/standards/boilerplate.html -->
+<title>What Does &ldquo;The Program&rdquo; Mean in GPLv3?
 - GNU Project - Free Software Foundation</title>
 <!--#include virtual="/licenses/po/gplv3-the-program.translist" -->
 <!--#include virtual="/server/banner.html" -->
-<h2>What does &quot;the Program&quot; mean in GPLv3?</h2>
+<div class="article reduced-width">
+<h2>What Does &ldquo;The Program&rdquo; Mean in GPLv3?</h2>
+<div class="thin"></div>
 
 <h3>Summary</h3>
 
-<p>In version 3 of the GNU General Public License (GPLv3), the term &quot;the
-Program&quot; means one particular work that is licensed under GPLv3 and is
+<p>In version 3 of the GNU General Public License (GPLv3), the term &rdquo;the
+Program&rdquo; means one particular work that is licensed under GPLv3 and is
 received by a particular licensee from an upstream licensor or
 distributor.  The Program is the particular work of software that you
 received in a given instance of GPLv3 licensing, as you received it.</p>
 
-<p>&quot;The Program&quot; cannot mean &quot;all the works ever licensed
-under GPLv3&quot;; that interpretation makes no sense, because &quot;the
-Program&quot; is singular: those many different programs do not constitute
+<p>&ldquo;The Program&rdquo; cannot mean &ldquo;all the works ever licensed
+under GPLv3&rdquo;; that interpretation makes no sense, because &ldquo;the
+Program&rdquo; is singular: those many different programs do not constitute
 one program.</p>
 
 <p>In particular, this applies to the clause in section 10, paragraph 3
-of GPLv3 which states</p>
+of GPLv3 which states:</p>
 
 <blockquote><p>[Y]ou may not initiate litigation (including a cross-claim or
   counterclaim in a lawsuit) alleging that any patent claim is
@@ -45,9 +48,9 @@
 
 <h3>Further analysis</h3>
 
-<p>GPLv3 defines &quot;the Program&quot; as follows:</p>
+<p>GPLv3 defines &ldquo;the Program&rdquo; as follows:</p>
 
-<blockquote><p>&quot;The Program&quot; refers to any copyrightable work
+<blockquote><p>&ldquo;The Program&rdquo; refers to any copyrightable work
   licensed under this License.</p></blockquote>
 
 <p>Some have contended that this definition can be read to mean all
@@ -56,60 +59,60 @@
 readers have expressed particular concern about the consequences of
 such an interpretation for the new patent provisions of GPLv3,
 especially the patent termination condition found in the third
-paragraph 10 and the express patent license grant made by upstream
+paragraph of section 10 and the express patent license grant made by upstream
 contributors under the third paragraph of section 11.  This overbroad
-reading of &quot;the Program&quot; is incorrect, and contrary to our intent as
+reading of &ldquo;the Program&rdquo; is incorrect, and contrary to our intent 
as
 the drafters of GPLv3.</p>
 
-<p>The word &quot;any&quot; is susceptible to multiple, subtly different
-shades of meaning in English.  In some contexts, &quot;any&quot; means
-&quot;every&quot; or &quot;all&quot;; in others, including the definition
-of &quot;the Program&quot; in GPLv3, it suggests &quot;one particular
-instance of, selected from many possibilities&quot;.  This variability has
+<p>The word &ldquo;any&rdquo; is susceptible to multiple, subtly different
+shades of meaning in English.  In some contexts, &ldquo;any&rdquo; means
+&ldquo;every&rdquo; or &ldquo;all&rdquo;; in others, including the definition
+of &ldquo;the Program&rdquo; in GPLv3, it suggests &ldquo;one particular
+instance of, selected from many possibilities.&rdquo;  This variability has
 to be resolved by the context.  This context resolves it, but it requires
 some thought.</p>
 
-<p>We could have worded the definition of &quot;the Program&quot;
-differently, such as by using &quot;a particular&quot; instead of
-&quot;any&quot;, but that would not have eliminated the need for thought.
-The phrase &quot;a particular work licensed under this License&quot;,
-regarded in isolation, would not necessarily signify *the* particular work
-received by a particular &quot;you&quot; in a particular act of licensing
+<p>We could have worded the definition of &ldquo;the Program&rdquo;
+differently, such as by using &ldquo;a particular&rdquo; instead of
+&ldquo;any,&rdquo; but that would not have eliminated the need for thought.
+The phrase &ldquo;a particular work licensed under this License,&rdquo;
+regarded in isolation, would not necessarily signify <em>the</em> particular 
work
+received by a particular &ldquo;you&rdquo; in a particular act of licensing
 or distribution.  Our review of other free software licenses shows that
 they raise similar issues of interpretation, with words of general
 reference used in order to facilitate license reuse.</p>
 
 <p>Given that no choice is so clear that all other candidate meanings
-must be rejected, &quot;any&quot; has certain advantages.  It is a somewhat
+must be rejected, &ldquo;any&rdquo; has certain advantages.  It is a somewhat
 more informal and less legalistic usage than the possible
 alternatives, an appropriate register for the developers reading
-and applying the license.  Moreover, the usage of &quot;any&quot;, through
+and applying the license.  Moreover, the usage of &ldquo;any,&rdquo; through
 its suggestion of selection out of many qualifying possibilities,
 has the effect of emphasizing the reusability of GPLv3 for
 multiple works of software and in multiple licensing situations.
 The GNU GPL is intended to be used by many developers on their programs
 and that too needs to be clear.</p>
 
-<p>The same use of &quot;any&quot; that has given rise to interpretive
+<p>The same use of &ldquo;any&rdquo; that has given rise to interpretive
 concerns under GPLv3 exists in GPLv2, in its corresponding definition.
 Section 0 of GPLv2 states:</p>
 
 <blockquote><p>This License applies to any program or other work which
   contains a notice placed by the copyright holder saying it may be
   distributed under the terms of this General Public License. The
-  &quot;Program&quot;, below, refers to any such program or work, and a
-  &quot;work based on the Program&quot; means either the Program or any
+  &ldquo;Program,&rdquo; below, refers to any such program or work, and a
+  &ldquo;work based on the Program&rdquo; means either the Program or any
   derivative work under copyright law &hellip;</p></blockquote>
 
 <p>However, it has always been the understanding of the FSF and others in
-the GPL-using community that &quot;the Program&quot; in GPLv2 means the
+the GPL-using community that &ldquo;the Program&rdquo; in GPLv2 means the
 particular GPL-covered work that you receive, before you make any
-possible modifications to it.  The definition of &quot;the Program&quot; in
+possible modifications to it.  The definition of &ldquo;the Program&rdquo; in
 GPLv3 is intended to preserve this meaning.</p>
 
 <p>We can find no clause in GPLv3 in which applying the suggested broad
-interpretation of &quot;the Program&quot; (and the superset term
-&quot;covered work&quot;) would make sense or have any practical
+interpretation of &ldquo;the Program&rdquo; (and the superset term
+&ldquo;covered work&rdquo;) would make sense or have any practical
 significance, consistent with the wording of the clause and its drafting
 history.  The patent provisions of GPLv3 are a case in point.</p>
 
@@ -121,11 +124,11 @@
   modify and propagate the contents of its contributor
   version.</p></blockquote>
 
-<p>A &quot;contributor&quot; is defined as &quot;a copyright holder who
+<p>A &ldquo;contributor&rdquo; is defined as &ldquo;a copyright holder who
 authorizes use under this License of the Program or a work on which the
-Program is based.&quot;</p>
+Program is based.&rdquo;</p>
 
-<p>The broad reading of &quot;the Program&quot;, it has been suggested,
+<p>The broad reading of &ldquo;the Program,&rdquo; it has been suggested,
 gives rise to an unreasonably broad patent license grant.  The reasoning is
 that, for a given GPLv3 licensee, the set of contributors granting patent
 licenses becomes all GPLv3 licensors of all GPLv3-covered works in the
@@ -135,7 +138,7 @@
 <p>Close attention to the wording of the patent license grant, however,
 shows that these concerns are unfounded.  In order to exercise the
 permissions of the patent license grant, a GPLv3 licensee must have
-&quot;the contents of [the contributor's] contributor version&quot; in his
+&ldquo;the contents of [the contributor's] contributor version&rdquo; in his
 possession.  If he does, then he is necessarily a recipient of that
 material, licensed to him under GPLv3.</p>
 
@@ -144,16 +147,16 @@
 benefiting from the patent license grant has ultimately received the
 material covered by the grant from those contributors.  If it were
 otherwise, the patent license grant would be meaningless, because the
-exercise of its permissions is tied to the contributor's &quot;contributor
-version&quot;.  The contributors and the section 11 patent licensee stand
+exercise of its permissions is tied to the contributor's &ldquo;contributor
+version.&rdquo;  The contributors and the section 11 patent licensee stand
 in a direct or indirect distribution relationship. Therefore, section 11,
 paragraph 3 does not require you to grant a patent license to anyone who is
 not also your copyright licensee.  (Non-contributor redistributors remain
 subject to applicable implied patent license doctrine and to the special
-&quot;automatic extension&quot; provision of section 11, paragraph 6.)</p>
+&ldquo;automatic extension&rdquo; provision of section 11, paragraph 6.)</p>
 
-<p>There is similarly no basis for the broad reading of &quot;the
-Program&quot; when one considers the patent-related clause in the third
+<p>There is similarly no basis for the broad reading of &ldquo;the
+Program&rdquo; when one considers the patent-related clause in the third
 paragraph of section 10.  This clause provides:</p>
 
 <blockquote><p>[Y]ou may not initiate litigation (including a cross-claim
@@ -179,7 +182,7 @@
 licenses, notably the Mozilla Public License version 1.1, with respect
 to termination of patent licenses.</p>
 
-<p>If the suggested interpretation of &quot;the Program&quot; applied to the
+<p>If the suggested interpretation of &ldquo;the Program&rdquo; applied to the
 section 10, paragraph 3 clause, the result would be a radical
 departure from our consistent past statements and policies concerning
 patent retaliation, which we clearly did not intend.</p>
@@ -209,22 +212,23 @@
 retaliation was criticized because it could apply to software patent
 lawsuits in which the accused software was unrelated to the software
 that was the subject of the license.  Seeing that there were no widely
-used licenses with which this would provide compatibility, in draft 3
+used licenses with which this would provide compatibility, in Draft 3
 we dropped broad patent retaliation from the range of GPL
 compatibility.</p>
 
 <p>We did so by replacing 7(b)(5) with text in section 10, in which we
 kept only what corresponded to the second category.  The first
-category therefore reverted to being a GPL-incompatible &quot;further
-restriction&quot; in Draft 3, and likewise in GPL version 3 as actually
+category therefore reverted to being a GPL-incompatible &ldquo;further
+restriction&rdquo; in Draft 3, and likewise in GPL version 3 as actually
 published.
 </p>
 
-<p><a href="/licenses/gpl-faq.html">Return to the FAQ</a></p>
+<p class="back"><a href="/licenses/gpl-faq.html">Return to the FAQ</a></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
@@ -242,19 +246,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
@@ -269,21 +273,20 @@
      There is more detail about copyright years in the GNU Maintainers
      Information document, www.gnu.org/prep/maintain. -->
 
-<p>Copyright &copy; 2007, 2008, 2014 Free Software Foundation, Inc.</p>
+<p>Copyright &copy; 2007, 2021 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>
+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: 2019/07/28 08:29:49 $
+$Date: 2021/12/21 01:30:16 $
 <!-- timestamp end -->
 </p>
 </div>
-</div>
+</div><!-- for class="inner", starts in the banner include -->
 </body>
 </html>

Index: licenses/po/gplv3-the-program.zh-cn.po
===================================================================
RCS file: /web/www/www/licenses/po/gplv3-the-program.zh-cn.po,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -b -r1.7 -r1.8
--- licenses/po/gplv3-the-program.zh-cn.po      21 Dec 2021 01:11:41 -0000      
1.7
+++ licenses/po/gplv3-the-program.zh-cn.po      21 Dec 2021 01:30:16 -0000      
1.8
@@ -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: 2021-12-17 13:26+0000\n"
 
 #. type: Content of: <title>
 msgid ""

Index: proprietary/proprietary.zh-cn.html
===================================================================
RCS file: /web/www/www/proprietary/proprietary.zh-cn.html,v
retrieving revision 1.71
retrieving revision 1.72
diff -u -b -r1.71 -r1.72
--- proprietary/proprietary.zh-cn.html  26 Nov 2021 06:45:58 -0000      1.71
+++ proprietary/proprietary.zh-cn.html  21 Dec 2021 01:30:16 -0000      1.72
@@ -88,7 +88,7 @@
 <hr class="thin" />
 </div>
 
-<p>截至 2021 年 10 月,此目录的页面中列出了大约 550 
个恶意功能实例(有 620 
多份证据支持),但是肯定还有数千个我们不知道情况。</p>
+<p>截至 2021 年 12 月,此目录的页面中列出了大约 550 
个恶意功能实例(有 630 
多份证据支持),但是肯定还有数千个我们不知道情况。</p>
 
 <p>如果你想在我们有更新或修改时收到消息,请订阅 <a
 href="https://lists.gnu.org/mailman/listinfo/www-malware-commits";>邮件列表
@@ -171,58 +171,58 @@
 <h3 id="latest">最新添加</h3>
 
 <ul class="blurbs">
-  <li id="M202110250">
+  <li id="M202111201">
     
     <!--#set var="DATE" value='<small class="date-tag">
-2021-10</small>'
+2021-11</small>'
     -->
 <!--#echo encoding="none" var="DATE" -->
-<p>教育科技公司使用å…
¶ç›‘控力量操纵学生,把他们引向不同水平的知识、权力和声名之路。这篇文ç«
 è®¨è®ºè¯´ <a
-href="https://blogs.lse.ac.uk/medialse/2021/10/25/algorithmic-injustice-in-education-why-tech-companies-should-require-a-license-to-operate-in-childrens-education/";>这些å
…
¬å¸åº”该获得许可才能运营</a>。虽然这么做没什么害处,但是它说的不是问题的æ
 ¹æºã€‚学校中关于学生、教师或雇员的数据不得离开学æ 
¡ï¼Œè€Œä¸”必须保存在学æ 
¡çš„运行着自由软件的计算机之中。这样,æ 
¡åŒºå’Œ/或家长就能够控制数据的用法。</p>
+<p>NordicTrack 是一个销售锻练机的å…
¬å¸ï¼Œè¿™ç§æœºå™¨èƒ½å¤Ÿæ˜¾ç¤ºè§†é¢‘ <a
+href="https://arstechnica.com/information-technology/2021/11/locked-out-of-god-mode-runners-are-hacking-their-treadmills/";>限制人们观看的å†
…容。最近该å…
¬å¸ç¦ç”¨äº†ä¸€ä¸ªåŽŸæ¥å¥½ç”¨çš„功能</a>。他们通过自动升级实现此操作,å
…¶ä¸­å¯èƒ½åŒ…含有全局后门。</p>
   </li>
 
-  <li id="M202111090">
+  <li id="M202111200">
     
     <!--#set var="DATE" value='<small class="date-tag">
 2021-11</small>'
     -->
 <!--#echo encoding="none" var="DATE" -->
-<p>洛杉矶一个带超市的建筑物 <a
-href="https://www.latimes.com/business/story/2021-11-09/column-trader-joes-parking-app";>要求顾客åŠ
 
载一个应用来支付停车费</a>,并接受广泛的监控。顾客也可以选择在小店处输å
…¥è½¦ç‰Œã€‚这也是不公正的。</p>
+<p>几百名特斯拉车主 <a
+href="https://www.theguardian.com/technology/2021/nov/20/tesla-app-outage-elon-musk-apologises";>由于特斯拉的应用宕机而æ—
 æ³•è¿›å…¥è½¦å­</a>,其原因
是该应用需要访问特斯拉的服务器。</p>
   </li>
 
-  <li id="M202111040">
+  <li id="M202111110">
     
     <!--#set var="DATE" value='<small class="date-tag">
 2021-11</small>'
     -->
 <!--#echo encoding="none" var="DATE" -->
-<p>苹果公司限制用户维修自己设备和强加 DRM 
有了新的伎俩,就是在你更换屏幕时 <a
-href="https://www.ifixit.com/News/54829/apples-new-screen-repair-trap-could-change-the-repair-industry-forever";>完å
…¨ç¦ç”¨
-Face ID 功能</a>。</p>
+<p>谷歌的研究人员 <a
+href="https://www.vice.com/en/article/93bw8y/google-caught-hackers-using-a-mac-zero-day-against-hong-kong-users";>发现
+MacOS 的一个零日漏洞,破坏者
可以针对特定人群使用</a>,这些人主要是香港访问媒体直营店的人、争取民主的劳动è€
…和政治团体。</p>
+
+  <p><small>请注意,本文错误地将&ldquo;<a
+href="/philosophy/words-to-avoid.html#Hacker">黑客</a>&rdquo;一词当成骇客来用。</small></p>
   </li>
 
-  <li id="M202108180">
+  <li id="M202110250">
     
     <!--#set var="DATE" value='<small class="date-tag">
-2021-08</small>'
+2021-10</small>'
     -->
 <!--#echo encoding="none" var="DATE" -->
-<p>微软让 <a
-href="https://www.theverge.com/22630319/microsoft-windows-11-default-browser-changes";>替换
-Windows 默认应用</a> 越来越难,反而强压用户使用å…
¶ä¸“有程序。我们坚信用 自由的 GNU 这样的操作系统来替换 
Windows
-系统是最佳应对。我们也维护着一个 <a 
href="/distros/free-distros.html">完全自由的 GNU 发行版列表</a>。</p>
+<p>教育科技公司使用å…
¶ç›‘控力量操纵学生,把他们引向不同水平的知识、权力和声名之路。这篇文ç«
 è®¨è®ºè¯´ <a
+href="https://blogs.lse.ac.uk/medialse/2021/10/25/algorithmic-injustice-in-education-why-tech-companies-should-require-a-license-to-operate-in-childrens-education/";>这些å
…
¬å¸åº”该获得许可才能运营</a>。虽然这么做没什么害处,但是它说的不是问题的æ
 ¹æºã€‚学校中关于学生、教师或雇员的数据不得离开学æ 
¡ï¼Œè€Œä¸”必须保存在学æ 
¡çš„运行着自由软件的计算机之中。这样,æ 
¡åŒºå’Œ/或家长就能够控制数据的用法。</p>
   </li>
 
-  <li id="M201802280">
+  <li id="M202111090">
     
     <!--#set var="DATE" value='<small class="date-tag">
-2018-02</small>'
+2021-11</small>'
     -->
 <!--#echo encoding="none" var="DATE" -->
-<p>Spotify 应用通过音乐、心情、观念、活动和品位等 <a
-href="https://www.sec.gov/Archives/edgar/data/1639920/000119312518063434/d494294df1.htm";>收集数据来确定用户身份和了解用户</a>。该程序每天会记录è¶
…过
-1500 亿包含用户数据和个人信息的事件。</p>
+<p>洛杉矶一个带超市的建筑物 <a
+href="https://www.latimes.com/business/story/2021-11-09/column-trader-joes-parking-app";>要求顾客åŠ
 
载一个应用来支付停车费</a>,并接受广泛的监控。顾客也可以选择在小店处输å
…¥è½¦ç‰Œã€‚这也是不公正的。</p>
   </li>
 </ul>
 <p class="button right-align">
@@ -299,7 +299,7 @@
 <p class="unprintable"><!-- timestamp start -->
 最后更新:
 
-$Date: 2021/11/26 06:45:58 $
+$Date: 2021/12/21 01:30:16 $
 
 <!-- timestamp end -->
 </p>

Index: proprietary/po/proprietary.zh-cn-en.html
===================================================================
RCS file: /web/www/www/proprietary/po/proprietary.zh-cn-en.html,v
retrieving revision 1.72
retrieving revision 1.73
diff -u -b -r1.72 -r1.73
--- proprietary/po/proprietary.zh-cn-en.html    26 Nov 2021 06:45:58 -0000      
1.72
+++ proprietary/po/proprietary.zh-cn-en.html    21 Dec 2021 01:30:16 -0000      
1.73
@@ -96,8 +96,8 @@
 <hr class="thin" />
 </div>
 
-<p>As of November, 2021, the pages in this directory list around 550
-instances of malicious functionalities (with more than 620 references to
+<p>As of December, 2021, the pages in this directory list around 550
+instances of malicious functionalities (with more than 630 references to
 back them up), but there are surely thousands more we don't know about.</p>
 
 <p>If you want to be notified when we add new items or make other changes,
@@ -188,6 +188,40 @@
 <h3 id="latest">Latest additions</h3>
 
 <ul class="blurbs">
+  <li id="M202111201">
+    <!--#set var="DATE" value='<small class="date-tag">2021-11</small>'
+    --><!--#echo encoding="none" var="DATE" -->
+    <p>NordicTrack, a company that sells
+    exercise machines with ability to show videos <a
+    
href="https://arstechnica.com/information-technology/2021/11/locked-out-of-god-mode-runners-are-hacking-their-treadmills/";>limits
+    what people can watch, and recently disabled a feature</a> that was
+    originally functional. This happened through automatic update and
+    probably involved a universal back door.</p>
+  </li>
+
+  <li id="M202111200">
+    <!--#set var="DATE" value='<small class="date-tag">2021-11</small>'
+    --><!--#echo encoding="none" var="DATE" -->
+    <p>Hundreds of Tesla drivers <a
+    
href="https://www.theguardian.com/technology/2021/nov/20/tesla-app-outage-elon-musk-apologises";>were
+    locked out of their cars as a result of Tesla's app suffering from an
+    outage</a>, which happened because the app is tethered to company's
+    servers.</p>
+  </li>
+
+  <li id="M202111110">
+    <!--#set var="DATE" value='<small class="date-tag">2021-11</small>'
+    --><!--#echo encoding="none" var="DATE" -->
+    <p>Some researchers at Google <a 
href="https://www.vice.com/en/article/93bw8y/google-caught-hackers-using-a-mac-zero-day-against-hong-kong-users";>found
+  a zero-day vulnerability on MacOS,
+  which crackers used to target people visiting the websites</a> of
+  a media outlet and a pro-democracy labor and political group in Hong
+  Kong.</p>
+
+  <p><small>Please note that the article wrongly refers
+  to crackers as &ldquo;<a 
href="/philosophy/words-to-avoid.html#Hacker">hackers</a>&rdquo;.</small></p>
+  </li>
+
   <li id="M202110250">
     <!--#set var="DATE" value='<small class="date-tag">2021-10</small>'
     --><!--#echo encoding="none" var="DATE" -->
@@ -213,39 +247,6 @@
     option of entering their license plate numbers in a kiosk. That is
     an injustice, too.</p>
   </li>
-
-  <li id="M202111040">
-    <!--#set var="DATE" value='<small class="date-tag">2021-11</small>'
-    --><!--#echo encoding="none" var="DATE" -->
-    <p>Apple's new tactic to restrict users from
-    repairing their own device and impose DRM on people is to <a
-    
href="https://www.ifixit.com/News/54829/apples-new-screen-repair-trap-could-change-the-repair-industry-forever";>completely
-    disable its Face ID functionality</a> when you replace its screen.</p>
-  </li>
-
-  <li id="M202108180">
-    <!--#set var="DATE" value='<small class="date-tag">2021-08</small>'
-    --><!--#echo encoding="none" var="DATE" -->
-    <p>Microsoft is making it harder and harder to <a
-    
href="https://www.theverge.com/22630319/microsoft-windows-11-default-browser-changes";>replace
-    default apps in its Windows</a> operating system and is pressuring
-    users to use its proprietary programs instead. We believe the
-    best approach to this would be replacing Windows with a free
-    (as in freedom) operating system like GNU. We also maintain a <a
-    href="/distros/free-distros.html">list of fully free distributions
-    of GNU</a>.</p>
-  </li>
-
-  <li id="M201802280">
-    <!--#set var="DATE" value='<small class="date-tag">2018-02</small>'
-    --><!--#echo encoding="none" var="DATE" -->
-    <p>Spotify app <a
-    
href="https://www.sec.gov/Archives/edgar/data/1639920/000119312518063434/d494294df1.htm";>harvests
-    users' data to personally identify and know people</a> through music,
-    their mood, mindset, activities, and tastes. There are over 150
-    billion events logged daily on the program which contains users'
-    data and personal information.</p>
-  </li>
 </ul>
 <p class="button right-align">
 <a href="/proprietary/all.html">More items&hellip;</a></p>
@@ -308,7 +309,7 @@
 
 <p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2021/11/26 06:45:58 $
+$Date: 2021/12/21 01:30:16 $
 <!-- timestamp end -->
 </p>
 </div>

Index: proprietary/po/proprietary.zh-cn.po
===================================================================
RCS file: /web/www/www/proprietary/po/proprietary.zh-cn.po,v
retrieving revision 1.290
retrieving revision 1.291
diff -u -b -r1.290 -r1.291
--- proprietary/po/proprietary.zh-cn.po 21 Dec 2021 01:10:17 -0000      1.290
+++ proprietary/po/proprietary.zh-cn.po 21 Dec 2021 01:30:16 -0000      1.291
@@ -15,7 +15,6 @@
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"X-Outdated-Since: 2021-12-19 07:58+0000\n"
 "X-Generator: Poedit 2.3\n"
 
 #. type: Content of: <title>

Index: proprietary/po/zh-cn.po
===================================================================
RCS file: /web/www/www/proprietary/po/zh-cn.po,v
retrieving revision 1.251
retrieving revision 1.252
diff -u -b -r1.251 -r1.252
--- proprietary/po/zh-cn.po     19 Dec 2021 09:08:33 -0000      1.251
+++ proprietary/po/zh-cn.po     21 Dec 2021 01:30:16 -0000      1.252
@@ -421,6 +421,10 @@
 "functional. This happened through automatic update and probably involved a "
 "universal back door."
 msgstr ""
+"NordicTrack 是一个销售锻练机的å…
¬å¸ï¼Œè¿™ç§æœºå™¨èƒ½å¤Ÿæ˜¾ç¤ºè§†é¢‘ <a href=\"https://";
+"arstechnica.com/information-technology/2021/11/locked-out-of-god-mode-"
+"runners-are-hacking-their-treadmills/\">限制人们观看的内
容。最近该公司禁用了"
+"一个原来好用的功能</a>。他们通过自动升级实现此操作,å…
¶ä¸­å¯èƒ½åŒ…含有全局后门。"
 
 #. type: Content of: <div><ul><li><p>
 msgid ""
@@ -429,6 +433,9 @@
 "out of their cars as a result of Tesla's app suffering from an outage</a>, "
 "which happened because the app is tethered to company's servers."
 msgstr ""
+"几百名特斯拉车主 <a 
href=\"https://www.theguardian.com/technology/2021/";
+"nov/20/tesla-app-outage-elon-musk-apologises\">由于特斯拉的应用宕机而æ—
 æ³•è¿›å…¥"
+"车子</a>,其原因是该应用需要访问特斯拉的服务器。"
 
 #. type: Content of: <div><ul><li><p>
 msgid ""
@@ -438,6 +445,10 @@
 "visiting the websites</a> of a media outlet and a pro-democracy labor and "
 "political group in Hong Kong."
 msgstr ""
+"谷歌的研究人员 <a 
href=\"https://www.vice.com/en/article/93bw8y/google-";
+"caught-hackers-using-a-mac-zero-day-against-hong-kong-users\">发现 MacOS 
的一"
+"个零日漏洞,破坏者
可以针对特定人群使用</a>,这些人主要是香港访问媒体直营店的"
+"人、争取民主的劳动者和政治团体。"
 
 #. type: Content of: <div><ul><li><p>
 #, fuzzy



reply via email to

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