www/licenses po/copyleft.translist po/copyleft....

[GNUN]

CVSROOT:        /web/www
Module name:    www
Changes by:     GNUN <gnun>     17/06/06 13:58:44

Modified files:
        licenses/po    : copyleft.translist copyleft.zh-tw.po 
Added files:
        licenses       : copyleft.zh-tw.html 
        licenses/po    : copyleft.zh-tw-en.html 

Log message:
        Automatic update by GNUnited Nations.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/copyleft.zh-tw.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/copyleft.translist?cvsroot=www&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/copyleft.zh-tw.po?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/copyleft.zh-tw-en.html?cvsroot=www&rev=1.1

Patches:
Index: po/copyleft.translist
===================================================================
RCS file: /web/www/www/licenses/po/copyleft.translist,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- po/copyleft.translist       6 Jul 2016 19:28:56 -0000       1.4
+++ po/copyleft.translist       6 Jun 2017 17:58:44 -0000       1.5
@@ -26,6 +26,7 @@
 <span dir="ltr"><a lang="tr" hreflang="tr" 
href="/licenses/copyleft.tr.html">Türkçe</a>&nbsp;[tr]</span> &nbsp;
 <span dir="ltr"><a lang="uk" hreflang="uk" 
href="/licenses/copyleft.uk.html">українська</a>&nbsp;[uk]</span> 
&nbsp;
 <span dir="ltr"><a lang="zh-cn" hreflang="zh-cn" 
href="/licenses/copyleft.zh-cn.html">简体中文</a>&nbsp;[zh-cn]</span> &nbsp;
+<span dir="ltr"><a lang="zh-tw" hreflang="zh-tw" 
href="/licenses/copyleft.zh-tw.html">繁體中文</a>&nbsp;[zh-tw]</span> &nbsp;
 </p>
 </div>' -->
 <link rel="alternate" type="text/html" href="/licenses/copyleft.html" 
hreflang="x-default" />
@@ -53,4 +54,5 @@
 <link rel="alternate" type="text/html" lang="tr" hreflang="tr" 
href="/licenses/copyleft.tr.html" title="Türkçe" />
 <link rel="alternate" type="text/html" lang="uk" hreflang="uk" 
href="/licenses/copyleft.uk.html" title="українська" />
 <link rel="alternate" type="text/html" lang="zh-cn" hreflang="zh-cn" 
href="/licenses/copyleft.zh-cn.html" title="简体中文" />
+<link rel="alternate" type="text/html" lang="zh-tw" hreflang="zh-tw" 
href="/licenses/copyleft.zh-tw.html" title="繁體中文" />
 <!-- end translist file -->

Index: po/copyleft.zh-tw.po
===================================================================
RCS file: /web/www/www/licenses/po/copyleft.zh-tw.po,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- po/copyleft.zh-tw.po        6 Jun 2017 17:41:23 -0000       1.1
+++ po/copyleft.zh-tw.po        6 Jun 2017 17:58:44 -0000       1.2
@@ -6,7 +6,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: copyleft.html\n"
-"POT-Creation-Date: 2017-06-07 00:59+0800\n"
+"POT-Creation-Date: 2017-04-05 12:26+0000\n"
 "PO-Revision-Date: 2017-06-07 00:59+0800\n"
 "Last-Translator: Cheng-Chia Tseng <address@hidden>\n"
 "Language-Team: Traditional Chinese <address@hidden>\n"

Index: copyleft.zh-tw.html
===================================================================
RCS file: copyleft.zh-tw.html
diff -N copyleft.zh-tw.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ copyleft.zh-tw.html 6 Jun 2017 17:58:44 -0000       1.1
@@ -0,0 +1,189 @@
+<!--#set var="ENGLISH_PAGE" value="/licenses/copyleft.en.html" -->
+
+<!--#include virtual="/server/header.zh-tw.html" -->
+<!-- Parent-Version: 1.83 -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>著作傳是什麼？ - GNU 專案 - 自由軟體基金會</title>
+<meta http-equiv="Keywords" content="GNU, FSF, Free Software Foundation, 
自由軟體基金會, Linux, Copyleft, 著作傳" />
+
+<!--#include virtual="/licenses/po/copyleft.translist" -->
+<!--#include virtual="/server/banner.zh-tw.html" -->
+<h2>著作傳 (Copyleft) 是什麼？</h2>
+
+<p>
+著作傳是種讓程式（或其他作品）自由（<a 
href="/philosophy/free-sw.html">意指自由的 freeï¼Œè€Œéžã€Œé›¶åƒ¹æ ¼ã€çš„
+free</a> <a 
href="#trans1">[按1]</a>）的通用方法，要求所有修改之後和延伸而出的程式版本都å¿
…é ˆåŒæ¨£è‡ªç”±ã€‚</p>
+
+<p>
+要讓程式變成自由軟體的最簡單方法，就是放棄著作權，使之成為<a
+href="/philosophy/categories.html#PublicDomainSoftware">å…¬æœ‰é ˜åŸŸçš„å…
¬ç‰ˆè‘—作 (public
+domain)</a>。這樣人們就能分享程式和相關改善，只要他們有這樣的想法。然而，這種作法卻也會讓不想合作的人將程式轉為<a
+href="/philosophy/categories.html#ProprietarySoftware">專有軟體 
(proprietary
+software)</a>。他們能做出改動，也許多也許少，接著將成品以專有產品的形式散布。收到修改後程式的人便失去原å
…ˆä½œè€…給予人們的自由；中間人已奪去了自由。</p>
+
+<p>
+在 <a href="/gnu/thegnuproject.html">GNU 
專案</a>中，我們的宗旨是要給予<em>所有</em>
+使用者再次散布、與修改 GNU 
軟體的自由。如果中間人可以將自由奪走，我們的程式碼也許「會有不少使用è€
…」，但是卻未能給予他們自由。與其讓 GNU
+軟體成為公版著作，我們更希望它成為「著作傳 
(copyleft)」。著作傳 [傳在此處的念法為ㄔㄨㄢˊ]
+的概念是任何人都能再次散布該軟體，不管有無更動，都必
é 
ˆæŠŠè‡ªç”±å‚³éžä¸‹åŽ»ï¼Œä½¿ä¹‹èƒ½é€²ä¸€æ­¥è¤‡è£½å’Œä¿®æ”¹ã€‚著作傳能保障任何使用è€
…都擁有自由。</p>
+
+<p>
+著作傳能讓其他程式設計師有<a 
href="/philosophy/pragmatic.html">動力</a>增添自由軟體。如 GNU C++
+ç·¨è­¯å™¨é€™é¡žé‡å¤§çš„è‡ªç”±è»Ÿé«”ä¹‹æ‰€ä»¥èƒ½å­˜åœ¨ï¼Œä¾¿æ˜¯å› 
為著作傳之故。</p>
+
+<p>
+著作傳也幫助想<a href="/prep/tasks.html">改善</a><a
+href="/philosophy/free-sw.html">自由軟體</a>的程式設計師能有權如此作為。舉例而言，這些程式設計師通常為那些盡可能賺錢的å
…
¬å¸æˆ–大學工作。若有一位程式設計師想將她的改動貢獻給社群，但她的老闆卻想讓這些更動轉變為專有軟體產品。</p>
+
+<p>
+一旦我們向這位老闆解釋散布修改後的版本係屬違法，除非該軟體是自由軟體後；通常這位老闆會決定將軟體以自由軟體的形式發行，而非直接丟棄。</p>
+
+<p>
+若要以著作傳保障程式，我們必å…
ˆé™³è¿°å®ƒå—åˆ°è‘—ä½œæ¬Šä¿è­·ï¼›æŽ¥è‘—æˆ‘å€‘åŠ å…
¥æ•£å¸ƒæ¢æ¬¾ï¼Œé€™äº›æ¢æ¬¾æ˜¯çµ¦äºˆæ‰€æœ‰äººå°ç¨‹å¼ä»£ç¢¼ã€<em>或是任何衍生而出的程式</em>有使用、修改、並再次散布等權利的法律工å
…
·ï¼Œå”¯æœ‰æ¢ä»¶æ˜¯æŽˆæ¬Šçš„散布條款不能更動。如此一來，這些程式碼和自由在法律上便無法分割開來。</p>
+
+<p>
+專有軟體開發者利用著作權奪走使用者
的自由；我們則使用著作權來保障大家的自由。這就是為何我們把著作權的名稱轉個彎，將「著作權
+(copyright)」轉為「著作傳 (copyleft)」。</p>
+
+<p>
+著作傳是程式著作權的一種運用方式。它不代表拋棄著作權；實際上，若以拋棄著作權的作法，去求著作傳想達成的保障，猶如緣木求魚。著作傳英文「copyleft」中的「left」並不是指動詞的「leave」離去
+— 而是單指「right」的鏡像 <a href="#trans2">[按2]</a>。</p>
+
+<p>
+è‘—ä½œå‚³æ˜¯ç¨®æ¦‚å¿µï¼Œä½†ä½ ç„¡æ³•ç›´æŽ¥å¥—ç”¨é€™ç¨®æ¦‚å¿µï¼›ä½ 
只能採用這種概念的特定實作方案。在 GNU 
專案中，我們大多數軟體採用的指定散布條款寫在<a
+href="/licenses/gpl.html">GNU 通用公眾授權 (GNU General Public 
License)</a>之中。GNU
+通用公眾授權又常被簡稱為 GNU GPL。這裡也有篇關於 GNU GPL 
的<a
+href="/licenses/gpl-faq.html">常見問答集</a>é é¢ã€‚ä½ 
也可以閱讀這篇<a
+href="/licenses/why-assign.html">為何 FSF 要從貢獻者
手中取得著作權的讓與</a>。</p>
+
+<p>
+著作傳的另一種選擇方案，<a href="/licenses/agpl.html">GNU Affero 
通用公眾授權 (GNU Affero
+General Public License, AGPL)</a>
+的設計係針對常見於伺服器上的程式而來。它能確保給大眾使用的服務å
…¶å¯¦ç¾ä½œæ³•çš„修改後版本可透過源始碼發行給大眾。</p>
+
+<p>
+著作傳的折衷方案，<a href="/licenses/lgpl.html">GNU 較寬鬆通用å…
¬çœ¾æŽˆæ¬Š (GNU Lesser General
+Public License, LGPL)</a> 用於少數（但非全部）的 GNU 
函式庫上。若想深入瞭解 LGPL 的適當使用方式，還請閱讀<a
+href="/philosophy/why-not-lgpl.html"><cite>ç‚ºä½•ä½ ä¸æ‡‰æ›¿ä½ 
下個函式庫使用 LGPL</cite></a>。</p>
+
+<p>
+<a href="/licenses/fdl.html">GNU 自由文件授權 (GNU Free Documentation 
License,
+FDL)</a>
+是企圖用於手冊、教科書、或å…
¶ä»–文件的著作傳方案，以保障任何人皆能擁有複製、再次散布這些文件的切確自由，不管有無修改、亦無論有無商業行為。</p>
+
+<p>
+許多手冊和各個 GNU 源始碼散布版之中皆有å…
§å«å°æ‡‰çš„授權條款。</p>
+
+<p>
+å‡å¦‚ä½ æ˜¯è‘—ä½œæ¬Šæ“æœ‰è€…ï¼Œæ‰€æœ‰é€™äº›æŽˆæ¬Šæ¢æ¬¾éƒ½è¨­è¨ˆçµ¦ä½ 
è¼•é¬†å¥—ç”¨åˆ°è‡ªå·±çš„ä½œå“ä¸Šã€‚ä½ ä¸å¿…
修改這些條款，只要將授權條款副本納å…
¥ä½œå“ä¹‹ä¸­ï¼Œä¸¦åœ¨æºå§‹æª”æ¡ˆä¸­å¦¥å–„åŠ 入參ç…
§è©²æŽˆæ¬Šæ¢æ¬¾çš„聲明即可。</p>
+
+<p>
+為許多不同程式採用相同的散布條款，能讓不同程式間的程式碼複製更為輕鬆簡單。當這些程式都採取相同的散布條款時，便不會有什麼問題。LGPL
 第 2
+ç‰ˆï¼Œå«æœ‰ä¸€å‰‡è¦å®šèƒ½è®“ä½ æ”¹è®Šå›žåŽŸå§‹çš„ GPL 
çš„æ•£å¸ƒæ¢æ¬¾ï¼Œå¦‚æ­¤ä½ å°±èƒ½å°‡ç¨‹å¼ç¢¼è¤‡è£½åˆ°å¦ä¸€å€‹ GPL 所包
覆的其他程式中。LGPL 第 3 ç‰ˆå‰‡æ‰“é€ ç‚º GPL
+第 3 ç‰ˆçš„é™„åŠ ä¾‹å¤–ï¼Œå¯è‡ªå‹•ç›¸å®¹ã€‚</p>
+
+<p>
+è‹¥ä½ å¸Œæœ›ç”¨ GNU GPL 或 GNU LGPL æŽˆæ¬Šè®“ä½ 
的程式保有著作傳，請參見<a
+href="/licenses/gpl-howto.html">授權條款指示é 
é¢</a>ä¸­çµ¦äºˆçš„æ„è¦‹ã€‚è«‹æ³¨æ„åˆ°ä½ å¿…é ˆæŽ¡ç”¨æ‰€é¸æŽˆæ¬Šçš„å®Œæ•´å…
§æ–‡ã€‚各個授權條款都是不能切分的整體，不å…
è¨±åªæ‘˜éŒ„部分的副本。</p>
+
+<p>
+è‹¥ä½ å¸Œæœ›ç”¨ GNU FDL æŽˆæ¬Šè®“ä½ çš„æ‰‹å†Šä¿æœ‰è‘—ä½œå‚³ï¼Œè«‹åƒè¦‹ FDL å…
§æ–‡çš„<a
+href="/licenses/fdl.html#addendum">結尾</a> ，以及 <a
+href="/licenses/fdl-howto.html">GFDL æŒ‡ç¤ºé é¢</a>。</p>
+
+<p>
+採用圓圈括住左右相反的 C
+而非著作權符號在法律上是個錯誤。著作傳於法律上係æ 
¹æ“šè‘—ä½œæ¬Šè€Œä¾†ï¼Œå› 此作品必é 
ˆæœ‰è‘—作權聲明。著作權聲明要有著作權符號（圓圈括住的
+C），或是有「著作權/Copyright」字眼。</p>
+
+<p>
+用圓圈括住左右相反的 C 
並沒有特別的法律意義，所以不能作為著作權聲明。也許將它放在書籍封面、海å
 ±â€¦ç­‰åª’材上會很有趣，但<a
+href="https://en.wikipedia.org/wiki/Copyleft#Symbol";>請留意網é 
ä¹‹ä¸­æ‰€æ‡‰å‘ˆç¾çš„形式！</a>
+</p>
+
+<div class="translators-notes">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
+<b>譯者按︰</b>
+<ol><li id="trans1">ä¸­æ–‡è®€è€…ä¹Ÿè¨±æœƒè¦ºå¾—é€™èªžå¥å¾ˆæ€ªï¼Œå› 
為英文的 Free
+有「自由」及「免費」兩個意思，所以作者
要求特別區分，以正視聽。</li>
+<li id="trans2">é¡åƒï¼Œä»£è¡¨ç‰©é«”çš„é¡ä¸­æ˜ 
像，是同一物體的反向觀。這也就是為何 copyleft 的中文 —
+著作傳，念法不同於著作權但諧音相似，暗指著作權的不同道路
 — 要將自由傳遞下去。</li>
+</ol></div>
+</div>
+
+<!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.zh-tw.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>請來信到 <a href="mailto:address@hidden";>&lt;address@hidden&gt;</a> 
詢問有關自由軟體基金會（FSF）和
+GNU 的一般問題；或者<a href="/contact/">以å…
¶ä»–方式</a>聯絡自由軟體基金會。至於損毀的連結及å…
¶ä»–修正和建議，可以將之寄給 <a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>。</p>
+
+<p>
+<!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to <a href="mailto:address@hidden";>
+
+        &lt;address@hidden&gt;</a>.</p>
+
+        <p>For information on coordinating and submitting translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+我們努力盡所能提供貼切、品質良善的翻譯。然而，我們無法十å
…¨åç¾Žï¼Œé‚„è«‹å°‡ä½ 的意見評述與一般建議寄給 <a href="mailto:web-
address@hidden">&lt;address@hidden&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; 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
+2006, 2007, 2008, 2009, 2014, 2015, 2016, 2017 Free Software Foundation,
+Inc.</p>
+
+<p>æœ¬é é¢æŽ¡ç”¨<a rel="license"
+href="https://creativecommons.org/licenses/by-nd/4.0/deed.zh_TW";>創用 CC
+授權姓名標示-禁止改作 4.0 國際</a>條款給予授權。</p>
+
+<!--#include virtual="/server/bottom-notes.zh-tw.html" -->
+<div class="translators-credits">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
+<b>翻譯</b>：曾政嘉
+<a href="mailto:zerngjia (at) member (dot) fsf (dot) org">&lt;zerngjia (at)
+member (dot) fsf (dot) org&gt;</a>,
+2017.</div>
+
+<p class="unprintable"><!-- timestamp start -->
+更新時間︰
+
+$Date: 2017/06/06 17:58:44 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>

Index: po/copyleft.zh-tw-en.html
===================================================================
RCS file: po/copyleft.zh-tw-en.html
diff -N po/copyleft.zh-tw-en.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ po/copyleft.zh-tw-en.html   6 Jun 2017 17:58:44 -0000       1.1
@@ -0,0 +1,229 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.83 -->
+<title>What is Copyleft? - GNU Project - Free Software Foundation</title>
+<meta http-equiv="Keywords" content="GNU, FSF, Free Software Foundation, 
Linux, Copyleft" />
+
+<!--#include virtual="/licenses/po/copyleft.translist" -->
+<!--#include virtual="/server/banner.html" -->
+   
+<h2>What is Copyleft?</h2>
+
+<p>
+Copyleft is a general method for making a program (or other work) free
+(<a href="/philosophy/free-sw.html">in the sense of freedom, not
+&ldquo;zero price&rdquo;</a>), and requiring all modified and extended 
versions of
+the program to be free as well.</p>
+
+<p>
+The simplest way to make a program free software is to put it in the
+<a href="/philosophy/categories.html#PublicDomainSoftware">public
+domain</a>, uncopyrighted.  This allows people to
+share the program and their improvements, if they are so minded.  But
+it also allows uncooperative people to convert the program into
+<a href="/philosophy/categories.html#ProprietarySoftware">proprietary
+software</a>.  They can make changes, many or few,
+and distribute the result as a proprietary product.  People who
+receive the program in that modified form do not have the freedom that
+the original author gave them; the middleman has stripped it away.</p>
+
+<p>
+In the <a href="/gnu/thegnuproject.html">GNU project</a>, our aim is
+to give <em>all</em> users the freedom to redistribute and change GNU
+software.  If middlemen could strip off the freedom, our code might &ldquo;have
+many users,&rdquo; but it would not give them freedom.  So instead of
+putting GNU software in the public domain, we &ldquo;copyleft&rdquo;
+it.  Copyleft says that anyone who redistributes the software, with or
+without changes, must pass along the freedom to further copy and
+change it.  Copyleft guarantees that every user has freedom.</p>
+
+<p>
+Copyleft also provides an
+<a href="/philosophy/pragmatic.html">incentive</a>
+for other programmers to add to free software.
+Important free programs such as the GNU C++ compiler exist
+only because of this.</p>
+
+<p>
+Copyleft also helps programmers who want to contribute
+<a href="/prep/tasks.html">improvements</a> to
+<a href="/philosophy/free-sw.html">free software</a> get permission to
+do so.  These programmers often work for companies or universities
+that would do almost anything to get more money.  A programmer may
+want to contribute her changes to the community, but her employer may
+want to turn the changes into a proprietary software product.</p>
+
+<p>
+When we explain to the employer that it is illegal to distribute the
+improved version except as free software, the employer usually decides
+to release it as free software rather than throw it away.</p>
+
+<p>
+To copyleft a program, we first state that it is copyrighted; then we
+add distribution terms, which are a legal instrument that gives
+everyone the rights to use, modify, and redistribute the program's
+code, <em>or any program derived from it</em>, but only if the
+distribution terms are unchanged.  Thus, the code and the freedoms
+become legally inseparable.</p>
+
+<p>
+Proprietary software developers use copyright to take away the users'
+freedom; we use copyright to guarantee their freedom.  That's why we
+reverse the name, changing &ldquo;copyright&rdquo; into
+&ldquo;copyleft.&rdquo;</p>
+
+<p>
+Copyleft is a way of using the copyright on the program.  It
+doesn't mean abandoning the copyright; in fact, doing so would make
+copyleft impossible.  The &ldquo;left&rdquo; in
+&ldquo;copyleft&rdquo; is not a reference to the verb &ldquo;to
+leave&rdquo;&mdash;only to the direction which is the mirror image of
+&ldquo;right&rdquo;.</p>
+
+<p>
+Copyleft is a general concept, and you can't use a general concept
+directly; you can only use a specific implementation of the concept.
+In the GNU Project, the specific distribution terms that we use for
+most software are contained in the <a href="/licenses/gpl.html">
+GNU General Public License</a>.  The GNU General
+Public License is often called the GNU GPL for short. There is also a
+<a href="/licenses/gpl-faq.html">Frequently Asked Questions</a> page
+about the GNU GPL.  You can also read about
+<a href="/licenses/why-assign.html">why the FSF gets copyright
+assignments from contributors</a>.</p>
+
+<p>
+An alternate form of copyleft, the <a href="/licenses/agpl.html">GNU
+Affero General Public License (AGPL)</a> is designed for
+programs that are likely to be used on servers.  It ensures that
+modified versions used to implement services available to the public
+are released as source code to the public.</p>
+
+<p>
+A compromise form of copyleft, the <a href="/licenses/lgpl.html">GNU
+Lesser General Public License (LGPL)</a> applies to a few (but not
+all) GNU libraries. To learn more about properly using the LGPL, please
+read the article <a href="/philosophy/why-not-lgpl.html"><cite>Why you
+shouldn't use the Lesser GPL for your next library</cite></a>.</p>
+
+<p>
+The <a href="/licenses/fdl.html">GNU Free Documentation License (FDL)</a>
+is a form of copyleft intended
+for use on a manual, textbook or other document to assure everyone the
+effective freedom to copy and redistribute it, with or without
+modifications, either commercially or noncommercially.</p>
+
+<p>
+The appropriate license is included in many manuals and in each GNU
+source code distribution.</p>
+
+<p>
+All these licenses are designed so that you can easily apply them to
+your own works, assuming you are the copyright holder.  You don't have
+to modify the license to do this, just include a copy of the license
+in the work, and add notices in the source files that refer properly
+to the license.</p>
+
+<p>
+Using the same distribution terms for many different programs makes it
+easy to copy code between various different programs.  When they all
+have the same distribution terms, there is no problem.  The Lesser
+GPL, version 2, includes a provision that lets you alter the
+distribution terms to the ordinary GPL, so that you can copy code into
+another program covered by the GPL.  Version 3 of the Lesser GPL is
+built as an exception added to GPL version 3, making the compatibility
+automatic.</p>
+
+<p>
+If you would like to copyleft your program with the GNU GPL or the GNU
+LGPL, please see the <a href="/licenses/gpl-howto.html">license
+instructions page</a> for advice.  Please note that you must use the entire
+text of the license you choose.  Each is an integral whole, and
+partial copies are not permitted.</p>
+
+<p>
+If you would like to copyleft your manual with the GNU FDL, please
+see the instructions at the
+<a href="/licenses/fdl.html#addendum">end</a> of the FDL text, and
+the <a href="/licenses/fdl-howto.html">GFDL instructions page</a>.  Again,
+partial copies are not permitted.</p>
+
+<p>
+It is a legal mistake to use a backwards C in a circle instead of a
+copyright symbol.  Copyleft is based legally on copyright, so the work
+should have a copyright notice.  A copyright notice requires either
+the copyright symbol (a C in a circle) or the word
+&ldquo;Copyright&rdquo;.</p>
+
+<p>
+A backwards C in a circle has no special legal significance, so it
+doesn't make a copyright notice.  It may be amusing in book covers,
+posters, and such, but
+<a href="https://en.wikipedia.org/wiki/Copyleft#Symbol";> be
+careful how you represent it in a web page!</a>
+</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: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&gt;</a>.</p>
+
+<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to <a href="mailto:address@hidden";>
+        &lt;address@hidden&gt;</a>.</p>
+
+        <p>For information on coordinating and submitting translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+Please see the <a
+href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting translations
+of this article.</p>
+</div>
+
+<!-- Regarding copyright, in general, standalone pages (as opposed to
+     files generated as part of manuals) on the GNU web server should
+     be under CC BY-ND 4.0.  Please do NOT change or remove this
+     without talking with the webmasters or licensing team first.
+     Please make sure the copyright date is consistent with the
+     document.  For web pages, it is ok to list just the latest year the
+     document was modified, or published.
+     
+     If you wish to list earlier years, that is ok too.
+     Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+     years, as long as each year in the range is in fact a copyrightable
+     year, i.e., a year in which the document was published (including
+     being publicly visible on the web or in a revision control system).
+     
+     There is more detail about copyright years in the GNU Maintainers
+     Information document, www.gnu.org/prep/maintain. -->
+
+<p>Copyright &copy; 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004,
+2005, 2006, 2007, 2008, 2009, 2014, 2015, 2016, 2017 Free Software Foundation, 
Inc.</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: 2017/06/06 17:58:44 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>