diff options
author | Christian Grothoff <christian@grothoff.org> | 2020-10-11 13:29:45 +0200 |
---|---|---|
committer | Christian Grothoff <christian@grothoff.org> | 2020-10-11 13:29:45 +0200 |
commit | 1ae0306a3cf2ea27f60b2d205789994d260c2cce (patch) | |
tree | 53117a55c27601e92172ea82f1d8cd11d355c06c /talermerchantdemos/blog/articles/zh/why-copyleft.html | |
parent | 2e665813a44988bfd906c0fab773f82652047841 (diff) | |
download | taler-merchant-demos-1ae0306a3cf2ea27f60b2d205789994d260c2cce.tar.gz taler-merchant-demos-1ae0306a3cf2ea27f60b2d205789994d260c2cce.tar.bz2 taler-merchant-demos-1ae0306a3cf2ea27f60b2d205789994d260c2cce.zip |
add i18n FSFS
Diffstat (limited to 'talermerchantdemos/blog/articles/zh/why-copyleft.html')
-rw-r--r-- | talermerchantdemos/blog/articles/zh/why-copyleft.html | 132 |
1 files changed, 132 insertions, 0 deletions
diff --git a/talermerchantdemos/blog/articles/zh/why-copyleft.html b/talermerchantdemos/blog/articles/zh/why-copyleft.html new file mode 100644 index 0000000..1295037 --- /dev/null +++ b/talermerchantdemos/blog/articles/zh/why-copyleft.html @@ -0,0 +1,132 @@ +<!--#set var="ENGLISH_PAGE" value="/philosophy/why-copyleft.en.html" --> + +<!--#include virtual="/server/header.zh-tw.html" --> +<!-- Parent-Version: 1.86 --> + +<!-- This file is automatically generated by GNUnited Nations! --> +<title>為什麼要用著作傳 (Copyleft)? - GNU 專案 - 自由軟體基金會</title> + +<!--#include virtual="/philosophy/po/why-copyleft.translist" --> +<!--#include virtual="/server/banner.zh-tw.html" --> +<h2>為什麼要用著作傳 (Copyleft)?</h2> + +<p> +<cite>「當要捍衛他人的自由時,躺下來休息與什麼都不做是種懦弱的行為,可不是謙卑的表現。」</cite> +</p> + +<p> +在 GNU 專案中,我們通常建議人們使用如 GNU GPL 之類的<a href="/licenses/copyleft.html">著作傳 +[唸法:ㄔㄨㄢˊ] (Copyleft) +</a>式授權條款,而非其他寬容式非著作傳自由軟體授權條款。我們並沒有措辭嚴厲地反對前述這些非著作傳的授權條款——事實上,我們在特定情況下偶爾會推薦這類授權——但是,這類授權條款的擁護者通常激烈反對 +<abbr title="General Public License">GPL</abbr>。 +</p> + +<p> +在其中一種反對論點中,某些人聲稱他使用其中一種 BSD +授權條款屬於「謙卑的行為」:「除了要寫上我的貢獻以外,我沒有要求使用我程式碼的人任何事情。」他將這種提及其貢獻的法律要求認為是「謙卑」,實為對這二字的曲解;除此之外,這裡還必須考慮更深的事情。 +</p> + +<p> +所謂謙卑,是放下你所擁有的自身利益;但是,當你不用著作傳授權把程式碼傳下去時,你所拋棄的利益可不只有你自己的。那些在非自由軟體中使用你程式碼的人,一併否認了其他人的自由,所以一旦你允許他們這麼做,那麼你就無法捍衛其他人的自由了。當要捍衛他人的自由時,躺下來休息與什麼事都不做是種懦弱的行為,可不是謙卑的表現。 +</p> + +<p> +採用<a href="/licenses/bsd.html">任一種 BSD +授權條款</a>,或者其他放任、寬容式的授權條款,來發行您的程式碼並沒有錯;那個程式仍屬於自由軟體,它也仍對我們社群有所貢獻。但這個力道相當薄弱,在大多數情況下,這並不是促進使用者自由分享軟體與修改軟體的最佳方式。 +</p> + +<p> +以下是對自由世界造成重大傷害的自由軟體之非自由修改版的案例。</p> + +<ul> +<li>那些採非著作傳式授權條款發行 LLVM 的人,<a +href="https://www.anandtech.com/show/5238/nvidia-releases-cuda-41-cuda-goes-llvm-and-open-source-kind-of">讓 +nVidia 得以發行高品質的非自由編譯器</a>給他們家的 GPU +使用,並同時將其指令集保為祕密不宣。因此,一旦沒有大型的逆向工程作業,我們就無法為該平臺編寫自由的編譯器。LLVM +的非自由修改版是這些機器僅能使用的編譯器,而這個情況很可能會一直持續下去。</li> + +<li>Intel 在其現代處理器的管理引擎 (Management Engine) 後門中使用了<a +href="http://www.tomshardware.com/news/google-removing-minix-management-engine-intel,35876.html">專有版本的 +MINIX 系統</a>;MINIX 是自由軟體,但並未採用著作傳式授權。</li> +</ul> + +<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"><gnu@gnu.org></a> 詢問有關自由軟體基金會(FSF)和 +GNU 的一般問題;或者<a href="/contact/">以其他方式</a>聯絡自由軟體基金會。至於損毀的連結及其他修正和建議,可以將之寄給 <a +href="mailto:webmasters@gnu.org"><webmasters@gnu.org></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"> + + <web-translators@gnu.org></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"><web-translators@gnu.org></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 © 2003, 2007, 2008, 2013, 2017, 2018, 2020 Free Software +Foundation, Inc.</p> + +<p>本頁面採用<a rel="license" +href="https://creativecommons.org/licenses/by-nd/4.0/deed.zh_TW">創用 CC +姓名標示-禁止改作 4.0 國際</a>條款給予授權。</p> + +<!--#include virtual="/server/bottom-notes.zh-tw.html" --> +<div class="translators-credits"> + +<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.--> +<b>翻譯</b>:黃柏諺 <a href="mailto:s8321414 (at) gmail (dot) com"><s8321414 +(at) gmail (dot) com></a>, 2018.<br /> +<b>校對</b>:曾政嘉 <a href="mailto:zerngjia (at) gmail (dot) com"><zerngjia +(at) gmail (dot) com></a>, 2018.</div> + +<p class="unprintable"><!-- timestamp start --> +更新時間︰ + +$Date: 2020/07/05 14:01:37 $ + +<!-- timestamp end --> +</p> +</div> +</div> +<!-- for class="inner", starts in the banner include --> +</body> +</html> |