www-commits
[Top][All Lists]
Advanced

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

www licenses/fdl-howto-opt.zh-cn.html philosoph...


From: GNUN
Subject: www licenses/fdl-howto-opt.zh-cn.html philosoph...
Date: Tue, 2 Jan 2018 08:31:27 -0500 (EST)

CVSROOT:        /web/www
Module name:    www
Changes by:     GNUN <gnun>     18/01/02 08:31:27

Modified files:
        licenses       : fdl-howto-opt.zh-cn.html 
        philosophy     : free-sw.zh-cn.html 
        philosophy/po  : free-sw.zh-cn-en.html free-sw.zh-cn.po 
Added files:
        licenses/po    : fdl-howto-opt.zh-cn-en.html 

Log message:
        Automatic update by GNUnited Nations.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/fdl-howto-opt.zh-cn.html?cvsroot=www&r1=1.3&r2=1.4
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/fdl-howto-opt.zh-cn-en.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/free-sw.zh-cn.html?cvsroot=www&r1=1.10&r2=1.11
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/free-sw.zh-cn-en.html?cvsroot=www&r1=1.3&r2=1.4
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/free-sw.zh-cn.po?cvsroot=www&r1=1.23&r2=1.24

Patches:
Index: licenses/fdl-howto-opt.zh-cn.html
===================================================================
RCS file: /web/www/www/licenses/fdl-howto-opt.zh-cn.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- licenses/fdl-howto-opt.zh-cn.html   30 Dec 2011 05:16:46 -0000      1.3
+++ licenses/fdl-howto-opt.zh-cn.html   2 Jan 2018 13:31:27 -0000       1.4
@@ -1,210 +1,156 @@
-<!DOCTYPE html PUBLIC "-//IETF//DTD HTML 2.0//EN">
-<HTML>
-<HEAD>
-<TITLE>ÈçºÎʹÓà GFDL ËùÌṩµÄ¿ÉÑ¡ÉèÖã¨feature£© - GNU ¹¤³Ì - 
×ÔÓÉÈí¼þ»ù½ð»á£¨FSF£©</TITLE>
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=gb2312">
-<LINK REV="made" HREF="mailto:address@hidden";>
-</HEAD>
-<BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#1F00FF" ALINK="#FF0000" 
VLINK="#9900DD">
-<H3>ÈçºÎʹÓà GFDL ËùÌṩµÄ¿ÉÑ¡ÉèÖã¨feature£©</H3>
-       <a href="http://www.stallman.org/";>Àí²éµÂ¡¤Ë¹¶à¶ûÂü</a> Öø
-
-<P>
-
-<A HREF="/graphics/philosophicalgnu.html"><IMG 
SRC="/graphics/philosophical-gnu-sm.jpg"
-   ALT=" [image of a Philosophical Gnu] "
-   WIDTH="160" HEIGHT="200"></A>
-<!-- Please keep this list alphabetical!!!  -->
-[
-  <A HREF="/licenses/fdl-howto-opt.zh-cn.html">¼òÌåÖÐÎÄ</A>
-| <A HREF="/licenses/fdl-howto-opt.zh-tw.html">·±ÌåÖÐÎÄ</A>
-| <A HREF="/licenses/fdl-howto-opt.en.html">Ó¢ÎÄ</A>
-| <A HREF="/licenses/fdl-howto-opt.ko.html">³¯ÏÊÓï</A>
-| <A HREF="/licenses/fdl-howto-opt.pl.html">²¨À¼Óï</A>
-]
-
-<P>
-<HR>
-<P>
-<H4>ÈçºÎʹÓà GFDL ËùÌṩµÄ¿ÉÑ¡ÉèÖã¨feature£©</H4>
-
-<P>
-<A HREF="/licenses/fdl.html">GNU FDL</A> (GNU Free Documentation License)
-°üÀ¨ÁËÁ½ÖÖ¿ÉÑ¡ÉèÖã¬
-<A NAME="TOC1" HREF="#SEC1"><STRONG>ºã³£Õ½Ú</STRONG></A> ºÍ
-<A NAME="TOC2" HREF="#SEC2"><STRONG>·âÃæÎÄ×Ö</STRONG></A> £¬
-¡²Ìṩ¸øÔÚ¡³µ±ÄúÏëÒªµÄʱºò¿ÉÒÔʹÓá£
-ʹÓÃÊÖ²áµÄÐí¿ÉÉùÃ÷Ó¦¸ÃҪ˵Ã÷ÄúÊÇ·ñÓÐʹÓÃÕâЩÉèÖá£
-<P>
-
-×î¼òµ¥µÄ×´¿ö¾ÍÊÇÄúûÓÐʹÓÃÕâЩÉèÖá£
-ÕâÑùµÄ»°Ðí¿ÉÉùÃ÷Ó¦¸ÃÒªÕâô˵£¬ÏñÊÇ£º
-<P>
-<PRE>
-      Permission is granted to copy, distribute and/or modify this
-      document under the terms of the GNU Free Documentation License,
-      Version 1.1 or any later version published by the Free Software
-      Foundation; with no Invariant Sections, no Front-Cover Texts and
-      no Back-Cover Texts.  A copy of the license is included in the
-      section entitled "GNU Free Documentation License".
-</PRE>
-<P>
-µ«ÊÇÈç¹ûÄúÏëҪʹÓÃÕâЩÉèÖã¬
-ÕâÀïÓÐÒ»¸ö¡¸ËüÃǵÄÄ¿±ê´òËãΪºÎ¡¹ÒÔ¼°¡¸ÈçºÎʹÓÃËüÃÇ¡¹µÄ½âÊÍ¡£
-<P>
-
-<H4><A NAME="SEC1" HREF="#TOC1">ºã³£Õ½Ú</A></H4>
-<P>
-ºã³£Õ½ڵÄÏë·¨¾ÍÊÇ£¬
-ËüÃǸøÓèÄúÒ»ÖÖ±í´ïÓйØì¶Õâ¸öÒéÌâµÄ¡¸·Ç¼¼Êõ¸öÈËÒâ¼û¡¹µÄ·½Ê½¡£
-<P>
-ÔÚ×ÔÓÉʹÓÃÊÖ²áÖУ¬
-Ò»¸öºã³£µÄ·Ç¼¼ÊõÐÔÕ½ڵľ­µä·¶Àý¾ÍÊÇ
-<A HREF="/gnu/manifesto.html">¡¶GNU ÉùÃ÷Êé¡·£¨GNU Manifesto£©</A> £¬
-Ëü±»°üÀ¨ÔÚ¡¶GNU Emacs ʹÓÃÊֲᡷÖС£
-¡¶GNU ÉùÃ÷Êé¡·²¢Ã»ÓÐ˵Ã÷ÈκÎÓйØì¶ÈçºÎʹÓà Emacs ×÷±à¼­µÄÊ£¬
-µ«Ëü½âÊÍÁËΪʲôÎÒ±àд GNU Emacs µÄÔ­Òò --
-ʹËü×÷Ϊ GNU ²Ù×÷ϵͳµÄÒ»¸ö±ØÒª²¿·Ý£¬
-´Ó¶ø¸øÓèµçÄÔʹÓÃÕßÔÚÒ»¸öÉçÍÅÀïÃæºÏ×÷µÄ×ÔÓÉ¡£
-ÓÉ춡¶GNU ÉùÃ÷Ê顷չʾÁË GNU ¹¤³ÌµÄÔ­Ôò£¬
-¶ø·Ç GNU Emacs µÄ¹¦ÄÜÌØÉ«£¬
-ÎÒÃǾö¶¨ÁËÔÚµ±ÖØÐÂÉ¢²¼¡¶Emacs ʹÓÃÊֲᡷʱ£¬
-ÆäËûÈ˲»¿ÉÒÔÒƳý»òÕ߸ü¶¯Ëü£¬
-²¢ÇÒÎÒÃǽ«ÄÇÏîÒªÇóд½øÁËÐí¿ÉÖ¤¡£
-ʵ¼ÊÉÏ£¬
-ËäÈ»²¢Ã»ÓÐʹÓÃÄǸöÊõÓ
-ÎÒÃÇʹ¡¶GNU ÉùÃ÷Êé¡·³ÉÁËÒ»·Ýºã³£Õ½ڡ£
-½ñÌìÈç¹ûÎÒÃÇҪʹÓà GNU FDL Õâô×öµÄ»°£¬
-ÎÒÃǻὫÐí¿ÉÉùÃ÷д³ÉÏñÊÇ£º
-<P>
-<PRE>
-      Permission is granted to copy, distribute and/or modify this
-      document under the terms of the GNU Free Documentation License,
-      Version 1.1 or any later version published by the Free Software
-      Foundation; with the Invariant Sections being just "GNU
-      Manifesto", with no Front-Cover Texts, and with no Back-Cover
-      Texts.  A copy of the license is included in the section
-      entitled "GNU Free Documentation License".
-</PRE>
-<P>
-Õâ˵Ã÷ÁË¡¸¡¶GNU ÉùÃ÷Êé¡·¡¹Õâ¸öÕ½ÚÊÇΨһµÄºã³£Õ½ڡ£
-<P>
-¾ÉµÄ¡¶Emacs ʹÓÃÊֲᡷÐí¿É£¬
-²¢Ã»ÓÐÔÊÐí¡¸ÐÞ¸ÄÒÔ¼°ÖØÐÂÉ¢²¼Õâ¸öʹÓÃÊÖ²áµÄÈË¡¹
-Ôö¼Óеĺ㳣Õ½ڵÄȨÀû¡£
-µ«ÊÇÔÚ½« GNU FDL µÄ¸ÅÄî¼ÓÒÔ¹«Ê½»¯£¬
-ʹÆä³ÉΪ½ÏΪһ°ãµÄ°æ±¾Ê±£¬
-ÎÒ¾õµÃÄÇЩÐÞ¸ÄÁËÒ»·ÝʹÓÃÊÖ²áµÄÈË£¬
-Èç¹ûÒ²¿ÉÒÔÈçͬµÚÒ»¸ö×÷ÕßÄÇ°ãµØ׫дºã³£Õ½ڣ¬
-Ó¦¸Ã±È½ÏºÏºõµÀÒåÔ­Ôò¡£
-Òò´Ë FDL ÔÊÐíÕâ¸ö×÷Ϊ¡£
-<P>
-µ«ÊÇÄǸöÉèÖÃÐèÒªÒ»ÖÖ°²È«»úÖÆ£¬
-±ÜÃâËü±»ÀÄÓôӶøΣ¼°µ½Ê¹ÓÃÊÖ²áµÄ×ÔÓÉ״̬¡£
-ÐÞ¸ÄÁËÓÉij¼×Ëù׫дµÄʹÓÃÊÖ²áµÄijÒÒ£¬
-²»Äܹ»Ê¹ÈκÎij¼×µÄÎĵµ*Ϊºã³£µÄ£¬
-ÒòΪÄÇÑùÒ»À´»á¾Ü¾øÁËij±û¸ü½øÒ»²½µØÐÞ¸ÄËüµÄÔÊÐí¡£
-ͬÑùµØ£¬
-Èç¹ûijÒÒÔö¼ÓÁ˶îÍâµÄ´ÎÒªÒéÌâµÄÎĵµ*£¬
-ÕâÔö¼ÓÁ˵ÄÎĵµ*Ò²²»¿ÉÒÔÊǺ㳣µÄ£»
-Ëü±¾Éí±ØÐë¿ÉÒÔΪÆäËûÈËËùÐ޸ġ£
-FDL ¹Øì¶Ôö¼Óºã³£Õ½ڵÄÌõ¼þÌṩÁËÕâÏȫ»úÖÆ¡£
-<P>
-ʹÓÃÊֲᲢ²»Ò»¶¨ÒªÓк㳣Õ½ڡ£
-×î¼òµ¥µÄ×´¿öÊǸù±¾¾ÍûÓС£
-Äú²»ÐèÒª½« GNU FDL Ëü±¾ÉíÁÐΪºã³£Õ½ڣ¬
-ÒòΪ FDL Çå³þÃ÷°×µØ˵Ã÷ FDL Ëü±¾Éí²»¿ÉÒÔ±»¸ü¶¯¡£
-FDL Ò²½«Ìض¨Õ½ڱêÌâ·Ö±ð¿ªÀ´£¬
-ÏñÊÇ¡¸ÀúÊ·¡¹¡¢¡¸¹±Ïס¹ºÍÆäËü¡²µÄһЩ¡³¡£
-Äú²»Ó¦¸Ã½«ÕâЩÕ½ÚÁÐΪºã³£µÄ£¬
-ÒòΪ FDL ÒѾ­¸øÓèÁËÕâЩÕ½ڹæÔò¡£
-<P>
-<H4><A NAME="SEC2" HREF="#TOC2">·âÃæÎÄ×Ö</A></H4>
-<P>
-·âÃæÎÄ×ÖÊÇÄú¼á³ÖÔÚµ±Ê¹ÓÃÊֲᱻ³ö°æʱ£¬
-±ØÐëÓ¡Ë¢ÔÚ·âÃæµÄһСƬ¶ÏÎÄ×Ö£¬
-¼´Ê¹ÊÇÓÉij¸öÆäËûÈ˳ö°æËüʱÒàͬ¡£
-Äú¿ÉÒÔÔØÃ÷±ØÐë±»Ó¡Ë¢ÔÚÇ°·âÃæµÄ¡¸Ç°·âÃæÎÄ×Ö¡¹£¬
-ÄúÒ²¿ÉÒÔÔØÃ÷±ØÐë±»Ó¡Ë¢ÔÚºó·âÃæµÄ¡¸ºó·âÃæÎÄ×Ö¡¹¡£
-Äú¿ÉÒÔÔØÃ÷ÆäÖÐÈκÎÒ»¸ö¡£
-<P>
-·âÃæÎÄ×ÖÊÇÒ»ÖÖеÄÉèÖã¬
-ËùÒÔÎÒûÓа취ÒýÓÃËüÃǹýÈ¥µÄʹÓÃÀý×Ó£¬
-µ«ÊÇËüËù´òËãµÄÄ¿±êºÜ¼òµ¥¡£
-ËûÃÇÊÇÓÃÀ´¸øÓèÒ»¸ö±à¼­Æ·µÄԭʼ³ö°æÕߣ¬
-Ò»¸öÇëÇó»òÕß¹ÄÀøÈËÃǹºÂòËûÃdzö°æµÄ¿½±´£¬
-¶ø²»ÊÇ´ÓһЩÆäËûµÄÖØÓ¡ÉÌ´¦¹ºÂòµÄÒ»ÖÖ·½Ê½¡£
-¾ÙÀýÀ´Ëµ£¬
-ÎÒÃÇ¿ÉÒÔÉèÏëÔØÃ÷Õâ¶Î×÷Ϊ·âÃæÎÄ×Ö£º
-<P>
-<PRE>
-    Free Manuals Inc. paid Alyssa P. Hacker to write this manual
-    and asks for your support through buying the Free Manuals edition.
-</PRE>
-ÕâÒ²Ðí¿ÉÒÔ°ïÖú×ÔÓÉÊֲṫ˾ÔÚ³ö°æ×ÔÓÉÊÖ²áµÄÉúÒâÖлñµÃ³É¹¦ --
-ÖÁÉÙ£¬
-ÄÇÊǸöÉèÏëµÄÇé¿ö¡£
-ÒªÔØÃ÷Õâ¸öºó·âÃæÎÄ×Ö£¬
-×ÔÓÉÊֲṫ˾Ӧ¸ÃÒª½«Ðí¿ÉÉùÃ÷д³ÉÕâÑù£º
-<P>
-<PRE>
-      Permission is granted to copy, distribute and/or modify this
-      document under the terms of the GNU Free Documentation License,
-      Version 1.1 or any later version published by the Free Software
-      Foundation; with no Invariant Sections, no Front-Cover Texts, and
-      one Back-Cover Text: "Free Manuals Inc. paid Alyssa P. Hacker to
-      write this manual and asks for your support through buying the
-      Free Manuals edition."  A copy of the license is included in the
-      section entitled "GNU Free Documentation License".
-</PRE>
-<P>
-<HR>
-
-·µ»Ø <A HREF="/home.zh-cn.html">GNU Ê×Ò³</A>¡£
-
-<P>
-Ç뽫ÓÐ¹Ø ×ÔÓÉÈí¼þ»ù½ð»á Óë GNU µÄ ²éѯ Óë ÎÊÌâ Ë͵½
-<A HREF="mailto:address@hidden";><EM>address@hidden</EM></A>¡£
-ÄãÒ²¿ÉÒÔʹÓà <A HREF="/home.html#ContactInfo">ÆäËû·½·¨ÁªÏµ</A>
-×ÔÓÉÈí¼þ»ù½ð»á¡£
-
-<P>
-Ç뽫ÓйØÍøÒ³µÄÒâ¼ûË͵½
-<A HREF="mailto:address@hidden";><EM>address@hidden</EM></A>£¬
-ÆäËûÎÊÌâÔòË͵½
-<A HREF="mailto:address@hidden";><EM>address@hidden</EM></A>¡£
-
-<P>
-Ç뽫ÓйØÖÐÎÄÍøÒ³µÄÒâ¼ûË͵½
-<A HREF="mailto:address@hidden";><EM>address@hidden</EM></A>£¬
-ÆäËûÎÊÌâÔòË͵½
-<A HREF="mailto:address@hidden";><EM>address@hidden</EM></A>¡£
-
-<P>
-Copyright (C) 2000 Free Software Foundation, Inc.,
-51 Franklin St, Fifth Floor, Boston, MA  02110,  USA
-
-<P>
-Verbatim copying and distribution of this entire article is
-permitted in any medium, provided this notice is preserved.
-<BR>
-¡¾±¾ÎÄÔÊÐíÔÚ²»±ä¸üÎĵµÄÚÈݵÄÇ°ÌáÏ¿¯µÇÔÚÈκÎÐÎʽµÄýÌåÖУ¬
-µ«Ðè±£Áô´ËÉùÃ÷¡£¡¿
-
-<P>
-·­Ò룺Áõ ÕѺꡣ
-<BR>
-ÑéÖ¤£ºÂí ѩƼ¡£
-<BR>
-Ç뽫Óйط­ÒëµÄÎÊÌâË͵½
-<A HREF="http://savannah.gnu.org/projects/chinese/";>GNU/CTT</A> µÄ
-<A HREF="mailto:address@hidden";>·­ÒëÈËÔ±</A>¡£
-
-<P>
-Updated:
-<!-- hhmts start -->
-Last modified: Sun Jul 15 13:06:38 CEST 2001
-<!-- hhmts end -->
-<HR>
-</BODY>
-</HTML>
+<!--#set var="ENGLISH_PAGE" value="/licenses/fdl-howto-opt.en.html" -->
+
+<!--#include virtual="/server/header.zh-cn.html" -->
+<!-- Parent-Version: 1.79 -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>如何使用FDL的可选功能 - GNU工程 - 
自由软件基金会</title>
+
+<!--#include virtual="/licenses/po/fdl-howto-opt.translist" -->
+<!--#include virtual="/server/banner.zh-cn.html" -->
+<h2>如何使用FDL的可选功能</h2>
+
+<p><a href="http://www.stallman.org/";>Richard Stallman</a> 著</p>
+
+<p>
+<a href="/licenses/fdl.html">GNU FDL</a>(GNU自由文档许可证)包
括了两种可选功能,<a
+href="#SEC1"><strong>恒定部分</strong></a>和<a
+href="#SEC2"><strong>封面文字</strong></a>,当您想要的时候可以使用它们。手册的许可声明中应该要说明您是否有使用这些功能。</p>
+
+<p>
+最简单的情
况就是您没有使用这些功能。此时,许可声明应该要明说,比如:</p>
+
+<pre>
+      您有权æ 
¹æ®è‡ªç”±è½¯ä»¶åŸºé‡‘会发布的GNU自由文档许可证1.3及更高版的条款
+      
复制、发布和/或修改本文档;本文档没有恒定部分、没有封面文字、也没
+      有封底文字。许可证的拷贝包含在æ 
‡é¢˜ä¸ºâ€GNU自由文档许可证“的部分。
+</pre>
+<p>
+但是如果您想要使用这些功能,请参看它们的目æ 
‡æ˜¯ä»€ä¹ˆä»¥åŠå¦‚何使用它们的内容。</p>
+
+<h3 id="SEC1">恒定部分</h3>
+<p>
+恒定部分给予您一种表达有å…
³äºŽæœ¬è®®é¢˜çš„非技术性个人意见的方式。</p>
+<p>
+在自由使用手册中,一个恒定的非技术性章节的经å…
¸èŒƒä¾‹å°±æ˜¯<a href="/gnu/manifesto.html">GNU宣言</a>,它被包括在GNU
+Emacs使用手册中。GNU宣言并没有说明任何和如何使用Emacs作编辑有å
…³çš„事,但它解释了为什么我编写GNU
+Emacs&mdash;使它作为GNU操作系统的一个必
要部份,从而给予电脑用户在社区里合作的自由。由于GNU宣言展示了GNU工程的原则,而非GNU
+Emacs的功能特色,我们决定了在重新发布Emacs
+使用手册时,其他人不可以移除或者
改动它,并且我们将此项要求写进了许可证。实际
上,虽然并没有使用该术语,我们使GNU宣言成了一个恒定部分。今天,如果我们要这æ
 ·è§„定GNU
+FDL的话,我们会将许可声明写成:</p>
+
+<pre>
+      您有权æ 
¹æ®è‡ªç”±è½¯ä»¶åŸºé‡‘会发布的GNU自由文档许可证1.3及更高版的条款
+      
复制、发布和/或修改本文档;本文档只有“GNU宣言”作为恒定部分、没有
+      封面文字、也没有封底文字。许可证的拷贝包含在æ 
‡é¢˜ä¸ºâ€GNU自由文档许
+      可证“的部分。
+</pre>
+<p>
+这说明了&rdquo;GNU宣言&ldquo;是文档的唯一恒定部分。 </p>
+<p>
+旧的Emacs使用手册的许可证没有å…
è®¸ä¿®æ”¹ä»¥åŠé‡æ–°å‘布手册的人增加
新的恒定部分。但是在将GNU
+FDL的概念定型,使å…
¶æˆä¸ºæ›´ä¸ºé€šç”¨çš„版本时,我觉得让那些修改了手册的人也拥有像第一个作è€
…那样撰写恒定部分的权利,更合乎道义原则。因此FDLå…
è®¸è¿™æ ·åšã€‚</p>
+<p>
+但是这个功能需要一种安全机制,避å…
å®ƒè¢«æ»¥ç”¨ä»Žè€Œå±åŠåˆ°æ‰‹å†Œçš„自由状态。修改了由某甲所撰写的手册的某乙,不能够使任何某甲的文档成为恒定部分,å›
 ä¸ºé‚£æ ·å°±ä¼šå‰¥å¤ºäº†æŸä¸™æ›´è¿›ä¸€æ­¥åœ°ä¿®æ”¹å®ƒçš„权利。同æ 
·åœ°ï¼Œå¦‚果某乙为文档增加了额外的议题,那么增加
议题的文档也不可以是恒定的;它本身必须可以为å…
¶ä»–人所修改。FDL关于增加恒定部分的条件就提供了这种安å…
¨æœºåˆ¶ã€‚</p>
+<p>
+手册并不一定要有恒定部分。最简单的状况是æ 
¹æœ¬å°±æ²¡æœ‰ã€‚您不需要将GNU
+FDL本身列为恒定部分,因为FDL清
楚明白地说明它本身不可以被更动。FDL也将特定章节按æ 
‡é¢˜åˆ†åˆ«å¼€æ¥ï¼Œæ¯”如&ldquo;历史&rdquo;、&ldquo;贡献&rdquo;和å…
¶ä»–部分。您不应该将这些部分列为恒定的,因
为FDL已经给予它们特定的规则。</p>
+
+<h3 id="SEC2">封面文字</h3>
+<p>
+封面文字是在当手册出版时,您坚持必
须印刷在封面的一段短小文字,即使是由å…
¶ä»–人出版时也是一样。您可以指定必
须被印刷在封面的&ldquo;封面文字&rdquo;,您也可以指定必
须被印刷在封底的&ldquo;封底文字&rdquo;。您可以每一个都指定。</p>
+<p>
+封面文字是一种新的功能,所以我没有办法引用它们过去的使用例子,但是它的目æ
 ‡å¾ˆç®€å•ã€‚他们给予某个发行版本的原始出版者
一种手段,让他们能够请求或者
鼓励人们购买他们出版的拷贝,而不是从å…
¶ä»–的重印商处购买。举例来说,我们可以设想指定以下这段作为封面文字:</p>
+
+<pre>
+    自由手册公司雇佣Alyssa P. Hacker编写此手册。我们请求您
+    购买由自由手册公司出版的手册以示对我们的支持。
+</pre>
+<p>
+这也许可以帮助自由手册å…
¬å¸åœ¨å‡ºç‰ˆè‡ªç”±æ‰‹å†Œçš„生意中获得成功&mdash;至少,这是个计划。要指定封底文字,自由手册å
…¬å¸åº”该将许可声明写成这样:</p>
+
+<pre>
+      您有权æ 
¹æ®è‡ªç”±è½¯ä»¶åŸºé‡‘会发布的GNU自由文档许可证1.3及更高版的条款
+      
复制、发布和/或修改本文档;本文档没有恒定部分、没有封面文字、有一
+      段封底文字:“自由手册公司雇佣Alyssa P. 
Hacker编写此手册。我们请
+      求您购买由自由手册å…
¬å¸å‡ºç‰ˆçš„手册以示对我们的支持。“许可证的拷贝包含
+      在标题为”GNU自由文档许可证“的部分。
+</pre>
+
+<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-cn.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>请将有å…
³è‡ªç”±è½¯ä»¶åŸºé‡‘会(FSF)&amp;GNU的一般性问题发送到<a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>。也可以通过<a
+href="/contact/">å…
¶ä»–联系方法</a>联系自由软件基金会(FSF)。请将无
效链接、其他错误或建议发送给<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="/server/standards/README.translations.html">翻译须知</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; 2000, 2008, 2014, 2016 Free Software Foundation, Inc.</p>
+
+<p>本页面使用<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.zh-cn.html" -->
+<div class="translators-credits">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
+<b>翻译</b>: 刘昭宏 <a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a><br></br>
+<b>审校</b>: 马雪萍<br></br>
+<b>翻译团队</b>:<a rel="team"
+href="https://savannah.gnu.org/projects/www-zh-cn/";>&lt;CTT&gt;</a>,2018。</div>
+
+<p class="unprintable"><!-- timestamp start -->
+最后更新:
+
+$Date: 2018/01/02 13:31:27 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>

Index: philosophy/free-sw.zh-cn.html
===================================================================
RCS file: /web/www/www/philosophy/free-sw.zh-cn.html,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
--- philosophy/free-sw.zh-cn.html       31 Dec 2017 08:24:44 -0000      1.10
+++ philosophy/free-sw.zh-cn.html       2 Jan 2018 13:31:27 -0000       1.11
@@ -30,18 +30,14 @@
 </blockquote>
 
 <p>
-&ldquo;自由软件&rdquo;
-尊重用户的自由,并且尊重整个社区。粗略来讲,一个软件如果是自由软件,这意味着<b>用户可以自由地运行,拷贝,分发,学ä¹
 ï¼Œä¿®æ”¹å¹¶æ”¹è¿›è¯¥è½¯ä»¶</b>。因此,&ldquo;
-自由软件 &rdquo; 是关乎自由的问题,与价格无å…
³ï¼Œè½¯ä»¶å¦‚何定价并不影响它是否被归类为自由软件。英文中,我们使用Free
-Software。由于Free一词既有自由,也有免费的意思。而Free 
Software中的Free是指 &ldquo; 自由言论 &rdquo;
-中的自由,而非 &ldquo; 免费 &rdquo; 这一意项。为避å…
æ­§ä¹‰ï¼Œåœ¨ä½¿ç”¨è‹±æ–‡æ—¶ï¼Œæˆ‘们也会借用法语或西班牙语的&ldquo;Libre
-Software&rdquo; 来指自由软件。
+&ldquo;自由软件&rdquo;尊重用户的自由,并且尊重整个社区。粗略来讲,一个软件如果是自由软件,这意味着<b>用户可以自由地运行,拷贝,分发,学ä¹
 ï¼Œä¿®æ”¹å¹¶æ”¹è¿›è¯¥è½¯ä»¶</b>。因此,&ldquo;自由软件&rdquo;是å…
³ä¹Žè‡ªç”±çš„问题,与价格无å…
³ï¼Œè½¯ä»¶å¦‚何定价并不影响它是否被归类为自由软件。英文中,我们使用Free
+Software。由于Free一词既有自由,也有免费的意思。而Free
+Software中的Free是指&ldquo;自由言论&rdquo;中的自由,而非&ldquo;å
…è´¹&rdquo;这一意项。为避å…
æ­§ä¹‰ï¼Œåœ¨ä½¿ç”¨è‹±æ–‡æ—¶ï¼Œæˆ‘们也会借用法语或西班牙语的&ldquo;Libre
+Software&rdquo;来指自由软件。
 </p>
 
 <p>
-我们支持软件用户的自由,因
为我们坚信这是每个用户应得的。有了这些自由,软件用户,æ—
 
论是个人还是集体,都可以掌控所运行的软件,并决定这些程序如何为自己服务。如果一个软件令用户失去了这种控制权,我们则称它为
-&ldquo; 非自由 &rdquo; 的,或 &ldquo; 专有 &rdquo;
-的程序。与自由软件相反,非自由软件会操控它的用户,而软件的开发è€
…则掌控着软件。 这使得非自由软件成为了<a
+我们支持软件用户的自由,因
为我们坚信这是每个用户应得的。有了这些自由,软件用户,æ—
 
论是个人还是集体,都可以掌控所运行的软件,并决定这些程序如何为自己服务。如果一个软件令用户失去了这种控制权,我们则称它为&ldquo;非自由&rdquo;的,或&ldquo;专有&rdquo;的程序。与自由软件相反,非自由软件会操控它的用户,而软件的开发è€
…则掌控着软件。这使得非自由软件成为了<a
 href="/philosophy/free-software-even-more-important.html"> 
非正义力量的帮凶</a>。
 </p>
 
@@ -67,8 +63,7 @@
 <p>无论在哪种情况下,只有所有用户使用的代ç 
éƒ½æ»¡è¶³äº†è¿™å››é¡¹åŸºæœ¬è‡ªç”±ï¼Œè¯¥ç¨‹åºæ‰èƒ½è¢«è§†ä½œè‡ªç”±è½¯ä»¶ã€‚例如,有两个程序,甲程序运行的时候会自动调用乙程序。发布甲程序意味着用户å¿
…须使用到乙程序,那么必
须甲乙两个程序都是自由的,甲程序才是自由的。如果通过修改甲程序,使å
…¶ä¸å†ä¾èµ–乙程序,那么仅仅
以自由软件的形式发布甲程序即可。</p>
 
 <p>
-&ldquo; 自由软件 &rdquo; 不等于 &ldquo; 非商业软件 &rdquo;
-。一个自由软件必须å…
è®¸å•†ä¸šç”¨æˆ·ï¼Œå•†ä¸šå¼€å‘,和商业发布。商业开发自由软件早就司空见惯了,这æ
 ·çš„自由软件非常重要。你
可能需要花钱购买自由软件的拷贝,也可能å…
è´¹æ‹¿åˆ°ã€‚但是无论你如何获得你的拷贝,作为用户,你
的四大自由都会被保证,你
可以自由地运行,修改,发布甚至<a
+&ldquo;自由软件&rdquo;不等于&ldquo;非商业软件&rdquo;。一个自由软件å¿
…é¡»å…
è®¸å•†ä¸šç”¨æˆ·ï¼Œå•†ä¸šå¼€å‘,和商业发布。商业开发自由软件早就司空见惯了,这æ
 ·çš„自由软件非常重要。你
可能需要花钱购买自由软件的拷贝,也可能å…
è´¹æ‹¿åˆ°ã€‚但是无论你如何获得你的拷贝,作为用户,你
的四大自由都会被保证,你
可以自由地运行,修改,发布甚至<a
 href="/philosophy/selling.html">出售</a>你拿到的自由软件。
 </p>
 
@@ -86,19 +81,16 @@
 <h4>学习和更改程序源代码的自由</h4>
 
 <p>
-自由度1和3(自由地修改软件;自由地发布修改后的软件)意味着用户å¿
…须有权访问程序的源代码。由此,访问源代ç 
æ˜¯æˆä¸ºè‡ªç”±è½¯ä»¶çš„必要条件。混编(Obfuscated)后的
-&ldquo; 源代码 &rdquo; 不能被算作此处讨论的源代码。
+自由度1和3(自由地修改软件;自由地发布修改后的软件)意味着用户å¿
…须有权访问程序的源代码。由此,访问源代ç 
æ˜¯æˆä¸ºè‡ªç”±è½¯ä»¶çš„å¿…
要条件。混编(Obfuscated)后的&ldquo;源代ç 
&rdquo;不能被算作此处讨论的源代码。
 </p>
 
 <p>
-自由度1(自由地运行程序)包
括自由地运行自己修改后的程序以替代原版程序。如果程序是跑在某种设备上,该设备可以运行别人修改的软件但不运行ä½
 ä¿®æ”¹çš„软件
-&mdash; 这个方法叫做 &ldquo;tivoization&rdquo; 或者 
&ldquo;锁死&rdquo;,或者(用其发明者的术语)叫做
-&ldquo;安全启动&rdquo; &mdash; 自由度1将被视为无
法满足。该设备中的程序也将不被视为自由软件,即使它们的源代ç
 æ˜¯è‡ªç”±çš„。
+自由度1(自由地运行程序)包
括自由地运行自己修改后的程序以替代原版程序。如果程序是跑在某种设备上,该设备可以运行别人修改的软件但不运行ä½
 ä¿®æ”¹çš„软件&mdash;这个方法叫做&ldquo;tivoization&rdquo;或者
+&ldquo;锁死&rdquo;,或者(用其发明者的术语)叫做&ldquo;安å…
¨å¯åŠ¨&rdquo;&mdash;自由度1将被视为无
法满足。该设备中的程序也将不被视为自由软件,即使它们的源代ç
 æ˜¯è‡ªç”±çš„。
 </p>
 
 <p>
-倘若要修改某个程序,一种很重要的方法就是从别的程序中拿来现成的函数,或模块来使用。如果某个程序的许可证中禁止ä½
 ä½¿ç”¨å…¶ä»–合理授权的软件的代码来修改该程序
-&mdash; 比如,如果某个程序的许可证要求你只能使用你
拥有版权的代码 &mdash; 
那么这个程序的许可证将不被视为自由软件许可证。
+倘若要修改某个程序,一种很重要的方法就是从别的程序中拿来现成的函数,或模块来使用。如果某个程序的许可证中禁止ä½
 ä½¿ç”¨å…¶ä»–合理授权的软件的代ç 
æ¥ä¿®æ”¹è¯¥ç¨‹åº&mdash;比如,如果某个程序的许可证要求你
只能使用你拥有版权的代ç 
&mdash;那么这个程序的许可证将不被视为自由软件许可证。
 </p>
 
 <p>
@@ -135,8 +127,7 @@
 
在GNU项目中,我们使用copyleft这一规则来保护软件用户的四大自由。我们相信<a
 href="/philosophy/pragmatic.html">Copyleft是更好的选择</a>。然而,<a
 
href="/philosophy/categories.html#Non-CopyleftedFreeSoftware">非copyleft的自由软件</a>也同æ
 ·æ˜¯åˆä¹Žé“义的。参见<a
-href="/philosophy/categories.html">自由软件分类</a>来了解更多关于 
&ldquo; 自由软件 &rdquo; ,
-&ldquo; copyleft软件 &rdquo; 以及其他分类和它们之间的关系。
+href="/philosophy/categories.html">自由软件分类</a>来了解更多å…
³äºŽ&ldquo;自由软件&rdquo;、&ldquo;copyleft软件&rdquo;以及å…
¶ä»–分类和它们之间的关系。
 </p>
 
 <h4>打包和发行的详细规则</h4>
@@ -146,8 +137,7 @@
 </p>
 
 <p>
-同理,自由软件也可以要求用户 &ldquo; 
如果以这种方式发布,那么用户必须也可以从另外某一渠
道获得 &rdquo;
-。比如,某个自由软件可能会要求如果发布了修改版,那么å¿
…须也要给原作者
一份修改后的拷贝。(注意:此处前提是软件必
须发布,用户可以私下修改软件而不发布,这样也就不必
把修改版发给开发者
了。)另外还有一些规则也不会与自由软件原则冲突,比如软件可以要求修改后的版本发布时需要附带相应的原版软件的代ç
 ã€‚
+同理,自由软件也可以要求用户&ldquo;如果以这种方式发布,那么用户å¿
…须也可以从另外某一渠
道获得&rdquo;。比如,某个自由软件可能会要求如果发布了修改版,那么å¿
…须也要给原作者
一份修改后的拷贝。(注意:此处前提是软件必
须发布,用户可以私下修改软件而不发布,这样也就不必
把修改版发给开发者
了。)另外还有一些规则也不会与自由软件原则冲突,比如软件可以要求修改后的版本发布时需要附带相应的原版软件的代ç
 ã€‚
 </p>
 
 <p>
@@ -171,8 +161,7 @@
 </p>
 
 <p>
-自由软件许可证不得要求用户额外遵守哪些非自由软件的许可证。例如,自由软件许可证不得要求用户å¿
…须遵守 &ldquo; 所有使用的软件的许可证
-&rdquo; 。因为用户可能使用非自由软件,而要求用户遵守å…
¨éƒ¨ä½¿ç”¨çš„软件的许可证则意味着需要遵守非自由软件许可证,这要的要求将被视作非自由的。
+自由软件许可证不得要求用户额外遵守哪些非自由软件的许可证。例如,自由软件许可证不得要求用户å¿
…须遵守&ldquo;所有使用的软件的许可证&rdquo;。因
为用户可能使用非自由软件,而要求用户遵守å…
¨éƒ¨ä½¿ç”¨çš„软件的许可证则意味着需要遵守非自由软件许可证,这要的要求将被视作非自由的。
 </p>
 
 <p>
@@ -192,12 +181,9 @@
 <h4>在谈论自由软件时使用正确的词汇</h4>
 
 <p>
-在讨论自由软件的时候,尽量避免使用 &ldquo; 赠送 &rdquo; 或 
&ldquo; 免费 &rdquo;
-一类的词汇。因为这会让人们联想到价æ 
¼ï¼Œè€Œéžè‡ªç”±ã€‚一些常见的词汇,例如 &ldquo; 盗版 &rdquo;
-,其中包含了或褒或贬的感情色彩,而这些感情
体现的价值观并不被我们接受。参见<a
+在讨论自由软件的时候,尽量避免使用&ldquo;赠
送&rdquo;或&ldquo;免费&rdquo;一类的词汇。因
为这会让人们联想到价æ 
¼ï¼Œè€Œéžè‡ªç”±ã€‚一些常见的词汇,例如&ldquo;盗版&rdquo;,å…
¶ä¸­åŒ…含了或褒或贬的感情色彩,而这些感情
体现的价值观并不被我们接受。参见<a
 
href="/philosophy/words-to-avoid.html">歧义词汇列表</a>,里面列举了我们不推荐使用的词汇以及相å
…³çš„讨论。我们还有一个<a
-href="/philosophy/fs-translations.html">列表</a>,包含了 &ldquo; 
自由软件 &rdquo;
-一词在不同语言中的推荐翻译。
+href="/philosophy/fs-translations.html">列表</a>,包
含了&ldquo;自由软件&rdquo;一词在不同语言中的推荐翻译。
 </p>
 
 <h4>我们如何诠释这些标准</h4>
@@ -242,9 +228,7 @@
 <h3 id="open-source">开源?</h3>
 
 <p>
-现在还有另外一伙人,使用 &ldquo; 开源 &rdquo; 一词来表达与 
&ldquo; 自由软件 &rdquo;
-类似,但不完全相同的概念。我们更倾向于使用 &ldquo; 
自由软件 &rdquo; 这个词。因为一旦你
看到自由二字,就明白了它所要表达的意思。而
-&ldquo; 开放 &rdquo; <a
+现在还有另外一伙人,使用&ldquo;开源&rdquo;一词来表达与&ldquo;自由软件&rdquo;类似,但不完å
…
¨ç›¸åŒçš„概念。我们更倾向于使用&ldquo;自由软件&rdquo;这个词。å›
 ä¸ºä¸€æ—¦ä½ 
看到自由二字,就明白了它所要表达的意思。而&ldquo;开放&rdquo;<a
 
href="/philosophy/open-source-misses-the-point.html">却并不意味着自由</a>。
 </p>
 
@@ -327,7 +311,7 @@
 
 <li><a
 
href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.56&amp;r2=1.57";>Version
-1.57</a>:加入 &quot; 软件之外 &quot; 一节。</li>
+1.57</a>:加入&quot;软件之外&quot;一节。</li>
 
 <li><a
 
href="http://web.cvs.savannah.gnu.org/viewvc/www/philosophy/free-sw.html?root=www&amp;r1=1.45&amp;r2=1.46";>Version
@@ -378,9 +362,9 @@
 <div id="footer">
 <div class="unprintable">
 
-<p>请将有关自由软件基金会与 GNU 的查询与问题发送到<a
-href="mailto:address@hidden";>&lt;address@hidden&gt;</a>。您也可以通过 <a
-href="/contact/">其它方法</a> 联系自由软件基金会。坏链接和å…
¶ä»–意见或建议请发送到<a
+<p>请将有关自由软件基金会与GNU的一般性问题发送到<a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>。您也可以通过<a
+href="/contact/">其它方法</a>联系自由软件基金会。坏链接和å…
¶ä»–意见或建议请发送到<a
 href="mailto:address@hidden";>&lt;address@hidden&gt;</a>。</p>
 
 <p>
@@ -417,12 +401,12 @@
      
      There is more detail about copyright years in the GNU Maintainers
      Information document, www.gnu.org/prep/maintain. -->
-<p>Copyright &copy; 1996, 2002, 2004-2007, 2009-2017 Free Software Foundation,
+<p>Copyright &copy; 1996, 2002, 2004-2007, 2009-2018 Free Software Foundation,
 Inc.</p>
 
-<p>本页面采用 <a rel="license"
+<p>本页面采用<a rel="license"
 href="http://creativecommons.org/licenses/by-nd/4.0/";>Creative Commons
-Attribution-NoDerivatives 4.0 International License</a> 授权。</p>
+Attribution-NoDerivatives 4.0 International License</a>授权。</p>
 
 <!--#include virtual="/server/bottom-notes.zh-cn.html" -->
 <div class="translators-credits">
@@ -431,12 +415,12 @@
 <b>翻译</b>:邓楠<a
 href="mailto:address@hidden";>&lt;address@hidden&gt;</a>,2015。<br></br>
 <b>翻译团队</b>:<a rel="team"
-href="https://savannah.gnu.org/projects/www-zh-cn/";>&lt;CTT&gt;</a>,2017。</div>
+href="https://savannah.gnu.org/projects/www-zh-cn/";>&lt;CTT&gt;</a>,2017,2018。</div>
 
 <p class="unprintable"><!-- timestamp start -->
 最后更新:
 
-$Date: 2017/12/31 08:24:44 $
+$Date: 2018/01/02 13:31:27 $
 
 <!-- timestamp end -->
 </p>

Index: philosophy/po/free-sw.zh-cn-en.html
===================================================================
RCS file: /web/www/www/philosophy/po/free-sw.zh-cn-en.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- philosophy/po/free-sw.zh-cn-en.html 31 Dec 2017 08:24:48 -0000      1.3
+++ philosophy/po/free-sw.zh-cn-en.html 2 Jan 2018 13:31:27 -0000       1.4
@@ -593,7 +593,7 @@
      There is more detail about copyright years in the GNU Maintainers
      Information document, www.gnu.org/prep/maintain. -->
 
-<p>Copyright &copy; 1996, 2002, 2004-2007, 2009-2017
+<p>Copyright &copy; 1996, 2002, 2004-2007, 2009-2018
 Free Software Foundation, Inc.</p>
 
 <p>This page is licensed under a <a rel="license"
@@ -604,7 +604,7 @@
 
 <p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2017/12/31 08:24:48 $
+$Date: 2018/01/02 13:31:27 $
 <!-- timestamp end -->
 </p>
 </div>

Index: philosophy/po/free-sw.zh-cn.po
===================================================================
RCS file: /web/www/www/philosophy/po/free-sw.zh-cn.po,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -b -r1.23 -r1.24
--- philosophy/po/free-sw.zh-cn.po      2 Jan 2018 13:07:49 -0000       1.23
+++ philosophy/po/free-sw.zh-cn.po      2 Jan 2018 13:31:27 -0000       1.24
@@ -15,7 +15,6 @@
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"X-Outdated-Since: 2018-01-01 05:58+0000\n"
 "X-Generator: Poedit 1.7.5\n"
 
 #. type: Content of: <title>

Index: licenses/po/fdl-howto-opt.zh-cn-en.html
===================================================================
RCS file: licenses/po/fdl-howto-opt.zh-cn-en.html
diff -N licenses/po/fdl-howto-opt.zh-cn-en.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ licenses/po/fdl-howto-opt.zh-cn-en.html     2 Jan 2018 13:31:27 -0000       
1.1
@@ -0,0 +1,193 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.79 -->
+<title>How to Use the Optional Features of the GFDL
+- GNU Project - Free Software Foundation</title>
+<!--#include virtual="/licenses/po/fdl-howto-opt.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>How to Use the Optional Features of the GFDL</h2>
+
+<p>by <a href="http://www.stallman.org/";>Richard Stallman</a></p>
+
+<p>
+The <a href="/licenses/fdl.html">GNU FDL</a> (GNU Free Documentation License)
+includes two optional features,
+<a href="#SEC1"><strong>invariant sections</strong></a>
+and
+<a href="#SEC2"><strong>cover texts</strong></a>,
+which you can use if you wish.  The manual's license
+notice should say whether you are using these features.</p>
+
+<p>
+The simplest case is that you do not use these features.  Then
+the license notice should say so, like this:</p>
+
+<pre>
+      Permission is granted to copy, distribute and/or modify this
+      document under the terms of the GNU Free Documentation License,
+      Version 1.3 or any later version published by the Free Software
+      Foundation; with no Invariant Sections, no Front-Cover Texts, and
+      no Back-Cover Texts.  A copy of the license is included in the
+      section entitled "GNU Free Documentation License".
+</pre>
+<p>
+But if you want to use these features, here is an explanation of
+what they are intended for and how to use them.</p>
+
+<h3 id="SEC1">Invariant sections</h3>
+<p>
+The idea of invariant sections is that they give you a way to express
+nontechnical personal opinions about the topic.</p>
+<p>
+The classical example of an invariant nontechnical section in a free
+manual is the <a href="/gnu/manifesto.html">GNU Manifesto</a>, which
+is included in the GNU Emacs Manual.  The GNU Manifesto says nothing
+about how to edit with Emacs, but it explains the reason why I wrote
+GNU Emacs&mdash;to be an essential part of the GNU operating system,
+which would give computer users freedom to cooperate in a community.
+Since the GNU Manifesto presents the principles of the GNU Project,
+rather than features of GNU Emacs, we decided that others should not
+remove or change it when redistributing the Emacs Manual, and we wrote
+that requirement into the license.  In effect, we made the GNU
+Manifesto into an invariant section, though without using that term.
+To do this today using the GNU FDL, we would write the license notice
+like this:</p>
+
+<pre>
+      Permission is granted to copy, distribute and/or modify this
+      document under the terms of the GNU Free Documentation License,
+      Version 1.3 or any later version published by the Free Software
+      Foundation; with the Invariant Sections being just "GNU
+      Manifesto", with no Front-Cover Texts, and with no Back-Cover
+      Texts.  A copy of the license is included in the section
+      entitled "GNU Free Documentation License".
+</pre>
+<p>
+This says that the section &ldquo;GNU Manifesto&rdquo; is the only
+invariant section.</p>
+<p>
+The old Emacs Manual license did not allow others who modify and
+redistribute the manual to add new invariant sections.  But while
+formulating a more general version of the concept for the GNU FDL, I
+felt that it would be more morally consistent if those who modify a
+manual can write invariant sections, just as the first authors can.
+The FDL permits this.</p>
+<p>
+But that feature requires a safeguard to prevent it from being abused
+to endanger the free status of the manual.  Person B who modifies a
+manual that was written by person A should not be able to make any of
+person A's documentation invariant, for that would deny person C the
+permission to modify it further.  Likewise, if person B adds
+documentation for additional subtopics, this added documentation must
+not be invariant; the documentation itself must be modifiable by
+others.  The FDL's conditions on adding invariant sections provide
+this safeguard.</p>
+<p>
+There is no need for a manual to have any invariant sections.  The
+simplest case is to have none at all.  You do not have to list the GNU
+FDL itself as an invariant section, because the FDL explicitly says
+that the FDL itself may not be changed.  The FDL also distinguishes
+certain section titles, &ldquo;History&rdquo; and
+&ldquo;Dedications&rdquo; and others.  You should not list these
+sections as invariant, because the FDL already gives the rules for
+these sections.</p>
+
+<h3 id="SEC2">Cover texts</h3>
+<p>
+A cover text is a short piece of text that you insist must be printed
+on the cover of the manual when the manual is published, even if
+someone else is publishing it.  You can specify a &ldquo;front-cover
+text&rdquo; which has to be printed on the front cover, and you can
+specify a &ldquo;back-cover text&rdquo; which has to be printed on the
+back cover.  You can specify one of each.</p>
+<p>
+Cover texts are a new feature, so I cannot cite past examples of their
+use, but the intended purpose is simple.  They are meant to give the
+original publisher of an edition a way to ask or encourage people to
+buy the copies they publish rather than those of some other reprinter.
+For example, we could imagine specifying this as a back-cover text:</p>
+
+<pre>
+    Free Manuals Inc. paid Alyssa P. Hacker to write this manual
+    and asks for your support through buying the Free Manuals edition.
+</pre>
+<p>
+This might help Free Manuals Inc. succeed in the business of
+publishing free manuals&mdash;at least, that is the plan.  To specify
+this back-cover text, Free Manuals Inc. would write the license notice
+like this:</p>
+
+<pre>
+      Permission is granted to copy, distribute and/or modify this
+      document under the terms of the GNU Free Documentation License,
+      Version 1.3 or any later version published by the Free Software
+      Foundation; with no Invariant Sections, no Front-Cover Texts, and
+      one Back-Cover Text: "Free Manuals Inc. paid Alyssa P. Hacker to
+      write this manual and asks for your support through buying the
+      Free Manuals edition."  A copy of the license is included in the
+      section entitled "GNU Free Documentation License".
+</pre>
+
+</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; 2000, 2008, 2014, 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/01/02 13:31:27 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>



reply via email to

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