Fix for bug causing gdmsetup to have performance issues starting up. Fixes

2006-07-17  Brian Cameron  <brian.cameron@sun.com>

        * gui/gdmsetup.c:  Fix for bug causing gdmsetup to have
          performance issues starting up.  Fixes bug #345118.
          Patch by Ray Strode <rstrode@redhat.com>.

4 files changed, 1902 insertions, 322 deletions

diff --git a/docs/es/gdm.xml b/docs/es/gdm.xml
index d8851d48..82597585 100644
--- a/docs/es/gdm.xml
+++ b/docs/es/gdm.xml
@@ -53,7 +53,23 @@
       <year>2003</year><year>2004</year><holder>Sun Microsystems, Inc.</holder>
     </copyright><copyright><year>2003, 2006.</year><holder>Francisco Javier F. Serrador (serrador@openshine.com)</holder></copyright>
 
-    &legal;
+      <legalnotice id="legalnotice">
+	<para>Se concede permiso para copiar, distribuir o modificar este documento según las condiciones de la GNU Free Documentation License (GFDL), Versión 1.1 o cualquier versión posterior publicada por la Free Software Foundation sin Secciones invariantes, Textos de portada y Textos de contraportada. Encontrará una copia de la GFDL en este <ulink type="help" url="ghelp:fdl">enlace</ulink> o en el archivo COPYING-DOCS distribuido con este manual.</para>
+         <para>Este manual forma parte de una colección de documentos de GNOME distribuidos según la GFDL. Si desea distribuir este manual de forma independiente de la colección, puede hacerlo agregando una copia de la licencia al documento, según se describe en la sección 6 de la misma.</para>
+
+	<para>Muchos de los nombres utilizados por las empresas para distinguir sus productos y servicios se consideran marcas comerciales. Cuando estos nombres aparezcan en la documentación de GNOME, y siempre que se haya informado a los miembros del Proyecto de documentación de GNOME de dichas marcas comerciales, los nombres aparecerán en mayúsculas o con las iniciales en mayúsculas.</para>
+
+	<para>ESTE DOCUMENTO Y LAS VERSIONES MODIFICADAS DEL MISMO SE OFRECEN SEGÚN LAS CONDICIONES ESTABLECIDAS EN LA LICENCIA DE DOCUMENTACIÓN LIBRE DE GNU (GFDL) Y TENIENDO EN CUENTA QUE: <orderedlist>
+		<listitem>
+		  <para>EL DOCUMENTO SE ENTREGA "TAL CUAL", SIN GARANTÍA DE NINGÚN TIPO, NI EXPLÍCITA NI IMPLÍCITA INCLUYENDO, SIN LIMITACIÓN, GARANTÍA DE QUE EL DOCUMENTO O VERSIÓN MODIFICADA DE ÉSTE CAREZCA DE DEFECTOS EN EL MOMENTO DE SU VENTA, SEA ADECUADO A UN FIN CONCRETO O INCUMPLA ALGUNA NORMATIVA. TODO EL RIESGO RELATIVO A LA CALIDAD, PRECISIÓN Y UTILIDAD DEL DOCUMENTO O SU VERSIÓN MODIFICADA RECAE EN USTED. SI CUALQUIER DOCUMENTO O VERSIÓN MODIFICADA DE AQUÉL RESULTARA DEFECTUOSO EN CUALQUIER ASPECTO, USTED (Y NO EL REDACTOR INICIAL, AUTOR O AUTOR DE APORTACIONES) ASUMIRÁ LOS COSTES DE TODA REPARACIÓN, MANTENIMIENTO O CORRECCIÓN NECESARIOS. ESTA EXENCIÓN DE RESPONSABILIDAD SOBRE LA GARANTÍA ES UNA PARTE ESENCIAL DE ESTA LICENCIA. NO SE AUTORIZA EL USO DE NINGÚN DOCUMENTO NI VERSIÓN MODIFICADA DE ÉSTE POR EL PRESENTE, SALVO DENTRO DEL CUMPLIMIENTO DE LA EXENCIÓN DE RESPONSABILIDAD;Y</para>
+		</listitem>
+		<listitem>
+		  <para>EN NINGUNA CIRCUNSTANCIA NI BAJO NINGUNA TEORÍA LEGAL, SEA POR ERROR (INCLUYENDO NEGLIGENCIA) CONTRATO O DOCUMENTO DE OTRO TIPO, EL AUTOR, EL ESCRITOR INICIAL, EL AUTOR DE APORTACIONES NI NINGÚN DISTRIBUIDOR DEL DOCUMENTO O VERSIÓN MODIFICADA DEL DOCUMENTO, NI NINGÚN PROVEEDOR DE NINGUNA DE ESAS PARTES, SERÁ RESPONSABLE ANTE NINGUNA PERSONA POR NINGÚN DAÑO DIRECTO, INDIRECTO, ESPECIAL, INCIDENTAL O DERIVADO DE NINGÚN TIPO, INCLUYENDO, SIN LIMITACIÓN DAÑOS POR PÉRDIDA DE FONDO DE COMERCIO, PARO TÉCNICO, FALLO INFORMÁTICO O AVERÍA O CUALQUIER OTRO POSIBLE DAÑO O AVERÍA DERIVADO O RELACIONADO CON EL USO DEL DOCUMENTO O SUS VERSIONES MODIFICADAS, AUNQUE DICHA PARTE HAYA SIDO INFORMADA DE LA POSIBILIDAD DE QUE SE PRODUJESEN ESOS DAÑOS.</para>
+		</listitem>
+	  </orderedlist></para>
+  </legalnotice>
+
+
 
     <releaseinfo>Este manual describe la versión 2.15 del Gestor de entrada de Gnome. Se actualizó por última vez en 12/05/2006.</releaseinfo>  
   </articleinfo>
@@ -102,7 +118,13 @@
 
       <para>Nota: las distribuciones a menudo cambian los valores predeterminados de las claves para soportar su plataforma. Los interfaces de línea de comandos para los programas GDM instalados en <filename>&lt;bin&gt;</filename> y <filename>&lt;sbin&gt;</filename> se consideran estables. Refiérase a su documentación de la distribución para ver si hay cualquier cambio específico de la distribución a estos interfaces de GDM y qué soporte existe para ellos.</para>
 
-      <para>En las series de desarrollo 2.15 los argumentos de un solo guión no están soportados más. Esto incluye el argumento «-no-daemon» usado por <command>gdm</command> y <command>gdm-binary</command>. También incluye los argumentos  "-xdmaddress", "-clientaddress", y "-connectionType" usados por <command>gdmchooser</command>. Estos argumentos se han cambiado para que ahora usen dos guiones. GDM anteriormente soportaba los argumentos de un guión para ser más similar al gestor XDM, pero los argumentos de línea de comandos con un guión se han declarado obsoletos en la pila de GNOME.</para>
+      <para>
+        As of the GDM 2.15 development series, some one-dash arguments are no
+        longer supported.  This includes the "-xdmaddress",
+        "-clientaddress", and "-connectionType" arguments
+        used by <command>gdmchooser</command>.  These arguments have been
+        changed to now use two dashes.
+      </para>
 
       <para>Si se descubrieran problemas que rompiesen la compatibilidad, por favor envíe un error con una prioridad «urgente».</para>
     </sect2>
@@ -3838,7 +3860,12 @@ remote-flexi  - In remote (XDMCP) &amp; flexi mode.
           <varlistentry>
             <term>--nodaemon</term>
             <listitem>
-              <para>Si se especifica esta opción, entonces GDM no se bifurca a un segundo plano cuando se ejecuta. Note que ya no puede usar la opción de un guión simple más que por ejemplo XDM entendería.</para>
+              <para>
+                If this option is specified, then GDM does not fork into the
+                background when run. You can also use a single-dash version,
+                "-nodaemon" for compatibility with other display
+                managers.
+              </para>
             </listitem>
           </varlistentry>
 
diff --git a/docs/es/legal.xml b/docs/es/legal.xml
index 59ab4bf7..04954d24 100644
--- a/docs/es/legal.xml
+++ b/docs/es/legal.xml
@@ -5,5 +5,12 @@
 
 	<para>Muchos de los nombres utilizados por las empresas para distinguir sus productos y servicios se consideran marcas comerciales. Cuando estos nombres aparezcan en la documentación de GNOME, y siempre que se haya informado a los miembros del Proyecto de documentación de GNOME de dichas marcas comerciales, los nombres aparecerán en mayúsculas o con las iniciales en mayúsculas.</para>
 
-	<para>ESTE DOCUMENTO Y LAS VERSIONES MODIFICADAS DEL MISMO SE OFRECEN SEGÚN LAS CONDICIONES ESTABLECIDAS EN LA LICENCIA DE DOCUMENTACIÓN LIBRE DE GNU (GFDL) Y TENIENDO EN CUENTA QUE: <orderedlist><listitem><para>EL DOCUMENTO SE ENTREGA "TAL CUAL", SIN GARANTÍA DE NINGÚN TIPO, NI EXPLÍCITA NI IMPLÍCITA INCLUYENDO, SIN LIMITACIÓN, GARANTÍA DE QUE EL DOCUMENTO O VERSIÓN MODIFICADA DE ÉSTE CAREZCA DE DEFECTOS EN EL MOMENTO DE SU VENTA, SEA ADECUADO A UN FIN CONCRETO O INCUMPLA ALGUNA NORMATIVA. TODO EL RIESGO RELATIVO A LA CALIDAD, PRECISIÓN Y UTILIDAD DEL DOCUMENTO O SU VERSIÓN MODIFICADA RECAE EN USTED. SI CUALQUIER DOCUMENTO O VERSIÓN MODIFICADA DE AQUÉL RESULTARA DEFECTUOSO EN CUALQUIER ASPECTO, USTED (Y NO EL REDACTOR INICIAL, AUTOR O AUTOR DE APORTACIONES) ASUMIRÁ LOS COSTES DE TODA REPARACIÓN, MANTENIMIENTO O CORRECCIÓN NECESARIOS. ESTA EXENCIÓN DE RESPONSABILIDAD SOBRE LA GARANTÍA ES UNA PARTE ESENCIAL DE ESTA LICENCIA. NO SE AUTORIZA EL USO DE NINGÚN DOCUMENTO NI VERSIÓN MODIFICADA DE ÉSTE POR EL PRESENTE, SALVO DENTRO DEL CUMPLIMIENTO DE LA EXENCIÓN DE RESPONSABILIDAD;Y</para></listitem><listitem><para>EN NINGUNA CIRCUNSTANCIA NI BAJO NINGUNA TEORÍA LEGAL, SEA POR ERROR (INCLUYENDO NEGLIGENCIA) CONTRATO O DOCUMENTO DE OTRO TIPO, EL AUTOR, EL ESCRITOR INICIAL, EL AUTOR DE APORTACIONES NI NINGÚN DISTRIBUIDOR DEL DOCUMENTO O VERSIÓN MODIFICADA DEL DOCUMENTO, NI NINGÚN PROVEEDOR DE NINGUNA DE ESAS PARTES, SERÁ RESPONSABLE ANTE NINGUNA PERSONA POR NINGÚN DAÑO DIRECTO, INDIRECTO, ESPECIAL, INCIDENTAL O DERIVADO DE NINGÚN TIPO, INCLUYENDO, SIN LIMITACIÓN DAÑOS POR PÉRDIDA DE FONDO DE COMERCIO, PARO TÉCNICO, FALLO INFORMÁTICO O AVERÍA O CUALQUIER OTRO POSIBLE DAÑO O AVERÍA DERIVADO O RELACIONADO CON EL USO DEL DOCUMENTO O SUS VERSIONES MODIFICADAS, AUNQUE DICHA PARTE HAYA SIDO INFORMADA DE LA POSIBILIDAD DE QUE SE PRODUJESEN ESOS DAÑOS.</para></listitem></orderedlist></para>
+	<para>ESTE DOCUMENTO Y LAS VERSIONES MODIFICADAS DEL MISMO SE OFRECEN SEGÚN LAS CONDICIONES ESTABLECIDAS EN LA LICENCIA DE DOCUMENTACIÓN LIBRE DE GNU (GFDL) Y TENIENDO EN CUENTA QUE: <orderedlist>
+		<listitem>
+		  <para>EL DOCUMENTO SE ENTREGA "TAL CUAL", SIN GARANTÍA DE NINGÚN TIPO, NI EXPLÍCITA NI IMPLÍCITA INCLUYENDO, SIN LIMITACIÓN, GARANTÍA DE QUE EL DOCUMENTO O VERSIÓN MODIFICADA DE ÉSTE CAREZCA DE DEFECTOS EN EL MOMENTO DE SU VENTA, SEA ADECUADO A UN FIN CONCRETO O INCUMPLA ALGUNA NORMATIVA. TODO EL RIESGO RELATIVO A LA CALIDAD, PRECISIÓN Y UTILIDAD DEL DOCUMENTO O SU VERSIÓN MODIFICADA RECAE EN USTED. SI CUALQUIER DOCUMENTO O VERSIÓN MODIFICADA DE AQUÉL RESULTARA DEFECTUOSO EN CUALQUIER ASPECTO, USTED (Y NO EL REDACTOR INICIAL, AUTOR O AUTOR DE APORTACIONES) ASUMIRÁ LOS COSTES DE TODA REPARACIÓN, MANTENIMIENTO O CORRECCIÓN NECESARIOS. ESTA EXENCIÓN DE RESPONSABILIDAD SOBRE LA GARANTÍA ES UNA PARTE ESENCIAL DE ESTA LICENCIA. NO SE AUTORIZA EL USO DE NINGÚN DOCUMENTO NI VERSIÓN MODIFICADA DE ÉSTE POR EL PRESENTE, SALVO DENTRO DEL CUMPLIMIENTO DE LA EXENCIÓN DE RESPONSABILIDAD;Y</para>
+		</listitem>
+		<listitem>
+		  <para>EN NINGUNA CIRCUNSTANCIA NI BAJO NINGUNA TEORÍA LEGAL, SEA POR ERROR (INCLUYENDO NEGLIGENCIA) CONTRATO O DOCUMENTO DE OTRO TIPO, EL AUTOR, EL ESCRITOR INICIAL, EL AUTOR DE APORTACIONES NI NINGÚN DISTRIBUIDOR DEL DOCUMENTO O VERSIÓN MODIFICADA DEL DOCUMENTO, NI NINGÚN PROVEEDOR DE NINGUNA DE ESAS PARTES, SERÁ RESPONSABLE ANTE NINGUNA PERSONA POR NINGÚN DAÑO DIRECTO, INDIRECTO, ESPECIAL, INCIDENTAL O DERIVADO DE NINGÚN TIPO, INCLUYENDO, SIN LIMITACIÓN DAÑOS POR PÉRDIDA DE FONDO DE COMERCIO, PARO TÉCNICO, FALLO INFORMÁTICO O AVERÍA O CUALQUIER OTRO POSIBLE DAÑO O AVERÍA DERIVADO O RELACIONADO CON EL USO DEL DOCUMENTO O SUS VERSIONES MODIFICADAS, AUNQUE DICHA PARTE HAYA SIDO INFORMADA DE LA POSIBILIDAD DE QUE SE PRODUJESEN ESOS DAÑOS.</para>
+		</listitem>
+	  </orderedlist></para>
   </legalnotice>
diff --git a/docs/uk/gdm.xml b/docs/uk/gdm.xml
index 5a26cd9f..d901d765 100644
--- a/docs/uk/gdm.xml
+++ b/docs/uk/gdm.xml
@@ -59,18 +59,31 @@
 
 	<para>Більшість назв, що використовуються компаніями для розповсюдження їх продуктів та послуг є торговими марками. Якщо такі назви зустрічаються у документації з GNOME та учасникам проекту документування GNOME відомо, що вони є торговими марками, тоді ці назви пишуться великими літерами або починаються з великої літери.</para>
 
-	<para>ДОКУМЕНТ ТА ЗМІНЕНІ ВЕРСІЇ ЦЬОГО ДОКУМЕНТУ ПОСТАЧАЮТЬСЯ НА УМОВАХ ВІЛЬНОЇ ЛІЦЕНЗІЇ ДЛЯ ДОКУМЕНТАЦІЇ GNU З ПОДАЛЬШИМ РОЗУМІННЯМ ЩО: <orderedlist><listitem><para>ДОКУМЕНТ НАДАЄТЬСЯ "ЯК Є", БЕЗ БУДЬ-ЯКИХ ГАРАНТІЇ, ЯВНИХ ЧИ НЕЯВНИХ, ВКЛЮЧАЮЧИ, АЛЕ НЕ ОБМЕЖУЮЧИСЬ, ГАРАНТІЙ ЩО ЦЕЙ ДОКУМЕНТ ЧИ ЗМІНЕНА ВЕРСІЯ ДОКУМЕНТА ВІЛЬНІ ВІД ДЕФЕКТІВ, ПРИДАТНІ ДО ПРОДАЖУ, ВІДПОВІДАЮТЬ ПЕВНІЙ МЕТІ АБО НЕ ПОРУШУЮТЬ ЧИЇСЬ ПРАВА. ВЕСЬ РИЗИК ЗА ЯКІСТЬ, ТОЧНІСТЬ, ТА ЧИННІСТЬ ЦЬОГО ДОКУМЕНТУ АБО ЙОГО ЗМІНЕНИХ ВЕРСІЙ ЛЕЖИТЬ НА ВАС.  ЯКЩО БУДЬ-ЯКИЙ ДОКУМЕНТ ЧИ ЗМІНЕНА ВЕРСІЯ БУДУТЬ ВИЗНАНІ ДЕФЕКТНИМИ У БУДЬ-ЯКОМУ ВІДНОШЕННІ, ВИ (НЕ ПОЧАТКОВИЙ УКЛАДАЧ, АВТОР АБО БУДЬ-ЯКИЙ СПІВАВТОР) БЕРЕТЕ НА СЕБЕ ВИТРАТИ ЗА БУДЬ-ЯКЕ НЕОБХІДНЕ ОБСЛУГОВУВАННЯ, РЕМОНТ ЧИ ВИПРАВЛЕННЯ. ЦЯ ВІДМОВА ВІД ГАРАНТІЙ СКЛАДАЄ ВАЖЛИВУ ЧАСТИНУ ЦІЄЇ ЛІЦЕНЗІЇ. НЕ ДОПУСКАЄТЬСЯ ВИКОРИСТАННЯ ЦЬОГО ДОКУМЕНТУ АБО ЙОГО ЗМІНЕНОЇ ВЕРСІЇ БЕЗ ПРИЙНЯТТЯ ЦІЄЇ ВІДМОВИ; ТА</para></listitem><listitem><para>НІ ЗА ЯКИХ ОБСТАВИН ТА ЗА БУДЬ-ЯКОГО ЗАКОНОДАВСТВА, ЧИ ТО ГРОМАДЯНСЬКОЇ ВІДПОВІДАЛЬНОСТІ (ВКЛЮЧАЮЧИ ХАЛАТНІСТЬ), ДОГОВОРУ, ЧИ ЧОГОСЬ ІНШОГО, АВТОР, ПОЧАТКОВИЙ УКЛАДАЧ, БУДЬ-ЯКИЙ СПІВАВТОР, АБО ДИСТРИБ'ЮТОР ДОКУМЕНТУ ЧИ ЗМІНЕНОЇ ВЕРСІЇ ДОКУМЕНТУ, АБО БУДЬ-ЯКИЙ ПОСТАЧАЛЬНИК БУДЬ-ЯКОЇ З ЦИХ СТОРІН, НЕ НЕСЕ ВІДПОВІДАЛЬНІСТЬ ПЕРЕД БУДЬ-ЯКОЮ ОСОБОЮ ЗА БУДЬ-ЯКІ ПРЯМІ, НЕПРЯМІ, ОСОБЛИВІ, ВИПАДКОВІ, АБО ІСТОТНІ ЗБИТКИ БУДЬ-ЯКОГО ХАРАКТЕРУ ВКЛЮЧАЮЧИ, АЛЕ НЕ ОБМЕЖУЮЧИСЬ, ЗБИТКАМИ ВІД ВТРАТИ ПРЕСТИЖУ, ЗУПИНКИ РОБОТИ, ЗБОЇВ АБО НЕСПРАВНОСТЕЙ КОМП'ЮТЕРА, АБО БУДЬ-ЯКІ ІНШІ ЗБИТКИ АБО ВТРАТИ ЩО ВИНИКЛИ БЕЗВІДНОСНО АБО ВНАСЛІДОК ВИКОРИСТАННЯ ЦЬОГО ДОКУМЕНТУ ТА ЗМІНЕНИХ ВЕРСІЙ ЦЬОГО ДОКУМЕНТУ, НАВІТЬ ЯКЩО ЦІ СТОРОНИ, МОЖЛИВО, БУЛИ ПРОІНФОРМОВАНІ ПРО МОЖЛИВІСТЬ ТАКИХ ЗБИТКІВ.</para></listitem></orderedlist></para>
+	<para>ДОКУМЕНТ ТА ЗМІНЕНІ ВЕРСІЇ ЦЬОГО ДОКУМЕНТУ ПОСТАЧАЮТЬСЯ НА УМОВАХ ВІЛЬНОЇ ЛІЦЕНЗІЇ ДЛЯ ДОКУМЕНТАЦІЇ GNU З ПОДАЛЬШИМ РОЗУМІННЯМ ЩО: <orderedlist>
+		<listitem>
+		  <para>ДОКУМЕНТ НАДАЄТЬСЯ "ЯК Є", БЕЗ БУДЬ-ЯКИХ ГАРАНТІЇ, ЯВНИХ ЧИ НЕЯВНИХ, ВКЛЮЧАЮЧИ, АЛЕ НЕ ОБМЕЖУЮЧИСЬ, ГАРАНТІЙ ЩО ЦЕЙ ДОКУМЕНТ ЧИ ЗМІНЕНА ВЕРСІЯ ДОКУМЕНТА ВІЛЬНІ ВІД ДЕФЕКТІВ, ПРИДАТНІ ДО ПРОДАЖУ, ВІДПОВІДАЮТЬ ПЕВНІЙ МЕТІ АБО НЕ ПОРУШУЮТЬ ЧИЇСЬ ПРАВА. ВЕСЬ РИЗИК ЗА ЯКІСТЬ, ТОЧНІСТЬ, ТА ЧИННІСТЬ ЦЬОГО ДОКУМЕНТУ АБО ЙОГО ЗМІНЕНИХ ВЕРСІЙ ЛЕЖИТЬ НА ВАС.  ЯКЩО БУДЬ-ЯКИЙ ДОКУМЕНТ ЧИ ЗМІНЕНА ВЕРСІЯ БУДУТЬ ВИЗНАНІ ДЕФЕКТНИМИ У БУДЬ-ЯКОМУ ВІДНОШЕННІ, ВИ (НЕ ПОЧАТКОВИЙ УКЛАДАЧ, АВТОР АБО БУДЬ-ЯКИЙ СПІВАВТОР) БЕРЕТЕ НА СЕБЕ ВИТРАТИ ЗА БУДЬ-ЯКЕ НЕОБХІДНЕ ОБСЛУГОВУВАННЯ, РЕМОНТ ЧИ ВИПРАВЛЕННЯ. ЦЯ ВІДМОВА ВІД ГАРАНТІЙ СКЛАДАЄ ВАЖЛИВУ ЧАСТИНУ ЦІЄЇ ЛІЦЕНЗІЇ. НЕ ДОПУСКАЄТЬСЯ ВИКОРИСТАННЯ ЦЬОГО ДОКУМЕНТУ АБО ЙОГО ЗМІНЕНОЇ ВЕРСІЇ БЕЗ ПРИЙНЯТТЯ ЦІЄЇ ВІДМОВИ; ТА</para>
+		</listitem>
+		<listitem>
+		  <para>НІ ЗА ЯКИХ ОБСТАВИН ТА ЗА БУДЬ-ЯКОГО ЗАКОНОДАВСТВА, ЧИ ТО ГРОМАДЯНСЬКОЇ ВІДПОВІДАЛЬНОСТІ (ВКЛЮЧАЮЧИ ХАЛАТНІСТЬ), ДОГОВОРУ, ЧИ ЧОГОСЬ ІНШОГО, АВТОР, ПОЧАТКОВИЙ УКЛАДАЧ, БУДЬ-ЯКИЙ СПІВАВТОР, АБО ДИСТРИБ'ЮТОР ДОКУМЕНТУ ЧИ ЗМІНЕНОЇ ВЕРСІЇ ДОКУМЕНТУ, АБО БУДЬ-ЯКИЙ ПОСТАЧАЛЬНИК БУДЬ-ЯКОЇ З ЦИХ СТОРІН, НЕ НЕСЕ ВІДПОВІДАЛЬНІСТЬ ПЕРЕД БУДЬ-ЯКОЮ ОСОБОЮ ЗА БУДЬ-ЯКІ ПРЯМІ, НЕПРЯМІ, ОСОБЛИВІ, ВИПАДКОВІ, АБО ІСТОТНІ ЗБИТКИ БУДЬ-ЯКОГО ХАРАКТЕРУ ВКЛЮЧАЮЧИ, АЛЕ НЕ ОБМЕЖУЮЧИСЬ, ЗБИТКАМИ ВІД ВТРАТИ ПРЕСТИЖУ, ЗУПИНКИ РОБОТИ, ЗБОЇВ АБО НЕСПРАВНОСТЕЙ КОМП'ЮТЕРА, АБО БУДЬ-ЯКІ ІНШІ ЗБИТКИ АБО ВТРАТИ ЩО ВИНИКЛИ БЕЗВІДНОСНО АБО ВНАСЛІДОК ВИКОРИСТАННЯ ЦЬОГО ДОКУМЕНТУ ТА ЗМІНЕНИХ ВЕРСІЙ ЦЬОГО ДОКУМЕНТУ, НАВІТЬ ЯКЩО ЦІ СТОРОНИ, МОЖЛИВО, БУЛИ ПРОІНФОРМОВАНІ ПРО МОЖЛИВІСТЬ ТАКИХ ЗБИТКІВ.</para>
+		</listitem>
+	  </orderedlist></para>
   </legalnotice>
 
 
 
-    <releaseinfo>This manual describes version 2.15.1 of the GNOME Display Manager. It was last updated on 05/12/2006.</releaseinfo>  
+    <releaseinfo>
+       This manual describes version 2.15.1 of the GNOME Display Manager.
+       It was last updated on 05/12/2006.
+    </releaseinfo>  
   </articleinfo>
 
   <sect1 id="preface">
     <title>Терміни та домовленості використані у цьому посібнику</title>
 
-    <para>This manual describes version 2.15.1 of the GNOME Display Manager. It was last updated on 05/12/2006.</para>  
+    <para>
+      This manual describes version 2.15.1 of the GNOME Display Manager.
+      It was last updated on 05/12/2006.
+    </para>  
 
     <para>Селектор - програма, що використовується для керування дисплеєм віддаленого вузла з локального дисплея (<command>gdmchooser</command>).</para>
 
@@ -107,49 +120,182 @@
     <sect2 id="stability">
       <title>Стабільність інтерфейсу</title>
 
-      <para>The key/value pairs defined in the GDM configuration files and the location of these files are considered "stable" interfaces and should only change in ways that are backwards compatible. Note that this includes functionality like the GDM scripts (Init, PreSession, PostSession, PostLogin, XKeepsCrashing, etc.); directory locations (ServAuthDir, PidFile, etc.), system applications (SoundProgram), etc. Some configuration values depend on OS interfaces may need to be modified to work on a given OS. Typical examples are HaltCommand, RebootCommand, SuspendCommand, StandardXServer, Xnest, SoundProgram, and the "command" value for each "server-foo".</para>
-
-      <para>Note: distributions often change the default values of keys to support their platform. Command-line interfaces for GDM programs installed to <filename>&lt;bin&gt;</filename> and <filename>&lt;sbin&gt;</filename> are considered stable. Refer to your distribution documentation to see if there are any distribution-specific changes to these GDM interfaces and what support exists for them.</para>
-
-      <para>As of the GDM 2.15 development series, some one-dash arguments are no longer supported. This includes the "-xdmaddress", "-clientaddress", and "-connectionType" arguments used by <command>gdmchooser</command>. These arguments have been changed to now use two dashes.</para>
-
-      <para>If issues are discovered that break compatibility, please file a bug with an "urgent" priority.</para>
+      <para>
+        The key/value pairs defined in the GDM configuration files and
+        the location of these files are considered "stable" interfaces
+        and should only change in ways that are backwards compatible.  Note that
+        this includes functionality like the GDM scripts (Init, PreSession,
+        PostSession, PostLogin, XKeepsCrashing, etc.); directory locations
+        (ServAuthDir, PidFile, etc.), system applications (SoundProgram), etc.
+        Some configuration values depend on OS interfaces may need to be
+        modified to work on a given OS.  Typical examples are HaltCommand,
+        RebootCommand, SuspendCommand, StandardXServer, Xnest, SoundProgram,
+        and the "command" value for each "server-foo".
+      </para>
+
+      <para>
+        Note: distributions often change the default values of keys to support
+        their platform.  Command-line interfaces for GDM programs installed to
+        <filename>&lt;bin&gt;</filename> and <filename>&lt;sbin&gt;</filename>
+        are considered stable.  Refer to your distribution documentation to see
+        if there are any distribution-specific changes to these GDM interfaces
+        and what support exists for them.
+      </para>
+
+      <para>
+        As of the GDM 2.15 development series, some one-dash arguments are no
+        longer supported.  This includes the "-xdmaddress",
+        "-clientaddress", and "-connectionType" arguments
+        used by <command>gdmchooser</command>.  These arguments have been
+        changed to now use two dashes.
+      </para>
+
+      <para>
+        If issues are discovered that break compatibility, please file a bug
+        with an "urgent" priority.
+      </para>
     </sect2>
 
     <sect2 id="daemonov">
       <title>Сервер GDM</title>
       
-      <para>The GDM daemon is responsible for managing displays on the system. This includes authenticating users, starting the user session, and terminating the user session. GDM is configurable and the ways it can be configured are described in the "Configuring GDM" section of this document. The <filename>Init</filename>, <filename>PostLogin</filename>, <filename>PreSession</filename>, and <filename>PostSession</filename> scripts discussed below are discussed in this "Configuring GDM section".</para>
-
-      <para>The GDM daemon supports a UNIX domain socket protocol which can be used to control aspects of its behavior and to query information. This protocol is described in the "Controlling GDM" section of this document.</para>
-
-      <para>GDM can be asked to manage a display a number of ways. Local displays are always managed when GDM starts and will be restarted when a user's session is finished. Displays can be requested via XDMCP, flexible displays can be requested by running the <command>gdmflexiserver</command> command. Displays that are started on request are not restarted on session exit. GDM also provides the <command>gdmdynamic</command> command to allow easier management of displays on a multi-user server. These display types are discussed further in the next section.</para>
+      <para>
+        The GDM daemon is responsible for managing displays on the system.
+        This includes authenticating users, starting the user session, and
+        terminating the user session.  GDM is configurable and the ways it can
+        be configured are described in the "Configuring GDM" section
+        of this document.  The <filename>Init</filename>,
+        <filename>PostLogin</filename>, <filename>PreSession</filename>, 
+        and <filename>PostSession</filename> scripts discussed below are 
+        discussed in this "Configuring GDM section".
+      </para>
+
+      <para>
+        The GDM daemon supports a UNIX domain socket protocol which can be used
+        to control aspects of its behavior and to query information.  This
+        protocol is described in the "Controlling GDM" section of
+        this document.  
+      </para>
+
+      <para>
+        GDM can be asked to manage a display a number of ways.  Local displays
+        are always managed when GDM starts and will be restarted when a user's
+        session is finished.  Displays can be requested via XDMCP, flexible
+        displays can be requested by running the
+        <command>gdmflexiserver</command> command.  Displays that are started
+        on request are not restarted on session exit.  GDM also provides the
+        <command>gdmdynamic</command> command to allow easier management of
+        displays on a multi-user server.  These display types are discussed
+        further in the next section.  
+      </para>
         
-      <para>When the GDM daemon is asked to manage a display, it will fork an X server process, then run the <filename>Init</filename> script as the root user, and start the login GUI dialog as a slave process on the display. GDM can be configured to use either <command>gdmgreeter</command> (the default) or <command>gdmlogin</command> as the GUI dialog program. The <command>gdmlogin</command> program supports accessibility while the <command>gdmgreeter</command> program supports greater themeability. The GUI dialog is run as the unpriviledged "gdm" user/group which is described in the "Security" section below. The GUI dialog communicates with the daemon via a sockets protocol and via standard input/output. The slave, for example passes the username and password information to the GDM daemon via standard input/output so the daemon can handle the actual authentication.</para>
-
-      <para>The login GUI dialog screen allows the user to select which session they wish to start and which language they wish to use. Sessions are defined by files that end in the .desktop extension and more information about these files can be found in the "Configuration" section. The user enters their name and password and if these successfully authenticate, GDM will start the requested session for the user. It is possible to configure GDM to avoid the authentication process by turning on the Automatic or Timed Login features in the GDM configuration. The login GUI can also be configured to provide additional features to the user, such as the Face Browser; the ability to halt, restart, or suspend the system; and/or edit the login configuration (after entering the root password).</para>
-
-      <para>GDM, by default, will use Pluggable Authentication Modules (PAM) for authentication, but can also support regular crypt and shadow passwords on legacy systems. After authenticating a user, the daemon runs the <filename>PostLogin</filename> script as root, and forks a slave process to start the requested session. This slave process runs the <filename>PreSession</filename> script as root, sets up the users environment, and starts the requested session. GDM keeps track of the user's default session and language in the user's <filename>~/.dmrc</filename> and will use these defaults if the user did not pick a session or language in the login GUI. On Solaris, GDM (since version 2.8.0.3) uses the SDTLOGIN interface after user authentication to tell the X server to be restarted as the user instead of as root for added security. When the users session exits, the GDM daemon will run the <filename>PostSession</filename> script as root.</para>
+      <para>
+        When the GDM daemon is asked to manage a display, it will fork an
+        X server process, then run the <filename>Init</filename> script as the
+        root user, and start the login GUI dialog as a slave process on the
+        display.  GDM can be configured to use either
+        <command>gdmgreeter</command> (the default) or
+        <command>gdmlogin</command> as the GUI dialog program.  The
+        <command>gdmlogin</command> program supports accessibility while the
+        <command>gdmgreeter</command> program supports greater themeability.
+        The GUI dialog is run as the unpriviledged "gdm" user/group
+        which is described in the "Security" section below.  The GUI
+        dialog communicates with the daemon via a sockets protocol and via
+        standard input/output.  The slave, for example passes the username and
+        password information to the GDM daemon via standard input/output so
+        the daemon can handle the actual authentication.
+      </para>
+
+      <para>
+        The login GUI dialog screen allows the user to select which session
+        they wish to start and which language they wish to use.  Sessions are
+        defined by files that end in the .desktop extension and more
+        information about these files can be found in the
+        "Configuration" section.  The user enters their name and
+        password and if these successfully authenticate, GDM will start the
+        requested session for the user.  It is possible to configure GDM to
+        avoid the authentication process by turning on the Automatic or Timed
+        Login features in the GDM configuration.  The login GUI can also be
+        configured to provide additional features to the user, such as the
+        Face Browser; the ability to halt, restart, or suspend the system;
+        and/or edit the login configuration (after entering the root password).
+      </para>
+
+      <para> 
+        GDM, by default, will use Pluggable Authentication Modules (PAM) for
+        authentication, but can also support regular crypt and shadow passwords
+        on legacy systems.  After authenticating a user, the daemon runs the
+        <filename>PostLogin</filename> script as root, and forks a slave
+        process to start the requested session.  This slave process runs the
+        <filename>PreSession</filename> script as root, sets up the users
+        environment, and starts the requested session.  GDM keeps track of the
+        user's default session and language in the user's
+        <filename>~/.dmrc</filename> and will use these defaults if the user
+        did not pick a session or language in the login GUI.  On Solaris, GDM
+        (since version 2.8.0.3) uses the SDTLOGIN interface after user
+        authentication to tell the X server to be restarted as the user instead
+        of as root for added security.  When the users session exits, the GDM
+        daemon will run the <filename>PostSession</filename> script as root.
+      </para>
     </sect2>
 
     <sect2 id="displaytypes">
       <title>Різні типи дисплеїв</title>
 
-      <para>GDM supports three different display types: static (local) displays, flexible (on-demand) displays, and XDMCP (remote) displays. The "X Server Definitions" and the "Local Static X Display Configuration" subsections of the "Configuration" section explains how these various types of displays are defined in the GDM configuration file.</para>
+      <para>
+        GDM supports three different display types: static (local) displays,
+        flexible (on-demand) displays, and XDMCP (remote) displays.  The
+        "X Server Definitions" and the "Local Static X Display
+        Configuration" subsections of the "Configuration"
+        section explains how these various types of displays are defined in
+        the GDM configuration file.
+      </para>
 
       <para>Локальні статичні дисплеї завжди запускаються службою, якщо вони завершуються або вмирають, вони перезапускаються. GDM може запускати їх стільки, скільки буде потрібно. GDM також може керувати серверами, на яких він не керує власне самим процесом входу, це дозволяє використовувати GDM при створенні X-терміналів.</para>
 
-      <para>Flexible, or on demand displays, are started via the socket protocol with the <command>gdmflexiserver</command> command. This feature is only available to users logged in on the console and will display a new login screen. If a flexible display has previously been started on the console, running <command>gdmflexiserver</command> again will display a menu allowing users to switch back to a previous session or start a new flexible session. The <command>gdmflexiserver</command> locks the current session before starting a new flexible display, so the user's password must be entered before returning to an existing session. The <command>gdmflexiserver</command> command can also be used to launch nested <command>Xnest</command> display. These are launched in a window in the user's current session. Nested displays can be started even if not logged into the console and are started by running the <command>gdmflexiserver -n</command> command. Flexible displays are not restarted when the user session ends. Flexible displays require virtual terminal (VT) support in the kernel, and will not be available if not supported (such as on Solaris). Nested displays require that the X server supports Xnest.</para>
+      <para>
+        Flexible, or on demand displays, are started via the socket protocol
+        with the <command>gdmflexiserver</command> command.  This feature is
+        only available to users logged in on the console and will display a new
+        login screen.  If a flexible display has previously been started on
+        the console, running <command>gdmflexiserver</command> again will
+        display a menu allowing users to switch back to a previous session
+        or start a new flexible session.  The <command>gdmflexiserver</command>
+        locks the current session before starting a new flexible display, so
+        the user's password must be entered before returning to an existing
+        session.  The <command>gdmflexiserver</command> command can also be
+        used to launch nested <command>Xnest</command> display.  These are
+        launched in a window in the user's current session.  Nested displays
+        can be started even if not logged into the console and are started by 
+        running the <command>gdmflexiserver -n</command> command.  Flexible
+        displays are not restarted when the user session ends.  Flexible
+        displays require virtual terminal (VT) support in the kernel, and will
+        not be available if not supported (such as on Solaris).  Nested
+        displays require that the X server supports Xnest.
+      </para>
 
       <para>Останній тип дисплеїв - віддалені XDMCP дисплеї, які описані у наступному розділі. Якщо цей параметр увімкнено, віддалені вузли можуть з'єднуватись з GDM та показувати вікно входу. Для цього типу сеансів є відмінності, наприклад, у меню <quote>Дії</quote> не показуються пункти, які дозволяють вимикати, перезавантажувати, або налаштовувати GDM.</para>
 
-      <para>Displays started via the <command>gdmdynamic</command> command are treated as local displays, so they are restarted automatically on when the session exits. This command is intended to more effectively manage the displays on a multi-user server (many displays connected to a single server).</para>
+      <para>
+        Displays started via the <command>gdmdynamic</command> command are
+        treated as local displays, so they are restarted automatically on
+        when the session exits.  This command is intended to more effectively
+        manage the displays on a multi-user server (many displays connected
+        to a single server).
+      </para>
     </sect2>
 
     <sect2 id="xdmcp">
       <title>XDMCP</title>
 
-      <para>The GDM daemon can be configured to listen for and manage X Display Manage Protocol (XDMCP) requests from remote displays. By default XDMCP support is turned off, but can be enabled if desired. If GDM is built with TCP Wrapper support, then the daemon will only grant access to hosts specified in the GDM service section in the TCP Wrappers configuration file.</para>
+      <para>
+        The GDM daemon can be configured to listen for and manage X Display
+        Manage Protocol (XDMCP) requests from remote displays.  By default
+        XDMCP support is turned off, but can be enabled if desired.  If GDM is
+        built with TCP Wrapper support, then the daemon will only grant access
+        to hosts specified in the GDM service section in the TCP Wrappers
+        configuration file.
+      </para>
 
       <para>GDM включає декілька заходів, які роблять його більш стійким до атак типу <quote>відмова у обслуговуванні</quote> на службу XDMCP. Можна налаштувати значну кількість параметрів протоколу, час очікування з'єднання, тощо. Проте, типові значення підійдуть для більшості систем. Не змінюйте їх, якщо не розумієте їх вплив на систему.</para>
 
@@ -157,16 +303,35 @@
 
       <para>GDM можна налаштувати на обробку INDIRECT запитів та відображення селектора вузлів на віддаленому дисплеї. GDM запам'ятовує вибір користувача та пересилає наступні запити вибраному менеджеру. GDM також підтримує розширення до протоколу, яке змушує забути про перенаправлення одразу після успішного з'єднання користувача. Це розширення підтримується якщо з обох сторін сервери GDM. Розширення прозоре і ігнорується XDM та іншими серверами, що підтримують XDMCP.</para>
 
-      <para>Refer to the "Security" section for information about security concerns when using XDMCP.</para>
+      <para>
+        Refer to the "Security" section for information about
+        security concerns when using XDMCP.
+      </para>
     </sect2>
 
     <sect2 id="secureremote">
       <title>Безпечне віддалене з'єднання через SSH</title>
-      <para>As explained in the "Security" section, XDMCP does not use any kind of encryption and as such is inherently insecure. As XDMCP uses UDP as a network transport layer, it is not possible to simply secure it through an SSH tunnel.</para>
-
-      <para>To remedy this problem, gdm can be configured at compilation-time with the option --enable-secureremote, in which case gdm proposes as a built-in session a session called "Secure Remote Connection". Starting such a session allows the user to enter the name or the address of the host on which to connect; provided the said host runs an SSH server, the user then gets connected to the server on which the default X session is started and displayed on the local host.</para>
+      <para>
+        As explained in the "Security" section, XDMCP does not use
+        any kind of encryption and as such is inherently insecure.  As XDMCP
+        uses UDP as a network transport layer, it is not possible to simply
+        secure it through an SSH tunnel.
+      </para>
+
+      <para>
+        To remedy this problem, gdm can be configured at compilation-time with
+        the option --enable-secureremote, in which case gdm proposes as a
+        built-in session a session called "Secure Remote Connection".
+        Starting such a session allows the user to enter the name or the
+        address of the host on which to connect; provided the said host runs an
+        SSH server, the user then gets connected to the server on which the
+        default X session is started and displayed on the local host.
+      </para>
       
-      <para>Using this session allows a much more secure network connection and only necessitates to have an SSH server running on the remote host.</para>
+      <para>
+        Using this session allows a much more secure network connection and
+        only necessitates to have an SSH server running on the remote host.
+      </para>
     </sect2>
 
     <sect2 id="gtkgreeter">
@@ -184,7 +349,15 @@
     <sect2 id="themedgreeter">
       <title>Програма привітання з темами</title>
 
-      <para>The Themed Greeter is a greeter interface that takes up the whole screen and is very themable. Themes can be selected and new themes can be installed by the configuration application or by setting the <filename>GraphicalTheme</filename> configuration key. The Themed Greeter is much like the GTK+ Greeter in that it is controlled by the underlying daemon, is stateless, and is controlled by the daemon using the same simple protocol.</para>
+      <para>
+        The Themed Greeter is a greeter interface that takes up the whole
+        screen and is very themable.  Themes can be selected and new themes
+        can be installed by the configuration application or by setting the
+        <filename>GraphicalTheme</filename> configuration key.  The Themed
+        Greeter is much like the GTK+ Greeter in that it is controlled by
+        the underlying daemon, is stateless, and is controlled by the
+        daemon using the same simple protocol.
+      </para>
 
       <para>Зовнішній вигляд вікна привітання залежить від теми, тому елементи інтерфейсу можуть відрізнятись. Єдиний елемент який завжди присутній - це текстове поле, яке описане у розділі <quote>Програма привітання на GTK+</quote>. Тема вожу включати кнопки вибору локалі/мови, зупинення/перезапуску/призупинення комп'ютера, налаштовування GDM (якщо користувач знає пароль адміністратора (root)), чи запуску селектора XDMCP. </para>
 
@@ -194,19 +367,73 @@
     <sect2 id="facebrowser">
       <title>Переглядач портретів GDM</title>
 
-      <para>GDM supports a face browser which will display a list of users who can login and an icon for each user. This feature can be used with the GTK+ Greeter if the <filename>Browser</filename> configuration option is set to "true". This feature can be used with the Themed Greeter if using a GDM theme which includes a "userlist" item type is defined, such as "happygnome-list"</para>
-
-      <para>By default, the face browser is disabled since revealing usernames on the login screen is not appropriate on many systems for security reasons. Also GDM requires some setup to specify which users should be visible. Setup can be done on the "Users" tab in <command>gdmsetup</command>. This feature is most practical to use on a system with a smaller number of users.</para>
+      <para>
+        GDM supports a face browser which will display a list of users who
+        can login and an icon for each user.  This feature can be used with
+        the GTK+ Greeter if the <filename>Browser</filename> configuration
+        option is set to "true".  This feature can be used with
+        the Themed Greeter if using a GDM theme which includes a
+        "userlist" item type is defined, such as
+        "happygnome-list"
+      </para>
+
+      <para>
+        By default, the face browser is disabled since revealing usernames on
+        the login screen is not appropriate on many systems for security 
+        reasons.  Also GDM requires some setup to specify which users should
+        be visible.  Setup can be done on the "Users" tab in
+        <command>gdmsetup</command>.  This feature is most practical to use
+        on a system with a smaller number of users.
+      </para>
 
       <para>Зображення можуть бути встановлені глобально адміністратором, або братись з домашніх каталогів користувачів. Якщо вони встановлені глобально, вони мають знаходитись у каталозі <filename>&lt;share&gt;/pixmaps/faces/</filename> (шлях до каталогу можна змінити використовуючи конфігураційну змінну <filename>GlobalFaceDir</filename>) та назва файлу повинна відповідати імені користувача, з необов'язковим суфіксом <filename>.png</filename>. Значки програм з глобального каталогу мають бути доступні для читання користувачу GDM. Проте, програма сервера передає зображення програмі привітання та таким права на читання потрібні не не користувачу "gdm", а root.</para>
 
-      <para>Users may run the <command>gdmphotosetup</command> command to configure the image to use for their userid. This program properly scales the file down if it is larger than the <filename>MaxIconWidth</filename> or <filename>MaxIconHeight</filename> configuration options and places the icon in a file called <filename>~/.face</filename>. Although <command>gdmphotosetup</command> scales user images automatically, this does not guarantee that user images are properly scaled since a user may create their <filename>~/.face</filename> file by hand.</para>
+      <para>
+        Users may run the <command>gdmphotosetup</command> command to 
+        configure the image to use for their userid.  This program properly
+        scales the file down if it is larger than the
+        <filename>MaxIconWidth</filename> or 
+        <filename>MaxIconHeight</filename> configuration options and places the
+        icon in a file called <filename>~/.face</filename>.  Although
+        <command>gdmphotosetup</command> scales user images automatically,
+        this does not guarantee that user images are properly scaled since
+        a user may create their <filename>~/.face</filename> file by hand.
+      </para>
         
-      <para>GDM will first look for the user's face image in <filename>~/.face</filename>. If not found, it will try <filename>~/.face.icon</filename>. If still not found, it will use the value defined for "face/picture=" in the <filename>~/.gnome2/gdm</filename> file. Lastly, it will try <filename>~/.gnome2/photo</filename> and <filename>~/.gnome/photo</filename> which are deprecated and supported for backwards compatibility.</para>
-
-      <para>If a user has no defined face image, GDM will use the "stock_person" icon defined in the current GTK+ theme. If no such image is defined, it will fallback to the image specified in the <filename>DefaultFace</filename> configuration option, normally <filename>&lt;share&gt;/pixmaps/nobody.png</filename>.</para>
+      <para>
+        GDM will first look for the user's face image in
+        <filename>~/.face</filename>.  If not found, it will try 
+        <filename>~/.face.icon</filename>.  If still not found, it will
+        use the value defined for "face/picture=" in the 
+        <filename>~/.gnome2/gdm</filename> file.  Lastly, it will try
+        <filename>~/.gnome2/photo</filename> and 
+        <filename>~/.gnome/photo</filename> which are deprecated and
+        supported for backwards compatibility.
+      </para>
+
+      <para>
+        If a user has no defined face image, GDM will use the
+        "stock_person" icon defined in the current GTK+ theme.  If no
+        such image is defined, it will fallback to the image specified in the
+        <filename>DefaultFace</filename> configuration option, normally
+        <filename>&lt;share&gt;/pixmaps/nobody.png</filename>.
+      </para>
       
-      <para>Please note that loading and scaling face icons located in user home directories can be a very time-consuming task. Since it not practical to load images over NIS or NFS, GDM does not attempt to load face images from remote home directories. Furthermore, GDM will give up loading face images after 5 seconds of activity and will only display the users whose pictures it has gotten so far. The <filename>Include</filename> configuration option can be used to specify a set of users who should appear on the face browser. As long as the users to include is of a reasonable size, there should not be a problem with GDM being unable to access the face images. To work around such problems, it is recommended to place face images in the directory specified by the <filename>GlobalFaceDir</filename> configuration option.</para>
+      <para>
+        Please note that loading and scaling face icons located in user home
+        directories can be a very time-consuming task.  Since it not 
+        practical to load images over NIS or NFS, GDM does not attempt to
+        load face images from remote home directories.  Furthermore, GDM will
+        give up loading face images after 5 seconds of activity and will
+        only display the users whose pictures it has gotten so far.  The
+        <filename>Include</filename> configuration option can be used to
+        specify a set of users who should appear on the face browser.  As
+        long as the users to include is of a reasonable size, there should
+        not be a problem with GDM being unable to access the face images.
+        To work around such problems, it is recommended to place face images
+        in the directory specified by the <filename>GlobalFaceDir</filename>
+        configuration option.
+      </para>
 
       <para>Для керування відображенням портретів у конфігураційному файлі є декілька параметрів. Якщо параметр <filename>IncludeAll</filename> встановлено у true, тоді у параметрі <filename>Include</filename> вказується список розділених комою імен користувачів, які будуть відображатись. Не залежно від параметра <filename>IncludeAll</filename>  не будуть відображатись будь-які користувачі, перелічені у списку <filename>Exclude</filename> та користувачі, ідентифікатор користувача (UID) яких менший за <filename>MinimalUID</filename>. <filename>IncludeAll</filename> не рекомендується для систем, на яких паролі передаються через мережу (наприклад NIS), тому що передавання великої кількості зображень через мережу може бути досить повільним.</para>
 
@@ -246,9 +473,31 @@
     <sect2 id="performance">
       <title>Швидкодія GDM</title>
 
-      <para>To speed performance it is possible to build GDM so that it will preload libraries when GDM first displays a greeter program. This has been shown to speed first time login since these libraries can be loaded into memory while the user types in their username and password.</para>
-
-      <para>To use this feature, configure GDM with the <command>--with-prefetch</command> option. This will cause GDM to install the <command>gdmprefetch</command> program to the <filename>libexecdir</filename> directory, install the <filename>gdmprefetchlist</filename> to the <filename>&lt;etc&gt;/gdm</filename> directory, and set the <filename>PreFetchProgram</filename> configuration variable so that the <command>gdmprefetch</command> program is called with the default <filename>gdmprefetchlist</filename> file. The default <filename>gdmprefetchlist</filename> file was optimized for a GNOME desktop running on Solaris, so may need fine-tuning on other systems. Alternative prefetchlist files can be contributed to the "gdm" category in <ulink type="http" url="http://bugzilla.gnome.org/">bugzilla.gnome.org</ulink>, so that they can be included in future GDM releases.</para>
+      <para>
+        To speed performance it is possible to build GDM so that it will
+        preload libraries when GDM first displays a greeter program.  This
+        has been shown to speed first time login since these libraries can
+        be loaded into memory while the user types in their username and
+        password.
+      </para>
+
+      <para>
+        To use this feature, configure GDM with the
+        <command>--with-prefetch</command> option.  This will cause GDM to
+        install the <command>gdmprefetch</command> program to the
+        <filename>libexecdir</filename> directory, install the
+        <filename>gdmprefetchlist</filename> to the
+        <filename>&lt;etc&gt;/gdm</filename> directory, and set the
+        <filename>PreFetchProgram</filename> configuration variable so that the
+        <command>gdmprefetch</command> program is called with the default
+        <filename>gdmprefetchlist</filename> file.  The default
+        <filename>gdmprefetchlist</filename> file was optimized
+        for a GNOME desktop running on Solaris, so may need fine-tuning on
+        other systems.  Alternative prefetchlist files can be contributed
+        to the "gdm" category in
+        <ulink type="http" url="http://bugzilla.gnome.org/">bugzilla.gnome.org</ulink>,
+        so that they can be included in future GDM releases.
+      </para>
     </sect2>
   </sect1>
 
@@ -258,31 +507,87 @@
     <sect2 id="PAM">
       <title>PAM</title>
 
-      <para>GDM uses PAM for login authentication, though if your machine does not support PAM you can build GDM to work with the password database and the crypt library function.</para>
-
-      <para>PAM stands for Pluggable Authentication Module, and is used by most programs that request authentication on your computer. It allows the administrator to configure different authentication behavior for different programs.</para>
-
-      <para>Some GDM features (like turning on automatic login) may require that you update your PAM configuration. PAM configuration has different, but similar, interfaces on different operating systems, so check your pam.d or pam.conf man page for details. Be sure that you read the PAM documentation (e.g. pam.d/pam.conf man page) and are comfortable with the security implications of any changes you intend to make to your configuration.</para>
-
-      <para>If there is no entry for GDM in your system's PAM configuration file, then features like automatic login may not work. Not having an entry will causes GDM to use default behavior, conservative settings are recommended and probably shipped with your distribution.</para>
-
-      <para>If you wish to make GDM work with other types of authentication mechanisms (such as a SmartCard), then you should implement this by using a PAM service module for the desired authentication type rather than by trying to modify the GDM code directly. Refer to the PAM documentation on your system. This issue has been discussed on the <address><email>gdm-list@gnome.org</email></address> mail list, so you can refer to the list archives for more information.</para>
+      <para>
+        GDM uses PAM for login authentication, though if your machine does not
+        support PAM you can build GDM to work with the password database and
+        the crypt library function.
+      </para>
+
+      <para>
+        PAM stands for Pluggable Authentication Module, and is used by most
+        programs that request authentication on your computer.  It allows the
+        administrator to configure different authentication behavior for
+        different programs.
+      </para>
+
+      <para>
+        Some GDM features (like turning on automatic login) may require that
+        you update your PAM configuration.  PAM configuration has different,
+        but similar, interfaces on different operating systems, so check your
+        pam.d or pam.conf man page for details.  Be sure that you read the
+        PAM documentation (e.g. pam.d/pam.conf man page) and are comfortable
+        with the security implications of any changes you intend to make to
+        your configuration.
+      </para>
+
+      <para>
+        If there is no entry for GDM in your system's PAM configuration file,
+        then features like automatic login may not work.  Not having an entry
+        will causes GDM to use default behavior, conservative settings are
+        recommended and probably shipped with your distribution.
+      </para>
+
+      <para>
+        If you wish to make GDM work with other types of authentication
+        mechanisms (such as a SmartCard), then you should implement this by
+        using a PAM service module for the desired authentication type rather
+        than by trying to modify the GDM code directly.  Refer to the PAM
+        documentation on your system.  This issue has been discussed on the
+        <address><email>gdm-list@gnome.org</email></address> mail list,
+        so you can refer to the list archives for more information.
+      </para>
     </sect2>
 
     <sect2 id="gdmuser">
       <title>Користувач GDM</title>
 
-      <para>For security reasons a dedicated user and group id are required for proper operation! The need to be able to write Xauth files is why user "nobody" is not appropriate for gdm.</para>
+      <para>
+        For security reasons a dedicated user and group id are required for
+        proper operation!  The need to be able to write Xauth files is why user
+        "nobody" is not appropriate for gdm.
+      </para>
 
       <para>Зазвичай GDM сервер запускається від імені адміністратора (root). Але GDM також має призначені ідентифікатори користувача (uid) та групи (gid), якими він користується для запуску графічного інтерфейсу, тобто <command>gdmgreeter</command> та <command>gdmlogin</command>. Вона налаштовуються у параметрах <filename>User</filename> та <filename>Group</filename> у файлі конфігурації GDM. Користувач та група мають існувати перед запуском "make install". Зазвичай користувач та група  GDM називається "gdm". </para>
 
-      <para>This userid is used to run the GDM GUI programs required for login. All functionality that requires root authority is done by the GDM daemon process. This design ensures that if the GUI programs are somehow exploited, only the dedicated user privileges are available.</para>
+      <para>
+        This userid is used to run the GDM GUI programs required for login.
+        All functionality that requires root authority is done by the GDM
+        daemon process.  This design ensures that if the GUI programs are
+        somehow exploited, only the dedicated user privileges are available.
+      </para>
 
       <para> слід зауважити, що користувач та група GDM мають деякі привілеї, які іноді можуть становити загрозу безпеці. По-перше, вони мають доступ до каталогу авторизації X-сервера. Також GDM повинен мати право на читання та запис ключів Xauth у  <filename>&lt;var&gt;/lib/gdm</filename>. Власником цього каталогу має бути  root:gdm, а  права доступу 1770. Ці права призначаються каталогу при виконанні "make install". Служба GDM буде встановлювати цьому каталогу правильні права, якщо вони відрізняються. </para>
 
-      <para>The danger is that someone who gains the GDM user/group privileges can then connect to any session. So you should not, under any circumstances, make this some user/group which may be easy to get access to, such as the user <filename>nobody</filename>. Users who gain access to the "gdm" user could also modify the Xauth keys causing Denial-Of-Service attacks. Also if a person gains the ability to run programs as the user "gdm", it would be possible to snoop on running GDM processes, including usernames and passwords as they are being typed in.</para>
-
-      <para>Distributions and system administrators using GDM are expected to setup the dedicated user properly. It is recommended that this userid be configured to disallow login and to not have a default shell. Distributions and system administrators should set up the filesystem to ensure that the GDM user does not have read or write access to sensitive files.</para>
+      <para>
+        The danger is that someone who gains the GDM user/group privileges can
+        then connect to any session.  So you should not, under any
+        circumstances, make this some user/group which may be easy to get
+        access to, such as the user <filename>nobody</filename>.  Users who
+        gain access to the "gdm" user could also modify the Xauth
+        keys causing Denial-Of-Service attacks.  Also if a person gains the
+        ability to run programs as the user "gdm", it would be
+        possible to snoop on running GDM processes, including usernames and
+        passwords as they are being typed in.  
+      </para>
+
+      <para>
+        Distributions and system administrators using GDM are expected to setup
+        the dedicated user properly.  It is recommended that this userid be
+        configured to disallow login and to not have a default shell.
+        Distributions and system administrators should set up the filesystem to
+        ensure that the GDM user does not have read or write access to
+        sensitive files.
+      </para>
     </sect2>
 
     <sect2 id="xauth">
@@ -304,7 +609,10 @@
 
       <para>Також буде розумно блокувати на брандмауері всі порти X сервера (TCP порт 6000 + номер дисплею). Зауважте, що різні частини GDM використовують дисплеї з номером 20 та більше (наприклад, при запуску серверів за вимогою).</para>
 
-      <para>X is not a very safe protocol for leaving on the net, and XDMCP is even less safe.</para>
+      <para>
+         X is not a very safe protocol for leaving on the net, and XDMCP is
+         even less safe.  
+      </para>
     </sect2>
 
     <sect2 id="nfssecurity">
@@ -316,13 +624,26 @@
     <sect2 id="xdmcpsecurity">
       <title>Безпека XDCMP</title>
 
-      <para>Even though your display is protected by cookies, XEvents and thus keystrokes typed when entering passwords will still go over the wire in clear text. It is trivial to capture these.</para>
+      <para>
+        Even though your display is protected by cookies, XEvents and thus
+        keystrokes typed when entering passwords will still go over the wire in
+        clear text.  It is trivial to capture these.
+      </para>
 
       <para>Головним чином XDMCP використовується для тонких клієнтів у лабораторних умовах. Цім тонким клієнтам для доступу до сервера необхідна лише мережа, та, здається, найкращою політикою безпеки буде тримати їх у окремій мережі, до якої неможливо отримати доступ із зовнішнього світу, а зв'язок є лише з сервером. Єдиною точкою доступу до зовнішнього світу повинен бути сервер.</para>
 
-      <para>The above sections "X Server Authentication Scheme" and "Firewall Security" also contain important information about using XDMCP securely. The next section also discusses how to set up XDMCP access control.</para>
-
-      <para>To workaround the inherent insecurity of XDMCP, gdm proposes a default built-in session that uses SSH to encrypt the remote connection. See the section "Securing remote connection through SSH" above.</para>
+      <para>
+        The above sections "X Server Authentication Scheme" and
+        "Firewall Security" also contain important information about
+        using XDMCP securely.  The next section also discusses how to set up
+        XDMCP access control.
+      </para>
+
+      <para>
+        To workaround the inherent insecurity of XDMCP, gdm proposes a default
+        built-in session that uses SSH to encrypt the remote connection.  See
+        the section "Securing remote connection through SSH" above.
+      </para>
     </sect2>
 
     <sect2 id="xdmcpaccess">
@@ -345,86 +666,357 @@ gdm: .your.domain
   <sect1 id="gdmsetupusage">
     <title>Using gdmsetup To Configure GDM</title>
 
-    <para>The <command>gdmsetup</command> application can be used to configure GDM. If you believe running root-owned GUI's causes security risk, then you would want to always edit the files by hand and not use <command>gdmsetup</command>. Editing the files by hand is explained in the "Configuration" section of this document. Note that <command>gdmsetup</command> does not support changing of all configuration variables, so it may be necessary to edit the files by hand for some configurations.</para>
-
-    <para>The <command>gdmsetup</command> program has five tabs: Local, Remote, Accessibility, Security, and Users, described below. In parenthesis is information about which GDM configuration key is affected by each GUI choice. Refer to the "Configuration" section of this manual and the comments in the &lt;share&gt;/gdm/defaults.conf file for additional details about each key.</para>
+    <para>
+      The <command>gdmsetup</command> application can be used to configure GDM.
+      If you believe running root-owned GUI's causes security risk, then you
+      would want to always edit the files by hand and not use
+      <command>gdmsetup</command>.  Editing the files by hand is explained in
+      the "Configuration" section of this document.  Note that 
+      <command>gdmsetup</command> does not support changing of all
+      configuration variables, so it may be necessary to edit the files by
+      hand for some configurations.
+    </para>
+
+    <para>
+      The <command>gdmsetup</command> program has five tabs: Local, Remote,
+      Accessibility, Security, and Users, described below.  In parenthesis is
+      information about which GDM configuration key is affected by each GUI
+      choice.  Refer to the "Configuration" section of this manual
+      and the comments in the &lt;share&gt;/gdm/defaults.conf file for
+      additional details about each key.
+    </para>
 
     <sect2 id="gdmsetuplocaltab">
       <title>Local Tab</title>
      
-      <para>The Local tab is used for controlling the appearance of GDM for local/static displays (non-XDMCP remote connections). The choices available in this tab depend on the setting of the "Style" combobox. This combobox is used to determine whether the "Plain" or "Themed" greeter GUI is used. The differences between these greeter programs are explained in the "Overview" section of this document.</para>
-
-      <para>If the "Style" choice is "Plain", then GDM will use the <command>gdmlogin</command> program as the GUI (daemon/Greeter). When this choice is selected, <command>gdmsetup</command> allows the user to select whether the background is an image or solid color (greeter/BackgroundType). If image is selected, there is a file selection button to pick the image file (greeter/BackgroundImage) and a checkbox to scale the image to fit the screen (greeter/BackgroundImageScaleToFit). If solid color is selected, there is a button available to allow the color selection (greeter/BackgroundColor). Also, the user may select the logo image that appears in gdmlogin (greeter/Logo).</para>
-
-      <para>If the "Style" choice is "Plain with face browser", then the <command>gdmlogin</command> program is used as the GUI (daemon/Greeter) and the face browser is turned on (greeter/Browser). The Face Browser is explained in the Overview section. Otherwise, the choices are the same as when the "Style" choice is "Plain". Additional setup in the Users tab may be necessary to choose which users appear in the Face Browser.</para>
-
-      <para>If the "Style" choice is "Themed", then the <command>gdmgreeter</command> program is used as the GUI (daemon/Greeter). When this choice is selected, <command>gdmsetup</command> allows the user to select the theme to be used (greeter/GraphicalTheme). Note that the checkbox to the left of the theme's name must be checked for a theme to be selected. Clicking on the theme, but not selecting the checkbox will highlight the theme and the "Remove" button can be used to delete the theme. Information about the theme's author and copyright are shown for the highlighted theme. The "Add" button can be used to add new themes to the system. To turn on the Face Browser, a theme which includes a Face Browser must be selected, such as happygnome-list. The "Background color" displayed when GDM starts (and if the theme has transparent elements) can also be selected (greeter/GraphicalThemedColor). The "Theme" combo box may be set to "Random from selected" if you want a random theme to be used for each login (greeter/GraphicalThemeRand and greeter/GraphicalThemes). To use random themes, select each theme that you wish to be used. By default this combobox is set to "Selected only", so that only a single theme can be selected and be used.</para>
-
-      <para>Regardless of the "Style" choice, the user may also select whether the Actions menu is visible (greeter/SystemMenu), whether the Actions menu includes the choice to start <command>gdmsetup</command> (greeter/ConfigAvailable), and whether the Action menu includes the choice to start <command>gdmchooser</command> to run a remote XDMCP login session (greeter/ChooserButton). Note that the root password must be entered to start <command>gdmsetup</command> from the login screen if it is enabled. Also the Welcome message displayed for local sessions may be selected (greeter/DefaultWelcome and greeter/Welcome). The Welcome message can contain the character sequences described in the "Text Node" section of the "Themed Greeter" section of this manual.</para>
+      <para>
+        The Local tab is used for controlling the appearance of GDM for
+        local/static displays (non-XDMCP remote connections).  The choices
+        available in this tab depend on the setting of the "Style"
+        combobox.  This combobox is used to determine whether the 
+        "Plain" or "Themed" greeter GUI is used.  The
+        differences between these greeter programs are explained in the
+        "Overview" section of this document.
+      </para>
+
+      <para>
+        If the "Style" choice is "Plain", then GDM will
+        use the <command>gdmlogin</command> program as the GUI
+        (daemon/Greeter).  When this choice is selected,
+        <command>gdmsetup</command> allows the user to select whether the
+        background is an image or solid color (greeter/BackgroundType).  If
+        image is selected, there is a file selection button to pick the image
+        file (greeter/BackgroundImage) and a checkbox to scale the image to fit
+        the screen (greeter/BackgroundImageScaleToFit).  If solid color is
+        selected, there is a button available to allow the color selection
+        (greeter/BackgroundColor).  Also, the user may select the logo image
+        that appears in gdmlogin (greeter/Logo).
+      </para>
+
+      <para>
+        If the "Style" choice is "Plain with face browser",
+        then the <command>gdmlogin</command> program is used as the GUI
+        (daemon/Greeter) and the face browser is turned on (greeter/Browser).
+        The Face Browser is explained in the Overview section.  Otherwise,
+        the choices are the same as when the "Style" choice is
+        "Plain".  Additional setup in the Users tab may be 
+        necessary to choose which users appear in the Face Browser.
+      </para>
+
+      <para>
+        If the "Style" choice is "Themed", then the 
+        <command>gdmgreeter</command> program is used as the GUI
+        (daemon/Greeter).  When this choice is selected,
+        <command>gdmsetup</command> allows the user to select the theme to be
+        used (greeter/GraphicalTheme).  Note that the checkbox to the left
+        of the theme's name must be checked for a theme to be selected.
+        Clicking on the theme, but not selecting the checkbox will highlight
+        the theme and the "Remove" button can be used to delete
+        the theme.  Information about the theme's author and copyright are
+        shown for the highlighted theme.  The "Add" button can be
+        used to add new themes to the system.  To turn on the Face Browser, a
+        theme which includes a Face Browser must be selected, such as 
+        happygnome-list.  The "Background color" displayed when
+        GDM starts (and if the theme has transparent elements) can also be
+        selected (greeter/GraphicalThemedColor).  The "Theme" combo
+        box may be set to "Random from selected" if you want a random
+        theme to be used for each login (greeter/GraphicalThemeRand and
+        greeter/GraphicalThemes).  To use random themes, select each theme that
+        you wish to be used.  By default this combobox is set to
+        "Selected only", so that only a single theme can be selected
+        and be used.
+      </para>
+
+      <para>
+        Regardless of the "Style" choice, the user may also select
+        whether the Actions menu is visible (greeter/SystemMenu), whether the
+        Actions menu includes the choice to start <command>gdmsetup</command>
+        (greeter/ConfigAvailable), and whether the Action menu includes the
+        choice to start <command>gdmchooser</command> to run a remote XDMCP
+        login session (greeter/ChooserButton).  Note that the root password
+        must be entered to start <command>gdmsetup</command> from the login
+        screen if it is enabled.   Also the Welcome message displayed for local
+        sessions may be selected (greeter/DefaultWelcome and greeter/Welcome). 
+        The Welcome message can contain the character sequences described in
+        the "Text Node" section of the "Themed Greeter"
+        section of this manual.
+      </para>
     </sect2>
 
     <sect2 id="gdmsetupremotetab">
       <title>Remote Tab</title>
 
-      <para>The Remote tab controls the appearance of the GDM for users logging in via XDMCP. By default XDMCP is disabled, and users should be comfortable with the XDMCP-related sections of the Security section of this document before enabling it. This tab includes a "Style" combobox which can be used to turn on XDMCP and control the appearance of GDM for remote users (gui/RemoteGreeter and xdmcp/Enable). This combobox may be set to "Remote login disabled" or "Same as Local". If the Local tab is set to "Plain" or "Plain with Face Browser", then the user may also select "Themed". If the Local tab is set to "Themed", then the user may also select "Plain" or "Plain with face browser". It is recommended that the "Plain" GUI be used for remote connections since it is more lightweight and tends to have better performance across a network.</para>
-
-      <para>If Remote login is enabled, then the user can specify the remote Welcome Message to be displayed (greeter/DefaultRemoteWelcome and greeter/RemoteWelcome). This welcome message is separate from the Local welcome message and can have a different value. The Welcome message can contain the character sequences described in the "Text Node" section of the "Themed Greeter" section of this manual.</para>
-
-      <para>If the "Style" choice is "Same as Local" and the local selection is "Plain" or "Plain with face browser", then the user may select whether background images should be displayed for remote logins (greeter/BackgroundRemoteOnlyColor).</para>
-
-      <para>If the "Style" choice is enabled and set to a different value than the Local tab, then the user has the same configuration choices as found on the Local tab except that the System Menu choices are not available since this is never available for remote logins for security purposes.</para>
-
-      <para>If Remote login is enabled, there is a "Configure XDMCP" button which displays a dialog allowing the user to set XDMCP configuration, including whether indirect requests are honored (xdmcp/HonorIndirect), UDP port (xdmcp/Port), maximum pending requests (xdmcp/MaxPending), maximum pending indirect requests (xmdcp/MaxPendingIndirect), maximum remote sessions (xdmcp/MaxSessions), maximum wait time (xdmcp/MaxWait), maximum indirect wait time (xdmcp/MaxWaitIndirect), displays per host (xdmcp/DisplaysPerHost), and ping interval (xdmcp/PingIntervalSeconds). The default settings are standard settings and should only be changed by someone who understands the ramifications of the change.</para>
+      <para>
+        The Remote tab controls the appearance of the GDM for users logging
+        in via XDMCP.  By default XDMCP is disabled, and users should be 
+        comfortable with the XDMCP-related sections of the Security section
+        of this document before enabling it.  This tab includes a
+        "Style" combobox which can be used to turn on XDMCP and
+        control the appearance of GDM for remote users (gui/RemoteGreeter
+        and xdmcp/Enable).  This combobox may be set to "Remote login
+        disabled" or "Same as Local".  If the Local tab
+        is set to "Plain" or "Plain with Face Browser",
+        then the user may also select "Themed".  If the Local tab
+        is set to "Themed", then the user may also select
+        "Plain" or "Plain with face browser".  It is
+        recommended that the "Plain" GUI be used for remote
+        connections since it is more lightweight and tends to have better
+        performance across a network.
+      </para>
+
+      <para>
+        If Remote login is enabled, then the user can specify the remote
+        Welcome Message to be displayed (greeter/DefaultRemoteWelcome and 
+        greeter/RemoteWelcome).  This welcome message is separate from the
+        Local welcome message and can have a different value.  The Welcome
+        message can contain the character sequences described in the
+        "Text Node" section of the "Themed Greeter"
+        section of this manual.
+      </para>
+
+      <para>
+        If the "Style" choice is "Same as Local" and the
+        local selection is "Plain" or "Plain with face
+        browser", then the user may select whether background images
+        should be displayed for remote logins
+        (greeter/BackgroundRemoteOnlyColor).
+      </para>
+
+      <para>
+        If the "Style" choice is enabled and set to a different
+        value than the Local tab, then the user has the same configuration
+        choices as found on the Local tab except that the System Menu 
+        choices are not available since this is never available for remote
+        logins for security purposes.
+      </para>
+
+      <para>
+        If Remote login is enabled, there is a "Configure XDMCP"
+        button which displays a dialog allowing the user to set XDMCP 
+        configuration, including whether indirect requests are honored
+        (xdmcp/HonorIndirect), UDP port (xdmcp/Port), maximum pending requests
+        (xdmcp/MaxPending), maximum pending indirect requests
+        (xmdcp/MaxPendingIndirect), maximum remote sessions
+        (xdmcp/MaxSessions), maximum wait time (xdmcp/MaxWait), maximum
+        indirect wait time (xdmcp/MaxWaitIndirect), displays per host
+        (xdmcp/DisplaysPerHost), and ping interval (xdmcp/PingIntervalSeconds).
+        The default settings are standard settings and should only be changed
+        by someone who understands the ramifications of the change.
+      </para>
     </sect2>
 
     <sect2 id="gdmsetupaccessibilitytab">
       <title>Accessibility Tab</title>
 
-      <para>The Accessibility tab is used to turn on Accessibility features in GDM. "Enable accessible login" (daemon/AddGtkModules and daemon/GtkModulesList) turns on GDM's gesture listeners which are explained in the "Accessibility" section of this document. There is also a checkbox to allow users to change the theme when using the Plain greeter (gui/AllowGtkThemeChange). This feature allows GDM users to switch the theme to the HighContrast or LowContrast themes if needed. The user may also select whether GDM should play a sound when the login screen is ready, when login is successful and when login has failed. File chooser buttons are used to select the sound file to be played, and the "Play" button can be used to sample the sound.</para>
+      <para>
+        The Accessibility tab is used to turn on Accessibility features in GDM.
+        "Enable accessible login" (daemon/AddGtkModules and
+        daemon/GtkModulesList) turns on GDM's gesture listeners which are
+        explained in the "Accessibility" section of this document.
+        There is also a checkbox to allow users to change the theme when using 
+        the Plain greeter (gui/AllowGtkThemeChange).  This feature allows GDM
+        users to switch the theme to the HighContrast or LowContrast themes if
+        needed.  The user may also select whether GDM should play a sound when
+        the login screen is ready, when login is successful and when login has
+        failed.  File chooser buttons are used to select the sound file to be
+        played, and the "Play" button can be used to sample the
+        sound.
+      </para>
     </sect2>
 
     <sect2 id="gdmsetupsecuritytab">
       <title>Security Tab</title>
 
-      <para>The Security tab allows the user to turn on Automatic and Timed login, which user is logged in via an automatic or timed login, and the timed login delay (daemon/AutomaticLoginEnable, daemon/AutomaticLogin, daemon/TimedLoginEnable, daemon/TimedLogin, and daemon/TimedLoginDelay). If automatic login is turned on, then the specified user will immediately log in on reboot without GDM asking for username/password. If the user logs out of their session, GDM will start and ask for username and password to log back in. If TimedLogin is turned on, then GDM will log in to the specified user after a specified number of seconds. The user may enable Timed Login for remote (XDMCP) connections by checking the "Allow remote timed logins" checkbox.</para>
-
-      <para>On this tab, the user may select whether the system administrator user can log in, and whether the system administrator user can log in via remote (XDMCP) connections (security/AllowRoot and security/AllowRemoteRoot). The user may turn on GDM debug (debug/Enable) which causes debug messages to be sent to the system log. Debug should only be used when diagnosing a problem and not be left on when not needed. The "Deny TCP connections to Xserver" choice will disable X forwarding if selected (security/DisallowTCP). A login retry delay (security/RetryDelay) can be set to cause GDM to wait a number of seconds after a failed login.</para>  
-
-      <para>The "Configure X Server" button can be used to specify how GDM manages each display. The "Servers" combobox shows what server definitions are available (Standard, Terminal, and Chooser by default). Refer to the "X Server Definitions" section of the "Configuration" section for more information about how to create new Server Definitions.</para>
-
-      <para>For any server type, the user may modify the "Server Name" (server/name), the "Command" (server/command) to be used to launch the Xserver, whether the server type will "Launch" (server/chooser) the greeter or chooser GUI after starting the Xserver, whether GDM handles this type (normally only set to false when logging into a Terminal session type), and whether the session type supports "Flexible" (server/flexible) sessions.</para>
-
-      <para>The "Servers To Start" section shows what server type is displayed for each display on the machine. Users may click on the "Add/Modify" button to add a new display to the list or to modify a selected display. This simply corresponds each physical display with the Server Definition to be used for managing that display. The "Remove" button may be used to remove a display from the list.</para>
+      <para>
+        The Security tab allows the user to turn on Automatic and Timed login,
+        which user is logged in via an automatic or timed login, and the
+        timed login delay (daemon/AutomaticLoginEnable, daemon/AutomaticLogin,
+        daemon/TimedLoginEnable, daemon/TimedLogin, and daemon/TimedLoginDelay).
+        If automatic login is turned on, then the specified user will
+        immediately log in on reboot without GDM asking for username/password.
+        If the user logs out of their session, GDM will start and ask for
+        username and password to log back in.  If TimedLogin is turned on, then
+        GDM will log in to the specified user after a specified number of
+        seconds.  The user may enable Timed Login for remote (XDMCP)
+        connections by checking the "Allow remote timed logins"
+        checkbox.
+      </para>
+
+      <para>
+        On this tab, the user may select whether the system administrator user
+        can log in, and whether the system administrator user can log in
+        via remote (XDMCP) connections (security/AllowRoot and
+        security/AllowRemoteRoot).  The user may turn on GDM debug 
+        (debug/Enable) which causes debug messages to be sent to the system
+        log.  Debug should only be used when diagnosing a problem and not be
+        left on when not needed.  The "Deny TCP connections to
+        Xserver" choice will disable X forwarding if selected
+        (security/DisallowTCP).  A login retry delay (security/RetryDelay) can
+        be set to cause GDM to wait a number of seconds after a failed login.
+      </para>  
+
+      <para>
+         The "Configure X Server" button can be used to specify how
+         GDM manages each display.  The "Servers" combobox shows what
+         server definitions are available (Standard, Terminal, and Chooser by
+         default).  Refer to the "X Server Definitions" section of
+         the "Configuration" section for more information about how 
+         to create new Server Definitions.
+      </para>
+
+      <para>
+         For any server type, the user may modify the "Server Name"
+         (server/name), the "Command" (server/command) to be used to
+         launch the Xserver, whether the server type will "Launch"
+         (server/chooser) the greeter or chooser GUI after starting the
+         Xserver, whether GDM handles this type (normally only set to false
+         when logging into a Terminal session type), and whether the session
+         type supports "Flexible" (server/flexible) sessions.
+      </para>
+
+      <para>
+         The "Servers To Start" section shows what server type is
+         displayed for each display on the machine.  Users may click on the
+         "Add/Modify" button to add a new display to the list or to
+         modify a selected display.  This simply corresponds each physical
+         display with the Server Definition to be used for managing that
+         display.  The "Remove" button may be used to remove a
+         display from the list.
+      </para>
     </sect2>
 
     <sect2 id="gdmsetupuserstab">
       <title>Users Tab</title>
 
-      <para>The Users tab controls which users appear in the Face Browser. If the "Include all users from /etc/password" checkbox is selected, then all users (with a userid above greeter/MinimalUID and not in the Exclude list) are displayed. If this checkbox is not selected, then users must be added to the "Include" list. Users in the "Exclude" list are never displayed. The "Add" and "Remove" buttons are used to add a new user to the list or remove a selected user from the list. The "Apply User Changes" button must be pressed after the "Include" and "Exclude" lists have been modified. The left and right arrow buttons between the "Include" and "Exclude" lists can be used to move a selected user from one list to the other.</para>
+      <para>
+         The Users tab controls which users appear in the Face Browser.  If the
+         "Include all users from /etc/password" checkbox is selected,
+         then all users (with a userid above greeter/MinimalUID and not in the
+         Exclude list) are displayed.  If this checkbox is not selected, then
+         users must be added to the "Include" list.  Users in the
+         "Exclude" list are never displayed.  The "Add" and
+         "Remove" buttons are used to add a new user to the list or
+         remove a selected user from the list.  The "Apply User
+         Changes" button must be pressed after the "Include" and
+         "Exclude" lists have been modified.  The left and right
+         arrow buttons between the "Include" and "Exclude"
+         lists can be used to move a selected user from one list to the other.
+      </para>
     </sect2>
   </sect1>
 
   <sect1 id="configuration">
     <title>Налаштовування</title>
 
-    <para>GDM has powerful configuration management. System configuration is stored in <filename>&lt;share&gt;/gdm/defaults.conf</filename> and the intention is that this file can be stored on a shared filesystem so that sysadmins can have a single file to modify to control configuration for multiple machines. Also GDM distributions may patch this file on update to improve usability, improve security, etc. Configuration may be customized for a specific machine by editing the <filename>&lt;etc&gt;/gdm/custom.conf</filename> file to include an override for a specific key. Those parameters in the "gui", "greeter" sections, and the security/PamStack key may be customized per-display by specifying them in a file named <filename>&lt;etc&gt;/gdm/custom.conf&lt;display num&gt;</filename>. For example, configuration overrides for display ":103" would be stored in the file <filename>&lt;etc&gt;/gdm/custom.conf:0</filename>. Per-display configuration is supported in GDM 2.14.6 and later.</para>
-
-    <para>The <command>gdmsetup</command> is a GUI program you can use to edit the GDM configuration. This program may also be launched directly from the login screen if the greeter/ConfigAvailable key is set to "true" Not all keys in the GDM configuration file are supported in the GUI, so you may need to edit the configuration files by hand to edit these keys. If you believe running root-owned GUI's causes security risk, then you would want to always edit the files by hand. This program does not support setting per-display configuration, so per-display configuration files must be set up by hand.</para>
-
-    <para>Distributions should edit the <filename>&lt;share&gt;/gdm/defaults.conf</filename> file to establish the default values so these are preserved as defaults and not modified by users modifying their personal configuration file <filename>&lt;etc&gt;/gdm/custom.conf</filename>.</para>
-
-    <para>If you want to change configuration by hand, edit the <filename>&lt;etc&gt;/gdm/custom.conf</filename> file and make sure the keyname=value pair you want is included in the appropriate section. For example, to change the "Greeter" key in the "daemon" section, make sure the daemon section of the <filename>&lt;etc&gt;/gdm/custom.conf</filename> file has the value like in this example.</para>
+    <para> 
+      GDM has powerful configuration management.  System configuration is stored
+      in <filename>&lt;share&gt;/gdm/defaults.conf</filename> and the intention
+      is that this file can be stored on a shared filesystem so that sysadmins
+      can have a single file to modify to control configuration for multiple
+      machines.  Also GDM distributions may patch this file on update to 
+      improve usability, improve security, etc.  Configuration may be customized
+      for a specific machine by editing the
+      <filename>&lt;etc&gt;/gdm/custom.conf</filename> file to include an
+      override for a specific key.  Those parameters in the "gui",
+      "greeter" sections, and the security/PamStack key may be
+      customized per-display by specifying them in a file named
+      <filename>&lt;etc&gt;/gdm/custom.conf&lt;display num&gt;</filename>.
+      For example, configuration overrides for display ":103" would be
+      stored in the file <filename>&lt;etc&gt;/gdm/custom.conf:0</filename>.
+      Per-display configuration is supported in GDM 2.14.6 and later.
+    </para>
+
+    <para>
+      The <command>gdmsetup</command> is a GUI program you can use to edit the
+      GDM configuration.  This program may also be launched directly from the
+      login screen if the greeter/ConfigAvailable key is set to "true"
+      Not all keys in the GDM configuration file are supported in the GUI, so
+      you may need to edit the configuration files by hand to edit these keys.
+      If you believe running root-owned GUI's causes security risk, then you
+      would want to always edit the files by hand.  This program does not
+      support setting per-display configuration, so per-display configuration
+      files must be set up by hand.
+    </para>
+
+    <para>
+      Distributions should edit the
+      <filename>&lt;share&gt;/gdm/defaults.conf</filename> file to establish
+      the default values so these are preserved as defaults and not modified
+      by users modifying their personal configuration file
+      <filename>&lt;etc&gt;/gdm/custom.conf</filename>.
+    </para>
+
+    <para>
+      If you want to change configuration by hand, edit the
+      <filename>&lt;etc&gt;/gdm/custom.conf</filename> file and make
+      sure the keyname=value pair you want is included in the appropriate
+      section.  For example, to change the "Greeter" key in the
+      "daemon" section, make sure the daemon section of the
+      <filename>&lt;etc&gt;/gdm/custom.conf</filename> file has the value
+      like in this example.  
+    </para>
 
 <screen>
 [daemon]
 Greeter=/usr/lib/gdmgreeter
 </screen>
 
-    <para>The configuration files (especially the <filename>&lt;share&gt;/gdm/defaults.conf</filename> and <filename>&lt;etc&gt;/gdm/custom.conf</filename> files) contain useful comments and examples, so read them for more information about changing your configuration. GDM considers lines that start with the "#" character a comment, and these lines will be ignored by GDM. Some keys in the <filename>&lt;share&gt;/gdm/defaults.conf</filename> are commented out while others are set. Commented out values show the default value.</para>
-
-    <para>The <filename>&lt;share&gt;/gdm/defaults.conf</filename> file contains the default configuration choices for GDM, and should not be modified by the user. The <filename>&lt;etc&gt;/gdm/custom.conf</filename> file is where users may specify their custom configuration choices. Configuration options specified in the <filename>&lt;etc&gt;/gdm/custom.conf</filename> file override the values in the main <filename>&lt;share&gt;/gdm/defaults.conf</filename> file. Running the <command>gdmsetup</command> command will cause the <filename>&lt;etc&gt;/gdm/custom.conf</filename> to be modified with the user's configuration choices and will cause any running GDM GUI programs to automatically update. Previous to version 2.13.0.4 GDM only supported the <filename>&lt;etc&gt;/gdm/gdm.conf</filename> file, so if using an older version of GDM just edit that file directly.</para>
-
-    <para>The location of the configuration files may be controlled via the <command>--with-defaults-conf</command> and <command>--with-custom-conf</command> configuration options. The GDM daemon --config option may also be used to specify the configuration file location. The GDM daemon must be restarted to change the configuration file being used.</para>
+    <para>
+      The configuration files (especially the
+      <filename>&lt;share&gt;/gdm/defaults.conf</filename> and
+      <filename>&lt;etc&gt;/gdm/custom.conf</filename> files) contain
+      useful comments and examples, so read them for more information about
+      changing your configuration.  GDM considers lines that start with the
+      "#" character a comment, and these lines will be ignored by
+      GDM.  Some keys in the <filename>&lt;share&gt;/gdm/defaults.conf</filename>
+      are commented out while others are set.  Commented out values show the
+      default value.
+    </para>
+
+    <para> 
+      The <filename>&lt;share&gt;/gdm/defaults.conf</filename> file contains
+      the default configuration choices for GDM, and should not be modified by
+      the user.  The <filename>&lt;etc&gt;/gdm/custom.conf</filename> file
+      is where users may specify their custom configuration choices.
+      Configuration options specified in the
+      <filename>&lt;etc&gt;/gdm/custom.conf</filename> file override the
+      values in the main <filename>&lt;share&gt;/gdm/defaults.conf</filename>
+      file.   Running the <command>gdmsetup</command> command will cause the
+      <filename>&lt;etc&gt;/gdm/custom.conf</filename> to be modified with
+      the user's configuration choices and will cause any running GDM GUI 
+      programs to automatically update.  Previous to version 2.13.0.4
+      GDM only supported the <filename>&lt;etc&gt;/gdm/gdm.conf</filename>
+      file, so if using an older version of GDM just edit that file directly.
+    </para>
+
+    <para>
+      The location of the configuration files may be controlled via the
+      <command>--with-defaults-conf</command> and
+      <command>--with-custom-conf</command> configuration options.  The GDM
+      daemon --config option may also be used to specify the configuration
+      file location.  The GDM daemon must be restarted to change the
+      configuration file being used.
+    </para>
 
     <para><filename>&lt;share&gt;/gdm/factory-defaults.conf</filename> - конфігураційний файл, що постачається із службою. Він може знадобитись щоб побачити зміни у файлі <filename>&lt;share&gt;/gdm/defaults.conf</filename> .</para>
 
@@ -445,7 +1037,16 @@ PostSession/
 
     <para><filename>locale.alias</filename> - файл, який схожий на системний файл псевдонімів локалізацій, але насправді вони відрізняються. У ньому перелічені доступні у вашій системі мови. Підтримка кожної мови перевіряється, перш ніж показати її користувачу у списку.</para>
 
-    <para><filename>Xsession</filename> is a script which sets up a user session and then executes the users choice of session. Note that the session script is typically started via the <filename>desktop</filename> file associated with the session the user has picked. Some sessions may start the user's session via a different mechanism than the <filename>Xsession</filename> script, so please check the appropriate <filename>desktop</filename> before assuming a session startup issue is being caused by this file.</para>
+    <para> 
+      <filename>Xsession</filename> is a script which sets up a user session
+      and then executes the users choice of session.  Note that the session
+      script is typically started via the <filename>desktop</filename>
+      file associated with the session the user has picked.  Some 
+      sessions may start the user's session via a different mechanism than
+      the <filename>Xsession</filename> script, so please check the
+      appropriate <filename>desktop</filename> before assuming a session
+      startup issue is being caused by this file.
+    </para>
 
     <para><filename>XKeepsCrashing</filename> - сценарій, який запускається коли X-сервер аварійно завершується декілька разів. Типовий сценарій працює у більшості дистрибутивів Linux. Він може запустити програму налаштовування X-Window, за умови, що особа за консоллю знає пароль адміністратора (root).</para>
 
@@ -484,13 +1085,48 @@ PostSession/
     <sect2 id="configfile">
       <title>Конфігураційний файл - <filename>defaults.conf</filename> та <filename>custom.conf</filename></title>
       
-      <para>GDM uses two configuration files: <filename>&lt;share&gt;/gdm/defaults.conf</filename> and <filename>&lt;etc&gt;/gdm/custom.conf</filename>. The <filename>&lt;share&gt;/gdm/defaults.conf</filename> file contains the default configuration choices for GDM, and should not be modified by the user. The <filename>&lt;etc&gt;/gdm/custom.conf</filename> file is where users may specify their custom configuration choices. Configuration options specified in the <filename>&lt;etc&gt;/gdm/custom.conf</filename> file override the values in the <filename>&lt;share&gt;/gdm/defaults.conf</filename> file. If a configuration option is not defined in either file, GDM will default to the value described in the comments in the <filename>&lt;share&gt;/gdm/defaults.conf</filename> file.</para>
-
-      <para>Running the <command>gdmsetup</command> command will cause the <filename>&lt;etc&gt;/gdm/custom.conf</filename> to be modified with the user's configuration choices.</para>
-
-      <para>Previous to GDM 2.13.0.4 only the <filename>&lt;etc&gt;/gdm/gdm.conf</filename> existed. If upgrading to the new version of GDM, install will check to see if your <filename>&lt;etc&gt;/gdm/gdm.conf</filename> file is different than your <filename>&lt;etc&gt;/gdm/factory-gdm.conf</filename> file. If so, your <filename>&lt;etc&gt;/gdm/gdm.conf</filename> file will be automatically copied to <filename>&lt;etc&gt;/gdm/custom.conf</filename> to preserve any configuration changes.</para>
+      <para>
+        GDM uses two configuration files:
+        <filename>&lt;share&gt;/gdm/defaults.conf</filename>
+        and <filename>&lt;etc&gt;/gdm/custom.conf</filename>.  The
+        <filename>&lt;share&gt;/gdm/defaults.conf</filename> file contains the
+        default configuration choices for GDM, and should not be modified by
+        the user.  The <filename>&lt;etc&gt;/gdm/custom.conf</filename>
+        file is where users may specify their custom configuration choices.  
+        Configuration options specified in the
+        <filename>&lt;etc&gt;/gdm/custom.conf</filename> file override the
+        values in the <filename>&lt;share&gt;/gdm/defaults.conf</filename>
+        file.  If a configuration option is not defined in either file, GDM
+        will default to the value described in the comments in the
+        <filename>&lt;share&gt;/gdm/defaults.conf</filename> file.
+      </para>
+
+      <para>
+        Running the <command>gdmsetup</command> command will cause the 
+        <filename>&lt;etc&gt;/gdm/custom.conf</filename> to be modified
+        with the user's configuration choices.
+      </para>
+
+      <para>
+        Previous to GDM 2.13.0.4 only the
+        <filename>&lt;etc&gt;/gdm/gdm.conf</filename> existed.  If upgrading
+        to the new version of GDM, install will check to see if your
+        <filename>&lt;etc&gt;/gdm/gdm.conf</filename> file is different than
+        your <filename>&lt;etc&gt;/gdm/factory-gdm.conf</filename> file.
+        If so, your <filename>&lt;etc&gt;/gdm/gdm.conf</filename> file will be 
+        automatically copied to
+        <filename>&lt;etc&gt;/gdm/custom.conf</filename> to preserve any
+        configuration changes.
+      </para>
         
-      <para>The location of the configuration files may be controlled via the <command>--with-defaults-conf</command> and <command>--with-custom-conf</command> configuration options. The GDM daemon --config option may instead be used to specify the configuration file location. The GDM daemon must be restarted to change the configuration file being used.</para>
+      <para>
+        The location of the configuration files may be controlled via the
+        <command>--with-defaults-conf</command> and
+        <command>--with-custom-conf</command> configuration options.  The
+        GDM daemon --config option may instead be used to specify the
+        configuration file location.  The GDM daemon must be restarted to
+        change the configuration file being used.
+      </para>
 
       <para>Обидва конфігураційні файли поділяється на розділи, кожен з яких містить змінні, які визначають поведінку окремих частин пакету GDM. Додаткову інформацію про конфігураційні параметри можна отримати з коментарів у файлі <filename>&lt;share&gt;/gdm/defaults.conf</filename>.</para>
 
@@ -523,7 +1159,14 @@ PostSession/
             <term>AlwaysLoginCurrentSession</term>
             <listitem>
               <synopsis>AlwaysLoginCurrentSession=true</synopsis>
-              <para>If true, then when the user logs in and already has an existing session, then they are connected to that session rather than starting a new session. This only works for session's running on VT's (Virtual Terminals) started with gdmflexiserver, and not with XDMCP. Note that VT's are not supported on all operating systems.</para>
+              <para>
+                If true, then when the user logs in and already has an
+                existing session, then they are connected to that session
+                rather than starting a new session.  This only works for
+                session's running on VT's (Virtual Terminals) started with
+                gdmflexiserver, and not with XDMCP.  Note that VT's are not
+                supported on all operating systems.
+              </para>
             </listitem>
           </varlistentry>
 
@@ -601,7 +1244,15 @@ PostSession/
             <term>DefaultPath</term>
             <listitem>
               <synopsis>DefaultPath=типовийшлях (значення визначається при configure)</synopsis>
-              <para>Specifies the path which will be set in the user's session. This value will be overridden with the value from <filename>/etc/default/login</filename> if it contains "ROOT=&lt;pathname&gt;". If the <filename>/etc/default/login</filename> file exists, but contains no value for ROOT, the value as defined in the GDM configuration will be be used.</para>
+              <para>
+                Specifies the path which will be set in the user's session.
+                This value will be overridden with the value from
+                <filename>/etc/default/login</filename> if it contains
+                "ROOT=&lt;pathname&gt;".  If the
+                <filename>/etc/default/login</filename> file exists, but
+                contains no value for ROOT, the value as defined in the GDM
+                configuration will be be used.
+              </para>
             </listitem>
           </varlistentry>
 
@@ -739,7 +1390,18 @@ PostSession/
             <term>PreFetchProgram</term>
             <listitem>
               <synopsis>PreFetchProgram=command</synopsis>
-              <para>Program to be run by the GDM greeter/login program when the initial screen is displayed. The purpose is to provide a hook where files which will be used after login can be preloaded to speed performance for the user. The program will be called once only, the first time a greeter is displayed. The gdmprefetch command may be used. This utility will load any libraries passed in on the command line, or if the argument starts with a "@" character, it will process the file assuming it is an ASCII file containing a list of libraries, one per line, and load each library in the file.</para>
+              <para>
+                Program to be run by the GDM greeter/login program when the
+                initial screen is displayed.  The  purpose is to provide a hook
+                where files which will be used after login can be preloaded to
+                speed performance for the user.  The program will be called
+                once only, the first time a greeter is displayed.  The
+                gdmprefetch command may be used.  This utility will load any
+                libraries passed in on the command line, or if the argument
+                starts with a "@" character, it will process the file assuming
+                it is an ASCII file containing a list of libraries, one per
+                line, and load each library in the file.
+              </para>
             </listitem>
           </varlistentry>
 
@@ -787,7 +1449,16 @@ PostSession/
             <term>RootPath</term>
             <listitem>
               <synopsis>RootPath=типовийшлях (значення визначається при configure)</synopsis>
-              <para>Specifies the path which will be set in the root's session and the {Init,PostLogin,PreSession,PostSession} scripts executed by GDM. This value will be overridden with the value from <filename>/etc/default/login</filename> if it contains "SUROOT=&lt;pathname&gt;". If the <filename>/etc/default/login</filename> file exists, but contains no value for SUROOT, the value as defined in the GDM configuration will be used.</para>
+              <para>
+                Specifies the path which will be set in the root's
+                session and the {Init,PostLogin,PreSession,PostSession} scripts
+                executed by GDM.  This value will be overridden with the value
+                from <filename>/etc/default/login</filename> if it
+                contains "SUROOT=&lt;pathname&gt;".  If the
+                <filename>/etc/default/login</filename> file exists, but
+                contains no value for SUROOT, the value as defined in the GDM
+                configuration will be used.
+              </para>
             </listitem>
           </varlistentry>
           
@@ -851,7 +1522,10 @@ PostSession/
             <term>TimedLoginDelay</term>
             <listitem>
               <synopsis>TimedLoginDelay=30</synopsis>
-              <para>Delay in seconds before the <filename>TimedLogin</filename> user will be logged in. It must be greater then or equal to 10.</para>
+              <para>
+                Delay in seconds before the <filename>TimedLogin</filename>
+                user will be logged in.  It must be greater then or equal to 10.
+              </para>
             </listitem>
           </varlistentry>
           
@@ -939,7 +1613,13 @@ PostSession/
               <synopsis>AllowRemoteRoot=false</synopsis>
               <para>Чи дозволяти користувачу root (адміністратору) входити віддалено через GDM. Якщо треба вимкнути такий тип входу, встановіть значення false. Віддаленим входом є будь-який вхід через XDMCP.</para>
               <para>На системах, що підтримуються PAM, цей параметр не такий корисний, тому що те саме можна зробити за допомогою PAM, та навіть більше.</para>
-              <para>This value will be overridden and set to false if the <filename>/etc/default/login</filename> file exists and contains "CONSOLE=/dev/login", and set to true if the <filename>/etc/default/login</filename> file exists and contains any other value or no value for CONSOLE.</para>
+              <para>
+                This value will be overridden and set to false if the
+                <filename>/etc/default/login</filename> file exists and
+                contains "CONSOLE=/dev/login", and set to true if the
+                <filename>/etc/default/login</filename> file exists and
+                contains any other value or no value for CONSOLE.
+              </para>
             </listitem>
           </varlistentry>
 
@@ -980,7 +1660,18 @@ PostSession/
             <term>PasswordRequired</term>
             <listitem>
               <synopsis>PasswordRequired=false</synopsis>
-              <para>If true, this will cause PAM_DISALLOW_NULL_AUTHTOK to be passed as a flag to pam_authenticate and pam_acct_mgmt, disallowing NULL password. This setting will only take effect if PAM is being used by GDM. This value will be overridden with the value from <filename>/etc/default/login</filename> if it contains "PASSREQ=[YES|NO]". If the <filename>/etc/default/login</filename> file exists, but contains no value for PASSREQ, the value as defined in the GDM configuration will be used.</para>
+              <para>
+                If true, this will cause PAM_DISALLOW_NULL_AUTHTOK to be
+                passed as a flag to pam_authenticate and pam_acct_mgmt,
+                disallowing NULL password.  This setting will only take
+                effect if PAM is being used by GDM.  This value will be
+                overridden with the value from
+                <filename>/etc/default/login</filename> if it contains
+                "PASSREQ=[YES|NO]".  If the
+                <filename>/etc/default/login</filename> file exists, but
+                contains no value for PASSREQ, the value as defined in the GDM
+                configuration will be used.
+              </para>
             </listitem>
           </varlistentry>
           
@@ -1451,7 +2142,13 @@ gdm:.my.domain
             <term>ChooserButtonLogo</term>
             <listitem>
               <synopsis>ChooserButtonLogo=&lt;share&gt;/pixmaps/gnome-logo-large.png</synopsis>
-              <para>Image file to display in the file chooser button in <command>gdmsetup</command>. This key is modified by <command>gdmsetup</command> and should not be manually modified by the user. This only affects the Login Window Preferences (<command>gdmsetup</command>).</para>
+              <para>
+                Image file to display in the file chooser button in
+                <command>gdmsetup</command>.  This key is modified by
+                <command>gdmsetup</command> and should not be manually
+                modified by the user.  This only affects the Login Window
+                Preferences (<command>gdmsetup</command>).
+              </para>
             </listitem>
           </varlistentry>
 
@@ -1764,7 +2461,12 @@ gdm:.my.domain
             <term>Enable</term>
             <listitem>
               <synopsis>Enable=false</synopsis>
-              <para>Setting to true sends debug ouput to the syslog. This can be useful for tracking down problems with GDM. This output tends to be verbose so should not be turned on for general use.</para>
+              <para>
+                Setting to true sends debug ouput to the syslog.  This can be 
+                useful for tracking down problems with GDM.  This output 
+                tends to be verbose so should not be turned on for general
+                use.
+              </para>
             </listitem>
           </varlistentry>
 
@@ -1772,7 +2474,13 @@ gdm:.my.domain
             <term>Жести</term>
             <listitem>
               <synopsis>Gestures=false</synopsis>
-              <para>Setting to true sends debug ouput concerning the accessibility gesture listeners to the syslog. This can be useful for tracking down problems with them not working properly. This output tends to be verbose so should not be turned on for general use.</para>
+              <para>
+                Setting to true sends debug ouput concerning the accessibility
+                gesture listeners to the syslog.  This can be useful for
+                tracking down problems with them not working properly.  This
+                output tends to be verbose so should not be turned on for
+                general use.
+              </para>
             </listitem>
           </varlistentry>
         </variablelist>
@@ -1783,7 +2491,22 @@ gdm:.my.domain
 
         <para>Щоб встановити X-сервери, слід вказати GDM інформацію про встановлені X-сервери. Можна створити довільну кількість різних визначень, кожна повинна мати унікальну назву. Назва <filename>Standard</filename> є обов'язковою. Якщо ви не вказали цей сервер, GDM беруться типові значення сервера 'Standard' та шлях вказаний у <filename>daemon/StandardXServer</filename>. Якщо не визначені інші сервери, використовується <filename>Standard</filename>.</para>
 
-        <para>Servers are defined by sections named <filename>server-</filename> followed by the identifier of this server. This should be a simple ASCII string with no spaces. The GUI configuration program allows users to edit the servers defined in the GDM configuration files but currently does not allow adding or deleting entries. Like normal configuration options, <filename>server-</filename> sections in the <filename>&lt;etc&gt;/gdm/custom.conf</filename> file override values in the <filename>&lt;share&gt;/gdm/defaults.conf</filename> file. In other words, if a <filename>server-Standard</filename> section is defined in <filename>&lt;etc&gt;/gdm/custom.conf</filename>, then that will be used and the section in the <filename>&lt;share&gt;/gdm/defaults.conf</filename> file will be ignored.</para>
+        <para>
+          Servers are defined by sections named <filename>server-</filename>
+          followed by the identifier of this server.  This should be a simple
+          ASCII string with no spaces.  The GUI configuration program allows
+          users to edit the servers defined in the GDM configuration files
+          but currently does not allow adding or deleting entries.  Like
+          normal configuration options, <filename>server-</filename>
+          sections in the <filename>&lt;etc&gt;/gdm/custom.conf</filename>
+          file override values in the
+          <filename>&lt;share&gt;/gdm/defaults.conf</filename> file.  In other
+          words, if a <filename>server-Standard</filename> section is defined
+          in <filename>&lt;etc&gt;/gdm/custom.conf</filename>, then that
+          will be used and the section in the
+          <filename>&lt;share&gt;/gdm/defaults.conf</filename> file will be
+          ignored.
+        </para>
         
         <variablelist>
           <title>[server-Standard]</title>
@@ -1835,7 +2558,15 @@ gdm:.my.domain
 
         <para>Статичні X-сервери - це сервери, які завжди керуються GDM. Наприклад, якщо сервер будь-коли завершується, він перезапускається. Можна мати будь-яку кількість статичних серверів, хоча зазвичай кожен з них підключений до реального дисплею . Наприклад, якщо в комп'ютері є два дисплеї (скажімо дисплей ":0" та дисплей ":1"), тоді у цьому розділі можна вказати, що для кожного екрану має використовуватись окремий екран входу. Кожен ключ у розділі <filename>[servers]</filename> відповідає номеру дисплея, на якому запускається сервер. Наприклад, зазвичай є лише один ключ, це <filename>0</filename>, який відповідає дисплею <filename>:0</filename>.</para>
 
-        <para>The GUI configuration program allows users to edit the static display configuration defined in the GDM configuration files and allows the user to add or delete entries. Like normal configuration options, the <filename>[servers]</filename> section in the <filename>&lt;etc&gt;/gdm/custom.conf</filename> file overrides values in the <filename>&lt;share&gt;/gdm/defaults.conf</filename> file.</para>
+        <para>
+          The GUI configuration program allows users to edit the static
+          display configuration defined in the GDM configuration files 
+          and allows the user to add or delete entries.  Like normal
+          configuration options, the <filename>[servers]</filename>
+          section in the <filename>&lt;etc&gt;/gdm/custom.conf</filename>
+          file overrides values in the
+          <filename>&lt;share&gt;/gdm/defaults.conf</filename> file.
+        </para>
 
         <variablelist>
           <title>[servers]</title>
@@ -1844,15 +2575,48 @@ gdm:.my.domain
             <term>&lt;номер дисплею&gt;</term>
             <listitem>
               <synopsis>0=Standard</synopsis>
-              <para>Control section for local displays. Each line indicates the local display number and the command that needs to be run to start the X server(s).</para>
-
-              <para>The command can either be a path to an X executable, or a name of one of the server definitions. This can be followed by some arguments that should be passed to the X server when executed. The gdm daemon doesn't enforce the numbers to be in order or for them to be "packed". They keyword "inactive" can be used instead of a command to specify that the display should be not managed. This can be used in the <filename>&lt;etc&gt;/gdm/custom.conf</filename> to turn off a display that is defined in the <filename>&lt;share&gt;/gdm/defaults.conf</filename> file.</para>
+              <para>
+                Control section for local displays. Each line indicates
+                the local display number and the command that needs to
+                be run to start the X server(s).
+              </para>
+
+              <para>
+                The command can either be a path to an X executable, or a name
+                of one of the server definitions.  This can be followed by some
+                arguments that should be passed to the X server when executed.
+                The gdm daemon doesn't enforce the numbers to be in order or
+                for them to be "packed".  They keyword
+                "inactive" can be used instead of a command to
+                specify that the display should be not managed.  This can be
+                used in the
+                <filename>&lt;etc&gt;/gdm/custom.conf</filename> to turn
+                off a display that is defined in the
+                <filename>&lt;share&gt;/gdm/defaults.conf</filename> file.
+              </para>
               
-              <para>GDM will splice "<filename>-auth &lt;ServAuthDir&gt;/:n.Xauth :n</filename>", where n is the display number. Inside the command line before all other arguments before running the X server.</para>
-
-              <para>On some systems it is necessary for GDM to know on which virtual consoles to run the X server. In this case, (if running XFree86) add "vt7" to the command line, for example, to run on virtual console 7. However on Linux and FreeBSD this is normally done automatically if the <filename>VTAllocation</filename> key is set.</para>
-
-              <para>Normally you do not need to add a <filename>-nolisten tcp</filename> flag as this is added automatically for local X servers when the <filename>DisallowTCP</filename> option is set.</para>
+              <para>
+                GDM will splice "<filename>-auth
+                &lt;ServAuthDir&gt;/:n.Xauth :n</filename>", where n is
+                the display number.  Inside the command line before all
+                other arguments before running the X server.
+              </para>
+
+              <para>
+                On some systems it is necessary for GDM to know on which
+                virtual consoles to run the X server.  In this case,
+                (if running XFree86) add "vt7" to the command line,
+                for example, to run on virtual console 7.  However on Linux and
+                FreeBSD this is normally done automatically if the
+                <filename>VTAllocation</filename> key is set.
+              </para>
+
+              <para>
+                Normally you do not need to add a
+                <filename>-nolisten tcp</filename> flag as this is added
+                automatically for local X servers when the
+                <filename>DisallowTCP</filename> option is set.
+              </para>
             </listitem>
           </varlistentry>
           
@@ -1860,7 +2624,15 @@ gdm:.my.domain
             <term>priority</term>
             <listitem>
               <synopsis>priority=0</synopsis>
-              <para>Indicates that the X server should be started at a different process priority. Values can be any integer value accepted by the setpriority C library function (normally between -20 and 20) with 0 being the default. For highly interactive applications, -5 yields good responsiveness. The default value is 0 and the setpriority function is not called if the value is 0.</para>
+              <para>
+                Indicates that the X server should be started at a
+                different process priority.  Values can be any integer
+                value accepted by the setpriority C library function
+                (normally between -20 and 20) with 0 being the default.
+                For highly interactive applications, -5 yields good
+                responsiveness.  The default value is 0 and the 
+                setpriority function is not called if the value is 0.
+              </para>
             </listitem>
           </varlistentry>
         </variablelist>
@@ -1870,11 +2642,38 @@ gdm:.my.domain
     <sect2 id="userconfig">
       <title>Параметри специфічні для користувача</title>
 
-      <para>There are some per user configuration settings that control how GDM behaves. GDM is picky about the file ownership and permissions of the user files it will access, and will ignore files if they are not owned by the user or files that have group/world write permission. It will also ignore the user if the user's $HOME directory is not owned by the user or if the user's $HOME directory has group/world write permission. files must also be smaller than the <filename>UserMaxFile</filename> value as defined in the GDM configuration. If it seems that GDM is not properly accessing user configuration settings, the problem is most likely caused by one of these checks failing.</para>
-
-      <para>First there is the <filename>~/.dmrc</filename> file. In theory this file should be shared between GDM and KDM, so users only have to configure things once. This is a standard <filename>.ini</filename> style configuration file. It has one section called <filename>[Desktop]</filename> which has two keys: <filename>Session</filename> and <filename>Language</filename>.</para>
-
-      <para>The <filename>Session</filename> key specifies the basename of the session <filename>.desktop</filename> file that the user wishes to normally use (without the <filename>.desktop</filename> extension, in other words). The <filename>Language</filename> key specifies the language that the user wishes to use by default. If either of these keys is missing, the system default is used. The file would normally look as follows:</para>
+      <para>
+        There are some per user configuration settings that control how GDM
+        behaves.  GDM is picky about the file ownership and permissions of 
+        the user files it will access, and will ignore files if they are not
+        owned by the user or files that have group/world write permission.
+        It will also ignore the user if the user's $HOME directory is not
+        owned by the user or if the user's $HOME directory has group/world
+        write permission.  files must also be smaller than the
+        <filename>UserMaxFile</filename> value as defined in the GDM
+        configuration.  If it seems that GDM is not properly accessing 
+        user configuration settings, the problem is most likely 
+        caused by one of these checks failing.
+      </para>
+
+      <para>
+        First there is the <filename>~/.dmrc</filename> file.  In
+        theory this file should be shared between GDM and KDM, so users only
+        have to configure things once.  This is a standard
+        <filename>.ini</filename> style configuration file.  It has one section
+        called <filename>[Desktop]</filename> which has two keys:
+        <filename>Session</filename> and <filename>Language</filename>.
+      </para>
+
+      <para>
+        The <filename>Session</filename> key specifies the basename of the
+        session <filename>.desktop</filename> file that the user wishes to
+        normally use (without the <filename>.desktop</filename> extension, in
+        other words).  The <filename>Language</filename> key specifies the
+        language that the user wishes to use by default.  If either of these
+        keys is missing, the system default is used.  The file would normally
+        look as follows:
+      </para>
 
 <screen>
 [Desktop]
@@ -1882,11 +2681,34 @@ Session=gnome
 Language=cs_CZ.UTF-8
 </screen>
 
-      <para>Normally GDM will write this file when the user logs in for the first time, and rewrite it if the user chooses to change their default values on a subsequent login.</para>
-
-      <para>If the GDM Face Browser is turned, then the file <filename>$HOME/.face</filename> is accessed. This file should be a standard image that GTK+ can read, such as PNG or JPEG. It also must be smaller than the <filename>MaxIconWidth</filename> and <filename>MaxIconHeight</filename> values defined in the GDM configuration or it will be ignored. Users can run the <command>gdmphotosetup</command> program to specify a face image and it will copy the file to the <filename>$HOME/.face</filename> location and scale it so its longest dimension is not larger than the <filename>MaxIconWidth</filename> or <filename>MaxIconHeight</filename> values. <command>gdmphotosetup</command> takes care to not change the aspect ratio of the image.</para>
-
-      <para>Face images can also be placed in the global face directory, which is specified by the <filename>GlobalFaceDir</filename> configuration option ( normally <filename>&lt;share&gt;/pixmaps/faces/</filename>) and the filename should be the name of the user, optionally with a <filename>.png</filename>, <filename>.jpg</filename>, etc. appended.</para>
+      <para>
+        Normally GDM will write this file when the user logs in for the first
+        time, and rewrite it if the user chooses to change their default values
+        on a subsequent login. 
+      </para>
+
+      <para>
+        If the GDM Face Browser is turned, then the file
+        <filename>$HOME/.face</filename> is accessed.  This file should be a 
+        standard image that GTK+ can read, such as PNG or JPEG.  It also must
+        be smaller than the <filename>MaxIconWidth</filename> and 
+        <filename>MaxIconHeight</filename> values defined in the GDM
+        configuration or it will be ignored.  Users can run the
+        <command>gdmphotosetup</command> program to specify a face image
+        and it will copy the file to the <filename>$HOME/.face</filename>
+        location and scale it so its longest dimension is not larger than the 
+        <filename>MaxIconWidth</filename> or <filename>MaxIconHeight</filename>
+        values.  <command>gdmphotosetup</command> takes care to not change
+        the aspect ratio of the image.
+      </para>
+
+      <para>
+        Face images can also be placed in the global face directory, which is
+        specified by the <filename>GlobalFaceDir</filename> configuration 
+        option ( normally <filename>&lt;share&gt;/pixmaps/faces/</filename>)
+        and the filename should be the name of the user, optionally with a
+        <filename>.png</filename>, <filename>.jpg</filename>, etc. appended.
+      </para>
     </sect2>
   </sect1>
 
@@ -1898,9 +2720,32 @@ Language=cs_CZ.UTF-8
     <sect2 id="commands">
       <title>Команди</title>
 
-      <para>To stop GDM, you can either send the TERM signal to the main daemon or run the <command>gdm-stop</command> command which is in the <filename>&lt;sbin&gt;/</filename> directory. To restart GDM, you can either send the HUP signal to the main daemon or run the <command>gdm-restart</command> command which is also in the <filename>&lt;sbin&gt;/</filename> directory. To restart GDM but only after all the users have logged out, you can either send the USR1 signal to the main daemon or run the <command>gdm-safe-restart</command> command which is in the <filename>&lt;sbin&gt;/</filename> directory as well.</para>
-
-      <para>The <command>gdmflexiserver</command> command can be used to start new flexible (on demand) displays if your system supports virtual terminals. This command will normally lock the current session with a screensaver so that the user can safely walk away from the computer and let someone else log in. If more that two flexible displays have started <command>gdmflexiserver</command> will display a pop-up dialog allowing the user to select which session to continue. The user will normally have to enter a password to return to the session. On session exit the system will return to the previous virtual terminal. Run <command>gdmflexiserver --help</command> to get a listing of possible options.</para>
+      <para>
+        To stop GDM, you can either send the TERM signal to the main daemon or
+        run the <command>gdm-stop</command> command which is in the
+        <filename>&lt;sbin&gt;/</filename> directory.  To restart GDM, you can
+        either send the HUP signal to the main daemon or run the
+        <command>gdm-restart</command> command which is also in the
+        <filename>&lt;sbin&gt;/</filename> directory.  To restart GDM but only
+        after all the users have logged out, you can either send the USR1
+        signal to the main daemon or run the
+        <command>gdm-safe-restart</command> command which is in the
+        <filename>&lt;sbin&gt;/</filename> directory as well.
+      </para>
+
+      <para>
+        The <command>gdmflexiserver</command> command can be used to start
+        new flexible (on demand) displays if your system supports virtual
+        terminals.  This command will normally lock the current session with a
+        screensaver so that the user can safely walk away from the computer and
+        let someone else log in.  If more that two flexible displays have 
+        started <command>gdmflexiserver</command> will display a pop-up dialog
+        allowing the user to select which session to continue.  The user will
+        normally have to enter a password to return to the session.  On session
+        exit the system will return to the previous virtual terminal.  Run
+        <command>gdmflexiserver --help</command> to get a listing of possible
+        options.  
+      </para>
     </sect2>
 
     <sect2 id="fifoprot">
@@ -1914,7 +2759,15 @@ Language=cs_CZ.UTF-8
     <sect2 id="socketprot">
       <title>Протокол роботи з сокетом</title>
 
-      <para>GDM provides a unix domain socket for communication at <filename>/tmp/.gdm_socket</filename>. Using this you can check if GDM is running, the version of the daemon, the current displays that are running and who is logged in on them, and if GDM supports it on your operating system, also the virtual terminals of all the console logins. The <command>gdmflexiserver</command> command uses this protocol, for example, to launch flexible (on-demand) displays.</para>
+      <para>
+        GDM provides a unix domain socket for communication at
+        <filename>/tmp/.gdm_socket</filename>.  Using this you can check if
+        GDM is running, the version of the daemon, the current displays that
+        are running and who is logged in on them, and if GDM supports it on
+        your operating system, also the virtual terminals of all the console
+        logins.  The <command>gdmflexiserver</command> command uses this
+        protocol, for example, to launch flexible (on-demand) displays.
+      </para>
 
       <para>gdmflexiserver приймає наступні команди у командному рядку --command:</para>
 
@@ -2527,12 +3380,28 @@ Answers:
     <sect2 id="bindir_binaries">
       <title>Команди користувача GDM</title>
 
-      <para>The GDM package provides the following different commands in <filename>bindir</filename> intended to be used by the end-user:</para>
+      <para>
+        The GDM package provides the following different commands in
+        <filename>bindir</filename> intended to be used by the end-user:
+      </para>
 
       <sect3 id="gdmxnestchoosercommandline">
-        <title><command>gdmXnestchooser</command> and <command>gdmXnest</command> Command Line Options</title>
+        <title><command>gdmXnestchooser</command> and
+               <command>gdmXnest</command> Command Line Options</title>
 
-        <para>The <command>gdmXnestchooser</command> command automatically gets the correct display number, sets up access, and runs <command>Xnest</command> with -indirect localhost. This way you get an XDMCP chooser provided by your computer. You can also supply as an argument the hostname whose chooser should be displayed, so <command>gdmXnestchooser somehost</command> will run the XDMCP chooser from host <command>somehost</command> inside an Xnest session. You can make this command do a direct query instead by passing the <command>-d</command> option as well. In addition to the following options, this command also supports standard GNOME options.</para>
+        <para>
+          The <command>gdmXnestchooser</command> command automatically gets
+          the correct display number, sets up access, and runs
+          <command>Xnest</command> with -indirect localhost.  This way you
+          get an XDMCP chooser provided by your computer. You can also supply
+          as an argument the hostname whose chooser should be displayed, so
+          <command>gdmXnestchooser somehost</command> will run the XDMCP
+          chooser from host <command>somehost</command> inside an Xnest
+          session.  You can make this command do a direct query instead by
+          passing the <command>-d</command> option as well.  In addition to
+          the following options, this command also supports standard GNOME
+          options.
+        </para>
 
         <variablelist>
         <title><command>gdmXnestchooser</command> Command Line Options</title>
@@ -2591,15 +3460,46 @@ Answers:
       <sect3 id="gdmflexichoosercommandline">
         <title><command>gdmflexichooser</command> Command Line Options</title>
 
-        <para>The <command>gdmflexiserver</command> command provides three features. It can be used to run flexible (on demand) X displays, to run a flexible display via Xnest, and to send commands to the GDM daemon process.</para>
+        <para>
+         The <command>gdmflexiserver</command> command provides three 
+         features.  It can be used to run flexible (on demand) X displays,
+         to run a flexible display via Xnest, and to send commands to the
+         GDM daemon process.
+        </para>
 
-        <para>Starting a flexible X display will normally lock the current session with a screensaver and will redisplay the GDM login screen so a second user can log in. This feature is only available on systems that support virtual terminals and have them enabled. This feature is useful if you are logged in as user A, and user B wants to log in quickly but user A does not wish to log out. The X server takes care of the virtual terminal switching so it works transparently. If there is more than one running display defined with flexible=true, then the user is shown a dialog that displays the currently running sessions. The user can then pick which session to continue and will normally have to enter the password to unlock the screen.</para>
+        <para>
+         Starting a flexible X display will normally lock the current session
+         with a screensaver and will redisplay the GDM login screen so a second
+         user can log in.   This feature is only available on systems that
+         support virtual terminals and have them enabled.  This feature is
+         useful if you are logged in as user A, and user B wants to log in
+         quickly but user A does not wish to log out.  The X server takes
+         care of the virtual terminal switching so it works transparently.
+         If there is more than one running display defined with flexible=true,
+         then the user is shown a dialog that displays the currently running
+         sessions.  The user can then pick which session to continue and will
+         normally have to enter the password to unlock the screen. 
+        </para>
 
-        <para>Flexible displays started via Xnest works on systems that do not support virtual terminals. This option starts a flexible display in a window in the current session. This does not lock the current session, so is not as secure as a flexible server started via virtual terminals.</para>
+        <para>
+         Flexible displays started via Xnest works on systems that do not 
+         support virtual terminals.  This option starts a flexible display
+         in a window in the current session.  This does not lock the current
+         session, so is not as secure as a flexible server started via
+         virtual terminals.
+        </para>
 
-        <para>The <command>gdmflexiserver --command</command> option provides a way to send commands to the GDM daemon and can be used to debug problems or to change the GDM configuration.</para>
+        <para>
+         The <command>gdmflexiserver --command</command> option provides a way
+         to send commands to the GDM daemon and can be used to debug problems
+         or to change the GDM configuration.
+        </para>
 
-        <para>In addition to the following options, <command>gdmflexiserver</command> also supports standard GNOME options.</para>
+        <para>
+         In addition to the following options,
+         <command>gdmflexiserver</command> also supports standard GNOME
+         options.
+        </para>
 
         <variablelist>
         <title><command>gdmflexichooser</command> Command Line Options</title>
@@ -2614,7 +3514,9 @@ Answers:
           <varlistentry>
             <term>-n, --xnest</term>
             <listitem>
-              <para>Start a flexible X display in Xnest mode</para>
+              <para>
+                Start a flexible X display in Xnest mode
+              </para>
             </listitem>
           </varlistentry>
 
@@ -2628,7 +3530,10 @@ Answers:
           <varlistentry>
             <term>-d, --debug</term>
             <listitem>
-              <para>Turns on debugging output which gets sent to syslog. Same as turning on debug in the configuration file.</para>
+              <para>
+                Turns on debugging output which gets sent to syslog.  Same as
+                turning on debug in the configuration file.
+              </para>
             </listitem>
           </varlistentry>
 
@@ -2651,9 +3556,28 @@ Answers:
       <sect3 id="gdmdynamiccommandline">
         <title><command>gdmdynamic</command> Command Line Options</title>
 
-        <para>The <command>gdmdynamic</command> command which creates, runs, and removes displays (X servers) on demand.</para>
+        <para>
+         The <command>gdmdynamic</command> command which creates, runs, and
+         removes displays (X servers) on demand.
+        </para>
 
-        <para>Some environments need the ability to tell GDM to create and manage new displays on the fly, where it is not possible to list the possible displays in GDM configuration files. The <command>gdmdynamic</command> command can be used to create a new display on a particular display number, run all newly created displays, or remove a display. The <command>gdmdynamic</command> command can also be used to list all attached displays, or only attached displays that match a pattern. This program is designed to manage multiple simultaneous requests and works to avoid flooding the daemon with requests. If the socket connection is busy, it will sleep and retry a certain number of times that can be tuned with the <command>-t</command> and <command>-s</command> arguments. <command>gdmdynamic</command> returns 1 on normal failure, and returns 2 if it is unable to connect to the daemon. Callers can choose to call again if a return code of 2 is received.</para>
+        <para>
+        Some environments need the ability to tell GDM to create and manage new
+        displays on the fly, where it is not possible to list the possible
+        displays in GDM configuration files. The <command>gdmdynamic</command>
+        command can be used to create a new display on a particular display
+        number, run all newly created displays, or remove a display. The
+        <command>gdmdynamic</command> command can also be used to list all
+        attached displays, or only attached displays that match a pattern.
+        This program is designed to manage multiple simultaneous requests and
+        works to avoid flooding the daemon with requests.  If the socket
+        connection is busy, it will sleep and retry a certain number of times
+        that can be tuned with the <command>-t</command> and
+        <command>-s</command> arguments.  <command>gdmdynamic</command>
+        returns 1 on normal failure, and returns 2 if it is unable to 
+        connect to the daemon.  Callers can choose to call again if a
+        return code of 2 is received.
+        </para>
 
         <variablelist>
           <title><command>gdmdynamic</command> Command Line Options</title>
@@ -2734,34 +3658,69 @@ Answers:
       <sect3 id="gdmphotosetupcommandline">
         <title><command>gdmphotosetup</command> Command Line Options</title>
 
-        <para>Allows the user to select an image that will be used as the user's photo by GDM's face browser, if enabled by GDM. The selected file is stored as <filename>~/.face</filename>. This command accepts standard GNOME options.</para>
+        <para>
+         Allows the user to select an image that will be used as the user's
+         photo by GDM's face browser, if enabled by GDM.  The selected file
+         is stored as <filename>~/.face</filename>.  This command accepts
+         standard GNOME options.
+        </para>
       </sect3>
 
       <sect3 id="gdmthemetestercommandline">
         <title><command>gdmthemetester</command> Command Line Options</title>
 
-        <para><command>gdmthemetester</command> takes two parameters. The first parameter specifies the environment and the second parameter specifies the path name or the name of a theme to view. This is a tool for viewing a theme outside of GDM. It is useful for testing or viewing themes. <command>gdmthemetester</command> requires that the system support <command>gdmXnest</command>. Note that themes can display differently depending on the theme's "Show mode". <command>gdmthemetester</command> allows viewing the themes in different modes via the environment option. Valid environment values and their meanings follow: <screen>
+        <para>
+         <command>gdmthemetester</command> takes two parameters.  The first
+         parameter specifies the environment and the second parameter
+         specifies the path name or the name of a theme to view.
+
+         This is a tool for viewing a theme outside of GDM.  It is useful for
+         testing or viewing themes.  <command>gdmthemetester</command> requires
+         that the system support <command>gdmXnest</command>.
+
+         Note that themes can display differently depending on the theme's
+         "Show mode".  <command>gdmthemetester</command> allows
+         viewing the themes in different modes via the environment option.
+         Valid environment values and their meanings follow:
+
+<screen>
 console       - In console mode.
 console-timed - In console non-flexi mode.
 flexi         - In flexi mode.
 xdmcp         - In remote (XDMCP) mode.
 remote-flexi  - In remote (XDMCP) &amp; flexi mode.
-</screen></para>
+</screen>
+        </para>
       </sect3>
     </sect2>
 
     <sect2 id="sbindir_binaries">
       <title>GDM Root User Commands</title>
 
-      <para>The GDM package provides the following different commands in <filename>sbindir</filename> intended to be used by the root user:</para>
+      <para>
+        The GDM package provides the following different commands in
+        <filename>sbindir</filename> intended to be used by the root user:
+      </para>
 
       <sect3 id="gdmcommandline">
-        <title><command>gdm</command> and <command>gdm-binary</command> Command Line Options</title>
+        <title><command>gdm</command> and <command>gdm-binary</command>
+               Command Line Options</title>
 
-        <para>The <command>gdm</command> command is really just a script which runs the <command>gdm-binary</command>, passing along any options. Before launching <command>gdm-binary</command>, the gdm wrapper script will source the <filename>&lt;etc&gt;/profile</filename> file to set the standard system environment variables. In order to better support internationalization, it will also set the LC_MESSAGES environment variable to LANG if neither LC_MESSAGES or LC_ALL are set. If you really need to set some additional environment before launching GDM, you can do so in this script.</para>
+        <para>
+          The <command>gdm</command> command is really just a script which
+          runs the <command>gdm-binary</command>, passing along any options.
+          Before launching <command>gdm-binary</command>, the gdm wrapper script
+          will source the <filename>&lt;etc&gt;/profile</filename> file to set 
+          the standard system environment variables.  In order to better support
+          internationalization, it will also set the LC_MESSAGES environment
+          variable to LANG if neither LC_MESSAGES or LC_ALL are set.  If you
+          really need to set some additional environment before launching GDM,
+          you can do so in this script.
+        </para>
 
         <variablelist>
-          <title><command>gdm</command> and <command>gdm-binary</command> Command Line Options</title>
+          <title><command>gdm</command> and <command>gdm-binary</command>
+                 Command Line Options</title>
 
           <varlistentry>
             <term>--help</term>
@@ -2773,7 +3732,12 @@ remote-flexi  - In remote (XDMCP) &amp; flexi mode.
           <varlistentry>
             <term>--nodaemon</term>
             <listitem>
-              <para>If this option is specified, then GDM does not fork into the background when run. You can also use a single-dash version, "-nodaemon" for compatibility with other display managers.</para>
+              <para>
+                If this option is specified, then GDM does not fork into the
+                background when run. You can also use a single-dash version,
+                "-nodaemon" for compatibility with other display
+                managers.
+              </para>
             </listitem>
           </varlistentry>
 
@@ -2817,43 +3781,80 @@ remote-flexi  - In remote (XDMCP) &amp; flexi mode.
       <sect3 id="gdmsetupcommandline">
         <title><command>gdmsetup</command> Command Line Options</title>
 
-        <para><command>gdmsetup</command> runs a graphical application for modifying the GDM configuration file. Normally on systems that support the PAM userhelper, this is setup such that when you run <command>gdmsetup</command> as an ordinary user, it will first ask you for your root password before starting. Otherwise, this application may only be run as root. This application supports standard GNOME options.</para>
+        <para>
+         <command>gdmsetup</command> runs a graphical application for modifying
+         the GDM configuration file.  Normally on systems that support
+         the PAM userhelper, this is setup such that when you run
+         <command>gdmsetup</command> as an ordinary user, it will first
+         ask you for your root password before starting.  Otherwise, this
+         application may only be run as root.  This application supports
+         standard GNOME options.
+        </para>
       </sect3>
 
       <sect3 id="gdmrestartcommandline">
         <title><command>gdm-restart</command> Command Line Options</title>
 
-        <para><command>gdm-restart</command> stops and restarts GDM by sending the GDM daemon a HUP signal. This command will immediately terminate all sessions and log out users currently logged in with GDM.</para>
+        <para>
+          <command>gdm-restart</command> stops and restarts GDM by sending
+          the GDM daemon a HUP signal.  This command will immediately terminate
+          all sessions and log out users currently logged in with GDM.
+        </para>
       </sect3>
 
       <sect3 id="gdmsaferestartcommandline">
         <title><command>gdm-safe-restart</command> Command Line Options</title>
   
-        <para><command>gdm-safe-restart</command> stops and restarts GDM by sending the GDM daemon a USR1 signal. GDM will be restarted as soon as all users log out.</para>
+        <para>
+          <command>gdm-safe-restart</command> stops and restarts GDM by
+          sending the GDM daemon a USR1 signal.  GDM will be restarted as soon
+          as all users log out.
+        </para>
       </sect3>
 
       <sect3 id="gdmstopcommandline">
         <title><command>gdm-stop</command> Command Line Options</title>
 
-        <para><command>gdm-stop</command> stops GDM by sending the GDM daemon a TERM signal.</para>
+        <para>
+          <command>gdm-stop</command> stops GDM by sending the GDM daemon
+          a TERM signal. 
+        </para>
       </sect3>
     </sect2>
 
     <sect2 id="libexecdir_binaries">
       <title>Внутрішні команди GDM</title>
 
-      <para>The GDM package provides the following different commands in <filename>libexecdir</filename> intended to be used by the gdm daemon process.</para>
+      <para>
+        The GDM package provides the following different commands in
+        <filename>libexecdir</filename> intended to be used by the gdm
+        daemon process.
+      </para>
 
       <sect3 id="gdmgreeterlogincommandline">
-        <title><command>gdmchooser</command> and <command>gdmlogin</command> Command Line Options</title>
+        <title><command>gdmchooser</command> and <command>gdmlogin</command>
+               Command Line Options</title>
 
-        <para>The <command>gdmgreeter</command> and <command>gdmlogin</command> are two different login applications, either can be used by GDM. <command>gdmgreeter</command> is themeable with GDM themes while <command>gdmlogin</command> is themable with GTK+ themes. These applications are normally executed by the GDM daemon. Both commands support standard GNOME options.</para>
+        <para>
+          The <command>gdmgreeter</command> and <command>gdmlogin</command>
+          are two different login applications, either can be used by GDM.  
+          <command>gdmgreeter</command> is themeable with GDM themes while
+          <command>gdmlogin</command> is themable with GTK+ themes.  These
+          applications are normally executed by the GDM daemon.  Both commands
+          support standard GNOME options. 
+        </para>
       </sect3>
 
       <sect3 id="gdmchoosercommandline">
         <title><command>gdmchooser</command> Command Line Options</title>
 
-        <para>The <command>gdmchooser</command> is the XDMCP chooser application. The <command>gdmchooser</command> is normally executed by the GDM daemon. It supports the following options for XDM compatibility. This command supports standard GNOME options and is found in support standard GNOME options.</para>
+        <para>
+          The <command>gdmchooser</command> is the XDMCP chooser application.  
+          The <command>gdmchooser</command> is normally executed by the GDM
+          daemon.  It supports the following options for XDM compatibility.
+          This command supports standard GNOME options and is found in
+          support standard GNOME options.
+        </para>
 
         <variablelist>
           <title><command>gdmchooser</command> Command Line Options</title>
@@ -2914,7 +3915,19 @@ Screenshot=screenshot.png
 
       <para>Назва, опис, автор та авторські права можна перекладати як і у інших файлах типу <filename>.desktop</filename>. Усі файли вказані файли мають у каталозі з темами. Файл, на який вказує поле Screenshot повинен бутизнімком екрану теми з розмірами 200x150 (він може бути відсутній, але якщо він є - це краще для користувача). У полі Greeter вказується файл XML, який містить опис теми. Опис буде згаданий далі.</para>
 
-      <para>Once you have theme ready and installed you can test it with the installed <command>gdmthemetester</command> script. This script assumes that the X server supports Xnest. This command takes two arguments, first the environment that should be used. This is one of console, console-timed, flexi, remote-flexi, xdmcp. Where console is a standard console login, console-timed is a console login with a timed login going on, flexi is for any local flexible display, remote-flexi is for flexi displays that are not local (such as an Xnest flexiserver run from a remote display) and xdmcp is for remote XDMCP connections. The second argument is the theme name. So for example to test how things look in the XDMCP mode with the circles theme you would run:</para>
+      <para>
+        Once you have theme ready and installed you can test it with the
+        installed <command>gdmthemetester</command> script.  This script
+        assumes that the X server supports Xnest.  This command takes two
+        arguments, first the environment that should be used.  This is one of
+        console, console-timed, flexi, remote-flexi, xdmcp.  Where console is a
+        standard console login, console-timed is a console login with a timed
+        login going on, flexi is for any local flexible display, remote-flexi
+        is for flexi displays that are not local (such as an Xnest flexiserver
+        run from a remote display) and xdmcp is for remote XDMCP connections.
+        The second argument is the theme name.  So for example to test how
+        things look in the XDMCP mode with the circles theme you would run:
+      </para>
 
 <screen>
 <command>gdmthemetester xdmcp circles</command>
@@ -2922,10 +3935,17 @@ Screenshot=screenshot.png
 
       <para>Перевірте тему в усіх варіантах оточення, та перевірте вигляд попередження про натискання caps lock. Також було б добре зробити знімок екрану, просто зробіть знімок екрану вікна Xnest. це можна зробити у GNOME, якщо передати фоку вводу вікну Xnest та натиснути Alt-PrintScreen.</para>
 
-      <para>Once you have all this done, then make a tarball that contains the directory name (so that you could just untar it in the <filename>&lt;share&gt;/gdm/themes</filename> directory). And this is the tarball you distribute and people can install from the graphical configuration application. You can do this with the commands: <screen>
+      <para>
+        Once you have all this done, then make a tarball that contains the
+        directory name (so that you could just untar it in the
+        <filename>&lt;share&gt;/gdm/themes</filename> directory).  And this is
+        the tarball you distribute and people can install from the graphical
+        configuration application.  You can do this with the commands:
+<screen>
 cd &lt;share&gt;/gdm/themes
 tar czvf &lt;theme_name&gt;.tar.gz &lt;theme_name&gt;/
-</screen></para>
+</screen>
+      </para>
     </sect2>
 
     <sect2 id="descofthemeformat">
@@ -2934,7 +3954,12 @@ tar czvf &lt;theme_name&gt;.tar.gz &lt;theme_name&gt;/
       <sect3 id="greetertag">
         <title>greeter tag</title>
 
-          <para>The GDM theme format is specified in XML format contained within a &lt;greeter&gt; tag. You may specify a GTK+ theme to be used with this theme by using the gtk-theme element in the greeter tag as in the following example.</para>
+          <para>
+            The GDM theme format is specified in XML format contained
+            within a &lt;greeter&gt; tag.  You may specify a GTK+ theme to
+            be used with this theme by using the gtk-theme element in the
+            greeter tag as in the following example.
+          </para>
 
 <screen>
 &lt;?xml version="1.0" encoding="UTF-8"?&gt;
@@ -2944,17 +3969,33 @@ tar czvf &lt;theme_name&gt;.tar.gz &lt;theme_name&gt;/
 &lt;/greeter&gt;
 </screen>
 
-          <para>Contained within the greeter tag can be the nodes described in the next sections of this document. Some of these nodes are containers (box nodes, rect item nodes) which can be used to organize how to display the nodes that the user sees and interacts with (such as button, pixmap and entry item nodes).</para>
+          <para>
+            Contained within the greeter tag can be the nodes described
+            in the next sections of this document.  Some of these nodes are
+            containers (box nodes, rect item nodes) which can be used to
+            organize how to display the nodes that the user sees and interacts
+            with (such as button, pixmap and entry item nodes).
+          </para>
       </sect3>
 
       <sect3 id="boxnodes">
         <title>Box Nodes</title>
 
-        <para>Box nodes are container nodes for item nodes. Box nodes are specified as follows: <screen>
+        <para>
+          Box nodes are container nodes for item nodes.  Box nodes are
+          specified as follows:
+<screen>
 &lt;box orientation="alignment" min-width="num"
 xpadding="num" ypadding="num" spacing="num"
 homogeneous="bool"&gt;
-</screen> Where "num" means number and bool means either "true" or "false" The alignment value can be either "horizontal" or "vertical". If you leave any property off it will default to zero or "false" in case of "homogeneous" and "vertical" for the orientation.</para>
+</screen>
+          Where "num" means number and bool means either
+          "true" or "false" The alignment value can be
+          either "horizontal" or "vertical".  If you leave
+          any property off it will default to zero or "false" in
+          case of "homogeneous" and "vertical" for the
+          orientation.
+        </para>
 
         <para>Якщо контейнер є однорідним, тоді дочірні елементи займають однаковий простір.</para>
 
@@ -2964,9 +4005,16 @@ homogeneous="bool"&gt;
       <sect3 id="fixednodes">
         <title>Вузли Fixed</title>
 
-        <para>Fixed is a container that has its children scattered about laid out with precise coordinates. The size of this container is the biggest rectangle that contains all the children. Fixed has no extra properties and so you just use: <screen>
+        <para>
+          Fixed is a container that has its children scattered about
+          laid out with precise coordinates.  The size of this container
+          is the biggest rectangle that contains all the children.  Fixed
+          has no extra properties and so you just use:
+<screen>
 &lt;fixed&gt;
-</screen> Then you put other items with proper position nodes inside this.</para>
+</screen>
+          Then you put other items with proper position nodes inside this.
+        </para>
 
         <para>Вузол "toplevel" подібний до вузла fixed.</para>
       </sect3>
@@ -2980,7 +4028,14 @@ homogeneous="bool"&gt;
           <varlistentry>
             <term>button</term>
             <listitem>
-              <para>A button field. This field uses a GTK+ button. It is also possible to make a "rect" item act like a button by setting its button element to true. However it is better to use GTK+ buttons in GDM themes since these are accessible to users with disabilities. Also, GTK+ buttons can be themed. This feature is supported in GDM 2.14.6 and later.</para>
+              <para>
+                A button field.  This field uses a GTK+ button.  It is also
+                possible to make a "rect" item act like a button by setting
+                its button element to true.  However it is better to use
+                GTK+ buttons in GDM themes since these are accessible to
+                users with disabilities.  Also, GTK+ buttons can be
+                themed.  This feature is supported in GDM 2.14.6 and later.
+              </para>
             </listitem>
           </varlistentry>
 
@@ -3001,7 +4056,10 @@ homogeneous="bool"&gt;
           <varlistentry>
             <term>list</term>
             <listitem>
-              <para>A face browser widget. Only useful if the face browser is enabled via the configuration.</para>
+              <para>
+                 A face browser widget.  Only useful if the face browser is
+                 enabled via the configuration.
+              </para>
             </listitem>
           </varlistentry>
 
@@ -3027,9 +4085,16 @@ homogeneous="bool"&gt;
           </varlistentry>
         </variablelist>
 
-        <para>For example: <screen>
+        <para>
+          For example: 
+<screen>
 &lt;item type="label"&gt;
-</screen> Items can specify ID values which gives them a specific look and feel or formatting. Furthermore you can customize the login process by adding custom widgets with custom id's for some items (currently only the list item)</para>
+</screen>
+          Items can specify ID values which gives them a specific look and feel
+          or formatting.  Furthermore you can customize the login process by
+          adding custom widgets with custom id's for some items (currently only
+          the list item)
+        </para>
 
         <para>Елементи вузлів можуть мати такі значення ідентифікаторів:</para>
 
@@ -3062,35 +4127,52 @@ homogeneous="bool"&gt;
           <varlistentry>
             <term>clock</term>
             <listitem>
-              <para>Label that displays the date and time.</para>
+              <para>
+                Label that displays the date and time.
+              </para>
             </listitem>
           </varlistentry>
 
           <varlistentry>
             <term>pam-prompt</term>
             <listitem>
-              <para>Label that displays the PAM prompt. This is the prompt that PAM uses to ask for username, password, etc...</para>
+              <para>
+                Label that displays the PAM prompt.  This is the prompt that PAM
+                uses to ask for username, password, etc...
+              </para>
             </listitem>
           </varlistentry>
 
           <varlistentry>
             <term>pam-error</term>
             <listitem>
-              <para>Label that displayst PAM/GDM error messages. Such as when user can't log in.</para>
+              <para>
+                Label that displayst PAM/GDM error messages.  Such as when user
+                can't log in.
+              </para>
             </listitem>
           </varlistentry>
 
           <varlistentry>
             <term>pam-error-logo</term>
             <listitem>
-              <para>An image that will be displayed only when a pam-error message is being displayed. This is useful for displaying an "Attention" icon, for example. This feature is supported in GDM 2.14.6 and later.</para>
+              <para>
+                An image that will be displayed only when a pam-error message
+                is being displayed.  This is useful for displaying an
+                "Attention" icon, for example.  This feature is
+		supported in GDM 2.14.6 and later.
+              </para>
             </listitem>
           </varlistentry>
 
           <varlistentry>
             <term>pam-message</term>
             <listitem>
-              <para>Label that displays the PAM message. These are messages that PAM/GDM gives about state of the account, help about the prompts and other information.</para>
+              <para>
+                Label that displays the PAM message.  These are messages that
+                PAM/GDM gives about state of the account, help about the
+                prompts and other information.
+              </para>
             </listitem>
           </varlistentry>
 
@@ -3113,9 +4195,13 @@ homogeneous="bool"&gt;
           </varlistentry>
         </variablelist>
 
-        <para>If an item is of type rect, the item can be a button. Buttons must also include a "button" value as follows: <screen>
+        <para>
+          If an item is of type rect, the item can be a button.  Buttons
+          must also include a "button" value as follows:
+<screen>
 &lt;item type="rect" id="disconnect_button" button="true"&gt;.
-</screen></para>
+</screen>
+        </para>
 
         <para>Можливі значення для кнопок:</para>
 
@@ -3179,7 +4265,13 @@ homogeneous="bool"&gt;
           <varlistentry>
             <term>system_button</term>
             <listitem>
-              <para>Perform halt/restart/suspend/etc. options (if allowed by GDM configuration). Also allows user to run configurator if user enters root password (again if allowed by GDM configuration). This is usually now labeled Actions, and referred to as the Actions menu.</para>
+              <para>
+                Perform halt/restart/suspend/etc. options (if allowed by GDM
+                configuration).  Also allows user to run configurator if user
+                enters root password (again if allowed by GDM configuration).
+                This is usually now labeled Actions, and referred to as the
+                Actions menu.
+              </para>
             </listitem>
           </varlistentry>
         </variablelist>
@@ -3188,17 +4280,28 @@ homogeneous="bool"&gt;
       <sect3 id="positionnodes">
         <title>Вузол позиції</title>
 
-        <para>Each item can specify its position and size via the "pos" node. For example: <screen>
+        <para>
+          Each item can specify its position and size via the "pos"
+          node.  For example:
+<screen>
 &lt;pos x="0" y="4" width="100%" height="100%"/&gt;
-</screen></para>
+</screen>
+        </para>
 
         <para>Обидві позиції та розмір може бути вказаний у відсотках та елемент буде займати вказаний відсоток розміру поточного контейнера. Елементи, не укладені у контейнер, займаються вказаний відсоток екрану.</para>
 
         <para>Для x та y, також можна вказати від'ємне значення розташування, що буде означати відлік від правого чи нижнього боку. Але це стосується лише абсолютних координат. Якщо вказано від'ємне значення відсотків, відлік все одно буде з того самого боку.</para>
 
-        <para>The position also specifies the anchor of the item, this can be "n" "ne" "e" "se" "s" "sw" "w" and "nw" or "center" which stand for the different edges/corners or "center" for center. For example: <screen>
+        <para>
+          The position also specifies the anchor of the item, this can be
+          "n" "ne" "e" "se"
+          "s" "sw" "w" and "nw" or
+          "center" which stand for the different edges/corners or
+          "center" for center.  For example:
+<screen>
 &lt;pos x="10%" y="50%" anchor="w" width="80%" height="95"/&gt;
-</screen></para>
+</screen>
+        </para>
 
         <para>Якщо елемент містить контейнер, можна вказати ширину та висоту "box", що означає, що вони вважаються шириною та висотою контейнера, тобто елементи у контейнері плюс відступи.</para>
 
@@ -3206,10 +4309,19 @@ homogeneous="bool"&gt;
 
         <para>Можна вказати властивості "expand" значення "true" чи false. Якщо вказано true, тоді дочірній елемент буде розширено наскільки це можливо (тобто він займатиме більше простору, якщо він є).</para>
 
-        <para>There are two extra properties you can specify (as of 2.4.4.3) for labels (and labels only). The first is "max-width" which will specify the maximum width of the label in pixels. And the second is "max-screen-percent-width" which specifies the maximum percentage of the screen width that the label can occupy. By default no label will occupy more then 90% of the screen by width. An example may be: <screen>
+        <para>
+          There are two extra properties you can specify (as of 2.4.4.3) for
+          labels (and labels only).  The first is "max-width" which
+          will specify the maximum width of the label in pixels.  And the
+          second is "max-screen-percent-width" which specifies the
+          maximum percentage of the screen width that the label can occupy.
+          By default no label will occupy more then 90% of the screen by width.
+          An example may be:
+<screen>
 &lt;item type="label"&gt;
 &lt;pos x="10%" max-screen-percent-width="50%"/&gt;
-</screen></para>
+</screen>
+        </para>
       </sect3>
 
       <sect3 id="shownodes">
@@ -3224,25 +4336,57 @@ homogeneous="bool"&gt;
         <para><filename>remote</filename> - віддалений режим.</para>
         <para><filename>remote-flexi</filename> - віддалений та гнучкий режим.</para>
 
-        <para>For example: <screen>
+        <para>
+          For example:
+<screen>
 &lt;show modes="flexi,remote"/&gt;
-</screen></para>
+</screen>
+        </para>
 
         <para>Також ви можете вказати значення "type", щоб позначити, що певні елементи мають відображатись якщо type має значення true. Допустимі значення:</para>
 
-        <para><filename>chooser</filename>, if ChooserButton is set to "true" in the GDM configuration.</para>
-        <para><filename>config</filename>, if ConfigAvailable is set to "true" in the GDM configuration.</para>
-        <para><filename>halt</filename>, if HaltDaemon is specified in the GDM configuration.</para>
-        <para><filename>reboot</filename>, if RebootCommand is specified in the GDM configuration.</para>
-        <para><filename>suspend</filename>, if SuspendCommand is specified in the GDM configuration.</para>
-        <para><filename>system</filename>, if SystemMenu is specified in the GDM configuration.</para>
-        <para><filename>timed</filename>, if TimedLoginEnabled is set to "true" in the GDM configuration.</para>
+        <para>
+          <filename>chooser</filename>, if ChooserButton is set to
+          "true" in the GDM configuration.
+        </para>
+        <para>
+          <filename>config</filename>, if ConfigAvailable is set to
+          "true" in the GDM configuration.
+        </para>
+        <para>
+          <filename>halt</filename>, if HaltDaemon is specified in
+          the GDM configuration.
+        </para>
+        <para>
+          <filename>reboot</filename>, if RebootCommand is specified in
+          the GDM configuration.
+        </para>
+        <para>
+          <filename>suspend</filename>, if SuspendCommand is specified in
+          the GDM configuration.
+        </para>
+        <para>
+          <filename>system</filename>, if SystemMenu is specified in
+          the GDM configuration.
+        </para>
+        <para>
+          <filename>timed</filename>, if TimedLoginEnabled is set to
+          "true" in the GDM configuration.
+        </para>
 
-        <para>For example: <screen>
+        <para>
+          For example:
+<screen>
 &lt;show modes="console" type="system"/&gt;
-</screen></para>
+</screen>
+        </para>
 
-        <para>Note that if SystemMenu is off then the halt, restart, suspend, chooser and config choices will not be shown, so this is a global toggle for them all. See some of the standard themes for how the show modes are used.</para>
+        <para>
+          Note that if SystemMenu is off then the halt, restart, suspend,
+          chooser and config choices will not be shown, so this is a global
+          toggle for them all.  See some of the standard themes for how the
+          show modes are used.
+        </para>
       </sect3>
 
       <sect3 id="noractprenodes">
@@ -3254,17 +4398,29 @@ homogeneous="bool"&gt;
         <para><filename>active</filename> - стан, коли елемент має фокус вводу.</para>
         <para><filename>prelight</filename> - коли миша знаходиться над елементом.</para>
 
-        <para>When item is "rect" (alpha can be omitted and defaults to 0.0): <screen>
+        <para>
+            When item is "rect" (alpha can be omitted and defaults to
+            0.0):
+<screen>
 &lt;normal color="#ffffff" alpha="0.0"&gt;
-</screen></para>
+</screen>
+        </para>
 
-        <para>When item is "label" <screen>
+        <para>
+          When item is "label"
+<screen>
 &lt;normal color="#ffffff" font="Sans 14"/&gt;
-</screen></para>
+</screen>
+        </para>
 
-        <para>When the item type is "pixmap" or "SVG", then the normal, active, and prelight tags specify the images to use as follows: <screen>
+        <para>
+          When the item type is "pixmap" or "SVG", then the
+          normal, active, and prelight tags specify the images to use as
+          follows:
+<screen>
 &lt;normal file="picture.png" tint="#dddddd"/&gt;
-</screen></para>
+</screen>
+        </para>
 
         <para>Зауважте, що відносні назви шляхів мають бути у тому самому каталозі, що й <filename>.xml</filename> файл теми у <filename>&lt;share&gt;/gdm/themes/&lt;theme_name&gt;</filename>.</para>
       </sect3>
@@ -3284,29 +4440,47 @@ homogeneous="bool"&gt;
       <sect3 id="textnodes">
         <title>Текстовий вузол</title>
 
-        <para>Text tags are used by labels. They can be used to display localized text as follows (if the "xml:lang" attribute is omitted, the C locale is assumed): <screen>
+        <para>
+          Text tags are used by labels.   They can be used to display
+          localized text as follows (if the "xml:lang" attribute is
+          omitted, the C locale is assumed):
+<screen>
 &lt;text xml:lang="fr"&gt;Option&lt;/text&gt;
-</screen></para>
+</screen>
+        </para>
 
-        <para>You can include pango markup in the text nodes for labels, however you must encode it. So for example to have the label of "foo&lt;sup&gt;bar&lt;/sup&gt;", you must type: <screen>
+        <para>
+          You can include pango markup in the text nodes for labels, however
+          you must encode it.  So for example to have the label of
+          "foo&lt;sup&gt;bar&lt;/sup&gt;", you must type:
+<screen>
 &lt;text&gt;"foo&lt;sup&gt;bar&lt;/sup&gt;"&lt;/text&gt;
-</screen></para>
+</screen>
+        </para>
 
         <para>Текстові вузли можуть містити наступні спеціальні послідовності символів:</para>
 
-        <para>%% - A literal % character</para>
+        <para>
+          %% - A literal % character
+        </para>
         <para>%c - час годинника. Лише позначки з ідентифікатором "clock" будуть оновлюватись кожну секунду. Інші позначки будуть містити статичне значення часу.</para>
         <para>%d - назва дисплею (змінна оточення DISPLAY)</para>
         <para>%h - назва вузла (вивід gethostname)</para>
         <para>%m - назва машини (вивід uname.machine)</para>
-        <para>%n - Node name (uname.nodename output)</para>
+        <para>
+          %n - Node name (uname.nodename output)
+        </para>
         <para>%o - назва домену (вивід getdomainname)</para>
         <para>%r - назва випуску (вивід uname.release)</para>
         <para>%s - назва системи (вивід uname.sysname)</para>
         <para>%t - поточне значення затримки для входу із затримкою з конфігураційного файл (0 - якщо вимкнено), за яким йде слово  "seconds", якщо значення більше ніж 1 або слово "second" якщо значення дорівнює 1. Ця символьна послідовність призначена для внутрішнього використання всередині для відображення повідомлень типу "позначка часу", що автоматично оновлюються кожної секунди.</para>
         <para>%u - ім'я користувача для входу із затримкою з конфігураційного файлу (порожнє, якщо вимкнено)  Ця символьна послідовність призначена для внутрішнього використання всередині для відображення повідомлень типу "позначка часу", що автоматично оновлюються кожної секунди.</para>
         <para>\n - переведення каретки</para>
-        <para>_ - An underscore causes the following character to be underlined. If it precedes a % character sequence, the string that replaces the character sequence is underlined.</para>
+        <para>
+          _ - An underscore causes the following character to be underlined.
+          If it precedes a % character sequence, the string that replaces the
+          character sequence is underlined.
+        </para>
       </sect3>
 
       <sect3 id="stocklabels">
@@ -3314,27 +4488,67 @@ homogeneous="bool"&gt;
 
         <para>Деякі загальні локалізовані позначки можна вказувати через теги з набору. Якщо вказано тег "stock", тоді тег "text" ігнорується. Слід використовувати позначки з набору позначок, замість призначення перекладеного значення у тему. При цьому прискорюється час завантаження та краще відбувається переклад. Можливі значення:</para>
 
-        <para><filename>cancel</filename>, _("_Cancel"</para>
-        <para><filename>caps-lock-warning</filename>, _("Caps Lock key is on."</para>
-        <para><filename>chooser</filename>, _("Remote Login via _XDMCP"</para>
-        <para><filename>config</filename>, _("_Configure"</para>
-        <para><filename>disconnect</filename>, _("D_isconnect"</para>
-        <para><filename>halt</filename>, _("Shut _Down"</para>
-        <para><filename>language</filename>, _("_Language"</para>
-        <para><filename>ok</filename>, _("_OK"</para>
-        <para><filename>quit</filename>, _("_Quit"</para>
-        <para><filename>reboot</filename>, _("_Restart"</para>
-        <para><filename>session</filename>, _("_Session"</para>
-        <para><filename>startover</filename>, _("_Start Over"</para>
-        <para><filename>suspend</filename>, _("Sus_pend"</para>
-        <para><filename>system</filename>, _("_Actions" (Formerly "S_ystem"</para>
-        <para><filename>timed-label</filename>, _("User %u will login in %t"</para>
-        <para><filename>username-label</filename>, _("Username:"</para>
-        <para><filename>welcome-label</filename>, _("Welcome to %n"</para>
-
-        <para>For example: <screen>
+        <para>
+          <filename>cancel</filename>, _("_Cancel"
+        </para>
+        <para>
+          <filename>caps-lock-warning</filename>,
+          _("Caps Lock key is on." 
+        </para>
+        <para>
+          <filename>chooser</filename>, _("Remote Login via _XDMCP"
+        </para>
+        <para>
+          <filename>config</filename>, _("_Configure"
+        </para>
+        <para>
+          <filename>disconnect</filename>, _("D_isconnect"
+        </para>
+        <para>
+          <filename>halt</filename>, _("Shut _Down"
+        </para>
+        <para>
+          <filename>language</filename>, _("_Language"
+        </para>
+        <para>
+          <filename>ok</filename>, _("_OK"
+        </para>
+        <para>
+          <filename>quit</filename>, _("_Quit"
+        </para>
+        <para>
+          <filename>reboot</filename>, _("_Restart"
+        </para>
+        <para>
+          <filename>session</filename>, _("_Session"
+        </para>
+        <para>
+          <filename>startover</filename>, _("_Start Over"
+        </para>
+        <para>
+          <filename>suspend</filename>, _("Sus_pend"
+        </para>
+        <para>
+          <filename>system</filename>, _("_Actions"
+          (Formerly "S_ystem"
+        </para>
+        <para>
+          <filename>timed-label</filename>,
+          _("User %u will login in %t"
+        </para>
+        <para>
+          <filename>username-label</filename>, _("Username:"
+        </para>
+        <para>
+          <filename>welcome-label</filename>, _("Welcome to %n"
+        </para>
+
+        <para>
+          For example:
+<screen>
 &lt;stock type="welcome-label"&gt;
-</screen></para>
+</screen>
+        </para>
       </sect3>
 
       <sect3 id="customwidgetry">
@@ -3356,56 +4570,186 @@ homogeneous="bool"&gt;
 &lt;/item&gt;
 </screen>
 
-        <para>Then if the user chooses 'Foo' then <filename>&lt;var&gt;/gdm/:0.GreeterInfo</filename> will contain: <screen>
+        <para>
+          Then if the user chooses 'Foo' then 
+          <filename>&lt;var&gt;/gdm/:0.GreeterInfo</filename> will contain:
+<screen>
 custom-config=foo
-</screen></para>
+</screen>
+        </para>
       </sect3>
     </sect2>
   </sect1>
 
   <sect1 id="accessibility">
     <title>Спеціальні можливості</title>
-      <para>GDM supports "Accessible Login" to allow users to log in to their desktop session even if they cannot easily use the screen, mouse, or keyboard in the usual way. Only the "Standard Greeter" supports accessibility, so use this login GUI for accessibility support. This is done by specifying the "Standard Greeter" in the "Local" tab for the console display and specifying the "Standard Greeter" in the "Remote" tab for remote displays. Or you can modify the <filename>Greeter</filename> configuration option by hand to be <command>gdmlogin</command>.</para>
-
-      <para>The Standard Greeter supports the ability to launch assistive technologies at login time via configurable "gestures" from the standard keyboard, pointing device, or switch device attached to the USB or PS/2 mouse port. Also the user can change the visual appearance of the login UI before logging in, for instance to use a higher-contrast color scheme for better visibility.</para>
+      <para>
+        GDM supports "Accessible Login" to allow users to log in to
+        their desktop session even if they cannot easily use the screen, mouse,
+        or keyboard in the usual way.  Only the "Standard Greeter"
+        supports accessibility, so use this login GUI for accessibility
+        support.  This is done by specifying the "Standard Greeter"
+        in the "Local" tab for the console display and specifying
+        the "Standard Greeter" in the "Remote" tab for 
+        remote displays.  Or you can modify the <filename>Greeter</filename>
+        configuration option by hand to be <command>gdmlogin</command>.
+      </para>
+
+      <para>
+        The Standard Greeter supports the ability to launch assistive
+        technologies at login time via configurable "gestures" from
+        the standard keyboard, pointing device, or switch device attached to
+        the USB or PS/2 mouse port.  Also the user can change the visual
+        appearance of the login UI before logging in, for instance to use a
+        higher-contrast color scheme for better visibility.  
+      </para>
 
        <sect2 id="accessibilityconfig">
           <title>Налаштовування спеціальних можливостей</title>
-             <para>In order to enable Accessible Login, the system administrator must make some changes to the default login configuration by manually modifying three human-readable configuration files, stored in the GDM configuration, AccessKeyMouseEvents and AccessDwellMouseEvents.</para>
-
-             <para>In order to allow users to change the color and contrast scheme of the login dialog, make sure the <filename>AllowThemeChange</filename> parameter in the GDM configuration is set to "true".</para>
-
-             <para>To restrict user changes to the visual appearance to a subset of available themes, the <filename>GtkThemesToAllow</filename> parameter in the GDM configuration can be set to a list of acceptable themes separated by commas. For example:</para>
+             <para>
+             In order to enable Accessible Login, the system administrator must
+             make some changes to the default login configuration by manually
+             modifying three human-readable configuration files, stored in
+             the GDM configuration, AccessKeyMouseEvents and
+             AccessDwellMouseEvents.
+             </para>
+
+             <para>
+             In order to allow users to change the color and contrast scheme of
+             the login dialog, make sure the
+             <filename>AllowThemeChange</filename> parameter in the GDM
+             configuration is set to "true".
+             </para>
+
+             <para>
+             To restrict user changes to the visual appearance to a subset of
+             available themes, the <filename>GtkThemesToAllow</filename>
+             parameter in the GDM configuration can be set to a list of
+             acceptable themes separated by commas.  For example:
+             </para>
 
 <screen>
 GtkThemesToAllow=HighContrast,HighContrastInverse
 </screen>
 
-             <para>To enable the use of assistive technologies such as the Onscreen Keyboard, Screen Reader, or Magnifier, the <filename>AddGtkModules</filename> parameter in the GDM configuration must be uncommented and set to "true". Also the <filename>GtkModulesList</filename> parameter must be uncommented and set as follows:</para>
+             <para>
+             To enable the use of assistive technologies such as the Onscreen
+             Keyboard, Screen Reader, or Magnifier, the
+             <filename>AddGtkModules</filename> parameter in the GDM
+             configuration must be uncommented and set to "true".
+             Also the <filename>GtkModulesList</filename> parameter must be
+             uncommented and set as follows:
+             </para>
 
 <screen>
 GtkModulesList=gail:atk-bridge:dwellmouselistener:keymouselistener
 </screen>
 
-             <para>System administrators may wish to load only the minimum subset of these modules which is required to support their user base. Depending on the end-user needs, not all of the above GtkModules may need to be loaded. If your end-users need the integrated Screen Reader and Magnifier, you must include "gail" and "atk-bridge". If your end-users will be using a pointing device without buttons or switches, include "dwellmouselistener". If some of your users will use pointing devices with switches, alternative physical keyboards, or switch/button devices, include "keymouselistener". Including all four is suitable for most system configurations. The Onscreen Keyboard can operate without gail and atk-bridge, but with a reduced feature set; for optimum accessibility we recommend including both gail and atk-bridge.</para>
-
-             <para>Once "keymouselistener" and/or "dwellmouselistener" have been added to the GtkModules loaded by GDM, you can assign end-user actions with the launching of specific assistive technologies. These gesture associations are contained in files AccessKeyMouseEvents and AccessDwellMouseEvents, respectively. Both files are located in the &lt;etc&gt;/gdm/modules directory. The gesture format is described in the two configuration files.</para>
-
-             <para>The AccessKeyMouseEvents file controls the keymouselistener Gesture Listener and is used to define key-press, mouse button, or XInput device sequences that can be used to launch applications needed for accessibility. In order to reduce the likelihood of unintentional launch, these "gestures" may be associated with multiple switch presses and/or minimum durations. Note that the XKB extension is needed for key gestures to work, so you may need to add +xkb to your Xserver command line for gestures to work properly.</para>
-
-             <para>The DwellKeyMouseEvents file controls the dwellmouselistner and supports gestures that involve only motion of a pointing device such as the system mouse of an alternative pointing device such as a head pointer or trackball may also be defined. All gestures are specified by the same syntax; that is, there is no distinction between a "core mouse" gesture and motion from an alternate input device.</para>
-
-             <para>Motion gestures are defined as "crossing events" into and out of the login dialog window. If the "dwellmouselistener" GtkModule is loaded, alternative pointing devices are temporarily "latched" to the core pointer, such that motion from alternative devices results in movement of the onscreen pointer.</para>
+             <para>
+             System administrators may wish to load only the minimum subset of
+             these modules which is required to support their user base.
+             Depending on the end-user needs, not all of the above GtkModules
+             may need to be loaded.  If your end-users need the integrated
+             Screen Reader and Magnifier, you must include "gail" and
+             "atk-bridge".  If your end-users will be using a
+             pointing device without buttons or switches, include
+             "dwellmouselistener".  If some of your users will use
+             pointing devices with switches, alternative physical keyboards, or
+             switch/button devices, include "keymouselistener".
+             Including all four is suitable for most system configurations.
+             The Onscreen Keyboard can operate without gail and atk-bridge, but
+             with a reduced feature set; for optimum accessibility we recommend
+             including both gail and atk-bridge.
+             </para>
+
+             <para>
+             Once "keymouselistener" and/or
+             "dwellmouselistener" have been added to the GtkModules
+             loaded by GDM, you can assign end-user actions with the launching
+             of specific assistive technologies.  These gesture associations
+             are contained in files AccessKeyMouseEvents and
+             AccessDwellMouseEvents, respectively.  Both files are located in
+             the &lt;etc&gt;/gdm/modules directory.  The gesture format is
+             described in the two configuration files.
+             </para>
+
+             <para>
+             The AccessKeyMouseEvents file controls the keymouselistener
+             Gesture Listener and is used to define key-press, mouse button,
+             or XInput device sequences that can be used to launch applications
+             needed for accessibility.  In order to reduce the likelihood of
+             unintentional launch, these "gestures" may be associated
+             with multiple switch presses and/or minimum durations.  Note that
+             the XKB extension is needed for key gestures to work, so you may
+             need to add +xkb to your Xserver command line for gestures to
+             work properly.
+             </para>
+
+             <para>
+             The DwellKeyMouseEvents file controls the dwellmouselistner and
+             supports gestures that involve only motion of a pointing device
+             such as the system mouse of an alternative pointing device such
+             as a head pointer or trackball may also be defined.   All gestures
+             are specified by the same syntax; that is, there is no distinction
+             between a "core mouse" gesture and motion from an
+             alternate input device.
+             </para>
+
+             <para>
+             Motion gestures are defined as "crossing events" into
+             and out of the login dialog window.  If the
+             "dwellmouselistener" GtkModule is loaded, alternative
+             pointing devices are temporarily "latched" to the core
+             pointer, such that motion from alternative devices results in
+             movement of the onscreen pointer.
+             </para>
 
              <para>Для використання служби промови тексту під час входу (наприклад, при використанні програми читання екрану в режимі speech) на деяких операційних системах, GDM user must be made a member of the "audio" group</para>
 
-             <para>Currently GDM does not remember what accessible technology programs have been started when switching applications. So if the user switches between the login program and the chooser, for example, then it is necessary for the user to redo the gesture. Users may need to also set up their default session so that the assistive technologies required are started automatically (or have appropriate key-bindings defined to start them) after the user session has started.</para>
-
-             <para>There are some issues that cause users to have problems getting the gesture listeners to work. It is recommended that people use GDM version 2.8.0.5 or later for best results. Some X servers have a bug which causes detectable autorepeat to fail when XEVIE is enabled (which happens when atk-bridge is included as a GTK Module). This bug causes key gestures with a duration greater than 0 to always fail. A workaround is to simply redefine all key gestures so they have zero length duration. Some versions of GOK and gnopernicus will not launch unless the "gdm" user has a writable home directory. If you see an hourglass cursor when you complete a gesture but the program does not start, then you are likely having this problem. It should be considered a bug for AT programs to require having a writable home directory, so please file a bug with the AT program if you encounter this problem. Also note that some input devices require X server configuration before GDM will recognize them.</para>
+             <para>
+             Currently GDM does not remember what accessible technology
+             programs have been started when switching applications.  So
+             if the user switches between the login program and the 
+             chooser, for example, then it is necessary for the user to
+             redo the gesture.  Users may need to also set up their default
+             session so that the assistive technologies required are
+             started automatically (or have appropriate key-bindings 
+             defined to start them) after the user session has started.
+             </para>
+
+             <para>
+             There are some issues that cause users to have problems
+             getting the gesture listeners to work.  It is recommended that
+             people use GDM version 2.8.0.5 or later for best results.  
+             Some X servers have a bug which causes detectable autorepeat
+             to fail when XEVIE is enabled (which happens when atk-bridge
+             is included as a GTK Module).  This bug causes key gestures
+             with a duration greater than 0 to always fail.  A workaround
+             is to simply redefine all key gestures so they have zero length
+             duration.  Some versions of GOK and gnopernicus will not launch
+             unless the "gdm" user has a writable home directory.
+             If you see an hourglass cursor when you complete a gesture but the
+             program does not start, then you are likely having this problem.
+             It should be considered a bug for AT programs to require having a
+             writable home directory, so please file a bug with the AT
+             program if you encounter this problem.  Also note that some input
+             devices require X server configuration before GDM will recognize
+             them.
+             </para>
        </sect2>
        <sect2 id="accessibilitysound">
           <title>Налаштовування звуку спеціальних пожливостей</title>
-             <para>By default, GDM requires a media application such as "sox" to be present to play sounds for successful or failed login. GDM defaults the location of this application to <filename>&lt;bin&gt;/play</filename> (or <filename>&lt;bin&gt;/audioplay</filename> on Solaris. This can be changed via the SoundProgram GDM configuration option. Typically most text-to-speech programs (such as ORCA or Gnopernicus) use a separate mechanism to play audio.</para>
+             <para>
+             By default, GDM requires a media application such as
+             "sox" to be present to play sounds for successful or
+             failed login.  GDM defaults
+             the location of this application to
+             <filename>&lt;bin&gt;/play</filename> (or
+             <filename>&lt;bin&gt;/audioplay</filename> on Solaris.  This can
+             be changed via the SoundProgram GDM configuration option.  
+             Typically most text-to-speech programs (such as ORCA or 
+             Gnopernicus) use a separate mechanism to play audio.
+             </para>
         </sect2>
   </sect1>
 
@@ -3414,35 +4758,83 @@ GtkModulesList=gail:atk-bridge:dwellmouselistener:keymouselistener
 
        <sect2 id="solarisconfiguration">
           <title>Налаштовування Solaris</title>
-             <para>On Solaris, the following configuration is recommended. This turns on IPv6 and also turns on PreFetch for performance benefit. <screen>
+             <para>
+               On Solaris, the following configuration is recommended.
+               This turns on IPv6 and also turns on PreFetch for
+               performance benefit.
+
+<screen>
 ./autogen.sh --prefix=/usr --sysconfdir=/etc/X11 --localstatedir=/var
    --libexecdir=/usr/lib --enable-ipv6=yes --with-at-bindir=/usr/sfw/bin
    --with-prefetch --with-post-path=/usr/openwin/bin
-</screen></para>
+</screen>
+             </para>
 
-             <para>Configuring GDM with the "--with-post-path=/usr/openwin/bin" on Solaris is recommended for access to programs like Xnest.</para>
+             <para>
+               Configuring GDM with the
+               "--with-post-path=/usr/openwin/bin" on Solaris is
+               recommended for access to programs like Xnest.
+             </para>
        </sect2>
 
        <sect2 id="solarislogindevperm">
           <title>Solaris /etc/logindevperm</title>
-             <para>GDM supports /etc/logindevperm, but only on Solaris 10 and higher. Refer to the logindevperm.4 man page for more information.</para>
-
-             <para>To make /etc/logindevperm functionality work on Solaris 9 or earlier you would have to hack the GDM PreSession and PostSession script to chmod the device permissions directly. In other words, if /etc/logindevperm had a listing like this:</para>
+             <para>
+               GDM supports /etc/logindevperm, but only on Solaris 10 and higher.
+               Refer to the logindevperm.4 man page for more information.
+             </para>
+
+             <para>
+               To make /etc/logindevperm functionality work on Solaris 9 or
+               earlier you would have to hack the GDM PreSession and
+               PostSession script to chmod the device permissions directly.  In
+               other words, if /etc/logindevperm had a listing like this:
+             </para>
 
 <screen>
 /dev/console    0600    /dev/sound/*            # звукові пристрої
 </screen>
      
-             <para>The PreSession script would need to be modified to chown /dev/console to the user:group who is logging into the console and ensure whatever permissions is specified in /etc/logindevperm (0600 for the line above). Then in the PostSession script chmod the device back to root:root and ensure 0600 this time (do not use the value in the /etc/logindevperm file). Linux uses a different mechanism for managing device permissions, so this extra scripting is not needed.</para>
+             <para>
+               The PreSession script would need to be modified to chown
+               /dev/console to the user:group who is logging into the console
+               and ensure whatever permissions is specified in /etc/logindevperm
+               (0600 for the line above).  Then in the PostSession script chmod
+               the device back to root:root and ensure 0600 this time (do not
+               use the value in the /etc/logindevperm file).  Linux uses a
+               different mechanism for managing device permissions, so this
+               extra scripting is not needed.
+             </para>
        </sect2>
 
        <sect2 id="solarisautomaticlogin">
           <title>Автоматичний вхід на Solaris</title>
-             <para>Automatic login does not work on Solaris because PAM is not configured to support this feature by default. Automatic login is a GDM feature that is not enabled by default, so you would only notice this problem if you try to make use of it. Turning this feature on causes your computer to login to a specified username on startup without asking for username and password. This is an unsecure way to set up your computer.</para>
-
-             <para>If using Solaris 10 or lower, then you need to compile the pam_allow.c code provided with the GDM release and install it to /usr/lib/security (or provide the full path in /etc/pam.conf) and ensure it is owned by uid 0 and not group or world writable.</para>
-
-             <para>The following are reasonable pam.conf values for turning on automatic login in GDM. Make sure to read the PAM documentation (e.g. pam.d/pam.conf man page) and be comfortable with the security implications of any changes you intend to make to your configuration.</para>
+             <para>
+               Automatic login does not work on Solaris because PAM is not
+               configured to support this feature by default.  Automatic 
+               login is a GDM feature that is not enabled by default, so you
+               would only notice this problem if you try to make use of it.
+               Turning this feature on causes your computer to login to a
+               specified username on startup without asking for username
+               and password.  This is an unsecure way to set up your
+               computer. 
+             </para>
+
+             <para>
+               If using Solaris 10 or lower, then you need to compile
+               the pam_allow.c code provided with the GDM release and
+               install it to /usr/lib/security (or provide the full path
+               in /etc/pam.conf) and ensure it is owned by uid 0 and not
+               group or world writable.
+             </para>
+
+             <para>
+               The following are reasonable pam.conf values for turning on
+               automatic login in GDM.  Make sure to read the PAM documentation
+               (e.g. pam.d/pam.conf man page) and be comfortable with the
+               security implications of any changes you intend to make to
+               your configuration.
+             </para>
 
 <screen>
        gdm-autologin auth  required    pam_unix_cred.so.1
@@ -3452,7 +4844,10 @@ GtkModulesList=gail:atk-bridge:dwellmouselistener:keymouselistener
        gdm-autologin password  sufficient  pam_allow.so.1
 </screen>
 
-             <para>The above setup will cause no lastlog entry to be generated. If a lastlog entry is desired, then use the following for session:</para>
+             <para>
+               The above setup will cause no lastlog entry to be generated.  If
+               a lastlog entry is desired, then use the following for session:
+             </para>
 
 <screen>
        gdm-autologin session required pam_unix_session.so.1
@@ -3463,11 +4858,29 @@ GtkModulesList=gail:atk-bridge:dwellmouselistener:keymouselistener
           <title>Інші особливості Solaris</title>
              <para>GDM підтримує деякі специфічні властивості Solaris:</para>
 
-             <para>GDM supports Solaris Auditing if running on Solaris 10 or higher. GDM should not be used if auditing is needed and running Solaris 9 or older.</para>
-
-            <para>GDM supports a security feature which causes the X server to run as the user instead of as the root user. GDM must be using PAM for this feature to be enabled, which is the normal case for Solaris. This second feature has the side-effect of causing the X server to always restart between sessions, which disables the AlwaysRestartServer configuration option.</para>
-
-            <para>Solaris supports the <filename>/etc/default/login</filename> interface, which affects the <filename>DefaultPath</filename>, <filename>RootPath</filename>, <filename>PasswordRequired</filename>, and <filename>AllowRemoteRoot</filename> options as described in the "Configuration" section.</para>
+             <para>
+               GDM supports Solaris Auditing if running on Solaris 10 or
+               higher.  GDM should not be used if auditing is needed and
+               running Solaris 9 or older.
+            </para>
+
+            <para>
+                GDM supports a security feature which causes the X server to
+                run as the user instead of as the root user.  GDM must be using
+                PAM for this feature to be enabled, which is the normal case
+                for Solaris.  This second feature has the side-effect of
+                causing the X server to always restart between sessions, which
+                disables the AlwaysRestartServer configuration option.  
+            </para>
+
+            <para>
+                Solaris supports the <filename>/etc/default/login</filename>
+                interface, which affects the <filename>DefaultPath</filename>,
+                <filename>RootPath</filename>,
+                <filename>PasswordRequired</filename>, and
+                <filename>AllowRemoteRoot</filename> options as described in the
+                "Configuration" section.
+            </para>
        </sect2>
   </sect1>
 
@@ -3479,23 +4892,48 @@ GtkModulesList=gail:atk-bridge:dwellmouselistener:keymouselistener
     <sect2 id="terminallab">
       <title>Термінальна лабораторія з одним сервером</title>
 
-      <para>Suppose you want to make a lab full of X terminals that all connect to one server machine. So let's call one X terminal <filename>xterminal</filename> and let's call the server machine <filename>appserver</filename>. You install GDM on both.</para>
+      <para>
+        Suppose you want to make a lab full of X terminals that all connect
+        to one server machine.  So let's call one X terminal
+        <filename>xterminal</filename> and let's call the server machine
+        <filename>appserver</filename>.  You install GDM on both.
+      </para>
 
-      <para>On <filename>appserver</filename> you enable XDMCP, so you have <screen>
+      <para>
+        On <filename>appserver</filename> you enable XDMCP, so you have
+<screen>
 [xdmcp]
 Enable=true
-</screen> If you want no local screens here, you can then make the <filename>[servers]</filename> section empty.</para>
-
-      <para>On the <filename>xterminal</filename> you disable XDMCP (you don't want anyone to connect to the xterminal really). You will add a server type perhaps called <filename>Terminal</filename> as follows: <screen>
+</screen>
+        If you want no local screens here, you can then
+        make the <filename>[servers]</filename> section empty.
+      </para>
+
+      <para>
+        On the <filename>xterminal</filename> you disable XDMCP (you don't
+        want anyone to connect to the xterminal really).  You will add a
+        server type perhaps called <filename>Terminal</filename> as follows:
+<screen>
 [server-Terminal]
 name=Terminal server
 command=/path/to/X -terminate
 flexible=false
 handled=false
-</screen> This definition should in fact be included in the standard configuration file. Notice that we made the <filename>handled</filename> key false since we don't want GDM to handle this server localy. Also note that we have not yet added the <filename>-query</filename> argument, you can add that here, or in the <filename>[servers]</filename> section. We'll define our local servers as follows: <screen>
+</screen>
+        This definition should in fact be included in the standard
+        configuration file.  Notice that we made the
+        <filename>handled</filename> key false since we don't want GDM to
+        handle this server localy.  Also note that we have not yet added the
+        <filename>-query</filename> argument, you can add that here, or in the
+        <filename>[servers]</filename> section.  We'll define our local
+        servers as follows:
+<screen>
 [servers]
 0=Terminal -query appserver
-</screen> This will run a direct XDMCP query to the server named <filename>appserver</filename>.</para>
+</screen>
+        This will run a direct XDMCP query to the server named
+        <filename>appserver</filename>.
+      </para>
     </sect2>
 
     <sect2 id="terminallabtwo">
@@ -3503,53 +4941,154 @@ handled=false
 
       <para>Скажімо ви хочете створити лабораторію з X-терміналами, які з'єднані з кількома серверами. Тож створимо їх <filename>appserverone</filename> та <filename>appservertwo</filename>. Знову назвемо наш сервер X-терміналів <filename>xterminal</filename>. Параметри на обох серверах такі ж як і у випадку з одним сервером. Не слід явно вмикати непрямі запити до сервера, бо на X-терміналах локально запускається селектор вузлів.</para>
 
-      <para>So on the <filename>xterminal</filename> you again disable XDMCP. You will add a server type perhaps called <filename>Chooser</filename> as follows: <screen>
+      <para>
+        So on the <filename>xterminal</filename> you again disable XDMCP.
+        You will add a server type perhaps called <filename>Chooser</filename>
+        as follows:
+<screen>
 [server-Chooser]
 name=Chooser server
 command=/path/to/X
 flexible=false
 chooser=true
-</screen> And again this definition should in fact be included in the standard configuration file. Notice that we made the <filename>chooser</filename> key true here. This will run the XDMCP chooser for this server, and when the user chooses a host GDM will run a query for that host. Then we will define our local servers as follows: <screen>
+</screen>
+        And again this definition should in fact be included in the standard
+        configuration file.  Notice that we made the
+        <filename>chooser</filename> key true here.  This will run the XDMCP
+        chooser for this server, and when the user chooses a host GDM will run
+        a query for that host.  Then we will define our local servers as
+        follows:
+<screen>
 [servers]
 0=Chooser
-</screen></para>
-
-      <para>The XDMCP chooser on the X terminal will normally give a broadcast query to see which servers exist on the network. If the two servers are not reachable by a broadcast query, you must add them by hand to the configuration file. So in the <filename>[chooser]</filename> section you would have: <screen>
+</screen>
+      </para>
+
+      <para>
+        The XDMCP chooser on the X terminal will normally give a broadcast
+        query to see which servers exist on the network.  If the two servers
+        are not reachable by a broadcast query, you must add them by hand to
+        the configuration file.  So in the <filename>[chooser]</filename>
+        section you would have:
+<screen>
 Hosts=appserverone,appservertwo
-</screen> and any other servers you wish the users to be able to connect to.</para>
-
-      <para>Sometimes you may want to run the chooser on the server side however. Then what you want to do is to run a configuration similar to the previous section about the one server configuration with XDMCP indirect queries enabled on <filename>appserver</filename> and on the X terminals you'd have <screen>
+</screen>
+        and any other servers you wish the users to be able to connect to.
+      </para>
+
+      <para>
+        Sometimes you may want to run the chooser on the server side however.
+        Then what you want to do is to run a configuration similar to the
+        previous section about the one server configuration with XDMCP
+        indirect queries enabled on <filename>appserver</filename> and on the
+        X terminals you'd have
+<screen>
 [servers]
 0=Terminal -indirect appserver
-</screen> This way for example you only have to maintain one <filename>Hosts</filename> entry. However as a disadvantage then, the <filename>appserver</filename> must then always be available. So it's not good for situations where you want to have several servers and not all of them have to be on all the time. You could also have one of the X terminals handle indirect XDMCP queries and serve up the chooser to the other X terminals.</para>
+</screen>
+        This way for example you only have to maintain one
+        <filename>Hosts</filename> entry.  However as a disadvantage then,
+        the <filename>appserver</filename> must then always be available.  So
+        it's not good for situations where you want to have several servers
+        and not all of them have to be on all the time.  You could also have
+        one of the X terminals handle indirect XDMCP queries and serve up the
+        chooser to the other X terminals.
+      </para>
     </sect2>
   </sect1>
 
   <sect1 id="troubleshooting">
     <title>Усунення проблем</title>
 
-    <para>This section discusses helpful tips for getting GDM working. In general, if you have a problem using GDM, you can submit a bug to the "gdm" category in <ulink type="http" url="http://bugzilla.gnome.org/">bugzilla.gnome.org</ulink> or send an email to the <address><email>gdm-list@gnome.org</email></address> mail list.</para>
-
-    <para>If GDM is failing to work properly, it is always a good idea to include debug information. Use the <command>gdmsetup</command> command to turn on debug ("Enable debug messages to system log" checkbox in the "Security" tab), then use GDM to the point where it fails, and include the GDM output sent to your system log (<filename>&lt;var&gt;/log/messages</filename> or <filename>&lt;var&gt;/adm/messages</filename> depending on your operating system). Since the system log can be large, please only include the GDM debug information and do not sent the entire file. If you do not see any GDM syslog output, you may need to configure syslog (see syslog.3c man page).</para>
-
-    <para>You should not leave debug on after collecting data. It will clutter your syslog and slow system performance.</para>
+    <para>
+      This section discusses helpful tips for getting GDM working.  In general,
+      if you have a problem using GDM, you can submit a bug to the
+      "gdm" category in
+      <ulink type="http" url="http://bugzilla.gnome.org/">bugzilla.gnome.org</ulink>
+      or send an email to the
+      <address><email>gdm-list@gnome.org</email></address> mail list.
+    </para>
+
+    <para>
+      If GDM is failing to work properly, it is always a good idea to include
+      debug information.  Use the <command>gdmsetup</command> command to turn
+      on debug ("Enable debug messages to system log" checkbox in the
+      "Security" tab), then use GDM to the point where it fails, and
+      include the GDM output sent to your system log
+      (<filename>&lt;var&gt;/log/messages</filename> or
+      <filename>&lt;var&gt;/adm/messages</filename> depending on your operating
+      system).  Since the system log can be large, please only include the GDM
+      debug information and do not sent the entire file.  If you do not see any
+      GDM syslog output, you may need to configure syslog (see syslog.3c man
+      page).
+    </para>
+
+    <para>
+      You should not leave debug on after collecting data.  It will clutter your
+      syslog and slow system performance.
+    </para>
 
     <sect2 id="wontstart">
       <title>GDM не запускається</title>
 
-      <para>There are a many problems that can cause GDM to fail to start, but this section will discuss a few common problems and how to approach tracking down a problem with GDM starting. Some problems will cause GDM to respond with an error message or dialog when it tries to start, but it can be difficult to track down problems when GDM fails silently.</para>
-
-      <para>First make sure that the Xserver is configured properly. The GDM configuration file contains a command in the [server-Standard] section that is used for starting the Xserver. Verify that this command works on your system. Running this command from the console should start the Xserver. If it fails, then the problem is likely with your Xserver configuration. Refer to your Xserver error log for an idea of what the problem may be. The problem may also be that your Xserver requires different command-line options. If so, then modify the Xserver command in the GDM configuration file so that it is correct for your system.</para>
-
-      <para>Another common problem is that the GDM greeter program is having trouble starting. This can happen, for example, if GDM cannot find a needed library or other resource. Try starting the Xserver and a terminal program, set the shell environment variable DOING_GDM_DEVELOPMENT=1 and run <command>&lt;lib&gt;/gdmlogin</command> or <command>&lt;lib&gt;/gdmgreeter</command>. Any error messages echoed to the terminal will likely highlight the problem. Also, turning on debug and checking the output sent to the system log will often highlight the problem.</para>
-
-      <para>Also make sure that the <filename>/tmp</filename> directory has reasonable ownership and permissions, and that the machine's file system is not full. These problems will cause GDM to fail to start.</para>
+      <para>
+         There are a many problems that can cause GDM to fail to start, but
+         this section will discuss a few common problems and how to approach
+         tracking down a problem with GDM starting.   Some problems will 
+         cause GDM to respond with an error message or dialog when it tries
+         to start, but it can be difficult to track down problems when GDM
+         fails silently.
+      </para>
+
+      <para>
+         First make sure that the Xserver is configured properly.  The 
+         GDM configuration file contains a command in the [server-Standard]
+         section that is used for starting the Xserver.  Verify that this
+         command works on your system.  Running this command from the 
+         console should start the Xserver.  If it fails, then the problem
+         is likely with your Xserver configuration.  Refer to your Xserver
+         error log for an idea of what the problem may be.  The problem may
+         also be that your Xserver requires different command-line options.
+         If so, then modify the Xserver command in the GDM configuration file
+         so that it is correct for your system.
+      </para>
+
+      <para>
+         Another common problem is that the GDM greeter program is having
+         trouble starting.  This can happen, for example, if GDM cannot find
+         a needed library or other resource.  Try starting the Xserver and
+         a terminal program, set the shell environment variable 
+         DOING_GDM_DEVELOPMENT=1 and run
+         <command>&lt;lib&gt;/gdmlogin</command>
+         or <command>&lt;lib&gt;/gdmgreeter</command>.  Any error messages
+         echoed to the terminal will likely highlight the problem.  Also,
+         turning on debug and checking the output sent to the system log 
+         will often highlight the problem.
+      </para>
+
+      <para>
+         Also make sure that the <filename>/tmp</filename> directory has
+         reasonable ownership and permissions, and that the machine's file
+         system is not full.  These problems will cause GDM to fail to start.
+      </para>
     </sect2>
 
     <sect2 id="notaccessfile">
       <title>GDM не може отримати доступ до параметрів користувача</title>
 
-      <para>GDM saves user settings, such as your default session and default language, in the <filename>~/.dmrc</filename>. Other files, such as the user's <filename>~/.Xauthority</filename> file will also affect login. GDM, by default, is strict about how it tries to access files in the users home directory, and will ignore the file if they do not conform to certain rules. You can use the <filename>RelaxPermissions</filename> configuration option to make GDM less strict about how it accesses files in the user's home directory, or correct the permissions issues that cause GDM to ignore the file. This is discussed in detail described in the "File Access" section of the "Overview".</para>
+      <para>
+         GDM saves user settings, such as your default session and default
+         language, in the <filename>~/.dmrc</filename>.  Other files, such
+         as the user's <filename>~/.Xauthority</filename> file will also
+         affect login.  GDM, by default, is strict about how it tries to
+         access files in the users home directory, and will ignore the file if
+         they do not conform to certain rules.  You can use the 
+         <filename>RelaxPermissions</filename> configuration option to
+         make GDM less strict about how it accesses files in the user's
+         home directory, or correct the permissions issues that cause GDM
+         to ignore the file.  This is discussed in detail described in the
+         "File Access" section of the "Overview". 
+      </para>
     </sect2>
   </sect1>
 
diff --git a/docs/uk/legal.xml b/docs/uk/legal.xml
index a9c75713..49a4a822 100644
--- a/docs/uk/legal.xml
+++ b/docs/uk/legal.xml
@@ -5,5 +5,12 @@
 
 	<para>Більшість назв, що використовуються компаніями для розповсюдження їх продуктів та послуг є торговими марками. Якщо такі назви зустрічаються у документації з GNOME та учасникам проекту документування GNOME відомо, що вони є торговими марками, тоді ці назви пишуться великими літерами або починаються з великої літери.</para>
 
-	<para>ДОКУМЕНТ ТА ЗМІНЕНІ ВЕРСІЇ ЦЬОГО ДОКУМЕНТУ ПОСТАЧАЮТЬСЯ НА УМОВАХ ВІЛЬНОЇ ЛІЦЕНЗІЇ ДЛЯ ДОКУМЕНТАЦІЇ GNU З ПОДАЛЬШИМ РОЗУМІННЯМ ЩО: <orderedlist><listitem><para>ДОКУМЕНТ НАДАЄТЬСЯ "ЯК Є", БЕЗ БУДЬ-ЯКИХ ГАРАНТІЇ, ЯВНИХ ЧИ НЕЯВНИХ, ВКЛЮЧАЮЧИ, АЛЕ НЕ ОБМЕЖУЮЧИСЬ, ГАРАНТІЙ ЩО ЦЕЙ ДОКУМЕНТ ЧИ ЗМІНЕНА ВЕРСІЯ ДОКУМЕНТА ВІЛЬНІ ВІД ДЕФЕКТІВ, ПРИДАТНІ ДО ПРОДАЖУ, ВІДПОВІДАЮТЬ ПЕВНІЙ МЕТІ АБО НЕ ПОРУШУЮТЬ ЧИЇСЬ ПРАВА. ВЕСЬ РИЗИК ЗА ЯКІСТЬ, ТОЧНІСТЬ, ТА ЧИННІСТЬ ЦЬОГО ДОКУМЕНТУ АБО ЙОГО ЗМІНЕНИХ ВЕРСІЙ ЛЕЖИТЬ НА ВАС.  ЯКЩО БУДЬ-ЯКИЙ ДОКУМЕНТ ЧИ ЗМІНЕНА ВЕРСІЯ БУДУТЬ ВИЗНАНІ ДЕФЕКТНИМИ У БУДЬ-ЯКОМУ ВІДНОШЕННІ, ВИ (НЕ ПОЧАТКОВИЙ УКЛАДАЧ, АВТОР АБО БУДЬ-ЯКИЙ СПІВАВТОР) БЕРЕТЕ НА СЕБЕ ВИТРАТИ ЗА БУДЬ-ЯКЕ НЕОБХІДНЕ ОБСЛУГОВУВАННЯ, РЕМОНТ ЧИ ВИПРАВЛЕННЯ. ЦЯ ВІДМОВА ВІД ГАРАНТІЙ СКЛАДАЄ ВАЖЛИВУ ЧАСТИНУ ЦІЄЇ ЛІЦЕНЗІЇ. НЕ ДОПУСКАЄТЬСЯ ВИКОРИСТАННЯ ЦЬОГО ДОКУМЕНТУ АБО ЙОГО ЗМІНЕНОЇ ВЕРСІЇ БЕЗ ПРИЙНЯТТЯ ЦІЄЇ ВІДМОВИ; ТА</para></listitem><listitem><para>НІ ЗА ЯКИХ ОБСТАВИН ТА ЗА БУДЬ-ЯКОГО ЗАКОНОДАВСТВА, ЧИ ТО ГРОМАДЯНСЬКОЇ ВІДПОВІДАЛЬНОСТІ (ВКЛЮЧАЮЧИ ХАЛАТНІСТЬ), ДОГОВОРУ, ЧИ ЧОГОСЬ ІНШОГО, АВТОР, ПОЧАТКОВИЙ УКЛАДАЧ, БУДЬ-ЯКИЙ СПІВАВТОР, АБО ДИСТРИБ'ЮТОР ДОКУМЕНТУ ЧИ ЗМІНЕНОЇ ВЕРСІЇ ДОКУМЕНТУ, АБО БУДЬ-ЯКИЙ ПОСТАЧАЛЬНИК БУДЬ-ЯКОЇ З ЦИХ СТОРІН, НЕ НЕСЕ ВІДПОВІДАЛЬНІСТЬ ПЕРЕД БУДЬ-ЯКОЮ ОСОБОЮ ЗА БУДЬ-ЯКІ ПРЯМІ, НЕПРЯМІ, ОСОБЛИВІ, ВИПАДКОВІ, АБО ІСТОТНІ ЗБИТКИ БУДЬ-ЯКОГО ХАРАКТЕРУ ВКЛЮЧАЮЧИ, АЛЕ НЕ ОБМЕЖУЮЧИСЬ, ЗБИТКАМИ ВІД ВТРАТИ ПРЕСТИЖУ, ЗУПИНКИ РОБОТИ, ЗБОЇВ АБО НЕСПРАВНОСТЕЙ КОМП'ЮТЕРА, АБО БУДЬ-ЯКІ ІНШІ ЗБИТКИ АБО ВТРАТИ ЩО ВИНИКЛИ БЕЗВІДНОСНО АБО ВНАСЛІДОК ВИКОРИСТАННЯ ЦЬОГО ДОКУМЕНТУ ТА ЗМІНЕНИХ ВЕРСІЙ ЦЬОГО ДОКУМЕНТУ, НАВІТЬ ЯКЩО ЦІ СТОРОНИ, МОЖЛИВО, БУЛИ ПРОІНФОРМОВАНІ ПРО МОЖЛИВІСТЬ ТАКИХ ЗБИТКІВ.</para></listitem></orderedlist></para>
+	<para>ДОКУМЕНТ ТА ЗМІНЕНІ ВЕРСІЇ ЦЬОГО ДОКУМЕНТУ ПОСТАЧАЮТЬСЯ НА УМОВАХ ВІЛЬНОЇ ЛІЦЕНЗІЇ ДЛЯ ДОКУМЕНТАЦІЇ GNU З ПОДАЛЬШИМ РОЗУМІННЯМ ЩО: <orderedlist>
+		<listitem>
+		  <para>ДОКУМЕНТ НАДАЄТЬСЯ "ЯК Є", БЕЗ БУДЬ-ЯКИХ ГАРАНТІЇ, ЯВНИХ ЧИ НЕЯВНИХ, ВКЛЮЧАЮЧИ, АЛЕ НЕ ОБМЕЖУЮЧИСЬ, ГАРАНТІЙ ЩО ЦЕЙ ДОКУМЕНТ ЧИ ЗМІНЕНА ВЕРСІЯ ДОКУМЕНТА ВІЛЬНІ ВІД ДЕФЕКТІВ, ПРИДАТНІ ДО ПРОДАЖУ, ВІДПОВІДАЮТЬ ПЕВНІЙ МЕТІ АБО НЕ ПОРУШУЮТЬ ЧИЇСЬ ПРАВА. ВЕСЬ РИЗИК ЗА ЯКІСТЬ, ТОЧНІСТЬ, ТА ЧИННІСТЬ ЦЬОГО ДОКУМЕНТУ АБО ЙОГО ЗМІНЕНИХ ВЕРСІЙ ЛЕЖИТЬ НА ВАС.  ЯКЩО БУДЬ-ЯКИЙ ДОКУМЕНТ ЧИ ЗМІНЕНА ВЕРСІЯ БУДУТЬ ВИЗНАНІ ДЕФЕКТНИМИ У БУДЬ-ЯКОМУ ВІДНОШЕННІ, ВИ (НЕ ПОЧАТКОВИЙ УКЛАДАЧ, АВТОР АБО БУДЬ-ЯКИЙ СПІВАВТОР) БЕРЕТЕ НА СЕБЕ ВИТРАТИ ЗА БУДЬ-ЯКЕ НЕОБХІДНЕ ОБСЛУГОВУВАННЯ, РЕМОНТ ЧИ ВИПРАВЛЕННЯ. ЦЯ ВІДМОВА ВІД ГАРАНТІЙ СКЛАДАЄ ВАЖЛИВУ ЧАСТИНУ ЦІЄЇ ЛІЦЕНЗІЇ. НЕ ДОПУСКАЄТЬСЯ ВИКОРИСТАННЯ ЦЬОГО ДОКУМЕНТУ АБО ЙОГО ЗМІНЕНОЇ ВЕРСІЇ БЕЗ ПРИЙНЯТТЯ ЦІЄЇ ВІДМОВИ; ТА</para>
+		</listitem>
+		<listitem>
+		  <para>НІ ЗА ЯКИХ ОБСТАВИН ТА ЗА БУДЬ-ЯКОГО ЗАКОНОДАВСТВА, ЧИ ТО ГРОМАДЯНСЬКОЇ ВІДПОВІДАЛЬНОСТІ (ВКЛЮЧАЮЧИ ХАЛАТНІСТЬ), ДОГОВОРУ, ЧИ ЧОГОСЬ ІНШОГО, АВТОР, ПОЧАТКОВИЙ УКЛАДАЧ, БУДЬ-ЯКИЙ СПІВАВТОР, АБО ДИСТРИБ'ЮТОР ДОКУМЕНТУ ЧИ ЗМІНЕНОЇ ВЕРСІЇ ДОКУМЕНТУ, АБО БУДЬ-ЯКИЙ ПОСТАЧАЛЬНИК БУДЬ-ЯКОЇ З ЦИХ СТОРІН, НЕ НЕСЕ ВІДПОВІДАЛЬНІСТЬ ПЕРЕД БУДЬ-ЯКОЮ ОСОБОЮ ЗА БУДЬ-ЯКІ ПРЯМІ, НЕПРЯМІ, ОСОБЛИВІ, ВИПАДКОВІ, АБО ІСТОТНІ ЗБИТКИ БУДЬ-ЯКОГО ХАРАКТЕРУ ВКЛЮЧАЮЧИ, АЛЕ НЕ ОБМЕЖУЮЧИСЬ, ЗБИТКАМИ ВІД ВТРАТИ ПРЕСТИЖУ, ЗУПИНКИ РОБОТИ, ЗБОЇВ АБО НЕСПРАВНОСТЕЙ КОМП'ЮТЕРА, АБО БУДЬ-ЯКІ ІНШІ ЗБИТКИ АБО ВТРАТИ ЩО ВИНИКЛИ БЕЗВІДНОСНО АБО ВНАСЛІДОК ВИКОРИСТАННЯ ЦЬОГО ДОКУМЕНТУ ТА ЗМІНЕНИХ ВЕРСІЙ ЦЬОГО ДОКУМЕНТУ, НАВІТЬ ЯКЩО ЦІ СТОРОНИ, МОЖЛИВО, БУЛИ ПРОІНФОРМОВАНІ ПРО МОЖЛИВІСТЬ ТАКИХ ЗБИТКІВ.</para>
+		</listitem>
+	  </orderedlist></para>
   </legalnotice>