www-commits
[Top][All Lists]
Advanced

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

www/philosophy po/x.translist po/x.zh-tw.po x.z...


From: GNUN
Subject: www/philosophy po/x.translist po/x.zh-tw.po x.z...
Date: Wed, 28 Apr 2021 09:00:45 -0400 (EDT)

CVSROOT:        /web/www
Module name:    www
Changes by:     GNUN <gnun>     21/04/28 09:00:45

Modified files:
        philosophy/po  : x.translist x.zh-tw.po 
Added files:
        philosophy     : x.zh-tw.html 
        philosophy/po  : x.zh-tw-en.html 

Log message:
        Automatic update by GNUnited Nations.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/x.zh-tw.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/x.translist?cvsroot=www&r1=1.13&r2=1.14
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/x.zh-tw.po?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/x.zh-tw-en.html?cvsroot=www&rev=1.1

Patches:
Index: po/x.translist
===================================================================
RCS file: /web/www/www/philosophy/po/x.translist,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -b -r1.13 -r1.14
--- po/x.translist      15 Mar 2020 18:34:47 -0000      1.13
+++ po/x.translist      28 Apr 2021 13:00:45 -0000      1.14
@@ -12,6 +12,7 @@
 <span dir="ltr">[nl]&nbsp;<a lang="nl" hreflang="nl" 
href="/philosophy/x.nl.html">Nederlands</a> &nbsp;</span>
 <span dir="ltr">[pl]&nbsp;<a lang="pl" hreflang="pl" 
href="/philosophy/x.pl.html">polski</a> &nbsp;</span>
 <span dir="ltr">[ru]&nbsp;<a lang="ru" hreflang="ru" 
href="/philosophy/x.ru.html">русский</a> &nbsp;</span>
+<span dir="ltr">[zh-tw]&nbsp;<a lang="zh-tw" hreflang="zh-tw" 
href="/philosophy/x.zh-tw.html">繁體中文</a> &nbsp;</span>
 </p>
 </div>' -->
 <link rel="alternate" type="text/html" href="/philosophy/x.html" 
hreflang="x-default" />
@@ -25,4 +26,5 @@
 <link rel="alternate" type="text/html" lang="nl" hreflang="nl" 
href="/philosophy/x.nl.html" title="Nederlands" />
 <link rel="alternate" type="text/html" lang="pl" hreflang="pl" 
href="/philosophy/x.pl.html" title="polski" />
 <link rel="alternate" type="text/html" lang="ru" hreflang="ru" 
href="/philosophy/x.ru.html" title="русский" />
+<link rel="alternate" type="text/html" lang="zh-tw" hreflang="zh-tw" 
href="/philosophy/x.zh-tw.html" title="繁體中文" />
 <!-- end translist file -->

Index: po/x.zh-tw.po
===================================================================
RCS file: /web/www/www/philosophy/po/x.zh-tw.po,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- po/x.zh-tw.po       28 Apr 2021 12:32:18 -0000      1.1
+++ po/x.zh-tw.po       28 Apr 2021 13:00:45 -0000      1.2
@@ -14,7 +14,6 @@
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"X-Outdated-Since: 2020-10-06 08:28+0000\n"
 "Plural-Forms: nplurals=1; plural=0;\n"
 "X-Generator: Lokalize 21.04.0\n"
 
@@ -39,8 +38,6 @@
 msgstr "X Window 系統的陷阱"
 
 #. type: Content of: <div><address>
-# | by Richard {+M.+} Stallman
-#| msgid "by Richard Stallman"
 msgid "by Richard M. Stallman"
 msgstr "作者為 Richard M. Stallman"
 
@@ -198,26 +195,6 @@
 "的 X 相關軟體以著作傳的方式釋出。"
 
 #. type: Content of: <div><div><p>
-# | When you work on the core of X, on programs such as the X server, Xlib,
-# | and Xt, there is a practical reason not to use copyleft.  The X.org group
-# | does an important job for the community in maintaining these programs, and
-# | the benefit of copylefting our changes would be less than the harm done by
-# | a fork in development.  So it is better to work with them, and not
-# | copyleft our changes on these programs.  Likewise for utilities such as
-# | [-<tt>xset</tt>-] {+<code>xset</code>+} and [-<tt>xrdb</tt>,-]
-# | {+<code>xrdb</code>,+} which are close to the core of X and do not need
-# | major improvements.  At least we know that the X.org group has a firm
-# | commitment to developing these programs as free software.
-#| msgid ""
-#| "When you work on the core of X, on programs such as the X server, Xlib, "
-#| "and Xt, there is a practical reason not to use copyleft.  The X.org group "
-#| "does an important job for the community in maintaining these programs, "
-#| "and the benefit of copylefting our changes would be less than the harm "
-#| "done by a fork in development.  So it is better to work with them, and "
-#| "not copyleft our changes on these programs.  Likewise for utilities such "
-#| "as <tt>xset</tt> and <tt>xrdb</tt>, which are close to the core of X and "
-#| "do not need major improvements.  At least we know that the X.org group "
-#| "has a firm commitment to developing these programs as free software."
 msgid ""
 "When you work on the core of X, on programs such as the X server, Xlib, and "
 "Xt, there is a practical reason not to use copyleft.  The X.org group does "
@@ -232,9 +209,9 @@
 "當你在 X 的核心上工作的時候,在如 X 伺服器、Xlib 與 Xt 
等程式,有一個不使用著"
 "作傳的實際原因。X.org 
小組在維護這些程式方面為社群做了重要的工作,將我們的變"
 
"更著作傳化的好處會少於分道揚鑣開發的壞處。所以應該要與他們合作,而非在這些程"
-"式上將我們的變更著作傳化。同樣適用於 <code>xset</code> 與 
<code>xrdb</code> 等工具程"
-"式,它們接近 X 的核心且不需要重大改進。至少我們知道 
X.org 小組堅決承諾將這些"
-"程式繼續作為自由軟體開發。"
+"式上將我們的變更著作傳化。同樣適用於 <code>xset</code> 與 
<code>xrdb</code> "
+"等工具程式,它們接近 X 的æ 
¸å¿ƒä¸”不需要重大改進。至少我們知道 X.org 小組堅決承"
+"諾將這些程式繼續作為自由軟體開發。"
 
 #. type: Content of: <div><div><p>
 msgid ""
@@ -328,9 +305,6 @@
 "宜。"
 
 #. type: Content of: <div><p>
-# | Copyright &copy; 1998, 1999, 2009, [-2015-] {+2015, 2020+} Richard M.
-# | Stallman
-#| msgid "Copyright &copy; 1998, 1999, 2009, 2015 Richard M. Stallman"
 msgid "Copyright &copy; 1998, 1999, 2009, 2015, 2020 Richard M. Stallman"
 msgstr "Copyright &copy; 1998, 1999, 2009, 2015, 2020 Richard M. Stallman"
 

Index: x.zh-tw.html
===================================================================
RCS file: x.zh-tw.html
diff -N x.zh-tw.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ x.zh-tw.html        28 Apr 2021 13:00:45 -0000      1.1
@@ -0,0 +1,165 @@
+<!--#set var="ENGLISH_PAGE" value="/philosophy/x.en.html" -->
+
+<!--#include virtual="/server/header.zh-tw.html" -->
+<!-- Parent-Version: 1.77 -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>X Window 系統的陷阱 - GNU 專案 - 自由軟體基金會</title>
+<meta http-equiv="Keywords"
+      content="GNU, FSF, 自由軟體基金會, 自由, Richard Stallman, rms, 
自由軟體運動" />
+<meta http-equiv="Description"
+      content="Richard Stallman 
討論開發自由作業系統運動的歷史。" />
+
+<!--#include virtual="/philosophy/po/x.translist" -->
+<!--#include virtual="/server/banner.zh-tw.html" -->
+<div class="reduced-width">
+<h2>X Window 系統的陷阱</h2>
+
+<address class="byline">作者為 Richard M. Stallman</address>
+<hr class="thin" />
+<div class="article">
+<p>
+要著作傳還是不要著作傳?這是自由軟體社群幾個主要的爭論點之一。著作傳的想法是我們應該以火æ»
…
火,亦即我們應該利用著作權來確保我們的程式碼保持自由。GNU
+通用公眾授權條款 (GNU GPL) 是著作傳式授權條款的å…
¶ä¸­ä¸€å€‹ä¾‹å­ã€‚</p>
+
+<p>
+某些自由軟體開發者
比較偏好非著作傳式的散佈方式。非著作傳式的授權條款,如
 XFree86 與 <a
+href="/licenses/bsd.html">BSD</a>
+是基於永遠不對任何人說不的想法,甚至對那些將你
的作品用做限制å…
¶ä»–人的基礎的人也一樣。非著作傳式授權條款並沒有錯,但它錯過了積極保護我們修改與轉散佈軟體的自由。為此,我們需要著作傳。</p>
+
+<p>
+多年以前,X
+協會是著作傳的主要對手。它既使用了道德勸說,也對自由軟體開發è€
…施加壓力以防他們將他們的程式著作傳化。其道德勸說是奠
基於說不是不好的行為。而壓力則源於å…
¶è®“著作傳軟體不能進入
+X 散佈版的規則。</p>
+
+<p>
+為什麼 X 
協會會有如此的政策?這要從他們對成功的概念談起。X 
協會將成功定義為受歡迎的程度,特別是讓電腦公司使用 X 
Window
+系統。這種定義讓電腦å…
¬å¸å¯ä»¥ç‚ºæ‰€æ¬²ç‚ºï¼šä¸è«–他們想要什麼,X 協會都必é 
ˆå”助他們取得。</p>
+
+<p>
+電腦公司通常是散佈專有軟體。他們想要自由軟體開發者
把他們的作品捐出來做為這類的用途。如果他們直接這樣做,人們只會嘲笑他們。但面對他們的
 X
+協會會將這類的要求視為一種無私的要求。「加å…
¥æˆ‘們,並將我們的作品捐贈給專有軟體開發者
,」他們這麼說,並表明這是一種高尚的自我犧牲的形式。「åŠ
 å…
¥æˆ‘們來贏得人氣,」他們又這麼說,並表示這甚至不是犧牲。</p>
+
+<p>
+但自我犧牲不是問題:拋棄由著作傳提供的可以保護整個社群的自由的防禦,犧牲的比自己還多。那些同意
 X 協會請求的人將社群的未來委託給 X 協會的善意。</p>
+
+<p>
+這種信任是錯誤的。在1997年,X 協會制定了一項
限制即將發佈的 X11R6.4
+版本的計畫,以使å…
¶è®Šç‚ºéžè‡ªç”±è»Ÿé«”。他們決定開始說不,不僅
是對專有軟體開發者,同時也是對我們的社群。</p>
+
+<p>
+這裡有點諷刺。如果你在 X 協會請求你
不要使用著作傳時說好,你就讓 X 協會獲得授權,並限制你
的程式的這個版本,以及 X 核心程式碼。</p>
+
+<p>
+X 協會並沒有執行這項計畫。相反地,它將自己關閉,並把 
X 的開發轉移給開放團體,而å…
¶å·¥ä½œäººå“¡æ­£åœ¨åŸ·è¡Œé¡žä¼¼çš„計畫。為了給他們榮譽,當我要求他們將
+X11R6.4 同時以 GNU GPL 
與他們計畫中的限制性授權條款發佈時,他們願意考æ…
®é€™å€‹æƒ³æ³•ã€‚(他們堅決反對保留舊的 X11
+散佈條款。)在他們對此提案說好或不好之前,它就已經因
為另一個原因失敗了:XFree86 小組遵循了 X 
協會的舊政策,並且不接受著作傳軟體。
+</p>
+
+<p>
+在1998年9月,X11R6.4 
以非自由散佈條款釋出後的數個月後,開放團體推翻了å…
¶æ±ºç­–,並將其以與 X11R6.3
+相同的非著作傳自由軟體授權條款釋出。因
此,開放團體最後做了正確的事情,但這並沒有改變æ 
¹æœ¬çš„問題。</p>
+
+<p>
+即便 X 協會與開放團體從未計畫限制
+X,å…
¶ä»–人也可以做到。非著作傳軟體容易受到各方面的攻擊;å…
¶å…è¨±ä»»ä½•äººè®“非自由版本處於主導地位,只要他們投入足夠
的資源,以專有程式碼加å…
¥é‡è¦çš„功能。選擇基於技術特性而非自由的使用者
將很容易被誘拐到非自由版本以獲得短期的便利。</p>
+
+<p>
+X 協會與開放團體就不能再施加道德勸說,因
為說不是錯誤的。這讓你更容易決定將你的 X 
相關軟體以著作傳的方式釋出。</p>
+
+<p>
+當你在 X 的核心上工作的時候,在如 X 伺服器、Xlib 與 Xt 
等程式,有一個不使用著作傳的實際原因。X.org
+小組在維護這些程式方面為社群做了重要的工作,將我們的變更著作傳化的好處會少於分道揚鑣開發的壞處。所以應該要與他們合作,而非在這些程式上將我們的變更著作傳化。同樣適用於
+<code>xset</code> 與 <code>xrdb</code> 等工具程式,它們接近 X 的æ 
¸å¿ƒä¸”不需要重大改進。至少我們知道 X.org
+小組堅決承諾將這些程式繼續作為自由軟體開發。</p>
+
+<p>
+而對於 X æ 
¸å¿ƒä»¥å¤–的程式,問題則有所不同:應用程式、視窗管理員與額外的函式庫與小工å
…
·ã€‚沒有理由不將它們著作傳化,我們應該將它們著作傳化。</p>
+
+<p>
+如果有人感受到包含在 X 散佈版中的標準所施加的壓力,GNU 
專案承諾將會宣傳可與 X
+一同運作的著作傳軟體包。如果你
想要將某些東西著作傳化,而且擔心其從 X 
散佈版遺漏而影響其人氣,請向我們尋求協助。</p>
+
+<p>
+同時,如果我們覺得不需要太多人氣,那就更好了。當一個商人以「更受歡迎」來誘惑ä½
 æ™‚,他可能是在試圖說服你,他對你
的程式的成功非常重要。不要相信他!如果你
的程式很好,它自然而然就會有很多使用者;你
不需要對特定的使用者感到絕望,如果你
不這樣,就會更強大。你可以回應「要不要隨你
,這對我沒有任何傷害」來獲得難以形容的快樂與自由。一旦ä½
 é–‹å§‹è™›å¼µè²å‹¢ï¼Œå•†äººé€šå¸¸æœƒè½‰è€ŒæŽ¥å—著作傳。</p>
+
+<p>
+朋友,自由軟體開發者
,不要重蹈覆轍!如果我們不對我們的軟體使用著作傳保護,我們就是將å
…
¶æœªä¾†ç½®æ–¼ä»»ä½•æ“æœ‰æ›´å¤šè³‡æºè€Œéžé¡§å¿Œçš„人手上。使用著作傳,我們可以捍衛自由,不åƒ
…僅是為了我們,而是為了整個社群。</p>
+</div>
+</div>
+<div class="translators-notes">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
+ </div>
+</div>
+
+<!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.zh-tw.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>請來信到 <a href="mailto:gnu@gnu.org";>&lt;gnu@gnu.org&gt;</a> 
詢問有關自由軟體基金會(FSF)和
+GNU 的一般問題;或者<a href="/contact/">以å…
¶ä»–方式</a>聯絡自由軟體基金會。至於損毀的連結及å…
¶ä»–修正和建議,可以將之寄給 <a
+href="mailto:webmasters@gnu.org";>&lt;webmasters@gnu.org&gt;</a>。</p>
+
+<p>
+<!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to <a href="mailto:web-translators@gnu.org";>
+
+        &lt;web-translators@gnu.org&gt;</a>.</p>
+
+        <p>For information on coordinating and submitting translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+我們努力盡所能提供貼切、品質良善的翻譯。然而,我們無法十å
…¨åç¾Žï¼Œé‚„請將你的意見評述與一般建議寄給 <a
+href="mailto:web-translators@gnu.org";>&lt;web-translators@gnu.org&gt;</a></p><p>請參ç
…§
+<a href="/server/standards/README.translations.html">翻譯讀我 README</a>
+來瞭解協調和提交我們的網頁翻譯相關事宜。</p>
+</div>
+
+<!-- Regarding copyright, in general, standalone pages (as opposed to
+     files generated as part of manuals) on the GNU web server should
+     be under CC BY-ND 4.0.  Please do NOT change or remove this
+     without talking with the webmasters or licensing team first.
+     Please make sure the copyright date is consistent with the
+     document.  For web pages, it is ok to list just the latest year the
+     document was modified, or published.
+     
+     If you wish to list earlier years, that is ok too.
+     Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+     years, as long as each year in the range is in fact a copyrightable
+     year, i.e., a year in which the document was published (including
+     being publicly visible on the web or in a revision control system).
+     
+     There is more detail about copyright years in the GNU Maintainers
+     Information document, www.gnu.org/prep/maintain. -->
+<p>Copyright &copy; 1998, 1999, 2009, 2015, 2020 Richard M. Stallman</p>
+
+<p>本頁面採用<a rel="license"
+href="https://creativecommons.org/licenses/by-nd/4.0/deed.zh_TW";>創用 CC
+姓名標示-禁止改作 4.0 國際</a>條款給予授權。</p>
+
+<!--#include virtual="/server/bottom-notes.zh-tw.html" -->
+<div class="translators-credits">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
+<b>翻譯</b>:黃柏諺 <a href="mailto:s8321414 (at) gmail (dot) 
com">&lt;s8321414
+(at) gmail (dot) com&gt;</a>, 2021.</div>
+
+<p class="unprintable"><!-- timestamp start -->
+更新時間︰
+
+$Date: 2021/04/28 13:00:45 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>

Index: po/x.zh-tw-en.html
===================================================================
RCS file: po/x.zh-tw-en.html
diff -N po/x.zh-tw-en.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ po/x.zh-tw-en.html  28 Apr 2021 13:00:45 -0000      1.1
@@ -0,0 +1,221 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.77 -->
+<title>The X Window System Trap
+- GNU Project - Free Software Foundation</title>
+<meta http-equiv="Keywords"
+      content="GNU, FSF, Free Software Foundation, freedom, Richard Stallman, 
rms, free software movement" />
+<meta http-equiv="Description"
+      content="Richard Stallman discusses the history of the movement to 
develop a free operating system." />
+
+<!--#include virtual="/philosophy/po/x.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<div class="reduced-width">
+<h2>The X Window System Trap</h2>
+
+<address class="byline">by Richard M. Stallman</address>
+<hr class="thin" />
+<div class="article">
+<p>
+To copyleft or not to copyleft?  That is one of the major
+controversies in the free software community.  The idea of copyleft is
+that we should fight fire with fire&mdash;that we should use copyright
+to make sure our code stays free.  The GNU General Public License (GNU
+GPL) is one example of a copyleft license.</p>
+
+<p>
+Some free software developers prefer noncopyleft distribution.
+Noncopyleft licenses such as the XFree86 and
+<a href="/licenses/bsd.html">BSD</a> licenses are based on the idea
+of never saying no to anyone&mdash;not even to someone who seeks to
+use your work as the basis for restricting other people.  Noncopyleft
+licensing does nothing wrong, but it misses the opportunity to
+actively protect our freedom to change and redistribute software.  For
+that, we need copyleft.</p>
+
+<p>
+For many years, the X Consortium was the chief opponent of copyleft.
+It exerted both moral suasion and pressure to discourage free software
+developers from copylefting their programs.  It used moral suasion by
+suggesting that it is not nice to say no.  It used pressure through
+its rule that copylefted software could not be in the X Distribution.</p>
+
+<p>
+Why did the X Consortium adopt this policy?  It had to do with their
+conception of success.  The X Consortium defined success as
+popularity&mdash;specifically, getting computer companies to use the X
+Window System.  This definition put the computer companies in the
+driver's seat: whatever they wanted, the X Consortium had to help
+them get it.</p>
+
+<p>
+Computer companies normally distribute proprietary software.  They
+wanted free software developers to donate their work for such use.  If
+they had asked for this directly, people would have laughed.  But the
+X Consortium, fronting for them, could present this request as an
+unselfish one.  &ldquo;Join us in donating our work to proprietary software
+developers,&rdquo; they said, suggesting that this is a noble form of
+self-sacrifice.  &ldquo;Join us in achieving popularity,&rdquo; they said,
+suggesting that it was not even a sacrifice.</p>
+
+<p>
+But self-sacrifice is not the issue: tossing away the defense that
+copyleft provides, which protects the freedom of the whole community,
+is sacrificing more than yourself.  Those who granted the X
+Consortium's request entrusted the community's future to the goodwill
+of the X Consortium.</p>
+
+<p>
+This trust was misplaced.  In its last year, the X Consortium made a
+plan to restrict the forthcoming X11R6.4 release so that it would not
+be free software.  They decided to start saying no, not only to
+proprietary software developers, but to our community as well.</p>
+
+<p>
+There is an irony here.  If you said yes when the X Consortium asked
+you not to use copyleft, you put the X Consortium in a position to
+license and restrict its version of your program, along with the
+code for the core of X.</p>
+
+<p>
+The X Consortium did not carry out this plan.  Instead it closed down
+and transferred X development to the Open Group, whose staff are now
+carrying out a similar plan.  To give them credit, when I asked them
+to release X11R6.4 under the GNU GPL in parallel with their planned
+restrictive license, they were willing to consider the idea.  (They
+were firmly against staying with the old X11 distribution terms.)
+Before they said yes or no to this proposal, it had already failed for
+another reason: the XFree86 group followed the X Consortium's old
+policy, and will not accept copylefted software.
+</p>
+
+<p>
+In September 1998, several months after X11R6.4 was released with
+nonfree distribution terms, the Open Group reversed its decision and
+rereleased it under the same noncopyleft free software license that
+was used for X11R6.3.  Thus, the Open Group therefore eventually did
+what was right, but that does not alter the general issue.</p>
+
+<p>
+Even if the X Consortium and the Open Group had never planned to
+restrict X, someone else could have done it.  Noncopylefted software
+is vulnerable from all directions; it lets anyone make a nonfree
+version dominant, if he will invest sufficient resources to add
+significantly important features using proprietary code.  Users who
+choose software based on technical characteristics, rather than on
+freedom, could easily be lured to the nonfree version for short-term
+convenience.</p>
+
+<p>
+The X Consortium and Open Group can no longer exert moral suasion by
+saying that it is wrong to say no.  This will make it easier to decide
+to copyleft your X-related software.</p>
+
+<p>
+When you work on the core of X, on programs such as the X server,
+Xlib, and Xt, there is a practical reason not to use copyleft.  The
+X.org group does an important job for the community in maintaining
+these programs, and the benefit of copylefting our changes would be
+less than the harm done by a fork in development.  So it is better to
+work with them, and not copyleft our changes on these programs.
+Likewise for utilities such as <code>xset</code> and <code>xrdb</code>,
+which are close to the
+core of X and do not need major improvements.  At least we know that
+the X.org group has a firm commitment to developing these programs as
+free software.</p>
+
+<p>
+The issue is different for programs outside the core of X:
+applications, window managers, and additional libraries and widgets.
+There is no reason not to copyleft them, and we should copyleft them.</p>
+
+<p>
+In case anyone feels the pressure exerted by the criteria for
+inclusion in the X distributions, the GNU Project will undertake to
+publicize copylefted packages that work with X.  If you would like to
+copyleft something, and you worry that its omission from the X
+distribution will impede its popularity, please ask us to help.</p>
+
+<p>
+At the same time, it is better if we do not feel too much need for
+popularity.  When a businessman tempts you with &ldquo;more
+popularity,&rdquo; he may try to convince you that his use of your
+program is crucial to its success.  Don't believe it!  If your program
+is good, it will find many users anyway; you don't need to feel
+desperate for any particular users, and you will be stronger if you do
+not.  You can get an indescribable sense of joy and freedom by
+responding, &ldquo;Take it or leave it&mdash;that's no skin off my
+back.&rdquo; Often the businessman will turn around and accept the
+program with copyleft, once you call the bluff.</p>
+
+<p>
+Friends, free software developers, don't repeat old mistakes!  If we
+do not copyleft our software, we put its future at the mercy of anyone
+equipped with more resources than scruples.  With copyleft, we can
+defend freedom, not just for ourselves, but for our whole
+community.</p>
+</div>
+</div>
+</div><!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>Please send general FSF &amp; GNU inquiries to
+<a href="mailto:gnu@gnu.org";>&lt;gnu@gnu.org&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:webmasters@gnu.org";>&lt;webmasters@gnu.org&gt;</a>.</p>
+
+<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to <a href="mailto:web-translators@gnu.org";>
+        &lt;web-translators@gnu.org&gt;</a>.</p>
+
+        <p>For information on coordinating and submitting translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+Please see the <a
+href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting translations
+of this article.</p>
+</div>
+
+<!-- Regarding copyright, in general, standalone pages (as opposed to
+     files generated as part of manuals) on the GNU web server should
+     be under CC BY-ND 4.0.  Please do NOT change or remove this
+     without talking with the webmasters or licensing team first.
+     Please make sure the copyright date is consistent with the
+     document.  For web pages, it is ok to list just the latest year the
+     document was modified, or published.
+     
+     If you wish to list earlier years, that is ok too.
+     Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+     years, as long as each year in the range is in fact a copyrightable
+     year, i.e., a year in which the document was published (including
+     being publicly visible on the web or in a revision control system).
+     
+     There is more detail about copyright years in the GNU Maintainers
+     Information document, www.gnu.org/prep/maintain. -->
+
+<p>Copyright &copy; 1998, 1999, 2009, 2015, 2020 Richard M. Stallman</p>
+
+<p>This page is licensed under a <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/4.0/";>Creative
+Commons Attribution-NoDerivatives 4.0 International License</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2021/04/28 13:00:45 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>



reply via email to

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