www/philosophy po/free-doc.translist po/free-do...

[GNUN]

CVSROOT:        /web/www
Module name:    www
Changes by:     GNUN <gnun>     18/12/17 12:59:30

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

Log message:
        Automatic update by GNUnited Nations.

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

Patches:
Index: po/free-doc.translist
===================================================================
RCS file: /web/www/www/philosophy/po/free-doc.translist,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- po/free-doc.translist       12 Apr 2016 15:42:10 -0000      1.15
+++ po/free-doc.translist       17 Dec 2018 17:59:30 -0000      1.16
@@ -27,6 +27,7 @@
 <span dir="ltr"><a lang="tr" hreflang="tr" 
href="/philosophy/free-doc.tr.html">Türkçe</a>&nbsp;[tr]</span> &nbsp;
 <span dir="ltr"><a lang="uk" hreflang="uk" 
href="/philosophy/free-doc.uk.html">українська</a>&nbsp;[uk]</span> 
&nbsp;
 <span dir="ltr"><a lang="zh-cn" hreflang="zh-cn" 
href="/philosophy/free-doc.zh-cn.html">简体中文</a>&nbsp;[zh-cn]</span> 
&nbsp;
+<span dir="ltr"><a lang="zh-tw" hreflang="zh-tw" 
href="/philosophy/free-doc.zh-tw.html">繁體中文</a>&nbsp;[zh-tw]</span> 
&nbsp;
 </p>
 </div>' -->
 <link rel="alternate" type="text/html" href="/philosophy/free-doc.html" 
hreflang="x-default" />
@@ -55,4 +56,5 @@
 <link rel="alternate" type="text/html" lang="tr" hreflang="tr" 
href="/philosophy/free-doc.tr.html" title="Türkçe" />
 <link rel="alternate" type="text/html" lang="uk" hreflang="uk" 
href="/philosophy/free-doc.uk.html" title="українська" />
 <link rel="alternate" type="text/html" lang="zh-cn" hreflang="zh-cn" 
href="/philosophy/free-doc.zh-cn.html" title="简体中文" />
+<link rel="alternate" type="text/html" lang="zh-tw" hreflang="zh-tw" 
href="/philosophy/free-doc.zh-tw.html" title="繁體中文" />
 <!-- end translist file -->

Index: po/free-doc.zh-tw.po
===================================================================
RCS file: /web/www/www/philosophy/po/free-doc.zh-tw.po,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2

Index: free-doc.zh-tw.html
===================================================================
RCS file: free-doc.zh-tw.html
diff -N free-doc.zh-tw.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ free-doc.zh-tw.html 17 Dec 2018 17:59:29 -0000      1.1
@@ -0,0 +1,161 @@
+<!--#set var="ENGLISH_PAGE" value="/philosophy/free-doc.en.html" -->
+
+<!--#include virtual="/server/header.zh-tw.html" -->
+<!-- Parent-Version: 1.79 -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>為什麼自由軟體需要自由文件 - GNU 專案 - 
自由軟體基金會</title>
+
+<!--#include virtual="/philosophy/po/free-doc.translist" -->
+<!--#include virtual="/server/banner.zh-tw.html" -->
+<h2>為什麼自由軟體需要自由文件</h2>
+
+<blockquote class="announcement"><p>
+<a href="http://defectivebydesign.org/ebooks.html";>åŠ å…
¥æˆ‘們討論電子書危害的郵遞論壇</a>。
+</p></blockquote>
+
+<ul>
+<li><a href="/copyleft/fdl.html">GNU 自由文件授權條款</a></li>
+</ul>
+
+<p>
+自由作業系統中最大的缺陷不在軟體上，而在於缺少可以收錄在這些系統中的優秀自由手冊。我們有許多重要程式都沒有附帶完整的手冊。文件可是任何軟體åŒ
…中必要的組成元件；當重要的自由軟體包
中沒有隨附自由手冊時，就會是很大的空白。而現在，我們就有很多這樣的空白。</p>
+
+<p>
+很久很久以前，我想過要學 
Perl，所以找來了一份自由手冊的副本，但發現很難讀。而當我向
 Perl
+群組詢問其他方案時，他們告訴我雖然有更好的å…
¥é–€æ‰‹å†Šï¼Œä½†æŽˆæ¬Šä¸¦ä¸è‡ªç”±ã€‚</p>
+
+<p>
+這是為什麼？那些好讀手冊的作者
ï¼Œç‚ºæ­èŠç¦®å‡ºç‰ˆç¤¾ç·¨å¯«æ–‡ç« 
，並以限制性的授權條款出版：不可複製、不能修改、當然也不提供原始檔，導致這些手冊被排除在自由軟體社群之外。</p>
+
+<p>
+這不是第一次發生這種事，（對我們社群的巨大損失來說）也不會是最後一次。從那段時期開始，發行專有手冊的出版社吸引了許許多多作è€
…以授權限制他們所編寫的手冊。有好多次，我聽到一些
+GNU 使用者告訴我，他正在編寫手冊來幫助 GNU
+å°ˆæ¡ˆï¼Œç„¶å¾Œæˆ‘çš„å¸Œæœ›ç¸½åœ¨ä¸ä¹…å¾Œç ´æ»…ï¼Œå› 
為他接著跟我說，他已經和出版社簽訂了合約，而合約會限制那份手冊，å›
 此我們社群無法自由運用。</p>
+
+<p>
+有鑑於以流暢英文撰寫手冊的能力，對程式設計師族群來說極為罕見，所以å›
 æŽˆæ¬Šè€Œå¤±åŽ»å¯è‡ªç”±é‹ç”¨çš„æ‰‹å†Šæ˜¯æˆ‘å€‘é›£ä»¥è² æ“”çš„ã€‚</p>
+
+<p>
+自由文件同自由軟體一樣，所注重的是自由而非價æ 
¼ã€‚這些手冊的問題所在，並不是歐萊禮出版社為印刷本收費，收費本身沒什麼。（自由軟體基金會也販售自由的
 <a
+href="/doc/doc.html">GNU 手冊</a>的<a
+href="http://shop.fsf.org/category/books/";>印刷本</a>。）但 GNU
+手冊提供原始檔，而前面提到的那些手冊只以紙本提供。GNU 
手冊給予讀者複製與修改的權利，而前述的 Perl 
手冊不行，這類限制才是問題所在。</p>
+
+<p>
+判斷自由手冊的標準與自由軟體大致相同：確認文件是能否給予所有使用è€
…ç‰¹å®šçš„è‡ªç”±æ¬Šåˆ©ã€‚æŽˆæ¬Šæ¢æ¬¾å¿…é ˆå…è¨±æ–‡ä»¶èƒ½å†æ¬¡æ•£å¸ƒï¼ˆåŒ…
含商業再散布），如此才能讓手冊伴隨程式的每份副本提供，無論是以線上提供或印到紙上皆然。å
…è¨±ä¿®æ”¹çš„權利也很重要。</p>
+
+<p>
+ä¸€èˆ¬è€Œè¨€ï¼Œæˆ‘èªç‚ºäººå€‘æ²’æœ‰å¿…è¦æ“æœ‰ä¿®æ”¹æ‰€æœ‰é¡žåž‹æ–‡ç« 
與書籍的權利。書面著作會遇到的問題不見得與軟體相同。舉例來說，我認為不管是ä½
 ，或是我，都無權修改如本文這類描述作者
ç¶“æ­·èˆ‡è§€é»žçš„æ–‡ç« ã€‚</p>
+
+<p>
+ä½†æ˜¯æœ‰å€‹ç‰¹æ®Šçš„åŽŸå› 
，能說明為什麼可以自由修改自由軟體的文件相當重要。當人們行使了修改軟體的權利，新增或修改部份功能時，如果他們做事å¤
 
認真，那他們也會一併修改手冊——如此才可以為修改後的程式提供準確可é
 
的文件。一份禁止程式設計師認真完成他們工作的手冊，或è€
…
更精確來說，一旦他們修改了程式，就得重新編寫一本新的手冊，並不能滿足我們社群的需求。</p>
+
+<p>
+ä»¤äººç„¡æ³•æŽ¥å—çš„æ˜¯å…¨é¢ç¦æ­¢ä¿®æ”¹ï¼›è€Œä¹Ÿæœ‰ä¸æœƒé€ 
æˆå•é¡Œçš„åšæ³•ï¼Œåƒæ˜¯å°ä¿®æ”¹æ–¹æ³•åŠ 
上某些限制。例如，要求保留原作者
的著作權聲明、散布條款、作者
名單……等資訊，這都不是問題。還有，要求修改後版本附上聲明表示是修改過的版本，或是要求某些與技術無關的部份å
…§å®¹ï¼Œæ•´æ®µä¸èƒ½åˆªé™¤æˆ–修改也是可以的（有些
+GNU 手冊就包含這類條款）。</p>
+
+<p>
+é€™é¡žé™åˆ¶ä¸æ˜¯å•é¡Œï¼Œå› 
為不會阻礙盡責的程式設計師修改手冊以é…
åˆä¿®æ”¹å¾Œçš„程式。換句話說，這不會妨礙自由軟體社群充
份利用該手冊。</p>
+
+<p>
+但是，手冊中所有的 <em>技術</em>
+內容都必é 
ˆå¯ä»¥ä¿®æ”¹ï¼Œä¸¦ä¸”可以透過所有常用媒體，以及所有常見管道散布修改成果。否則，這樣的限制就會妨礙社群，讓手冊不再自由，而我們就得要再重寫另一份手冊。</p>
+
+<p>
+不幸的是，每當有專有手冊出現的時候，就很難再找到人去寫另外一本替補的自由手冊了。障礙的主å›
 æ˜¯å¾ˆå¤šä½¿ç”¨è€…èªç‚ºï¼Œå°ˆæœ‰æ‰‹å†Šçš„å“è³ªå·²ç¶“å¤ 
好了，所以沒有必
要再寫另一份自由手冊。他們沒看到自由作業系統這一塊需要填補的空白。</p>
+
+<p>
+ç‚ºä»€éº¼ä½¿ç”¨è€…è¦ºå¾—å°ˆæœ‰æ‰‹å†Šå·²ç¶“å¤ 
å¥½äº†å‘¢ï¼Ÿæœ‰äº›äººå¯å¾žæ²’æƒ³éŽé€™å€‹å•é¡Œï¼Œè€Œæˆ‘å¸Œæœ›é€™ç¯‡æ–‡ç« 
可以發揮作用改變現狀。</p>
+
+<p>
+è‡³æ–¼å…¶ä»–ä½¿ç”¨è€…å‰‡èªç‚ºï¼Œå°ˆæœ‰æ‰‹å†Šæ˜¯å¯ä»¥æŽ¥å—çš„ï¼ŒåŽŸå› 
與許多人認為專有軟體是可以接受的理由相同：他們純粹只看實用與否，而不是以自由為評判標準。這些人有權表達他們的觀點，但這些觀點源於缺乏自由的價值觀，å›
 
此對於我們這些非常重視自由的人來說，這些意見並不值得參考。</p>
+
+<p>
+è«‹å‘Šè¨´ç¤¾æœƒå¤§çœ¾é€™å€‹è­°é¡Œï¼šæˆ‘å€‘æ­£å› 
專有授權的出版品而失去自由的手冊。如果我們將專有手冊的缺憾之處傳遍å
…¨ä¸–界，也許下一位想要編寫文件協助 GNU
+的人，就能及早明瞭讓手冊自由的重要性。</p>
+
+<p>
+我們也可以多鼓勵商業出版社銷售自由、採用著作傳式授權的手冊，取代專有手冊。有個ä½
 可以幫上忙的方法，就是在購買手冊之前，å…
ˆç¢ºèªå®ƒçš„授權條款，並優先考æ…
®ä»¥è‘—作傳保護自由的手冊。</p>
+<p>
+[注意：我們有維護一份<a href="/doc/other-free-books.html">å…
¶ä»–出版社發行的自由書籍書單</a>]</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: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: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, 2009, 2015, 2016 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">&lt;s8321414
+(at) gmail (dot) com&gt;</a>, 2018.
+<b>æ ¡å°</b>：曾政嘉 <a href="mailto:zerngjia (at) gmail (dot) 
com">&lt;zerngjia
+(at) gmail (dot) com&gt;</a>, 2018.</div>
+
+<p class="unprintable"><!-- timestamp start -->
+更新時間︰
+
+$Date: 2018/12/17 17:59:29 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>

Index: po/free-doc.zh-tw-en.html
===================================================================
RCS file: po/free-doc.zh-tw-en.html
diff -N po/free-doc.zh-tw-en.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ po/free-doc.zh-tw-en.html   17 Dec 2018 17:59:30 -0000      1.1
@@ -0,0 +1,214 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.79 -->
+<title>Why Free Software needs Free Documentation
+- GNU Project - Free Software Foundation</title>
+
+<!--#include virtual="/philosophy/po/free-doc.translist" -->
+<!--#include virtual="/server/banner.html" -->
+   
+<h2>Why Free Software needs Free Documentation</h2>
+
+<blockquote class="announcement"><p>
+<a href="http://defectivebydesign.org/ebooks.html";>Join our mailing list
+about the dangers of eBooks</a>.
+</p></blockquote>
+
+<ul>
+<li><a href="/copyleft/fdl.html">The GNU Free Documentation License</a></li>
+</ul>
+
+<p>
+The biggest deficiency in free operating systems is not in the
+software&mdash;it is the lack of good free manuals that we can include
+in these systems.  Many of our most important programs do not come
+with full manuals.  Documentation is an essential part of any software
+package; when an important free software package does not come with a
+free manual, that is a major gap.  We have many such gaps today.</p>
+
+<p>
+Once upon a time, many years ago, I thought I would learn Perl.  I got
+a copy of a free manual, but I found it hard to read.  When I asked
+Perl users about alternatives, they told me that there were better
+introductory manuals&mdash;but those were not free.</p>
+
+<p>
+Why was this?  The authors of the good manuals had written them for
+O'Reilly Associates, which published them with restrictive
+terms&mdash;no copying, no modification, source files not
+available&mdash;which exclude them from the free software
+community.</p>
+
+<p>
+That wasn't the first time this sort of thing has happened, and (to
+our community's great loss) it was far from the last.  Proprietary
+manual publishers have enticed a great many authors to restrict their
+manuals since then.  Many times I have heard a GNU user eagerly tell
+me about a manual that he is writing, with which he expects to help
+the GNU Project&mdash;and then had my hopes dashed, as he proceeded to
+explain that he had signed a contract with a publisher that would
+restrict it so that we cannot use it.</p>
+
+<p>
+Given that writing good English is a rare skill among programmers, we
+can ill afford to lose manuals this way.</p>
+
+<p>
+Free documentation, like free software, is a matter of freedom, not
+price.  The problem with these manuals was not that O'Reilly
+Associates charged a price for printed copies&mdash;that in itself is
+fine.  (The Free Software Foundation
+<a href="http://shop.fsf.org/category/books/";>sells printed
+copies</a> of free <a href="/doc/doc.html">GNU manuals</a>, too.)  But
+GNU manuals are available in source code form, while these manuals are
+available only on paper.  GNU manuals come with permission to copy and
+modify; the Perl manuals do not.  These restrictions are the problems.</p>
+
+<p>
+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 redistribution) must be
+permitted, so that the manual can accompany every copy of the program,
+on line or on paper.  Permission for modification is crucial too.</p>
+
+<p>
+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.  The issues
+for writings are not necessarily the same as those for software.  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.</p>
+
+<p>
+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 manual
+which forbids programmers from being conscientious and finishing the job, or
+more precisely requires them to write a new manual from scratch if
+they change the program, does not fill our community's needs.</p>
+
+<p>
+While a blanket prohibition on modification is unacceptable, some
+kinds of limits on the method of modification 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.  (Some GNU manuals have them.)</p>
+
+<p>
+These kinds of restrictions are not a problem because, as a practical
+matter, 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.</p>
+
+<p>
+However, it must be possible to modify all the <em>technical</em>
+content of the manual, and then distribute the result through all the usual
+media, through all the usual channels; otherwise, the restrictions do
+block the community, the manual is not free, and so we need another
+manual.</p>
+
+<p>
+Unfortunately, it is often hard to find someone to write another
+manual when a proprietary manual exists.  The obstacle is that many
+users think that a proprietary manual is good enough&mdash;so they
+don't see the need to write a free manual.  They do not see that the
+free operating system has a gap that needs filling.</p>
+
+<p>
+Why do users think that proprietary manuals are good enough?  Some
+have not considered the issue.  I hope this article will do something
+to change that.</p>
+
+<p>
+Other users consider proprietary manuals acceptable for the same
+reason so many people consider proprietary software acceptable: they
+judge in purely practical terms, not using freedom as a criterion.
+These people are entitled to their opinions, but since those opinions
+spring from values which do not include freedom, they are no guide for
+those of us who do value freedom.</p>
+
+<p>
+Please spread the word about this issue.  We continue to lose manuals
+to proprietary publishing.  If we spread the word that proprietary
+manuals are not sufficient, perhaps the next person who wants to help
+GNU by writing documentation will realize, before it is too late, that
+he must above all make it free.</p>
+
+<p>
+We can also encourage commercial publishers to sell free, copylefted
+manuals instead of proprietary ones.  One way you can help this is to
+check the distribution terms of a manual before you buy it, and
+prefer copylefted manuals to noncopylefted ones.</p>
+<p>
+[Note: We maintain a <a href="/doc/other-free-books.html">page
+that lists free books available from other publishers</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, 2009, 2015, 2016 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: 2018/12/17 17:59:30 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>