www-commits
[Top][All Lists]
Advanced

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

www gnu/thegnuproject.el.html philosophy/words-...


From: GNUN
Subject: www gnu/thegnuproject.el.html philosophy/words-...
Date: Sun, 15 Jul 2012 08:28:17 +0000

CVSROOT:        /web/www
Module name:    www
Changes by:     GNUN <gnun>     12/07/15 08:28:17

Modified files:
        gnu            : thegnuproject.el.html 
        philosophy     : words-to-avoid.de.html 
        philosophy/po  : why-free.translist why-free.zh-tw.po 
                         words-to-avoid.de-en.html 
Added files:
        gnu/po         : thegnuproject.el-diff.html 
        philosophy     : why-free.zh-tw.html 
        philosophy/po  : why-free.zh-tw-en.html 
        server/gnun/compendia: compendium.zh-tw.po 

Log message:
        Automatic update by GNUnited Nations.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/thegnuproject.el.html?cvsroot=www&r1=1.22&r2=1.23
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/thegnuproject.el-diff.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/words-to-avoid.de.html?cvsroot=www&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/why-free.zh-tw.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/why-free.translist?cvsroot=www&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/why-free.zh-tw.po?cvsroot=www&r1=1.2&r2=1.3
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/words-to-avoid.de-en.html?cvsroot=www&r1=1.9&r2=1.10
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/why-free.zh-tw-en.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/server/gnun/compendia/compendium.zh-tw.po?cvsroot=www&rev=1.1

Patches:
Index: gnu/thegnuproject.el.html
===================================================================
RCS file: /web/www/www/gnu/thegnuproject.el.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -b -r1.22 -r1.23
--- gnu/thegnuproject.el.html   26 Apr 2012 16:32:57 -0000      1.22
+++ gnu/thegnuproject.el.html   15 Jul 2012 08:27:04 -0000      1.23
@@ -8,6 +8,12 @@
 <meta http-equiv="Keywords" content="GNU, έργο GNU, ΙΕΛ, 
ελεύθερο λογισμικό, Ίδρυμα Ελεύθερου 
Λογισμικού, ιστορία" />
 
 <!--#include virtual="/server/banner.el.html" -->
+<!--#set var="PO_FILE"
+ value='<a href="http://www.gnu.org/gnu/po/thegnuproject.el.po";>
+ http://www.gnu.org/gnu/po/thegnuproject.el.po</a>' -->
+ <!--#set var="ORIGINAL_FILE" value="/gnu/thegnuproject.html" -->
+ <!--#set var="DIFF_FILE" value="/gnu/po/thegnuproject.el-diff.html" -->
+ <!--#include virtual="/server/outdated.el.html" -->
 <!--#include virtual="/gnu/po/thegnuproject.translist" -->
 <h2>Το έργο GNU</h2>
 
@@ -1159,7 +1165,7 @@
 <!-- timestamp start -->
 Ενημερώθηκε:
 
-$Date: 2012/04/26 16:32:57 $
+$Date: 2012/07/15 08:27:04 $
 
 <!-- timestamp end -->
 </p>

Index: philosophy/words-to-avoid.de.html
===================================================================
RCS file: /web/www/www/philosophy/words-to-avoid.de.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- philosophy/words-to-avoid.de.html   3 Jul 2012 16:49:04 -0000       1.9
+++ philosophy/words-to-avoid.de.html   15 Jul 2012 08:27:33 -0000      1.10
@@ -78,7 +78,7 @@
 
 <p>
 Wir glauben, dass der einzige ethische Weg, um Software zu vertreiben, Freie
-Software ist. Daher wollen wir Freie Software zu mehr als eine Alternative
+Software ist. Daher wollen wir Freie Software zu mehr als einer Alternative
 machen. Unser Ziel ist eine Welt, in der alle Programme <em>frei</em> sind,
 damit alle ihre Nutzer frei sind.
 </p>
@@ -155,8 +155,8 @@
 
 <p>
 Eine weitere Bedeutung ist die Anmietung eines physischen Remoteservers oder
-eines virtuellen Servers. Diese können unter bestimmten Umständen in
-Ordnung.sein.
+eines virtuellen Servers. Diese können unter bestimmten Umständen in Ordnung
+sein.
 </p>
 
 <h4 id="Commercial"><em>Kommerziell</em></h4>
@@ -220,7 +220,7 @@
 mit. Diese tendieren dazu, Gedanken zu verzerren.</p>
 <p>
 Softwarenutzer darüber hinaus als <em>Konsumenten</em> oder
-<em>Verbraucher</em> zu beschreiben, geht von einer geringfügige Rolle aus:
+<em>Verbraucher</em> zu beschreiben, geht von einer geringfügigen Rolle aus:
 es lässt sie wie Schafe aussehen, die passiv auf dem weiden, was ihnen
 andere anbieten.</p>
 <p>
@@ -818,7 +818,7 @@
 <!-- timestamp start -->
 Aktualisierung:
 
-$Date: 2012/07/03 16:49:04 $
+$Date: 2012/07/15 08:27:33 $
 
 <!-- timestamp end -->
 </p>

Index: philosophy/po/why-free.translist
===================================================================
RCS file: /web/www/www/philosophy/po/why-free.translist,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- philosophy/po/why-free.translist    11 Mar 2012 11:49:57 -0000      1.4
+++ philosophy/po/why-free.translist    15 Jul 2012 08:27:56 -0000      1.5
@@ -56,6 +56,8 @@
 <li><a href="/philosophy/why-free.ta.html">தமிழ்</a>&nbsp;[ta]</li>
 <!-- Turkish -->
 <li><a href="/philosophy/why-free.tr.html">Türkçe</a>&nbsp;[tr]</li>
+<!-- Chinese (Traditional) -->
+<li><a 
href="/philosophy/why-free.zh-tw.html">繁體中文</a>&nbsp;[zh-tw]</li>
 </ul>
 </div> <!-- id="translations" -->
 <div class="netscape4" id="skiptrans"></div>

Index: philosophy/po/why-free.zh-tw.po
===================================================================
RCS file: /web/www/www/philosophy/po/why-free.zh-tw.po,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- philosophy/po/why-free.zh-tw.po     15 Jul 2012 06:23:43 -0000      1.2
+++ philosophy/po/why-free.zh-tw.po     15 Jul 2012 08:27:56 -0000      1.3
@@ -6,20 +6,25 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: why-free.html\n"
-"POT-Creation-Date: 2012-06-11 14:25-0300\n"
+"POT-Creation-Date: 2012-06-10 04:29-0300\n"
 "PO-Revision-Date: 2012-07-11 16:48+0800\n"
 "Last-Translator: Karl Lam <address@hidden>\n"
 "Language-Team: GNUCTT <address@hidden>\n"
+"Language: \n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
 
 #. type: Content of: <title>
-msgid "Why Software Should Not Have Owners - GNU Project - Free Software 
Foundation (FSF)"
+msgid ""
+"Why Software Should Not Have Owners - GNU Project - Free Software Foundation "
+"(FSF)"
 msgstr "為甚麽軟體不應有主人 - GNU項目 - 自由軟體基金會 
(FSF)"
 
 #. type: Attribute 'content' of: <meta>
-msgid "GNU, GNU Project, FSF, Free Software, Free Software Foundation, Why 
Software Should Not Have Owners"
+msgid ""
+"GNU, GNU Project, FSF, Free Software, Free Software Foundation, Why Software "
+"Should Not Have Owners"
 msgstr "GNU, GNU項目, FSF, 自由軟體, 自由軟體基金會, 
為甚麽軟體不應有主人"
 
 #. type: Content of: <h2>
@@ -27,47 +32,106 @@
 msgstr "為甚麽軟體不應有主人"
 
 #. type: Content of: <p>
-msgid "by <a href=\"http://www.stallman.org/\";><strong>Richard 
Stallman</strong></a>"
-msgstr "作者︰<a href=\"http://www.stallman.org/\";><strong>Richard 
Stallman</strong></a>"
+msgid ""
+"by <a href=\"http://www.stallman.org/\";><strong>Richard Stallman</strong></a>"
+msgstr ""
+"作者︰<a href=\"http://www.stallman.org/\";><strong>Richard Stallman</"
+"strong></a>"
 
 #. type: Content of: <p>
-msgid "Digital information technology contributes to the world by making it 
easier to copy and modify information.  Computers promise to make this easier 
for all of us."
+msgid ""
+"Digital information technology contributes to the world by making it easier "
+"to copy and modify information.  Computers promise to make this easier for "
+"all of us."
 msgstr "數碼資訊科技令大眾更容易複製和變更資料。"
 
 #. type: Content of: <p>
-msgid "Not everyone wants it to be easier.  The system of copyright gives 
software programs &ldquo;owners&rdquo;, most of whom aim to withhold software's 
potential benefit from the rest of the public.  They would like to be the only 
ones who can copy and modify the software that we use."
-msgstr 
"然而不是所有人都希望這樣。版權制度容許軟體有「主人」。他們主要目的在於從å
…
¬çœ¾å¥ªå–軟體的潛在利益。他們希望獨佔這些軟體的複製、更改權利。"
-
-#. type: Content of: <p>
-msgid "The copyright system grew up with printing&mdash;a technology for 
mass-production copying.  Copyright fit in well with this technology because it 
restricted only the mass producers of copies.  It did not take freedom away 
from readers of books.  An ordinary reader, who did not own a printing press, 
could copy books only with pen and ink, and few readers were sued for that."
-msgstr 
"版權制度隨著印刷技術而發展--印刷是一種大量製作副本的技術。版權很適合這é
 …技術,因
為它只限制了大規模的複製。它並沒有剝奪圖書讀者
的自由。一般讀者
沒有印刷機,他們只能用筆墨抄寫作品,所以很少有讀者因
此而被控告。"
-
-#. type: Content of: <p>
-msgid "Digital technology is more flexible than the printing press: when 
information has digital form, you can easily copy it to share it with others.  
This very flexibility makes a bad fit with a system like copyright.  That's the 
reason for the increasingly nasty and draconian measures now used to enforce 
software copyright.  Consider these four practices of the Software Publishers 
Association (SPA):"
-msgstr "數碼科技比印刷機更靈活:當信息呈數碼形式時,你
能很容易把它跟別人分享。這種情況不太配合故
有的版權制度,所以現在有越來越多日益嚴厲的措施用來加
強軟體版權。看看這些軟體出版商協會(Software Publishers 
Association, SPA)的四種慣常說法:"
+msgid ""
+"Not everyone wants it to be easier.  The system of copyright gives software "
+"programs &ldquo;owners&rdquo;, most of whom aim to withhold software's "
+"potential benefit from the rest of the public.  They would like to be the "
+"only ones who can copy and modify the software that we use."
+msgstr ""
+"然而不是所有人都希望這樣。版權制度容許軟體有「主人」。他們主要目的在於從å
…¬çœ¾"
+"奪取軟體的潛在利益。他們希望獨佔這些軟體的複製、更改權利。"
+
+#. type: Content of: <p>
+msgid ""
+"The copyright system grew up with printing&mdash;a technology for mass-"
+"production copying.  Copyright fit in well with this technology because it "
+"restricted only the mass producers of copies.  It did not take freedom away "
+"from readers of books.  An ordinary reader, who did not own a printing "
+"press, could copy books only with pen and ink, and few readers were sued for "
+"that."
+msgstr ""
+"版權制度隨著印刷技術而發展--印刷是一種大量製作副本的技術。版權很適合這é
 …技"
+"術,因為它只限制了大規模的複製。它並沒有剝奪圖書讀者
的自由。一般讀者沒有印刷"
+"機,他們只能用筆墨抄寫作品,所以很少有讀者因
此而被控告。"
+
+#. type: Content of: <p>
+msgid ""
+"Digital technology is more flexible than the printing press: when "
+"information has digital form, you can easily copy it to share it with "
+"others.  This very flexibility makes a bad fit with a system like "
+"copyright.  That's the reason for the increasingly nasty and draconian "
+"measures now used to enforce software copyright.  Consider these four "
+"practices of the Software Publishers Association (SPA):"
+msgstr ""
+"數碼科技比印刷機更靈活:當信息呈數碼形式時,你
能很容易把它跟別人分享。這種情"
+"況不太配合故
有的版權制度,所以現在有越來越多日益嚴厲的措施用來加
強軟體版權。"
+"看看這些軟體出版商協會(Software Publishers Association, 
SPA)的四種慣常說"
+"法:"
 
 #. type: Content of: <ul><li>
-msgid "Massive propaganda saying it is wrong to disobey the owners to help 
your friend."
+msgid ""
+"Massive propaganda saying it is wrong to disobey the owners to help your "
+"friend."
 msgstr "大肆宣傳違反版權法去幫助朋友是錯誤的。"
 
 #. type: Content of: <ul><li>
-msgid "Solicitation for stool pigeons to inform on their coworkers and 
colleagues."
+msgid ""
+"Solicitation for stool pigeons to inform on their coworkers and colleagues."
 msgstr "誘使大家告發違返規定的同事和同僚。"
 
 #. type: Content of: <ul><li>
-msgid "Raids (with police help) on offices and schools, in which people are 
told they must prove they are innocent of illegal copying."
+msgid ""
+"Raids (with police help) on offices and schools, in which people are told "
+"they must prove they are innocent of illegal copying."
 msgstr "如果警察協助突擊搜查公司和學校,那裡的人們必é 
ˆè­‰æ˜Žè‡ªå·±æ²’有非法複製。"
 
 #. type: Content of: <ul><li>
-msgid "Prosecution (by the US government, at the SPA's request) of people such 
as <acronym title=\"Massachusetts Institute of Technology\">MIT</acronym>'s 
David LaMacchia, not for copying software (he is not accused of copying any), 
but merely for leaving copying facilities unguarded and failing to censor their 
use.<a href=\"#footnote1\">[1]</a>"
-msgstr "因
軟體出版商協會提出要求,美國政府起訴一些如麻省理工學院的
 David LaMacchia的人,不是因為他非法軟複製件,而只是因
為沒有升級他的複製工å…
·ï¼Œå¾žè€Œä¸èƒ½å°ç”¨æˆ¶éžæ³•è¤‡è£½è»Ÿé«”進行檢查。<a 
href=\"#footnote1\">[1]</a>"
-
-#. type: Content of: <p>
-msgid "All four practices resemble those used in the former Soviet Union, 
where every copying machine had a guard to prevent forbidden copying, and where 
individuals had to copy information secretly and pass it from hand to hand as 
samizdat.  There is of course a difference: the motive for information control 
in the Soviet Union was political; in the US the motive is profit.  But it is 
the actions that affect us, not the motive.  Any attempt to block the sharing 
of information, no matter why, leads to the same methods and the same 
harshness."
-msgstr "這些æ…
£å¸¸èªªæ³•å’Œå‰è˜‡è¯æ›¾ç”¨éŽçš„做法相似,在每一台影印機前都有一個守衛,以防止那些未經許可複印,同時個人只有秘密地複製信息,並像「秘密出版物」<a
 href=\"#trans1\">[按1]</a>一樣在手é 
­å‚³æ’­ã€‚不同的是,蘇聯管制信息是政治原因
,而美國則是為了經濟利益。無論動機如何,我們都受到影響。不管什麼原å›
 ï¼Œä»»ä½•äººä¼åœ–阻止信息å…
±äº«ï¼Œéƒ½å°Žè‡´äº†ç›¸åŒçš„後果和同樣的不便。"
-
-#. type: Content of: <p>
-msgid "Owners make several kinds of arguments for giving them the power to 
control how we use information:"
+msgid ""
+"Prosecution (by the US government, at the SPA's request) of people such as "
+"<acronym title=\"Massachusetts Institute of Technology\">MIT</acronym>'s "
+"David LaMacchia, not for copying software (he is not accused of copying "
+"any), but merely for leaving copying facilities unguarded and failing to "
+"censor their use.<a href=\"#footnote1\">[1]</a>"
+msgstr ""
+"因
軟體出版商協會提出要求,美國政府起訴一些如麻省理工學院的
 David LaMacchia的"
+"人,不是因為他非法軟複製件,而只是因
為沒有升級他的複製工具,從而不能對用戶非"
+"法複製軟體進行檢查。<a href=\"#footnote1\">[1]</a>"
+
+#. type: Content of: <p>
+msgid ""
+"All four practices resemble those used in the former Soviet Union, where "
+"every copying machine had a guard to prevent forbidden copying, and where "
+"individuals had to copy information secretly and pass it from hand to hand "
+"as samizdat.  There is of course a difference: the motive for information "
+"control in the Soviet Union was political; in the US the motive is profit.  "
+"But it is the actions that affect us, not the motive.  Any attempt to block "
+"the sharing of information, no matter why, leads to the same methods and the "
+"same harshness."
+msgstr ""
+"這些æ…
£å¸¸èªªæ³•å’Œå‰è˜‡è¯æ›¾ç”¨éŽçš„做法相似,在每一台影印機前都有一個守衛,以防止那"
+"些未經許可複印,同時個人只有秘密地複製信息,並像「秘密出版物」<a
 href="
+"\"#trans1\">[按1]</a>一樣在手é 
­å‚³æ’­ã€‚不同的是,蘇聯管制信息是政治原因,而美國"
+"則是為了經濟利益。無論動機如何,我們都受到影響。不管什麼原å›
 ï¼Œä»»ä½•äººä¼åœ–阻止"
+"信息共享,都導致了相同的後果和同樣的不便。"
+
+#. type: Content of: <p>
+msgid ""
+"Owners make several kinds of arguments for giving them the power to control "
+"how we use information:"
 msgstr "軟體所有者
用各種理由來控制我們如何使用資訊的權利︰"
 
 #. type: Content of: <ul><li>
@@ -75,152 +139,358 @@
 msgstr "中傷"
 
 #. type: Content of: <ul><li><p>
-msgid "Owners use smear words such as &ldquo;piracy&rdquo; and 
&ldquo;theft&rdquo;, as well as expert terminology such as &ldquo;intellectual 
property&rdquo; and &ldquo;damage&rdquo;, to suggest a certain line of thinking 
to the public&mdash;a simplistic analogy between programs and physical objects."
-msgstr "軟體所有者
使用「盜竊」、「剽竊」這類帶有誣衊的詞語,或者
「知識產權」、「損害」之類專業的術語,向å…
¬çœ¾æš—示他們是合理的--å…
¶å¯¦ï¼Œä»–們是將軟體和真實物件混為一談。"
-
-#. type: Content of: <ul><li><p>
-msgid "Our ideas and intuitions about property for material objects are about 
whether it is right to <em>take an object away</em> from someone else.  They 
don't directly apply to <em>making a copy</em> of something.  But the owners 
ask us to apply them anyway."
-msgstr "我們對「拿取別人的物件」的概念 
,並不能直接套用在複製這件事,然而軟體所有者
卻迫使我們必須接受他們的想法。"
+msgid ""
+"Owners use smear words such as &ldquo;piracy&rdquo; and &ldquo;theft&rdquo;, "
+"as well as expert terminology such as &ldquo;intellectual property&rdquo; "
+"and &ldquo;damage&rdquo;, to suggest a certain line of thinking to the "
+"public&mdash;a simplistic analogy between programs and physical objects."
+msgstr ""
+"軟體所有者
使用「盜竊」、「剽竊」這類帶有誣衊的詞語,或者
「知識產權」、「損"
+"害」之類專業的術語,向公眾暗示他們是合理的--å…
¶å¯¦ï¼Œä»–們是將軟體和真實物件混"
+"為一談。"
+
+#. type: Content of: <ul><li><p>
+msgid ""
+"Our ideas and intuitions about property for material objects are about "
+"whether it is right to <em>take an object away</em> from someone else.  They "
+"don't directly apply to <em>making a copy</em> of something.  But the owners "
+"ask us to apply them anyway."
+msgstr ""
+"我們對「拿取別人的物件」的概念 
,並不能直接套用在複製這件事,然而軟體所有者卻"
+"迫使我們必須接受他們的想法。"
 
 #. type: Content of: <ul><li>
 msgid "Exaggeration."
 msgstr "憑空誇大"
 
 #. type: Content of: <ul><li><p>
-msgid "Owners say that they suffer &ldquo;harm&rdquo; or &ldquo;economic 
loss&rdquo; when users copy programs themselves.  But the copying has no direct 
effect on the owner, and it harms no one.  The owner can lose only if the 
person who made the copy would otherwise have paid for one from the owner."
-msgstr "軟體所有者
聲稱當用戶複製他們的程序時,他們受到「傷害」或「經濟損失」。但複製並不會對軟體所有è€
…造成直接的影響,也沒有傷害到任何人。只有在使用複製者
不願意給軟體所有者付費時,軟體所有者才會受損失。"
-
-#. type: Content of: <ul><li><p>
-msgid "A little thought shows that most such people would not have bought 
copies.  Yet the owners compute their &ldquo;losses&rdquo; as if each and every 
one would have bought a copy.  That is exaggeration&mdash;to put it kindly."
-msgstr 
"很明顯大多數這樣的人不願意購買這些程式,但是軟體所有è€
…
會假定所有人都會購買,並以此來計算他們的「損失」。客氣點說這就是誇大了專有軟體的價值。"
+msgid ""
+"Owners say that they suffer &ldquo;harm&rdquo; or &ldquo;economic "
+"loss&rdquo; when users copy programs themselves.  But the copying has no "
+"direct effect on the owner, and it harms no one.  The owner can lose only if "
+"the person who made the copy would otherwise have paid for one from the "
+"owner."
+msgstr ""
+"軟體所有者
聲稱當用戶複製他們的程序時,他們受到「傷害」或「經濟損失」。但複製"
+"並不會對軟體所有者造
成直接的影響,也沒有傷害到任何人。只有在使用複製者
不願意"
+"給軟體所有者付費時,軟體所有者才會受損失。"
+
+#. type: Content of: <ul><li><p>
+msgid ""
+"A little thought shows that most such people would not have bought copies.  "
+"Yet the owners compute their &ldquo;losses&rdquo; as if each and every one "
+"would have bought a copy.  That is exaggeration&mdash;to put it kindly."
+msgstr ""
+"很明顯大多數這樣的人不願意購買這些程式,但是軟體所有è€
…會假定所有人都會購買,"
+"並以此來計算他們的「損失」。客氣點說這就是誇大了專有軟體的價值。"
 
 #. type: Content of: <ul><li>
 msgid "The law."
 msgstr "法律"
 
 #. type: Content of: <ul><li><p>
-msgid "Owners often describe the current state of the law, and the harsh 
penalties they can threaten us with.  Implicit in this approach is the 
suggestion that today's law reflects an unquestionable view of 
morality&mdash;yet at the same time, we are urged to regard these penalties as 
facts of nature that can't be blamed on anyone."
-msgstr "軟體所有者經常引用當今的法律和苛刻的刑罰來威脅
我們。這暗示現今的法律反映
了一個不容置疑的道德觀念,同時æ…
«æ¿æˆ‘們視這些刑罰為正常及不能推卸。"
+msgid ""
+"Owners often describe the current state of the law, and the harsh penalties "
+"they can threaten us with.  Implicit in this approach is the suggestion that "
+"today's law reflects an unquestionable view of morality&mdash;yet at the "
+"same time, we are urged to regard these penalties as facts of nature that "
+"can't be blamed on anyone."
+msgstr ""
+"軟體所有者經常引用當今的法律和苛刻的刑罰來威脅
我們。這暗示現今的法律反映了一"
+"個不容置疑的道德觀念,同時æ…
«æ¿æˆ‘們視這些刑罰為正常及不能推卸。"
 
 #. type: Content of: <ul><li><p>
-msgid "This line of persuasion isn't designed to stand up to critical 
thinking; it's intended to reinforce a habitual mental pathway."
+msgid ""
+"This line of persuasion isn't designed to stand up to critical thinking; "
+"it's intended to reinforce a habitual mental pathway."
 msgstr "這些說詞面對嚴謹的思維是站不住è…
³çš„,這做法只是打算利用了人的慣性思維。"
 
 #. type: Content of: <ul><li><p>
-msgid "It's elementary that laws don't decide right and wrong.  Every American 
should know that, in the 1950s, it was against the law in many states for a 
black person to sit in the front of a bus; but only racists would say sitting 
there was wrong."
-msgstr 
"顯然法律是不能決定錯對的。美國人都應該知道,五十年代的黑人在許多州份坐在巴士前座是違法的;但只有種族主義è€
…才會說他們是錯誤的。"
+msgid ""
+"It's elementary that laws don't decide right and wrong.  Every American "
+"should know that, in the 1950s, it was against the law in many states for a "
+"black person to sit in the front of a bus; but only racists would say "
+"sitting there was wrong."
+msgstr ""
+"顯然法律是不能決定錯對的。美國人都應該知道,五十年代的黑人在許多州份坐在巴士"
+"前座是違法的;但只有種族主義者才會說他們是錯誤的。"
 
 #. type: Content of: <ul><li>
 msgid "Natural rights."
 msgstr "自然權利"
 
 #. type: Content of: <ul><li><p>
-msgid "Authors often claim a special connection with programs they have 
written, and go on to assert that, as a result, their desires and interests 
concerning the program simply outweigh those of anyone else&mdash;or even those 
of the whole rest of the world.  (Typically companies, not authors, hold the 
copyrights on software, but we are expected to ignore this discrepancy.)"
-msgstr "軟體作者
常常聲稱與自己編寫的程式有一種特殊聯繫,因
此他們宣稱對這個程序的渴望和興趣是高於世上任何人。(通常是å
…¬å¸æŒæœ‰è»Ÿé«”版權,而不是作者,但是我們é 
æœŸå¿½ç•¥é€™å€‹å·®ç•°ã€‚)"
-
-#. type: Content of: <ul><li><p>
-msgid "To those who propose this as an ethical axiom&mdash;the author is more 
important than you&mdash;I can only say that I, a notable software author 
myself, call it bunk."
-msgstr "對那些打算把「作者
高於一切」推崇為一種道德的人,本人作為一個著名的軟體開發è€
…,只能說這是廢話。"
-
-#. type: Content of: <ul><li><p>
-msgid "But people in general are only likely to feel any sympathy with the 
natural rights claims for two reasons."
+msgid ""
+"Authors often claim a special connection with programs they have written, "
+"and go on to assert that, as a result, their desires and interests "
+"concerning the program simply outweigh those of anyone else&mdash;or even "
+"those of the whole rest of the world.  (Typically companies, not authors, "
+"hold the copyrights on software, but we are expected to ignore this "
+"discrepancy.)"
+msgstr ""
+"軟體作者常常聲稱與自己編寫的程式有一種特殊聯繫,因
此他們宣稱對這個程序的渴望"
+"和興趣是高於世上任何人。(通常是å…
¬å¸æŒæœ‰è»Ÿé«”版權,而不是作者,但是我們預期忽"
+"略這個差異。)"
+
+#. type: Content of: <ul><li><p>
+msgid ""
+"To those who propose this as an ethical axiom&mdash;the author is more "
+"important than you&mdash;I can only say that I, a notable software author "
+"myself, call it bunk."
+msgstr ""
+"對那些打算把「作者
高於一切」推崇為一種道德的人,本人作為一個著名的軟體開發"
+"者,只能說這是廢話。"
+
+#. type: Content of: <ul><li><p>
+msgid ""
+"But people in general are only likely to feel any sympathy with the natural "
+"rights claims for two reasons."
 msgstr "但一般人有兩個原因對自然權利的說法產生共鳴。"
 
 #. type: Content of: <ul><li><p>
-msgid "One reason is an overstretched analogy with material objects.  When I 
cook spaghetti, I do object if someone else eats it, because then I cannot eat 
it.  His action hurts me exactly as much as it benefits him; only one of us can 
eat the spaghetti, so the question is, which one? The smallest distinction 
between us is enough to tip the ethical balance."
-msgstr "第一個原因
是將軟體與現實事物過分地類比。當我做意大利麵時,如果å…
¶ä»–人也要吃,我一定會反感,因
為那樣的話,我就吃不上了。他的行為對我造
成的損失,正如他得到的利益一樣。我們中僅
有一人可以吃意大利麵,問題是誰來吃?我們兩者
之間最小的分歧也足以打破道德上的平衡。"
-
-#. type: Content of: <ul><li><p>
-msgid "But whether you run or change a program I wrote affects you directly 
and me only indirectly.  Whether you give a copy to your friend affects you and 
your friend much more than it affects me.  I shouldn't have the power to tell 
you not to do these things.  No one should."
-msgstr "問題是︰你會否因
為運行或修改一個我寫的程序而直接影響到你
,而對我只會產生一點間接影響?你會否複製我的軟體給你
的朋友,而對你們的影響遠
比對我的還要大?我不應有這樣的權利去叫你
不要這麼做。任何人都不該有。"
-
-#. type: Content of: <ul><li><p>
-msgid "The second reason is that people have been told that natural rights for 
authors is the accepted and unquestioned tradition of our society."
+msgid ""
+"One reason is an overstretched analogy with material objects.  When I cook "
+"spaghetti, I do object if someone else eats it, because then I cannot eat "
+"it.  His action hurts me exactly as much as it benefits him; only one of us "
+"can eat the spaghetti, so the question is, which one? The smallest "
+"distinction between us is enough to tip the ethical balance."
+msgstr ""
+"第一個原因
是將軟體與現實事物過分地類比。當我做意大利麵時,如果å…
¶ä»–人也要吃,"
+"我一定會反感,因
為那樣的話,我就吃不上了。他的行為對我造
成的損失,正如他得到"
+"的利益一樣。我們中僅
有一人可以吃意大利麵,問題是誰來吃?我們兩者
之間最小的分"
+"歧也足以打破道德上的平衡。"
+
+#. type: Content of: <ul><li><p>
+msgid ""
+"But whether you run or change a program I wrote affects you directly and me "
+"only indirectly.  Whether you give a copy to your friend affects you and "
+"your friend much more than it affects me.  I shouldn't have the power to "
+"tell you not to do these things.  No one should."
+msgstr ""
+"問題是︰你會否因
為運行或修改一個我寫的程序而直接影響到你
,而對我只會產生一點"
+"間接影響?你會否複製我的軟體給你的朋友,而對你
們的影響遠比對我的還要大?我不"
+"應有這樣的權利去叫你不要這麼做。任何人都不該有。"
+
+#. type: Content of: <ul><li><p>
+msgid ""
+"The second reason is that people have been told that natural rights for "
+"authors is the accepted and unquestioned tradition of our society."
 msgstr "這第二個原因就是,人們被告知作者
的自然權利是社會約定俗成的準則。"
 
 #. type: Content of: <ul><li><p>
-msgid "As a matter of history, the opposite is true.  The idea of natural 
rights of authors was proposed and decisively rejected when the US Constitution 
was drawn up.  That's why the Constitution only <em>permits</em> a system of 
copyright and does not <em>require</em> one; that's why it says that copyright 
must be temporary.  It also states that the purpose of copyright is to promote 
progress&mdash;not to reward authors.  Copyright does reward authors somewhat, 
and publishers more, but that is intended as a means of modifying their 
behavior."
-msgstr 
"歷史證明,相反的一方才是正確的。當年起草美國憲法時堅
決駁回了關於作者自然權利的提議。這就是為什麼憲法只是å…
è¨±ç‰ˆæ¬Šé«”系,而並不強制要求;所以說版權體制一定是臨時的。憲法也說明版權體制的目的是促進發展,而不是獎勵作è€
…。版權確實給作者
和出版社帶來了更多收益,但這本來只是一種激勵他們的手段而已。"
-
-#. type: Content of: <ul><li><p>
-msgid "The real established tradition of our society is that copyright cuts 
into the natural rights of the public&mdash;and that this can only be justified 
for the public's sake."
-msgstr "事實是我們的社會建立了削弱å…
¬çœ¾è‡ªç„¶æ¬Šåˆ©çš„版權制度。然而版權只有用於å…
¬ç›Šäº‹æ¥­æ‰æ˜¯æ­£ç•¶çš„。"
+msgid ""
+"As a matter of history, the opposite is true.  The idea of natural rights of "
+"authors was proposed and decisively rejected when the US Constitution was "
+"drawn up.  That's why the Constitution only <em>permits</em> a system of "
+"copyright and does not <em>require</em> one; that's why it says that "
+"copyright must be temporary.  It also states that the purpose of copyright "
+"is to promote progress&mdash;not to reward authors.  Copyright does reward "
+"authors somewhat, and publishers more, but that is intended as a means of "
+"modifying their behavior."
+msgstr ""
+"歷史證明,相反的一方才是正確的。當年起草美國憲法時堅
決駁回了關於作者自然權利"
+"的提議。這就是為什麼憲法只是å…
è¨±ç‰ˆæ¬Šé«”系,而並不強制要求;所以說版權體制一定是"
+"臨時的。憲法也說明版權體制的目的是促進發展,而不是獎勵作è€
…。版權確實給作者和"
+"出版社帶來了更多收益,但這本來只是一種激勵他們的手段而已。"
+
+#. type: Content of: <ul><li><p>
+msgid ""
+"The real established tradition of our society is that copyright cuts into "
+"the natural rights of the public&mdash;and that this can only be justified "
+"for the public's sake."
+msgstr ""
+"事實是我們的社會建立了削弱å…
¬çœ¾è‡ªç„¶æ¬Šåˆ©çš„版權制度。然而版權只有用於公益事業才"
+"是正當的。"
 
 #. type: Content of: <ul><li>
 msgid "Economics."
 msgstr "經濟"
 
 #. type: Content of: <ul><li><p>
-msgid "The final argument made for having owners of software is that this 
leads to production of more software."
+msgid ""
+"The final argument made for having owners of software is that this leads to "
+"production of more software."
 msgstr 
"軟體應該有主人的最終辯解理由是,這會提高軟體產量。"
 
 #. type: Content of: <ul><li><p>
-msgid "Unlike the others, this argument at least takes a legitimate approach 
to the subject.  It is based on a valid goal&mdash;satisfying the users of 
software.  And it is empirically clear that people will produce more of 
something if they are well paid for doing so."
-msgstr 
"這個論據至少比以上的更切合主題。它立足於一個合理目標——滿足軟體用戶的需求。以經驗看來,人們å›
 ç‚ºæ»¿æ„çš„回報而生產更多,是很容易理解的。"
-
-#. type: Content of: <ul><li><p>
-msgid "But the economic argument has a flaw: it is based on the assumption 
that the difference is only a matter of how much money we have to pay.  It 
assumes that <em>production of software</em> is what we want, whether the 
software has owners or not."
-msgstr 
"但是這個關於經濟的論據有瑕疵:它基於這樣一個假設,區別åƒ
…僅是我們要付多少錢的問題。它假設無論軟體是否有å…
¶æ‰€æœ‰è€…,「軟體產品」都是我們想要的。"
-
-#. type: Content of: <ul><li><p>
-msgid "People readily accept this assumption because it accords with our 
experiences with material objects.  Consider a sandwich, for instance.  You 
might well be able to get an equivalent sandwich either gratis or for a price.  
If so, the amount you pay is the only difference.  Whether or not you have to 
buy it, the sandwich has the same taste, the same nutritional value, and in 
either case you can only eat it once.  Whether you get the sandwich from an 
owner or not cannot directly affect anything but the amount of money you have 
afterwards."
-msgstr 
"由於這個假設合乎我們處理真實物件的經驗,所以人們很樂意接受。假設ä½
 ä»˜è²»èˆ‡å¦éƒ½èƒ½å¾—到一份一樣的三明治,這樣你
付的費用就是唯一的分別。不管你
是否購買,三明治有相同的味道和相同的營養,但你
只能吃一次。不管你是否從所有者
手中得到三明治,它都不能直接影響到你
的金錢以外的任何事情。"
-
-#. type: Content of: <ul><li><p>
-msgid "This is true for any kind of material object&mdash;whether or not it 
has an owner does not directly affect what it <em>is</em>, or what you can do 
with it if you acquire it."
-msgstr 
"對任何真實物件,這都是正確的︰不管它是否有主人都不會直接影響它的本質和用途。"
-
-#. type: Content of: <ul><li><p>
-msgid "But if a program has an owner, this very much affects what it is, and 
what you can do with a copy if you buy one.  The difference is not just a 
matter of money.  The system of owners of software encourages software owners 
to produce something&mdash;but not what society really needs.  And it causes 
intangible ethical pollution that affects us all."
-msgstr "如果程式有了主人,這將大大影響它的本質,和你
對它的用途。不同之處不僅僅
是錢的問題。軟體該有主人的體制鼓勵軟體主人生產,但不一定是社會真正需要的。它導致的道德低落影響我們所有人。"
-
-#. type: Content of: <p>
-msgid "What does society need? It needs information that is truly available to 
its citizens&mdash;for example, programs that people can read, fix, adapt, and 
improve, not just operate.  But what software owners typically deliver is a 
black box that we can't study or change."
-msgstr "社會需要什麼?社會需要對å…
¬æ°‘真實可用的信息──例如,人們可以解讀、修補、使用和改進的程式,而不只是操作。但是軟體主人往往會給我們一個不能ç
 ”究和修改的黑盒子。"
-
-#. type: Content of: <p>
-msgid "Society also needs freedom.  When a program has an owner, the users 
lose freedom to control part of their own lives."
+msgid ""
+"Unlike the others, this argument at least takes a legitimate approach to the "
+"subject.  It is based on a valid goal&mdash;satisfying the users of "
+"software.  And it is empirically clear that people will produce more of "
+"something if they are well paid for doing so."
+msgstr ""
+"這個論據至少比以上的更切合主題。它立足於一個合理目標——滿足軟體用戶的需求。以"
+"經驗看來,人們因為滿意的回å 
±è€Œç”Ÿç”¢æ›´å¤šï¼Œæ˜¯å¾ˆå®¹æ˜“理解的。"
+
+#. type: Content of: <ul><li><p>
+msgid ""
+"But the economic argument has a flaw: it is based on the assumption that the "
+"difference is only a matter of how much money we have to pay.  It assumes "
+"that <em>production of software</em> is what we want, whether the software "
+"has owners or not."
+msgstr ""
+"但是這個關於經濟的論據有瑕疵:它基於這樣一個假設,區別åƒ
…僅是我們要付多少錢的"
+"問題。它假設無論軟體是否有其所有者
,「軟體產品」都是我們想要的。"
+
+#. type: Content of: <ul><li><p>
+msgid ""
+"People readily accept this assumption because it accords with our "
+"experiences with material objects.  Consider a sandwich, for instance.  You "
+"might well be able to get an equivalent sandwich either gratis or for a "
+"price.  If so, the amount you pay is the only difference.  Whether or not "
+"you have to buy it, the sandwich has the same taste, the same nutritional "
+"value, and in either case you can only eat it once.  Whether you get the "
+"sandwich from an owner or not cannot directly affect anything but the amount "
+"of money you have afterwards."
+msgstr ""
+"由於這個假設合乎我們處理真實物件的經驗,所以人們很樂意接受。假設ä½
 ä»˜è²»èˆ‡å¦éƒ½"
+"能得到一份一樣的三明治,這樣你
付的費用就是唯一的分別。不管你是否購買,三明治"
+"有相同的味道和相同的營養,但你只能吃一次。不管你
是否從所有者手中得到三明治,"
+"它都不能直接影響到你的金錢以外的任何事情。"
+
+#. type: Content of: <ul><li><p>
+msgid ""
+"This is true for any kind of material object&mdash;whether or not it has an "
+"owner does not directly affect what it <em>is</em>, or what you can do with "
+"it if you acquire it."
+msgstr ""
+"對任何真實物件,這都是正確的︰不管它是否有主人都不會直接影響它的本質和用途。"
+
+#. type: Content of: <ul><li><p>
+msgid ""
+"But if a program has an owner, this very much affects what it is, and what "
+"you can do with a copy if you buy one.  The difference is not just a matter "
+"of money.  The system of owners of software encourages software owners to "
+"produce something&mdash;but not what society really needs.  And it causes "
+"intangible ethical pollution that affects us all."
+msgstr ""
+"如果程式有了主人,這將大大影響它的本質,和你
對它的用途。不同之處不僅僅是錢的"
+"問題。軟體該有主人的體制鼓勵軟體主人生產,但不一定是社會真正需要的。它導致的"
+"道德低落影響我們所有人。"
+
+#. type: Content of: <p>
+msgid ""
+"What does society need? It needs information that is truly available to its "
+"citizens&mdash;for example, programs that people can read, fix, adapt, and "
+"improve, not just operate.  But what software owners typically deliver is a "
+"black box that we can't study or change."
+msgstr ""
+"社會需要什麼?社會需要對å…
¬æ°‘真實可用的信息──例如,人們可以解讀、修補、使用和"
+"改進的程式,而不只是操作。但是軟體主人往往會給我們一個不能ç
 ”究和修改的黑盒"
+"子。"
+
+#. type: Content of: <p>
+msgid ""
+"Society also needs freedom.  When a program has an owner, the users lose "
+"freedom to control part of their own lives."
 msgstr 
"社會也需要自由。當程式有了主人,用戶就失去了控制他們部分生活的自由。"
 
 #. type: Content of: <p>
-msgid "And, above all, society needs to encourage the spirit of voluntary 
cooperation in its citizens.  When software owners tell us that helping our 
neighbors in a natural way is &ldquo;piracy&rdquo;, they pollute our society's 
civic spirit."
-msgstr "總之社會需要鼓勵å…
¬æ°‘們自主合作的精神。當軟體主人告訴我們用這種自然的方式幫助旁人是剽竊行為時,那他們就是玷污我們的人æ
 ¼ã€‚"
-
-#. type: Content of: <p>
-msgid "This is why we say that <a href=\"/philosophy/free-sw.html\">free 
software</a> is a matter of freedom, not price."
-msgstr "這正是我們提倡<a 
href=\"/philosophy/free-sw.html\">自由軟體</a> 事關自由,而並非價æ 
¼çš„原因。"
-
-#. type: Content of: <p>
-msgid "The economic argument for owners is erroneous, but the economic issue 
is real.  Some people write useful software for the pleasure of writing it or 
for admiration and love; but if we want more software than those people write, 
we need to raise funds."
-msgstr "支持所有者
的經濟論據是錯誤的,但是經濟問題確實存在。一些人出於榮譽、認同和博愛,而編寫了有用的軟體,但是如果我們希望有更多的軟體,就需要籌集資金。"
-
-#. type: Content of: <p>
-msgid "Since the 1980s, free software developers have tried various methods of 
finding funds, with some success.  There's no need to make anyone rich; a 
typical income is plenty of incentive to do many jobs that are less satisfying 
than programming."
-msgstr "自由軟體開發者自從å…
«åå¹´ä»£å˜—試過許多尋求財源的方法,稍有小成。我們不需要讓任何人置富,å
…¸åž‹çš„收入,足以吸引人做很多比編程少滿足感的工作。"
-
-#. type: Content of: <p>
-msgid "For years, until a fellowship made it unnecessary, I made a living from 
custom enhancements of the free software I had written.  Each enhancement was 
added to the standard released version and thus eventually became available to 
the general public.  Clients paid me so that I would work on the enhancements 
they wanted, rather than on the features I would otherwise have considered 
highest priority."
-msgstr "多年以來,我一直靠
改進自己編寫的自由軟體為生,直到獲得ç 
”究經費。每次改進我都會添加
到標準發佈版本,使得大眾受益。客戶為我付費,這樣我就會優å
…ˆå®Œæˆä»–們需求,自己的變成次要。"
-
-#. type: Content of: <p>
-msgid "Some free software developers make money by selling support services.  
In 1994, Cygnus Support, with around 50 employees, estimated that about 15 
percent of its staff activity was free software development&mdash;a respectable 
percentage for a software company."
-msgstr "一些自由軟體開發者通過支援服務賺錢。1994年,Cygnus 
有近50個員工,估計有大約百分之十五的員工從事自由軟體開發︰對一間軟體å
…¬å¸è€Œè¨€ï¼Œé€™æ˜¯å€‹äº†ä¸èµ·çš„比例。"
-
-#. type: Content of: <p>
-msgid "In the early 1990s, companies including Intel, Motorola, Texas 
Instruments and Analog Devices combined to fund the continued development of 
the GNU C compiler.  Most GCC development is still done by paid developers.  
The GNU compiler for the Ada language was funded in the 90s by the US Air 
Force, and continued since then by a company formed specifically for the 
purpose."
-msgstr "九十年代,Intel、Motorola、Texas Instruments 和 Analog Devices 
等公司聯合贊助持續發展的GNU 
C語言編譯器。現在大部份開發GCC的人工作還是受薪的開發者
完成的。GNU的Ada語言編譯器受美國空軍贊助,之後成立專屬å…
¬å¸å»¶çºŒéŽå€‹é …目。"
-
-#. type: Content of: <p>
-msgid "The free software movement is still small, but the example of 
listener-supported radio in the US shows it's possible to support a large 
activity without forcing each user to pay."
-msgstr "自由軟體運動的規模還是很小,但是靠
聽眾支持的美國電台的例子說明,不用強迫每個用戶付費也可以支撐一個巨大的活動。"
-
-#. type: Content of: <p>
-msgid "As a computer user today, you may find yourself using a <a 
href=\"/philosophy/categories.html#ProprietarySoftware\">proprietary</a> 
program.  If your friend asks to make a copy, it would be wrong to refuse.  
Cooperation is more important than copyright.  But underground, closet 
cooperation does not make for a good society.  A person should aspire to live 
an upright life openly with pride, and this means saying no to proprietary 
software."
-msgstr "今天如果你發現用了<a 
href=\"/philosophy/categories.html#ProprietarySoftware\">專有軟體</a>。如果ä½
 çš„朋友問你
複製一份,拒絕是不對的。合作比版權更重要。私下傳播也不能建立健康的社會。人應當自豪的嚮往開放而正直的生活,這就意味著應該對專有軟體說「不」。"
-
-#. type: Content of: <p>
-msgid "You deserve to be able to cooperate openly and freely with other people 
who use software.  You deserve to be able to learn how the software works, and 
to teach your students with it.  You deserve to be able to hire your favorite 
programmer to fix it when it breaks."
-msgstr "你應該能與其他軟體使用者開放、自由地合作,能夠
學習軟體如何運作,並教導學生,能夠
在軟體出問題時請中意的程式員修復它。"
+msgid ""
+"And, above all, society needs to encourage the spirit of voluntary "
+"cooperation in its citizens.  When software owners tell us that helping our "
+"neighbors in a natural way is &ldquo;piracy&rdquo;, they pollute our "
+"society's civic spirit."
+msgstr ""
+"總之社會需要鼓勵å…
¬æ°‘們自主合作的精神。當軟體主人告訴我們用這種自然的方式幫助"
+"旁人是剽竊行為時,那他們就是玷污我們的人格。"
+
+#. type: Content of: <p>
+msgid ""
+"This is why we say that <a href=\"/philosophy/free-sw.html\">free software</"
+"a> is a matter of freedom, not price."
+msgstr ""
+"這正是我們提倡<a href=\"/philosophy/free-sw.html\">自由軟體</a> 
事關自由,而"
+"並非價格的原因。"
+
+#. type: Content of: <p>
+msgid ""
+"The economic argument for owners is erroneous, but the economic issue is "
+"real.  Some people write useful software for the pleasure of writing it or "
+"for admiration and love; but if we want more software than those people "
+"write, we need to raise funds."
+msgstr ""
+"支持所有者
的經濟論據是錯誤的,但是經濟問題確實存在。一些人出於榮譽、認同和博"
+"愛,而編寫了有用的軟體,但是如果我們希望有更多的軟體,就需要籌集資金。"
+
+#. type: Content of: <p>
+msgid ""
+"Since the 1980s, free software developers have tried various methods of "
+"finding funds, with some success.  There's no need to make anyone rich; a "
+"typical income is plenty of incentive to do many jobs that are less "
+"satisfying than programming."
+msgstr ""
+"自由軟體開發者自從å…
«åå¹´ä»£å˜—試過許多尋求財源的方法,稍有小成。我們不需要讓任"
+"何人置富,典型的收å…
¥ï¼Œè¶³ä»¥å¸å¼•äººåšå¾ˆå¤šæ¯”編程少滿足感的工作。"
+
+#. type: Content of: <p>
+msgid ""
+"For years, until a fellowship made it unnecessary, I made a living from "
+"custom enhancements of the free software I had written.  Each enhancement "
+"was added to the standard released version and thus eventually became "
+"available to the general public.  Clients paid me so that I would work on "
+"the enhancements they wanted, rather than on the features I would otherwise "
+"have considered highest priority."
+msgstr ""
+"多年以來,我一直靠
改進自己編寫的自由軟體為生,直到獲得ç 
”究經費。每次改進我都"
+"會添加
到標準發佈版本,使得大眾受益。客戶為我付費,這樣我就會優å
…ˆå®Œæˆä»–們需"
+"求,自己的變成次要。"
+
+#. type: Content of: <p>
+msgid ""
+"Some free software developers make money by selling support services.  In "
+"1994, Cygnus Support, with around 50 employees, estimated that about 15 "
+"percent of its staff activity was free software development&mdash;a "
+"respectable percentage for a software company."
+msgstr ""
+"一些自由軟體開發者通過支援服務賺錢。1994年,Cygnus 
有近50個員工,估計有大約百"
+"分之十五的員工從事自由軟體開發︰對一間軟體å…
¬å¸è€Œè¨€ï¼Œé€™æ˜¯å€‹äº†ä¸èµ·çš„比例。"
+
+#. type: Content of: <p>
+msgid ""
+"In the early 1990s, companies including Intel, Motorola, Texas Instruments "
+"and Analog Devices combined to fund the continued development of the GNU C "
+"compiler.  Most GCC development is still done by paid developers.  The GNU "
+"compiler for the Ada language was funded in the 90s by the US Air Force, and "
+"continued since then by a company formed specifically for the purpose."
+msgstr ""
+"九十年代,Intel、Motorola、Texas Instruments 和 Analog Devices 等å…
¬å¸è¯åˆè´ŠåŠ©"
+"持續發展的GNU 
C語言編譯器。現在大部份開發GCC的人工作還是受薪的開發者
完成的。"
+"GNU的Ada語言編譯器受美國空軍贊助,之後成立專屬å…
¬å¸å»¶çºŒéŽå€‹é …目。"
+
+#. type: Content of: <p>
+msgid ""
+"The free software movement is still small, but the example of listener-"
+"supported radio in the US shows it's possible to support a large activity "
+"without forcing each user to pay."
+msgstr ""
+"自由軟體運動的規模還是很小,但是靠
聽眾支持的美國電台的例子說明,不用強迫每個"
+"用戶付費也可以支撐一個巨大的活動。"
+
+#. type: Content of: <p>
+msgid ""
+"As a computer user today, you may find yourself using a <a href=\"/"
+"philosophy/categories.html#ProprietarySoftware\">proprietary</a> program.  "
+"If your friend asks to make a copy, it would be wrong to refuse.  "
+"Cooperation is more important than copyright.  But underground, closet "
+"cooperation does not make for a good society.  A person should aspire to "
+"live an upright life openly with pride, and this means saying no to "
+"proprietary software."
+msgstr ""
+"今天如果你發現用了<a 
href=\"/philosophy/categories.html#ProprietarySoftware"
+"\">專有軟體</a>。如果你的朋友問你
複製一份,拒絕是不對的。合作比版權更重要。私"
+"下傳播也不能建立健康的社會。人應當自豪的嚮往開放而正直的生活,這就意味著應該"
+"對專有軟體說「不」。"
+
+#. type: Content of: <p>
+msgid ""
+"You deserve to be able to cooperate openly and freely with other people who "
+"use software.  You deserve to be able to learn how the software works, and "
+"to teach your students with it.  You deserve to be able to hire your "
+"favorite programmer to fix it when it breaks."
+msgstr ""
+"你應該能與其他軟體使用者開放、自由地合作,能夠
學習軟體如何運作,並教導學生,"
+"能夠在軟體出問題時請中意的程式員修復它。"
 
 #. type: Content of: <p>
 msgid "You deserve free software."
@@ -235,33 +505,64 @@
 msgstr "這項指控後來徹銷了"
 
 #. type: Content of: <h4>
-msgid "This essay is published in <a 
href=\"http://shop.fsf.org/product/free-software-free-society/\";><cite>Free 
Software, Free Society: The Selected Essays of Richard M. Stallman</cite></a>."
-msgstr "本文的英文版刊登於<a 
href=\"http://shop.fsf.org/product/free-software-free-society/\";><cite>Free 
Software, Free Society: The Selected Essays of Richard M. 
Stallman</cite></a>。"
+msgid ""
+"This essay is published in <a href=\"http://shop.fsf.org/product/free-";
+"software-free-society/\"><cite>Free Software, Free Society: The Selected "
+"Essays of Richard M. Stallman</cite></a>."
+msgstr ""
+"本文的英文版刊登於<a 
href=\"http://shop.fsf.org/product/free-software-free-";
+"society/\"><cite>Free Software, Free Society: The Selected Essays of Richard "
+"M. Stallman</cite></a>。"
 
 #. TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.
 #. type: Content of: <div>
 msgid "*GNUN-SLOT: TRANSLATOR'S NOTES*"
-msgstr "<p>譯者按︰</p><ol><li 
id=\"trans1\">俄語:самиздат,蘇聯政府有思想審查,禁止的刊物就是é
 é€™ç¨®æ–¹å¼å‚³æ’­ï¼Œè©³æƒ…可參照<a 
href=\"http://zh.wikipedia.org/zh-tw/%E7%A7%98%E5%AF%86%E5%87%BA%E7%89%88%E7%89%A9\";>維基百科條目︰秘密出版物</a></li></ol>"
+msgstr ""
+"<p>譯者按︰</p><ol><li 
id=\"trans1\">俄語:самиздат,蘇聯政府有思想審查,禁止"
+"的刊物就是靠這種方式傳播,詳情可參照<a 
href=\"http://zh.wikipedia.org/zh-tw/";
+"%E7%A7%98%E5%AF%86%E5%87%BA%E7%89%88%E7%89%A9\">維基百科條目︰秘密出版物</"
+"a></li></ol>"
 
 #. type: Content of: <div><p>
-msgid "Please send 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."
-msgstr "請來郵 <a 
href=\"mailto:address@hidden";>&lt;address@hidden&gt;</a>查詢「自由軟體基金會」及「GNU
 計畫」的事宜。或者<a href=\"/contact/\">透過å…
¶ä»–方式</a>聯絡自由軟體基金會。"
+msgid ""
+"Please send 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."
+msgstr ""
+"請來郵 <a 
href=\"mailto:address@hidden";>&lt;address@hidden&gt;</a>查詢「自由軟體基"
+"金會」及「GNU 計畫」的事宜。或者<a href=\"/contact/\">透過å…
¶ä»–方式</a>聯絡自"
+"由軟體基金會。"
 
 #. type: Content of: <div><p>
-msgid "Please send broken links and other corrections or suggestions to <a 
href=\"mailto:address@hidden";>&lt;address@hidden&gt;</a>."
-msgstr "請來郵<a 
href=\"mailto:address@hidden";>&lt;address@hidden&gt;</a>告訴我們任何失效的連結、錯誤和建議。"
+msgid ""
+"Please send broken links and other corrections or suggestions to <a href="
+"\"mailto:address@hidden";>&lt;address@hidden&gt;</a>."
+msgstr ""
+"請來郵<a href=\"mailto:address@hidden";>&lt;address@hidden&gt;</a>告"
+"訴我們任何失效的連結、錯誤和建議。"
 
 #. type: Content of: <div><p>
-msgid "Please see the <a 
href=\"/server/standards/README.translations.html\">Translations README</a> for 
information on coordinating and submitting translations of this article."
-msgstr "請參照 <a 
href=\"/server/standards/README.translations.html\">翻譯說明</a> 
了解有關協助翻譯本文的事情。"
+msgid ""
+"Please see the <a href=\"/server/standards/README.translations.html"
+"\">Translations README</a> for information on coordinating and submitting "
+"translations of this article."
+msgstr ""
+"請參照 <a 
href=\"/server/standards/README.translations.html\">翻譯說明</a> 了"
+"解有關協助翻譯本文的事情。"
 
 #. type: Content of: <div><p>
 msgid "Copyright &copy; 1994, 2009 Richard Stallman"
 msgstr "版權所有 &copy; 1994, 2009 Richard Stallman"
 
 #. type: Content of: <div><p>
-msgid "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>."
-msgstr "本頁面採用 <a rel=\"license\" 
href=\"http://creativecommons.org/licenses/by-nd/3.0/us/\";>Creative Commons 
Attribution-NoDerivs 3.0 United States License</a> 許可證授權。"
+msgid ""
+"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>."
+msgstr ""
+"本頁面採用 <a rel=\"license\" 
href=\"http://creativecommons.org/licenses/by-";
+"nd/3.0/us/\">Creative Commons Attribution-NoDerivs 3.0 United States "
+"License</a> 許可證授權。"
 
 #. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.
 #. type: Content of: <div><div>
@@ -272,4 +573,3 @@
 #. type: Content of: <div><p>
 msgid "Updated:"
 msgstr "更新時間︰"
-

Index: philosophy/po/words-to-avoid.de-en.html
===================================================================
RCS file: /web/www/www/philosophy/po/words-to-avoid.de-en.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -b -r1.9 -r1.10
--- philosophy/po/words-to-avoid.de-en.html     3 Jul 2012 16:49:41 -0000       
1.9
+++ philosophy/po/words-to-avoid.de-en.html     15 Jul 2012 08:27:56 -0000      
1.10
@@ -782,7 +782,7 @@
 <p>
 Updated:
 <!-- timestamp start -->
-$Date: 2012/07/03 16:49:41 $
+$Date: 2012/07/15 08:27:56 $
 <!-- timestamp end -->
 </p>
 </div>

Index: gnu/po/thegnuproject.el-diff.html
===================================================================
RCS file: gnu/po/thegnuproject.el-diff.html
diff -N gnu/po/thegnuproject.el-diff.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ gnu/po/thegnuproject.el-diff.html   15 Jul 2012 08:27:22 -0000      1.1
@@ -0,0 +1,1114 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
+<!-- Generated by GNUN -->
+<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
+<head>
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<title>/gnu/thegnuproject.html-diff</title>
+<style type="text/css">
+span.removed { background-color: #f22; color: #000; }
+span.inserted { background-color: #2f2; color: #000; }
+</style></head>
+<body><pre>
+&lt;!--#include virtual="/server/header.html" --&gt;
+
+&lt;title&gt;About the GNU Project - GNU Project - Free Software Foundation 
(FSF)&lt;/title&gt;
+
+&lt;meta http-equiv="Keywords" content="GNU, GNU Project, FSF, Free Software, 
Free Software Foundation, History" /&gt;
+
+&lt;!--#include virtual="/server/banner.html" --&gt;
+&lt;!--#include virtual="/gnu/po/thegnuproject.translist" --&gt;
+
+&lt;h2&gt;The GNU Project&lt;/h2&gt;
+
+&lt;!-- This document uses XHTML 1.0 Strict, but may be served as --&gt;
+&lt;!-- text/html.  Please ensure that markup style considers --&gt;
+&lt;!-- appendex C of the XHTML 1.0 standard. See validator.w3.org. --&gt;
+
+&lt;!-- Please ensure links are consistent with Apache's MultiView. --&gt;
+&lt;!-- Change include statements to be consistent with the relevant --&gt;
+&lt;!-- language, where necessary. --&gt;
+
+&lt;p&gt;
+by &lt;a href="http://www.stallman.org/"&gt;&lt;strong&gt;Richard 
Stallman&lt;/strong&gt;&lt;/a&gt;&lt;/p&gt;
+&lt;p&gt;
+the original version was published in the book &ldquo;Open 
Sources&rdquo;&lt;/p&gt;
+
+
+&lt;h3&gt;The first software-sharing community&lt;/h3&gt;
+&lt;p&gt;
+When I started working at the 
+&lt;acronym title="Massachusetts Institute of 
Technology"&gt;MIT&lt;/acronym&gt;
+Artificial Intelligence Lab in 1971, I became part of a
+software-sharing community that had existed for many years.  Sharing
+of software was not limited to our particular community; it is as old
+as computers, just as sharing of recipes is as old as cooking.  But we
+did it more than most.&lt;/p&gt;
+&lt;p&gt;
+The AI Lab used a timesharing operating system called
+&lt;acronym title="Incompatible Timesharing System"&gt;ITS&lt;/acronym&gt; (the
+Incompatible Timesharing System) that the lab's staff hackers (1) had
+designed and written in assembler language for the Digital
+&lt;acronym title="Programmed Data Processor"&gt;PDP&lt;/acronym&gt;-10, one of
+the large computers of the era.  As a member of this community, an AI
+Lab staff system hacker, my job was to improve this system.&lt;/p&gt;
+&lt;p&gt;
+We did not call our software &ldquo;free software&rdquo;, because that
+term did not yet exist; but that is what it was.  Whenever people from
+another university or a company wanted to port and use a program, we
+gladly let them.  If you saw someone using an unfamiliar and
+interesting program, you could always ask to see the source code, so
+that you could read it, change it, or cannibalize parts of it to make
+a new program.&lt;/p&gt;
+&lt;p&gt;
+(1) The use of &ldquo;hacker&rdquo; to mean &ldquo;security
+breaker&rdquo; is a confusion on the part of the mass media.  We
+hackers refuse to recognize that meaning, and continue using the word
+to mean someone who loves to program, someone who enjoys playful
+cleverness, or the combination of the two.  See my
+article, &lt;a href="http://stallman.org/articles/on-hacking.html"&gt;On
+Hacking&lt;/a&gt;.&lt;/p&gt;
+
+&lt;h3&gt;The collapse of the community&lt;/h3&gt;
+&lt;p&gt;
+The situation changed drastically in the early 1980s when Digital
+discontinued the PDP-10 series.  Its architecture, elegant and
+powerful in the 60s, could not extend naturally to the larger address
+spaces that were becoming feasible in the 80s.  This meant that nearly
+all of the programs composing ITS were obsolete.&lt;/p&gt;
+&lt;p&gt;
+The AI Lab hacker community had already collapsed, not long before.
+In 1981, the spin-off company Symbolics had hired away nearly all of
+the hackers from the AI Lab, and the depopulated community was unable
+to maintain itself.  (The book Hackers, by Steve Levy, describes these
+events, as well as giving a clear picture of this community in its
+prime.)  When the AI Lab bought a new PDP-10 in 1982, its
+administrators decided to use Digital's nonfree timesharing system
+instead of ITS.&lt;/p&gt;
+&lt;p&gt;
+The modern computers of the era, such as the VAX or the 68020, had
+their own operating systems, but none of them were free software: you
+had to sign a nondisclosure agreement even to get an executable copy.&lt;/p&gt;
+&lt;p&gt;
+This meant that the first step in using a computer was to promise not
+to help your neighbor.  A cooperating community was forbidden.  The
+rule made by the owners of proprietary software was, &ldquo;If you
+share with your neighbor, you are a pirate.  If you want any changes,
+beg us to make them.&rdquo;&lt;/p&gt;
+&lt;p&gt;
+The idea that the proprietary software social system&mdash;the system
+that says you are not allowed to share or change software&mdash;is
+antisocial, that it is unethical, that it is simply wrong, may come as
+a surprise to some readers.  But what else could we say about a system
+based on dividing the public and keeping users helpless?  Readers who
+find the idea surprising may have taken the proprietary software
+social system as a given, or judged it on the terms suggested by
+proprietary software businesses.  Software publishers have worked long
+and hard to convince people that there is only one way to look at the
+issue.&lt;/p&gt;
+&lt;p&gt;
+When software publishers talk about &ldquo;enforcing&rdquo; their
+&ldquo;rights&rdquo; or &ldquo;stopping &lt;a 
href="/philosophy/words-to-avoid.html#Piracy"&gt;piracy&lt;/a&gt;&rdquo;, what 
they
+actually &lt;em&gt;say&lt;/em&gt; is secondary.  The real message of these 
statements is
+in the unstated assumptions they take for granted, which the public is
+asked to accept without examination.  Let's therefore examine them.&lt;/p&gt;
+&lt;p&gt;
+One assumption is that software companies have an unquestionable natural
+right to own software and thus have power over all its users.  (If
+this were a natural right, then no matter how much harm it does to the
+public, we could not object.)  Interestingly, the US Constitution and
+legal tradition reject this view; copyright is not a natural right,
+but an artificial government-imposed monopoly that limits the users'
+natural right to copy.&lt;/p&gt;
+&lt;p&gt;
+Another unstated assumption is that the only important thing about
+software is what jobs it allows you to do&mdash;that we computer users
+should not care what kind of society we are allowed to have.&lt;/p&gt;
+&lt;p&gt;
+A third assumption is that we would have no usable software (or would
+never have a program to do this or that particular job) if we did not
+offer a company power over the users of the program.  This assumption
+may have seemed plausible, before the free software movement
+demonstrated that we can make plenty of useful software without
+putting chains on it.&lt;/p&gt;
+&lt;p&gt;
+If we decline to accept these assumptions, and judge these issues
+based on ordinary commonsense morality while placing the users first,
+we arrive at very different conclusions.  Computer users should be
+free to modify programs to fit their needs, and free to share
+software, because helping other people is the basis of society.&lt;/p&gt;
+&lt;p&gt;
+There is no room here for an extensive statement of the reasoning
+behind this conclusion, so I refer the reader to the web page,
+&lt;a href="/philosophy/why-free.html"&gt;
+http://www.gnu.org/philosophy/why-free.html&lt;/a&gt;.&lt;/p&gt;
+
+&lt;h3&gt;A stark moral choice.&lt;/h3&gt;
+&lt;p&gt;
+With my community gone, to continue as before was impossible.
+Instead, I faced a stark moral choice.&lt;/p&gt;
+&lt;p&gt;
+The easy choice was to join the proprietary software world, signing
+nondisclosure agreements and promising not to help my fellow hacker.
+Most likely I would also be developing software that was released
+under nondisclosure agreements, thus adding to the pressure on other
+people to betray their fellows too.&lt;/p&gt;
+&lt;p&gt;
+I could have made money this way, and perhaps amused myself writing
+code.  But I knew that at the end of my career, I would look back on
+years of building walls to divide people, and feel I had spent my life
+making the world a worse place.&lt;/p&gt;
+&lt;p&gt;
+I had already experienced being on the receiving end of a
+nondisclosure agreement, when someone refused to give me and the MIT
+AI Lab the source code for the control program for our printer.  (The
+lack of certain features in this program made use of the printer
+extremely frustrating.)  So I could not tell myself that nondisclosure
+agreements were innocent.  I was very angry when he refused to share
+with us; I could not turn around and do the same thing to everyone
+else.&lt;/p&gt;
+&lt;p&gt;
+Another choice, straightforward but unpleasant, was to leave the
+computer field.  That way my skills would not be misused, but they
+would still be wasted.  I would not be culpable for dividing and
+restricting computer users, but it would happen nonetheless.&lt;/p&gt;
+&lt;p&gt;
+So I looked for a way that a programmer could do something for the
+good.  I asked myself, was there a program or programs that I could
+write, so as to make a community possible once again?&lt;/p&gt;
+&lt;p&gt;
+The answer was clear: what was needed first was an operating system.
+That is the crucial software for starting to use a computer.  With an
+operating system, you can do many things; without one, you cannot run
+the computer at all.  With a free operating system, we could again
+have a community of cooperating hackers&mdash;and invite anyone to join.
+And anyone would be able to use a computer without starting out by
+conspiring to deprive his or her friends.&lt;/p&gt;
+&lt;p&gt;
+As an operating system developer, I had the right skills for this job.
+So even though I could not take success for granted, I realized that I
+was elected to do the job.  I chose to make the system compatible with
+Unix so that it would be portable, and so that Unix users could easily
+switch to it.  The name GNU was chosen, following a hacker tradition, as
+a recursive acronym for &ldquo;GNU's Not Unix.&rdquo;&lt;/p&gt;
+&lt;p&gt;
+An operating system does not mean just a kernel, barely enough to run
+other programs.  In the 1970s, every operating system worthy of the
+name included command processors, assemblers, compilers, interpreters,
+debuggers, text editors, mailers, and much more.  ITS had them,
+Multics had them, VMS had them, and Unix had them.  The GNU operating
+system would include them too.&lt;/p&gt;
+&lt;p&gt;
+Later I heard these words, attributed to Hillel (1):&lt;/p&gt;
+
+&lt;blockquote&gt;&lt;p&gt;
+     If I am not for myself, who will be for me?&lt;br /&gt;
+     If I am only for myself, what am I?&lt;br /&gt;
+     If not now, when?
+&lt;/p&gt;&lt;/blockquote&gt;
+&lt;p&gt;
+The decision to start the GNU Project was based on a similar spirit.&lt;/p&gt;
+&lt;p&gt;
+(1) As an Atheist, I don't follow any religious leaders, but I
+sometimes find I admire something one of them has said.&lt;/p&gt;
+
+&lt;h3&gt;Free as in freedom&lt;/h3&gt;
+&lt;p&gt;
+The term &ldquo;free software&rdquo; is sometimes misunderstood&mdash;it
+has nothing to do with price.  It is about freedom.  Here, therefore,
+is the definition of free software.&lt;/p&gt;
+
+&lt;p&gt;A program is free software, for you, a particular user, if:&lt;/p&gt;
+
+&lt;ul&gt;
+  &lt;li&gt;You have the freedom to run the program as you wish, for any 
purpose.&lt;/li&gt;
+
+  &lt;li&gt;You have the freedom to modify the program to suit your needs.
+     (To make this freedom effective in practice, you must have access
+     to the source code, since making changes in a program without
+     having the source code is exceedingly difficult.)&lt;/li&gt;
+
+  &lt;li&gt;You have the freedom to redistribute copies, either gratis
+     or for a fee.&lt;/li&gt;
+
+  &lt;li&gt;You have the freedom to distribute modified versions of the 
program,
+     so that the community can benefit from your improvements.&lt;/li&gt;
+&lt;/ul&gt;
+&lt;p&gt;
+Since &ldquo;free&rdquo; refers to freedom, not to price, there is no
+contradiction between selling copies and free software.  In fact, the
+freedom to sell copies is crucial: collections of free software sold
+on CD-ROMs are important for the community, and selling them is an
+important way to raise funds for free software development.
+Therefore, a program which people are not free to include on these
+collections is not free software.&lt;/p&gt;
+&lt;p&gt;
+Because of the ambiguity of &ldquo;free&rdquo;, people have long
+looked for alternatives, but no one has found a better term.
+The English language has more words and nuances than any other, but it
+lacks a simple, unambiguous, word that means &ldquo;free&rdquo;, as in
+freedom&mdash;&ldquo;unfettered&rdquo; being the word that comes closest in
+meaning.  Such alternatives as &ldquo;liberated&rdquo;,
+&ldquo;freedom&rdquo;, and &ldquo;open&rdquo; have either the wrong
+meaning or some other disadvantage.&lt;/p&gt;
+
+&lt;h3&gt;GNU software and the GNU system&lt;/h3&gt;
+&lt;p&gt;
+Developing a whole system is a very large project.  To bring it into
+reach, I decided to adapt and use existing pieces of free software
+wherever that was possible.  For example, I decided at the very
+beginning to use TeX as the principal text formatter; a few years
+later, I decided to use the X Window System rather than writing
+another window system for GNU.&lt;/p&gt;
+&lt;p&gt;
+Because of this decision, the GNU system is not the same as the
+collection of all
+GNU software.  The GNU system includes programs that are not GNU
+software, programs that were developed by other people and projects
+for their own purposes, but which we can use because they are free
+software.&lt;/p&gt;
+
+&lt;h3&gt;Commencing the project&lt;/h3&gt;
+&lt;p&gt;
+In January 1984 I quit my job at MIT and began writing GNU software.
+Leaving MIT was necessary so that MIT would not be able to interfere
+with distributing GNU as free software.  If I had remained on the
+staff, MIT could have claimed to own the work, and could have imposed
+their own distribution terms, or even turned the work into a
+proprietary software package.  I had no intention of doing a large
+amount of work only to see it become useless for its intended purpose:
+creating a new software-sharing community.&lt;/p&gt;
+&lt;p&gt;
+However, Professor Winston, then the head of the MIT AI Lab, kindly
+invited me to keep using the lab's facilities.&lt;/p&gt;
+
+&lt;h3&gt;The first steps&lt;/h3&gt;
+&lt;p&gt;
+Shortly before beginning the GNU Project, I heard about the Free
+University Compiler Kit, also known as VUCK.  (The Dutch word for
+&ldquo;free&rdquo; is written with a &lt;em&gt;v&lt;/em&gt;.)  This was a 
compiler
+designed to handle multiple languages, including C and Pascal, and to
+support multiple target machines.  I wrote to its author asking if GNU
+could use it.&lt;/p&gt;
+&lt;p&gt;
+He responded derisively, stating that the university was free but the
+compiler was not.  I therefore decided that my first program for the
+GNU Project would be a multilanguage, multiplatform compiler.&lt;/p&gt;
+&lt;p&gt;
+Hoping to avoid the need to write the whole compiler myself, I
+obtained the source code for the Pastel compiler, which was a
+multiplatform compiler developed at Lawrence Livermore Lab.  It
+supported, and was written in, an extended version of Pascal, designed
+to be a system-programming language.  I added a C front end, and began
+porting it to the Motorola 68000 computer.  But I had to give that
+up when I discovered that the compiler needed many megabytes of stack
+space, and the available 68000 Unix system would only allow 64k.&lt;/p&gt;
+&lt;p&gt;
+I then realized that the Pastel compiler functioned by parsing the
+entire input file into a syntax tree, converting the whole syntax tree
+into a chain of &ldquo;instructions&rdquo;, and then generating the
+whole output file, without ever freeing any storage.  At this point, I
+concluded I would have to write a new compiler from scratch.  That new
+compiler is now known as &lt;acronym title="GNU Compiler 
Collection"&gt;GCC&lt;/acronym&gt;;
+none of the Pastel compiler is used in it, but I managed to adapt and
+use the C front end that I had written.  But that was some years
+later; first, I worked on GNU Emacs.&lt;/p&gt;
+
+&lt;h3&gt;GNU Emacs&lt;/h3&gt;
+&lt;p&gt;
+I began work on GNU Emacs in September 1984, and in early 1985 it was
+beginning to be usable.  This enabled me to begin using Unix systems
+to do editing; having no interest in learning to use vi or ed, I had
+done my editing on other kinds of machines until then.&lt;/p&gt;
+&lt;p&gt;
+At this point, people began wanting to use GNU Emacs, which raised the
+question of how to distribute it.  Of course, I put it on the
+anonymous ftp server on the MIT computer that I used.  (This computer,
+prep.ai.mit.edu, thus became the principal GNU ftp distribution site;
+when it was decommissioned a few years later, we transferred the name
+to our new ftp server.)  But at that time, many of the interested
+people were not on the Internet and could not get a copy by ftp.  So
+the question was, what would I say to them?&lt;/p&gt;
+&lt;p&gt;
+I could have said, &ldquo;Find a friend who is on the net and who will make
+a copy for you.&rdquo;  Or I could have done what I did with the original
+PDP-10 Emacs: tell them, &ldquo;Mail me a tape and a
+&lt;acronym title="Self-addressed Stamped Envelope"&gt;SASE&lt;/acronym&gt;, 
and I
+will mail it back with Emacs on it.&rdquo; But I had no job, and I was
+looking for ways to make money from free software.  So I announced
+that I would mail a tape to whoever wanted one, for a fee of $150.  In
+this way, I started a free software distribution business, the
+precursor of the companies that today distribute entire Linux-based
+GNU systems.&lt;/p&gt;
+
+&lt;h3&gt;Is a program free for every user?&lt;/h3&gt;
+&lt;p&gt;
+If a program is free software when it leaves the hands of its author,
+this does not necessarily mean it will be free software for everyone
+who has a copy of it.  For example,
+&lt;a href="/philosophy/categories.html#PublicDomainSoftware"&gt; public domain
+software&lt;/a&gt; (software that is not copyrighted) is free software; but
+anyone can make a proprietary modified version of it.  Likewise, many
+free programs are copyrighted but distributed under simple permissive
+licenses which allow proprietary modified versions.&lt;/p&gt;
+&lt;p&gt;
+The paradigmatic example of this problem is the X Window System.
+Developed at MIT, and released as free software with a permissive
+license, it was soon adopted by various computer companies.  They
+added X to their proprietary Unix systems, in binary form only, and
+covered by the same nondisclosure agreement.  These copies of X were
+no more free software than Unix was.&lt;/p&gt;
+&lt;p&gt;
+The developers of the X Window System did not consider this a
+problem&mdash;they expected and intended this to happen.  Their goal was
+not freedom, just &ldquo;success&rdquo;, defined as &ldquo;having many
+users.&rdquo; They did not care whether these users had freedom, only
+that they should be numerous.&lt;/p&gt;
+&lt;p&gt;
+This led to a paradoxical situation where two different ways of
+counting the amount of freedom gave different answers to the question,
+&ldquo;Is this program free?&rdquo; If you judged based on the freedom
+provided by the distribution terms of the MIT release, you would say
+that X was free software.  But if you measured the freedom of the
+average user of X, you would have to say it was proprietary software.
+Most X users were running the proprietary versions that came with Unix
+systems, not the free version.&lt;/p&gt;
+
+&lt;h3&gt;Copyleft and the GNU GPL&lt;/h3&gt;
+&lt;p&gt;
+The goal of GNU was to give users freedom, not just to be popular.  So
+we needed to use distribution terms that would prevent GNU software
+from being turned into proprietary software.  The method we use is
+called &ldquo;copyleft&rdquo;.(1)&lt;/p&gt;
+&lt;p&gt;
+Copyleft uses copyright law, but flips it over to serve the opposite
+of its usual purpose: instead of a means for restricting a program, it
+becomes a means for keeping the program free.&lt;/p&gt;
+&lt;p&gt;
+The central idea of copyleft is that we give everyone permission to
+run the program, copy the program, modify the program, and distribute
+modified versions&mdash;but not permission to add restrictions of their
+own.  Thus, the crucial freedoms that define &ldquo;free
+software&rdquo; are guaranteed to everyone who has a copy; they become
+inalienable rights.&lt;/p&gt;
+&lt;p&gt;
+For an effective copyleft, modified versions must also be free.  This
+ensures that work based on ours becomes available to our community if
+it is published.  When programmers who have jobs as programmers
+volunteer to improve GNU software, it is copyleft that prevents their
+employers from saying, &ldquo;You can't share those changes, because
+we are going to use them to make our proprietary version of the
+program.&rdquo;&lt;/p&gt;
+&lt;p&gt;
+The requirement that changes must be free is essential if we want to
+ensure freedom for every user of the program.  The companies that
+privatized the X Window System usually made some changes to port it to
+their systems and hardware.  These changes were small compared with
+the great extent of X, but they were not trivial.  If making changes
+were an excuse to deny the users freedom, it would be easy for anyone
+to take advantage of the excuse.&lt;/p&gt;
+&lt;p&gt;
+A related issue concerns combining a free program with nonfree code.
+Such a combination would inevitably be nonfree; whichever freedoms
+are lacking for the nonfree part would be lacking for the whole as
+well.  To permit such combinations would open a hole big enough to
+sink a ship.  Therefore, a crucial requirement for copyleft is to plug
+this hole: anything added to or combined with a copylefted program
+must be such that the larger combined version is also free and
+copylefted.&lt;/p&gt;
+&lt;p&gt;
+The specific implementation of copyleft that we use for most GNU
+software is the GNU General Public License, or GNU GPL for short.  We
+have other kinds of copyleft that are used in specific circumstances.
+GNU manuals are copylefted also, but use a much simpler kind of
+copyleft, because the complexity of the GNU GPL is not necessary
+for manuals.(2)&lt;/p&gt;
+&lt;p&gt;
+(1) In 1984 or 1985, Don Hopkins (a very imaginative fellow) mailed me
+a letter.  On the envelope he had written several amusing sayings,
+including this one: &ldquo;Copyleft&mdash;all rights reversed.&rdquo; I
+used the word &ldquo;copyleft&rdquo; to name the distribution concept
+I was developing at the time.&lt;/p&gt;
+
+&lt;p&gt;
+(2) We now use the &lt;a href="/licenses/fdl.html"&gt;GNU Free
+Documentation License&lt;/a&gt; for documentation.&lt;/p&gt;
+
+&lt;h3&gt;The Free Software Foundation&lt;/h3&gt;
+
+&lt;p&gt;As interest in using Emacs was growing, other people became
+involved in the GNU project, and we decided that it was time to seek
+funding once again.  So in 1985 we created
+the &lt;a href="http://www.fsf.org/"&gt;Free Software Foundation&lt;/a&gt; 
(FSF),
+a tax-exempt charity for free software development.  The
+&lt;acronym title="Free Software Foundation"&gt;FSF&lt;/acronym&gt; also took 
over
+the Emacs tape distribution business; later it extended this by adding
+other free software (both GNU and non-GNU) to the tape, and by selling
+free manuals as well.&lt;/p&gt;
+
+&lt;p&gt;Most of the FSF's income used to come from sales of copies of free
+software and of other related services (CD-ROMs of source code,
+CD-ROMs with binaries, nicely printed manuals, all with the freedom to
+redistribute and modify), and Deluxe Distributions (distributions for
+which we built the whole collection of software for the customer's
+choice of platform).  Today the FSF
+still &lt;a href="http://shop.fsf.org/"&gt; sells manuals and other
+gear&lt;/a&gt;, but it gets the bulk of its funding from members' dues.  You
+can join the FSF at &lt;a 
href="http://fsf.org/join"&gt;fsf.org&lt;/a&gt;.&lt;/p&gt;
+
+&lt;p&gt;Free Software Foundation employees have written and maintained a
+number of GNU software packages.  Two notable ones are the C library
+and the shell.  The GNU C library is what every program running on a
+GNU/Linux system uses to communicate with Linux.  It was developed by
+a member of the Free Software Foundation staff, Roland McGrath.  The
+shell used on most GNU/Linux systems is
+&lt;acronym title="Bourne Again Shell"&gt;BASH&lt;/acronym&gt;, the Bourne 
Again
+Shell(1), which was developed by FSF employee Brian Fox.&lt;/p&gt;
+
+&lt;p&gt;We funded development of these programs because the GNU Project was
+not just about tools or a development environment.  Our goal was a
+complete operating system, and these programs were needed for that
+goal.&lt;/p&gt;
+
+&lt;p&gt;(1) &ldquo;Bourne Again Shell&rdquo; is a play on the name
+&ldquo;Bourne Shell&rdquo;, which was the usual shell on Unix.&lt;/p&gt;
+
+&lt;h3&gt;Free software support&lt;/h3&gt;
+
+&lt;p&gt;The free software philosophy rejects a specific widespread business
+practice, but it is not against business.  When businesses respect the
+users' freedom, we wish them success.&lt;/p&gt;
+
+&lt;p&gt;Selling copies of Emacs demonstrates one kind of free software
+business.  When the FSF took over that business, I needed another way
+to make a living.  I found it in selling services relating to the free
+software I had developed.  This included teaching, for subjects such
+as how to program GNU Emacs and how to customize GCC, and software
+development, mostly porting GCC to new platforms.&lt;/p&gt;
+
+&lt;p&gt;Today each of these kinds of free software business is practiced by a
+number of corporations.  Some distribute free software collections on
+CD-ROM; others sell support at levels ranging from answering user
+questions, to fixing bugs, to adding major new features.  We are even
+beginning to see free software companies based on launching new free
+software products.&lt;/p&gt;
+
+&lt;p&gt;Watch out, though&mdash;a number of companies that associate 
themselves
+with the term &ldquo;open source&rdquo; actually base their business
+on nonfree software that works with free software.  These are not
+free software companies, they are proprietary software companies whose
+products tempt users away from freedom.  They call these programs
+&ldquo;value-added packages&rdquo;, which shows the values they
+would like us to adopt: convenience above freedom.  If we value freedom
+more, we should call them &ldquo;freedom-subtracted&rdquo; packages.&lt;/p&gt;
+
+&lt;h3&gt;Technical goals&lt;/h3&gt;
+
+&lt;p&gt;The principal goal of GNU is to be free software.  Even if GNU had no
+technical advantage over Unix, it would have a social advantage,
+allowing users to cooperate, and an ethical advantage, respecting the
+user's freedom.&lt;/p&gt;
+
+&lt;p&gt;But it was natural to apply the known standards of good practice to
+the work&mdash;for example, dynamically allocating data structures to avoid
+arbitrary fixed size limits, and handling all the possible 8-bit codes
+wherever that made sense.&lt;/p&gt;
+
+&lt;p&gt;In addition, we rejected the Unix focus on small memory size, by
+deciding not to support 16-bit machines (it was clear that 32-bit
+machines would be the norm by the time the GNU system was finished),
+and to make no effort to reduce memory usage unless it exceeded a
+megabyte.  In programs for which handling very large files was not
+crucial, we encouraged programmers to read an entire input file into
+core, then scan its contents without having to worry about I/O.&lt;/p&gt;
+
+&lt;p&gt;These decisions enabled many GNU programs to surpass their Unix
+counterparts in reliability and speed.&lt;/p&gt;
+
+&lt;h3&gt;Donated computers&lt;/h3&gt;
+
+&lt;p&gt;As the GNU Project's reputation grew, people began offering to donate
+machines running Unix to the project.  These were very useful, because
+the easiest way to develop components of GNU was to do it on a Unix
+system, and replace the components of that system one by one.  But
+they raised an ethical issue: whether it was right for us to have a
+copy of Unix at all.&lt;/p&gt;
+
+&lt;p&gt;Unix was (and is) proprietary software, and the GNU Project's
+philosophy said that we should not use proprietary software.  But,
+applying the same reasoning that leads to the conclusion that violence
+in self defense is justified, I concluded that it was legitimate to
+use a proprietary package when that was crucial for developing a free
+replacement that would help others stop using the proprietary 
package.&lt;/p&gt;
+
+&lt;p&gt;But, even if this was a justifiable evil, it was still an evil.  Today
+we no longer have any copies of Unix, because we have replaced them
+with free operating systems.  If we could not replace a machine's
+operating system with a free one, we replaced the machine instead.&lt;/p&gt;
+
+&lt;h3&gt;The GNU Task List&lt;/h3&gt;
+
+&lt;p&gt;As the GNU Project proceeded, and increasing numbers of system
+components were found or developed, eventually it became useful to
+make a list of the remaining gaps.  We used it to recruit developers
+to write the missing pieces.  This list became known as the GNU Task
+List.  In addition to missing Unix components, we listed various
+other useful software and documentation projects that, we thought, a
+truly complete system ought to have.&lt;/p&gt;
+
+&lt;p&gt;Today (1), hardly any Unix components are left in the GNU Task
+List&mdash;those jobs had been done, aside from a few inessential
+ones.  But the list is full of projects that some might call
+&ldquo;applications&rdquo;.  Any program that appeals to more than a
+narrow class of users would be a useful thing to add to an operating
+system.&lt;/p&gt;
+
+&lt;p&gt;Even games are included in the task list&mdash;and have been since the
+beginning.  Unix included games, so naturally GNU should too.  But
+compatibility was not an issue for games, so we did not follow the
+list of games that Unix had.  Instead, we listed a spectrum of
+different kinds of games that users might like.&lt;/p&gt;
+
+&lt;p&gt;(1) That was written in 1998.  In 2009 we no longer maintain a long
+task list.  The community develops free software so fast that we can't
+even keep track of it all.  Instead, we have a list of High Priority
+Projects, a much shorter list of projects we really want to encourage
+people to write.&lt;/p&gt;
+
+&lt;h3&gt;The GNU Library GPL&lt;/h3&gt;
+
+&lt;p&gt;The GNU C library uses a special kind of copyleft called the GNU
+Library General Public License(1), which gives permission to link
+proprietary software with the library.  Why make this exception?&lt;/p&gt;
+
+&lt;p&gt;It is not a matter of principle; there is no principle that says
+proprietary software products are entitled to include our code.  (Why
+contribute to a project predicated on refusing to share with us?)
+Using the LGPL for the C library, or for any library, is a matter of
+strategy.&lt;/p&gt;
+
+&lt;p&gt;The C library does a generic job; every proprietary system or compiler
+comes with a C library.  Therefore, to make our C library available
+only to free software would not have given free software any
+advantage&mdash;it would only have discouraged use of our library.&lt;/p&gt;
+
+&lt;p&gt;One system is an exception to this: on the GNU system (and this
+includes GNU/Linux), the GNU C library is the only C library.  So the
+distribution terms of the GNU C library determine whether it is
+possible to compile a proprietary program for the GNU system.  There
+is no ethical reason to allow proprietary applications on the GNU
+system, but strategically it seems that disallowing them would do more
+to discourage use of the GNU system than to encourage development of
+free applications.  That is why using the Library GPL is a good
+strategy for the C library.&lt;/p&gt;
+
+&lt;p&gt;For other libraries, the strategic decision needs to be
+considered on a case-by-case basis.  When a library does a special job
+that can help write certain kinds of programs, then releasing it under
+the GPL, limiting it to free programs only, is a way of helping other
+free software developers, giving them an advantage against proprietary
+software.&lt;/p&gt;
+
+&lt;p&gt;Consider GNU Readline, a library that was developed to provide
+command-line editing for BASH.  Readline is released under the
+ordinary GNU GPL, not the Library GPL.  This probably does reduce the
+amount Readline is used, but that is no loss for us.  Meanwhile, at
+least one useful application has been made free software specifically
+so it could use Readline, and that is a real gain for the
+community.&lt;/p&gt;
+
+&lt;p&gt;Proprietary software developers have the advantages money provides;
+free software developers need to make advantages for each other.  I
+hope some day we will have a large collection of GPL-covered libraries
+that have no parallel available to proprietary software, providing
+useful modules to serve as building blocks in new free software, and
+adding up to a major advantage for further free software development.&lt;/p&gt;
+
+&lt;p&gt;(1) This license is now called the GNU Lesser General Public License,
+to avoid giving the idea that all libraries ought to use it. 
+See &lt;a href="/philosophy/why-not-lgpl.html"&gt;Why you shouldn't use the
+Lesser GPL for your next library&lt;/a&gt; for more information.&lt;/p&gt;
+
+&lt;h3&gt;Scratching an itch?&lt;/h3&gt;
+&lt;p&gt;
+Eric Raymond says that &ldquo;Every good work of software starts by
+scratching a developer's personal itch.&rdquo;  Maybe that happens
+sometimes, but many essential pieces of GNU software were developed in
+order to have a complete free operating system.  They come from a
+vision and a plan, not from impulse.&lt;/p&gt;
+&lt;p&gt;
+For example, we developed the GNU C library because a Unix-like system
+needs a C library, BASH because a Unix-like
+system needs a shell, and GNU tar because a Unix-like system needs a
+tar program.  The same is true for my own programs&mdash;the GNU C
+compiler, GNU Emacs, GDB and GNU Make.&lt;/p&gt;
+&lt;p&gt;
+Some GNU programs were developed to cope with specific threats to our
+freedom.  Thus, we developed gzip to replace the Compress program,
+which had been lost to the community because of
+the &lt;acronym title="Lempel-Ziv-Welch"&gt;LZW&lt;/acronym&gt; patents.  We 
found
+people to develop LessTif, and more recently started
+&lt;acronym title="GNU Network Object Model 
Environment"&gt;GNOME&lt;/acronym&gt;
+and Harmony, to address the problems caused by certain proprietary
+libraries (see below).  We are developing the GNU Privacy Guard to
+replace popular nonfree encryption software, because users should not
+have to choose between privacy and freedom.&lt;/p&gt;
+&lt;p&gt;
+Of course, the people writing these programs became interested in the
+work, and many features were added to them by various people for the
+sake of their own needs and interests.  But that is not why the
+programs exist.&lt;/p&gt;
+
+&lt;h3&gt;Unexpected developments&lt;/h3&gt;
+&lt;p&gt;
+At the beginning of the GNU Project, I imagined that we would develop
+the whole GNU system, then release it as a whole.  That is not how it
+happened.&lt;/p&gt;
+&lt;p&gt;
+Since each component of the GNU system was implemented on a Unix
+system, each component could run on Unix systems long before a
+complete GNU system existed.  Some of these programs became popular,
+and users began extending them and porting them&mdash;to the various
+incompatible versions of Unix, and sometimes to other systems as 
well.&lt;/p&gt;
+&lt;p&gt;
+The process made these programs much more powerful, and attracted both
+funds and contributors to the GNU Project.  But it probably also
+delayed completion of a minimal working system by several years, as
+GNU developers' time was put into maintaining these ports and adding
+features to the existing components, rather than moving on to write
+one missing component after another.&lt;/p&gt;
+
+&lt;h3&gt;The GNU Hurd&lt;/h3&gt;
+&lt;p&gt;
+By 1990, the GNU system was almost complete; the only major missing
+component was the kernel.  We had decided to implement our kernel as a
+collection of server processes running on top of Mach.  Mach is a
+microkernel developed at Carnegie Mellon University and then at the
+University of Utah; the GNU Hurd is a collection of servers (i.e., a
+herd of GNUs) that run on top of Mach, and do the
+various jobs of the Unix kernel.  The start of development was delayed
+as we waited for Mach to be released as free software, as had been
+promised.&lt;/p&gt;
+&lt;p&gt;
+One reason for choosing this design was to avoid what seemed to be the
+hardest part of the job: debugging a kernel program without a
+source-level debugger to do it with.  This part of the job had been
+done already, in Mach, and we expected to debug the Hurd servers as
+user programs, with GDB.  But it took a long time to make that possible,
+and the multithreaded servers that send messages to each other have
+turned out to be very hard to debug.  Making the Hurd work solidly has
+stretched on for many years.&lt;/p&gt;
+
+&lt;h3&gt;Alix&lt;/h3&gt;
+&lt;p&gt;
+The GNU kernel was not originally supposed to be called the Hurd.  Its
+original name was Alix&mdash;named after the woman who was my sweetheart at
+the time.  She, a Unix system administrator, had pointed out how her
+name would fit a common naming pattern for Unix system versions; as a
+joke, she told her friends, &ldquo;Someone should name a kernel after
+me.&rdquo; I said nothing, but decided to surprise her with a kernel
+named Alix.&lt;/p&gt;
+&lt;p&gt;
+It did not stay that way.  Michael (now Thomas) Bushnell, the main
+developer of the kernel, preferred the name Hurd, and redefined Alix
+to refer to a certain part of the kernel&mdash;the part that would trap
+system calls and handle them by sending messages to Hurd servers.&lt;/p&gt;
+&lt;p&gt;
+Later, Alix and I broke up, and she changed her name;
+independently, the Hurd design was changed so that the C library would
+send messages directly to servers, and this made the Alix component
+disappear from the design.&lt;/p&gt;
+&lt;p&gt;
+But before these things happened, a friend of hers came across the
+name Alix in the Hurd source code, and mentioned it to her.  So
+she did have the chance to find a kernel named after her.&lt;/p&gt;
+
+&lt;h3&gt;Linux and GNU/Linux&lt;/h3&gt;
+&lt;p&gt;
+The GNU Hurd is not suitable for production use, and we don't know
+if it ever will be.  The capability-based design has problems that
+result directly from the flexibility of the design, and it is not
+clear <span class="inserted"><ins><em>whether</em></ins></span> solutions 
exist.&lt;/p&gt;
+
+&lt;p&gt;
+Fortunately, another
+kernel is available.  In 1991, Linus Torvalds developed a
+Unix-compatible kernel and called it Linux.  In 1992, he made Linux
+free software; combining Linux with the not-quite-complete GNU system
+resulted in a complete free operating system.  (Combining them was a
+substantial job in itself, of course.)  It is due to Linux that we can
+actually run a version of the GNU system today.&lt;/p&gt;
+&lt;p&gt;
+We call this system version GNU/Linux, to express its composition as a
+combination of the GNU system with Linux as the kernel.&lt;/p&gt;
+
+&lt;h3&gt;Challenges in our future&lt;/h3&gt;
+&lt;p&gt;
+We have proved our ability to develop a broad spectrum of free
+software.  This does not mean we are invincible and unstoppable.
+Several challenges make the future of free software uncertain; meeting
+them will require steadfast effort and endurance, sometimes lasting
+for years.  It will require the kind of determination that people
+display when they value their freedom and will not let anyone take it
+away.&lt;/p&gt;
+&lt;p&gt;
+The following four sections discuss these challenges.&lt;/p&gt;
+
+&lt;h3&gt;Secret hardware&lt;/h3&gt;
+&lt;p&gt;
+Hardware manufacturers increasingly tend to keep hardware
+specifications secret.  This makes it difficult to write free drivers
+so that Linux and XFree86 can support new hardware.  We have complete
+free systems today, but we will not have them tomorrow if we cannot
+support tomorrow's computers.&lt;/p&gt;
+&lt;p&gt;
+There are two ways to cope with this problem.  Programmers can do
+reverse engineering to figure out how to support the hardware.  The
+rest of us can choose the hardware that is supported by free software;
+as our numbers increase, secrecy of specifications will become a
+self-defeating policy.&lt;/p&gt;
+&lt;p&gt;
+Reverse engineering is a big job; will we have programmers with
+sufficient determination to undertake it?  Yes&mdash;if we have built up a
+strong feeling that free software is a matter of principle, and
+nonfree drivers are intolerable.  And will large numbers of us spend
+extra money, or even a little extra time, so we can use free drivers?
+Yes, if the determination to have freedom is widespread.&lt;/p&gt;
+&lt;p&gt;
+(2008 note: this issue extends to the BIOS as well.
+There is a free BIOS, coreboot; the problem is getting specs
+for machines so that coreboot can support them.)&lt;/p&gt;
+
+&lt;h3&gt;Nonfree libraries&lt;/h3&gt;
+&lt;p&gt;
+A nonfree library that runs on free operating systems acts as a trap
+for free software developers.  The library's attractive features are
+the bait; if you use the library, you fall into the trap, because your
+program cannot usefully be part of a free operating system.  (Strictly
+speaking, we could include your program, but it
+won't &lt;em&gt;run&lt;/em&gt; with the library missing.)  Even worse, if
+a program that uses the proprietary library becomes popular, it can
+lure other unsuspecting programmers into the trap.&lt;/p&gt;
+&lt;p&gt;
+The first instance of this problem was the Motif toolkit, back in the
+80s.  Although there were as yet no free operating systems, it was
+clear what problem Motif would cause for them later on.  The GNU
+Project responded in two ways: by asking individual free software
+projects to support the free X Toolkit widgets as well as Motif, and
+by asking for someone to write a free replacement for Motif.  The job
+took many years; LessTif, developed by the Hungry Programmers, became
+powerful enough to support most Motif applications only in 1997.&lt;/p&gt;
+&lt;p&gt;
+Between 1996 and 1998, another nonfree 
+&lt;acronym title="Graphical User Interface"&gt;GUI&lt;/acronym&gt; toolkit
+library, called Qt, was used in a substantial collection of free
+software, the desktop
+&lt;acronym title="K Desktop Environment"&gt;KDE&lt;/acronym&gt;.&lt;/p&gt;
+&lt;p&gt;
+Free GNU/Linux systems were unable to use KDE, because we could not
+use the library.  However, some commercial distributors of GNU/Linux
+systems who were not strict about sticking with free software added
+KDE to their systems&mdash;producing a system with more capabilities,
+but less freedom.  The KDE group was actively encouraging more
+programmers to use Qt, and millions of new &ldquo;Linux users&rdquo;
+had never been exposed to the idea that there was a problem in this.
+The situation appeared grim.&lt;/p&gt;
+&lt;p&gt;
+The free software community responded to the problem in two ways:
+GNOME and Harmony.&lt;/p&gt;
+&lt;p&gt;
+GNOME, the GNU Network Object Model Environment, is GNU's desktop
+project.  Started in 1997 by Miguel de Icaza, and developed with the
+support of Red Hat Software, GNOME set out to provide similar desktop
+facilities, but using free software exclusively.  It has technical
+advantages as well, such as supporting a variety of languages, not
+just C++.  But its main purpose was freedom: not to require the use of
+any nonfree software.&lt;/p&gt;
+&lt;p&gt;
+Harmony is a compatible replacement library, designed to make it
+possible to run KDE software without using Qt.&lt;/p&gt;
+&lt;p&gt;
+In November 1998, the developers of Qt announced a change of license
+which, when carried out, should make Qt free software.  There is no
+way to be sure, but I think that this was partly due to the
+community's firm response to the problem that Qt posed when it was
+nonfree.  (The new license is inconvenient and inequitable, so it
+remains desirable to avoid using Qt.)&lt;/p&gt;
+&lt;p&gt;
+[Subsequent note: in September 2000, Qt was rereleased under the GNU GPL,
+which essentially solved this problem.]&lt;/p&gt;
+&lt;p&gt;
+How will we respond to the next tempting nonfree library?  Will the
+whole community understand the need to stay out of the trap?  Or will
+many of us give up freedom for convenience, and produce a major
+problem?  Our future depends on our philosophy.&lt;/p&gt;
+
+&lt;h3&gt;Software patents&lt;/h3&gt;
+&lt;p&gt;
+The worst threat we face comes from software patents, which can put
+algorithms and features off limits to free software for up to twenty
+years.  The LZW compression algorithm patents were applied for in
+1983, and we still cannot release free software to produce proper
+compressed &lt;acronym title="Graphics Interchange 
Format"&gt;GIF&lt;/acronym&gt;s.
+[As of 2009 they have expired.]  In 1998, a free program to produce
+&lt;acronym title="MPEG-1 Audio Layer 3"&gt;MP3&lt;/acronym&gt; compressed 
audio
+was removed from distribution under threat of a patent suit.&lt;/p&gt;
+&lt;p&gt;
+There are ways to cope with patents: we can search for evidence that a
+patent is invalid, and we can look for alternative ways to do a job.
+But each of these methods works only sometimes; when both fail, a
+patent may force all free software to lack some feature that users
+want.  What will we do when this happens?&lt;/p&gt;
+&lt;p&gt;
+Those of us who value free software for freedom's sake will stay with
+free software anyway.  We will manage to get work done without the
+patented features.  But those who value free software because they
+expect it to be technically superior are likely to call it a failure
+when a patent holds it back.  Thus, while it is useful to talk about
+the practical effectiveness of the &ldquo;bazaar&rdquo; model of
+development, and the reliability and power of some free software,
+we must not stop there.  We must talk about freedom and principle.&lt;/p&gt;
+
+&lt;h3&gt;Free documentation&lt;/h3&gt;
+&lt;p&gt;
+The biggest deficiency in our free operating systems is not in the
+software&mdash;it is the lack of good free manuals that we can include in
+our systems.  Documentation is an essential part of any software
+package; when an important free software package does not come with a
+good free manual, that is a major gap.  We have many such gaps today.&lt;/p&gt;
+&lt;p&gt;
+Free documentation, like free software, is a matter of freedom, not
+price.  The criterion for a free manual is pretty much the same as for
+free software: it is a matter of giving all users certain freedoms.
+Redistribution (including commercial sale) must be permitted, online
+and on paper, so that the manual can accompany every copy of the
+program.&lt;/p&gt;
+&lt;p&gt;
+Permission for modification is crucial too.  As a general rule, I
+don't believe that it is essential for people to have permission to
+modify all sorts of articles and books.  For example, I don't think
+you or I are obliged to give permission to modify articles like this
+one, which describe our actions and our views.&lt;/p&gt;
+&lt;p&gt;
+But there is a particular reason why the freedom to modify is crucial
+for documentation for free software.  When people exercise their right
+to modify the software, and add or change its features, if they are
+conscientious they will change the manual, too&mdash;so they can
+provide accurate and usable documentation with the modified program.
+A nonfree manual, which does not allow programmers to be conscientious
+and finish the job, does not fill our community's needs.&lt;/p&gt;
+&lt;p&gt;
+Some kinds of limits on how modifications are done pose no problem.
+For example, requirements to preserve the original author's copyright
+notice, the distribution terms, or the list of authors, are OK.  It is
+also no problem to require modified versions to include notice that
+they were modified, even to have entire sections that may not be
+deleted or changed, as long as these sections deal with nontechnical
+topics.  These kinds of restrictions are not a problem because they
+don't stop the conscientious programmer from adapting the manual to
+fit the modified program.  In other words, they don't block the free
+software community from making full use of the manual.&lt;/p&gt;
+&lt;p&gt;
+However, it must be possible to modify all the &lt;em&gt;technical&lt;/em&gt; 
content of
+the manual, and then distribute the result in all the usual media,
+through all the usual channels; otherwise, the restrictions do
+obstruct the community, the manual is not free, and we need another
+manual.&lt;/p&gt;
+&lt;p&gt;
+Will free software developers have the awareness and determination to
+produce a full spectrum of free manuals?  Once again, our future
+depends on philosophy.&lt;/p&gt;
+
+&lt;h3&gt;We must talk about freedom&lt;/h3&gt;
+&lt;p&gt;
+Estimates today are that there are ten million users of GNU/Linux
+systems such as Debian GNU/Linux and Red Hat &ldquo;Linux&rdquo;.
+Free software has developed such practical advantages that users are
+flocking to it for purely practical reasons.&lt;/p&gt;
+&lt;p&gt;
+The good consequences of this are evident: more interest in developing
+free software, more customers for free software businesses, and more
+ability to encourage companies to develop commercial free software
+instead of proprietary software products.&lt;/p&gt;
+&lt;p&gt;
+But interest in the software is growing faster than awareness of the
+philosophy it is based on, and this leads to trouble.  Our ability to
+meet the challenges and threats described above depends on the will to
+stand firm for freedom.  To make sure our community has this will, we
+need to spread the idea to the new users as they come into the
+community.&lt;/p&gt;
+&lt;p&gt;
+But we are failing to do so: the efforts to attract new users into our
+community are far outstripping the efforts to teach them the civics of
+our community.  We need to do both, and we need to keep the two
+efforts in balance.&lt;/p&gt;
+
+&lt;h3&gt;&ldquo;Open Source&rdquo;&lt;/h3&gt;
+&lt;p&gt;
+Teaching new users about freedom became more difficult in 1998, when a
+part of the community decided to stop using the term &ldquo;free
+software&rdquo; and say &ldquo;open source software&rdquo;
+instead.&lt;/p&gt;
+&lt;p&gt;
+Some who favored this term aimed to avoid the confusion of
+&ldquo;free&rdquo; with &ldquo;gratis&rdquo;&mdash;a valid goal.  Others,
+however, aimed to set aside the spirit of principle that had motivated
+the free software movement and the GNU Project, and to appeal instead
+to executives and business users, many of whom hold an ideology that
+places profit above freedom, above community, above principle.  Thus,
+the rhetoric of &ldquo;open source&rdquo; focuses on the potential to
+make high-quality, powerful software, but shuns the ideas of freedom,
+community, and principle.&lt;/p&gt;
+&lt;p&gt;
+The &ldquo;Linux&rdquo; magazines are a clear example of this&mdash;they
+are filled with advertisements for proprietary software that works
+with GNU/Linux.  When the next Motif or Qt appears, will these
+magazines warn programmers to stay away from it, or will they run ads
+for it?&lt;/p&gt;
+&lt;p&gt;
+The support of business can contribute to the community in many ways;
+all else being equal, it is useful.  But winning their support by
+speaking even less about freedom and principle can be disastrous; it
+makes the previous imbalance between outreach and civics education
+even worse.&lt;/p&gt;
+&lt;p&gt;
+&ldquo;Free software&rdquo; and &ldquo;open source&rdquo; describe the
+same category of software, more or less, but say different things
+about the software, and about values.  The GNU Project continues to
+use the term &ldquo;free software&rdquo;, to express the idea that
+freedom, not just technology, is important.&lt;/p&gt;
+
+&lt;h3&gt;Try!&lt;/h3&gt;
+&lt;p&gt;
+Yoda's aphorism (&ldquo;There is no &lsquo;try&rsquo;&rdquo;) sounds
+neat, but it doesn't work for me.  I have done most of my work while
+anxious about whether I could do the job, and unsure that it would be
+enough to achieve the goal if I did.  But I tried anyway, because
+there was no one but me between the enemy and my city.  Surprising
+myself, I have sometimes succeeded.&lt;/p&gt;
+&lt;p&gt;
+Sometimes I failed; some of my cities have fallen.  Then I found
+another threatened city, and got ready for another battle.  Over time,
+I've learned to look for threats and put myself between them and my
+city, calling on other hackers to come and join me.&lt;/p&gt;
+&lt;p&gt;
+Nowadays, often I'm not the only one.  It is a relief and a joy when I
+see a regiment of hackers digging in to hold the line, and I realize,
+this city may survive&mdash;for now.  But the dangers are greater each
+year, and now Microsoft has explicitly targeted our community.  We
+can't take the future of freedom for granted.  Don't take it for
+granted!  If you want to keep your freedom, you must be prepared to
+defend it.&lt;/p&gt;
+
+
+&lt;!-- If needed, change the copyright block at the bottom. In general, --&gt;
+&lt;!-- all pages on the GNU web server should have the section about    --&gt;
+&lt;!-- verbatim copying.  Please do NOT remove this without talking     --&gt;
+&lt;!-- with the webmasters first. --&gt; 
+&lt;!-- Please make sure the copyright date is consistent with the document 
--&gt;
+&lt;!-- and that it is like this "2001, 2002" not this "2001-2002." --&gt;
+
+&lt;/div&gt;
+
+&lt;!--#include virtual="/server/footer.html" --&gt;
+
+&lt;div id="footer"&gt;
+
+&lt;p&gt;
+Please send FSF &amp; GNU inquiries to 
+&lt;a href="mailto:address@hidden"&gt;&lt;address@hidden&gt;&lt;/a&gt;.  There 
are
+also &lt;a href="/contact/"&gt;other ways to contact&lt;/a&gt; the FSF.
+&lt;br /&gt;
+Please send broken links and other corrections or suggestions to
+&lt;a href="mailto:address@hidden"&gt;&lt;address@hidden&gt;&lt;/a&gt;.
+&lt;/p&gt;
+
+&lt;p&gt;
+Please see the 
+&lt;a href="/server/standards/README.translations.html"&gt;Translations
+README&lt;/a&gt; for information on coordinating and submitting
+translations of this article.
+&lt;/p&gt;
+
+&lt;p&gt;
+Copyright &copy; 1998, 2001, 2002, 2005, 2006, 2007, 2008, 2010 Richard 
Stallman
+&lt;br /&gt;
+This page is licensed under a &lt;a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/"&gt;Creative
+Commons Attribution-NoDerivs 3.0 United States License&lt;/a&gt;.
+&lt;/p&gt;
+
+&lt;p&gt;
+Updated:
+&lt;!-- timestamp start --&gt;
+$Date: 2012/07/15 08:27:22 $
+&lt;!-- timestamp end --&gt;
+&lt;/p&gt;
+&lt;/div&gt;
+
+<span class="removed"><del><strong>&lt;!-- &lt;div id="translations"&gt; --&gt;
+&lt;!-- &lt;h4&gt;Translations of this page&lt;/h4&gt; --&gt;
+&lt;!--  --&gt;
+&lt;!--  --&gt;
+&lt;!-- Please keep this list alphabetical by language code. --&gt;
+&lt;!--      Comment what the language is for each type, i.e. de is German. 
--&gt;
+&lt;!--      Write the language name in its own language (Deutsch) in the 
text. --&gt;
+&lt;!--      If you add a new language here, please --&gt;
+&lt;!--      advise address@hidden and add it to --&gt;
+&lt;!--       - /home/www/html/server/standards/README.translations.html --&gt;
+&lt;!--       - one of the lists under the section "Translations Underway" 
--&gt;
+&lt;!--       - if there is a translation team, you also have to add an alias 
--&gt;
+&lt;!--       to mail.gnu.org:/com/mailer/aliases --&gt;
+&lt;!--      Please also check you have the language code right; see: --&gt;
+&lt;!--      http://www.loc.gov/standards/iso639-2/php/code_list.php --&gt;
+&lt;!--      If the 2-letter ISO 639-1 code is not available, --&gt;
+&lt;!--      use the 3-letter ISO 639-2. --&gt;
+&lt;!--      Please use W3C normative character entities. --&gt;
+&lt;!--  --&gt;
+&lt;!-- &lt;ul class="translations-list"&gt; --&gt;
+&lt;!-- Bosnian --&gt;
+&lt;!-- &lt;li&gt;&lt;a 
href="/gnu/thegnuproject.bs.html"&gt;bosanski&lt;/a&gt;&nbsp;[bs]&lt;/li&gt; 
--&gt;
+&lt;!-- Catalan --&gt;
+&lt;!-- &lt;li&gt;&lt;a 
href="/gnu/thegnuproject.ca.html"&gt;catal&#x00e0;&lt;/a&gt;&nbsp;[ca]&lt;/li&gt;
 --&gt;
+&lt;!-- Czech --&gt;
+&lt;!-- &lt;li&gt;&lt;a 
href="/gnu/thegnuproject.cs.html"&gt;&#x010c;esky&lt;/a&gt;&nbsp;[cs]&lt;/li&gt;
 --&gt;
+&lt;!-- German --&gt;
+&lt;!-- &lt;li&gt;&lt;a 
href="/gnu/thegnuproject.de.html"&gt;Deutsch&lt;/a&gt;&nbsp;[de]&lt;/li&gt; 
--&gt;
+&lt;!-- Greek --&gt;
+&lt;!-- &lt;li&gt;&lt;a 
href="/gnu/thegnuproject.el.html"&gt;&#x0395;&#x03bb;&#x03bb;&#x03b7;&#x03bd;&#x03b9;&#x03ba;&#x03ac;&lt;/a&gt;&nbsp;[el]&lt;/li&gt;
 --&gt;
+&lt;!-- English --&gt;
+&lt;!-- &lt;li&gt;&lt;a 
href="/gnu/thegnuproject.html"&gt;English&lt;/a&gt;&nbsp;[en]&lt;/li&gt; --&gt;
+&lt;!-- Spanish --&gt;
+&lt;!-- &lt;li&gt;&lt;a 
href="/gnu/thegnuproject.es.html"&gt;espa&#x00f1;ol&lt;/a&gt;&nbsp;[es]&lt;/li&gt;
 --&gt;
+&lt;!-- Finnish --&gt;
+&lt;!-- &lt;li&gt;&lt;a 
href="/gnu/thegnuproject.fi.html"&gt;suomi&lt;/a&gt;&nbsp;[fi]&lt;/li&gt; --&gt;
+&lt;!-- French --&gt;
+&lt;!-- &lt;li&gt;&lt;a 
href="/gnu/thegnuproject.fr.html"&gt;fran&#x00e7;ais&lt;/a&gt;&nbsp;[fr]&lt;/li&gt;
 --&gt;
+&lt;!-- Indonesian --&gt;
+&lt;!-- &lt;li&gt;&lt;a href="/gnu/thegnuproject.id.html"&gt;Bahasa 
Indonesia&lt;/a&gt;&nbsp;[id]&lt;/li&gt; --&gt;
+&lt;!-- Italian --&gt;
+&lt;!-- &lt;li&gt;&lt;a 
href="/gnu/thegnuproject.it.html"&gt;italiano&lt;/a&gt;&nbsp;[it]&lt;/li&gt; 
--&gt;
+&lt;!-- Japanese --&gt;
+&lt;!-- &lt;li&gt;&lt;a 
href="/gnu/thegnuproject.ja.html"&gt;&#x65e5;&#x672c;&#x8a9e;&lt;/a&gt;&nbsp;[ja]&lt;/li&gt;
 --&gt;
+&lt;!-- Korean --&gt;
+&lt;!-- &lt;li&gt;&lt;a 
href="/gnu/thegnuproject.ko.html"&gt;&#xd55c;&#xad6d;&#xc5b4;&lt;/a&gt;&nbsp;[ko]&lt;/li&gt;
 --&gt;
+&lt;!-- Dutch --&gt;
+&lt;!-- &lt;li&gt;&lt;a 
href="/gnu/thegnuproject.nl.html"&gt;Nederlands&lt;/a&gt;&nbsp;[nl]&lt;/li&gt; 
--&gt;
+&lt;!-- Polish --&gt;
+&lt;!-- &lt;li&gt;&lt;a 
href="/gnu/thegnuproject.pl.html"&gt;polski&lt;/a&gt;&nbsp;[pl]&lt;/li&gt; 
--&gt;
+&lt;!-- Russian --&gt;
+&lt;!-- &lt;li&gt;&lt;a 
href="/gnu/thegnuproject.ru.html"&gt;&#x0440;&#x0443;&#x0441;&#x0441;&#x043a;&#x0438;&#x0439;&lt;/a&gt;&nbsp;[ru]&lt;/li&gt;
 --&gt;
+&lt;!-- Turkish --&gt;
+&lt;!-- &lt;li&gt;&lt;a 
href="/gnu/thegnuproject.tr.html"&gt;T&#x00fc;rk&#x00e7;e&lt;/a&gt;&nbsp;[tr]&lt;/li&gt;
 --&gt;
+&lt;!-- Chinese (Simplified) --&gt;
+&lt;!-- &lt;li&gt;&lt;a 
href="/gnu/thegnuproject.zh-cn.html"&gt;&#x7b80;&#x4f53;&#x4e2d;&#x6587;&lt;/a&gt;&nbsp;[zh-cn]&lt;/li&gt;
 --&gt;
+&lt;!-- Chinese(Traditional) --&gt;
+&lt;!-- &lt;li&gt;&lt;a 
href="/gnu/thegnuproject.zh-tw.html"&gt;&#x7e41;&#x9ad4;&#x4e2d;&#x6587;&lt;/a&gt;&nbsp;[zh-tw]&lt;/li&gt;
 --&gt;
+&lt;!-- &lt;/ul&gt; --&gt;
+&lt;!-- &lt;/div&gt; --&gt;</strong></del></span>
+
+
+&lt;/div&gt;
+&lt;/body&gt;
+&lt;/html&gt;
+</pre></body></html>

Index: philosophy/why-free.zh-tw.html
===================================================================
RCS file: philosophy/why-free.zh-tw.html
diff -N philosophy/why-free.zh-tw.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ philosophy/why-free.zh-tw.html      15 Jul 2012 08:27:32 -0000      1.1
@@ -0,0 +1,234 @@
+
+
+<!--#include virtual="/server/header.zh-tw.html" -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>為甚麽軟體不應有主人 - GNU項目 - 自由軟體基金會 
(FSF)</title>
+
+<meta name="Keywords" content="GNU, GNU項目, FSF, 自由軟體, 
自由軟體基金會, 為甚麽軟體不應有主人" />
+
+<!--#include virtual="/server/banner.zh-tw.html" -->
+<!--#include virtual="/philosophy/po/why-free.translist" -->
+<h2>為甚麽軟體不應有主人</h2>
+
+<p>作者︰<a href="http://www.stallman.org/";><strong>Richard 
Stallman</strong></a></p>
+
+<p>
+數碼資訊科技令大眾更容易複製和變更資料。</p>
+
+<p>
+然而不是所有人都希望這樣。版權制度容許軟體有「主人」。他們主要目的在於從å
…
¬çœ¾å¥ªå–軟體的潛在利益。他們希望獨佔這些軟體的複製、更改權利。</p>
+
+<p>
+版權制度隨著印刷技術而發展--印刷是一種大量製作副本的技術。版權很適合這é
 …技術,因
為它只限制了大規模的複製。它並沒有剝奪圖書讀者
的自由。一般讀者
沒有印刷機,他們只能用筆墨抄寫作品,所以很少有讀者因
此而被控告。</p>
+
+<p>
+數碼科技比印刷機更靈活:當信息呈數碼形式時,你
能很容易把它跟別人分享。這種情況不太配合故
有的版權制度,所以現在有越來越多日益嚴厲的措施用來加
強軟體版權。看看這些軟體出版商協會(Software
+Publishers Association, SPA)的四種慣常說法:</p>
+
+<ul>
+<li>大肆宣傳違反版權法去幫助朋友是錯誤的。</li>
+
+<li>誘使大家告發違返規定的同事和同僚。</li>
+
+<li>如果警察協助突擊搜查公司和學校,那裡的人們必é 
ˆè­‰æ˜Žè‡ªå·±æ²’有非法複製。</li>
+
+<li>因
軟體出版商協會提出要求,美國政府起訴一些如麻省理工學院的
 David
+LaMacchia的人,不是因為他非法軟複製件,而只是因
為沒有升級他的複製工å…
·ï¼Œå¾žè€Œä¸èƒ½å°ç”¨æˆ¶éžæ³•è¤‡è£½è»Ÿé«”進行檢查。<a
+href="#footnote1">[1]</a></li>
+</ul>
+
+<p>
+這些æ…
£å¸¸èªªæ³•å’Œå‰è˜‡è¯æ›¾ç”¨éŽçš„做法相似,在每一台影印機前都有一個守衛,以防止那些未經許可複印,同時個人只有秘密地複製信息,並像「秘密出版物」<a
+href="#trans1">[按1]</a>一樣在手é 
­å‚³æ’­ã€‚不同的是,蘇聯管制信息是政治原因
,而美國則是為了經濟利益。無論動機如何,我們都受到影響。不管什麼原å›
 ï¼Œä»»ä½•äººä¼åœ–阻止信息å…
±äº«ï¼Œéƒ½å°Žè‡´äº†ç›¸åŒçš„後果和同樣的不便。</p>
+
+<p>
+軟體所有者用各種理由來控制我們如何使用資訊的權利︰</p>
+
+
+<ul>
+<li id="name-calling">中傷
+
+<p>
+軟體所有者
使用「盜竊」、「剽竊」這類帶有誣衊的詞語,或者
「知識產權」、「損害」之類專業的術語,向å…
¬çœ¾æš—示他們是合理的--å…
¶å¯¦ï¼Œä»–們是將軟體和真實物件混為一談。</p>
+
+<p>
+我們對「拿取別人的物件」的概念 
,並不能直接套用在複製這件事,然而軟體所有者
卻迫使我們必須接受他們的想法。</p></li>
+
+<li id="exaggeration">憑空誇大
+
+<p>
+軟體所有者
聲稱當用戶複製他們的程序時,他們受到「傷害」或「經濟損失」。但複製並不會對軟體所有è€
…造成直接的影響,也沒有傷害到任何人。只有在使用複製者
不願意給軟體所有者付費時,軟體所有者才會受損失。</p>
+
+<p>
+很明顯大多數這樣的人不願意購買這些程式,但是軟體所有è€
…
會假定所有人都會購買,並以此來計算他們的「損失」。客氣點說這就是誇大了專有軟體的價值。</p></li>
+
+<li id="law">法律
+
+<p>
+軟體所有者經常引用當今的法律和苛刻的刑罰來威脅
我們。這暗示現今的法律反映
了一個不容置疑的道德觀念,同時æ…
«æ¿æˆ‘們視這些刑罰為正常及不能推卸。</p>
+
+<p>
+這些說詞面對嚴謹的思維是站不住è…
³çš„,這做法只是打算利用了人的慣性思維。</p>
+
+<p>
+顯然法律是不能決定錯對的。美國人都應該知道,五十年代的黑人在許多州份坐在巴士前座是違法的;但只有種族主義è€
…才會說他們是錯誤的。</p></li>
+
+<li id="natural-rights">自然權利
+
+<p>
+軟體作者常常聲稱與自己編寫的程式有一種特殊聯繫,因
此他們宣稱對這個程序的渴望和興趣是高於世上任何人。(通常是å
…¬å¸æŒæœ‰è»Ÿé«”版權,而不是作者,但是我們é 
æœŸå¿½ç•¥é€™å€‹å·®ç•°ã€‚)</p>
+
+<p>
+對那些打算把「作者
高於一切」推崇為一種道德的人,本人作為一個著名的軟體開發è€
…,只能說這是廢話。</p>
+
+<p>
+但一般人有兩個原因對自然權利的說法產生共鳴。</p>
+
+<p>
+第一個原因
是將軟體與現實事物過分地類比。當我做意大利麵時,如果å…
¶ä»–人也要吃,我一定會反感,因
為那樣的話,我就吃不上了。他的行為對我造
成的損失,正如他得到的利益一樣。我們中僅
有一人可以吃意大利麵,問題是誰來吃?我們兩者
之間最小的分歧也足以打破道德上的平衡。</p>
+
+<p>
+問題是︰你會否因
為運行或修改一個我寫的程序而直接影響到你
,而對我只會產生一點間接影響?你會否複製我的軟體給你
的朋友,而對你們的影響遠
比對我的還要大?我不應有這樣的權利去叫你
不要這麼做。任何人都不該有。</p>
+
+<p>
+這第二個原因就是,人們被告知作者
的自然權利是社會約定俗成的準則。</p>
+
+<p>
+歷史證明,相反的一方才是正確的。當年起草美國憲法時堅
決駁回了關於作者自然權利的提議。這就是為什麼憲法只是å…
è¨±ç‰ˆæ¬Šé«”系,而並不強制要求;所以說版權體制一定是臨時的。憲法也說明版權體制的目的是促進發展,而不是獎勵作è€
…。版權確實給作者
和出版社帶來了更多收益,但這本來只是一種激勵他們的手段而已。</p>
+
+<p>
+事實是我們的社會建立了削弱å…
¬çœ¾è‡ªç„¶æ¬Šåˆ©çš„版權制度。然而版權只有用於å…
¬ç›Šäº‹æ¥­æ‰æ˜¯æ­£ç•¶çš„。</p></li>
+
+<li id="economics">經濟
+
+<p>
+軟體應該有主人的最終辯解理由是,這會提高軟體產量。</p>
+
+<p>
+這個論據至少比以上的更切合主題。它立足於一個合理目標——滿足軟體用戶的需求。以經驗看來,人們å›
 ç‚ºæ»¿æ„çš„回報而生產更多,是很容易理解的。</p>
+
+<p>
+但是這個關於經濟的論據有瑕疵:它基於這樣一個假設,區別åƒ
…僅是我們要付多少錢的問題。它假設無論軟體是否有å…
¶æ‰€æœ‰è€…,「軟體產品」都是我們想要的。</p>
+
+<p>
+由於這個假設合乎我們處理真實物件的經驗,所以人們很樂意接受。假設ä½
 ä»˜è²»èˆ‡å¦éƒ½èƒ½å¾—到一份一樣的三明治,這樣你
付的費用就是唯一的分別。不管你
是否購買,三明治有相同的味道和相同的營養,但你
只能吃一次。不管你是否從所有者
手中得到三明治,它都不能直接影響到你
的金錢以外的任何事情。</p>
+
+<p>
+對任何真實物件,這都是正確的︰不管它是否有主人都不會直接影響它的本質和用途。</p>
+
+<p>
+如果程式有了主人,這將大大影響它的本質,和你
對它的用途。不同之處不僅僅
是錢的問題。軟體該有主人的體制鼓勵軟體主人生產,但不一定是社會真正需要的。它導致的道德低落影響我們所有人。</p></li>
+
+</ul>
+
+<p>
+社會需要什麼?社會需要對å…
¬æ°‘真實可用的信息──例如,人們可以解讀、修補、使用和改進的程式,而不只是操作。但是軟體主人往往會給我們一個不能ç
 ”究和修改的黑盒子。</p>
+
+<p>
+社會也需要自由。當程式有了主人,用戶就失去了控制他們部分生活的自由。</p>
+
+<p>
+總之社會需要鼓勵å…
¬æ°‘們自主合作的精神。當軟體主人告訴我們用這種自然的方式幫助旁人是剽竊行為時,那他們就是玷污我們的人æ
 ¼ã€‚</p>
+
+<p>
+這正是我們提倡<a href="/philosophy/free-sw.html">自由軟體</a> 
事關自由,而並非價格的原因。</p>
+
+<p>
+支持所有者
的經濟論據是錯誤的,但是經濟問題確實存在。一些人出於榮譽、認同和博愛,而編寫了有用的軟體,但是如果我們希望有更多的軟體,就需要籌集資金。</p>
+
+<p>
+自由軟體開發者自從å…
«åå¹´ä»£å˜—試過許多尋求財源的方法,稍有小成。我們不需要讓任何人置富,å
…¸åž‹çš„收入,足以吸引人做很多比編程少滿足感的工作。</p>
+
+<p>
+多年以來,我一直靠
改進自己編寫的自由軟體為生,直到獲得ç 
”究經費。每次改進我都會添加
到標準發佈版本,使得大眾受益。客戶為我付費,這樣我就會優å
…ˆå®Œæˆä»–們需求,自己的變成次要。</p>
+
+<p>
+一些自由軟體開發者通過支援服務賺錢。1994年,Cygnus
+有近50個員工,估計有大約百分之十五的員工從事自由軟體開發︰對一間軟體å
…¬å¸è€Œè¨€ï¼Œé€™æ˜¯å€‹äº†ä¸èµ·çš„比例。</p>
+
+<p>
+九十年代,Intel、Motorola、Texas Instruments 和 Analog Devices 等å…
¬å¸è¯åˆè´ŠåŠ©æŒçºŒç™¼å±•çš„GNU
+C語言編譯器。現在大部份開發GCC的人工作還是受薪的開發者
完成的。GNU的Ada語言編譯器受美國空軍贊助,之後成立專屬å…
¬å¸å»¶çºŒéŽå€‹é …目。</p>
+
+<p>
+自由軟體運動的規模還是很小,但是靠
聽眾支持的美國電台的例子說明,不用強迫每個用戶付費也可以支撐一個巨大的活動。</p>
+
+<p>
+今天如果你發現用了<a
+href="/philosophy/categories.html#ProprietarySoftware">專有軟體</a>。如果ä½
 çš„朋友問你
複製一份,拒絕是不對的。合作比版權更重要。私下傳播也不能建立健康的社會。人應當自豪的嚮往開放而正直的生活,這就意味著應該對專有軟體說「不」。</p>
+
+<p>
+你應該能與其他軟體使用者開放、自由地合作,能夠
學習軟體如何運作,並教導學生,能夠
在軟體出問題時請中意的程式員修復它。</p>
+
+<p>
+你應該得到自由軟體。</p>
+
+<h4>註釋</h4>
+<ol>
+<li id="footnote1">這項指控後來徹銷了</li>
+</ol>
+
+<hr />
+<h4>本文的英文版刊登於<a
+href="http://shop.fsf.org/product/free-software-free-society/";><cite>Free
+Software, Free Society: The Selected Essays of Richard
+M. Stallman</cite></a>。</h4>
+
+
+<div style="font-size: small;">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
+<p>譯者按︰</p><ol><li 
id="trans1">俄語:самиздат,蘇聯政府有思想審查,禁止的刊物就是é
 é€™ç¨®æ–¹å¼å‚³æ’­ï¼Œè©³æƒ…可參照<a
+href="http://zh.wikipedia.org/zh-tw/%E7%A7%98%E5%AF%86%E5%87%BA%E7%89%88%E7%89%A9";>維基百科條目︰秘密出版物</a></li></ol></div>
+</div>
+
+<!-- All pages on the GNU web server should have the section about    -->
+<!-- verbatim copying.  Please do NOT remove this without talking     -->
+<!-- with the webmasters first. -->
+<!-- Please make sure the copyright date is consistent with the document -->
+<!-- and that it is like this "2001, 2002" not this "2001-2002." -->
+<!--#include virtual="/server/footer.zh-tw.html" -->
+<div id="footer">
+
+<p>
+請來郵 <a 
href="mailto:address@hidden";>&lt;address@hidden&gt;</a>查詢「自由軟體基金會」及「GNU
+計畫」的事宜。或者<a href="/contact/">透過å…
¶ä»–方式</a>聯絡自由軟體基金會。
+<br />
+請來郵<a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>告訴我們任何失效的連結、錯誤和建議。
+</p>
+
+<p>
+請參照 <a href="/server/standards/README.translations.html">翻譯說明</a>
+了解有關協助翻譯本文的事情。
+</p>
+
+<p>
+版權所有 &copy; 1994, 2009 Richard Stallman
+<br />
+本頁面採用 <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/";>Creative Commons
+Attribution-NoDerivs 3.0 United States License</a> 許可證授權。
+</p>
+
+
+<div class="translators-credits">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
+<b>翻譯</b>: Karl Lam 2012</div>
+
+
+ <p><!-- timestamp start -->
+更新時間︰
+
+$Date: 2012/07/15 08:27:32 $
+
+<!-- timestamp end -->
+</p>
+</div>
+
+
+</div>
+</body>
+</html>

Index: philosophy/po/why-free.zh-tw-en.html
===================================================================
RCS file: philosophy/po/why-free.zh-tw-en.html
diff -N philosophy/po/why-free.zh-tw-en.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ philosophy/po/why-free.zh-tw-en.html        15 Jul 2012 08:27:56 -0000      
1.1
@@ -0,0 +1,358 @@
+<!--#include virtual="/server/header.html" -->
+
+<title>Why Software Should Not Have Owners - GNU Project - Free Software 
Foundation (FSF)</title>
+
+<meta name="Keywords" content="GNU, GNU Project, FSF, Free Software, Free 
Software Foundation, Why Software Should Not Have Owners" />
+
+<!--#include virtual="/server/banner.html" -->
+<!--#include virtual="/philosophy/po/why-free.translist" -->
+
+<h2>Why Software Should Not Have Owners</h2>
+
+<p>by <a href="http://www.stallman.org/";><strong>Richard
+Stallman</strong></a></p>
+
+<p>
+Digital information technology contributes to the world by making it
+easier to copy and modify information.  Computers promise to make this
+easier for all of us.</p>
+
+<p>
+Not everyone wants it to be easier.  The system of copyright gives
+software programs &ldquo;owners&rdquo;, most of whom aim to withhold
+software's potential benefit from the rest of the public.  They would
+like to be the only ones who can copy and modify the software that we
+use.</p>
+
+<p>
+The copyright system grew up with printing&mdash;a technology for
+mass-production copying.  Copyright fit in well with this technology
+because it restricted only the mass producers of copies.  It did not
+take freedom away from readers of books.  An ordinary reader, who did
+not own a printing press, could copy books only with pen and ink, and
+few readers were sued for that.</p>
+
+<p>
+Digital technology is more flexible than the printing press: when
+information has digital form, you can easily copy it to share it with
+others.  This very flexibility makes a bad fit with a system like
+copyright.  That's the reason for the increasingly nasty and draconian
+measures now used to enforce software copyright.  Consider these four
+practices of the Software Publishers Association (SPA):</p>
+
+<ul>
+<li>Massive propaganda saying it is wrong to disobey the owners to
+help your friend.</li>
+
+<li>Solicitation for stool pigeons to inform on their coworkers and
+colleagues.</li>
+
+<li>Raids (with police help) on offices and schools, in which people
+are told they must prove they are innocent of illegal copying.</li>
+
+<li>Prosecution (by the US government, at the SPA's request) of people
+such as
+<acronym title="Massachusetts Institute of Technology">MIT</acronym>'s
+David LaMacchia, not for copying software (he is not accused of
+copying any), but merely for leaving copying facilities unguarded and
+failing to censor their use.<a href="#footnote1">[1]</a></li>
+</ul>
+
+<p>
+All four practices resemble those used in the former Soviet Union,
+where every copying machine had a guard to prevent forbidden copying,
+and where individuals had to copy information secretly and pass it
+from hand to hand as samizdat.  There is of course a difference: the
+motive for information control in the Soviet Union was political; in
+the US the motive is profit.  But it is the actions that affect us,
+not the motive.  Any attempt to block the sharing of information, no
+matter why, leads to the same methods and the same harshness.</p>
+
+<p>
+Owners make several kinds of arguments for giving them the power
+to control how we use information:</p>
+
+
+<ul>
+<li id="name-calling">Name calling.
+
+<p>
+Owners use smear words such as &ldquo;piracy&rdquo; and
+&ldquo;theft&rdquo;, as well as expert terminology such as
+&ldquo;intellectual property&rdquo; and &ldquo;damage&rdquo;, to
+suggest a certain line of thinking to the public&mdash;a simplistic
+analogy between programs and physical objects.</p>
+
+<p>
+Our ideas and intuitions about property for material objects are about
+whether it is right to <em>take an object away</em> from someone else.  They
+don't directly apply to <em>making a copy</em> of something.  But the owners
+ask us to apply them anyway.</p></li>
+
+<li id="exaggeration">Exaggeration.
+
+<p>
+Owners say that they suffer &ldquo;harm&rdquo; or &ldquo;economic
+loss&rdquo; when users copy programs themselves.  But the copying has
+no direct effect on the owner, and it harms no one.  The owner can
+lose only if the person who made the copy would otherwise have paid
+for one from the owner.</p>
+
+<p>
+A little thought shows that most such people would not have bought
+copies.  Yet the owners compute their &ldquo;losses&rdquo; as if each
+and every one would have bought a copy.  That is exaggeration&mdash;to
+put it kindly.</p></li>
+
+<li id="law">The law.
+
+<p>
+Owners often describe the current state of the law, and the harsh
+penalties they can threaten us with.  Implicit in this approach is the
+suggestion that today's law reflects an unquestionable view of
+morality&mdash;yet at the same time, we are urged to regard these
+penalties as facts of nature that can't be blamed on anyone.</p>
+
+<p>
+This line of persuasion isn't designed to stand up to critical
+thinking; it's intended to reinforce a habitual mental pathway.</p>
+
+<p>
+It's elementary that laws don't decide right and wrong.  Every American
+should know that, in the 1950s, it was against the law in many
+states for a black person to sit in the front of a bus; but only
+racists would say sitting there was wrong.</p></li>
+
+<li id="natural-rights">Natural rights.
+
+<p>
+Authors often claim a special connection with programs they have
+written, and go on to assert that, as a result, their desires and
+interests concerning the program simply outweigh those of anyone
+else&mdash;or even those of the whole rest of the world.  (Typically
+companies, not authors, hold the copyrights on software, but we are
+expected to ignore this discrepancy.)</p>
+
+<p>
+To those who propose this as an ethical axiom&mdash;the author is more
+important than you&mdash;I can only say that I, a notable software
+author myself, call it bunk.</p>
+
+<p>
+But people in general are only likely to feel any sympathy with the
+natural rights claims for two reasons.</p>
+
+<p>
+One reason is an overstretched analogy with material objects.  When I
+cook spaghetti, I do object if someone else eats it, because then I
+cannot eat it.  His action hurts me exactly as much as it benefits
+him; only one of us can eat the spaghetti, so the question is, which one?
+The smallest distinction between us is enough to tip the ethical
+balance.</p>
+
+<p>
+But whether you run or change a program I wrote affects you directly
+and me only indirectly.  Whether you give a copy to your friend
+affects you and your friend much more than it affects me.  I shouldn't
+have the power to tell you not to do these things.  No one should.</p>
+
+<p>
+The second reason is that people have been told that natural rights
+for authors is the accepted and unquestioned tradition of our society.</p>
+
+<p>
+As a matter of history, the opposite is true.  The idea of natural
+rights of authors was proposed and decisively rejected when the US
+Constitution was drawn up.  That's why the Constitution only
+<em>permits</em> a system of copyright and does not <em>require</em>
+one; that's why it says that copyright must be temporary.  It also
+states that the purpose of copyright is to promote progress&mdash;not
+to reward authors.  Copyright does reward authors somewhat, and
+publishers more, but that is intended as a means of modifying their
+behavior.</p>
+
+<p>
+The real established tradition of our society is that copyright cuts
+into the natural rights of the public&mdash;and that this can only be
+justified for the public's sake.</p></li>
+
+<li id="economics">Economics.
+
+<p>
+The final argument made for having owners of software is that this
+leads to production of more software.</p>
+
+<p>
+Unlike the others, this argument at least takes a legitimate approach
+to the subject.  It is based on a valid goal&mdash;satisfying the
+users of software.  And it is empirically clear that people will
+produce more of something if they are well paid for doing so.</p>
+
+<p>
+But the economic argument has a flaw: it is based on the assumption
+that the difference is only a matter of how much money we have to pay.
+It assumes that <em>production of software</em> is what we want,
+whether the software has owners or not.</p>
+
+<p>
+People readily accept this assumption because it accords with our
+experiences with material objects.  Consider a sandwich, for instance.
+You might well be able to get an equivalent sandwich either gratis or
+for a price.  If so, the amount you pay is the only difference.
+Whether or not you have to buy it, the sandwich has the same taste,
+the same nutritional value, and in either case you can only eat it
+once.  Whether you get the sandwich from an owner or not cannot
+directly affect anything but the amount of money you have afterwards.</p>
+
+<p>
+This is true for any kind of material object&mdash;whether or not it
+has an owner does not directly affect what it <em>is</em>, or what you
+can do with it if you acquire it.</p>
+
+<p>
+But if a program has an owner, this very much affects what it is, and
+what you can do with a copy if you buy one.  The difference is not
+just a matter of money.  The system of owners of software encourages
+software owners to produce something&mdash;but not what society really
+needs.  And it causes intangible ethical pollution that affects us
+all.</p></li>
+
+</ul>
+
+<p>
+What does society need?  It needs information that is truly available
+to its citizens&mdash;for example, programs that people can read, fix,
+adapt, and improve, not just operate.  But what software owners
+typically deliver is a black box that we can't study or change.</p>
+
+<p>
+Society also needs freedom.  When a program has an owner, the users
+lose freedom to control part of their own lives.</p>
+
+<p>
+And, above all, society needs to encourage the spirit of voluntary
+cooperation in its citizens.  When software owners tell us that
+helping our neighbors in a natural way is &ldquo;piracy&rdquo;, they
+pollute our society's civic spirit.</p>
+
+<p>
+This is why we say that
+<a href="/philosophy/free-sw.html">free software</a>
+is a matter of freedom, not price.</p>
+
+<p>
+The economic argument for owners is erroneous, but the economic issue
+is real.  Some people write useful software for the pleasure of
+writing it or for admiration and love; but if we want more software
+than those people write, we need to raise funds.</p>
+
+<p>
+Since the 1980s, free software developers have tried various methods
+of finding funds, with some success.  There's no need to make anyone
+rich; a typical income is plenty of incentive to do many jobs that are
+less satisfying than programming.</p>
+
+<p>
+For years, until a fellowship made it unnecessary, I made a living
+from custom enhancements of the free software I had written.  Each
+enhancement was added to the standard released version and thus
+eventually became available to the general public.  Clients paid me so
+that I would work on the enhancements they wanted, rather than on the
+features I would otherwise have considered highest priority.</p>
+
+<p>
+Some free software developers make money by selling support services.
+In 1994, Cygnus Support, with around 50 employees, estimated that
+about 15 percent of its staff activity was free software
+development&mdash;a respectable percentage for a software company.</p>
+
+<p>
+In the early 1990s, companies including Intel, Motorola, Texas
+Instruments and Analog Devices combined to fund the continued
+development of the GNU C compiler.  Most GCC development is still done
+by paid developers.  The GNU compiler for the Ada language was funded
+in the 90s by the US Air Force, and continued since then by a company
+formed specifically for the purpose.</p>
+
+<p>
+The free software movement is still small, but the example of
+listener-supported radio in the US shows it's possible to support a
+large activity without forcing each user to pay.</p>
+
+<p>
+As a computer user today, you may find yourself using a
+<a href="/philosophy/categories.html#ProprietarySoftware">proprietary</a>
+program.  If your friend asks to make a copy, it would be wrong to
+refuse.  Cooperation is more important than copyright.  But
+underground, closet cooperation does not make for a good society.  A
+person should aspire to live an upright life openly with pride, and
+this means saying no to proprietary software.</p>
+
+<p>
+You deserve to be able to cooperate openly and freely with other
+people who use software.  You deserve to be able to learn how the
+software works, and to teach your students with it.  You deserve to be
+able to hire your favorite programmer to fix it when it breaks.</p>
+
+<p>
+You deserve free software.</p>
+
+<h4>Footnotes</h4>
+<ol>
+<li id="footnote1">The charges were subsequently dismissed.</li>
+</ol>
+
+<hr />
+<h4>This essay is published
+in <a href="http://shop.fsf.org/product/free-software-free-society/";><cite>Free
+Software, Free Society: The Selected Essays of Richard
+M. Stallman</cite></a>.</h4>
+
+</div>
+
+<!-- All pages on the GNU web server should have the section about    -->
+<!-- verbatim copying.  Please do NOT remove this without talking     -->
+<!-- with the webmasters first. --> 
+<!-- Please make sure the copyright date is consistent with the document -->
+<!-- and that it is like this "2001, 2002" not this "2001-2002." -->
+
+<!--#include virtual="/server/footer.html" -->
+
+<div id="footer">
+
+<p>
+Please send 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>
+
+<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>
+Copyright &copy; 1994, 2009 Richard Stallman
+<br />
+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>
+
+<p>Updated:
+<!-- timestamp start -->
+$Date: 2012/07/15 08:27:56 $
+<!-- timestamp end -->
+</p>
+</div>
+
+
+</div>
+</body>
+</html>

Index: server/gnun/compendia/compendium.zh-tw.po
===================================================================
RCS file: server/gnun/compendia/compendium.zh-tw.po
diff -N server/gnun/compendia/compendium.zh-tw.po
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ server/gnun/compendia/compendium.zh-tw.po   15 Jul 2012 08:28:05 -0000      
1.1
@@ -0,0 +1,262 @@
+# Traditional Chinese translation of 
http://www.gnu.org/server/body-include-2.html
+# Copyright (C) 2008 Free Software Foundation, Inc.
+# This file is distributed under the same license as the gnu.org article.
+#
+msgid ""
+msgstr ""
+"Project-Id-Version: body-include-2.html\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2010-11-22 12:25-0500\n"
+"PO-Revision-Date: 2012-02-15 13:54+0800\n"
+"Last-Translator: \n"
+"Language-Team: Chinese <address@hidden>\n"
+"Language: zh-tw\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8-bit\n"
+"Outdated-Since: 2012-05-05 16:00-0300\n"
+
+#. type: Content of: <div><p>
+msgid ""
+"Please send 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."
+msgstr ""
+"請來郵 <a 
href=\"mailto:address@hidden";>&lt;address@hidden&gt;</a>查詢「自由軟體基"
+"金會」及「GNU 計畫」的事宜。或者<a href=\"/contact/\">透過å…
¶ä»–方式</a>聯絡自"
+"由軟體基金會。"
+
+#. type: Content of: <div><p>
+msgid ""
+"Please send broken links and other corrections or suggestions to <a href="
+"\"mailto:address@hidden";>&lt;address@hidden&gt;</a>."
+msgstr ""
+"請來郵<a href=\"mailto:address@hidden";>&lt;address@hidden&gt;</a>告"
+"訴我們任何失效的連結、錯誤和建議。"
+
+#. type: Content of: <div><p>
+msgid ""
+"Please see the <a href=\"/server/standards/README.translations.html"
+"\">Translations README</a> for information on coordinating and submitting "
+"translations of this article."
+msgstr ""
+"請參照 <a 
href=\"/server/standards/README.translations.html\">翻譯說明</a> 了"
+"解有關協助翻譯本文的事情。"
+
+#.  timestamp start 
+#. type: Content of: <div><p>
+msgid "Updated:"
+msgstr "更新時間︰"
+
+#. type: Content of: <div><address>
+msgid "51 Franklin St, Fifth Floor, Boston, MA 02110, USA"
+msgstr ""
+
+#. type: Content of: <div><p>
+msgid ""
+"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>."
+msgstr ""
+"本頁面採用 <a rel=\"license\" 
href=\"http://creativecommons.org/licenses/by-";
+"nd/3.0/us/\">Creative Commons Attribution-NoDerivs 3.0 United States "
+"License</a> 許可證授權。"
+
+#. type: Content of: <div><p>
+#, fuzzy
+#| msgid ""
+#| "Please send 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."
+msgid ""
+"Please send FSF &amp; GNU inquiries to <a href=\"mailto:address@hidden";
+"\"><em>address@hidden</em></a>.  There are also <a href=\"/contact/\">other "
+"ways to contact</a> the FSF."
+msgstr ""
+"請來郵 <a 
href=\"mailto:address@hidden";>&lt;address@hidden&gt;</a>查詢「自由軟體基"
+"金會」及「GNU 計畫」的事宜。或者<a href=\"/contact/\">透過å…
¶ä»–方式</a>聯絡自"
+"由軟體基金會。"
+
+#. type: Content of: <div><p>
+#, fuzzy
+#| msgid ""
+#| "Please send broken links and other corrections or suggestions to <a href="
+#| "\"mailto:address@hidden";>&lt;address@hidden&gt;</a>."
+msgid ""
+"Please send broken links and other corrections or suggestions to <a href="
+"\"mailto:address@hidden";><em>address@hidden</em></a>."
+msgstr ""
+"請來郵<a href=\"mailto:address@hidden";>&lt;address@hidden&gt;</a>告"
+"訴我們任何失效的連結、錯誤和建議。"
+
+#. type: Content of: <ul><li>
+msgid "Paul Eggert"
+msgstr ""
+
+#. type: Content of: <div><address>
+msgid "51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA"
+msgstr ""
+
+#. type: Content of: <div><p>
+#, fuzzy
+#| msgid ""
+#| "Please send 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."
+msgid ""
+"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."
+msgstr ""
+"請來郵 <a 
href=\"mailto:address@hidden";>&lt;address@hidden&gt;</a>查詢「自由軟體基"
+"金會」及「GNU 計畫」的事宜。或者<a href=\"/contact/\">透過å…
¶ä»–方式</a>聯絡自"
+"由軟體基金會。"
+
+#. type: Content of: <table><tr><td>
+msgid "</a>"
+msgstr ""
+
+#. type: Content of: <div><p>
+msgid "Copyright &copy; 2011, 2012 Free Software Foundation, Inc."
+msgstr ""
+
+#. type: Content of: <div><ul><li>
+msgid "<a href=\"/education/edu-contents.html\">Education Contents</a>"
+msgstr ""
+
+#. type: Content of: <div><ul><li>
+msgid "<a href=\"/education/edu-cases.html\">Case Studies</a>"
+msgstr ""
+
+#. type: Content of: <div><ul><li>
+msgid "<a href=\"/education/edu-resources.html\">Educational Resources</a>"
+msgstr ""
+
+#. type: Content of: <div><ul><li>
+msgid "<a href=\"/education/edu-projects.html\">Education Projects</a>"
+msgstr ""
+
+#. type: Content of: <div><ul><li>
+msgid "<a href=\"/education/edu-faq.html\">FAQ</a>"
+msgstr ""
+
+#. type: Content of: <div><ul><li>
+msgid "<a href=\"/education/edu-team.html\">The Education Team</a>"
+msgstr ""
+
+#. type: Content of: <div><p>
+#, fuzzy
+#| msgid ""
+#| "Please send broken links and other corrections or suggestions to <a href="
+#| "\"mailto:address@hidden";>&lt;address@hidden&gt;</a>."
+msgid ""
+"Please send broken links and other corrections or suggestions to <a href="
+"\"mailto:address@hidden";>&lt;address@hidden&gt;</a>."
+msgstr ""
+"請來郵<a href=\"mailto:address@hidden";>&lt;address@hidden&gt;</a>告"
+"訴我們任何失效的連結、錯誤和建議。"
+
+#. type: Content of: <p>
+#, fuzzy
+#| msgid ""
+#| "by <a href=\"http://www.stallman.org/\";><strong>Richard Stallman</"
+#| "strong></a>"
+msgid "by <a href=\"http://www.stallman.org/\";>Richard Stallman</a>"
+msgstr ""
+"作者︰<a href=\"http://www.stallman.org/\";><strong>Richard Stallman</"
+"strong></a>"
+
+#. type: Content of: <div><p>
+#, fuzzy
+#| msgid ""
+#| "Please send 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."
+msgid ""
+"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"
+"org&gt;</a>."
+msgstr ""
+"請來郵 <a 
href=\"mailto:address@hidden";>&lt;address@hidden&gt;</a>查詢「自由軟體基"
+"金會」及「GNU 計畫」的事宜。或者<a href=\"/contact/\">透過å…
¶ä»–方式</a>聯絡自"
+"由軟體基金會。"
+
+#. type: Attribute 'content' of: <meta>
+msgid ""
+"GNU, FSF, Free Software Foundation, Linux, Emacs, GCC, Unix, Free Software, "
+"Operating System, GNU Kernel, HURD, GNU HURD, Hurd"
+msgstr ""
+
+#. type: Attribute 'content' of: <meta>
+msgid ""
+"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."
+msgstr ""
+
+#. type: Attribute 'title' of: <link>
+msgid "What's New"
+msgstr ""
+
+#. type: Attribute 'title' of: <link>
+msgid "New Free Software"
+msgstr ""
+
+#. type: Content of: <h2>
+msgid "Disclaimer"
+msgstr ""
+
+#. type: Content of: <p>
+msgid ""
+"<a href=\"/fun/humor.html\">Other humor</a> in the GNU Humor Collection."
+msgstr ""
+
+#. type: Content of: <p>
+msgid "The Free Software Foundation claims no copyright on this joke."
+msgstr ""
+
+#. type: Content of: <p>
+msgid ""
+"The joke on this page was obtained from the FSF's <a href=\"http://lists.gnu.";
+"org/\">email archives</a> of the GNU Project."
+msgstr ""
+
+#. type: Content of: <h4>
+msgid "Footnotes"
+msgstr "註釋"
+
+#. type: Content of: <p>
+msgid ""
+"by <a href=\"http://www.stallman.org/\";><strong>Richard Stallman</strong></a>"
+msgstr ""
+"作者︰<a href=\"http://www.stallman.org/\";><strong>Richard Stallman</"
+"strong></a>"
+
+#. type: Content of: <p>
+msgid ""
+"<a href=\"/graphics/graphics.html\">Other art</a> in the GNU Art Gallery."
+msgstr ""
+
+#. type: Content of: <div><p>
+msgid ""
+"The GNU logo can be used verbatim in contexts talking about GNU in a "
+"supportive and accurate way.  For permission, ask address@hidden"
+msgstr ""
+
+#. type: Content of: <p>
+msgid "This picture is available in the following formats:"
+msgstr ""
+
+#. type: Content of: <div><p>
+msgid "Copyright notice above."
+msgstr ""
+
+#. type: Content of: <p>
+msgid "Global NAPs, for T1 Internet connectivity to the FSF offices"
+msgstr ""
+
+#. type: Content of: <p>
+msgid "Terence O'Gorman"
+msgstr ""



reply via email to

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