www planetfeeds.pt-br.html philosophy/po/applyi...

[GNUN]

CVSROOT:        /web/www
Module name:    www
Changes by:     GNUN <gnun>     18/12/31 08:31:00

Modified files:
        .              : planetfeeds.pt-br.html 
        philosophy/po  : applying-free-sw-criteria.translist 
        po             : planetfeeds.pt-br.po 
Added files:
        philosophy     : applying-free-sw-criteria.zh-cn.html 
        philosophy/po  : applying-free-sw-criteria.zh-cn-en.html 

Log message:
        Automatic update by GNUnited Nations.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/planetfeeds.pt-br.html?cvsroot=www&r1=1.496&r2=1.497
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/applying-free-sw-criteria.zh-cn.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/applying-free-sw-criteria.translist?cvsroot=www&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/applying-free-sw-criteria.zh-cn-en.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/po/planetfeeds.pt-br.po?cvsroot=www&r1=1.204&r2=1.205

Patches:
Index: planetfeeds.pt-br.html
===================================================================
RCS file: /web/www/www/planetfeeds.pt-br.html,v
retrieving revision 1.496
retrieving revision 1.497
diff -u -b -r1.496 -r1.497
--- planetfeeds.pt-br.html      31 Dec 2018 05:59:02 -0000      1.496
+++ planetfeeds.pt-br.html      31 Dec 2018 13:30:57 -0000      1.497
@@ -6,35 +6,35 @@
 value="<a 
href='http://www.fsf.org/blogs/community/a-message-from-richard-m-stallman'>" 
-->
 <!--#echo
 encoding="none" var="link" -->
-A message from Richard M. Stallman<!--#echo encoding="none"
+Uma mensagem do Richard M. Stallman<!--#echo encoding="none"
 var="a_close" -->
 <!-- TRANSLATORS: 
 http://www.fsf.org/blogs/community/a-message-from-richard-m-stallman -->
-: The donation from the Pineapple Fund arrived in the form of Bitcoin and
-had gone down to around $860,000 by the time we could convert it all to
-dollars. Ar...
+: A doação do Pineapple Fund chegou na forma de Bitcoin e caiu para cerca de
+US$ 860.000 no momento em que pudemos converter tudo para dólares. Cerca da
+metade...
 </p>
 <p>
 <!--#set var="link"
 value="<a href='http://savannah.gnu.org/forum/forum.php?forum_id=9339'>" -->
 <!--#echo
 encoding="none" var="link" -->
-gzip-1.10 released [stable]<!--#echo encoding="none"
+gzip-1.10 lançado [estável]<!--#echo encoding="none"
 var="a_close" -->
 <!-- TRANSLATORS: 
 http://savannah.gnu.org/forum/forum.php?forum_id=9339 -->
-: This is to announce gzip-1.10, a stable release. There have been 19
-commits by 2 people in the 51 weeks since 1.9, not to mention the 559
-gnulib-related changes...
+:  Isso é para anunciar o gzip-1.10, uma versão estável. Houve 19 commits
+por 2 pessoas nas 51 semanas desde 1.9, sem contar com as 559 alterações
+relacionadas com...
 </p>
 <p>
 <!--#set var="link"
 value="<a href='http://savannah.gnu.org/forum/forum.php?forum_id=9338'>" -->
 <!--#echo
 encoding="none" var="link" -->
-Gnuastro 0.8 released<!--#echo encoding="none"
+Gnuastro 0.8 lançado<!--#echo encoding="none"
 var="a_close" -->
 <!-- TRANSLATORS: 
 http://savannah.gnu.org/forum/forum.php?forum_id=9338 -->
-: The 8th release of GNU Astronomy Utilities (Gnuastro) is now available for
-download. Please see the announcement for details.</p>
+: O 8º lançamento do GNU Astronomy Utilities (Gnuastro) já está disponível
+para download. Por favor, veja o anúncio para detalhes.</p>

Index: philosophy/po/applying-free-sw-criteria.translist
===================================================================
RCS file: /web/www/www/philosophy/po/applying-free-sw-criteria.translist,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- philosophy/po/applying-free-sw-criteria.translist   22 May 2016 18:28:55 
-0000      1.4
+++ philosophy/po/applying-free-sw-criteria.translist   31 Dec 2018 13:31:00 
-0000      1.5
@@ -6,6 +6,7 @@
 <span dir="ltr"><a lang="fr" hreflang="fr" 
href="/philosophy/applying-free-sw-criteria.fr.html">français</a>&nbsp;[fr]</span>
 &nbsp;
 <span dir="ltr"><a lang="it" hreflang="it" 
href="/philosophy/applying-free-sw-criteria.it.html">italiano</a>&nbsp;[it]</span>
 &nbsp;
 <span dir="ltr"><a lang="ru" hreflang="ru" 
href="/philosophy/applying-free-sw-criteria.ru.html">русский</a>&nbsp;[ru]</span>
 &nbsp;
+<span dir="ltr"><a lang="zh-cn" hreflang="zh-cn" 
href="/philosophy/applying-free-sw-criteria.zh-cn.html">简体中文</a>&nbsp;[zh-cn]</span>
 &nbsp;
 </p>
 </div>' -->
 <link rel="alternate" type="text/html" 
href="/philosophy/applying-free-sw-criteria.html" hreflang="x-default" />
@@ -13,4 +14,5 @@
 <link rel="alternate" type="text/html" lang="fr" hreflang="fr" 
href="/philosophy/applying-free-sw-criteria.fr.html" title="français" />
 <link rel="alternate" type="text/html" lang="it" hreflang="it" 
href="/philosophy/applying-free-sw-criteria.it.html" title="italiano" />
 <link rel="alternate" type="text/html" lang="ru" hreflang="ru" 
href="/philosophy/applying-free-sw-criteria.ru.html" title="русский" />
+<link rel="alternate" type="text/html" lang="zh-cn" hreflang="zh-cn" 
href="/philosophy/applying-free-sw-criteria.zh-cn.html" title="简体中文" />
 <!-- end translist file -->

Index: po/planetfeeds.pt-br.po
===================================================================
RCS file: /web/www/www/po/planetfeeds.pt-br.po,v
retrieving revision 1.204
retrieving revision 1.205
diff -u -b -r1.204 -r1.205
--- po/planetfeeds.pt-br.po     31 Dec 2018 13:07:32 -0000      1.204
+++ po/planetfeeds.pt-br.po     31 Dec 2018 13:31:00 -0000      1.205
@@ -15,7 +15,6 @@
 "Content-Transfer-Encoding: 8bit\n"
 "Plural-Forms: nplurals=2; plural=(n > 1);\n"
 "X-Generator: Virtaal 1.0.0-beta1\n"
-"X-Outdated-Since: 2018-12-31 05:57+0000\n"
 
 #. type: Content of: <p>
 msgid "A message from Richard M. Stallman"

Index: philosophy/applying-free-sw-criteria.zh-cn.html
===================================================================
RCS file: philosophy/applying-free-sw-criteria.zh-cn.html
diff -N philosophy/applying-free-sw-criteria.zh-cn.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ philosophy/applying-free-sw-criteria.zh-cn.html     31 Dec 2018 13:31:00 
-0000      1.1
@@ -0,0 +1,221 @@
+<!--#set var="ENGLISH_PAGE" 
value="/philosophy/applying-free-sw-criteria.en.html" -->
+
+<!--#include virtual="/server/header.zh-cn.html" -->
+<!-- Parent-Version: 1.79 -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>应用自由软件判断准则 - GNU 工程 - 
自由软件基金会</title>
+
+<!--#include virtual="/philosophy/po/applying-free-sw-criteria.translist" -->
+<!--#include virtual="/server/banner.zh-cn.html" -->
+<h2>应用自由软件判断准则</h2>
+
+<p>理查德·斯托曼 著</p>
+
+<p>四项基本自由为判断<a
+href="/philosophy/free-sw.html">某一特定代ç 
ç‰‡æ–­æ˜¯å¦ä¸ºè‡ªç”±çš„</a>（即尊重用户自由）提供了准则。我们应当如何将它们应用于判断一个软件åŒ
…
、一套操作系统、一台计算机、或是一个网页是否适合被推荐使用呢？</p>
+
+<p>一个程序是否是自由的首å…
ˆå½±å“åˆ°çš„是我们对于自己的私人行为的决定：为了捍卫我们自己的自由，我们需要拒绝那些将会剥夺我们自由的程序。然而，这也会影响到我们应当对别人怎æ
 ·è¯´å’Œæ€Žæ ·åšã€‚</p>
+
+<p>非自由程序是不å…
¬æ­£çš„。发布一个非自由程序、向他人推荐非自由程序、或是更为普遍地将它们引å
…
¥è¯¾ç¨‹è€Œå¼•å¯¼äººä»¬ä½¿ç”¨éžè‡ªç”±è½¯ä»¶ï¼Œä»¥ä¸Šè¿™äº›è¡Œä¸ºæ„å‘³ç€å¼•å¯¼äººä»¬æ”¾å¼ƒè‡ªå·±çš„自由。可以肯定的是，引导人们使用非自由软件并不等同于在他们的计算机上安è£
…非自由软件，但我们不应该将人们引入歧途。</p>
+
+<p>在更深层次上，我们不能提出一个非自由程序作为一个解决方案，å›
 为这将会承认其合法性。非自由软件是一种问题； <a
+href="/philosophy/compromise.html">将å…
¶ä»¥ä¸€ç§è§£å†³æ–¹æ¡ˆçš„方式呈现否认了这一问题的存在</a>。</p>
+
+<p>本文阐述了我们应当如何应用自由软件的基本准则来判断不同种类的事物，并且决定是否应该推荐它们。</p>
+
+<h3>软件包</h3>
+
+<p>ä¸€ä¸ªè½¯ä»¶åŒ…è‹¥è¦æˆä¸ºè‡ªç”±çš„ï¼Œå…¶ä¸­æ‰€æœ‰ä»£ç å¿…
é¡»éƒ½æ˜¯è‡ªç”±çš„ã€‚ä½†ä¸ä»…é™äºŽä»£ç ã€‚ç”±äºŽæ–‡æ¡£æ–‡ä»¶åŒ…
含手册、自述（README）、更新日志等，这些都是软件包的必
要的技术组成部分，<a
+href="/philosophy/free-doc.html">它们必须也是自由的</a>。</p>
+
+<p>一个软件包通常与很多其他软件包一起使用，并且与å…
¶ä¸­çš„一些进行交互。与非自由软件进行的何种交互才是伦理上可接受的呢？</p>
+
+<p>我们着手开发 GNU 
的目的是带来一款自由的操作系统，由于在 1983 年还没有这æ 
·çš„自由操作系统。当我们于 20 世纪 80 年代开发出最早的 GNU
+组件时，其中每个组件都依赖于非自由软件是不可避å…
çš„。例如，没有任何一个 C 程序可以离开非自由的 C 
编译器而运行，直到 GCC
+可以正常工作，并且它们也不能离开 Unix libc 而运行，直到 
glibc
+可以正常工作。每个组件都只能运行在非自由操作系统上，å›
 为当时所有的操作系统都是非自由的。</p>
+
+<p>每当我们发布一款可以运行在某些非自由操作系统上的组件时，用户将å
…¶ç§»æ¤åˆ°å…
¶ä»–非自由操作系统上。从伦理上讲，这些移植并不比我们曾经用于开发这些组件的限定平台代ç
 æ›´åï¼Œå› 此我们整合了他们的修补程序。</p>
+
+<p>当 Linux å†…æ ¸äºŽ 1992 年变为自由之时，它填补了 GNU 
操作系统的最后一块空缺（Linux 最初于 1991
+年以一种非自由许可证发布）。GNU 和 Linux 
的组合成为了一种完全自由的操作系统&mdash;<a
+href="/gnu/linux-and-gnu.html">GNU/Linux</a>。</p>
+
+<p>此时，我们可以选择移除对非自由平台的支持，但是我们决定不这æ
 ·åšã€‚非自由操作系统是不å…
¬çš„，但用户运行非自由操作系统并不是我们的过错。支持该非自由操作系统上的自由软件并不会进一步恶化这种不å
…¬ã€‚并且这将是实用的，不仅
对于那些非自由操作系统用户，也对于吸引更多人为开发该自由软件做贡献。</p>
+
+<p>然而，在自由程序上运行非自由程序是一个完å…
¨ä¸åŒçš„é—®é¢˜ï¼Œå› 
为这是在诱导用户在自由之路上倒退。在某些情况下我们完å…
¨ç¦æ­¢è¿™æ ·åšï¼šä¾‹å¦‚ <a
+href="https://gcc.gnu.org/ml/gcc/2014-01/msg00247.html";>GCC
+禁止任何非自由插件</a>。当一个程序å…
è®¸éžè‡ªç”±æ‰©å±•çš„时候，它至少不应该引导用户使用它们。例如，我们更倾向于选择
 LibreOffice 而非
+OpenOffice，由于后者提示用户使用非自由扩展，而 LibreOffice 
则避开了它们。我们开发<a
+href="http://directory.fsf.org/wiki/IceCat";>冰猫（IceCat）</a>起初也是为了避å
…å‘用户推广由火狐（FireFox）建议使用的非自由扩展。</p>
+
+<p>事实上，如果冰猫解释如何在 MacOS 
上运行冰猫，这将不会引导用户去运行
+MacOS。但如果它介绍了一些非自由扩展，它将会鼓励冰猫用户安è£
…è¿™äº›éžè‡ªç”±æ‰©å±•ã€‚å› 此，冰猫软件包及å…
¶æ‰‹å†Œå’Œç½‘站不应该介绍这些东西。</p>
+
+<p>有时一个自由软件和一个非自由软件协同工作，但å…
¶ä¸­ä»»ä½•ä¸€æ–¹éƒ½ä¸æ˜¯åŸºäºŽå¦ä¸€æ–¹çš„。我们针对这种情
况的规则是，如果该非自由软件非常有名，我们应当告知人们如何使用我们的自由软件与之工作；但如果该专有软件鲜为人知，我们不应该暗示å
…¶å­˜åœ¨ã€‚有时我们会在该非自由软件存在的情
况下提供互操作支持，但避免告知用户这么做的可能性。</p>
+
+<p>我们拒绝任何仅
可用于某一非自由操作系统的&ldquo;增强组件&rdquo;。它们会鼓励人们使用该非自由操作系统而非
 GNU，如同自摆乌龙。</p>
+
+<h3>GNU/Linux 发行版</h3>
+
+<p>随着 Linux å†…æ ¸äºŽ 1992 年自由化，人们开始开发 GNU/Linux 
发行版（&ldquo;distros&rdquo;）。但只有少数发行版是
+<a href="/distros">完全由自由软件构成的</a>。</p>
+
+<p>适用于软件包
的规则也适用于发行版：一个符合伦理的发行版必须仅包
含自由软件并且只将用户向自由软件的方向引导。但是，对于一个发行版而言，&ldquo;åŒ
…含&rdquo;一个特定的软件包是什么意思呢？</p>
+
+<p>某些发行版从二进制包安装作为å…
¶å‘行版一部分的软件；而其他发行版从上游源代ç 
æž„建每个软件，并且从字面意义上讲，它们所<em>包
含</em>的只是需要下载并构建的列表。对于自由的问题，发行版怎æ
 ·å®‰è£…一个给定的软件包并不重要；如果它将某个软件包
作为可选项提供，或者它的网站这æ 
·åšï¼Œæˆ‘们称该发行版&ldquo;包含&rdquo;该软件包。</p>
+
+<p>自由操作系统的用户拥有对它的控制权，于是他们可以安è£
…他们想要安装
的任何东西。自由发行版提供了用户可用于安装
他们自己的程序以及他们对于自由软件的修改版本的通用工å…
·ï¼›ä»–们也可以安装
非自由软件。在这些发行版中提供这些通用工å…
·å¹¶ä¸æ˜¯ä¼¦ç†ç‘•ç–µï¼Œç”±äºŽè¯¥å‘行版的开发者对于用户基于å…
¶è‡ªèº«çš„主动权获取并安装什么软件并不负有责任。</p>
+
+<p>然而，当开发者
引导用户走向非自由软件的时候，他们对于用户安装
非自由软件就应当负有责任了&mdash;例如，将非自由软件置于流行发行版的软件åŒ
…列表中，或者从它们的服务器进行分发，或者将å…
¶å‘ˆçŽ°ä¸ºä¸€ç§è§£å†³æ–¹æ¡ˆè€Œéžä¸€ç§é—®é¢˜ã€‚这正是为何大多数
+GNU/Linux 发行版具有伦理瑕疵的问题之所在。</p>
+
+<p>自行安装软件包的用户通常å…
·æœ‰ä¸€å®šçš„判断能力：如果我们告诉他们&ldquo;Baby 包
å«éžè‡ªç”±ä»£ç ï¼Œè€Œ Gbaby
+是自由的&rdquo;，我们可以预见他们能够留心记住哪个是哪个。但发行版是推荐给那些不了解这些细节的普通用户的。他们将会想&ldquo;我应该使用他们所说的哪个呢？我想它应该是
+Baby&rdquo;。</p>
+
+<p>å› æ­¤ï¼Œè¦æƒ³å‘å…
¬ä¼—推荐一款发行版，我们坚持要求它们的名字不能与我们所拒绝的某个发行版相似，唯有如此，我们å
…³äºŽä»…ä»…æŽ¨èè‡ªç”±å‘è¡Œç‰ˆçš„ä¿¡æ¯æ‰èƒ½è¢«å¯é åœ°ä¼ è¾¾ã€‚</p>
+
+<p>å‘è¡Œç‰ˆå’Œè½¯ä»¶åŒ…ä¹‹é—´çš„å¦ä¸€ä¸ªåŒºåˆ«åœ¨äºŽå‘å…¶ä¸­æ·»åŠ 
éžè‡ªç”±ä»£ç çš„å¯èƒ½æ€§ã€‚ç¨‹åºå¼€å‘è€…ä¼šä»”ç»†æ£€æŸ¥ä»–ä»¬å‘å…
¶ä¸­æ·»åŠ 的代ç 
ã€‚如果他们决定使该程序成为自由的，他们不太会向å…
¶ä¸­æ·»åŠ éžè‡ªç”±ä»£ç ã€‚ä¸è¿‡ä¹Ÿæœ‰ä¾‹å¤–ï¼ŒåŒ…æ‹¬
+Linux å†…æ ¸ä¸­æ·»åŠ &ldquo;二进制 blobs&rdquo;这æ 
·æ¶åŠ£çš„æ¡ˆä¾‹ï¼Œä½†å®ƒä»¬ä¸ŽçŽ°å­˜çš„è‡ªç”±è½¯ä»¶ç›¸æ¯”åªå 
一小部分。</p>
+
+<p>与之相反，一个 GNU/Linux
+发行版通常包含数千个软件包，并且其开发者
å¯èƒ½æ¯å¹´éƒ½ä¼šå‘å…¶ä¸­æ·»åŠ æ•°ç™¾ä¸ªæ–°çš„è½¯ä»¶åŒ…
ã€‚å¦‚æžœæœªèƒ½å°½åŠ›é¿å…é‚£äº›åŒ…å«æŸç§éžè‡ªç”±è½¯ä»¶çš„è½¯ä»¶åŒ…ï¼Œå‡ 
乎肯定会有一些非自由软件混入å…
¶ä¸­ã€‚由于自由发行版的数量很少，作为列出那些发行版的条件，我们要求每位自由发行版的开发è€
…é€šè¿‡ç§»é™¤ä»»ä½•éžè‡ªç”±ä»£ç æˆ–æ¶æ„ä»£ç 
æ¥æ‰¿è¯ºä¿æŒè¯¥å‘行版成为自由软件。参见
+<a
+href="http://gnu.org/distros/free-system-distribution-guidelines.html";>GNU
+自由操作系统发行版指导意</a>。</p>
+
+<p>我们不要求自由软件包的开发者也做出这æ 
·çš„承诺，这是不现实的，幸运地是，这也不是必
需的。得到超过 30000
+个自由软件的开发者的承诺也许能够避免少数问题，但å…
¶ä»£ä»·æ˜¯æžå¤§å¢žåŠ 
自由软件基金会（FSF）员工的工作量；此外，这些开发者
中的大部分与 GNU
+è®¡åˆ’å¹¶æ— å…³ç³»ï¼Œä»–ä»¬ä¹Ÿä¸æ„¿æ„å‘æˆ‘ä»¬åšå‡ºä»»ä½•æ‰¿è¯ºã€‚å› 
此我们只需在发现问题的时候应对这些使自由软件变为非自由软件的少数案例。</p>
+
+<h3>外设</h3>
+
+<p>è®¡ç®—æœºå¤–è®¾è¦æ±‚è®¡ç®—æœºä¸­çš„è½¯ä»¶è¢«æ“ä½œç³»ç»ŸåŠ è½½åˆ°å…
¶ä¸­ä»¥ä¾¿ä½¿å…¶å·¥ä½œ&mdash;è¿™äº›è½¯ä»¶å¯ä»¥æ˜¯é©±åŠ¨ç¨‹åºæˆ–å›ºä»¶ã€‚å› 
此，如果一件外设可以在一台未安装
任何非自由软件的计算机上使用&mdash;如果该外设的驱动程序以及任何需要由操作系统åŠ
 载到å…
¶ä¸­çš„固件都是自由的，那么它是可接受并使用以及推荐的。</p>
+
+<p>验证这一点是简单的：将该外设连接到一台运行完å…
¨è‡ªç”±çš„ GNU/Linux
+发行版的计算机上并且观察它是否正常工作。但是大多数用户需要在购买外设<em>之前</em>获知这一点，å›
 此我们在 <a
+href="https://www.h-node.org/";>h-node.org</a>
+列出了很多外设的信息，这是一个完å…
¨è‡ªç”±çš„操作系统的硬件数据库。</p>
+
+<h3>计算机</h3>
+
+<p>一台计算机在不同层次上包
含不同的软件。我们应当基于什么准则来判断一台计算机是否&rdquo;尊重您的自由&ldquo;呢？</p>
+
+<p>显而易见的是：操作系统和其中的任何软件都必
须是自由的。在 20 世纪 90 å¹´ä»£ï¼Œå¯åŠ¨åŠ 
载软件（当时是&ldquo;基本输入/输出系统&rdquo;，即
+BIOS）成为可替换的，并且由于它运行在中央处理器（CPU）上，它与操作系统所存在的是同一类的问题。å›
 此，诸如固件或驱动程序，不论安装
åœ¨æ“ä½œç³»ç»Ÿä¸­ï¼Œæˆ–æ˜¯éšæ“ä½œç³»ç»Ÿä¸€èµ·å®‰è£…ï¼Œæˆ–æ˜¯å¯åŠ¨åŠ 
载程序都必须是自由的。</p>
+
+<p>如果一台计算机拥有某些要求在操作系统中安装
的非自由驱动程序或固件的硬件功能，我们可能仍然能够推荐它。如果它在没有那些功能的æƒ
…
况下仍然可用，并且我们认为大部分人不会为了使该功能可用而被引导安è£
…
非自由软件，那么我们仍然能够推荐它们。否则我们就不能。这将是一种主观判断。</p>
+
+<p>一台计算机可能在较低的层次上带有预装
的可修改固件和微ç 
ã€‚它也可能在真正只读的存储器中拥有代ç 
ã€‚我们决定在现今我们所使用的认证准则中忽略这些程序，这是由于如若不然就没有任何计算机可以满足，并且å›
 ä¸ºé€šå¸¸ä¸ä¼šè¢«æ›´æ”¹çš„å›ºä»¶åœ¨ä¼¦ç†ä¸Šä¸Žç”µè·¯ç›¸åŒã€‚å› 
此我们的认证准则仅仅
覆盖那些运行在计算机的主处理器上且储存在非真正只读存储器中的代ç
 ã€‚当在å…
¶ä»–层次上运行自由软件成为可能，我们也会要求这些层次上的软件是自由的。</p>
+
+<p>由于认证一款产品是对它的积极推广，我们要求它们的贩卖è€
…以支持我们作为回报，这可以通过谈论<a
+href="/philosophy/free-software-even-more-important.html">自由软件</a>而非<a
+href="/philosophy/open-source-misses-the-point.html">开源软件</a>以及将 
GNU 和 Linux
+的结合体称为 <a 
href="/gnu/linux-and-gnu.html">&rdquo;GNU/Linux&ldquo;</a>
+来做到。我们没有义务积极支持那些不认可我们的工作或是不支持我们运动的项目。</p>
+
+<p>参见 <a
+href="https://www.fsf.org/resources/hw/endorsement/criteria";>我们的认证准则</a>。</p>
+
+<h3>网页</h3>
+
+<p>现在的很多网页都包含复杂的 JavaScript
+ç¨‹åºå¹¶ä¸”éœ€è¦å®ƒä»¬æ‰èƒ½å·¥ä½œã€‚è¿™æ˜¯ä¸€ç§æœ‰å®³çš„å®žè·µï¼Œå› 
为它阻碍用户对他们自己计算的控制。更坏的是，这些程序中的大部分是非自由的，这是一种不å
…¬ã€‚JavaScript
+ä»£ç å¸¸å¸¸çª¥æŽ¢ç”¨æˆ·ã€‚<a 
href="philosophy/javascript-trap.html">JavaScript</a>
+已经变成了一种对用户自由的威胁。</p>
+
+<p>为了解决这一问题，我们开发了 <a 
href="/software/librejs">LibreJS</a>，这是一种用于阻止非普通非自由的
+JavaScript ä»£ç çš„ç«ç‹æµè§ˆå™¨æ‰©å±•ï¼ˆæ²¡æœ‰å¿…
要阻止简单的脚本，如果它们只是实现一些次要的用户界面特性）。我们请求网站将它们的
 JavaScript
+ç¨‹åºè‡ªç”±åŒ–å¹¶ä¸”æ ‡è®°å…¶è®¸å¯è¯ä»¥ä¾¿ LibreJS 识别。</p>
+
+<p>与此同时，链接至一个包含非自由 JavaScript 
程序的网页是否符合伦理呢？如果我们坚决不做任何妥协，我们将只能链接至自由的
 JavaScript
+ä»£ç ã€‚ç„¶è€Œï¼Œå¾ˆå¤šç½‘é¡µå³ä½¿ä¸è¿è¡Œå®ƒä»¬çš„ JavaScript 代ç 
ä¹Ÿèƒ½å·¥ä½œã€‚此外，除了我们的链接，您会经常在å…
¶å®ƒç½‘站遇到非自由的 JavaScript
+ä»£ç ï¼›ä¸ºäº†é¿å…è¿™äº›æƒ…å†µï¼Œæ‚¨å¿…é¡»ä½¿ç”¨ LibreJS 或禁用 
JavaScriptã€‚å› 
此，我们决定做出让步并且链接那些不运行非自由 JavaScript
+程序也能工作的网页，同时鼓励用户在普遍意义上保护自己不受来自非自由
 JavaScript 程序的威胁。</p>
+
+<p>然而，如果某个网页不运行非自由 JavaScript 
程序就不能实现其功能，链接到它将会不可避å…
åœ°è¦æ±‚人们运行该非自由 JavaScript
+ä»£ç ã€‚åŽŸåˆ™ä¸Šï¼Œæˆ‘ä»¬ä¸ä¼šé“¾æŽ¥è¿™äº›ç½‘é¡µã€‚</p>
+
+<h3>结论</h3>
+
+<p>将<em>&rdquo;软件应当是自由的&ldquo;</em>这一基本理念应用到不同场合要求不同的实践策略。随着新æƒ
…况的出现，GNU 计划和 FSF
+将会适é…
æˆ‘们的自由准则，不论在实践中还是理论上，都将计算机用户引向自由。通过ä»
…ä»…
推荐尊重用户自由的程序、发行版和硬件产品，并且宣示您的立场，您可以为自由软件运动提供它所急需的支持。</p>
+
+<div class="translators-notes">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
+ </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 的一般性 &amp; 
问题发送到<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 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
+     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; 2015, 2016 Richard Stallman</p>
+
+<p>本页面使用<a rel="license"
+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.nongnu.org/projects/blug/";>BLUG</a><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/12/31 13:31:00 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>

Index: philosophy/po/applying-free-sw-criteria.zh-cn-en.html
===================================================================
RCS file: philosophy/po/applying-free-sw-criteria.zh-cn-en.html
diff -N philosophy/po/applying-free-sw-criteria.zh-cn-en.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ philosophy/po/applying-free-sw-criteria.zh-cn-en.html       31 Dec 2018 
13:31:00 -0000      1.1
@@ -0,0 +1,336 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.79 -->
+<title>Applying the Free Software Criteria
+- GNU Project - Free Software Foundation</title>
+ <!--#include virtual="/philosophy/po/applying-free-sw-criteria.translist" -->
+<!--#include virtual="/server/banner.html" -->
+
+<h2>Applying the Free Software Criteria</h2>
+
+<p>by Richard Stallman</p>
+
+<p>The four essential freedoms provide the criteria for <a
+href="/philosophy/free-sw.html">whether a particular piece of code is
+free/libre</a> (i.e., respects its users' freedom).  How should we
+apply them to judge whether a software package, an operating system, a
+computer, or a web page is fit to recommend?</p>
+
+<p>Whether a program is free affects first of all our decisions about our
+private activities: to maintain our freedom, we need to reject the
+programs that would take it away.  However, it also affects what we
+should say to others and do with others.</p>
+
+<p>A nonfree program is an injustice.  To distribute a nonfree program,
+to recommend a nonfree program to other people, or more generally
+steer them into a course that leads to using nonfree software, means
+leading them to give up their freedom.  To be sure, leading people to
+use nonfree software is not the same as installing nonfree software in
+their computers, but we should not lead people in the wrong direction.</p>
+
+<p>At a deeper level, we must not present a nonfree program as a solution
+because that would grant it legitimacy.  Nonfree software is a
+problem; <a href="/philosophy/compromise.html"> to present it as a
+solution denies the existence of the problem</a>.</p>
+
+<p>This article explains how we apply the basic free software criteria to
+judging various kinds of things, so we can decide whether to recommend
+them or not.</p>
+
+<h3>Software packages</h3>
+
+<p>For a software package to be free, all the code in it must be free.
+But not only the code.  Since documentation files including manuals,
+README, change log, and so on are essential technical parts of a
+software package, <a href="/philosophy/free-doc.html">they must be
+free as well</a>.</p>
+
+<p>A software package is typically used alongside many other packages,
+and interacts with some of them.  Which kinds of interaction with
+nonfree programs are ethically acceptable?</p>
+
+<p>We developed GNU so that there would be a free operating system,
+because in 1983 none existed.  As we developed the initial components
+of GNU, in the 1980s, it was inevitable that each component depended
+on nonfree software.  For instance, no C program could run without a
+nonfree C compiler until GCC was working, and none could run without
+Unix libc until glibc was working.  Each component could run only
+on nonfree systems, because all systems were nonfree.</p>
+
+<p>After we released a component that could run on some nonfree systems,
+users ported it to other nonfree systems; those ports were no worse,
+ethically, than the platform-specific code we needed to develop these
+components, so we incorporated their patches.</p>
+
+<p>When the kernel, Linux, was freed in 1992, it filled the last gap in
+the GNU system.  (Initially, in 1991, Linux had been distributed under
+a nonfree license.)  The combination of GNU and Linux made a complete
+free operating system&mdash;<a
+href="/gnu/linux-and-gnu.html">GNU/Linux</a>.</p>
+
+<p>At that point, we could have deleted the support for nonfree
+platforms, but we decided not to.  A nonfree system is an injustice,
+but it's not our fault a user runs one.  Supporting a free program on
+that system does not compound the injustice.  And it's useful, not
+only for users of those systems, but also for attracting more people
+to contribute to developing the free program.</p>
+
+<p>However, a nonfree program that runs on top of a free program is a
+completely different issue, because it leads users to take a step away
+from freedom.  In some cases we disallow this: for instance, <a
+href="https://gcc.gnu.org/ml/gcc/2014-01/msg00247.html";>GCC prohibits
+nonfree plug-ins</a>.  When a program permits nonfree add-ons, it
+should at least not steer people towards using them.  For instance, we
+choose LibreOffice over OpenOffice because OpenOffice suggests use of
+nonfree add-ons, while LibreOffice shuns them.  We developed <a
+href="http://directory.fsf.org/wiki/IceCat";>IceCat</a> initially to
+avoid proposing the nonfree add-ons suggested by Firefox.</p>
+
+<p>In practice, if the IceCat package explains how to run IceCat on
+MacOS, that will not lead people to run MacOS.  But if it talked about
+some nonfree add-on, that would encourage IceCat users to install the
+add-on.  Therefore, the IceCat package, including manuals and web
+site, shouldn't talk about such things.</p>
+
+<p>Sometimes a free program and a nonfree program interoperate but
+neither is based on the other.  Our rule for such cases is that if the
+nonfree program is very well known, we should tell people how to use
+our free program with it; but if the proprietary program is obscure,
+we should not hint that it exists.  Sometimes we support
+interoperation with the nonfree program if that is installed, but
+avoid telling users about the possibility of doing so.</p>
+
+<p>We reject &ldquo;enhancements&rdquo; that would work only on a nonfree 
system.
+Those would encourage people to use the nonfree system instead of GNU,
+scoring an own-goal.</p>
+
+<h3>GNU/Linux distros</h3>
+
+<p>After the liberation of Linux in 1992, people began developing
+GNU/Linux distributions (&ldquo;distros&rdquo;).  Only a few distros
+are <a href="/distros">entirely free software</a>.</p>
+
+<p>The rules for a software package apply to a distro too: an ethical
+distro must contain only free software and steer users only towards
+free software.  But what does it mean for a distro to
+&ldquo;contain&rdquo; a particular software package?</p>
+
+<p>Some distros install programs from binary packages that are part of
+the distro; others build each program from upstream source, and
+literally <em>contain</em> only the recipes to download and build it.
+For issues of freedom, how a distro installs a given package is not
+significant; if it presents that package as an option, or its web site
+does, we say it &ldquo;contains&rdquo; that package.</p>
+
+<p>The users of a free system have control over it, so they can install
+whatever they wish.  Free distros provide general facilities with
+which users can install their own programs and their modified versions
+of free programs; they can also install nonfree programs.  Providing
+these general facilities is not an ethical flaw in the distro, because
+the distro's developers are not responsible for what users get and
+install on their own initiative.</p>
+
+<p>The developers become responsible for installation of nonfree software
+when they steer the users toward a nonfree program&mdash;for
+instance, by putting it in the distro's list of packages, or
+distributing it from their server, or presenting it as a solution
+rather than a problem.  This is the point where most GNU/Linux
+distros have an ethical flaw.</p>
+
+<p>People who install software packages on their own have a certain level
+of sophistication: if we tell them &ldquo;Baby contains nonfree code,
+but Gbaby is free,&rdquo; we can expect them to take care to remember
+which is which.  But distros are recommended to ordinary users who
+would forget such details.  They would think, &ldquo;What name did
+they say I should use?  I think it was Baby.&rdquo;</p>
+
+<p>Therefore, to recommend a distro to the general public, we insist that
+its name not be similar to a distro we reject, so our message
+recommending only the free distro can be reliably transmitted.</p>
+
+<p>Another difference between a distro and a software package is how
+likely it is for nonfree code to be added.  The developers of a
+program carefully check the code they add.  If they have decided to
+make the program free, they are unlikely to add nonfree code.
+There have been exceptions, including the very harmful case of the
+&ldquo;binary blobs&rdquo; that were added to Linux, but they are a
+small fraction of the free programs that exist.</p>
+
+<p>By contrast, a GNU/Linux distro typically contains thousands of
+packages, and the distro's developers may add hundreds of packages a
+year.  Without a careful effort to avoid packages that contain some
+nonfree software, some will surely creep in.  Since the free distros
+are few in number, we ask the developers of each free distro to make a
+commitment to keep the distro free software by removing any nonfree
+code or malware, as a condition for listing that distro.  See the <a
+href="/distros/free-system-distribution-guidelines.html">GNU free
+system distribution guidelines</a>.</p>
+
+<p>We don't ask for such promises for free software packages: it's not
+feasible, and fortunately not necessary.  To get promises from the
+developers of 30,000 free programs to keep them free would avoid a few
+problems, at the cost of much work for the FSF staff; in addition,
+most of those developers have no relationship with the GNU Project and
+might have no interest in making us any promises.  So we deal with
+the rare cases that change from free to nonfree, when we find out
+about them.</p>
+
+<h3>Peripherals</h3>
+
+<p>A computer peripheral needs software in the computer&mdash;perhaps a
+driver, perhaps firmware to be loaded by the system into the
+peripheral to make it run.  Thus, a peripheral is acceptable to use
+and recommend if it can be used from a computer that has no nonfree
+software installed&mdash;the peripheral's driver, and any firmware that
+the system needs to load into it, are free.</p>
+
+<p>It is simple to check this: connect the peripheral to a computer
+running a totally free GNU/Linux distro and see if it works.  But most
+users would like to know <em>before</em> they buy the peripheral, so
+we list information about many peripherals
+in <a href="https://www.h-node.org/";>h-node.org</a>, a hardware
+database for fully free operating systems.</p>
+
+<h3>Computers</h3>
+
+<p>A computer contains software at various levels.  On what criterion
+should we certify that a computer &ldquo;Respects Your Freedom&rdquo;?</p>
+
+<p>Obviously the operating system and everything above it must be free.
+In the 90s, the startup software (BIOS, then) became replaceable, and
+since it runs on the CPU, it is the same sort of issue as the
+operating system.  Thus, programs such as firmware and drivers that
+are installed in or with the system or the startup software must be free.</p>
+
+<p>If a computer has hardware features that require nonfree drivers or
+firmware installed with the system, we may be able to endorse it.  If
+it is usable without those features, and if we think most people won't
+be led to install the nonfree software to make them function, then we
+can endorse it.  Otherwise, we can't.  This will be a judgment call.</p>
+
+<p>A computer can have modifiable preinstalled firmware and microcode at
+lower levels.  It can also have code in true read-only memory.  We
+decided to ignore these programs in our certification criteria today,
+because otherwise no computer could comply, and because firmware that
+is not normally changed is ethically equivalent to circuits.  So our
+certification criteria cover only the code that runs on the computer's
+main processor and is not in true read-only memory.  When and as free
+software becomes possible for other levels of processing, we will
+require free software at those levels too.</p>
+
+<p>Since certifying a product is active promotion of it, we insist
+that the seller support us in return, by talking
+about <a href="/philosophy/free-software-even-more-important.html">free
+software</a> rather
+than <a href="/philosophy/open-source-misses-the-point.html">open
+source</a> and referring to the combination of GNU and Linux
+as <a href="/gnu/linux-and-gnu.html">&ldquo;GNU/Linux&rdquo;</a>.  We
+have no obligation to actively promote projects that won't recognize
+our work and support our movement.</p>
+
+<p>See <a href="https://www.fsf.org/resources/hw/endorsement/criteria";>our
+certification criteria</a>.</p>
+
+<h3>Web pages</h3>
+
+<p>Nowadays many web pages contain complex JavaScript programs and won't
+work without them.  This is a harmful practice since it hampers users'
+control over their computing.  Furthermore, most of these programs are
+nonfree, an injustice.  Often the JavaScript code spies on the user.
+<a href="/philosophy/javascript-trap.html">JavaScript has morphed into
+a attack on users' freedom.</a></p>
+
+<p>To address this problem, we have developed <a
+href="/software/librejs">LibreJS</a>, an add-on for Firefox that
+blocks nontrivial nonfree JavaScript code.  (There is no need to block
+the simple scripts that implement minor user interface hacks.)  We ask
+sites to please free their JavaScript programs and mark their licenses
+for LibreJS to recognize.</p>
+
+<p>Meanwhile, is it ethical to link to a web page that contains a nonfree
+JavaScript program?  If we were totally unyielding, we would link only
+to free JavaScript code.  However, many pages do work even when their
+JavaScript code is not run.  Also, you will most often encounter nonfree
+JavaScript in other ways besides following our links; to avoid it,
+you must use LibreJS or disable JavaScript.  So we have decided to go
+ahead and link to pages that work without nonfree JavaScript, while urging
+users to protect themselves from nonfree JavaScript in general.</p>
+
+<p>However, if a page can't do its job without running the nonfree
+JavaScript code, linking to it undeniably asks people to run that
+nonfree code.  On principle, we do not link to such pages.</p>
+
+<h3>Conclusion</h3>
+
+<p>Applying the basic idea that <em>software should be free</em> to
+different situations leads to different practical policies.  As new
+situations arise, the GNU Project and the Free Software Foundation
+will adapt our freedom criteria so as to lead computer users towards
+freedom, in practice and in principle.  By recommending only
+freedom-respecting programs, distros, and hardware products, and
+stating your policy, you can give much-needed support to the free
+software movement.</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 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
+     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; 2015, 2016 Richard Stallman</p>
+
+<p>This page is licensed under a <a rel="license"
+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: 2018/12/31 13:31:00 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>