Rename kdebugdialog -> tdedebugdialog

5 files changed, 22 insertions, 22 deletions

diff --git a/doc/kdebugdialog/CMakeLists.txt b/doc/tdedebugdialog/CMakeLists.txt
index 3f3ce3cf2..d83bc9162 100644
--- a/doc/kdebugdialog/CMakeLists.txt
+++ b/doc/tdedebugdialog/CMakeLists.txt
@@ -9,4 +9,4 @@
 #
 #################################################
 
-tde_create_handbook( DESTINATION kdebugdialog )
+tde_create_handbook( DESTINATION tdedebugdialog )
diff --git a/doc/kdebugdialog/Makefile.am b/doc/tdedebugdialog/Makefile.am
index e786da562..e786da562 100644
--- a/doc/kdebugdialog/Makefile.am
+++ b/doc/tdedebugdialog/Makefile.am
diff --git a/doc/kdebugdialog/index.docbook b/doc/tdedebugdialog/index.docbook
index fefe25ce9..e23d599af 100644
--- a/doc/kdebugdialog/index.docbook
+++ b/doc/tdedebugdialog/index.docbook
@@ -1,8 +1,8 @@
 <?xml version="1.0" ?>
 <!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
 "dtd/kdex.dtd" [
-  <!ENTITY kdebugdialog "<application>KDebugDialog</application>">
-  <!ENTITY kappname "&kdebugdialog;">
+  <!ENTITY tdedebugdialog "<application>TDEDebugDialog</application>">
+  <!ENTITY kappname "&tdedebugdialog;">
   <!ENTITY % addindex "IGNORE">
   <!ENTITY % English "INCLUDE" > <!-- change language only here -->
   
@@ -11,7 +11,7 @@
 
 <book lang="&language;">
 <bookinfo>
-<title>The &kdebugdialog; Handbook</title>
+<title>The &tdedebugdialog; Handbook</title>
 
 <authorgroup>
 <author>&David.Faure; &David.Faure.mail;</author>
@@ -22,22 +22,22 @@
 <releaseinfo>0.03.00</releaseinfo>
 
 <abstract>
-<para>This document describes &kdebugdialog;.</para>
+<para>This document describes &tdedebugdialog;.</para>
 </abstract>
 
 <keywordset>
 <keyword>KDE</keyword>
-<keyword>KDebugdialog</keyword>
+<keyword>TDEDebugdialog</keyword>
 </keywordset>
 </bookinfo>
 
 <chapter id="Introduction">
-<title>What is KDebugDialog?</title>
+<title>What is TDEDebugDialog?</title>
 
 <para>It is a dialog box for managing diagnostic messages at runtime.
 </para>
 
-<para>If you simply start <command>kdebugdialog</command>, you will
+<para>If you simply start <command>tdedebugdialog</command>, you will
 see a list of <quote>areas</quote>, that can be disabled or enabled. A
 <function>kdDebug(area)</function> call in the code will show
 something in the debug output only if the area is enabled.</para>
@@ -60,7 +60,7 @@ the syntax start-end. Thus a valid entry could be:
 </varlistentry>
 </variablelist>
 
-<para>If you start <command>kdebugdialog</command>
+<para>If you start <command>tdedebugdialog</command>
 <option>--fullmode</option>, then for every severity level you can
 define separately what should be done with the diagnostic messages of
 that level, and the same for each debug area.</para>
@@ -116,7 +116,7 @@ your entries apply immediately and are saved in
 ones are restored.</para>
 
 <para>Credits to Kalle Dalheimer for the original version of
-&kdebugdialog;</para>
+&tdedebugdialog;</para>
 
 </chapter>
 
diff --git a/doc/userguide/credits-and-license.docbook b/doc/userguide/credits-and-license.docbook
index cc1872d2e..b4395aed1 100644
--- a/doc/userguide/credits-and-license.docbook
+++ b/doc/userguide/credits-and-license.docbook
@@ -105,7 +105,7 @@ The &tde; Team thanks and acknowledges the original &kde; contributors of this g
 <itemizedlist>
 <listitem><para>Wrote <xref linkend="configuring-toolbars"/>.</para>
 </listitem>
-<listitem><para>Wrote <xref linkend="kdebugdialog" />.</para>
+<listitem><para>Wrote <xref linkend="tdedebugdialog" />.</para>
 </listitem>
 </itemizedlist>
 
diff --git a/doc/userguide/under-the-hood.docbook b/doc/userguide/under-the-hood.docbook
index 62ab1a5ec..6757cc8d9 100644
--- a/doc/userguide/under-the-hood.docbook
+++ b/doc/userguide/under-the-hood.docbook
@@ -385,17 +385,17 @@ window.</para></listitem>
 
 </sect1>
 
-<sect1 id="kdebugdialog">
+<sect1 id="tdedebugdialog">
 
-<title>&kdebugdialog;  - Controlling &tde;'s Debugging Output</title>
+<title>&tdedebugdialog;  - Controlling &tde;'s Debugging Output</title>
 
-<sect2 id="kdebugdialog-basic-usage">
+<sect2 id="tdedebugdialog-basic-usage">
 <title>Basic Usage</title>
 
-<para>&kdebugdialog; is not in the &kmenu; by default. You will need to run
+<para>&tdedebugdialog; is not in the &kmenu; by default. You will need to run
 it from the shell or from the mini-CLI <!-- link to CLI, for sure --> with
-the command <userinput><command>kdebugdialog</command></userinput>.
-&kdebugdialog; pops up a window with a long list of debugging areas. Each
+the command <userinput><command>tdedebugdialog</command></userinput>.
+&tdedebugdialog; pops up a window with a long list of debugging areas. Each
 area has a checkbox that you can check or uncheck <!-- perhaps
 select/deselect --> in order to enable or disable debugging output for
 that part of &tde;.</para>
@@ -416,13 +416,13 @@ buttons which will cause &tde; to produce a mountain of debugging output, or
 very little.</para>
 </sect2>
 
-<sect2 id="kdebugdialog-fullmode">
-<title>KDebugDialog in full mode</title>
+<sect2 id="tdedebugdialog-fullmode">
+<title>TDEDebugDialog in full mode</title>
 
-<!-- this text partly taken from the kdebugdialog handbook -->
+<!-- this text partly taken from the tdedebugdialog handbook -->
 
-<para>In full mode, which is what you get when you start kdebugdialog as
-<userinput><command>kdebugdialog</command>
+<para>In full mode, which is what you get when you start tdedebugdialog as
+<userinput><command>tdedebugdialog</command>
 <option>--fullmode</option></userinput>, the same list of debugging areas
 as in plain mode is available, but you can select only one at a time from a
 drop-down <!-- combo? --> box. You may then  independently set the output