Additional kde to tde renaming

1 files changed, 8 insertions, 8 deletions

diff --git a/doc/kde_app_devel/index.docbook b/doc/kde_app_devel/index.docbook
index 2ec1f0e4..0ebf7e71 100644
--- a/doc/kde_app_devel/index.docbook
+++ b/doc/kde_app_devel/index.docbook
@@ -525,10 +525,10 @@ and the <ulink url="doc.trolltech.com">Qt online reference</ulink>.
 The main KDE libraries you'll be using for creating your own KDE applications are:
 <itemizedlist>
 <listitem><para>
-the kdecore library, containing all classes that are non-visible elements to provide application functionality
+the tdecore library, containing all classes that are non-visible elements to provide application functionality
 </para></listitem>
 <listitem><para>
-the kdeui library, containing user interface elements like menubars, toolbars, etc.
+the tdeui library, containing user interface elements like menubars, toolbars, etc.
 </para></listitem>
 <listitem><para>
 the kfile library, containing the file selection dialogs
@@ -539,7 +539,7 @@ the kfile library, containing the file selection dialogs
 Additionally, for specific solutions KDE offers the following libraries:
 <itemizedlist>
 <listitem><para>
-the kdefx library, containing pixmaps, image effects the KStyle extension to QStyle
+the tdefx library, containing pixmaps, image effects the KStyle extension to QStyle
 </para></listitem>
 <listitem><para>
 the khtml library, containing KDE's html component
@@ -590,7 +590,7 @@ You see that first we have changed from <classname>QApplication</classname> to <
 </classname>. Further, we had to change the previously used <methodname>setMainWidget()</methodname> method 
 to <methodname>setTopWidget</methodname>, which <classname>KApplication</classname> uses to set the main 
 widget. That's it! Your first KDE application is ready - you only have to tell the compiler the KDE 
-include path and the linker to link in the kdecore library with -lkdecore. 
+include path and the linker to link in the tdecore library with -ltdecore. 
 </para>
 <para>
 As you now know what at least the <function>main()</function> function provides generally and how an 
@@ -601,7 +601,7 @@ mentioned before and see the effects.
 <para>
 What you should have looked into additionally until now is the reference documentation for Qt, 
 especially the <classname>QApplication</classname>, <classname>QWidget</classname> and <classname>QObject
-</classname> class and the kdecore library documentation for the <classname>KApplication</classname> class. 
+</classname> class and the tdecore library documentation for the <classname>KApplication</classname> class. 
 The <ulink url="developer.kde.org/documentation/library/libraryref.html">KDE Library Reference handbook</ulink> 
 also covers a complete description about the invocation of the <classname>QApplication</classname> and 
 <classname>KApplication</classname> constructors including command-line argument processing. 
@@ -803,7 +803,7 @@ the compilation phase.
    -Wall -pedantic -W -Wpointer-arith -Wmissing-prototypes -Wwrite-strings -ansi -D_XOPEN_SOURCE=500 
    -D_BSD_SOURCE -Wcast-align -Wconversion -O2 -fno-exceptions -fno-check-new -o kscribble_client -R 
    /usr/local/trinity/lib -R /usr/lib/qt/lib -R /usr/X11R6/lib -L/usr/X11R6/lib -L/usr/lib/qt/lib 
-   -L/usr/local/trinity/lib kscribble_client.o -lkdecore 
+   -L/usr/local/trinity/lib kscribble_client.o -ltdecore 
 59 gmake[2]: Leaving directory `/home/caleb/kscribble/src'
 60 gmake[2]: Entering directory `/home/caleb/kscribble'
 61 gmake[2]: Nothing to be done for `all-am'.
@@ -1120,7 +1120,7 @@ know how to handle them and only have to concentrate on the displayed data.
 <title>KDE Views</title>
 <para>
 The KDE libraries were invented to make designing applications for the K Desktop Environment easier
-and capable of more functionality than what Qt alone is offering. The kdeui library offers: 
+and capable of more functionality than what Qt alone is offering. The tdeui library offers: 
 <orderedlist>
 <listitem><para>
 KListView: a more powerful version of <classname>QListView</classname>
@@ -1274,7 +1274,7 @@ either displaying the button, button with text on the right, button with text be
 This possibility should be made configurable by the user, but isn't a must-be. The text is shown
 as a tool-tip anyway and a toolbar usually consists of buttons and other widgets like lineedits and 
 combo boxes. For a complete reference, see the <classname>KToolBar</classname> class reference located 
-in the kdeui library. 
+in the tdeui library. 
 </para>
 <para>
 As an example, we have a look at the "New File" button in a generic application: