www/licenses po/rms-why-gplv3.translist po/rms-...

[GNUN]

CVSROOT:        /web/www
Module name:    www
Changes by:     GNUN <gnun>     21/05/21 09:29:15

Modified files:
        licenses/po    : rms-why-gplv3.translist rms-why-gplv3.zh-tw.po 
Added files:
        licenses       : rms-why-gplv3.zh-tw.html 
        licenses/po    : rms-why-gplv3.zh-tw-en.html 

Log message:
        Automatic update by GNUnited Nations.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/rms-why-gplv3.zh-tw.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/rms-why-gplv3.translist?cvsroot=www&r1=1.16&r2=1.17
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/rms-why-gplv3.zh-tw.po?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/rms-why-gplv3.zh-tw-en.html?cvsroot=www&rev=1.1

Patches:
Index: po/rms-why-gplv3.translist
===================================================================
RCS file: /web/www/www/licenses/po/rms-why-gplv3.translist,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- po/rms-why-gplv3.translist  26 May 2020 08:32:08 -0000      1.16
+++ po/rms-why-gplv3.translist  21 May 2021 13:29:15 -0000      1.17
@@ -12,6 +12,7 @@
 <span dir="ltr">[ru]&nbsp;<a lang="ru" hreflang="ru" 
href="/licenses/rms-why-gplv3.ru.html">русский</a> &nbsp;</span>
 <span dir="ltr">[tr]&nbsp;<a lang="tr" hreflang="tr" 
href="/licenses/rms-why-gplv3.tr.html">Türkçe</a> &nbsp;</span>
 <span dir="ltr">[zh-cn]&nbsp;<a lang="zh-cn" hreflang="zh-cn" 
href="/licenses/rms-why-gplv3.zh-cn.html">简体中文</a> &nbsp;</span>
+<span dir="ltr">[zh-tw]&nbsp;<a lang="zh-tw" hreflang="zh-tw" 
href="/licenses/rms-why-gplv3.zh-tw.html">繁體中文</a> &nbsp;</span>
 </p>
 </div>' -->
 <link rel="alternate" type="text/html" href="/licenses/rms-why-gplv3.html" 
hreflang="x-default" />
@@ -25,4 +26,5 @@
 <link rel="alternate" type="text/html" lang="ru" hreflang="ru" 
href="/licenses/rms-why-gplv3.ru.html" title="русский" />
 <link rel="alternate" type="text/html" lang="tr" hreflang="tr" 
href="/licenses/rms-why-gplv3.tr.html" title="Türkçe" />
 <link rel="alternate" type="text/html" lang="zh-cn" hreflang="zh-cn" 
href="/licenses/rms-why-gplv3.zh-cn.html" title="简体中文" />
+<link rel="alternate" type="text/html" lang="zh-tw" hreflang="zh-tw" 
href="/licenses/rms-why-gplv3.zh-tw.html" title="繁體中文" />
 <!-- end translist file -->

Index: po/rms-why-gplv3.zh-tw.po
===================================================================
RCS file: /web/www/www/licenses/po/rms-why-gplv3.zh-tw.po,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- po/rms-why-gplv3.zh-tw.po   21 May 2021 13:16:38 -0000      1.1
+++ po/rms-why-gplv3.zh-tw.po   21 May 2021 13:29:15 -0000      1.2
@@ -10,10 +10,10 @@
 "PO-Revision-Date: 2021-05-21 20:42+0800\n"
 "Last-Translator: Jeff Huang <s8321414@gmail.com>\n"
 "Language-Team: Traditional Chinese <www-zh-tw-translators@gnu.org>\n"
+"Language: zh_TW\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"Language: zh_TW\n"
 "X-Generator: Lokalize 21.04.1\n"
 "Plural-Forms: nplurals=1; plural=0;\n"
 
@@ -36,10 +36,9 @@
 "from GPL version 2.  This article explains why upgrading the license is "
 "important."
 msgstr ""
-"<a href=\"/licenses/gpl.html\">第三版的 GNU 通用公眾授權<"
-"/a>（GNU GPL，以下簡稱 GPLv3）已經發佈了，並讓自由軟體包
可以"
-"從 GPL 第二版（以下簡稱 GPLv2ï¼‰å‡ç´šä¸Šä¾†ã€‚é€™ç¯‡æ–‡ç« 
會解釋會什麼升級授權條款"
-"很重要。"
+"<a href=\"/licenses/gpl.html\">第三版的 GNU 通用公眾授權</a>（GNU 
GPL，以下簡"
+"稱 GPLv3）已經發佈了，並讓自由軟體包可以從 GPL 
第二版（以下簡稱 GPLv2）升級上"
+"ä¾†ã€‚é€™ç¯‡æ–‡ç« æœƒè§£é‡‹æœƒä»€éº¼å‡ç´šæŽˆæ¬Šæ¢æ¬¾å¾ˆé‡è¦ã€‚"
 
 #. type: Content of: <p>
 msgid ""
@@ -48,10 +47,9 @@
 "programs remain under GPLv2 while others advance to GPLv3.  These two "
 "licenses are incompatible, but that isn't a fundamental problem."
 msgstr ""
-"首先，升級不是必要的，只是一種選擇。"
-"GPLv2 仍然可以使用。若有程式使用 GPLv2，"
-"而其他的程式正在使用 GPLv3，也不會發生問題。"
-"é›–ç„¶é€™å…©å€‹æŽˆæ¬Šæ¢æ¬¾ä¸¦ä¸ç›¸å®¹ï¼Œä½†é€™ä¸¦ä¸æ˜¯æ ¹æœ¬çš„å•é¡Œã€‚"
+"首先，升級不是必要的，只是一種選擇。GPLv2 
仍然可以使用。若有程式使用 GPLv2，"
+"而其他的程式正在使用 GPLv3，也不會發生問題。雖然這å…
©å€‹æŽˆæ¬Šæ¢æ¬¾ä¸¦ä¸ç›¸å®¹ï¼Œä½†é€™"
+"ä¸¦ä¸æ˜¯æ ¹æœ¬çš„å•é¡Œã€‚"
 
 #. type: Content of: <p>
 msgid ""
@@ -64,14 +62,11 @@
 "to GPLv3, but it wouldn't do the job, because GPLv2 would need a similar "
 "clause."
 msgstr ""
-"我們說 GPLv2 和 GPLv3 不相容，是指我們沒有"
-"任何合法的方法能將 GPLv2 和 GPLv3 的程式碼整合成一個"
-"ç¨‹å¼ã€‚é€™æ˜¯å› ç‚º GPLv2 和 GPLv3 
都是著作傳授權條款，且各自都有如此的聲明："
-"ã€Œå¦‚æžœä½ æŠŠé€™æ®µç¨‹å¼ç¢¼æ‡‰ç”¨åœ¨æ›´å¤§çš„ç¨‹å¼ä¹‹ä¸­ï¼Œ"
-"é‚£è©²ç¨‹å¼ä¹Ÿæœƒé©ç”¨é€™é …æŽˆæ¬Šæ¢æ¬¾ã€‚ã€å› æ­¤"
-"無法相容。我們可以在 GPLv3 中聲明 GPLv3 與 GPLv2 相容，"
-"ä½†é€™ä»ç„¶ç„¡æ³•æ”¹è®Šä»–å€‘ç„¡æ³•ç›¸å®¹çš„æƒ…æ³ï¼Œå› ç‚º GPLv2 
也同時需要作出類似的"
-"聲明。"
+"我們說 GPLv2 和 GPLv3 
不相容，是指我們沒有任何合法的方法能將 GPLv2 和 GPLv3 "
+"çš„ç¨‹å¼ç¢¼æ•´åˆæˆä¸€å€‹ç¨‹å¼ã€‚é€™æ˜¯å› ç‚º GPLv2 和 GPLv3 
都是著作傳授權條款，且各自都"
+"æœ‰å¦‚æ­¤çš„è²æ˜Žï¼šã€Œå¦‚æžœä½ 
把這段程式碼應用在更大的程式之中，那該程式也會適用這é 
…"
+"æŽˆæ¬Šæ¢æ¬¾ã€‚ã€å› æ­¤ç„¡æ³•ç›¸å®¹ã€‚æˆ‘å€‘å¯ä»¥åœ¨ GPLv3 中聲明 GPLv3 
與 GPLv2 相容，但這仍"
+"ç„¶ç„¡æ³•æ”¹è®Šä»–å€‘ç„¡æ³•ç›¸å®¹çš„æƒ…æ³ï¼Œå› ç‚º GPLv2 
也同時需要作出類似的聲明。"
 
 #. type: Content of: <p>
 msgid ""
@@ -84,22 +79,20 @@
 "because they are all separate programs.  Likewise, if Bash and GCC move to "
 "GPLv3, while Linux remains under GPLv2, there is no conflict."
 msgstr ""
-"幸好授權條款不相容的問題只會在您想要把å…
©å€‹ä¸åŒçš„程式連結"
-"或合併成一個程式時才會發生。"
-"然而，在作業系統中同時執行 GPLv3 授權的程式和 GPLv2 授權"
-"的程式是沒有問題的。例如，TeX 授權條款"
-"和 Apache 授權條款與 GPLv2 
不相容，但這並不能阻擋我們在與 Linux、"
-"Bash 與 GCC 相同的系統上執行 TeX 與 Apache。這是"
-"å› ç‚ºå®ƒå€‘éƒ½æ˜¯ç¨ç«‹çš„ç¨‹å¼ã€‚åŒæ¨£çš„ï¼Œå¦‚æžœ Bash 和 GCC 
都升級為 GPLv3"
-"，但 Linux æ ¸å¿ƒä»ä½¿ç”¨ GPLv2 也不會發生衝突。"
+"幸好授權條款不相容的問題只會在您想要把å…
©å€‹ä¸åŒçš„程式連結或合併成一個程式時才"
+"會發生。然而，在作業系統中同時執行 GPLv3 授權的程式和 
GPLv2 授權的程式是沒有"
+"問題的。例如，TeX 授權條款和 Apache 授權條款與 GPLv2 
不相容，但這並不能阻擋我"
+"們在與 Linux、Bash 與 GCC 相同的系統上執行 TeX 與 
Apacheã€‚é€™æ˜¯å› ç‚ºå®ƒå€‘éƒ½æ˜¯ç¨"
+"立的程式。同樣的，如果 Bash 和 GCC 都升級為 GPLv3，但 Linux 
æ ¸å¿ƒä»ä½¿ç”¨ GPLv2 "
+"也不會發生衝突。"
 
 #. type: Content of: <p>
 msgid ""
 "Keeping a program under GPLv2 won't create problems.  The reason to migrate "
 "is because of the existing problems that GPLv3 will address."
 msgstr ""
-"讓程式繼續使用 GPLv2 ä¸¦ä¸æœƒé€ æˆä»»ä½•å•é¡Œã€‚å‡ç´šçš„ç†ç”±"
-"是 GPLv3 可以解決一些現有的問題。"
+"讓程式繼續使用 GPLv2 ä¸¦ä¸æœƒé€ æˆä»»ä½•å•é¡Œã€‚å‡ç´šçš„ç†ç”±æ˜¯ 
GPLv3 可以解決一些現有"
+"的問題。"
 
 #. type: Content of: <p>
 msgid ""
@@ -112,13 +105,11 @@
 "manufacturers of these computers take advantage of the freedom that free "
 "software provides, but they don't let you do likewise."
 msgstr ""
-"GPLv3 阻止的一個主要危險是 Tivoization。Tivoization 的意思是"
-"特定的「裝置」（其中帶有電腦）包
含了您無法有效更改的 GPL 授權"
-"è»Ÿé«”ï¼Œå› ç‚ºè£ç½®åµæ¸¬åˆ°è»Ÿé«”è¢«è®Šæ›´æ™‚å°±æœƒé—œæ©Ÿã€‚"
-"Tivoization çš„å‹•æ©Ÿé€šå¸¸æ˜¯è£½é€ å•†çŸ¥é“è»Ÿé«”"
-"æœ‰æŸäº›äººå€‘æœƒæƒ³è¦ä¿®æ”¹çš„åŠŸèƒ½ï¼Œä½†è£½é€ å•†"
-"å°±æ˜¯ä¸å¸Œæœ›äººå€‘ä¿®æ”¹ã€‚è£½é€ å•†åˆ©ç”¨äº†è‡ªç”±"
-"軟體提供的自由，卻不讓使用者也這麼做。"
+"GPLv3 阻止的一個主要危險是 Tivoization。Tivoization 
的意思是特定的「裝置」"
+"（其中帶有電腦）包含了您無法有效更改的 GPL 
æŽˆæ¬Šè»Ÿé«”ï¼Œå› ç‚ºè£ç½®åµæ¸¬åˆ°è»Ÿé«”è¢«è®Šæ›´"
+"時就會關機。Tivoization çš„å‹•æ©Ÿé€šå¸¸æ˜¯è£½é€ 
商知道軟體有某些人們會想要修改的功"
+"èƒ½ï¼Œä½†è£½é€ å•†å°±æ˜¯ä¸å¸Œæœ›äººå€‘ä¿®æ”¹ã€‚è£½é€ 
商利用了自由軟體提供的自由，卻不讓使用者"
+"也這麼做。"
 
 #. type: Content of: <p>
 msgid ""
@@ -129,12 +120,10 @@
 "isn't freedom.  Freedom means <em>you</em> control what your software does, "
 "not merely that you can beg or threaten someone else who decides for you."
 msgstr ""
-"æŸäº›äººèªç‚ºè‡ªç”±å¸‚å ´çš„ç«¶çˆ­æœƒè®“è£ç½®ä¸Šè¼ƒå·®çš„åŠŸèƒ½"
-"è™•æ–¼è¼ƒä½Žçš„æ°´æº–ã€‚æˆ–è¨±å…‰é ç«¶çˆ­å¯ä»¥é¿å…"
-"ã€Œæ¯é€±äºŒä¸‹åˆä¸€é»žè‡³äº”é»žå¿…é ˆé—œæ©Ÿã€é€™é¡žéš¨æ„çš„ã€"
-"沒道理的糟糕功能。但即便如此，擁有裝置的人仍"
-"無法自由的選擇。自由應該是<em>您</em>å¯ä»¥æŽ§åˆ¶ä½ 
的程式能做什麼，"
-"而不用透過乞求他人或脅迫他人的方式。"
+"某些人認為自由市å 
´çš„ç«¶çˆ­æœƒè®“è£ç½®ä¸Šè¼ƒå·®çš„åŠŸèƒ½è™•æ–¼è¼ƒä½Žçš„æ°´æº–ã€‚æˆ–è¨±å…‰é 
競爭可以"
+"避免「每週二下午一點至五點必é 
ˆé—œæ©Ÿã€é€™é¡žéš¨æ„çš„、沒道理的糟糕功能。但即便如"
+"此，擁有裝置的人仍無法自由的選擇。自由應該是<em>您</em>可以控制ä½
 的程式能做什"
+"麼，而不用透過乞求他人或脅迫他人的方式。"
 
 #. type: Content of: <p>
 msgid ""
@@ -149,16 +138,13 @@
 "buying non-DRM players because none are available.  No matter how many "
 "products you can choose from, they all have equivalent digital handcuffs."
 msgstr ""
-"在數位限制管理 (DRM) 中 &mdash; 這是限制您使用"
-"自己電腦中資料的卑劣功能 &mdash; 競爭無濟於事"
-"ï¼Œå› ç‚ºç›¸é—œçš„ç«¶çˆ­æ˜¯è¢«ç¦æ­¢çš„ã€‚"
-"諸如《數位千禧年著作權法》之類的法律表示"
-"，在美國和許多其他國家，如果您沒有按照 DVD 
陰謀的官方規則"
-"（其網站為 <a 
href=\"http://www.dvdcca.org/\";>http://www.dvdcca.org/</a>，但是"
-"規則看來並沒有在此發佈）散佈限制使用者的 DVD 
播放器，那就是違法的。"
-"大眾無法透過購買非 DRM 的播放器來拒絕 DRM"
-"ï¼Œå› ç‚ºæ²’æœ‰é€™æ¨£çš„æ’­æ”¾å™¨ã€‚ç„¡è«–æœ‰å¤šå°‘ç¨®ç”¢å“"
-"供您選擇，它們都是帶有數位枷鎖的。"
+"在數位限制管理 (DRM) 中 &mdash; 這是限制您使用自己電è…
¦ä¸­è³‡æ–™çš„卑劣功能 "
+"&mdash; ç«¶çˆ­ç„¡æ¿Ÿæ–¼äº‹ï¼Œå› 
為相關的競爭是被禁止的。諸如《數位千禧年著作權法》之"
+"類的法律表示，在美國和許多其他國家，如果您沒有按照 
DVD 陰謀的官方規則（其網站"
+"為 <a 
href=\"http://www.dvdcca.org/\";>http://www.dvdcca.org/</a>，但是規則看"
+"來並沒有在此發佈）散佈限制使用者的 DVD 
播放器，那就是違法的。大眾無法透過購買"
+"非 DRM 的播放器來拒絕 DRMï¼Œå› 
為沒有這樣的播放器。無論有多少種產品供您選擇，它"
+"們都是帶有數位枷鎖的。"
 
 #. type: Content of: <p>
 msgid ""
@@ -169,11 +155,10 @@
 "of your copy was to add them.  Tivoization is the way they deny you that "
 "freedom; to protect your freedom, GPLv3 forbids tivoization."
 msgstr ""
-"GPLv3 確保您可以自由移除這些限制。其並未禁止 DRM 或"
-"å…¶ä»–åŠŸèƒ½ã€‚å…¶ä¸¦ä¸é™åˆ¶æ‚¨ç‚ºæ‚¨çš„ç¨‹å¼å¢žåŠ æˆ–åˆªé™¤ä»»ä½•"
-"重要功能。反之，其確保了您能像您副本的散佈者"
-"新增討厭的功能一樣刪除那些功能。 Tivoization 
就是他們阻止您"
-"ç²å¾—è‡ªç”±çš„æ–¹å¼ã€‚ç‚ºäº†ä¿éšœä½ çš„è‡ªç”±ï¼ŒGPLv3 禁止 
Tivoization。"
+"GPLv3 確保您可以自由移除這些限制。其並未禁止 DRM 或å…
¶ä»–功能。其並不限制您為您"
+"çš„ç¨‹å¼å¢žåŠ æˆ–åˆªé™¤ä»»ä½•é‡è¦åŠŸèƒ½ã€‚åä¹‹ï¼Œå…
¶ç¢ºä¿äº†æ‚¨èƒ½åƒæ‚¨å‰¯æœ¬çš„散佈者新增討厭的功"
+"能一樣刪除那些功能。 Tivoization 
å°±æ˜¯ä»–å€‘é˜»æ­¢æ‚¨ç²å¾—è‡ªç”±çš„æ–¹å¼ã€‚ç‚ºäº†ä¿éšœä½ çš„è‡ª"
+"由，GPLv3 禁止 Tivoization。"
 
 #. type: Content of: <p>
 msgid ""
@@ -181,9 +166,8 @@
 "be expected, even occasionally.  GPLv3 tolerates tivoization only for "
 "products that are almost exclusively meant for businesses and organizations."
 msgstr ""
-"對 tivoization 的禁止適用於任何可能會被消費者使用"
-"的產品，即便只是偶爾用到也一樣。GPLv3 只允許 tivoization 
出現"
-"在那些幾乎只用於企業與組織的產品。"
+"對 tivoization 的禁止適用於任何可能會被消費者
使用的產品，即便只是偶爾用到也一"
+"樣。GPLv3 只允許 tivoization 
出現在那些幾乎只用於企業與組織的產品。"
 
 #. type: Content of: <p>
 msgid ""
@@ -193,11 +177,9 @@
 "pact to try to achieve that.  The deal offers rather limited protection from "
 "Microsoft patents to Novell's customers."
 msgstr ""
-"GPLv3 要對抗的另一個威脅是像 Novell-Microsoft 協定"
-"之類的專利交易。微軟用它擁有的上千個專利讓使用者"
-"付錢給微軟來取得執行 GNU/Linux 的權力，並企圖透"
-"過這類的專利交易來達到目的。此交易對 Novell 使用者"
-"使用微軟專利的保護非常有限。"
+"GPLv3 要對抗的另一個威脅是像 Novell-Microsoft 
協定之類的專利交易。微軟用它擁"
+"有的上千個專利讓使用者付錢給微軟來取得執行 GNU/Linux 
的權力，並企圖透過這類的"
+"專利交易來達到目的。此交易對 Novell 使用者
使用微軟專利的保護非常有限。"
 
 #. type: Content of: <p>
 msgid ""
@@ -206,9 +188,8 @@
 "protection to the whole community.  In order to take advantage of this "
 "protection, programs need to use GPLv3."
 msgstr ""
-"微軟在 Novell-Microsoft 的交易上仍犯了集少數的錯誤，而 
GPLv3 將"
-"用來向微軟反擊，從而將å…
¶å°ˆåˆ©ä¿è­·æ“´å¤§åˆ°æ•´å€‹ç¤¾ç¾¤ã€‚為了取得這類"
-"ä¿è­·ï¼Œç¨‹å¼å¿…é ˆä½¿ç”¨ GPLv3。"
+"微軟在 Novell-Microsoft 的交易上仍犯了集少數的錯誤，而 
GPLv3 將用來向微軟反"
+"擊，從而將å…
¶å°ˆåˆ©ä¿è­·æ“´å¤§åˆ°æ•´å€‹ç¤¾ç¾¤ã€‚為了取得這類保護，程式必é 
ˆä½¿ç”¨ GPLv3。"
 
 #. type: Content of: <p>
 msgid ""
@@ -218,11 +199,9 @@
 "Microsoft's future attempts to make redistributors collect Microsoft "
 "royalties from the program's users."
 msgstr ""
-"微軟的律師們並不笨，下一次他們可能會設法避開"
-"é‚£äº›å¤±èª¤ã€‚å› æ­¤ï¼ŒGPLv3 讓他們不再有「下次」"
-"的機會。使用 GPLv3 發布的程式可以保護其免受"
-"微軟將來試圖讓轉散發者從程式的使用者那裡"
-"收取微軟專利費用的嘗試。"
+"微軟的律師們並不笨，下一次他們可能會設法避開那些失誤。å›
 此，GPLv3 讓他們不再"
+"有「下次」的機會。使用 GPLv3 發布的程式可以保護其å…
å—微軟將來試圖讓轉散發者從"
+"程式的使用者那裡收取微軟專利費用的嘗試。"
 
 #. type: Content of: <p>
 msgid ""
@@ -232,11 +211,9 @@
 "won't sue them, or the people they redistribute copies to, for patent "
 "infringement."
 msgstr ""
-"GPLv3 還提供使用者來自程式貢獻者與"
-"轉散發者明確的專利保護。使用 GPLv2"
-"，使用者則僅能依賴潛在的專利授權"
-"來確保向其提供副本的公司不會對他們提告"
-"，或是對轉散發其副本的人們提告專利侵權。"
+"GPLv3 還提供使用者來自程式貢獻者與轉散發者
明確的專利保護。使用 GPLv2，使用者"
+"則僅能依賴潛在的專利授權來確保向其提供副本的å…
¬å¸ä¸æœƒå°ä»–們提告，或是對轉散發"
+"其副本的人們提告專利侵權。"
 
 #. type: Content of: <p>
 msgid ""
@@ -252,15 +229,12 @@
 "those patents to bully smaller developers.  Patents already obstruct free "
 "software development."
 msgstr ""
-"GPLv3 中的明確專利授權條款並未如我們所想要的"
-"程度。理想的情況是，我們希望每個 GPL 程式碼的轉散發者"
-"èˆ‡éžè½‰æ•£ç™¼è€…éƒ½æ”¾æ£„å…¨éƒ¨çš„è»Ÿé«”å°ˆåˆ©ï¼Œå› 
為本來就不該有軟體專利。"
-"軟體專利是一套惡毒且荒謬的體系，它讓所有開發者
都面臨"
-"è¢«ç´ æ˜§å¹³ç”Ÿçš„å…¬å¸æå‘Šçš„é¢¨éšªï¼Œç•¶ç„¶ä¹ŸåŒ…å«è¢«åŒé ˜åŸŸçš„è¶…
級大公司"
-"起訴的風險。大型軟體通常都結合了成千上萬個想法，"
-"所以其中的數百個想法已經被申請成專利並不意外。"
-"超級大公司掌握上千個專利，並且用那些專利來"
-"霸凌其他弱小的開發者。專利已在阻撓自由軟體的開發。"
+"GPLv3 
中的明確專利授權條款並未如我們所想要的程度。理想的情
況是，我們希望每個 "
+"GPL 程式碼的轉散發者與非轉散發者都放棄å…
¨éƒ¨çš„è»Ÿé«”å°ˆåˆ©ï¼Œå› 為本來就不該有軟體專"
+"利。軟體專利是一套惡毒且荒謬的體系，它讓所有開發者
éƒ½é¢è‡¨è¢«ç´ æ˜§å¹³ç”Ÿçš„å…¬å¸æå‘Š"
+"çš„é¢¨éšªï¼Œç•¶ç„¶ä¹ŸåŒ…å«è¢«åŒé ˜åŸŸçš„è¶…ç´šå¤§å…
¬å¸èµ·è¨´çš„風險。大型軟體通常都結合了成千上"
+"萬個想法，所以å…
¶ä¸­çš„數百個想法已經被申請成專利並不意外。超級大å…
¬å¸æŽŒæ¡ä¸Šåƒå€‹"
+"專利，並且用那些專利來霸凌其他弱小的開發者
。專利已在阻撓自由軟體的開發。"
 
 #. type: Content of: <p>
 msgid ""
@@ -272,14 +246,11 @@
 "software development safe from patents.  If we tried to do this with GPLv3, "
 "it would fail."
 msgstr ""
-"確保軟體開發安全的唯一方法就是廢除軟體"
-"å°ˆåˆ©ã€‚æˆ‘å€‘å¸Œæœ›å°‡ä¾†é€™å€‹ç›®æ¨™èƒ½å¤ 
實現。但是我們無法透過"
-"軟體的授權條款來實現這個目的。任何一個程式，無論å…
¶æ˜¯å¦"
-"為自由軟體，都會被不相關的軟體專利持有者幹掉，"
-"而軟體授權條款並不能使其倖免於難。只有透過法院的"
-"判決或是專利法的改革才能讓軟體開發者免除專利的"
-"風險。如果我們試著用 GPLv3 來改變現狀，"
-"那必然會失敗。"
+"確保軟體開發安å…
¨çš„å”¯ä¸€æ–¹æ³•å°±æ˜¯å»¢é™¤è»Ÿé«”å°ˆåˆ©ã€‚æˆ‘å€‘å¸Œæœ›å°‡ä¾†é€™å€‹ç›®æ¨™èƒ½å¤ 
實現。但"
+"是我們無法透過軟體的授權條款來實現這個目的。任何一個程式，無論å
…¶æ˜¯å¦ç‚ºè‡ªç”±è»Ÿ"
+"體，都會被不相關的軟體專利持有者
幹掉，而軟體授權條款並不能使其倖免於難。只有"
+"透過法院的判決或是專利法的改革才能讓軟體開發者å…
é™¤å°ˆåˆ©çš„風險。如果我們試著用 "
+"GPLv3 來改變現狀，那必然會失敗。"
 
 #. type: Content of: <p>
 msgid ""
@@ -291,12 +262,10 @@
 "doesn't include you.&rdquo; It also stops them from colluding with other "
 "patent holders to do this."
 msgstr ""
-"å› æ­¤ï¼ŒGPLv3 試圖限制並疏導這種危險。具體來說，我們"
-"是在盡力拯救自由軟體，讓自由軟體不會落入生不如死的"
-"地步：亦即透過專利變成專有軟體。GPLv3 明確的專利"
-"授權條款可確保使用 GPL 賦予使用者四種自由的公司"
-"不能反悔並使用其專利告訴某些使用者「這並不包
含您。」"
-"並同時阻止了他們與其他專利持有者共謀。"
+"å› æ­¤ï¼ŒGPLv3 試圖限制並疏導這種危險。å…
·é«”來說，我們是在盡力拯救自由軟體，讓自"
+"由軟體不會落å…
¥ç”Ÿä¸å¦‚死的地步：亦即透過專利變成專有軟體。GPLv3 
明確的專利授權"
+"條款可確保使用 GPL 賦予使用者四種自由的å…
¬å¸ä¸èƒ½åæ‚”並使用其專利告訴某些使用者"
+"「這並不包含您。」並同時阻止了他們與其他專利持有者å…
±è¬€ã€‚"
 
 #. type: Content of: <p>
 msgid ""
@@ -304,9 +273,8 @@
 "termination, support for BitTorrent, and compatibility with the Apache "
 "license.  All in all, plenty of reason to upgrade."
 msgstr ""
-"GPLv3 的其他優點包含了更國際化、更溫和的"
-"中止授權、支援 BitTorrent、與 Apache 授權"
-"æ¢æ¬¾ç›¸å®¹ã€‚ç¸½ä¹‹ï¼Œæœ‰è¶³å¤ çš„ç†ç”±å‡ç´šã€‚"
+"GPLv3 的其他優點包
含了更國際化、更溫和的中止授權、支援 BitTorrent、與 Apache "
+"æŽˆæ¬Šæ¢æ¬¾ç›¸å®¹ã€‚ç¸½ä¹‹ï¼Œæœ‰è¶³å¤ çš„ç†ç”±å‡ç´šã€‚"
 
 #. type: Content of: <p>
 msgid ""
@@ -315,10 +283,9 @@
 "important to make sure that programs will have no trouble upgrading to GPLv4 "
 "if and when we write one."
 msgstr ""
-"在 GPLv3 發佈後仍可能有其他的變動。如果威脅"
-"使用者自由的事情持續發展，我們將會編寫 GPLv4。"
-"如果我們真的編寫了 GPLv4，重要的是要確保程式"
-"都能毫無困難地升級到新版本。"
+"在 GPLv3 發佈後仍可能有其他的變動。如果威脅使用者
自由的事情持續發展，我們將會"
+"編寫 GPLv4。如果我們真的編寫了 
GPLv4，重要的是要確保程式都能毫無困難地升級到"
+"新版本。"
 
 #. type: Content of: <p>
 msgid ""
@@ -330,14 +297,10 @@
 "One way or another, programs should provide this flexibility for future GPL "
 "versions."
 msgstr ""
-"其中一個解決方法就是讓程式以「GPLv3 或"
-"更新版本」發佈。另一個方法就是"
-"讓程式的所有貢獻者指定一個代理人，"
-"讓他來決定是否要升級到新版的 GPL。"
-"第三種方法則是把所有貢獻者的版權都轉讓給"
-"一個版權持有者，讓他來決定授權條款的升級問題。"
-"無論是用那一種方法，程式都應該提供彈性給"
-"未來版本的 GPL。"
+"其中一個解決方法就是讓程式以「GPLv3 
或更新版本」發佈。另一個方法就是讓程式的"
+"所有貢獻者
指定一個代理人，讓他來決定是否要升級到新版的 
GPL。第三種方法則是把"
+"所有貢獻者的版權都轉讓給一個版權持有者
，讓他來決定授權條款的升級問題。無論是"
+"用那一種方法，程式都應該提供彈性給未來版本的 GPL。"
 
 #. TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.
 #. type: Content of: <div>
@@ -357,9 +320,6 @@
 "聯絡自由軟體基金會。至於損毀的連結及å…
¶ä»–修正和建議，可以將之寄給 <a href="
 "\"mailto:webmasters@gnu.org\";>&lt;webmasters@gnu.org&gt;</a>。"
 
-#
-#
-#
 #. 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
@@ -393,8 +353,8 @@
 "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/\">創用 CC 姓名標示-禁止改作 3.0 
美國</a>條款給予授權。"
+"æœ¬é é¢æŽ¡ç”¨<a rel=\"license\" 
href=\"https://creativecommons.org/licenses/by-";
+"nd/3.0/us/\">創用 CC 姓名標示-禁止改作 3.0 
美國</a>條款給予授權。"
 
 #. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.
 #. type: Content of: <div><div>

Index: rms-why-gplv3.zh-tw.html
===================================================================
RCS file: rms-why-gplv3.zh-tw.html
diff -N rms-why-gplv3.zh-tw.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ rms-why-gplv3.zh-tw.html    21 May 2021 13:29:15 -0000      1.1
@@ -0,0 +1,167 @@
+<!--#set var="ENGLISH_PAGE" value="/licenses/rms-why-gplv3.en.html" -->
+
+<!--#include virtual="/server/header.zh-tw.html" -->
+<!-- Parent-Version: 1.77 -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>為什麼要升級到 GPLv3 - GNU 專案 - 自由軟體基金會</title>
+
+<!--#include virtual="/licenses/po/rms-why-gplv3.translist" -->
+<!--#include virtual="/server/banner.zh-tw.html" -->
+<h2>為什麼要升級到 GPLv3</h2>
+
+<p>作者為 <strong>Richard Stallman</strong></p>
+
+<p><a href="/licenses/gpl.html">第三版的 GNU 通用公眾授權</a>（GNU 
GPL，以下簡稱
+GPLv3）已經發佈了，並讓自由軟體包可以從 GPL 
第二版（以下簡稱 GPLv2ï¼‰å‡ç´šä¸Šä¾†ã€‚é€™ç¯‡æ–‡ç« 
會解釋會什麼升級授權條款很重要。</p>
+
+<p id="choice">
+首先，升級不是必要的，只是一種選擇。GPLv2 
仍然可以使用。若有程式使用 GPLv2，而其他的程式正在使用
+GPLv3，也不會發生問題。雖然這å…
©å€‹æŽˆæ¬Šæ¢æ¬¾ä¸¦ä¸ç›¸å®¹ï¼Œä½†é€™ä¸¦ä¸æ˜¯æ ¹æœ¬çš„問題。</p>
+
+<p id="incompatibility">
+我們說 GPLv2 和 GPLv3 
不相容，是指我們沒有任何合法的方法能將 GPLv2 和 GPLv3 
çš„ç¨‹å¼ç¢¼æ•´åˆæˆä¸€å€‹ç¨‹å¼ã€‚é€™æ˜¯å› ç‚º GPLv2 和
+GPLv3 
éƒ½æ˜¯è‘—ä½œå‚³æŽˆæ¬Šæ¢æ¬¾ï¼Œä¸”å„è‡ªéƒ½æœ‰å¦‚æ­¤çš„è²æ˜Žï¼šã€Œå¦‚æžœä½ 
把這段程式碼應用在更大的程式之中，那該程式也會適用這é 
…æŽˆæ¬Šæ¢æ¬¾ã€‚ã€å› 此無法相容。我們可以在
+GPLv3 中聲明 GPLv3 與 GPLv2 
ç›¸å®¹ï¼Œä½†é€™ä»ç„¶ç„¡æ³•æ”¹è®Šä»–å€‘ç„¡æ³•ç›¸å®¹çš„æƒ…æ³ï¼Œå› ç‚º GPLv2 
也同時需要作出類似的聲明。</p>
+
+<p>幸好授權條款不相容的問題只會在您想要把å…
©å€‹ä¸åŒçš„程式連結或合併成一個程式時才會發生。然而，在作業系統中同時執行
 GPLv3 授權的程式和 GPLv2
+授權的程式是沒有問題的。例如，TeX 授權條款和 Apache 
授權條款與 GPLv2 不相容，但這並不能阻擋我們在與 
Linux、Bash 與 GCC
+相同的系統上執行 TeX 與 Apacheã€‚é€™æ˜¯å› 
為它們都是獨立的程式。同樣的，如果 Bash 和 GCC 都升級為 
GPLv3，但 Linux
+æ ¸å¿ƒä»ä½¿ç”¨ GPLv2 也不會發生衝突。</p>
+
+<p>讓程式繼續使用 GPLv2 ä¸¦ä¸æœƒé€ 
成任何問題。升級的理由是 GPLv3 
可以解決一些現有的問題。</p>
+
+<p id="tivoization">
+GPLv3 阻止的一個主要危險是 Tivoization。Tivoization 
的意思是特定的「裝置」（其中帶有電腦）包
含了您無法有效更改的 GPL
+æŽˆæ¬Šè»Ÿé«”ï¼Œå› 
為裝置偵測到軟體被變更時就會關機。Tivoization
+çš„å‹•æ©Ÿé€šå¸¸æ˜¯è£½é€ 
å•†çŸ¥é“è»Ÿé«”æœ‰æŸäº›äººå€‘æœƒæƒ³è¦ä¿®æ”¹çš„åŠŸèƒ½ï¼Œä½†è£½é€ 
å•†å°±æ˜¯ä¸å¸Œæœ›äººå€‘ä¿®æ”¹ã€‚è£½é€ 
商利用了自由軟體提供的自由，卻不讓使用者也這麼做。</p>
+
+<p>某些人認為自由市å 
´çš„ç«¶çˆ­æœƒè®“è£ç½®ä¸Šè¼ƒå·®çš„åŠŸèƒ½è™•æ–¼è¼ƒä½Žçš„æ°´æº–ã€‚æˆ–è¨±å…‰é 
競爭可以避免「每週二下午一點至五點必é 
ˆé—œæ©Ÿã€é€™é¡žéš¨æ„çš„、沒道理的糟糕功能。但即便如此，擁有裝置的人仍無法自由的選擇。自由應該是<em>您</em>可以控制ä½
 的程式能做什麼，而不用透過乞求他人或脅
迫他人的方式。</p>
+
+<p id="drm">
+在數位限制管理 (DRM) 中 &mdash; 這是限制您使用自己電è…
¦ä¸­è³‡æ–™çš„卑劣功能 &mdash;
+ç«¶çˆ­ç„¡æ¿Ÿæ–¼äº‹ï¼Œå› 
為相關的競爭是被禁止的。諸如《數位千禧年著作權法》之類的法律表示，在美國和許多å
…¶ä»–國家，如果您沒有按照 DVD 陰謀的官方規則（其網站為
+<a
+href="http://www.dvdcca.org/";>http://www.dvdcca.org/</a>，但是規則看來並沒有在此發佈）散佈限制使用è€
…çš„
+DVD 播放器，那就是違法的。大眾無法透過購買非 DRM 
的播放器來拒絕
+DRMï¼Œå› 
為沒有這樣的播放器。無論有多少種產品供您選擇，它們都是帶有數位枷鎖的。</p>
+
+<p>GPLv3 確保您可以自由移除這些限制。其並未禁止 DRM
+æˆ–å…¶ä»–åŠŸèƒ½ã€‚å…¶ä¸¦ä¸é™åˆ¶æ‚¨ç‚ºæ‚¨çš„ç¨‹å¼å¢žåŠ 
或刪除任何重要功能。反之，å…
¶ç¢ºä¿äº†æ‚¨èƒ½åƒæ‚¨å‰¯æœ¬çš„散佈者
新增討厭的功能一樣刪除那些功能。 Tivoization
+å°±æ˜¯ä»–å€‘é˜»æ­¢æ‚¨ç²å¾—è‡ªç”±çš„æ–¹å¼ã€‚ç‚ºäº†ä¿éšœä½ çš„è‡ªç”±ï¼ŒGPLv3 
禁止 Tivoization。</p>
+
+<p>對 tivoization 的禁止適用於任何可能會被消費者
使用的產品，即便只是偶爾用到也一樣。GPLv3 只允許 
tivoization
+出現在那些幾乎只用於企業與組織的產品。</p>
+
+<p id="patent-deals">
+GPLv3 要對抗的另一個威脅是像 Novell-Microsoft 
協定之類的專利交易。微軟用它擁有的上千個專利讓使用者
付錢給微軟來取得執行
+GNU/Linux 
的權力，並企圖透過這類的專利交易來達到目的。此交易對 
Novell 使用者使用微軟專利的保護非常有限。</p>
+
+<p>微軟在 Novell-Microsoft 的交易上仍犯了集少數的錯誤，而 
GPLv3
+將用來向微軟反擊，從而將å…
¶å°ˆåˆ©ä¿è­·æ“´å¤§åˆ°æ•´å€‹ç¤¾ç¾¤ã€‚為了取得這類保護，程式必é 
ˆä½¿ç”¨ GPLv3。</p>
+
+<p>微軟的律師們並不笨，下一次他們可能會設法避開那些失誤。å›
 此，GPLv3 讓他們不再有「下次」的機會。使用 GPLv3
+發布的程式可以保護其免受微軟將來試圖讓轉散發者
從程式的使用者那裡收取微軟專利費用的嘗試。</p>
+
+<p id="patent-protection">
+GPLv3 還提供使用者來自程式貢獻者與轉散發者
明確的專利保護。使用
+GPLv2，使用者則僅能依賴潛在的專利授權來確保向å…
¶æä¾›å‰¯æœ¬çš„公司不會對他們提告，或是對轉散發å…
¶å‰¯æœ¬çš„人們提告專利侵權。</p>
+
+<p>GPLv3 
中的明確專利授權條款並未如我們所想要的程度。理想的情
況是，我們希望每個 GPL
+ç¨‹å¼ç¢¼çš„è½‰æ•£ç™¼è€…èˆ‡éžè½‰æ•£ç™¼è€…éƒ½æ”¾æ£„å…¨éƒ¨çš„è»Ÿé«”å°ˆåˆ©ï¼Œå› 
為本來就不該有軟體專利。軟體專利是一套惡毒且荒謬的體系，它讓所有開發è€
…éƒ½é¢è‡¨è¢«ç´ 昧平生的公司提告的風險，當然也包含被同é 
˜åŸŸçš„超級大å…
¬å¸èµ·è¨´çš„風險。大型軟體通常都結合了成千上萬個想法，所以å
…¶ä¸­çš„數百個想法已經被申請成專利並不意外。超級大å…
¬å¸æŽŒæ¡ä¸Šåƒå€‹å°ˆåˆ©ï¼Œä¸¦ä¸”用那些專利來霸凌å…
¶ä»–弱小的開發者。專利已在阻撓自由軟體的開發。</p>
+
+<p>確保軟體開發安å…
¨çš„å”¯ä¸€æ–¹æ³•å°±æ˜¯å»¢é™¤è»Ÿé«”å°ˆåˆ©ã€‚æˆ‘å€‘å¸Œæœ›å°‡ä¾†é€™å€‹ç›®æ¨™èƒ½å¤ 
實現。但是我們無法透過軟體的授權條款來實現這個目的。任何一個程式，無論å
…¶æ˜¯å¦ç‚ºè‡ªç”±è»Ÿé«”，都會被不相關的軟體專利持有者
幹掉，而軟體授權條款並不能使其倖å…
æ–¼é›£ã€‚只有透過法院的判決或是專利法的改革才能讓軟體開發è€
…免除專利的風險。如果我們試著用
+GPLv3 來改變現狀，那必然會失敗。</p>
+
+<p>å› æ­¤ï¼ŒGPLv3 試圖限制並疏導這種危險。å…
·é«”來說，我們是在盡力拯救自由軟體，讓自由軟體不會落å…
¥ç”Ÿä¸å¦‚死的地步：亦即透過專利變成專有軟體。GPLv3
+明確的專利授權條款可確保使用 GPL 賦予使用者四種自由的å…
¬å¸ä¸èƒ½åæ‚”並使用其專利告訴某些使用者「這並不包
含您。」並同時阻止了他們與其他專利持有者共謀。</p>
+
+<p id="further-advantages">
+GPLv3 的其他優點包含了更國際化、更溫和的中止授權、支援 
BitTorrent、與 Apache æŽˆæ¬Šæ¢æ¬¾ç›¸å®¹ã€‚ç¸½ä¹‹ï¼Œæœ‰è¶³å¤ 
的理由升級。</p>
+
+<p id="gpl4">
+在 GPLv3 發佈後仍可能有其他的變動。如果威脅使用者
自由的事情持續發展，我們將會編寫 
GPLv4。如果我們真的編寫了
+GPLv4，重要的是要確保程式都能毫無困難地升級到新版本。</p>
+
+<p id="future-proofing">
+其中一個解決方法就是讓程式以「GPLv3 
或更新版本」發佈。另一個方法就是讓程式的所有貢獻者
指定一個代理人，讓他來決定是否要升級到新版的
+GPL。第三種方法則是把所有貢獻者
的版權都轉讓給一個版權持有者
，讓他來決定授權條款的升級問題。無論是用那一種方法，程式都應該提供彈性給未來版本的
+GPL。</p>
+
+<div class="translators-notes">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
+ </div>
+</div>
+
+<!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.zh-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 3.0 US.  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; 2007, 2009, 2014 Richard Stallman</p>
+
+<p>æœ¬é é¢æŽ¡ç”¨<a rel="license"
+href="https://creativecommons.org/licenses/by-nd/3.0/us/";>創用 CC 
姓名標示-禁止改作
+3.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>：國立陽明交通大學 服務學習成果, 2021.<br />
+<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/05/21 13:29:15 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>

Index: po/rms-why-gplv3.zh-tw-en.html
===================================================================
RCS file: po/rms-why-gplv3.zh-tw-en.html
diff -N po/rms-why-gplv3.zh-tw-en.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ po/rms-why-gplv3.zh-tw-en.html      21 May 2021 13:29:15 -0000      1.1
@@ -0,0 +1,228 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.77 -->
+<title>Why Upgrade to GPLv3
+- GNU Project - Free Software Foundation</title>
+<!--#include virtual="/licenses/po/rms-why-gplv3.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>Why Upgrade to GPLv3</h2>
+
+<p>by <strong>Richard Stallman</strong></p>
+
+<p><a href="/licenses/gpl.html">Version 3 of the GNU General Public
+License</a> (GNU GPL) has been released, enabling free software packages to
+upgrade from GPL version 2.  This article explains why upgrading the
+license is important.</p>
+
+<p id="choice">
+First of all, it is important to note that upgrading is a choice.  GPL
+version 2 will remain a valid license, and no disaster will happen if
+some programs remain under GPLv2 while others advance to GPLv3.  These
+two licenses are incompatible, but that isn't a fundamental problem.</p>
+
+<p id="incompatibility">
+When we say that GPLv2 and GPLv3 are incompatible, it means there is
+no legal way to combine code under GPLv2 with code under GPLv3 in a
+single program.  This is because both GPLv2 and GPLv3 are copyleft
+licenses: each of them says, &ldquo;If you include code under this license
+in a larger program, the larger program must be under this license
+too.&rdquo;  There is no way to make them compatible.  We could add a
+GPLv2-compatibility clause to GPLv3, but it wouldn't do the job,
+because GPLv2 would need a similar clause.</p>
+
+<p>Fortunately, license incompatibility matters only when you want to
+link, merge or combine code from two different programs into a single
+program.  There is no problem in having GPLv3-covered and
+GPLv2-covered programs side by side in an operating system.  For
+instance, the TeX license and the Apache license are incompatible with
+GPLv2, but that doesn't stop us from running TeX and Apache in the
+same system with Linux, Bash and GCC.  This is because they are all
+separate programs.  Likewise, if Bash and GCC move to GPLv3, while
+Linux remains under GPLv2, there is no conflict.</p>
+
+<p>Keeping a program under GPLv2 won't create problems.  The reason to
+migrate is because of the existing problems that GPLv3 will address.</p>
+
+<p id="tivoization">
+One major danger that GPLv3 will block is tivoization.  Tivoization
+means certain &ldquo;appliances&rdquo; (which have computers inside)
+contain GPL-covered software that you can't effectively change, because the
+appliance shuts down if it detects modified software.  The usual
+motive for tivoization is that the software has features the
+manufacturer knows people will want to change, and aims
+to stop people from changing them.  The manufacturers of
+these computers take advantage of the freedom that free software
+provides, but they don't let you do likewise.</p>
+
+<p>Some argue that competition between appliances in a free market should
+suffice to keep nasty features to a low level.  Perhaps competition
+alone would avoid arbitrary, pointless misfeatures like &ldquo;Must shut
+down between 1pm and 5pm every Tuesday&rdquo;, but even so, a choice of
+masters isn't freedom.  Freedom means <em>you</em> control what your software
+does, not merely that you can beg or threaten someone else who decides
+for you.</p>
+
+<p id="drm">
+In the crucial area of Digital Restrictions Management (DRM)&mdash;nasty 
features
+designed to restrict your use of the data in your
+computer&mdash;competition is no help, because relevant competition is
+forbidden.  Under the Digital Millennium Copyright Act and similar
+laws, it is illegal, in the US and many other countries, to distribute
+DVD players unless they restrict the user according to the official
+rules of the DVD conspiracy (its web site is <a 
href="http://www.dvdcca.org/";>http://www.dvdcca.org/</a>,
+but the rules do not seem to be published there).  The public can't
+reject DRM by buying non-DRM players because none are available.  No
+matter how many products you can choose from, they all have equivalent
+digital handcuffs.</p>
+
+<p>GPLv3 ensures you are free to remove the handcuffs.  It doesn't forbid
+DRM, or any kind of feature.  It places no limits on the substantive
+functionality you can add to a program, or remove from it.  Rather, it
+makes sure that you are just as free to remove nasty features as the
+distributor of your copy was to add them.  Tivoization is the way they
+deny you that freedom; to protect your freedom, GPLv3 forbids
+tivoization.</p>
+
+<p>The ban on tivoization applies to any product whose use by consumers is to 
be expected, even occasionally.  GPLv3 tolerates tivoization
+only for products that are almost exclusively meant for businesses and
+organizations.</p>
+
+<p id="patent-deals">
+Another threat that GPLv3 resists is that of patent deals like the
+Novell-Microsoft pact.  Microsoft wants to use its thousands of
+patents to make users pay Microsoft for the privilege of running
+GNU/Linux, and made this pact to try to achieve that.  The deal offers
+rather limited protection from Microsoft patents to Novell's customers.</p>
+
+<p>Microsoft made a few mistakes in the Novell-Microsoft deal, and GPLv3
+is designed to turn them against Microsoft, extending that limited
+patent protection to the whole community.  In order to take advantage
+of this protection, programs need to use GPLv3.</p>
+
+<p>Microsoft's lawyers are not stupid, and next time they may manage to
+avoid those mistakes.  GPLv3 therefore says they don't get a &ldquo;next
+time&rdquo;.  Releasing a program under GPL version 3 protects it from
+Microsoft's future attempts to make redistributors collect Microsoft
+royalties from the program's users.</p>
+
+<p id="patent-protection">
+GPLv3 also provides users with explicit patent protection from
+the program's contributors and redistributors.  With GPLv2, users rely
+on an implicit patent license to make sure that the company which
+provided them a copy won't sue them, or the people they redistribute
+copies to, for patent infringement.</p>
+
+<p>The explicit patent license in GPLv3 does not go as far as we might
+have liked.  Ideally, we would make everyone who redistributes
+GPL-covered code give up all software patents, along with everyone
+who does not redistribute GPL-covered code, because there should be
+no software patents.  Software patents are a
+vicious and absurd system that puts all software developers in danger
+of being sued by companies they have never heard of, as well as by all
+the megacorporations in the field.  Large programs typically combine
+thousands of ideas, so it is no surprise if they implement ideas
+covered by hundreds of patents.  Megacorporations collect thousands of
+patents, and use those patents to bully smaller developers.  Patents
+already obstruct free software development.</p>
+
+<p>The only way to make software development safe is to abolish software
+patents, and we aim to achieve this some day.  But we cannot do this
+through a software license.  Any program, free or not, can be killed
+by a software patent in the hands of an unrelated party, and the
+program's license cannot prevent that.  Only court decisions or
+changes in patent law can make software development safe from patents.
+If we tried to do this with GPLv3, it would fail.</p>
+
+<p>Therefore, GPLv3 seeks to limit and channel the danger.  In
+particular, we have tried to save free software from a fate worse than
+death: to be made effectively proprietary, through patents.  The
+explicit patent license of GPLv3 makes sure companies that use the GPL
+to give users the four freedoms cannot turn around and use their
+patents to tell some users, &ldquo;That doesn't include you.&rdquo;
+It also stops
+them from colluding with other patent holders to do this.</p>
+
+<p id="further-advantages">
+Further advantages of GPLv3 include better internationalization, gentler
+termination, support for BitTorrent, and compatibility with the Apache
+license.  All in all, plenty of
+reason to upgrade.</p>
+
+<p id="gpl4">
+Change is unlikely to cease once GPLv3 is released.  If new threats to
+users' freedom develop, we will have to develop GPL version 4.  It is
+important to make sure that programs will have no trouble upgrading to
+GPLv4 if and when we write one.</p>
+
+<p id="future-proofing">
+One way to do this is to release a program under &ldquo;GPL version 3 or any
+later version&rdquo;.  Another way is for all the contributors to a program
+to state a proxy who can decide on upgrading to future GPL versions.
+The third way is for all the contributors to assign copyright to one
+designated copyright holder, who will be in a position to upgrade the
+license version.  One way or another, programs should provide this
+flexibility for future GPL versions.</p>
+
+</div><!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>Please send general FSF &amp; GNU inquiries to
+<a href="mailto: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 3.0 US.  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; 2007, 2009, 2014 Richard Stallman</p>
+
+<p>This page is licensed under a <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/";>Creative
+Commons Attribution-NoDerivs 3.0 United States License</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2021/05/21 13:29:15 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>