Additional kde to tde renaming

4 files changed, 13 insertions, 13 deletions

diff --git a/Documentation/ConduitProgrammingTutorial/index.tex b/Documentation/ConduitProgrammingTutorial/index.tex
index 66b17f3..679fcc0 100644
--- a/Documentation/ConduitProgrammingTutorial/index.tex
+++ b/Documentation/ConduitProgrammingTutorial/index.tex
@@ -182,11 +182,11 @@ with the handheld. Figure \ref{ConduitStructure} shows this as a diagram:
 
 Before we delve into programming details, let us look a bit at the compilation framework.
 
-If you develop your conduit inside the \file{kdepim/kpilot/conduits} directory of KDE's 
+If you develop your conduit inside the \file{tdepim/kpilot/conduits} directory of KDE's 
 CVS tree, all you need to do is to provide a Makefile.am in your conduit directory 
-(e.g. \file{kdepim/kpilot/conduits/malconduit}), and add the name of your 
+(e.g. \file{tdepim/kpilot/conduits/malconduit}), and add the name of your 
 directory (\file{malconduit} in this example) to the variable \code{SUBDIRS} 
-in \file{kdepim/kpilot/conduits/Makefile.am}:
+in \file{tdepim/kpilot/conduits/Makefile.am}:
 {\small
 \begin{verbatim}
 SUBDIRS = knotes expense null vcalconduit \
@@ -249,7 +249,7 @@ pointing to the headers and the library of libmal, and are set by
 \vspace{1em}
 
 If you have special library requirements (e.g. the malconduit needs libmal to work), 
-you need to add special configure checks to the autoconf file \file{kdepim/kpilot/conduits/configure.in.in} (for an 
+you need to add special configure checks to the autoconf file \file{tdepim/kpilot/conduits/configure.in.in} (for an 
 example, you should look at the checks the malconduit added to the file in CVS) 
 and include the directory only if the appropriate libraries and header files are installed. 
 One way to achieve this is to add the following line after your configure checks, which set 
@@ -262,7 +262,7 @@ AM_CONDITIONAL(include_malconduit, test "$HAVE_MAL" = "1")
 }
 
 You can then use "\code{include\_malconduit}" in the KPilot conduit 
-directory's makefile \file{kdepim/kpilot/conduits/Makefile.am}:
+directory's makefile \file{tdepim/kpilot/conduits/Makefile.am}:
 {\footnotesize
 \begin{verbatim}
 MALSUBDIR=
@@ -333,7 +333,7 @@ Debugging KPilot conduits is not an easy task, as one cannot use a debugger
 in the background when it is started).
 
 So printing debug output is the only way to get any information about what 
-the conduit is doing. If you don't configure kdepim it with \code{--no-debug}, or don't add 
+the conduit is doing. If you don't configure tdepim it with \code{--no-debug}, or don't add 
 \code{--NDEBUG} in Makefile.am, then you can easily print out debug messages
 using the \code{DEBUGCONDUIT} stream. However, at the beginning of each 
 function where you want to use it, you need to add the macro \code{FUNCTIONSETUP;}, 
@@ -1528,7 +1528,7 @@ These code pieces from the docconduit are supposed to give you an insight into h
 
 
 \section{A record-based conduit}\label{SectionRecordBasedConduit}
-If you work with record-based conduits (e.g. addressbook, calendar conduits etc.), you might proceed similar to a document-based conduit (where records correspond to documents, of course), although you probably want to do the synchronization step immediately instead of storing all information about the states in a big list and only later sync the data. To dig deeper into the structure of such conduits (which I admit are the most common ones, but also the most complex), take a look at the addressbook conduit of KDE 3.1 (e.g. using KDE's webcvs at \htmladdnormallink{http://webcvs.kde.org/cgi-bin/cvsweb.cgi/kdepim/kpilot/conduits/abbrowserconduit/}{http://webcvs.kde.org/cgi-bin/cvsweb.cgi/kdepim/kpilot/conduits/abbrowserconduit/}).
+If you work with record-based conduits (e.g. addressbook, calendar conduits etc.), you might proceed similar to a document-based conduit (where records correspond to documents, of course), although you probably want to do the synchronization step immediately instead of storing all information about the states in a big list and only later sync the data. To dig deeper into the structure of such conduits (which I admit are the most common ones, but also the most complex), take a look at the addressbook conduit of KDE 3.1 (e.g. using KDE's webcvs at \htmladdnormallink{http://webcvs.kde.org/cgi-bin/cvsweb.cgi/tdepim/kpilot/conduits/abbrowserconduit/}{http://webcvs.kde.org/cgi-bin/cvsweb.cgi/tdepim/kpilot/conduits/abbrowserconduit/}).
 %TODO
 
 
diff --git a/Documentation/README-4.0.0 b/Documentation/README-4.0.0
index f9fdccb..9b68a81 100644
--- a/Documentation/README-4.0.0
+++ b/Documentation/README-4.0.0
@@ -20,8 +20,8 @@ INSTALLATION INSTRUCTIONS
 =========================
 
 	The file ../README contains minimal information on how to compile
-and install KPilot. Since KPilot is part of the kdepim package, you
-should also have the INSTALL file for kdepim, probably in ../../INSTALL.
+and install KPilot. Since KPilot is part of the tdepim package, you
+should also have the INSTALL file for tdepim, probably in ../../INSTALL.
 
 	This README file only contains the release notes for KPilot 4.0.0.
 
diff --git a/Documentation/README-4.2.1 b/Documentation/README-4.2.1
index 71db728..5316384 100644
--- a/Documentation/README-4.2.1
+++ b/Documentation/README-4.2.1
@@ -20,8 +20,8 @@ INSTALLATION INSTRUCTIONS
 =========================
 
 	The file ../README contains minimal information on how to compile
-and install KPilot. Since KPilot is part of the kdepim package, you
-should also have the INSTALL file for kdepim, probably in ../../INSTALL.
+and install KPilot. Since KPilot is part of the tdepim package, you
+should also have the INSTALL file for tdepim, probably in ../../INSTALL.
 
 	This README file only contains the release notes for KPilot 4.2.1.
 
diff --git a/Documentation/README-4.2.2 b/Documentation/README-4.2.2
index 604460f..69ce2cd 100644
--- a/Documentation/README-4.2.2
+++ b/Documentation/README-4.2.2
@@ -21,8 +21,8 @@ INSTALLATION INSTRUCTIONS
 =========================
 
 	The file ../README contains minimal information on how to compile
-and install KPilot. Since KPilot is part of the kdepim package, you
-should also have the INSTALL file for kdepim, probably in ../../INSTALL.
+and install KPilot. Since KPilot is part of the tdepim package, you
+should also have the INSTALL file for tdepim, probably in ../../INSTALL.
 
 	This README file only contains the release notes for KPilot 4.2.2.