Beautify docbook files

1 files changed, 98 insertions, 298 deletions

diff --git a/tde-i18n-nl/docs/tdewebdev/klinkstatus/index.docbook b/tde-i18n-nl/docs/tdewebdev/klinkstatus/index.docbook
index 7bbf1b900c6..5c9c1877484 100644
--- a/tde-i18n-nl/docs/tdewebdev/klinkstatus/index.docbook
+++ b/tde-i18n-nl/docs/tdewebdev/klinkstatus/index.docbook
@@ -1,15 +1,10 @@
 <?xml version="1.0" ?>
 <!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
-  <!ENTITY klinkstatus "<application
->KLinkStatus</application
->">
-  <!ENTITY kappname "&klinkstatus;"
-><!-- Do *not* replace kappname-->
-  <!ENTITY package "kde-module"
-><!-- tdebase, tdeadmin, etc -->
+  <!ENTITY klinkstatus "<application>KLinkStatus</application>">
+  <!ENTITY kappname "&klinkstatus;"><!-- Do *not* replace kappname-->
+  <!ENTITY package "kde-module"><!-- tdebase, tdeadmin, etc -->
   <!ENTITY % addindex "IGNORE">
-  <!ENTITY % Dutch "INCLUDE"
-><!-- change language only here -->
+  <!ENTITY % Dutch "INCLUDE"><!-- change language only here -->
   
   
   <!-- Do not define any other entities; instead, use the entities
@@ -32,8 +27,7 @@ You may freely use this template for writing any sort of KDE documentation.
 If you have any changes or improvements, please let us know.
 
 Remember:
-- in XML, the case of the <tags
-> and attributes is relevant ;
+- in XML, the case of the <tags> and attributes is relevant ;
 - also, quote all attributes.
 
 Please don't forget to remove all these comments in your final documentation,
@@ -50,22 +44,10 @@ thanks ;-).
 as Authors, publish date, the abstract, and Keywords -->
 
 <bookinfo>
-<title
->Het handboek van &klinkstatus;</title>
+<title>Het handboek van &klinkstatus;</title>
 
 <authorgroup>
-<author
-><firstname
-></firstname
-> <othername
-></othername
-> <surname
->Paulo Moura Guedes</surname
-> <affiliation
-> <address
-><email
->moura&#64;tdewebdev&#46;org</email
-></address>
+<author><firstname></firstname> <othername></othername> <surname>Paulo Moura Guedes</surname> <affiliation> <address><email>moura&#64;tdewebdev&#46;org</email></address>
 </affiliation>
 </author>
 </authorgroup>
@@ -73,19 +55,14 @@ as Authors, publish date, the abstract, and Keywords -->
 &Sander.Koning;&Tom.Albers; 
 
 <copyright>
-<year
->2004</year>
-<!--<year
->2004</year
->-->
-<holder
->Paulo Moura Guedes</holder>
+<year>2004</year>
+<!--<year>2004</year>-->
+<holder>Paulo Moura Guedes</holder>
 </copyright>
 <!-- Translators: put here the copyright notice of the translation -->
 <!-- Put here the FDL notice.  Read the explanation in fdl-notice.docbook
      and in the FDL itself on how to use it. -->
-<legalnotice
->&FDLNotice;</legalnotice>
+<legalnotice>&FDLNotice;</legalnotice>
 
 <!-- Date and version information of the documentation
 Don't forget to include this last date and this last revision number, we
@@ -94,16 +71,13 @@ Please respect the format of the date (YYYY-MM-DD) and of the version
 (V.MM.LL), it could be used by automation scripts.
 Do NOT change these in the translation. -->
 
-<date
->2004-04-29</date>
-<releaseinfo
->0&#46;1&#46;3</releaseinfo>
+<date>2004-04-29</date>
+<releaseinfo>0&#46;1&#46;3</releaseinfo>
 
 <!-- Abstract about this handbook -->
 
 <abstract>
-<para
->&klinkstatus; is een KDE-programma dat koppelingen controleert. </para>
+<para>&klinkstatus; is een KDE-programma dat koppelingen controleert. </para>
 </abstract>
 
 <!-- This is a set of Keywords for indexing by search engines.
@@ -111,14 +85,10 @@ Please at least include KDE, the KDE package it is in, the name
  of your application, and a few relevant keywords. -->
 
 <keywordset>
-<keyword
->KDE</keyword>
-<keyword
->KLinkStatus</keyword>
-<keyword
->koppelingscontrole</keyword>
-<keyword
->validatie</keyword>
+<keyword>KDE</keyword>
+<keyword>KLinkStatus</keyword>
+<keyword>koppelingscontrole</keyword>
+<keyword>validatie</keyword>
 </keywordset>
 
 </bookinfo>
@@ -133,21 +103,18 @@ discretion. Other chapters should not be left out in order to maintain a
 consistent documentation style across all KDE apps. -->
 
 <chapter id="introduction">
-<title
->Inleiding</title>
+<title>Inleiding</title>
 
 <!-- The introduction chapter contains a brief introduction for the
 application that explains what it does and where to report
 problems. Basically a long version of the abstract.  Don't include a
 revision history. (see installation appendix comment) -->
 
-<para
->&klinkstatus; is een KDE-programma dat koppelingen controleert. U kunt er interne en externe koppelingen in uw hele website of in een enkele pagina mee controleren op diverse diepteniveaus. U kunt ook lokale bestanden, ftp, fish, enzovoort doorzoeken omdat KLinkStatus TDEIO gebruikt. Koppelingen kunnen tegelijkertijd doorzocht worden om de prestatie te verbeteren. Problemen of verzoeken kunt u doorgeven op http://linkstatus.paradigma.co.pt/bugs/. </para>
+<para>&klinkstatus; is een KDE-programma dat koppelingen controleert. U kunt er interne en externe koppelingen in uw hele website of in een enkele pagina mee controleren op diverse diepteniveaus. U kunt ook lokale bestanden, ftp, fish, enzovoort doorzoeken omdat KLinkStatus TDEIO gebruikt. Koppelingen kunnen tegelijkertijd doorzocht worden om de prestatie te verbeteren. Problemen of verzoeken kunt u doorgeven op http://linkstatus.paradigma.co.pt/bugs/. </para>
 </chapter>
 
 <chapter id="using-klinkstatus">
-<title
->&klinkstatus; gebruiken</title>
+<title>&klinkstatus; gebruiken</title>
 
 <!-- This chapter should tell the user how to use your app. You should use as
 many sections (Chapter, Sect1, Sect3, etc...) as is necessary to fully document
@@ -159,8 +126,7 @@ your application. -->
 patent issues. -->
 
 <screenshot>
-<screeninfo
->Dit is een schermafdruk van &klinkstatus;</screeninfo>
+<screeninfo>Dit is een schermafdruk van &klinkstatus;</screeninfo>
 	<mediaobject>
 	  <imageobject>
 	    <imagedata fileref="screenshot.png" format="PNG"/>
@@ -169,8 +135,7 @@ patent issues. -->
 	    <imagedata fileref="screenshot.eps" format="EPS"/>
 	  </imageobject>
 	  <textobject>
-	    <phrase
->Schermafdruk</phrase>
+	    <phrase>Schermafdruk</phrase>
 	  </textobject>
 	</mediaobject>
 </screenshot>
@@ -178,20 +143,16 @@ patent issues. -->
 
 
 <sect1 id="klinkstatus-features">
-<title
->Meer mogelijkheden van &klinkstatus;</title>
+<title>Meer mogelijkheden van &klinkstatus;</title>
 
-<para
-></para>
-<para
-></para>
+<para></para>
+<para></para>
 
 </sect1>
 </chapter>
 
 <chapter id="commands">
-<title
->Opdrachtengids</title>
+<title>Opdrachtengids</title>
 
 <!-- (OPTIONAL, BUT RECOMMENDED) This chapter should list all of the
 application windows and their menubar and toolbar commands for easy reference.
@@ -200,79 +161,23 @@ menus or toolbars. This may not be necessary for small apps or apps with no tool
 or menu bars. -->
 
 <sect1 id="klinkstatus-mainwindow">
-<title
->Het hoofdvenster van &klinkstatus;</title>
+<title>Het hoofdvenster van &klinkstatus;</title>
 
 <sect2>
-<title
->Het menu Bestand</title>
+<title>Het menu Bestand</title>
 <para>
 <variablelist>
 <varlistentry>
-<term
-><menuchoice
-><shortcut
-> <keycombo action="simul"
->&Ctrl;<keycap
->N</keycap
-></keycombo
-> </shortcut
-> <guimenu
->Bestand</guimenu
-> <guimenuitem
->Nieuwe koppelingcontrole</guimenuitem
-> </menuchoice
-></term>
-<listitem
-><para
-><action
->Maakt een nieuwe sessie, als er geen lege beschikbaar is.</action
-></para
-></listitem>
+<term><menuchoice><shortcut> <keycombo action="simul">&Ctrl;<keycap>N</keycap></keycombo> </shortcut> <guimenu>Bestand</guimenu> <guimenuitem>Nieuwe koppelingcontrole</guimenuitem> </menuchoice></term>
+<listitem><para><action>Maakt een nieuwe sessie, als er geen lege beschikbaar is.</action></para></listitem>
 </varlistentry>
 <varlistentry>
-<term
-><menuchoice
-><shortcut
-> <keycombo action="simul"
->&Ctrl;<keycap
->O</keycap
-></keycombo
-> </shortcut
-> <guimenu
->Bestand</guimenu
-> <guimenuitem
->URL-adres openen </guimenuitem
-> </menuchoice
-></term>
-<listitem
-><para
-><action
->Opent een URL-adres</action
-></para
-></listitem>
+<term><menuchoice><shortcut> <keycombo action="simul">&Ctrl;<keycap>O</keycap></keycombo> </shortcut> <guimenu>Bestand</guimenu> <guimenuitem>URL-adres openen </guimenuitem> </menuchoice></term>
+<listitem><para><action>Opent een URL-adres</action></para></listitem>
 </varlistentry>
 <varlistentry>
-<term
-><menuchoice
-><shortcut
-> <keycombo action="simul"
->&Ctrl;<keycap
->W</keycap
-></keycombo
-> </shortcut
-> <guimenu
->Bestand</guimenu
-> <guimenuitem
->Tabblad sluiten </guimenuitem
-> </menuchoice
-></term>
-<listitem
-><para
-><action
->Sluit het huidige tabblad.</action
-></para
-></listitem>
+<term><menuchoice><shortcut> <keycombo action="simul">&Ctrl;<keycap>W</keycap></keycombo> </shortcut> <guimenu>Bestand</guimenu> <guimenuitem>Tabblad sluiten </guimenuitem> </menuchoice></term>
+<listitem><para><action>Sluit het huidige tabblad.</action></para></listitem>
 </varlistentry>
 </variablelist>
 </para>
@@ -280,10 +185,7 @@ or menu bars. -->
 </sect2>
 
 <sect2>
-<title
->Het menu <guimenu
->Help</guimenu
-></title>
+<title>Het menu <guimenu>Help</guimenu></title>
 &help.menu.documentation; </sect2>
 
 </sect1>
@@ -291,8 +193,7 @@ or menu bars. -->
 
 <!--
 <chapter id="developers">
-<title
->Developer's Guide to &klinkstatus;</title>
+<title>Developer's Guide to &klinkstatus;</title>
 -->
 <!-- (OPTIONAL) A Programming/Scripting reference chapter should be
 used for apps that use plugins or that provide their own scripting hooks
@@ -306,173 +207,112 @@ taken from that reference and shortened a bit for readability.
 
 <refentry id="re-1007-unmanagechildren-1">
 <refmeta>
-<refentrytitle
->XtUnmanageChildren</refentrytitle>
-<refmiscinfo
->Xt - Geometry Management</refmiscinfo>
+<refentrytitle>XtUnmanageChildren</refentrytitle>
+<refmiscinfo>Xt - Geometry Management</refmiscinfo>
 </refmeta>
 <refnamediv>
-<refname
->XtUnmanageChildren
+<refname>XtUnmanageChildren
 </refname>
-<refpurpose
->remove a list of children from a parent widget's managed
+<refpurpose>remove a list of children from a parent widget's managed
 list.
-<indexterm id="ix-1007-unmanagechildren-1"
-><primary
->widgets</primary
-><secondary
->removing</secondary
-></indexterm>
-<indexterm id="ix-1007-unmanagechildren-2"
-><primary
->XtUnmanageChildren</primary
-></indexterm
-> 
+<indexterm id="ix-1007-unmanagechildren-1"><primary>widgets</primary><secondary>removing</secondary></indexterm>
+<indexterm id="ix-1007-unmanagechildren-2"><primary>XtUnmanageChildren</primary></indexterm> 
 </refpurpose>
 
 </refnamediv>
 <refsynopsisdiv>
 <refsynopsisdivinfo>
-<date
->4 March 1996</date>
+<date>4 March 1996</date>
 </refsynopsisdivinfo>
-<synopsis
->
+<synopsis>
 void XtUnmanageChildren(<replaceable class="parameter">children</replaceable>, <replaceable class="parameter">num_children</replaceable>)
     WidgetList <replaceable class="parameter">children</replaceable>;
     Cardinal <replaceable class="parameter">num_children</replaceable>;
 </synopsis>
 
 <refsect2 id="r2-1007-unmanagechildren-1">
-<title
->Inputs</title>
+<title>Inputs</title>
 <variablelist>
 <varlistentry>
-<term
-><replaceable class="parameter"
->children</replaceable>
+<term><replaceable class="parameter">children</replaceable>
 </term>
 <listitem>
-<para
->Specifies an array of child widgets. Each child must be of
+<para>Specifies an array of child widgets. Each child must be of
 class RectObj or any subclass thereof.
 </para>
 </listitem>
 </varlistentry>
 <varlistentry>
-<term
-><replaceable class="parameter"
->num_children</replaceable>
+<term><replaceable class="parameter">num_children</replaceable>
 </term>
 <listitem>
-<para
->Specifies the number of elements in <replaceable class="parameter"
->children</replaceable
->.
+<para>Specifies the number of elements in <replaceable class="parameter">children</replaceable>.
 </para>
 </listitem>
 </varlistentry>
 </variablelist>
-</refsect2
-></refsynopsisdiv>
+</refsect2></refsynopsisdiv>
 
 <refsect1 id="r1-1007-unmanagechildren-1">
-<title
->Description
+<title>Description
 </title>
-<para
-><function
->XtUnmanageChildren()</function
-> unmaps the specified widgets
+<para><function>XtUnmanageChildren()</function> unmaps the specified widgets
 and removes them from their parent's geometry management.
 The widgets will disappear from the screen, and (depending
 on its parent) may no longer have screen space allocated for
 them.
 </para>
-<para
->Each of the widgets in the <replaceable class="parameter"
->children</replaceable
-> array must have
+<para>Each of the widgets in the <replaceable class="parameter">children</replaceable> array must have
 the same parent.
 </para>
-<para
->See the &ldquo;Algorithm&rdquo; section below for full details of the
+<para>See the &ldquo;Algorithm&rdquo; section below for full details of the
 widget unmanagement procedure.
 </para>
 </refsect1>
 
 <refsect1 id="r1-1007-unmanagechildren-2">
-<title
->Usage</title>
-<para
->Unmanaging widgets is the usual method for temporarily
+<title>Usage</title>
+<para>Unmanaging widgets is the usual method for temporarily
 making them invisible.  They can be re-managed with
-<function
->XtManageChildren()</function
->.
+<function>XtManageChildren()</function>.
 </para>
-<para
->You can unmap a widget, but leave it under geometry
-management by calling <function
->XtUnmapWidget()</function
->.  You can
+<para>You can unmap a widget, but leave it under geometry
+management by calling <function>XtUnmapWidget()</function>.  You can
 destroy a widget's window without destroying the widget by
-calling <function
->XtUnrealizeWidget()</function
->.  You can destroy a
-widget completely with <function
->XtDestroyWidget()</function
->.
+calling <function>XtUnrealizeWidget()</function>.  You can destroy a
+widget completely with <function>XtDestroyWidget()</function>.
 </para>
-<para
->If you are only going to unmanage a single widget, it is
-more convenient to call <function
->XtUnmanageChild()</function
->.  It is
-often more convenient to call <function
->XtUnmanageChild()</function>
+<para>If you are only going to unmanage a single widget, it is
+more convenient to call <function>XtUnmanageChild()</function>.  It is
+often more convenient to call <function>XtUnmanageChild()</function>
 several times than it is to declare and initialize an array
-of widgets to pass to <function
->XtUnmanageChildren()</function
->.  Calling
-<function
->XtUnmanageChildren()</function
-> is more efficient, however,
-because it only calls the parent's <function
->change_managed()</function>
+of widgets to pass to <function>XtUnmanageChildren()</function>.  Calling
+<function>XtUnmanageChildren()</function> is more efficient, however,
+because it only calls the parent's <function>change_managed()</function>
 method once.
 </para>
 </refsect1>
 
 <refsect1 id="r1-1007-unmanagechildren-3">
-<title
->Algorithm
+<title>Algorithm
 </title>
-<para
-><function
->XtUnmanageChildren()</function
-> performs the following:
+<para><function>XtUnmanageChildren()</function> performs the following:
 </para>
 <variablelist>
 <varlistentry>
-<term
->-
+<term>-
 </term>
 <listitem>
-<para
->Ignores the child if it already is unmanaged or is being
+<para>Ignores the child if it already is unmanaged or is being
 destroyed.
 </para>
 </listitem>
 </varlistentry>
 <varlistentry>
-<term
->-
+<term>-
 </term>
 <listitem>
-<para
->Otherwise, if the child is realized, it makes it nonvisible
+<para>Otherwise, if the child is realized, it makes it nonvisible
 by unmapping it.
 </para>
 </listitem>
@@ -482,15 +322,10 @@ by unmapping it.
 </refsect1>
 
 <refsect1 id="r1-1007-unmanagechildren-4">
-<title
->Structures</title>
-<para
->The <type
->WidgetList</type
-> type is simply an array of widgets:
+<title>Structures</title>
+<para>The <type>WidgetList</type> type is simply an array of widgets:
 </para>
-<screen id="sc-1007-unmanagechildren-1"
->typedef Widget *WidgetList;
+<screen id="sc-1007-unmanagechildren-1">typedef Widget *WidgetList;
 </screen>
 </refsect1>
 </refentry>
@@ -500,8 +335,7 @@ by unmapping it.
 
 <!--
 <chapter id="faq">
-<title
->Questions and Answers</title>
+<title>Questions and Answers</title>
 -->
 <!-- (OPTIONAL but recommended) This chapter should include all of the silly
 (and not-so-silly) newbie questions that fill up your mailbox. This chapter
@@ -521,25 +355,19 @@ application work. -->
 <qandaentry>
 -
 <question>
-<para
->My Mouse doesn't work. How do I quit &klinkstatus;?</para>
+<para>My Mouse doesn't work. How do I quit &klinkstatus;?</para>
 </question>
 <answer>
-<para
->You silly goose! Check out the <link linkend="commands"
->Commands
-Section</link
-> for the answer.</para>
+<para>You silly goose! Check out the <link linkend="commands">Commands
+Section</link> for the answer.</para>
 </answer>
 </qandaentry>
 <qandaentry>
 <question>
-<para
->Why can't I twiddle my documents?</para>
+<para>Why can't I twiddle my documents?</para>
 </question>
 <answer>
-<para
->You can only twiddle your documents if you have the foobar.lib
+<para>You can only twiddle your documents if you have the foobar.lib
 installed.</para>
 </answer>
 
@@ -556,65 +384,45 @@ contributors here. The license for your software should then be included below
 the credits with a reference to the appropriate license file included in the KDE
 distribution. -->
 
-<title
->Dankbetuigingen en licentie</title>
+<title>Dankbetuigingen en licentie</title>
 
-<para
->&klinkstatus; </para>
-<para
->Programma copyright 2004 Paulo Moura Guedes <email
->pmg&#64;netcabo&#46;pt</email
-> </para>
+<para>&klinkstatus; </para>
+<para>Programma copyright 2004 Paulo Moura Guedes <email>pmg&#64;netcabo&#46;pt</email> </para>
 <!--
 <para>
 Contributors:
 <itemizedlist>
-<listitem
-><para
->Konqui the KDE Dragon <email
->konqui@kde.org</email
-></para>
+<listitem><para>Konqui the KDE Dragon <email>konqui@kde.org</email></para>
 </listitem>
-<listitem
-><para
->Tux the Linux Penguin <email
->tux@linux.org</email
-></para>
+<listitem><para>Tux the Linux Penguin <email>tux@linux.org</email></para>
 </listitem>
 </itemizedlist>
 </para>
 -->
-<para
->Documentatie copyright 2004 Paulo Moura Guedes <email
->pmg&#64;netcabo&#46;pt</email
-> </para>
+<para>Documentatie copyright 2004 Paulo Moura Guedes <email>pmg&#64;netcabo&#46;pt</email> </para>
 
 &meld.fouten;&vertaling.sander;&nagelezen.tom; 
 &underFDL; &underGPL; </chapter>
 
 <appendix id="installation">
-<title
->Installatie</title>
+<title>Installatie</title>
 
 <sect1 id="getting-klinkstatus">
-<title
->&klinkstatus; verkrijgen</title>
+<title>&klinkstatus; verkrijgen</title>
 
 <!-- This first entity contains boiler plate for applications that are
 part of KDE CVS.  You should remove it if you are releasing your
 application --> 
 
 <!--&install.intro.documentation;-->
-<para
->http://kde-apps.org </para>
+<para>http://kde-apps.org </para>
 
 </sect1>
 
 
 <!--
 <sect1 id="requirements">
-<title
->Requirements</title>
+<title>Requirements</title>
 
 List any special requirements for your application here. This should include:
 .Libraries or other software that is not included in tdesupport,
@@ -635,9 +443,7 @@ platform and configuration.
 
 <para>
 All required libraries as well as &klinkstatus; itself can be found
-on <ulink url="ftp://ftp.klinkstatus.org"
->The &klinkstatus; home page</ulink
->.
+on <ulink url="ftp://ftp.klinkstatus.org">The &klinkstatus; home page</ulink>.
 </para>
 -->
 <!-- For a list of updates, you may refer to the application web site
@@ -645,24 +451,18 @@ or the ChangeLog file, or ... -->
 <!--
 <para>
 You can find a list of changes at <ulink
-url="http://apps.kde.org/klinkstatus"
->http://apps.kde.org/klinkstatus</ulink
->.
+url="http://apps.kde.org/klinkstatus">http://apps.kde.org/klinkstatus</ulink>.
 </para>
 </sect1>
 -->
 <sect1 id="compilation">
-<title
->Compileren en installeren</title>
+<title>Compileren en installeren</title>
 &install.compile.documentation; </sect1>
 <!--
 <sect1 id="configuration">
-<title
->Configuration</title>
+<title>Configuration</title>
 
-<para
->Don't forget to tell your system to start the <filename
->dtd</filename>
+<para>Don't forget to tell your system to start the <filename>dtd</filename>
 dicer-toaster daemon first, or &klinkstatus; won't work !</para>
 
 </sect1>