7 files changed, 29 insertions, 29 deletions

diff --git a/doc/api/FutureTasks.dox b/doc/api/FutureTasks.dox
index fbed119a..5e2b8268 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 kdelibs/kutils/kreplace.* and kdelibs/kutils/kfind.*
+      - Replace editors/qeditor/koReplace.* and editors/qeditor/koFind.* with tdelibs/kutils/kreplace.* and tdelibs/kutils/kfind.*
 
     
 \section extensiontodo Extensions / New Functionality:
diff --git a/doc/api/HighPriTasks.dox b/doc/api/HighPriTasks.dox
index 21116342..062b3b06 100644
--- a/doc/api/HighPriTasks.dox
+++ b/doc/api/HighPriTasks.dox
@@ -5,16 +5,16 @@
 
 \section fixMajBugs Fixing major/annoying bugs
 
-  - Fix the mess of .kdevelop and .kdevses file.
-    - All project wide setings should go into .kdevelop and
+  - Fix the mess of .tdevelop and .kdevses file.
+    - All project wide setings should go into .tdevelop and
     - all session (and personal) options should go into .kdevses file
     .
-    This way the .kdevelop file can be shared in teams of developers.
+    This way the .tdevelop file can be shared in teams of developers.
 
 
 \section KDevelop2compat KDevelop 2 compatibility
 (These are things that must be accomplished before we can say that KDevelop 3
->= kdevelop 2.x UI-wise and functionality-wise!)
+>= tdevelop 2.x UI-wise and functionality-wise!)
 
   - general UI issues:
     - toplevel UI mode broken concerning to the accels
@@ -29,7 +29,7 @@
     - implement "Make User Manual"
     - use kdoc to update Qt/KDE docs
     .
-  - Solve the regression bugs. These are the <a href= "http://bugs.kde.org/buglist.cgi?product=kdevelop&bug_status=UNCONFIRMED&bug_status=NEW&priority=HI">ones
+  - Solve the regression bugs. These are the <a href= "http://bugs.kde.org/buglist.cgi?product=tdevelop&bug_status=UNCONFIRMED&bug_status=NEW&priority=HI">ones
 marked with priority "HI" in the bug database</a>
 
 
diff --git a/doc/api/HowToAddApplicationTemplates.dox b/doc/api/HowToAddApplicationTemplates.dox
index 7eec80c7..b948c934 100644
--- a/doc/api/HowToAddApplicationTemplates.dox
+++ b/doc/api/HowToAddApplicationTemplates.dox
@@ -6,7 +6,7 @@
 Project templates provide the developer with a basic application framework.
 This is necessary for rapid application development (RAD) and makes it even possible
 for an inexperienced 3rd party developer to create standard conforming
-applications like kedit as well as plugins for example for kdevelop or noatun.\n\n
+applications like kedit as well as plugins for example for tdevelop or noatun.\n\n
 \ref templates_1\n
     - \ref templates_1_1
     - \ref templates_1_2
@@ -36,7 +36,7 @@ Create a directory <code>template-khello</code> with the files
     - template-khello/app.cpp
     - template-khello/app.h
     - template-khello/app.desktop
-    - template-khello/app.kdevelop
+    - template-khello/app.tdevelop
     - template-khello/appui.rc
     - template-khello/khello
     - template-khello/main.cpp
@@ -64,7 +64,7 @@ wizard will replace:
     - \%{YEAR} ........ by the year
     .
 </pre></code>
-All this can be found in <code>$KDEDIR/share/apps/kdevappwizard/template-common/kdevelop.pm</code>.
+All this can be found in <code>$KDEDIR/share/apps/kdevappwizard/template-common/tdevelop.pm</code>.
 \subsubsection templates_1_2a I.2.1. The Source Files
 
 The files <code>template-khello/app.cpp, template-khello/app.h</code> and
@@ -117,7 +117,7 @@ This file will be copied to the <code>$PROJECTDIR/src/</code>.
 
 The following script is used to install the template and replaces all
 variables by the corresponding value. The result is a hopefully working
-kdevelop project!
+tdevelop project!
 \verbinclude khello/script
 <br>
 \note There are several application templates which use some identical
@@ -155,7 +155,7 @@ if [ ! -e "${newdir}/template-common" ]; then ln -s "${kde_prefix}/share/apps/kd
 # install now
 cp -R --target-directory "$newdir" template-khello
 # the file template-khello/khello must go to the "templates" directory that
-# kdevelop knows that it exists
+# tdevelop knows that it exists
 mv "$newdir/template-khello/khello" "$newdir/templates/"
 echo "done"
 \endcode
@@ -164,9 +164,9 @@ echo "done"
 
 \section templates_3 III. How To Add The Template To KDevelop CVS HEAD
 
-This section is for kdevelop developers only. Most probably you don't have to read this!.\n
-Move the directory <code>"template-khello"</code> to <code>kdevelop/languages/cpp/app_templates/</code>
-and then add the following files in <code>kdevelop/languages/cpp/app_templates/template-khello/</code>
+This section is for tdevelop developers only. Most probably you don't have to read this!.\n
+Move the directory <code>"template-khello"</code> to <code>tdevelop/languages/cpp/app_templates/</code>
+and then add the following files in <code>tdevelop/languages/cpp/app_templates/template-khello/</code>
 (in this example the language is c++ if you use other language replace cpp with the language name):
     - <code>".kdev_ignore"</code> is an empty file. It prevents KDevelop's
     C++-parser from parsing the C++ template files. This is necessary because the template files are just code templates and not real code (yet).
@@ -179,9 +179,9 @@ script.local
     - <code>"Makefile.am"</code> looks like this:
     \verbinclude khello/Makefile.am
     .
-Finally add <code>"template-khello"</code> to "SUBDIRS = " in <code>kdevelop/languages/cpp/app_templates/Makefile.am</code>.\n
+Finally add <code>"template-khello"</code> to "SUBDIRS = " in <code>tdevelop/languages/cpp/app_templates/Makefile.am</code>.\n
 \attention Please test your template whether it installs and behaves correctly!
-Test, test and test again! It works? Well - now talk to the kdevelop guys so
+Test, test and test again! It works? Well - now talk to the tdevelop guys so
 that they know what's going on and probably you may commit. ;)
 
 \section templates_4 IV. Changes to the template system (VERY IMPORTANT)
@@ -192,14 +192,14 @@ information from the script file will need to be moved into the ini file.
 The example is as follows:
 \code
 install(
-"${src}/template-chello/app.kdevelop","${dest}/${APPNAMELC}.kdevelop" );
+"${src}/template-chello/app.tdevelop","${dest}/${APPNAMELC}.tdevelop" );
 \endcode
 becomes
 \code
 [PROJECT]
 Type=install
-Source=%{src}/template-chello/app.kdevelop
-Dest=%{dest}/%{APPNAMELC}.kdevelop
+Source=%{src}/template-chello/app.tdevelop
+Dest=%{dest}/%{APPNAMELC}.tdevelop
 \endcode
 
 Things like <code>installIncAdmin();</code> and <code>installGNU();</code> now involve unpacking
diff --git a/doc/api/HowToAddPlugins.dox b/doc/api/HowToAddPlugins.dox
index 6171d9aa..3ab31af9 100644
--- a/doc/api/HowToAddPlugins.dox
+++ b/doc/api/HowToAddPlugins.dox
@@ -119,11 +119,11 @@ developers (e.g. via version control application CVS). So some user preferences
 very individual, and some may be valid for all of the team - project-wide so to speak.
 
 That's why the KDevelop architecture makes a difference here and supports two files
-which will be stored in the project root directory. They are the project file (*.kdevelop)
+which will be stored in the project root directory. They are the project file (*.tdevelop)
 and the session (*.kdevses) file. The later is for individual settings, not to be thought
 to be shared.
 
-\subsection domProject Project file (*.kdevelop)
+\subsection domProject Project file (*.tdevelop)
 
 For your convenience, you don't have to use the quite complex DOM API. Strings
 can very easily be read from and written to this document using the
@@ -195,7 +195,7 @@ void GDBBreakpointWidget::savePartialProjectSession(QDomElement* el)
 </pre></code>
 
 Note that the .kdevses is related to a project. User settings equal for all projects don't
-belong to here. You save them to ~/.kde/share/config/kdeveloprc via class KConfig of the
+belong to here. You save them to ~/.kde/share/config/tdeveloprc via class KConfig of the
 tdecore library.
 
 Document your part in the way described at \ref howToDocument (doc/api/HowToDocument.dox file).
diff --git a/doc/api/HowToAddProgrammingLanguages.dox b/doc/api/HowToAddProgrammingLanguages.dox
index 5cfa3643..504a397e 100644
--- a/doc/api/HowToAddProgrammingLanguages.dox
+++ b/doc/api/HowToAddProgrammingLanguages.dox
@@ -42,7 +42,7 @@ Take a look at \ref LangSupportStatus (doc/api/LangSupportStatus.dox file) to se
 
 \section sectionLanguageSupport Language Support
 
-Any language support should be written as a kdevelop part and implement
+Any language support should be written as a tdevelop part and implement
 KDevLanguageSupport interface (<code>lib/interfaces/kdevlanguagesupport.h</code>).
 
 Implementing methods:
@@ -137,7 +137,7 @@ and look at <code>languages/ruby/app_templates/rubyhello</code>, <code>languages
 \subsubsection sectionApplicationImportTemplates Application import templates
 
 KDevelop has the ability to <b>create a new project from existing projects or source code</b>.
-It scans for project files ('*.kdevelop, *.kdevprj, *.studio, *.pro) and if
+It scans for project files ('*.tdevelop, *.kdevprj, *.studio, *.pro) and if
   - it finds a project it extracts the necessary information
   - it does not find project files it scans for source files (*.cpp, *.java, *.pl, *.py, ...)
   .
diff --git a/doc/api/HowToDocument.dox b/doc/api/HowToDocument.dox
index d606a8bf..f767fc5b 100644
--- a/doc/api/HowToDocument.dox
+++ b/doc/api/HowToDocument.dox
@@ -8,7 +8,7 @@ You should add a README and a README.dox file to your part (KDevPlugin).
 On the README file put this text:
 \verbatim
 Please read the on-line, automaticaly updated KDevelop API documentation at:
-http://www.kdevelop.org
+http://www.tdevelop.org
 or read the README.dox file.
 \endverbatim
 
diff --git a/doc/api/Mainpage.dox b/doc/api/Mainpage.dox
index 9d4b6d4c..48640827 100644
--- a/doc/api/Mainpage.dox
+++ b/doc/api/Mainpage.dox
@@ -13,14 +13,14 @@ This document is targeted at all those that want to add or improve KDevelop's so
 If you are instead looking for a user manual, just go to the help menu of your KDevelop and select KDevelop handbook.
 This documentation contains the KDevelop online class reference for the current
 development version of KDevelop.  Additionally, you
-can subscribe or read the <a href="http://www.kdevelop.org/index.html?filename=mailinglist.html">mailing list</a> for any additions and/or
+can subscribe or read the <a href="http://www.tdevelop.org/index.html?filename=mailinglist.html">mailing list</a> for any additions and/or
 modifications to the %API.
 
-An on-line, updated every 24H, html version of this documentation can be found at: http://www.kdevelop.org/HEAD/doc/api/html/index.html
+An on-line, updated every 24H, html version of this documentation can be found at: http://www.tdevelop.org/HEAD/doc/api/html/index.html
 
 More information about the KDevelop architecture in form of tutorials, HOWTOs,
 and FAQs can be found at
-the <a href="http://www.kdevelop.org">KDevelop website</a>.
+the <a href="http://www.tdevelop.org">KDevelop website</a>.
 
 
 \section status Current Status
@@ -45,7 +45,7 @@ Additionally you may also want to find out \ref howToDocument (doc/api/HowToDocu
 Here is a priority ordered list:
   -# \ref HighPriTasks (doc/api/HighPriTasks.dox file)
   -# fix the dispersed \ref fixme
-  -# <a href="http://bugs.kde.org/buglist.cgi?product=kdevelop&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&order=bugs.bug_id">reported bugs in bugzilla database</a>
+  -# <a href="http://bugs.kde.org/buglist.cgi?product=tdevelop&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&order=bugs.bug_id">reported bugs in bugzilla database</a>
   -# fix the bugs in the \ref bug
   -# fix the dispersed \ref todo all over the code.
   .