cmake files: change keywords to lower case

Signed-off-by: Michele Calgaro <michele.calgaro@yahoo.it>

3 files changed, 12 insertions, 20 deletions

diff --git a/Documentation/ConduitProgrammingTutorial/index.tex b/Documentation/ConduitProgrammingTutorial/index.tex
index d334c15..e852eeb 100644
--- a/Documentation/ConduitProgrammingTutorial/index.tex
+++ b/Documentation/ConduitProgrammingTutorial/index.tex
@@ -371,8 +371,8 @@ To provide a consistent experience to KPilot users, there already
 exists a class \class{ConduitConfig} which is a subclass of \class{KDialog}. 
 This dialog does most of the basic work for you.
 
-\subsection{The dialog template, using QT Designer}
-Of course, first we need to have a dialog template in the form of a QT 
+\subsection{The dialog template, using TQt Designer}
+Of course, first we need to have a dialog template in the form of a TQt 
 Designer file (which has an extension .ui). Start up \file{designer} and 
 create a new widget (no dialogbox, i.e. no OK or cancel buttons, these will be added automatically). The dialogbox should contain a QTabWidget, even if you only need one tab. A second tab "About" will be added more or less automatically by the conduit listing the copyright and the authors of your conduit. A typical example of the coknduit setup widget dialog is shown in the following screenshot:
 \includegraphics[width=14cm]{pictures/ProxyTab}
@@ -437,7 +437,7 @@ The first two lines create an instance of our dialog template and add it
 as the tab widget to the dialog. Since we will have to set and read the 
 values of the controls in that tab widget, we need to store a pointer to 
 the instance in the variable \code{fConfigWidget} which is of the same type 
-(\code{MALWidget}) we assigned to our dialog template in QT Designer. The 
+(\code{MALWidget}) we assigned to our dialog template in TQt Designer. The 
 third line of code adds the about page (which is created by the factory, 
 see last section) to the tab widget, while the last two line just adjust 
 the size of the dialog box and are not always needed.
@@ -453,7 +453,7 @@ char*} variable of the conduit factory class), and then we can use the methods
 \item \code{fConfig->readEntry("entryname", \em{defaultstring})}
 \item \code{fConfig->readBoolEntry("entryname", \em{defaultBoolValue})}
 \end{itemize}
-to retrieve the settings from the configuration file. We then use the methods of the QT and KDE widgets to assign the text or value to the controls:
+to retrieve the settings from the configuration file. We then use the methods of the TQt and TDE widgets to assign the text or value to the controls:
 
 {\footnotesize\begin{verbatim}
 /* virtual */ void MALWidgetSetup::readSettings()
@@ -945,7 +945,7 @@ Another issue is how to propagate log messages from the external library to KPil
 emit logMessage(i18n("My own log message"));
 \end{verbatim}
 
-The problem with these slots is that they are Qt-specific, while most libraries are written in C, and expect a hook function that will be called whenever a message needs to be written out. Unfortunately you cannot pass a member of your SyncAction-derived class, either, so the way out is to store a pointer to the current conduit instance (only one will be active at any time, anyway) in a static variable, and call the member method from this pointer:
+The problem with these slots is that they are TQt-specific, while most libraries are written in C, and expect a hook function that will be called whenever a message needs to be written out. Unfortunately you cannot pass a member of your SyncAction-derived class, either, so the way out is to store a pointer to the current conduit instance (only one will be active at any time, anyway) in a static variable, and call the member method from this pointer:
 
 {\footnotesize
 \begin{verbatim}
@@ -1632,7 +1632,7 @@ This is also varpoware
 
 
 > 5) How about responsiveness of the front end? I realized there are no
-> QTimer::singleShot to let qt process the queue between syncing two records.
+> TQTimer::singleShot to let tqt process the queue between syncing two records.
 > Or did I miss something?
 
 currenlty this is true. While we aim for ASYNC the syncing is currently 
diff --git a/Documentation/HOWTO-CODE.txt b/Documentation/HOWTO-CODE.txt
index 99c093c..f28a319 100644
--- a/Documentation/HOWTO-CODE.txt
+++ b/Documentation/HOWTO-CODE.txt
@@ -58,7 +58,7 @@ Header Files
 ============
 
 One thing we *do* need to agree on is how to protect
-.h files from double-inclusion. In Qt and KDE there's:
+.h files from double-inclusion. In TQt and TDE there's:
 
 	#ifndef QTCLASS_H
 	#ifndef _KDECLASS_H
diff --git a/Documentation/README-3.2.1+ b/Documentation/README-3.2.1+
index ca9a1cc..611c5b9 100644
--- a/Documentation/README-3.2.1+
+++ b/Documentation/README-3.2.1+
@@ -48,8 +48,7 @@ Current features include:
 
 INSTALLATION
 ============
-	KPilot 4.0.0 _REQUIRES_ KDE 2 (http://www.kde.org/) and
-v2.2.0 or better of the QT widget set (http://www.troll.no/). 
+	KPilot 4.0.0 _REQUIRES_ TDE and the TQt library
 KPilot also _REQUIRES_ pilot-link, which is not distributed with 
 all the linux distro's out there. You may have to go looking.
 
@@ -60,11 +59,6 @@ all the linux distro's out there. You may have to go looking.
 	make install
 
 	from the kpilot-4.0.0 directory should configure and install KPilot.  
-If you are using KPanel (the panel that comes with KDE) restarting it
-should insert an icon into the Utilities submenu.  If you are not using
-KPanel, the executable is named kpilot and will be installed in either
-/opt/kde/bin/ or /usr/local/kde/bin (whichever is appropriate for your
-system).
 
 	In some cases KPilot will not compile due to configuration
 differences; in this case a less simple
@@ -79,14 +73,12 @@ should do the trick. If this fails as well, you can subscribe to the
 KPilot mailing list and state the nature of the failure there.
 
 	*NOTE* that KPilot makes assumptions about where pilot-link and
-the Qt libraries are; in particular it is important to set TQTDIR correctly
-(to the Qt 1.44 directories) when compiling KPilot. On many systems the
-command to do this will be
+the TQt libraries are; in particular it is important to set TQTDIR correctly
+when compiling KPilot. On many systems the command to do this will be
 
-	export TQTDIR=/usr/lib/qt-2*
+	export TQTDIR=/usr/lib/tqt
 
-but your mileage may vary. RedHat 6.2 systems ship with Qt 1.45 and Qt 2.1,
-in which case it is doubly important to set TQTDIR properly.
+but your mileage may vary.
 
 USING THE SOFTWARE
 ==================