Rename a number of libraries and executables to avoid conflicts with KDE4

4 files changed, 11 insertions, 11 deletions

diff --git a/doc/api/FutureTasks.dox b/doc/api/FutureTasks.dox
index 5e2b8268..c738a3f3 100644
--- a/doc/api/FutureTasks.dox
+++ b/doc/api/FutureTasks.dox
@@ -99,7 +99,7 @@
       - cd's when selecting a file, but doesn't when selecting a dir,
         desired: a menu option to "cd" to that directory
     - QEditor
-      - Replace editors/qeditor/koReplace.* and editors/qeditor/koFind.* with tdelibs/kutils/kreplace.* and tdelibs/kutils/kfind.*
+      - Replace editors/qeditor/koReplace.* and editors/qeditor/koFind.* with tdelibs/tdeutils/kreplace.* and tdelibs/tdeutils/kfind.*
 
     
 \section extensiontodo Extensions / New Functionality:
diff --git a/doc/kde_app_devel/index.docbook b/doc/kde_app_devel/index.docbook
index bfade594..a73c681a 100644
--- a/doc/kde_app_devel/index.docbook
+++ b/doc/kde_app_devel/index.docbook
@@ -542,7 +542,7 @@ Additionally, for specific solutions KDE offers the following libraries:
 the tdefx library, containing pixmaps, image effects the KStyle extension to QStyle
 </para></listitem>
 <listitem><para>
-the khtml library, containing KDE's html component
+the tdehtml library, containing KDE's html component
 </para></listitem>
 <listitem><para>
 the kjs library, containing KDE's Javascript support
@@ -551,7 +551,7 @@ the kjs library, containing KDE's Javascript support
 the kio library, containing low level access to network files
 </para></listitem>
 <listitem><para>
-the kparts library, containing support for re-usable embeddable extendable applications
+the tdeparts library, containing support for re-usable embeddable extendable applications
 </para></listitem>
 </itemizedlist>
 </para>
@@ -1131,7 +1131,7 @@ KIconView: a graphical viewer of icon files
 </orderedlist>
 </para>
 <para>
-The khtml library, on the other hand, offers a complete HTML-interpreting widget that is ready to use.
+The tdehtml library, on the other hand, offers a complete HTML-interpreting widget that is ready to use.
 It is scrollable already, so you don't even have to take care for that. A possible use could be to
 integrate it as a preview widget for an HTML editor; used by applications such as Konqueror to display HTML files. 
 </para>
diff --git a/doc/kdearch/index.docbook b/doc/kdearch/index.docbook
index e5942974..7bccb9fa 100644
--- a/doc/kdearch/index.docbook
+++ b/doc/kdearch/index.docbook
@@ -87,9 +87,9 @@ The <literal>kjs</literal> library provides an implementation of JavaScript.
 </varlistentry>
 
 <varlistentry>
-<term><ulink url="kdeapi:khtml/index.html">khtml</ulink></term>
+<term><ulink url="kdeapi:tdehtml/index.html">tdehtml</ulink></term>
 <listitem><para>
-The <literal>khtml</literal> library contains the KHTML part, a HTML browsing
+The <literal>tdehtml</literal> library contains the KHTML part, a HTML browsing
 widget, DOM API and parser, including interfaces to Java and JavaScript.
 </para></listitem>
 </varlistentry>
@@ -592,7 +592,7 @@ A GUI fragment consisting of an action collection and a DOM tree representing th
 </para>
 </formalpara></listitem>
 
-<listitem><formalpara><title><ulink url="kdeapi:kparts/KPartManager">KPartManager</ulink></title>
+<listitem><formalpara><title><ulink url="kdeapi:tdeparts/KPartManager">KPartManager</ulink></title>
 <para>
 Manages the activation of XMLGUI clients.
 </para>
@@ -2004,9 +2004,9 @@ The type of the factory class <classname>DoxygenFactory</classname> depends on
 the specific service type the service implements. In our example of a TDevelop
 plugin, the factory must be a <classname>KDevFactory</classname> (which
 inherits <classname>KLibFactory</classname>). More common examples are
-<ulink url="kdeapi:kparts/KParts::Factory">KParts::Factory</ulink>
+<ulink url="kdeapi:tdeparts/KParts::Factory">KParts::Factory</ulink>
 which is supposed to produce 
-<ulink url="kdeapi:kparts/KParts::ReadOnlyPart">KParts::ReadOnlyPart</ulink>
+<ulink url="kdeapi:tdeparts/KParts::ReadOnlyPart">KParts::ReadOnlyPart</ulink>
 objects or in most cases the generic
 <ulink url="kdeapi:tdecore/KLibFactory">KLibFactory</ulink>.
 </para>
diff --git a/doc/tdevelop/setup.docbook b/doc/tdevelop/setup.docbook
index 366f25a7..0c078a3b 100644
--- a/doc/tdevelop/setup.docbook
+++ b/doc/tdevelop/setup.docbook
@@ -540,7 +540,7 @@ The active toolview window must be shown fixed (non-overlap mode), sharing the w
 </screenshot>
 
 <para>
-To select a new editor, click on the arrow on the drop down list field. Depending on the editor parts interfaces your &kde; version has compiled in you will be provided with a list of editors you may select from (see the <link linkend="setup-editor-kparts">Important</link> note below for this). Click on the editor of your liking and click <guilabel>OK</guilabel>. Currently there are two possibilities:
+To select a new editor, click on the arrow on the drop down list field. Depending on the editor parts interfaces your &kde; version has compiled in you will be provided with a list of editors you may select from (see the <link linkend="setup-editor-tdeparts">Important</link> note below for this). Click on the editor of your liking and click <guilabel>OK</guilabel>. Currently there are two possibilities:
 </para>
 
 <variablelist>
@@ -567,7 +567,7 @@ These editor interfaces are fully integrated in the &tdevelop; IDE concept. Part
 Changing the editor will not effect already open files. There are two possibilities to proceed. Either close all open text windows and reopen them one by one. Or simply close the whole project and reopen it again. The windows will then automatically open under the new text editor interface.
 </para></note>
 
-<important id="setup-editor-kparts"><para>
+<important id="setup-editor-tdeparts"><para>
 KDevelop lets you use editor interfaces which have registered with &kde; and that provide a KatePart interface. If you miss one one of the selections shown above check your &kde; installation if the corresponding KPart was correctly installed.
 </para></important>