Synced with english version

1 files changed, 551 insertions, 33 deletions

diff --git a/faq/es/sylpheed-faq.sgml b/faq/es/sylpheed-faq.sgml
index fec12b7..66fe41b 100644
--- a/faq/es/sylpheed-faq.sgml
+++ b/faq/es/sylpheed-faq.sgml
@@ -9,11 +9,30 @@ Ricardo Mones Lastra <tt>&lt;mones@aic.uniovi.es&gt;</tt>
 </author>
 
 <abstract>
-  Preguntas más frecuentes (FAQ) de Sylpheed para la versión 0.7.4 - 
+  Preguntas más frecuentes (FAQ) de Sylpheed para la versión 0.8.0 - 
   basado en el documento original en inglés de Paul Kater (paul@nlpagan.net)
-  y Jens Oberender (j.obi@troja.net)
+  y Jens Oberender (j.obi@troja.net).
+  Mantenido por François Barrière (barriere.francois@libertysurf.fr).
 </abstract>
 
+<toc>
+
+<p>
+Copyright (c) 2002 Ricardo Mones Lastra.
+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, with no Front-Cover Texts, and no Back-Cover Texts.
+A copy of the license is included in the section entitled "GNU Free 
+Documentation License".
+</p>
+<p>
+N. del T.: se incluye la versión original en inglés ya que a efectos legales
+es la única válida. Si desea una versión traducida, pero no oficial, puede
+visitar <url url="http://www.geocities.com/larteaga/gnu/gfdl.html" 
+name="La licencia de documentación libre GNU">.
+</p>
+
 <!--  General information -->
 <sect>
 Información general
@@ -24,19 +43,18 @@ Información general
 R.: Si, los siguientes enlaces corresponden a distintas traducciones
 disponibles:
 <itemize>
-<item><url url="http://nlpagan.net/sylpheedfaq.htm" name="http://nlpagan.net/sylpheedfaq.htm"> : FAQ original en Inglés, cortesía de Paul Kater, Jens Oberender y otros
-<item><url url="http://www.enseirb.fr/~dinh/sylpheed/sylpheed-FAQ-fr.html" name="http://www.enseirb.fr/~dinh/sylpheed/sylpheed-FAQ-fr.html"> : FAQ de Sylpheed en Francés, cortesía de Dinh V. Hoa
-<item><url url="http://silver.lacmhacarh.gr.jp/sylpheed/sylpheedfaq-ja.htm" name="http://silver.lacmhacarh.gr.jp/sylpheed/sylpheedfaq-ja.htm"> : FAQ de Sylpheed en Japonés, cortesía de Wakai "SilverRain" Kazunao
-<item><url url="http://beatles.cselt.it/~mau/sylpheed/sylpheedfaq.html" name="http://beatles.cselt.it/~mau/sylpheed/sylpheedfaq.html"> : FAQ de Sylpheed en Italiano, cortesía de Maurizio Codogno
-<item><url url="http://www.synconet.de/privhome/rs/sylpheed_faq.html" name="http://www.synconet.de/privhome/rs/sylpheed_faq.html"> : FAQ de Sylpheed en Alemán (HTML) y <url url="http://www.synconet.de/privhome/rs/sylpheed_faq.txt" name="http://www.synconet.de/privhome/rs/sylpheed_faq.txt"> (solo texto), ambos cortesía de Ralf Schiffers
-<item><url url="http://www.cs.uoi.gr/~csst9910/el_sylfaq.html" name="http://www.cs.uoi.gr/~csst9910/el_sylfaq.html"> : FAQ de Sylpheed en Griego, cortesía de Theofilos Intzoglou
-<item><url url="http://sylpheed.republika.pl" name="http://sylpheed.republika.pl"> : FAQ de Sylpheed en Polaco, cortesía de Przemyslaw Sulek
-<item><url url="http://linux.fisek.com.tr/dfisek/sylpheed-sss.html" name="http://linux.fisek.com.tr/dfisek/sylpheed-sss.html"> : FAQ de Sylpheed en turco, cortesía de Doruk Fisek
-<item><url url="http://hem.passagen.se/webplats/sylpheed-faq-se.html" name="http://hem.passagen.se/webplats/sylpheed-faq-se.html"> : FAQ de Sylpheed en Sueco, cortesía de Mattias Stergren
+<item><url url="http://nlpagan.net/sylpheedfaq.htm" name="http://nlpagan.net/sylpheedfaq.htm"> : FAQ original en Inglés, cortesía de Paul Kater, Jens Oberender y otros.
+<item><url url="http://www.enseirb.fr/~dinh/sylpheed/sylpheed-FAQ-fr.html" name="http://www.enseirb.fr/~dinh/sylpheed/sylpheed-FAQ-fr.html"> : FAQ de Sylpheed en Francés, cortesía de Dinh V. Hoa.
+<item><url url="http://silver.lacmhacarh.gr.jp/sylpheed/sylpheedfaq-ja.htm" name="http://silver.lacmhacarh.gr.jp/sylpheed/sylpheedfaq-ja.htm"> : FAQ de Sylpheed en Japonés, cortesía de Wakai "SilverRain" Kazunao.
+<item><url url="http://beatles.cselt.it/~mau/sylpheed/sylpheedfaq.html" name="http://beatles.cselt.it/~mau/sylpheed/sylpheedfaq.html"> : FAQ de Sylpheed en Italiano, cortesía de Maurizio Codogno.
+<item><url url="http://www.synconet.de/privhome/rs/sylpheed_faq.html" name="http://www.synconet.de/privhome/rs/sylpheed_faq.html"> : FAQ de Sylpheed en Alemán (HTML) y <url url="http://www.synconet.de/privhome/rs/sylpheed_faq.txt" name="http://www.synconet.de/privhome/rs/sylpheed_faq.txt"> (solo texto), ambos cortesía de Ralf Schiffers.
+<item><url url="http://www.cs.uoi.gr/~csst9910/el_sylfaq.html" name="http://www.cs.uoi.gr/~csst9910/el_sylfaq.html"> : FAQ de Sylpheed en Griego, cortesía de Theofilos Intzoglou.
+<item><url url="http://sylpheed.republika.pl" name="http://sylpheed.republika.pl"> : FAQ de Sylpheed en Polaco, cortesía de Przemyslaw Sulek.
+<item><url url="http://linux.fisek.com.tr/dfisek/sylpheed-sss.html" name="http://linux.fisek.com.tr/dfisek/sylpheed-sss.html"> : FAQ de Sylpheed en turco, cortesía de Doruk Fisek.
+<item><url url="http://hem.passagen.se/webplats/sylpheed-faq-se.html" name="http://hem.passagen.se/webplats/sylpheed-faq-se.html"> : FAQ de Sylpheed en Sueco, cortesía de Mattias Stergren.
+<item><url url="http://sylpheed.goodhorse.idv.tw/faq/sylpheed-faq.html" name="Traditional Chinese FAQ">, cortesía de Franklin.
 </itemize>
-
-También puedes encontrar la última versión en línea de este FAQ en <url url="http://www.aic.uniovi.es/mones/sylpheed/faq-es/" name="http://www.aic.uniovi.es/mones/sylpheed/faq-es/"> (hay enlaces a diferentes formatos).
-</p>
+Puedes descargar este FAQ desde <url url="http://sylpheeddoc.sf.net" name="http://sylpheeddoc.sf.net"> y también desde <url url="http://www.aic.uniovi.es/mones/sylpheed/faq-es/" name="http://www.aic.uniovi.es/mones/sylpheed/faq-es/">.
 </sect1>
 
 <!-- gi.Q02 -->
@@ -162,14 +180,14 @@ Página de Parches de Sylpheed (ver más adelante en este mismo documento).
 <sect1>
 ¿Tiene Sylpheed autocompletado de nombres en los campos de dirección?
 <p>
-R.: Si. Cuando busque un nombre que empieze por ``don'', teclee
-``don'' (sin las comillas) y pulse el tabulador. Esto le    
+R.: Si. Cuando busque un nombre que empieze por ``<tt>don</tt>'', teclee
+``<tt>don</tt>'' (sin las comillas) y pulse el tabulador. Esto le    
 mostrará el nombre correcto si solamente existe un ``don''
 en su libro de direcciones, si no aparecerá una lista
 desplegable que le permitirá seleccionar el nombre   
 deseado, p.ej. Donald Duck, Don Jonhson, pero también las
-direcciones de correo que empiecen por ``don'' aparecerán en
-la lista, como ``don.giovanni@maffia.org''.
+direcciones de correo que empiecen por ``<tt>don</tt>'' aparecerán en
+la lista, como ``<tt>don.giovanni@maffia.org</tt>''.
 </p>
 </sect1>
 
@@ -235,7 +253,7 @@ se moverá a una nueva, dejando una o dos palabras de la anterior
 ``colgando'' solas. Por ejemplo:
 
 <tt>
-<p>     Esta es una línea larga</p>
+<p>     Esta es una línea larga que</p>
 <p>     es partida.</p>
 </tt>
 
@@ -249,6 +267,9 @@ Si ahora se añade una palabra en la primera línea:
                 
 Esto provocaría un monton de trabajo manual para reformatear 
 y dejar presentable el correo de nuevo.
+<p>
+Nota: a partir de Sylpheed 0.8.0 se ha implementado el recorte activo. Puede activarlo en Preferencias comunes-&gt;Componer-&gt;Recortar al escribir.
+</p>
 </sect1>
 
 <!-- gi.Q22 -->
@@ -285,6 +306,7 @@ R.: Si! Al actualizar a
 <item> 0.4.50: deberías reconfigurar las preferencias de los grupos de noticias.
 <item> 0.4.63: deberías establecer los colores para las URL en el menú de configuración.
 <item> 0.4.65: algunos elementos de menú han sido reubicados.
+<item> 0.7.3: muchas asociaciones de teclado han cambiado.
 </itemize>
 </p>
 </sect1>
@@ -348,6 +370,13 @@ a cualquier otro que desee mientras sea un nombre de directorio válido.
 </sect1>
      
 <!-- ic.Q03 -->
+<sect1>¿Por qué ha fallado la creación del buzón?
+<p>
+R.: Sylpheed informa de este error si no puede crear los buzones por defecto (entrada, salida, etc.). Esto puede ser debido a que el &lt;directorioinicial&gt;/Mail ya contenga ficheros con los mismos nombres. Esto ocurre al cambiar de Kmail a Sylpheed, en ese caso haga copia de seguridad de él y elimine el directorio Mail o utilize otro nombre para el directorio de correo de Sylpheed.
+</p>
+</sect1>
+     
+<!-- ic.Q04 -->
 <sect1>¿Cómo configuro una cuenta?
 <p>
 R.: Después de cargar Sylpheed la primera vez se puede añadir una cuenta de correo
@@ -357,14 +386,14 @@ y rellenando los campos del cuadro de diálogo con los valores adecuados.
 </p>
 </sect1>
 
-<!-- ic.Q04 -->
+<!-- ic.Q05 -->
 <sect1>¿Cuántas cuentas puedo configurar en Sylpheed?
 <p>
 R.: El número es ilimitado. El límite se alcanza cuando su ordenador deje de responder.
 </p>
 </sect1>
 
-<!-- ic.Q05 -->
+<!-- ic.Q06 -->
 <sect1>¿Por qué Sylpheed no borra mis correos cuando pulso ``Borrar``? ¿O cuando establezco
 un filtro y Sylpheed no filtra? ¿O muevo correo a una carpeta diferente y no se mueve?
 <p>
@@ -374,7 +403,7 @@ R.: Tienes que pulsar el botón ``Ejecutar``. Otra solución consiste en marcar la
 </p>
 </sect1>
 
-<!-- ic.Q06 -->
+<!-- ic.Q07 -->
 <sect1>¿Puedo establecer direcciones o puertos especiales para mi servidor de correo/noticias?
 <p>
 R.: Si, puede. En la configuración de cada cuenta se pueden especificar los puertos concretos
@@ -383,7 +412,7 @@ que desee utilizar.
 </sect1>
 
 
-<!-- ic.Q07 -->
+<!-- ic.Q08 -->
 <sect1>¿Tiene Sylpheed opciones para separar en hilos los mensajes?
 <p>
 R.: Si. Se puede activar o desactivar en el menú ``Resumen`` seleccionando 
@@ -391,14 +420,14 @@ R.: Si. Se puede activar o desactivar en el menú ``Resumen`` seleccionando
 </p>
 </sect1>
 
-<!-- ic.Q08 -->
+<!-- ic.Q09 -->
 <sect1>¿Puedo crear varios niveles de subcarpetas para almacenar el correo?
 <p>
 R.: Si, no hay ningún problema.
 </p>
 </sect1>
 
-<!-- ic.Q09 -->
+<!-- ic.Q10 -->
 <sect1>¿Por qué no esta Sylpheed enviando mis correos?
 <p>
 R.: Necesita crear al menos una cuenta para poder enviar correo.
@@ -406,7 +435,7 @@ R.: Necesita crear al menos una cuenta para poder enviar correo.
 </p>
 </sect1>
 
-<!-- ic.Q10 -->
+<!-- ic.Q11 -->
 <sect1>¿Cómo aplico un parche después de haberlo descargado? 
 <p>
 R.: Copie el parche al directorio de Sylpheed. Aplíquelo con la orden:
@@ -425,15 +454,15 @@ encuentran en la Página de Parches de Sylpheed).
 </p>
 </sect1>
 
-<!-- ic.Q11 -->
-<sect1>¿Cómo puedo compilar el soporte para los dibujos compface?
+<!-- ic.Q12 -->
+<sect1>¿Cómo puedo compilar el soporte para las imágenes compface?
 <p>
 R.: Deberá tener instalado el paquete en el que esté incluido <tt>libcompface</tt>
 (normalmente denominado <tt>faces</tt>), de manera que esté disponible para compilar con Sylpheed.
 </p>
 </sect1>
 
-<!-- ic.Q12 -->
+<!-- ic.Q13 -->
 <sect1>¿Cómo puedo crear mi propia imagen compface?
 <p>
 R.: Dentro del paquete <tt>faces</tt> existe el programa <tt>xmb2icon</tt> (un guión de shell)
@@ -444,7 +473,7 @@ Gracias a Jeff Daikiri está disponible un curso completo en línea sobre esto, vi
 </p>
 </sect1>
 
-<!-- ic.Q13 -->
+<!-- ic.Q14 -->
 <sect1>¿Cómo le puedo indicar a mi navegador, cliente de noticias u otro programa que
 utilize Sylpheed como cliente de correo?
 <p>
@@ -452,7 +481,7 @@ R.: En la sección de configuración del programa correspondiente escriba:
       <tt> sylpheed --compose</tt>
 </p>
 
-<!-- ic.Q14 -->
+<!-- ic.Q15 -->
 <sect1>¿Cómo puedo habilitar el soporte de GPG en Sylpheed?
 <p>
 R.: Cuando compile Sylpheed asegúrese de añadir la opción <tt>--enable-gpgme</tt> al
@@ -461,14 +490,14 @@ Cuando la compilación termine correctamente aparecerá en el diálogo de Preferenc
 </p>
 </sect1>
 
-<!-- ic.Q15 -->
+<!-- ic.Q16 -->
 <sect1>Mutt no reconoce la estructura de carpetas MH de Sylpheed
 <p>
 R.:  Deberá hacer <tt>touch .xmhcache</tt> en todas y cada una de las cada carpetas MH, y Mutt funcionará correctamente.
 </p>
 </sect1>
 
-<!-- ic.Q16 -->
+<!-- ic.Q17 -->
 <sect1>Sylpheed provoca una violación de segmento cuando veo un fichero GIF
 <p>
 R.: Si sucede esto se puede solucionar fácilmente añadiendo lo siguiente al
@@ -477,6 +506,31 @@ fichero /etc/mime.types :
 </p>
 </sect1>
 
+<!-- ic.Q18 -->
+<sect1>¿Cómo puedo hacer que Sylpheed me avise cuando llega correo nuevo?
+<p>
+R.: Tienes varias posibilidades para esto:<p>
+* Buscar en la página de parches de Sylpheed en <url url="http://www.thewildbeast.co.uk/sylpheed/" name="http://www.thewildbeast.co.uk/sylpheed/"> un parche para notificación de correo nuevo.<p>
+* Descargarte Gkrellm o algún programa similar que sea capaz de notificar la llegada de correo nuevo. Gkrellm esta disponible en <url url="http://www.gkrellm.net" name="la página de Gkrellm">.
+</p>
+</sect1>
+
+<!-- ic.Q19 -->
+<sect1>¿Puedo utilizar un corrector ortográfico con Sylpheed?
+<p>
+R.: Si, puede utilizar <tt>ispell</tt> para ello. En Preferencias comunes, en el lugar donde se puede definir un editor externo (siempre y cuando no haga uso de esta opción, por supuesto) puede teclear "xterm -e ispell %s", sin las comillas. Con esta configuración puede comprobar la corrección ortográfica al escribir un correo pulsando el botón "Editor" en la ventana de composición.</p>
+<p>
+Nota: puede utilizar el tipo de xterm que prefiera, así pues wterm, eterm y aterm deberían funcionar también, siempre que esten instaladas en el sistema.
+</p>
+</sect1>
+
+<!-- ic.Q20 -->
+<sect1>¿Cómo puedo hacer que Sylpheed envie mi imagen compface en los correos?
+<p>
+R.: En el menú Configuración, Preferencias de la cuenta actual, pestaña Enviar, marque la casilla "Añadir cabecera de usuario" y pulse el botón "Editar". Aparecerá un diálogo, añada una cabecera con nombre "X-Face" y rellene el campo valor con los datos de la imagen compface. Nota: Si pega los datos desde una terminal en el campo pueden añadirse retornos de carro espúreos, y estos pueden corromper la imagen, tenga cuidado.
+</p>
+</sect1>
+
 </sect>
 
 <!--  Interface -->
@@ -628,4 +682,468 @@ Por ejemplo: <tt>gedit '%s'</tt>
 
 </sect>
 
+<appendix>
+
+<!-- - GNU Project - Free Software Foundation (FSF) -->
+<!-- LINK REV="made" HREF="mailto:webmasters@gnu.org" -->
+
+
+  <sect>
+    GNU Free Documentation License
+
+    <p>Version 1.1, March 2000</p>
+
+    <p>Copyright (C) 2000  Free Software Foundation, Inc.
+       59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
+       Everyone is permitted to copy and distribute verbatim copies
+       of this license document, but changing it is not allowed.
+    </p>
+
+  <sect1>
+    PREAMBLE
+
+    <p>The purpose of this License is to make a manual, textbook,
+    or other written document "free" in the sense of freedom: to
+    assure everyone the effective freedom to copy and redistribute it,
+    with or without modifying it, either commercially or
+    noncommercially.  Secondarily, this License preserves for the
+    author and publisher a way to get credit for their work, while not
+    being considered responsible for modifications made by
+    others.</p>
+
+    <p>This License is a kind of "copyleft", which means that
+    derivative works of the document must themselves be free in the
+    same sense.  It complements the GNU General Public License, which
+    is a copyleft license designed for free software.</p>
+
+    <p>We have designed this License in order to use it for manuals
+    for free software, because free software needs free documentation:
+    a free program should come with manuals providing the same
+    freedoms that the software does.  But this License is not limited
+    to software manuals; it can be used for any textual work,
+    regardless of subject matter or whether it is published as a
+    printed book.  We recommend this License principally for works
+    whose purpose is instruction or reference.</p>
+  </sect1>
+
+  <sect1>
+    APPLICABILITY AND DEFINITIONS
+
+    <p>This License applies to any manual or other work that
+    contains a notice placed by the copyright holder saying it can be
+    distributed under the terms of this License.  The "Document",
+    below, refers to any such manual or work.  Any member of the
+    public is a licensee, and is addressed as "you".</p>
+
+    <p>A "Modified Version" of the Document means any work
+    containing the Document or a portion of it, either copied
+    verbatim, or with modifications and/or translated into another
+    language.</p>
+
+    <p>A "Secondary Section" is a named appendix or a front-matter
+    section of the Document that deals exclusively with the
+    relationship of the publishers or authors of the Document to the
+    Document's overall subject (or to related matters) and contains
+    nothing that could fall directly within that overall subject.
+    (For example, if the Document is in part a textbook of
+    mathematics, a Secondary Section may not explain any mathematics.)
+    The relationship could be a matter of historical connection with
+    the subject or with related matters, or of legal, commercial,
+    philosophical, ethical or political position regarding
+    them.</p>
+
+    <p>The "Invariant Sections" are certain Secondary Sections
+    whose titles are designated, as being those of Invariant Sections,
+    in the notice that says that the Document is released under this
+    License.</p>
+ 
+    <p>The "Cover Texts" are certain short passages of text that
+    are listed, as Front-Cover Texts or Back-Cover Texts, in the
+    notice that says that the Document is released under this
+    License.</p>
+
+    <p>A "Transparent" copy of the Document means a
+    machine-readable copy, represented in a format whose specification
+    is available to the general public, whose contents can be viewed
+    and edited directly and straightforwardly with generic text
+    editors or (for images composed of pixels) generic paint programs
+    or (for drawings) some widely available drawing editor, and that
+    is suitable for input to text formatters or for automatic
+    translation to a variety of formats suitable for input to text
+    formatters.  A copy made in an otherwise Transparent file format
+    whose markup has been designed to thwart or discourage subsequent
+    modification by readers is not Transparent.  A copy that is not
+    "Transparent" is called "Opaque".</p>
+
+    <p>Examples of suitable formats for Transparent copies include
+    plain ASCII without markup, Texinfo input format, LaTeX input
+    format, SGML or XML using a publicly available DTD, and
+    standard-conforming simple HTML designed for human modification.
+    Opaque formats include PostScript, PDF, proprietary formats that
+    can be read and edited only by proprietary word processors, SGML
+    or XML for which the DTD and/or processing tools are not generally
+    available, and the machine-generated HTML produced by some word
+    processors for output purposes only.</p>
+
+    <p>The "Title Page" means, for a printed book, the title page
+    itself, plus such following pages as are needed to hold, legibly,
+    the material this License requires to appear in the title page.
+    For works in formats which do not have any title page as such,
+    "Title Page" means the text near the most prominent appearance of
+    the work's title, preceding the beginning of the body of the
+    text.</p>
+  </sect1>
+
+  <sect1>
+    VERBATIM COPYING
+
+   <p>You may copy and distribute the Document in any medium,
+    either commercially or noncommercially, provided that this
+    License, the copyright notices, and the license notice saying this
+    License applies to the Document are reproduced in all copies, and
+    that you add no other conditions whatsoever to those of this
+    License.  You may not use technical measures to obstruct or
+    control the reading or further copying of the copies you make or
+    distribute.  However, you may accept compensation in exchange for
+    copies.  If you distribute a large enough number of copies you
+    must also follow the conditions in section 3.</p>
+
+    <p>You may also lend copies, under the same conditions stated
+    above, and you may publicly display copies.</p>
+</sect1>
+
+  <sect1>
+    COPYING IN QUANTITY
+
+   <p>If you publish printed copies of the Document numbering more
+    than 100, and the Document's license notice requires Cover Texts,
+    you must enclose the copies in covers that carry, clearly and
+    legibly, all these Cover Texts: Front-Cover Texts on the front
+    cover, and Back-Cover Texts on the back cover.  Both covers must
+    also clearly and legibly identify you as the publisher of these
+    copies.  The front cover must present the full title with all
+    words of the title equally prominent and visible.  You may add
+    other material on the covers in addition.  Copying with changes
+    limited to the covers, as long as they preserve the title of the
+    Document and satisfy these conditions, can be treated as verbatim
+    copying in other respects.</p>
+
+    <p>If the required texts for either cover are too voluminous to
+    fit legibly, you should put the first ones listed (as many as fit
+    reasonably) on the actual cover, and continue the rest onto
+    adjacent pages.</p>
+
+    <p>If you publish or distribute Opaque copies of the Document
+    numbering more than 100, you must either include a
+    machine-readable Transparent copy along with each Opaque copy, or
+    state in or with each Opaque copy a publicly-accessible
+    computer-network location containing a complete Transparent copy
+    of the Document, free of added material, which the general
+    network-using public has access to download anonymously at no
+    charge using public-standard network protocols.  If you use the
+    latter option, you must take reasonably prudent steps, when you
+    begin distribution of Opaque copies in quantity, to ensure that
+    this Transparent copy will remain thus accessible at the stated
+    location until at least one year after the last time you
+    distribute an Opaque copy (directly or through your agents or
+    retailers) of that edition to the public.</p>
+
+    <p>It is requested, but not required, that you contact the
+    authors of the Document well before redistributing any large
+    number of copies, to give them a chance to provide you with an
+    updated version of the Document.</p>
+  </sect1>
+
+  <sect1>
+    MODIFICATIONS
+
+    <p>You may copy and distribute a Modified Version of the
+    Document under the conditions of sections 2 and 3 above, provided
+    that you release the Modified Version under precisely this
+    License, with the Modified Version filling the role of the
+    Document, thus licensing distribution and modification of the
+    Modified Version to whoever possesses a copy of it.  In addition,
+    you must do these things in the Modified Version:</p>
+
+    <p><itemize>
+      <item>Use in the Title Page
+      (and on the covers, if any) a title distinct from that of the
+      Document, and from those of previous versions (which should, if
+      there were any, be listed in the History section of the
+      Document).  You may use the same title as a previous version if
+      the original publisher of that version gives permission.
+      </item>
+
+      <item>List on the Title Page,
+      as authors, one or more persons or entities responsible for
+      authorship of the modifications in the Modified Version,
+      together with at least five of the principal authors of the
+      Document (all of its principal authors, if it has less than
+      five).
+      </item>
+
+      <item>State on the Title page
+      the name of the publisher of the Modified Version, as the
+      publisher.
+      </item>
+
+      <item>Preserve all the
+      copyright notices of the Document.
+      </item>
+
+      <item>Add an appropriate
+      copyright notice for your modifications adjacent to the other
+      copyright notices.
+      </item>
+
+      <item>Include, immediately
+      after the copyright notices, a license notice giving the public
+      permission to use the Modified Version under the terms of this
+      License, in the form shown in the Addendum below.
+      </item>
+
+      <item>Preserve in that license
+      notice the full lists of Invariant Sections and required Cover
+      Texts given in the Document's license notice.
+      </item>
+
+      <item>Include an unaltered
+      copy of this License.
+      </item>
+
+      <item>Preserve the section
+      entitled "History", and its title, and add to it an item stating
+      at least the title, year, new authors, and publisher of the
+      Modified Version as given on the Title Page.  If there is no
+      section entitled "History" in the Document, create one stating
+      the title, year, authors, and publisher of the Document as given
+      on its Title Page, then add an item describing the Modified
+      Version as stated in the previous sentence.
+      </item>
+
+      <item>Preserve the network
+      location, if any, given in the Document for public access to a
+      Transparent copy of the Document, and likewise the network
+      locations given in the Document for previous versions it was
+      based on.  These may be placed in the "History" section.  You
+      may omit a network location for a work that was published at
+      least four years before the Document itself, or if the original
+      publisher of the version it refers to gives permission.
+      </item>
+
+      <item>In any section entitled
+      "Acknowledgements" or "Dedications", preserve the section's
+      title, and preserve in the section all the substance and tone of
+      each of the contributor acknowledgements and/or dedications
+      given therein.
+      </item>
+
+      <item>Preserve all the
+      Invariant Sections of the Document, unaltered in their text and
+      in their titles.  Section numbers or the equivalent are not
+      considered part of the section titles.
+      </item>
+
+      <item>Delete any section
+      entitled "Endorsements".  Such a section may not be included in
+      the Modified Version.
+      </item>
+
+      <item>Do not retitle any
+      existing section as "Endorsements" or to conflict in title with
+      any Invariant Section.
+      </item>
+    </itemize>
+    
+    <p>If the Modified Version includes new front-matter sections
+    or appendices that qualify as Secondary Sections and contain no
+    material copied from the Document, you may at your option
+    designate some or all of these sections as invariant.  To do this,
+    add their titles to the list of Invariant Sections in the Modified
+    Version's license notice.  These titles must be distinct from any
+    other section titles.</p>
+
+    <p>You may add a section entitled "Endorsements", provided it
+    contains nothing but endorsements of your Modified Version by
+    various parties--for example, statements of peer review or that
+    the text has been approved by an organization as the authoritative
+    definition of a standard.</p>
+
+    <p>You may add a passage of up to five words as a Front-Cover
+    Text, and a passage of up to 25 words as a Back-Cover Text, to the
+    end of the list of Cover Texts in the Modified Version.  Only one
+    passage of Front-Cover Text and one of Back-Cover Text may be
+    added by (or through arrangements made by) any one entity.  If the
+    Document already includes a cover text for the same cover,
+    previously added by you or by arrangement made by the same entity
+    you are acting on behalf of, you may not add another; but you may
+    replace the old one, on explicit permission from the previous
+    publisher that added the old one.</p>
+
+    <p>The author(s) and publisher(s) of the Document do not by
+    this License give permission to use their names for publicity for
+    or to assert or imply endorsement of any Modified Version.</p>
+  </sect1>
+
+  <sect1>
+    COMBINING DOCUMENTS
+
+    <p>You may combine the Document with other documents released
+    under this License, under the terms defined in section 4 above for
+    modified versions, provided that you include in the combination
+    all of the Invariant Sections of all of the original documents,
+    unmodified, and list them all as Invariant Sections of your
+    combined work in its license notice.</p>
+
+    <p>The combined work need only contain one copy of this
+    License, and multiple identical Invariant Sections may be replaced
+    with a single copy.  If there are multiple Invariant Sections with
+    the same name but different contents, make the title of each such
+    section unique by adding at the end of it, in parentheses, the
+    name of the original author or publisher of that section if known,
+    or else a unique number.  Make the same adjustment to the section
+    titles in the list of Invariant Sections in the license notice of
+    the combined work.</p>
+
+    <p>In the combination, you must combine any sections entitled
+    "History" in the various original documents, forming one section
+    entitled "History"; likewise combine any sections entitled
+    "Acknowledgements", and any sections entitled "Dedications".  You
+    must delete all sections entitled "Endorsements."</p>
+  </sect1>
+
+  <sect1>
+    COLLECTIONS OF DOCUMENTS
+
+    <p>You may make a collection consisting of the Document and
+    other documents released under this License, and replace the
+    individual copies of this License in the various documents with a
+    single copy that is included in the collection, provided that you
+    follow the rules of this License for verbatim copying of each of
+    the documents in all other respects.</p>
+ 
+    <p>You may extract a single document from such a collection,
+    and distribute it individually under this License, provided you
+    insert a copy of this License into the extracted document, and
+    follow this License in all other respects regarding verbatim
+    copying of that document.</p>
+  </sect1>
+
+  <sect1>
+    AGGREGATION WITH INDEPENDENT WORKS
+    
+    <p>A compilation of the Document or its derivatives with other
+    separate and independent documents or works, in or on a volume of
+    a storage or distribution medium, does not as a whole count as a
+    Modified Version of the Document, provided no compilation
+    copyright is claimed for the compilation.  Such a compilation is
+    called an "aggregate", and this License does not apply to the
+    other self-contained works thus compiled with the Document, on
+    account of their being thus compiled, if they are not themselves
+    derivative works of the Document.</p>
+
+    <p>If the Cover Text requirement of section 3 is applicable to
+    these copies of the Document, then if the Document is less than
+    one quarter of the entire aggregate, the Document's Cover Texts
+    may be placed on covers that surround only the Document within the
+    aggregate.  Otherwise they must appear on covers around the whole
+    aggregate.</p>
+  </sect1>
+
+  <sect1>
+    TRANSLATION
+
+    <p>Translation is considered a kind of modification, so you may
+    distribute translations of the Document under the terms of section
+    4.  Replacing Invariant Sections with translations requires
+    special permission from their copyright holders, but you may
+    include translations of some or all Invariant Sections in addition
+    to the original versions of these Invariant Sections.  You may
+    include a translation of this License provided that you also
+    include the original English version of this License.  In case of
+    a disagreement between the translation and the original English
+    version of this License, the original English version will
+    prevail.</p>
+  </sect1>
+
+  <sect1>
+    TERMINATION
+    
+    <p>You may not copy, modify, sublicense, or distribute the
+    Document except as expressly provided for under this License.  Any
+    other attempt to copy, modify, sublicense or distribute the
+    Document is void, and will automatically terminate your rights
+    under this License.  However, parties who have received copies, or
+    rights, from you under this License will not have their licenses
+    terminated so long as such parties remain in full
+    compliance.</p>
+  </sect1>
+
+  <sect1>
+    FUTURE REVISIONS OF THIS LICENSE
+
+    <p>The Free Software Foundation may publish new, revised
+    versions of the GNU Free Documentation License from time to time.
+    Such new versions will be similar in spirit to the present
+    version, but may differ in detail to address new problems or
+    concerns.  See <url url="http://www.gnu.org/copyleft/" name="http://www.gnu.org/copyleft/">.</p>
+ 
+    <p>Each version of the License is given a distinguishing
+    version number.  If the Document specifies that a particular
+    numbered version of this License "or any later version" applies to
+    it, you have the option of following the terms and conditions
+    either of that specified version or of any later version that has
+    been published (not as a draft) by the Free Software Foundation.
+    If the Document does not specify a version number of this License,
+    you may choose any version ever published (not as a draft) by the
+    Free Software Foundation.</p>
+  </sect1>
+
+  <sect1>
+    How to use this License for your documents
+
+    <p>To use this License in a document you have written, include
+    a copy of the License in the document and put the following
+    copyright and license notices just after the title page:</p>
+
+<p><tt>
+      Copyright (c)  YEAR  YOUR NAME.
+      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 LIST THEIR TITLES, with the
+      Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.
+      A copy of the license is included in the section entitled "GNU
+      Free Documentation License".
+</tt></p>
+
+    <p>If you have no Invariant Sections, write "with no Invariant
+    Sections" instead of saying which ones are invariant.  If you have
+    no Front-Cover Texts, write "no Front-Cover Texts" instead of
+    "Front-Cover Texts being LIST"; likewise for Back-Cover
+    Texts.</p>
+
+    <p>If your document contains nontrivial examples of program
+    code, we recommend releasing these examples in parallel under your
+    choice of free software license, such as the GNU General Public
+    License, to permit their use in free software.</p>
+  </sect1>
+
+<!-- Keep this comment at the end of the file
+Local variables:
+mode: sgml
+sgml-omittag:nil
+sgml-shorttag:t
+sgml-minimize-attributes:nil
+sgml-always-quote-attributes:t
+sgml-indent-step:2
+sgml-parent-document: ("referenz.sgml" "appendix")
+sgml-exposed-tags:nil
+sgml-local-ecat-files:nil
+sgml-local-catalogs: CATALOG
+sgml-validate-command: "nsgmls -s referenz.sgml"
+ispell-skip-sgml: t
+End:
+-->
+
 </article>