Additional renaming of kde to tde

1 files changed, 9 insertions, 9 deletions

diff --git a/doc/kdevelop/project-management.docbook b/doc/kdevelop/project-management.docbook
index 75674203..69ca9474 100644
--- a/doc/kdevelop/project-management.docbook
+++ b/doc/kdevelop/project-management.docbook
@@ -34,7 +34,7 @@ You will find here information on:</para>
 In the <link linkend="unixdev-buildsystems">Build systems</link> chapter we have given a rough overview of the build systems commonly in use on &UNIX; systems. In the following sections we will look at this in more detail.
 </para>
 <para>
-There is some confusion about how to name such things. &GNU; calls them <quote>build systems</quote> when it describes Automake, Autoconf and Libtool. QMake calls itself <quote>a tool to write Makefiles for different compilers and platforms</quote>. In &kde; often the term <quote>project management systems</quote> is used. We will use this term in a broader sense to describe the built-in environments in &kdevelop; which are used to organize and build your projects. In the context of this section, however, we will mostly talk about <quote>automated build systems</quote>.
+There is some confusion about how to name such things. &GNU; calls them <quote>build systems</quote> when it describes Automake, Autoconf and Libtool. QMake calls itself <quote>a tool to write Makefiles for different compilers and platforms</quote>. In &kde; often the term <quote>project management systems</quote> is used. We will use this term in a broader sense to describe the built-in environments in &tdevelop; which are used to organize and build your projects. In the context of this section, however, we will mostly talk about <quote>automated build systems</quote>.
 </para>
 
 <sect2 id="automake-manager-summary-buildsys">
@@ -95,7 +95,7 @@ A build system will iron out these differences for you.
 </itemizedlist>
 
 <para>
-In brief, a build system offers safe and secure methods for your application to be compiled and installed correctly on any receiving machine. As we have shown before in the <link linkend="makesystems">Project Management Systems</link> survey, &kdevelop; offers three automated build systems and the option of creating your own Makefile, in short (click on the project names to get more information):
+In brief, a build system offers safe and secure methods for your application to be compiled and installed correctly on any receiving machine. As we have shown before in the <link linkend="makesystems">Project Management Systems</link> survey, &tdevelop; offers three automated build systems and the option of creating your own Makefile, in short (click on the project names to get more information):
 </para>
 <itemizedlist>
   <listitem><para>
@@ -126,7 +126,7 @@ One of these four alternatives must be chosen when you create a project and <emp
 There are several tutorials available on the &GNU; Build System (<command>Autoconf</command>, <command>Automake</command> and <command>Libtool</command>) of which the &automanag; makes use.
 </para>
 <itemizedlist>
-  <listitem><para>A short <ulink url="http://www.kdevelop.org/index.html?filename=tutorial_autoconf.html">autoconf tutorial</ulink> written by Christopher W. Curtis available on the &kdevelop; home page. It concentrates on some basic steps to modify a <filename>Makefile</filename>.
+  <listitem><para>A short <ulink url="http://www.tdevelop.org/index.html?filename=tutorial_autoconf.html">autoconf tutorial</ulink> written by Christopher W. Curtis available on the &tdevelop; home page. It concentrates on some basic steps to modify a <filename>Makefile</filename>.
   </para></listitem>
   <listitem><para>
   A more detailed tutorial can be found in a greater set of tutorials on  <ulink url="http://www.amath.washington.edu/~lf/tutorials/autoconf/toolsmanual_toc.html"><quote>Developing software with GNU</quote></ulink>.
@@ -181,14 +181,14 @@ How does this work? Well <command>configure</command> is a script that
 The <filename>Makefile.in</filename> are <quote>input</quote> files&mdash;templates which provide basic information for the <filename>Makefile</filename>s to be produced from them by filling in some system dependent information. They are generated by the <command>Automake</command> utility from the <filename>Makefile.am</filename> files.
 </para>
 <para>
-The process of going from <filename>Makefile.am</filename> (<filename>.am</filename> denotes <quote>Automake</quote> template files) to <filename>Makefile</filename> files is handled automatically by the &kdevelop; &promanag;, using the <command>Autoconf</command> utility, <command>M4</command> macros and other arcana we need not go into here.
+The process of going from <filename>Makefile.am</filename> (<filename>.am</filename> denotes <quote>Automake</quote> template files) to <filename>Makefile</filename> files is handled automatically by the &tdevelop; &promanag;, using the <command>Autoconf</command> utility, <command>M4</command> macros and other arcana we need not go into here.
 </para>
 <para>
 So when <command>make</command> runs, it automatically picks up the correct pieces from the current environment, such as compilers and libraries. Similarly, <command>make install</command> puts your application components, such as executables, documentation and data files in the correct places for that environment.
 </para>
 
 <para>
-If you distribute your application as a <quote>tarball</quote> (a single compressed file that &kdevelop; can create for you), it will include the <filename>Makefile.in</filename> files and the <filename>configure</filename> script file, so the recipient can compile, build and install your application without having <command>Automake</command>, <command>Autoconf</command> or &kdevelop; on their machine. The <filename>Makefile.am</filename> files are also included, just in case the receiver needs to do any source-code modifications.
+If you distribute your application as a <quote>tarball</quote> (a single compressed file that &tdevelop; can create for you), it will include the <filename>Makefile.in</filename> files and the <filename>configure</filename> script file, so the recipient can compile, build and install your application without having <command>Automake</command>, <command>Autoconf</command> or &tdevelop; on their machine. The <filename>Makefile.am</filename> files are also included, just in case the receiver needs to do any source-code modifications.
 </para>
 <note><para>
 The rules are rather different if you distribute via a web-based source-code repository such as &kde; &cvs;.
@@ -290,7 +290,7 @@ As you can see, many of the items on the right hand side are symbols of the form
 </para>
 
 <para>
-Also, sometime after you have started with &kdevelop;, it is a good idea to run the command <command>./configure --help</command>, which will show you the range of things you can change at build and installation time, such as for a test environment. In particular, the command:
+Also, sometime after you have started with &tdevelop;, it is a good idea to run the command <command>./configure --help</command>, which will show you the range of things you can change at build and installation time, such as for a test environment. In particular, the command:
 
 <screen>
 ./configure --prefix=/where/you/wish
@@ -346,7 +346,7 @@ In this chapter you will find a basic description of the &automanag; elements an
     On top of each view there is a <emphasis>toolbar</emphasis>, the buttons in which will become activated when an element in this view is selected. This provides one way you can access the actions provided for that view element. The other are context menus which pop up on right mouse button click as will be discussed below.
     </para></listitem>
     <listitem><para>
-    In IDEAl mode there are two additional small buttons in the &automanag; window titlebar left hand side &ndash; a triangular shaped right arrow, and a dot button. The arrow button is used to <emphasis>close the window</emphasis>. The dot button on the other hand will <emphasis>keep the window open</emphasis> even if another &kdevelop; window has been selected. (Otherwise the &automanag; window will automatically close whenever another window gets the input focus.)
+    In IDEAl mode there are two additional small buttons in the &automanag; window titlebar left hand side &ndash; a triangular shaped right arrow, and a dot button. The arrow button is used to <emphasis>close the window</emphasis>. The dot button on the other hand will <emphasis>keep the window open</emphasis> even if another &tdevelop; window has been selected. (Otherwise the &automanag; window will automatically close whenever another window gets the input focus.)
     </para></listitem>
   </itemizedlist></entry>
 </row></tbody></tgroup>
@@ -429,7 +429,7 @@ In both the overall and the detail view you can left-click on the <symbol>+</sym
 <term>Opening a file for Edit</term>
 <listitem>
 <para>If you <emphasis>&LMB; click</emphasis> on a file name in the detail
-view, the corresponding file opens up in &kdevelop;'s editing window.</para>
+view, the corresponding file opens up in &tdevelop;'s editing window.</para>
 </listitem>
 </varlistentry>
 
@@ -677,7 +677,7 @@ CXX = g++
 
 
 <sect2 id="automake-manager">
-<title>&kdevelop;'s &automanag;</title>
+<title>&tdevelop;'s &automanag;</title>
 
 <figure id="screenshot-automake-manager" float="1">
 <title>A screenshot of the automake manager</title>