Revert to .kdevelop files with <kdevelop> entity name for project files.

This resolves bug 2308.

Signed-off-by: Michele Calgaro <michele.calgaro@yahoo.it>
(cherry picked from commit e044c5463329652f28565dfc7de24ef8b0edaa6f)

4 files changed, 10 insertions, 10 deletions

diff --git a/doc/api/HighPriTasks.dox b/doc/api/HighPriTasks.dox
index 850053f9..1158d82c 100644
--- a/doc/api/HighPriTasks.dox
+++ b/doc/api/HighPriTasks.dox
@@ -5,11 +5,11 @@
 
 \section fixMajBugs Fixing major/annoying bugs
 
-  - Fix the mess of .tdevelop and .kdevses file.
-    - All project wide setings should go into .tdevelop and
+  - Fix the mess of .kdevelop and .kdevses file.
+    - All project wide setings should go into .kdevelop and
     - all session (and personal) options should go into .kdevses file
     .
-    This way the .tdevelop file can be shared in teams of developers.
+    This way the .kdevelop file can be shared in teams of developers.
 
 
 \section TDevelop2compat TDevelop 2 compatibility
diff --git a/doc/api/HowToAddApplicationTemplates.dox b/doc/api/HowToAddApplicationTemplates.dox
index 4b77b9e2..e1b9c223 100644
--- a/doc/api/HowToAddApplicationTemplates.dox
+++ b/doc/api/HowToAddApplicationTemplates.dox
@@ -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.tdevelop
+    - template-khello/app.kdevelop
     - template-khello/appui.rc
     - template-khello/khello
     - template-khello/main.cpp
@@ -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.tdevelop","${dest}/${APPNAMELC}.tdevelop" );
+"${src}/template-chello/app.kdevelop","${dest}/${APPNAMELC}.kdevelop" );
 \endcode
 becomes
 \code
 [PROJECT]
 Type=install
-Source=%{src}/template-chello/app.tdevelop
-Dest=%{dest}/%{APPNAMELC}.tdevelop
+Source=%{src}/template-chello/app.kdevelop
+Dest=%{dest}/%{APPNAMELC}.kdevelop
 \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 012cb5d0..3f9d1b20 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 TDevelop architecture makes a difference here and supports two files
-which will be stored in the project root directory. They are the project file (*.tdevelop)
+which will be stored in the project root directory. They are the project file (*.kdevelop)
 and the session (*.kdevses) file. The later is for individual settings, not to be thought
 to be shared.
 
-\subsection domProject Project file (*.tdevelop)
+\subsection domProject Project file (*.kdevelop)
 
 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
diff --git a/doc/api/HowToAddProgrammingLanguages.dox b/doc/api/HowToAddProgrammingLanguages.dox
index 1926d811..9ef228e2 100644
--- a/doc/api/HowToAddProgrammingLanguages.dox
+++ b/doc/api/HowToAddProgrammingLanguages.dox
@@ -137,7 +137,7 @@ and look at <code>languages/ruby/app_templates/rubyhello</code>, <code>languages
 \subsubsection sectionApplicationImportTemplates Application import templates
 
 TDevelop has the ability to <b>create a new project from existing projects or source code</b>.
-It scans for project files ('*.tdevelop, *.kdevprj, *.studio, *.pro) and if
+It scans for project files ('*.kdevelop, *.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, ...)
   .