www-commits
[Top][All Lists]
Advanced

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

www distros/common-distros.zh-tw.html distros/p...


From: GNUN
Subject: www distros/common-distros.zh-tw.html distros/p...
Date: Sun, 4 Jun 2017 11:58:19 -0400 (EDT)

CVSROOT:        /web/www
Module name:    www
Changes by:     GNUN <gnun>     17/06/04 11:58:19

Modified files:
        distros        : common-distros.zh-tw.html 
        distros/po     : common-distros.zh-tw.po 
        philosophy     : free-sw.zh-tw.html fs-motives.nl.html 
        philosophy/po  : free-sw.zh-tw-en.html free-sw.zh-tw.po 
                         fs-motives.nl.po 

Log message:
        Automatic update by GNUnited Nations.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/distros/common-distros.zh-tw.html?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/distros/po/common-distros.zh-tw.po?cvsroot=www&r1=1.3&r2=1.4
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/free-sw.zh-tw.html?cvsroot=www&r1=1.16&r2=1.17
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/fs-motives.nl.html?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/free-sw.zh-tw-en.html?cvsroot=www&r1=1.2&r2=1.3
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/free-sw.zh-tw.po?cvsroot=www&r1=1.39&r2=1.40
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/fs-motives.nl.po?cvsroot=www&r1=1.3&r2=1.4

Patches:
Index: distros/common-distros.zh-tw.html
===================================================================
RCS file: /web/www/www/distros/common-distros.zh-tw.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- distros/common-distros.zh-tw.html   30 May 2017 08:01:17 -0000      1.1
+++ distros/common-distros.zh-tw.html   4 Jun 2017 15:58:18 -0000       1.2
@@ -211,7 +211,7 @@
         href="/server/standards/README.translations.html">Translations
         README</a>. -->
 
我們努力盡所能提供貼切、品質良善的翻譯。然而,我們無法十å
…¨åç¾Žï¼Œé‚„請將你的意見評述與一般建議寄給 <a
-href="mailto:address@hidden";>&lt;address@hidden&gt;</a></p>
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a></p>
 <p>請參照 <a href="/server/standards/README.translations.html">翻譯讀我 
README</a>
 來瞭解協調和提交我們的網頁翻譯相關事宜。</p>
 </div>
@@ -249,7 +249,7 @@
 <p class="unprintable"><!-- timestamp start -->
 更新時間︰
 
-$Date: 2017/05/30 08:01:17 $
+$Date: 2017/06/04 15:58:18 $
 
 <!-- timestamp end -->
 </p>

Index: distros/po/common-distros.zh-tw.po
===================================================================
RCS file: /web/www/www/distros/po/common-distros.zh-tw.po,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- distros/po/common-distros.zh-tw.po  4 Jun 2017 15:31:41 -0000       1.3
+++ distros/po/common-distros.zh-tw.po  4 Jun 2017 15:58:18 -0000       1.4
@@ -565,8 +565,8 @@
 "translations of this article."
 msgstr ""
 
"我們努力盡所能提供貼切、品質良善的翻譯。然而,我們無法十å
…¨åç¾Žï¼Œé‚„請將你的意"
-"見評述與一般建議寄給 <a href=\"mailto:address@hidden";>&lt;"
-"address@hidden&gt;</a></p>\n"
+"見評述與一般建議寄給 <a href=\"mailto:address@hidden";>&lt;web-"
+"address@hidden&gt;</a></p>\n"
 "<p>請參照 <a 
href=\"/server/standards/README.translations.html\">翻譯讀我 "
 "README</a> 來瞭解協調和提交我們的網頁翻譯相關事宜。"
 

Index: philosophy/free-sw.zh-tw.html
===================================================================
RCS file: /web/www/www/philosophy/free-sw.zh-tw.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- philosophy/free-sw.zh-tw.html       20 Aug 2016 14:58:39 -0000      1.16
+++ philosophy/free-sw.zh-tw.html       4 Jun 2017 15:58:19 -0000       1.17
@@ -1,340 +1,451 @@
-<!--#set var="PO_FILE"
- value='<a href="/philosophy/po/free-sw.zh-tw.po">
- https://www.gnu.org/philosophy/po/free-sw.zh-tw.po</a>'
- --><!--#set var="ORIGINAL_FILE" value="/philosophy/free-sw.html"
- --><!--#set var="DIFF_FILE" value="/philosophy/po/free-sw.zh-tw-diff.html"
- --><!--#set var="OUTDATED_SINCE" value="2013-05-27" -->
+<!--#set var="ENGLISH_PAGE" value="/philosophy/free-sw.en.html" -->
 
 <!--#include virtual="/server/header.zh-tw.html" -->
+<!-- Parent-Version: 1.79 -->
 
 <!-- This file is automatically generated by GNUnited Nations! -->
-<!--#set var="DISABLE_TOP_ADDENDUM" value="yes" -->
- <!--#set var="ENGLISH_PAGE" value="/philosophy/free-sw.en.html" -->
+<title>自由軟體是什麼? - GNU 專案 - 自由軟體基金會</title>
 
-<title>甚麼是自由軟體? - GNU 項目 - 自由軟體基金會</title>
-
-<!-- Fixed by hand on August 20, 2014:
-     - disable top addendum,
-     - partially update footer,
-     - remove links to obsolete news. 
--->
-<meta http-equiv="Keywords" content="GNU, FSF, 自由軟體基金會, Linux, 
Emacs, GCC, Unix, 自由軟體, 操作系統, GNU 核心, GNU Hurd" />
-<meta http-equiv="Description" content="從1983年,不斷開發Unix風æ 
¼çš„自由操作系統 GNU,使電è…
¦ç”¨æˆ¶å¯ä»¥è‡ªç”±åœ°åˆ†äº«åŠæ”¹è‰¯é€™äº›è»Ÿé«”。" />
+<meta http-equiv="Keywords" content="GNU, FSF, Free Software Foundation, 
自由軟體基金會, Linux, Emacs, GCC, Unix, Free
+Software, 自由軟體, Operating System, 作業系統, GNU Kernel, GNU æ 
¸å¿ƒ, GNU 內核, HURD,
+GNU Hurd, Hurd" />
+<meta http-equiv="Description" 
content="起源於1983年,持續不斷開發自由的 Unix 風作業系統 
GNU,使電腦使用者能擁有分享這些軟體並改善的自由。" />
 
 <!--#include virtual="/philosophy/po/free-sw.translist" -->
 <!--#include virtual="/server/banner.zh-tw.html" -->
-<!--#include virtual="/server/outdated.zh-tw.html" -->
-<h2>甚麼是自由軟體?</h2>
+<h2>自由軟體是什麼?</h2>
+
+<blockquote class="note" id="fsf-licensing"><p style="font-size: 80%">
+對於自由軟體授權還有這裡尚未解答的疑惑嗎?請參考我們å
…¶ä»–çš„ <a
+href="http://www.fsf.org/licensing";>授權條款資源</a>,若有需要請不吝寫信至
 <a
+href="mailto:address@hidden";>address@hidden</a> 向 FSF 合規ç 
”究室詢問相關事宜。</p>
+</blockquote>
 
-<h3>自由軟體的定義</h3>
+<h3>自由軟體定義</h3>
 
 <blockquote>
 <p>
-  自由軟體(Free
-Software)的定義界定了一個特定的軟體能否乎合自由軟體的準則。為了解決一些細節的問題,我們不時會重新審視這些準則。可以從以下的<a
-href="#History">更新記錄</a>了解這個定義的演變。
+自由軟體(free
+software)的定義界定了一特定軟體是否能合乎自由軟體的準則。為了更æ¸
…楚說明或解決一些細微問題,我們會不時修訂這項
定義。請見下方的<a
+href="#History">歷史記錄區段</a>瞭解自由軟體定義的更動處。
 </p>
 </blockquote>
 
 <p>
-  「自由軟體」指尊重使用者
及社群自由的軟體。簡單來說<b>使用者
可以自由運行、複製、發佈、學習、修改及改良軟體。他們有操控軟體用途的權利</b>。
+「自由軟體」代表軟體尊重使用者
的自由,以及社群的自由。粗略地講,它代表<b>使用者
擁有執行、複製、散布、ç 
”究、更動和改善該軟體的自由</b>;所以,「自由軟體」所講述的是自由,無關乎價æ
 ¼ã€‚自由軟體這個概念就跟「自由言論
+(free speech)」一樣,而不是「免費啤酒 (free beer)」<a
+href="#trans1">[按1]</a>。西方有時也會借用法文或西班牙文的「libre
+software」來描述自由的「free」,藉此表明這裡講的並非是å…
é™¤è²»ç”¨çš„軟體。
 </p>
 
 <p>
-  如果使用者
不能控制軟體,就會反被軟體操控,而軟體開發者
就可以透過軟體操控使用者
。這些不自由(nonfree)或專有(proprietary)的軟體就成為不å…
¬ç¾©å‹¢åŠ›çš„利器。
+因
為人人都應得自由,所以我們為所有人爭取這些自由。有了這些自由,使用è€
…(包
括個人與集體)才能控制這個軟體、以及這個軟體的所作所為。一旦使用è€
…無法控制軟體,我們便將之稱為「非自由
+(nonfree)」軟體或「專有 
(proprietary)」軟體。非自由軟體控制住使用者
,而該軟體則接受開發者
的控制;如此一來這個程式軟體便成了<a
+href="/philosophy/free-software-even-more-important.html">不正當權力的施行工å
…·</a>。
 </p>
 
-<p>
-  所以「自由軟體」是自由、權利的問題,而不是價æ 
¼çš„問題。自由軟體的性質就跟「自由言論」一樣,而不是「å
…è²»å•¤é…’」<a
-href="#trans1">[按1]</a>。
-</p>
+<h4> 四大自由</h4>
 
 <p>
-  如果軟體使用者有以下四項
自由,那軟體就是自由軟體︰
+如果軟體使用者能擁有以下四項
自由,則該程式軟體就是自由軟體︰
 </p>
 
 <ul>
-  <li>  以任何目的運行該程式 (自由0)<a 
href="#trans2">[按2]</a>。</li>
-  <li>  取得軟體的代碼(source 
code)並學習程式的運作、修改為你想要的樣子 (自由1)
+  <li>依照你
的想法執行該程式的自由,無論任何目的(自由之零)<a 
href="#trans2">[按2]</a>。</li>
+  <li>研究該程式如何運作的自由,並依照你
的想法修改它以符合你
的運算所需(自由之壹)。能取得程式的源始碼 (source code) 
是這項自由的先決條件。
   </li>
-  <li>  隨意發佈軟體副本以幫助別人 (自由2)。
+  <li>再次散布程式副本的自由,如此你就能幫助你
的親朋好友街坊鄰居(自由之貳)。
   </li>
-  <li>  隨意分發你修改的版本(包括代碼)給別人 (自由 
3)。此舉可使你的版本惠及社群。
+  <li>將你
修改過後的版本散布給他人的自由(自由之參)。如此你
就有機會讓你的改善惠及社群整體。能存取源始碼是這項
自由的先決條件。
   </li>
 </ul>
 
 <p>
-  如果使用者有以上的自由,那程式就是自由軟體。你
有自由用任何方式發佈副本給任<a
-href="#exportcontrol">何地方的所有人</a>,不論是原封不動還是修改過的版本、不論是å
…
è²»é‚„是收費。自由的意思是不用給任何人同意、或付費取得權限。
+若一軟體能妥善給予使用者
上述的這些自由,那麼它就是自由軟體;否則的話,就是非自由軟體。儘管我們能æ
 ¹æ“šé€™äº›éžè‡ªç”±è»Ÿé«”的散布方式排列出它們與自由之間的遠
近;但我們認為那全都不合道德,無論有多接近自由。</p>
+
+<p>在任何情
境之下,無論我們打算利用的任何程式碼為何,或是引導他人利用的任何程式碼為何,這些自由都å¿
…é 
ˆä¸€ä½µé©ç”¨ã€‚舉例而言,假想甲程式會自動啟動乙程式處理某些事。如果我們打算散布這樣的甲程式,那麼代表使用è€
…也將需要乙程式,因此我們必é 
ˆåˆ¤æ–·æ˜¯å¦ç”²ç¨‹å¼ã€ä¹™ç¨‹å¼çš†æ˜¯è‡ªç”±è»Ÿé«”。然而,如果我們打算修改甲程式讓它不會用到乙程式,那麼只有甲程式需要是自由軟體,而乙程式對這樣的做法就不會產生影響。</p>
+
+<p>
+「自由軟體」不代表「非商業行為」。自由軟體必é 
ˆèƒ½ä½œç‚ºå•†æ¥­ä½¿ç”¨ã€å•†æ¥­é–‹ç™¼ã€èˆ‡å•†æ¥­æ•£å¸ƒç­‰ã€‚如今商業開發的自由軟體已經相當常見,有這樣的自由商業軟體至關重要。ä½
 å¯èƒ½éœ€è¦ä»˜è²»å–得某自由軟體的副本,但你也可能å…
è²»å–得;無論你是怎樣取得軟體副本的,你必
然享有複製與改動該軟體的自由,甚至也能<a
+href="/philosophy/selling.html">銷售該軟體的副本</a>。
 </p>
 
+<p>本頁其餘內容在說明如何妥善滿足特定自由的要點。</p>
+
+<h4>依照你的想法執行該程式的自由</h4>
+
 <p>
-  你也有私下修改及使用自由軟體的自由,而且不必
提及這件事。如果你發表這些修改,也不必
以任何方式通知任何人。
+執行程式的自由,意指任何人或組織皆可在任何電è…
¦ç³»çµ±ä¸Šä½¿ç”¨è©²ç¨‹å¼ã€ç”¨æ–¼ä»»ä½•ä½œæ¥­èˆ‡ç”¨é€”,而不必
知會開發者或任何其他特定單位。這項
自由,訴求的重點是<em>使用者</em>
+的自身目的,而無關<em>開發者</em>
+所設想的目的;你身為使用者
擁有依個人目的執行程式的自由。如果你把軟體散布給å…
¶ä»–人,那麼她便擁有依其個人用途執行軟體的自由,你
無法將你所設想的用途強加在她身上。
 </p>
 
 <p>
-  運行程式的自由指任何人物、組織可以在任何電è…
¦ç³»çµ±é‹è¡Œè©²ç¨‹å¼ä½œä»»ä½•ç”¨é€”,而不必知會第三者
。這是<em>使用者</em>的事情,跟<em>開發者
</em>無關。以使用者身份你可以個人目的使用程式。如果你
把軟體分發給å…
¶ä»–人,那他們也可以為各自的用途使用軟體,而且你
不能強制他們的用途。
+依照你
的想法執行該程式的自由,代表無法禁止或阻止誰執行它。這和程式本身所擁有的功能無關,無論å
…¶æŠ€è¡“上在任何給定環境下能否運作、或無論å…
¶æ˜¯å¦èƒ½ç”¨æ–¼ç‰¹å®šçš„電腦作業。</p>
+
+<h4>研究源始碼並修改的自由</h4>
+
+<p>
+為了讓自由之壹和參(修改軟體之自由,以及發布修改後版本的自由)有意義,ä½
 å¿…須能夠
取得程式的源始碼。所以,源始碼的可得性是自由軟體的必
要條件。混淆後無法解讀的「源始碼」並非真正的源始碼,å›
 è€Œä¸èƒ½ç®—是源始碼。
 </p>
 
 <p>
-  發佈軟體的自由必需包括程式的二進制或可執行形式<a
-href="#trans3">[按3]</a>、和代碼、原版及修改後的版本。(以可執行形式發佈軟體十分重要,可以使自由的操作系統更方便安裝)有些例外是軟體所採用的編程言語沒有可執行形式的功能,但ä½
 ä¸€å®šè¦æœ‰è‡ªç”±ç™¼ä½ˆé‚£ç¨®å½¢å¼ã€‚
+自由之壹包括改用你
修改後版本來替換原來版本的自由。如果一產品中的程式可執行某人修改後的版本,卻拒絕運行ä½
 çš„版本 — 這種做法稱之為「tivo 行為
+(tivoization)」或「閉鎖 (lockdown)」、或像(其施行者
講的邪魔外道用語)是「安全開機 (secure boot)」—
+自由之壹便成空中樓閣,而非真實不虛。這樣的二進位檔並非自由軟體,即使軟體的編譯用源始碼是自由的亦是如此。
 </p>
 
 <p>
-  為了自由 
1、3(修改軟體及發佈修改版本的自由)變得有意義,你必
需取得程式的代碼,所以取得代碼是自由軟體的必
要條件。打亂了的「代碼」並不能視為代碼。
+修改程式的重要方式之一是合併現成的自由副常式及模組。如果程式的授權條款不å
…è¨±ä½ åˆä½µé©ç•¶æŽˆæ¬Šçš„既有模組,例如:要求你必須是你所加
入的任意代碼之著作權人 —
+那麼這樣的授權條款限制性過大,稱不上自由的授權。
 </p>
 
 <p>
-  自由1包括使用你
的修改版本代替原來版本的自由。如果某產品預設運行å…
¶ä¿®æ”¹ç‰ˆæœ¬è€Œæ‹’絕運行你的版本 — a practice known as
-“tivoization” or “lockdown”, or (in its practitioners' perverse 
terminology)
-as “secure boot” — 
自由1就變成空想的理論而不是實際的自由。這是不足夠
的,就算該程式的源碼是自由的,但å…
¶å¯åŸ·è¡Œæª”也不是自由軟體。
+對軟體的修改是否屬於改善是種主觀的問題。如果你
修改程式的權利受到實質限制,無論之前的修改有多大幅
度的改善,也都算不上是自由軟體。
+</p>
+
+<h4>依照你的想法再次散布的自由:基本需求</h4>
+
+<p>散布的自由意味著你
能自由地再次散布軟體副本,不管有無任何修改,無論有無對散布行為收取費用,更不å¿
…提想散布給<a
+href="#exportcontrol">什麼地方的什麼人</a>。自由的意義在於當ä½
 åšé€™äº›äº‹çš„時候,不用另外尋求任何許可、也不必
付費取得任何同意。
 </p>
 
 <p>
-  一個重要的修改程式方法就是合併現成的子程式及模組。如果程式的許可證不å
…è¨±é€™ç¨®åšæ³•ï¼Œä¾‹å¦‚要求你持有版權才以添加
代碼,這樣的限製實在太大,算不上甚麼自由。
+你應該也擁有做出修改、並私自用於個人作品或者
把玩的自由,更而無須向他人提及這件事。如果你有å…
¬é–‹ç™¼å¸ƒé€™äº›ä¿®æ”¹ï¼Œä¹Ÿä¸å¿…另外以任何方式通知任何人。
 </p>
 
 <p>
-  自由3包
括以自由軟體方式發佈修改版本的自由。一個自由的許可證也要å
…è¨±å…¶ä»–的發佈方式,簡言之許可證不必是公å…
±ç‰ˆæ¬Š(copyleft)。然而,要求修改後的版本成為非自由的不算是自由許可證。
+自由之參包括以自由軟體發行你
修改後版本的自由。自由的授權條款可能也允許以å…
¶ä»–方式發行軟體;換句話說,自由的授權條款不一定要是<a
+href="/copyleft/copyleft.html">著作傳
+(copyleft)</a>式的授權條款。然而,若授權條款要求修改後的版本得改為非自由軟體,那就不算是自由的授權條款。
 </p>
 
 <p>
-  要落實這些自由,自由的許可證必
需是不可逆轉的;如果開發者可以廢除許可證,或加
逆向增加限制條款,這個都不是自由軟體。
+再次散布軟體副本的自由必須包含程式的二進位檔或å…
¶å¯åŸ·è¡Œå½¢å¼ã€èˆ‡å…
¶æºå§‹ç¢¼ï¼Œç„¡è«–該軟體是否被修改或沒有被修改。(以可執行形式散布軟體對於能方便安裝的自由作業系統來說是å¿
…要的。)如果某些程式無法產出二進位檔或可執行形式(因
某些程式語言不支援該功能之故)則沒有關係,但當你
發現或發展出解決這個問題的方法時,就必é 
ˆæ“æœ‰å†æ¬¡æ•£å¸ƒè©²ç¨®è»Ÿé«”形式的自由。
 </p>
 
+<h4>著作傳</h4>
+
 <p>
-  然而,不限制核心自由的規則是可以接受的。例如公å…
±ç‰ˆæ¬Šè¦å®šäº†ç™¼ä½ˆç¨‹å¼æ™‚,不能限制別人的æ 
¸å¿ƒè‡ªç”±ã€‚這規定就沒有跟核心自由沖突,而且還加強保護。
+我們可以採取一些措施來規範自由軟體的散布方式,只要這些規則不會和æ
 ¸å¿ƒè‡ªç”±è¡çªå³å¯ã€‚舉例來說,<a
+href="/copyleft/copyleft.html">著作傳 (copyleft)</a> 
[此處傳的發音為ㄔㄨㄢˊ]
+是一種再次散布程式的規則,使你無法對其他人施加
限制以綁住他們的重要自由;這樣的規則不會與æ 
¸å¿ƒè‡ªç”±è¡çªï¼Œåè€Œæ›´åŠ ä¿è­·é€™äº›è‡ªç”±ã€‚
 </p>
 
 <p>
-  「自由軟體」不代表「非商業用途」。自由軟體必
需要容許作商業用途。現在商業的自由軟體開發已經十分常見,而且十分重要。ä½
 æˆ–者曾付款購買自由軟體的複製本,或者å…
è²»ç²å¾—;無論軟體來自何方,你
一定有修改、複製、售賣軟體的自由。
+在 GNU 專案中,我們採取<a href="/copyleft/copyleft.html">著作傳</a>
+的方式以法律手段保護所有人的四大自由。基於許多重要因
素,我們認為<a
+href="/philosophy/pragmatic.html">採取著作傳的方式更佳</a>;不過,å
…¶ä»–採用<a
+href="/philosophy/categories.html#Non-CopyleftedFreeSoftware">非著作傳方式散布的自由軟體</a>亦合乎道德。請見<a
+href="/philosophy/categories.html">自由軟體類別</a>來瞭解「自由軟體」、「著作傳軟體」及å
…¶ä»–軟體類別之間的相互關係。
 </p>
 
+<h4>詳述有關打包和散布的規則</h4>
+
 <p>
-  對軟體的修改是否屬於改進是主觀的問題。如果你
修改程式的權利受到限制,無論之前的修改有多大的改進,也不能算是自由軟體。
+打包的規則若沒有實質限制你
發行修改後版本軟體的自由,或限制你
私下製作並自行運用修改後版本的自由,那麼這些軟體的打åŒ
…規則便可以接受。因此,如果授權條款要求你必é 
ˆæ›´å‹•ä¿®æ”¹å¾Œç‰ˆæœ¬çš„軟體名稱、移除原
+Logo
+標誌、或辨別出你
的修改…等等,都是可以接受的。只要這些要求不會繁瑣沉重到實際阻礙ä½
 ç™¼è¡Œè‡ªå·±çš„更動,那麼就能接受;試想你
已經對這個軟體做出許多更動,再多做一點點應該也不成問題。
 </p>
 
 <p>
-  然而,如果沒有限制你
發放或私人使用修改版本的自由,規定打包
修改版本的方式是可接受的。只要不妨礙你
發佈修改版本,許可證要求你
對修改版本更改名稱、移除圖案、標明你
修改的地方也是可以接受的;你
已經修改了程式,多作少許修改應該沒有困難。
+「如果你以這種方式發布你的軟體版本,那麼你也必é 
ˆè¦ç”¨é‚£ç¨®æ–¹å¼ç™¼å¸ƒã€çš„規則,只要滿足相同的條件也可以接受。可接受的規則範例之一是,如果ä½
 å·²å°‡ä¸€å€‹ä¿®æ”¹å¾Œçš„軟體版本散布出去,接著軟體å…
ˆå‰çš„開發者要求你給他一份副本,那麼你就必é 
ˆæä¾›çµ¦ä»–。(請留意到,即使在此規則之下,你
依然保有到底要不要將你
自己的版本散布出去的選擇。)要求你
將提供給大眾使用的版本之程式源始碼發行出來的規則亦可接受。
+</p>
+
+<p>
+有個特殊情況是,如果授權條款要求修改後的版本必é 
ˆæ”¹åï¼Œä½†é€™å€‹ç¨‹å¼å»æœƒè¢«å…¶ä»–程式調用。這樣å…
¶ä»–程式便無法調用你的版本,嚴重妨礙你
用修改後的版本替換原版。這類要求唯有程式å…
·å‚™å¦¥ç•¶çš„別名對照功能,允許你指定原始程式的名稱作為你
修改後版本的別名,如此才能接受。</p>
+
+<h4>出口管制</h4>
+
+<p>
+有時候政府的<a
+id="exportcontrol">出口管制條例</a>和貿易制裁會限制你
在國際散布軟體的自由。軟體開發者
並沒有權力消除或凌駕這些限制,但他們可以做、且必é 
ˆåšçš„是拒絕施加
這些限制作為使用該程式的條款。這樣一來,在這些政府管轄範圍以外的相關行為活動或人們就不會å›
 è€Œå—到影響。因此,自由軟體必
然不要求遵循任何高位階效力的出口管制條例作為實現任何å¿
…要自由的條款之一。
 </p>
 
 <p>
-  有個特殊情況,如果許可證要求改名的程式會給å…
¶ä»–程式調用。這會嚴重妨礙你
以修改的版本代替原版的功能。這類要一定要發佈者
提供適當的措施把修改了的程式的名稱聯繫到原版的名稱,不則不能接受。</p>
+單獨來看出口管制條例存在一事,只要不把它們納為授權本身的條款,那麼既然沒有限制使用è€
…
,就能接受。如果出口管制條例的位階實際上對自由軟體來說效力更輕微,那麼要求將它作為條款之一也不成問題;然而,這可能存有潛在問題,畢竟往後若出口法令修改使得該要求效力更高,那麼該軟體將轉變為非自由軟體。
+</p>
+
+<h4>法律觀點</h4>
 
 <p>
-  「如果你這樣發佈你的軟體版本,你
也一定要這樣做」的規則也可以接受,大家的條件是一樣的。例子之一就是如果ä½
 ç™¼ä½ˆäº†ä¸€å€‹ä¿®æ”¹å¥½çš„版本,然後舊版本的開發者
要求一份副本,你一定要提供。(請注意,你
還是有權決定是否發佈你的版本)。要求發佈你向å…
¬çœ¾ç™¼è¡¨çš„版本代碼給使用者也是可以接受的。
+為了讓這些自由成真,只要你沒做錯任何事,這些自由就必
須永恆、不可撤銷。如果軟體的開發者,在即便你
沒有做出任何可給予錯誤原因之情
事的狀況下,仍擁有撤銷授權條款、或往回追溯增補限制條款的權力,那便不是自由軟體。
 </p>
 
 <p>
-  我們的GNU項目會使用<a
-href="/copyleft/copyleft.html">公å…
±ç‰ˆæ¬Š</a>以法律手段保障所有人使用軟體的自由。但也有<a
-href="/philosophy/categories.html#Non-CopyleftedFreeSoftware">不是公å…
±ç‰ˆæ¬Šçš„自由軟體</a>。我們堅信<a
-href="/philosophy/pragmatic.html">使用公å…
±ç‰ˆæ¬Šæ˜¯è¼ƒå¥½çš„</a>,但如果你的程式屬於不是公å…
±ç‰ˆæ¬Šçš„自由軟體,基本上也是合符道德的。(看看<a
-href="/philosophy/categories.html">自由軟體</a>分類了解「自由軟體」、「å
…¬å…±ç‰ˆæ¬Šè»Ÿé«”」及其他種類軟體的關係。)
+自由的授權條款不可要求遵守非自由軟體的授權條款。因
此,舉例而言,若授權條款要求你遵循「你
使用之所有軟體程式」的授權條款,剛好使用者
有執行非自由的軟體程式,這就需要遵守那些非自由軟體的授權條款;那麼這樣的授權條款便非自由授權。
 </p>
 
 <p>
-  有些政府的<a
-id="exportcontrol">出口控制條款</a>和貿易制裁會限制你
在國際發佈軟體的自由。軟體開發者
沒有權力消除這些限制,但他們一定不要把這些限制成為使用軟體的條件。這樣在這些政府權力以外的人就可以不受限制。å
…¶å¯¦è‡ªç”±è»Ÿé«”根本就不可以要求服從任何限制æ 
¸å¿ƒè‡ªç”±çš„條款。
+指定司法裁判之適用法律、或是訴訟之提起地點、抑或是å…
©è€…,仍得被接受為自由的授權條款。
 </p>
 
+<h4>以契約為基礎的授權條款</h4>
+
 <p>
-  大部份自由軟體許可證都是基於版權法,而且可以要求的事是有限制的。如果一個基於版權法的許可證尊重以上所說的自由,就應該不會碰到我們從未遇過的問題(雖然有時會罕有地發生)。然而,有些自由軟體許可證是有合約的,合約就有很大的機會可以增åŠ
 é™åˆ¶ã€‚這意味這類許可證有機會過份地限制軟體而令å…
¶ä¸å†è‡ªç”±ã€‚
+大多數自由軟體的授權條款都是æ 
¹æ“šè‘—作權而來,而可透過著作權施予的相關要求會有所限制。如果以著作權為基礎的授權條款能以上述方式尊重自由,那麼似乎不會有å
…¶ä»–我們從未é 
æœŸçš„問題(雖然偶爾還是會發生)。然而,有些自由軟體的授權條款æ
 ¹æ“šå¥‘約而來,而契約可以施加
更多的可能限制。這代表這類授權條款很可能被視為無法接受地限制æ•
…為非自由。
 </p>
 
 <p>
-  我們無法列舉所有的情
況。如果上述的許可證以不常見的方法限制使用者
,就要重新審視,大概我們都會認為這不是自由軟體。
+我們無法列舉所有可能發生的情
況。如果以契約為基礎的授權條款,透過著作權式授權條款無法達成的非尋常方式限制使用è€
…,而且並未在此列為適當的自由軟體授權之一,我們必
需花點時間考量,而最終多半可能認為它屬於非自由授權。
 </p>
 
+<h4>當提及自由軟體時請使用正當的字詞</h4>
+
 <p>
-  提及有關自由軟體的時候,最好避å…
ä½¿ç”¨ã€Œæ”¾æ£„」、「免費」等字眼,因
為這類字眼暗示了這是價æ 
¼å•é¡Œï¼Œè€Œä¸æ˜¯è‡ªç”±ã€‚一些常見如「盜版」等有偏見的用語希望ä½
 ä¸è¦èªåŒã€‚請參考<a
-href="/philosophy/words-to-avoid.html">混淆和應避å…
ä½¿ç”¨çš„詞語</a>的討論。我們也有張<a
-href="/philosophy/fs-translations.html">翻譯「自由軟體」到不同語言</a>的æ¸
…單。
+當提及自由軟體時,最好要避免使用「贈送」、或「å…
è²»ã€ç­‰å­—詞,因為這類字詞暗指重點在於價æ 
¼ï¼Œè€Œä¸æ˜¯è‡ªç”±ã€‚一些常見用語如「盜版」,涵蓋了我們希望各位不要贊同的想法。請參考<a
+href="/philosophy/words-to-avoid.html">值得避å…
çš„混淆字詞</a>一文,å…
§æœ‰é€™é¡žå­—詞的相關討論。我們也有一份妥善將<a
+href="/philosophy/fs-translations.html">「自由軟體」一詞翻譯</a>成各種語言的æ¸
…單。
 </p>
 
+<h4>我們該如何解釋這些準則</h4>
+
 <p>
-  最後,注意有關這篇自由軟體的準則要小心詮釋。決定某軟體許可證是否自由,我們會審視它是否符合自由軟體的精神,還有準確用詞。如果許可證åŒ
…括無理的限制,就算我們沒有預期那些情況會發生,一律堅
決拒絕。有些許可證涉及太多考æ…
®ï¼Œæˆ‘們要咨詢律師才能下判斷。當我們給新問題下定論,就會更新這些準則令大家容易了解這些原å›
 ã€‚
+最後,當你
在詮釋本篇自由軟體定義中所陳述的準則時請務必謹æ…
Žæ€è€ƒã€‚若要判定某特定軟體授權是否符合自由軟體授權的定義時,我們便æ
 
¹æ“šé€™äº›æº–則來判斷它是否合乎自由軟體的精神、以及用辭是否準確。如果授權條款åŒ
…含無理的限制,即便我們é 
æœŸé‚£äº›ç‹€æ³ä¸æœƒç™¼ç”Ÿï¼Œæˆ‘們仍一樣堅
決反對。有時某授權條款的要求引起廣大的思æ…
®ï¼Œåœ¨æˆ‘們能判斷出該要求是否可接受之前,還需要å…
ˆå’Œå¾‹å¸«è¨Žè«–過。一旦我們對新議題有了總結,我們一般會更新這些準則讓大眾能更輕鬆瞭解為何哪些授權條款符合,而哪些不符。
 </p>
 
+<h4>尋求自由授權條款的相關幫助</h4>
+
 <p>
-  如果想了解某許可證是否符合自由軟體許可證,看看我們的<a
-href="/licenses/license-list.html">許可證清單</a>。如果你
想了解的不在此列,請來信 <a
+如果你
想瞭解某特定授權條款是否合乎自由軟體的授權條款,請見我們的<a
+href="/licenses/license-list.html">授權條款清單</a>。如果你
想瞭解的授權條款不在此列,請寫信寄送到 <a
 href="mailto:address@hidden";>&lt;address@hidden&gt;</a> 詢問。
 </p> 
 
 <p>
-  如果想撰寫新的許可證,請å…
ˆè¯çµ¡è‡ªç”±è»Ÿé«”基金會,我們會嘗試幫忙找出適合你
的現成許可證。
+若你苦心孤詣想撰寫出新的授權條款,還請å…
ˆé€éŽç›¸é—œæ–¹å¼ä¾†è¯çµ¡è‡ªç”±è»Ÿé«”基金會。畢竟不同的自由軟體授權條款若持續誕生,代表使用è€
…得下更多苦工去瞭解各種授權條款;而我們可協助你
找出合乎需求的現成自由軟體授權條款。
 </p>
 
 <p>
-  如果真的找不到,我們可以幫你
確保新的許可證為真正的自由軟體許可證,同時避å…
äº†å¾ˆå¤šå¯¦å‹™é›£é¡Œã€‚
+如果真的無法做到,萬一你
真的需要新的授權條款,我們可以協助你
確保新的授權條款成為真正的自由軟體授權,同時避å…
è¨±å¤šå¯¦å‹™ä¸Šçš„問題。
 </p>
 
-<h3 id="beyond-software">軟體以外</h3>
+<h3 id="beyond-software">軟體之外</h3>
 
 <p>
-  跟軟體一樣,其<a 
href="/philosophy/free-doc.html">說明書也一定要自由</a>,因
為說明書是軟體極重要的一部份。
+跟軟體必須自由一樣,<a
+href="/philosophy/free-doc.html">軟體使用手冊也一定要自由</a>,因
為使用手冊屬於軟體的作用部份。
 </p>
 
 <p>
-  這論點也適用於日常生活,教育工作和參考作品一類的知識。<a
-href="http://zh.wikipedia.org/zh-tw/";>維基百科</a>就是最廣為人知的樣版。
+這些論點也同樣適用於日常生活的作品 — 
像是承載有用知識的作品,包括教育著作和參考書等。其中 
<a
+href="http://zh.wikipedia.org/zh-tw/";>維基百科</a> 
是最廣為人知的範例。
 </p>
 
 <p>
-  任何種類的作品也<em>可以</em>自由,自由軟體的定義已伸延到<a
-href="http://freedomdefined.org/";>自由文化作品</a>。
+任何類型的作品也<em>能夠
</em>自由,自由軟體的定義已延伸出<a
+href="http://freedomdefined.org/";>自由文化作品</a>的定義,能用於任何類型的作品。
 </p>
 
-<h3 id="open-source">開放源碼?</h3>
+<h3 id="open-source">開放源始碼?</h3>
 
 <p>
-  有一群姐開始使用「開放源碼」這詞語指示近乎(但不å…
¨å®Œä¸€æ¨£)「自由軟體」的東西。我們屬意「自由軟體」一詞,å›
 ç‚ºé€™æ„å‘³è‡ªç”±è€Œä¸æ˜¯åƒ¹æ 
¼ï¼Œé€™å–šèµ·è‡ªç”±çš„聯想。「開放」一詞<a
-href="/philosophy/open-source-misses-the-point.html">很難聯想到自由</a>。
+有另一群人開始用「開放源始碼」或「開源」等這些詞彙來表示類同(但並非å
…
¨å®Œç­‰åŒï¼‰ã€Œè‡ªç”±è»Ÿé«”」的東西。我們更偏愛「自由軟體」一詞,å›
 ç‚ºä¸€æ—¦ä½ çž­è§£å®ƒæ‰€æè¿°çš„是自由而非價æ 
¼å¾Œï¼Œé€™æœƒå–šèµ·äººå€‘對自由的關注。至於「開放」一詞,<a
+href="/philosophy/open-source-misses-the-point.html">永遠
都不會讓人想到自由</a>。
 </p>
 
-<h3 id="History">更新記錄</h3>
+<h3 id="History">歷史記錄</h3>
 
-<p>  我們不時重新審視自由軟體的定義。這裏有些更新的記錄,還附有詳細解釋的連結。</p>
+<p>我們會不時修訂「自由軟體」的定義。這裡是有實際更改的紀錄æ¸
…單,隨附確實指出修改何處的連結。</p>
 
 <ul>
 
 <li><a
-href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.110&amp;r2=1.111";>版本
-1.111</a>。澄清︰版本1.77
-有關只有涉及以往的<em>限制</em>不被接受的說法。版權持有人有權同時就不同方式發佈的著作賦予額外的<em>權限</em>。</li>
+href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.152&amp;r2=1.153";>1.153
+版</a>:澄清執行程式的自由代表沒有什麼可以阻止你
讓它執行。</li>
+
+<li><a
+href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.40&amp;r2=1.141";>1.141
+版</a>:澄清何程式碼需要自由。</li>
+
+<li><a
+href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.134&amp;r2=1.135";>1.135
+版</a>:在每次講到自由之零時提到它是依據你
的想法執行程式的自由。</li>
+
+<li><a
+href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.133&amp;r2=1.134";>1.134
+版</a>:自由之零無關程式具備的功能。</li>
+
+<li><a
+href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.130&amp;r2=1.131";>1.131
+版</a>:自由的授權條款不可要求遵守å…
¶ä»–非自由的授權。</li>
+
+<li><a
+href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.128&amp;r2=1.129";>1.129
+版</a>:明確表達可選擇適用之法律與指定裁判之法庭。(這一直都是我們的政策方針。)</li>
+
+<li><a
+href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.121&amp;r2=1.122";>1.122
+版</a>:出口管制條例只有在位階低微才會造
成真正的問題;否則它只是潛在問題。</li>
+
+<li><a
+href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.117&amp;r2=1.118";>1.118
+版</a>:澄清:問題在於限制你修改的權利,而非限制你
做出怎樣的修改。任何修改都不只限於「改善」。</li>
 
 <li><a
-href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.104&amp;r2=1.105";>版本
-1.105</a>。表示自由1的聲明的論點(已在1.80表示)︰包括使用你
修改後的軟體版本。</li>
+href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.110&amp;r2=1.111";>1.111
+版</a>:澄清 1.77
+版只講到溯及以往的<em>限制</em>不可接受。著作權持有人永é
 æœ‰æ¬ŠåŒæ™‚以不同方式發行著作並賦予額外<em>許可</em>。</li>
 
 <li><a
-href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.91&amp;r2=1.92";>版本
-1.92</a>。澄清︰打亂的程式碼並不能視為源碼。</li>
+href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.104&amp;r2=1.105";>1.105
+版</a>:在自由之壹的簡要聲明中,反映出(已在 1.80 
版中表述)確實包含使用你
修改後的版本作為個人運算用的論點。</li>
 
 <li><a
-href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.89&amp;r2=1.90";>版本
-1.90</a>。澄清︰自由3 指發佈你
修改或改良軟體版本的權利,不是參與某開發項
目的權利。</li>
+href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.91&amp;r2=1.92";>1.92
+版</a>:澄清代碼混淆並不算得上是源始碼。</li>
 
 <li><a
-href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.88&amp;r2=1.89";>版本
-1.89</a>。自由3包括以自由軟體發佈修改版的權利。</li>
+href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.89&amp;r2=1.90";>1.90
+版</a>:澄清自由之參意指自由散布你
所修改後或改善後軟體版本的權利,而不是去參與他人開發專案的權利。</li>
 
 <li><a
-href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.79&amp;r2=1.80";>版本
-1.80</a>。自由1一定要落實,不可以以流於理論。例如︰不能Tivoization
 (譯者
按︰利用硬體限制自由軟體的自由,如有好的中譯,請通知我們)</li>
+href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.88&amp;r2=1.89";>1.89
+版</a>:自由之參包
括將修改後的版本以自由軟體發行的權利。</li>
 
 <li><a
-href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.76&amp;r2=1.77";>版本
-1.77</a>。澄清︰就算沒有完å…
¨å–代原意,追溯以往授權許可證的變更也是不能接受的。</li>
+href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.79&amp;r2=1.80";>1.80
+版</a>:自由之壹必
得實現,不能只是空談。例如︰不能接受 Tivo 行為。</li>
 
 <li><a
-href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.73&amp;r2=1.74";>版本
-1.74</a>。澄清四個不清𥇦、不全面的論點︰
+href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.76&amp;r2=1.77";>1.77
+版</a>:澄清就算沒有要完å…
¨å–代,只要是往回追溯更動授權條款也是不能接受的。</li>
+
+<li><a
+href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.73&amp;r2=1.74";>1.74
+版</a>:澄清四個不夠清𥇦、或是其他地方有提及但未å…
¨é¢åæ˜ çš„論點︰
 <ul>
-<li>「改良」不是指許可證可以限制發佈修改版本的種類。自由
 3 包括了發佈修改版本,不只變更。</li>
-<li>合併現有模組的權利只限於本身有適合許可證的模組。</li>
-<li>明確表示有關出口限制的結論。</li>
-<li>強制轉換許可證使舊許可證作廢。</li>
+<li>「改善」並不代表授權可實質限制你
可發行何種修改後版本的類型。自由之參包
含散布修改後的版本,不只是更改而已。</li>
+<li>合併至既有模組的權利僅
限於以適合條款授權的模組。</li>
+<li>明確聲明有關出口限制的結論。</li>
+<li>強行改變授權條款致使舊授權條款撤銷之議題。</li>
 </ul>
 </li>
 
 <li><a
-href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.56&amp;r2=1.57";>版本
-1.57</a>。增加段落「軟體以外」。</li>
+href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.56&amp;r2=1.57";>1.57
+版</a>:增補【軟體之外】小節。</li>
 
 <li><a
-href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.45&amp;r2=1.46";>版本
-1.46</a>。澄清︰ 
他以任何目的運行程式的自由的目的有重大意義。</li>
+href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.45&amp;r2=1.46";>1.46
+版</a>:澄清在依據個人目的執行程式的自由之中,何者
的目的是重點。</li>
 
 <li><a
-href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.40&amp;r2=1.41";>版本
-1.41</a>。澄清︰ 有關基於合約的許可證的用詞。</li>
+href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.40&amp;r2=1.41";>1.41
+版</a>:澄清有關基於契約的授權條款之用字遣詞。</li>
 
 <li><a
-href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.39&amp;r2=1.40";>版本
-1.40</a>。解釋自由的許可證一定容許你使用å…
¶ä»–自由軟體作修改。</li>
+href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.39&amp;r2=1.40";>1.40
+版</a>:解釋自由的授權條款必須允許你運用å…
¶ä»–現有的自由軟體來作修改。</li>
 
 <li><a
-href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.38&amp;r2=1.39";>版本
-1.39</a>。註明許可證可以要求發佈者提供在公共å 
´åˆä½¿ç”¨çš„軟件版本的源碼。</li>
+href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.38&amp;r2=1.39";>1.39
+版</a>:註明授權條款可以要求你提供你發布給å…
¬çœ¾ä½¿ç”¨çš„軟體版本其程式源始碼。</li>
 
 <li><a
-href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.30&amp;r2=1.31";>版本
-1.31</a>。註明許可證可要求修改者識別自己為修改者。å…
¶ä»–次要的澄清。</li>
+href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.30&amp;r2=1.31";>1.31
+版</a>:註明授權條款可以要求將你辨別為修改的作者
。文中載有其他次之的澄清。</li>
 
 <li><a
-href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.22&amp;r2=1.23";>版本
-1.23</a>。指出基於合約的許可證潛在的問題。</li>
+href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.22&amp;r2=1.23";>1.23
+版</a>:指出基於契約法的授權條款的潛在問題。</li>
 
 <li><a
-href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.15&amp;r2=1.16";>版本
-1.16</a>。解釋為何發佈可執行檔如此重要。</li>
+href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.15&amp;r2=1.16";>1.16
+版</a>:解釋為何散布二進位檔相當重要。</li>
 
 <li><a
-href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.10&amp;r2=1.11";>版本
-1.11</a>。註明自由許可證可以要求你向原作者
提供一份抄本。</li>
+href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.10&amp;r2=1.11";>1.11
+版</a>:註明自由授權條款可以依據前作者要求向其提供你
所散布之版本的副本。</li>
 
 </ul>
 
-<p>上面並沒有顯示一些對定義影響不大的版本。 你可以在<a
-href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;view=log";>cvs網é
 ç•Œé¢</a>找到完整的更新記錄。</p>
+<p>版號之間有略過一些,因為這些版本中本é 
é¢çš„變動並未影響到定義或者解釋。舉例來說,清
單未列出不影響內容的更動,像是格式設定、拼字、標點、é 
é¢çš„其他部分。你可以透過<a
+href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;view=log";>cvs
+網頁界面</a> 檢閱本頁的完整更動清單。</p>
 
 
 <div class="translators-notes">
 
 <!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
-<p><b>譯者按︰</b></p><ol><li
-id="trans1">中文讀者會覺得這句很奇怪,因
為英文的"Free"有「自由」及「免費」兩個意思,所以作者
要特別聲別,以正視聽。</li><li
-id="trans2">電è…
¦æœ‰ã€Œé›¶ã€çš„概念,很多時軟體工程師在編>程是都會以0為開始,很有趣吧!</li><li
-id="trans3">截至今天2012-7-15,這種>形式多數是指日常電è…
¦æª”案,但難保明天有其他新形式,所以譯者
保留原著採用形式(forms)這>個較抽象的字眼</li></ol></div>
+<b>譯者按︰</b>
+<ol><li id="trans1">中文讀者也許會覺得這語句很怪,因
為英文的 Free
+有「自由」及「免費」兩個意思,所以作者
要特別聲明,以正視聽。</li>
+<li id="trans2">電è…
¦æœ‰ã€Œé›¶ã€çš„概念,很多時軟體工程師在編程時都會以 0 
開始,很有趣吧!</li>
+</ol></div>
 </div>
 
+<!-- for id="content", starts in the include above -->
 <!--#include virtual="/server/footer.zh-tw.html" -->
 <div id="footer">
 <div class="unprintable">
 
-<p>
-請來郵 <a 
href="mailto:address@hidden";>&lt;address@hidden&gt;</a>查詢「自由軟體基金會」及「GNU
-計畫」的事宜。或者<a href="/contact/">透過å…
¶ä»–方式</a>聯絡自由軟體基金會。
-請來郵<a
-href="mailto:address@hidden";>&lt;address@hidden&gt;</a>告訴我們任何失效的連結、錯誤和建議。
-</p>
-
-<p>
-請參照 <a href="/server/standards/README.translations.html">翻譯說明</a>
-了解有關協助翻譯本文的事情。
-</p>
+<p>請來信到 <a href="mailto:address@hidden";>&lt;address@hidden&gt;</a> 
詢問有關自由軟體基金會(FSF)和
+GNU 的一般問題;或者<a href="/contact/">以å…
¶ä»–方式</a>聯絡自由軟體基金會。至於損毀的連結及å…
¶ä»–修正和建議,可以將之寄給 <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="mailto:address@hidden";>&lt;address@hidden&gt;</a></p>
+<p>請參照 <a href="/server/standards/README.translations.html">翻譯讀我 
README</a>
+來瞭解協調和提交我們的網頁翻譯相關事宜。</p>
 </div>
 
-<p>
-Copyright &copy; 1996-2002, 2004-2007, 2009, 2010, 2012, 2013 
自由軟體基金會
-</p>
-<p>本頁面採用 <a rel="license"
-href="http://creativecommons.org/licenses/by-nd/3.0/us/deed.zh_TW";>Creative 
Commons
-Attribution-NoDerivs 3.0 United States License</a> 許可證授權。
-</p>
+<!-- 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; 1996, 2002, 2004-2007, 2009-2017 Free Software Foundation,
+Inc.</p>
+
+<p>本頁面採用<a rel="license"
+href="https://creativecommons.org/licenses/by-nd/4.0/deed.zh_TW";>創用 CC
+授權姓名標示-禁止改作 4.0 國際</a>條款給予授權。</p>
 
 <!--#include virtual="/server/bottom-notes.zh-tw.html" -->
 <div class="translators-credits">
 
 <!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
-<p><b>翻譯</b>:</p>2013︰Karl Lam | karl dot v dot lam at gmail dot com
-<br/>2008︰林鈺維 | Yuwei Lin | yuwei {at} ylin {dot} org</div>
-
+<b>翻譯</b>:曾政嘉 <a href="mailto:zerngjia (at) member (dot) fsf (dot)
+org">&lt;zerngjia (at) member (dot) fsf (dot) org&gt;</a>, 2017.
+Karl Lam <a href="mailto:karl (dot) v (dot) lam (at) gmail (dot)
+com">&lt;karl (dot) v (dot) lam (at) gmail (dot) com&gt;</a>, 2013.
+林鈺維 <a href="mailto:yuwei (at) ylin (dot) org">Yuwei Lin</a>, 2008.</div>
 
 <p class="unprintable"><!-- timestamp start -->
 更新時間︰
 
-$Date: 2016/08/20 14:58:39 $
+$Date: 2017/06/04 15:58:19 $
 
 <!-- timestamp end -->
 </p>
 </div>
-
-
 </div>
-
 </body>
 </html>

Index: philosophy/fs-motives.nl.html
===================================================================
RCS file: /web/www/www/philosophy/fs-motives.nl.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- philosophy/fs-motives.nl.html       28 May 2017 16:58:57 -0000      1.1
+++ philosophy/fs-motives.nl.html       4 Jun 2017 15:58:19 -0000       1.2
@@ -53,7 +53,7 @@
 technische en sociale vaardigheden te verbeteren. Als leraar kan je je
 leerlingen aanmoedigen om deel te nemen aan een bestaand
 vrijesoftwareproject of je kan hen indelen in een vrijesoftwareproject, wat
-een uitstekende mogelijkheid kan zijn.</dd>
+een uitstekende leermogelijkheid kan zijn.</dd>
 
 <dt>Dankbaarheid</dt>
 
@@ -93,8 +93,8 @@
 
 </dl>
 
-<p>De mens is complex, en het is vrij gebruikelijk dat iemand ergens meerdere
-motieven tegelijkertijd voor heeft.</p>
+<p>Mensen zijn complex, en het komt vaak voor dat iemand meerdere motieven
+heeft voor een enkele handeling.</p>
 
 <p>Iedereen is anders, en er kunnen andere motieven zijn die niet in deze lijst
 staan. Als je andere motieven kent die hier niet staan, stuur dan een e-mail
@@ -174,7 +174,7 @@
 <p class="unprintable"><!-- timestamp start -->
 Bijgewerkt:
 
-$Date: 2017/05/28 16:58:57 $
+$Date: 2017/06/04 15:58:19 $
 
 <!-- timestamp end -->
 </p>

Index: philosophy/po/free-sw.zh-tw-en.html
===================================================================
RCS file: /web/www/www/philosophy/po/free-sw.zh-tw-en.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- philosophy/po/free-sw.zh-tw-en.html 3 Mar 2013 06:03:19 -0000       1.2
+++ philosophy/po/free-sw.zh-tw-en.html 4 Jun 2017 15:58:19 -0000       1.3
@@ -1,17 +1,23 @@
 <!--#include virtual="/server/header.html" -->
-
-<title>What is free software? - GNU Project - Free Software Foundation 
(FSF)</title>
+<!-- Parent-Version: 1.79 -->
+<title>What is free software?
+- GNU Project - Free Software Foundation</title>
 
 <meta http-equiv="Keywords" content="GNU, FSF, Free Software Foundation, 
Linux, Emacs, GCC, Unix, Free Software, Operating System, GNU Kernel, HURD, GNU 
HURD, Hurd" />
 <meta http-equiv="Description" content="Since 1983, developing the free Unix 
style operating system GNU, so that computer users can have the freedom to 
share and improve the software they use." />
-<link rel="alternate" title="What's New" 
href="http://www.gnu.org/rss/whatsnew.rss"; type="application/rss+xml" />
-<link rel="alternate" title="New Free Software" 
href="http://www.gnu.org/rss/quagga.rss"; type="application/rss+xml" />
 
 <!--#include virtual="/philosophy/po/free-sw.translist" -->
 <!--#include virtual="/server/banner.html" -->
 
 <h2>What is free software?</h2>
 
+<blockquote class="note" id="fsf-licensing"><p style="font-size: 80%">
+Have a question about free software licensing not answered here?
+See our other <a href="http://www.fsf.org/licensing";>licensing resources</a>,
+and if necessary contact the FSF Compliance Lab
+at <a href="mailto:address@hidden";>address@hidden</a>.</p>
+</blockquote>
+
 <h3>The Free Software Definition</h3>
 
 <blockquote>
@@ -27,24 +33,29 @@
 
 <p>
 &ldquo;Free software&rdquo; means software that respects users'
-freedom and community.  Roughly, <b>the users have the freedom to run,
-copy, distribute, study, change and improve the software</b>.  With these
-freedoms, the users (both individually and collectively) control the
-program and what it does for them.
+freedom and community.  Roughly, it means that <b>the users have the
+freedom to run, copy, distribute, study, change and improve the
+software</b>.  Thus, &ldquo;free software&rdquo; is a matter of
+liberty, not price.  To understand the concept, you should think of
+&ldquo;free&rdquo; as in &ldquo;free speech,&rdquo; not as in
+&ldquo;free beer&rdquo;.  We sometimes call it &ldquo;libre
+software,&rdquo; borrowing the French or Spanish word for
+&ldquo;free&rdquo; as in freedom, to show we do not mean the software
+is gratis.
 </p>
 
 <p>
-When users don't control the program, the program controls the users.
-The developer controls the program, and through it controls the users.
-This nonfree or &ldquo;proprietary&rdquo; program is therefore an
-instrument of unjust power.
+We campaign for these freedoms because everyone deserves them.  With
+these freedoms, the users (both individually and collectively) control
+the program and what it does for them.  When users don't control the
+program, we call it a &ldquo;nonfree&rdquo; or
+&ldquo;proprietary&rdquo; program.  The nonfree program controls the
+users, and the developer controls the program; this makes the
+program <a href="/philosophy/free-software-even-more-important.html">
+an instrument of unjust power</a>.
 </p>
 
-<p>
-Thus, &ldquo;free software&rdquo; is a matter of liberty, not price.
-To understand the concept, you should think of &ldquo;free&rdquo; as
-in &ldquo;free speech,&rdquo; not as in &ldquo;free beer&rdquo;.
-</p>
+<h4> The four essential freedoms</h4>
 
 <p>
 A program is free software if the program's users have the
@@ -52,7 +63,8 @@
 </p>
 
 <ul>
-  <li>The freedom to run the program, for any purpose (freedom 0).</li>
+  <li>The freedom to run the program as you wish,
+      for any purpose (freedom 0).</li>
   <li>The freedom to study how the program works, and change it so it
       does your computing as you wish (freedom 1). Access to the source
       code is a precondition for this.
@@ -68,21 +80,35 @@
 </ul>
 
 <p>
-A program is free software if users have all of these freedoms.  Thus,
-you should be free to redistribute copies, either with or without
-modifications, either gratis or charging a fee for distribution, to
-<a href="#exportcontrol">anyone anywhere</a>.  Being free to do these
-things means (among other things) that you do not have to ask or pay
-for permission to do so.
-</p>
+A program is free software if it gives users adequately all of these
+freedoms.  Otherwise, it is nonfree.  While we can distinguish various
+nonfree distribution schemes in terms of how far they fall short of
+being free, we consider them all equally unethical.</p>
+
+<p>In any given scenario, these freedoms must apply to whatever code
+we plan to make use of, or lead others to make use of.  For instance,
+consider a program A which automatically launches a program B to
+handle some cases.  If we plan to distribute A as it stands, that
+implies users will need B, so we need to judge whether both A and B
+are free.  However, if we plan to modify A so that it doesn't use B,
+only A needs to be free; B is not pertinent to that plan.</p>
 
 <p>
-You should also have the freedom to make modifications and use them
-privately in your own work or play, without even mentioning that they
-exist.  If you do publish your changes, you should not be required to
-notify anyone in particular, or in any particular way.
+&ldquo;Free software&rdquo; does not mean &ldquo;noncommercial&rdquo;.  A free
+program must be available for commercial use, commercial development,
+and commercial distribution.  Commercial development of free software
+is no longer unusual; such free commercial software is very important.
+You may have paid money to get copies of free software, or you may have
+obtained copies at no charge.  But regardless of how you got your copies,
+you always have the freedom to copy and change the software, even to 
+<a href="/philosophy/selling.html">sell copies</a>.
 </p>
 
+<p>The rest of this page clarifies certain points about what makes
+specific freedoms adequate or not.</p>
+
+<h4>The freedom to run the program as you wish</h4>
+
 <p>
 The freedom to run the program means the freedom for any kind of person
 or organization to use it on any kind of computer system, for any kind of
@@ -95,15 +121,13 @@
 </p>
 
 <p>
-The freedom to redistribute copies must include binary or executable
-forms of the program, as well as source code, for both modified and
-unmodified versions.  (Distributing programs in runnable form is necessary
-for conveniently installable free operating systems.)  It is OK if there
-is no way to produce a binary or executable form for a certain program
-(since some languages don't support that feature), but you must have the
-freedom to redistribute such forms should you find or develop a way to
-make them.
-</p>
+The freedom to run the program as you wish means that you are not
+forbidden or stopped from making it run.  This has nothing to do with what
+functionality the program has, whether it is technically capable of
+functioning in any given environment, or whether it is useful for any
+particular computing activity.</p>
+
+<h4>The freedom to study the source code and make changes</h4>
 
 <p>
 In order for freedoms 1 and 3 (the freedom to make changes and the
@@ -120,10 +144,9 @@
 run someone else's modified versions but refuse to run yours &mdash; a
 practice known as &ldquo;tivoization&rdquo; or &ldquo;lockdown&rdquo;,
 or (in its practitioners' perverse terminology) as &ldquo;secure
-boot&rdquo; &mdash; freedom 1 becomes a theoretical fiction rather
-than a practical freedom.  This is not sufficient.  In other words,
-these binaries are not free software even if the source code they are
-compiled from is free.
+boot&rdquo; &mdash; freedom 1 becomes an empty pretense rather than a
+practical reality.  These binaries are not free
+software even if the source code they are compiled from is free.
 </p>
 
 <p>
@@ -135,6 +158,29 @@
 </p>
 
 <p>
+Whether a change constitutes an improvement is a subjective matter.
+If your right to modify a program is limited, in substance, to changes that
+someone else considers an improvement, that program is not free.
+</p>
+
+<h4>The freedom to redistribute if you wish: basic requirements</h4>
+
+<p>Freedom to distribute (freedoms 2 and 3) means you are free to
+redistribute copies, either with or without modifications, either
+gratis or charging a fee for distribution, to
+<a href="#exportcontrol">anyone anywhere</a>.  Being free to do these
+things means (among other things) that you do not have to ask or pay
+for permission to do so.
+</p>
+
+<p>
+You should also have the freedom to make modifications and use them
+privately in your own work or play, without even mentioning that they
+exist.  If you do publish your changes, you should not be required to
+notify anyone in particular, or in any particular way.
+</p>
+
+<p>
 Freedom 3 includes the freedom to release your modified versions
 as free software.  A free license may also permit other ways of
 releasing them; in other words, it does not have to be
@@ -144,41 +190,45 @@
 </p>
 
 <p>
-In order for these freedoms to be real, they must be permanent and
-irrevocable as long as you do nothing wrong; if the developer of the
-software has the power to revoke the license, or retroactively add
-restrictions to its terms, without your doing anything wrong to give
-cause, the software is not free.
+The freedom to redistribute copies must include binary or executable
+forms of the program, as well as source code, for both modified and
+unmodified versions.  (Distributing programs in runnable form is necessary
+for conveniently installable free operating systems.)  It is OK if there
+is no way to produce a binary or executable form for a certain program
+(since some languages don't support that feature), but you must have the
+freedom to redistribute such forms should you find or develop a way to
+make them.
 </p>
 
+<h4>Copyleft</h4>
+
 <p>
-However, certain kinds of rules about the manner of distributing free
+Certain kinds of rules about the manner of distributing free
 software are acceptable, when they don't conflict with the central
-freedoms.  For example, copyleft (very simply stated) is the rule that
-when redistributing the program, you cannot add restrictions to deny
-other people the central freedoms.  This rule does not conflict with
-the central freedoms; rather it protects them.
+freedoms.  For example, <a href="/copyleft/copyleft.html">copyleft</a>
+(very simply stated) is the rule that when redistributing the program,
+you cannot add restrictions to deny other people the central freedoms.
+This rule does not conflict with the central freedoms; rather it
+protects them.
 </p>
 
 <p>
-&ldquo;Free software&rdquo; does not mean &ldquo;noncommercial&rdquo;.  A free
-program must be available for commercial use, commercial development,
-and commercial distribution.  Commercial development of free software
-is no longer unusual; such free commercial software is very important.
-You may have paid money to get copies of free software, or you may have
-obtained copies at no charge.  But regardless of how you got your copies,
-you always have the freedom to copy and change the software, even to 
-<a href="/philosophy/selling.html">sell copies</a>.
+In the GNU project, we use copyleft to protect the four freedoms
+legally for everyone.  We believe there are important reasons why
+<a href="/philosophy/pragmatic.html">it is better to use
+copyleft</a>.  However,
+<a href="/philosophy/categories.html#Non-CopyleftedFreeSoftware">
+noncopylefted free software</a> is ethical
+too.  See <a href="/philosophy/categories.html">Categories of Free
+Software</a> for a description of how &ldquo;free software,&rdquo;
+&ldquo;copylefted software&rdquo; and other categories of software
+relate to each other.
 </p>
 
-<p>
-Whether a change constitutes an improvement is a subjective matter.
-If your right to modify a program is limited, in substance, to changes that
-someone else considers an improvement, that program is not free.
-</p>
+<h4>Rules about packaging and distribution details</h4>
 
 <p>
-However, rules about how to package a modified version are acceptable,
+Rules about how to package a modified version are acceptable,
 if they don't substantively limit your freedom to release modified
 versions, or your freedom to make and use modified versions privately.
 Thus, it is acceptable for the license to require that you change the
@@ -190,15 +240,6 @@
 </p>
 
 <p>
-A special issue arises when a license requires changing the name by
-which the program will be invoked from other programs.  That
-effectively hampers you from releasing your changed version so that it
-can replace the original when invoked by those other programs.  This
-sort of requirement is acceptable only if there's a suitable aliasing
-facility that allows you to specify the original program's name as an
-alias for the modified version.</p>
-
-<p>
 Rules that &ldquo;if you make your version available in this way, you
 must make it available in that way also&rdquo; can be acceptable too,
 on the same condition.  An example of such an acceptable rule is one
@@ -211,15 +252,15 @@
 </p>
 
 <p>
-In the GNU project, we use 
-<a href="/copyleft/copyleft.html">copyleft</a>
-to protect these freedoms legally for everyone.  But 
-<a href="/philosophy/categories.html#Non-CopyleftedFreeSoftware">noncopylefted
-free software</a> also exists.  We believe there are important reasons why
-<a href="/philosophy/pragmatic.html">it is better to use copyleft</a>,
-but if your program is noncopylefted free software, it is still basically
-ethical. (See <a href="/philosophy/categories.html">Categories of Free 
Software</a> for a description of how &ldquo;free software,&rdquo; 
&ldquo;copylefted software&rdquo; and other categories of software relate to 
each other.)
-</p>
+A special issue arises when a license requires changing the name by
+which the program will be invoked from other programs.  That
+effectively hampers you from releasing your changed version so that it
+can replace the original when invoked by those other programs.  This
+sort of requirement is acceptable only if there's a suitable aliasing
+facility that allows you to specify the original program's name as an
+alias for the modified version.</p>
+
+<h4>Export regulations</h4>
 
 <p>
 Sometimes government <a id="exportcontrol">export control regulations</a>
@@ -229,11 +270,47 @@
 is refuse to impose them as conditions of use of the program.  In this
 way, the restrictions will not affect activities and people outside the
 jurisdictions of these governments.  Thus, free software licenses
-must not require obedience to any export regulations as a condition of
-any of the essential freedoms.
+must not require obedience to any nontrivial export regulations as a
+condition of exercising any of the essential freedoms.
+</p>
+
+<p>
+Merely mentioning the existence of export regulations, without making
+them a condition of the license itself, is acceptable since it does
+not restrict users.  If an export regulation is actually trivial for
+free software, then requiring it as a condition is not an actual
+problem; however, it is a potential problem, since a later change in
+export law could make the requirement nontrivial and thus render the
+software nonfree.
+</p>
+
+<h4>Legal considerations</h4>
+
+<p>
+In order for these freedoms to be real, they must be permanent and
+irrevocable as long as you do nothing wrong; if the developer of the
+software has the power to revoke the license, or retroactively add
+restrictions to its terms, without your doing anything wrong to give
+cause, the software is not free.
+</p>
+
+<p>
+A free license may not require compliance with the license of a
+nonfree program.  Thus, for instance, if a license requires you to
+comply with the licenses of &ldquo;all the programs you use&rdquo;, in
+the case of a user that runs nonfree programs this would require
+compliance with the licenses of those nonfree programs; that makes the
+license nonfree.
 </p>
 
 <p>
+It is acceptable for a free license to specify which jurisdiction's
+law applies, or where litigation must be done, or both.
+</p>
+
+<h4>Contract-based licenses</h4>
+
+<p>
 Most free software licenses are based on copyright, and there are limits
 on what kinds of requirements can be imposed through copyright.  If a
 copyright-based license respects freedom in the ways described above, it
@@ -252,6 +329,8 @@
 it is nonfree.
 </p>
 
+<h4>Use the right words when talking about free software</h4>
+
 <p>
 When talking about free software, it is best to avoid using terms
 like &ldquo;give away&rdquo; or &ldquo;for free,&rdquo; because those terms 
imply that
@@ -263,6 +342,8 @@
 &ldquo;free software&rdquo;</a> into various languages.
 </p>
 
+<h4>How we interpret these criteria</h4>
+
 <p>
 Finally, note that criteria such as those stated in this free software
 definition require careful thought for their interpretation.  To decide
@@ -277,6 +358,8 @@
 it easier to see why certain licenses do or don't qualify.
 </p>
 
+<h4>Get help with free licenses</h4>
+
 <p>
 If you are interested in whether a specific license qualifies as a free
 software license, see our <a href="/licenses/license-list.html">list
@@ -324,7 +407,7 @@
 <h3 id="open-source">Open Source?</h3>
 
 <p>
-Another group has started using the term &ldquo;open source&rdquo; to mean
+Another group uses the term &ldquo;open source&rdquo; to mean
 something close (but not identical) to &ldquo;free software&rdquo;.  We
 prefer the term &ldquo;free software&rdquo; because, once you have heard that
 it refers to freedom rather than price, it calls to mind freedom.  The
@@ -335,11 +418,42 @@
 <h3 id="History">History</h3>
 
 <p>From time to time we revise this Free Software Definition.  Here is
-the list of changes, along with links to show exactly what was
-changed.</p>
+the list of substantive changes, along with links to show exactly what
+was changed.</p>
 
 <ul>
 
+<li><a 
href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.152&amp;r2=1.153";>Version
+1.153</a>: Clarify that freedom to run the program means nothing stops
+you from making it run.</li>
+
+<li><a 
href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.140&amp;r2=1.141";>Version
+1.141</a>: Clarify which code needs to be free.</li>
+
+<li><a 
href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.134&amp;r2=1.135";>Version
+1.135</a>: Say each time that freedom 0 is the freedom to run the program
+as you wish.</li>
+
+<li><a 
href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.133&amp;r2=1.134";>Version
+1.134</a>: Freedom 0 is not a matter of the program's functionality.</li>
+
+<li><a 
href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.130&amp;r2=1.131";>Version
+1.131</a>: A free license may not require compliance with a nonfree license
+of another program.</li>
+
+<li><a 
href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.128&amp;r2=1.129";>Version
+1.129</a>: State explicitly that choice of law and choice of forum
+specifications are allowed.  (This was always our policy.)</li>
+
+<li><a 
href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.121&amp;r2=1.122";>Version
+1.122</a>: An export control requirement is a real problem if the
+requirement is nontrivial; otherwise it is only a potential problem.</li>
+
+<li><a 
href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.117&amp;r2=1.118";>Version
+1.118</a>: Clarification: the issue is limits on your right to modify,
+not on what modifications you have made.  And modifications are not limited
+to &ldquo;improvements&rdquo;</li>
+
 <li><a 
href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.110&amp;r2=1.111";>Version
 1.111</a>: Clarify 1.77 by saying that only
 retroactive <em>restrictions</em> are unacceptable.  The copyright
@@ -419,60 +533,81 @@
 
 <li><a 
href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.10&amp;r2=1.11";>Version
 1.11</a>: Note that a free license may require you to send a copy of
-versions you distribute to the author.</li>
+versions you distribute to previous developers on request.</li>
 
 </ul>
 
 <p>There are gaps in the version numbers shown above because there are
-other changes in this page that do not affect the definition as such.
-These changes are in other parts of the page.  You can review the
-complete list of changes to the page through
+other changes in this page that do not affect the definition or its
+interpretations.  For instance, the list does not include changes in
+asides, formatting, spelling, punctuation, or other parts of the page.
+You can review the complete list of changes to the page through
 the <a 
href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;view=log";>cvsweb
 interface</a>.</p>
 
-</div>
 
+</div><!-- for id="content", starts in the include above -->
 <!--#include virtual="/server/footer.html" -->
-
 <div id="footer">
+<div class="unprintable">
 
-<p>
-Please send FSF &amp; GNU inquiries to 
+<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.
-<br />
-Please send broken links and other corrections or suggestions to
-<a href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.
-</p>
+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>
-Please see the 
-<a href="/server/standards/README.translations.html">Translations
-README</a> for information on coordinating and submitting
-translations of this article.
-</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; 1996, 2002, 2004-2007, 2009-2017
+Free Software Foundation, Inc.</p>
 
-<p>
-Copyright &copy; 1996-2002, 2004-2007, 2009, 2010, 2012 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>Updated:
+<p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2013/03/03 06:03:19 $
+$Date: 2017/06/04 15:58:19 $
 <!-- timestamp end -->
 </p>
 </div>
-
-
 </div>
-
 </body>
 </html>

Index: philosophy/po/free-sw.zh-tw.po
===================================================================
RCS file: /web/www/www/philosophy/po/free-sw.zh-tw.po,v
retrieving revision 1.39
retrieving revision 1.40
diff -u -b -r1.39 -r1.40
--- philosophy/po/free-sw.zh-tw.po      4 Jun 2017 15:34:04 -0000       1.39
+++ philosophy/po/free-sw.zh-tw.po      4 Jun 2017 15:58:19 -0000       1.40
@@ -12,12 +12,11 @@
 "PO-Revision-Date: 2017-06-04 03:28+0800\n"
 "Last-Translator: Cheng-Chia Tseng <address@hidden>\n"
 "Language-Team: Traditional Chinese <address@hidden>\n"
-"Plural-Forms: nplurals=1; plural=0;\n"
 "Language: zh_TW\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"Outdated-Since: 2013-05-27 03:55+0000\n"
+"Plural-Forms: nplurals=1; plural=0;\n"
 "X-Generator: Poedit 1.8.13\n"
 
 #. type: Content of: <title>
@@ -685,11 +684,6 @@
 "改何處的連結。"
 
 #. type: Content of: <ul><li>
-#| msgid ""
-#| "<a href=\"http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.";
-#| "html?root=www&amp;r1=1.10&amp;r2=1.11\">Version 1.11</a>: Note that a "
-#| "free license may require you to send a copy of versions you distribute to "
-#| "the author."
 msgid ""
 "<a href=\"http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?";
 "root=www&amp;r1=1.152&amp;r2=1.153\">Version 1.153</a>: Clarify that freedom "
@@ -709,11 +703,6 @@
 "root=www&amp;r1=1.40&amp;r2=1.141\">1.141 版</a>:澄清
何程式碼需要自由。"
 
 #. type: Content of: <ul><li>
-#| msgid ""
-#| "<a href=\"http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.";
-#| "html?root=www&amp;r1=1.10&amp;r2=1.11\">Version 1.11</a>: Note that a "
-#| "free license may require you to send a copy of versions you distribute to "
-#| "the author."
 msgid ""
 "<a href=\"http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?";
 "root=www&amp;r1=1.134&amp;r2=1.135\">Version 1.135</a>: Say each time that "
@@ -724,11 +713,6 @@
 "是依據你的想法執行程式的自由。"
 
 #. type: Content of: <ul><li>
-#| msgid ""
-#| "<a href=\"http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.";
-#| "html?root=www&amp;r1=1.10&amp;r2=1.11\">Version 1.11</a>: Note that a "
-#| "free license may require you to send a copy of versions you distribute to "
-#| "the author."
 msgid ""
 "<a href=\"http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?";
 "root=www&amp;r1=1.133&amp;r2=1.134\">Version 1.134</a>: Freedom 0 is not a "
@@ -739,11 +723,6 @@
 "能。"
 
 #. type: Content of: <ul><li>
-#| msgid ""
-#| "<a href=\"http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.";
-#| "html?root=www&amp;r1=1.10&amp;r2=1.11\">Version 1.11</a>: Note that a "
-#| "free license may require you to send a copy of versions you distribute to "
-#| "the author."
 msgid ""
 "<a href=\"http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?";
 "root=www&amp;r1=1.130&amp;r2=1.131\">Version 1.131</a>: A free license may "
@@ -765,10 +744,6 @@
 "指定裁判之法庭。(這一直都是我們的政策方針。)"
 
 #. type: Content of: <ul><li>
-#| msgid ""
-#| "<a href=\"http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.";
-#| "html?root=www&amp;r1=1.22&amp;r2=1.23\">Version 1.23</a>: Address "
-#| "potential problems related to contract-based licenses."
 msgid ""
 "<a href=\"http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?";
 "root=www&amp;r1=1.121&amp;r2=1.122\">Version 1.122</a>: An export control "
@@ -1050,15 +1025,12 @@
 "translations of this article."
 msgstr ""
 
"我們努力盡所能提供貼切、品質良善的翻譯。然而,我們無法十å
…¨åç¾Žï¼Œé‚„請將你的意"
-"見評述與一般建議寄給 <a href=\"mailto:address@hidden";>&lt;"
-"address@hidden&gt;</a></p>\n"
+"見評述與一般建議寄給 <a href=\"mailto:address@hidden";>&lt;web-"
+"address@hidden&gt;</a></p>\n"
 "<p>請參照 <a 
href=\"/server/standards/README.translations.html\">翻譯讀我 "
 "README</a> 來瞭解協調和提交我們的網頁翻譯相關事宜。"
 
 #. type: Content of: <div><p>
-#| msgid ""
-#| "Copyright &copy; 1996-2002, 2004-2007, 2009, 2010, 2012 Free Software "
-#| "Foundation, Inc."
 msgid ""
 "Copyright &copy; 1996, 2002, 2004-2007, 2009-2017 Free Software Foundation, "
 "Inc."

Index: philosophy/po/fs-motives.nl.po
===================================================================
RCS file: /web/www/www/philosophy/po/fs-motives.nl.po,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4



reply via email to

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