29 files changed, 106 insertions, 106 deletions
diff --git a/doc/html/emb-fonts.html b/doc/html/emb-fonts.html
index 6583963..234c53f 100644
--- a/doc/html/emb-fonts.html
+++ b/doc/html/emb-fonts.html
@@ -61,7 +61,7 @@ enabled) can be enabled or disabled independently by using the <a href="emb-feat
 support in Qt/Embedded for writing a QPF font file from any font, so
 you can initially enable TTF and BDF formats, save QPF files for the
 fonts and sizes you need, then remove TTF and BDF support.
-<p> See <a href="makeqpf.html">tools/makeqpf</a> for a tool that helps
+<p> See <a href="maketqpf.html">tools/maketqpf</a> for a tool that helps
 produce QPF files from the TTF and BDF, or just run your application
 with the <tt>-savefonts</tt> option.
 <p> <h2> Memory Requirements
@@ -151,7 +151,7 @@ generate all 4 rotations of fonts would be to run the following at a real frameb
 <pre>
 for dpy in LinuxFb Transformed:Rot90 Transformed:Rot180 Transformed:Rot270
 do
-    QWS_DISPLAY=$dpy ./makeqpf "$@"
+    QWS_DISPLAY=$dpy ./maketqpf "$@"
 done
 </pre><p> If programs are only ever run in one orientation on a device, only the one
 appropriate set of fonts is needed.
diff --git a/doc/html/emb-install.html b/doc/html/emb-install.html
index 47ae22a..d04a04a 100644
--- a/doc/html/emb-install.html
+++ b/doc/html/emb-install.html
@@ -144,7 +144,7 @@ named pipe <tt>/tmp/qtembedded-username/QtEmbedded-0</tt>; sometimes it may need
 <p> The Qt/Embedded library can be reduced in size by
 <a href="emb-features.html">removing unnecessary features</a>.
 <p> <li> This document shows how to use Qt/Embedded with the Linux framebuffer. For
-development and debugging purposes it is often easier to use the <a href="emb-qvfb.html">Qt/Embedded virtual framebuffer</a> instead.
+development and debugging purposes it is often easier to use the <a href="emb-tqvfb.html">Qt/Embedded virtual framebuffer</a> instead.
 <p> </ol>
 <p> 
 <!-- eof -->
diff --git a/doc/html/emb-qvfb.html b/doc/html/emb-qvfb.html
index df971cc..c2a301e 100644
--- a/doc/html/emb-qvfb.html
+++ b/doc/html/emb-qvfb.html
@@ -1,5 +1,5 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<!-- /home/espenr/tmp/qt-3.3.8-espenr-2499/qt-x11-free-3.3.8/doc/qvfb.doc:36 -->
+<!-- /home/espenr/tmp/qt-3.3.8-espenr-2499/qt-x11-free-3.3.8/doc/tqvfb.doc:36 -->
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
@@ -34,17 +34,17 @@ body { background: #ffffff; color: black; }
  
 <p> The virtual framebuffer allows Qt/Embedded programs to be developed on
 a desktop machine, without switching between consoles and X11.
-<p> The virtual framebuffer is located in <tt>$QTDIR/tools/qvfb</tt>.
+<p> The virtual framebuffer is located in <tt>$QTDIR/tools/tqvfb</tt>.
 <p> <h2> Using the Virtual Framebuffer
 </h2>
 <a name="1"></a><p> <ol type=1> 
-<li> Configure Qt/Embedded with the <tt>-qvfb</tt> argument and compile the library:
+<li> Configure Qt/Embedded with the <tt>-tqvfb</tt> argument and compile the library:
 <pre>
-    ./configure -qvfb
+    ./configure -tqvfb
     make
     </pre>
  
-<li> Compile <tt>qvfb</tt> as a normal Qt/X11 application and run it. Do <em>not</em>
+<li> Compile <tt>tqvfb</tt> as a normal Qt/X11 application and run it. Do <em>not</em>
 compile it as a Qt/Embedded application.
 <li> Start a Qt/Embedded master application (i.e., construct
 <a href="qapplication.html">QApplication</a> with the QApplication::GuiServer flag or use the <tt>-qws</tt> command line parameter). You can specify to the server that
@@ -53,13 +53,13 @@ you wish to use the virtual framebuffer driver, e.g.:
     masterapp -qws -display QVFb:0
     </pre>
  
-<li> Qt/Embedded will autodetect qvfb, so you can omit the <tt>-display</tt>
-command line parameter if you know that qvfb is running, and that
-the Qt/Embedded library supports qvfb. (If this is not the case,
+<li> Qt/Embedded will autodetect tqvfb, so you can omit the <tt>-display</tt>
+command line parameter if you know that tqvfb is running, and that
+the Qt/Embedded library supports tqvfb. (If this is not the case,
 Qt/Embedded will write to the real framebuffer, and your X11
 display will be corrupted.)
 <p> </ol>
-<p> <tt>qvfb</tt> supports the following command line options:
+<p> <tt>tqvfb</tt> supports the following command line options:
 <p> <center><table cellpadding="4" cellspacing="2" border="0">
 <tr bgcolor="#a2c511"> <th valign="top">Option <th valign="top">Meaning
 <tr bgcolor="#f0f0f0">
@@ -82,23 +82,23 @@ display will be corrupted.)
 </h2>
 <a name="2"></a><p> The virtual framebuffer emulates a framebuffer using a shared memory region
 (the virtual frame buffer) and a utility to display the framebuffer in a
-window (<tt>qvfb</tt>). The regions of the display that have changed are updated
+window (<tt>tqvfb</tt>). The regions of the display that have changed are updated
 periodically, so you will see discrete snapshots of the framebuffer rather
 than each individual drawing operation. For this reason drawing problems
 such as flickering may not be apparent until the program is run using a real
 framebuffer.
 <p> The target refresh rate can be set via the <b>View|Refresh Rate</b>
-menu item. This will cause <tt>qvfb</tt> to check for updated regions more
+menu item. This will cause <tt>tqvfb</tt> to check for updated regions more
 frequently. The rate is a target only. If little drawing is being
 done, the framebuffer will not show any updates between drawing
 events. If an application is displaying an animation the updates will
-be frequent, then the application and <tt>qvfb</tt> will compete for
+be frequent, then the application and <tt>tqvfb</tt> will compete for
 processor time.
 <p> Mouse and keyboard events are passed to the Qt/Embedded master process via
 named pipes.
 <p> The virtual framebuffer is a development tool only. No security issues have
 been considered in the virtual framebuffer design. It should be avoided
-in a production environment; do not configure production libraries with <tt>-qvfb</tt>.
+in a production environment; do not configure production libraries with <tt>-tqvfb</tt>.
 <p> 
 <!-- eof -->
 <p><address><hr><div align=center>
diff --git a/doc/html/emb-running.html b/doc/html/emb-running.html
index fae839b..499d99e 100644
--- a/doc/html/emb-running.html
+++ b/doc/html/emb-running.html
@@ -43,7 +43,7 @@ command line option.
 <p> This document assumes you have the Linux framebuffer configured correctly
 and no master process is running. If you do not have a working Linux
 framebuffer you can use the
-<a href="emb-qvfb.html">Qt/Embedded virtual framebuffer</a>, or you can
+<a href="emb-tqvfb.html">Qt/Embedded virtual framebuffer</a>, or you can
 run Qt/Embedded as a <a href="emb-vnc.html">VNC server</a>.
 <p> Change to a Linux console and select an example to run, e.g. <tt>examples/widgets</tt>. Make sure $QTDIR is set to the directory where you
 installed Qt/Embedded and add the $QTDIR/lib directory to
diff --git a/doc/html/emb-vnc.html b/doc/html/emb-vnc.html
index 6d88dba..8a1a09a 100644
--- a/doc/html/emb-vnc.html
+++ b/doc/html/emb-vnc.html
@@ -54,7 +54,7 @@ can change this by setting the <tt>QWS_SIZE</tt> environment variable to
 another size, e.g. <tt>QWS_SIZE=240x320</tt>.
 <p> VNC clients are available for a vast array of display systems: X11,
 Windows, Amiga, DOS, VMS, and dozens of others.
-<p> The <a href="emb-qvfb.html">Qt Virtual Framebuffer</a> is an alternative
+<p> The <a href="emb-tqvfb.html">Qt Virtual Framebuffer</a> is an alternative
 technique. It uses shared memory and thus is much faster and smoother, but
 it does not operate over a network.
 <p> 
diff --git a/doc/html/i18n.html b/doc/html/i18n.html
index 2b3803a..3efb156 100644
--- a/doc/html/i18n.html
+++ b/doc/html/i18n.html
@@ -347,7 +347,7 @@ file for <em>lupdate</em>; your <tt>qmake</tt> project file will work fine once
 you add the <tt>TRANSLATIONS</tt> entry.
 <p> In your application, you must <a href="qtranslator.html#load">QTranslator::load</a>() the translation
 files appropriate for the user's language, and install them using <a href="qapplication.html#installTranslator">QApplication::installTranslator</a>().
-<p> If you have been using the old Qt tools (<tt>findtr</tt>, <tt>msg2qm</tt> and <tt>mergetr</tt>), you can use <em>qm2ts</em> to convert your old <tt>.qm</tt> files.
+<p> If you have been using the old Qt tools (<tt>tqtfindtr</tt>, <tt>msg2tqm</tt> and <tt>tqtmergetr</tt>), you can use <em>tqm2ts</em> to convert your old <tt>.qm</tt> files.
 <p> <em>linguist</em>, <em>lupdate</em> and <em>lrelease</em> are installed in the <tt>bin</tt>
 subdirectory of the base directory Qt is installed into. Click Help|Manual
 in <em>Qt Linguist</em> to access the user's manual; it contains a tutorial
diff --git a/doc/html/index b/doc/html/index
index cc7ca30..c98b4c2 100644
--- a/doc/html/index
+++ b/doc/html/index
@@ -8140,7 +8140,7 @@
 "Qt's Tools" tools-list.html
 "Qt/Embedded Performance Tuning" emb-performance.html
 "Qt/Embedded Pointer Handling" emb-pointer.html
-"Qt/Embedded Virtual Framebuffer" emb-qvfb.html
+"Qt/Embedded Virtual Framebuffer" emb-tqvfb.html
 "Qt/Embedded as a VNC Server" emb-vnc.html
 "Qt/Embedded environment variables" emb-envvars.html
 "Qt/Mac Issues" mac-differences.html
@@ -8282,7 +8282,7 @@
 "i18n" i18n.html
 "images" images.html
 "io" io.html
-"makeqpf" makeqpf.html
+"maketqpf" maketqpf.html
 "misc" misc.html
 "motif-examples" motif-examples.html
 "multimedia" multimedia.html
diff --git a/doc/html/linguist-manual-2.html b/doc/html/linguist-manual-2.html
index e95e386..79dc168 100644
--- a/doc/html/linguist-manual-2.html
+++ b/doc/html/linguist-manual-2.html
@@ -32,7 +32,7 @@ body { background: #ffffff; color: black; }
 <td align="right" valign="center"><img src="logo32.png" align="right" width="64" height="32" border="0"></td></tr></table><p align="right">[<a href="linguist-manual-1.html">Prev: Introduction</a>] [<a href="linguist-manual.html">Home</a>] [<a href="linguist-manual-3.html">Next: Translators</a>]</p>
 <h2 align="center">Release Manager</h2>
 <!-- index Release Manager --><p>Two tools are provided for the release manager, <a href="linguist-manual-2.html#2">lupdate</a> and <a href="linguist-manual-2.html#3">lrelease</a>. These tools depend on <em>qmake</em> project files. You don't have to use <em>qmake</em>, though.</p>
-<p>A third tool, <tt>qm2ts</tt>, can be used for converting Qt 2.x message files to <tt>.ts</tt> files.</p>
+<p>A third tool, <tt>tqm2ts</tt>, can be used for converting Qt 2.x message files to <tt>.ts</tt> files.</p>
 <h3><a name="1"></a>Qt Project Files</h3>
 <!-- index .pro Files --><!-- index Project Files --><!-- index qmake!Project Files --><p><a href="linguist-manual-2.html#2">lupdate</a> and <a href="linguist-manual-2.html#3">lrelease</a> depend on information in the application's <tt>.pro</tt> Qt project file. There must be an entry in the <tt>TRANSLATIONS</tt> section of the project file for each language that is additional to the native language. A typical entry looks like this:</p>
 <!-- index TRANSLATIONS!in Project Files --><pre>    TRANSLATIONS    = tt2_fr.ts \
diff --git a/doc/html/makeqpf.html b/doc/html/makeqpf.html
index 54e1c11..e56614f 100644
--- a/doc/html/makeqpf.html
+++ b/doc/html/makeqpf.html
@@ -1,9 +1,9 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<!-- /home/espenr/tmp/qt-3.3.8-espenr-2499/qt-x11-free-3.3.8/doc/makeqpf.doc:36 -->
+<!-- /home/espenr/tmp/qt-3.3.8-espenr-2499/qt-x11-free-3.3.8/doc/maketqpf.doc:36 -->
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>makeqpf</title>
+<title>maketqpf</title>
 <style type="text/css"><!--
 fn { margin-left: 1cm; text-indent: -1cm; }
 a:link { color: #004faf; text-decoration: none }
@@ -29,7 +29,7 @@ body { background: #ffffff; color: black; }
  | <a href="functions.html">
 <font color="#004faf">Functions</font></a>
 </td>
-<td align="right" valign="center"><img src="logo32.png" align="right" width="64" height="32" border="0"></td></tr></table><h1 align=center>makeqpf</h1>
+<td align="right" valign="center"><img src="logo32.png" align="right" width="64" height="32" border="0"></td></tr></table><h1 align=center>maketqpf</h1>
 
 
 
@@ -37,7 +37,7 @@ body { background: #ffffff; color: black; }
 <p> <h2> Usage
 </h2>
 <a name="1"></a><p> <pre>
-makeqpf [-A] [-f spec-file] [font ...]
+maketqpf [-A] [-f spec-file] [font ...]
 </pre>
  
 <p> <ul>
diff --git a/doc/html/overviews-list.html b/doc/html/overviews-list.html
index 8630ec1..c47d38b 100644
--- a/doc/html/overviews-list.html
+++ b/doc/html/overviews-list.html
@@ -95,7 +95,7 @@ body { background: #ffffff; color: black; }
 </ul>
 <p> <td valign="top">
 <ul>
-<li> <a href="emb-qvfb.html">QVFb tool - virtual framebuffer for Qt/Embedded</a>
+<li> <a href="emb-tqvfb.html">QVFb tool - virtual framebuffer for Qt/Embedded</a>
 <p>&nbsp;</p>
 <li> <a href="emb-install.html">Installing Qt/Embedded</a>
 <li> <a href="emb-features.html">The Feature Definition File</a>
diff --git a/doc/html/porting2.html b/doc/html/porting2.html
index cfa84fd..70dbcb5 100644
--- a/doc/html/porting2.html
+++ b/doc/html/porting2.html
@@ -134,7 +134,7 @@ etc. are totally unaffected, but code that is
 <em>not</em> in functions of classes inherited from <code>Qt</code>,
 you must qualify these identifiers like this: <code>Qt::red,
 Qt::LeftButton, Qt::AlignRight</code>, etc.
-<p> <p>The <code>qt/bin/qt20fix</code> script helps to fix the code that
+<p> <p>The <code>qt/bin/tqt20fix</code> script helps to fix the code that
 needs adaption, though most code does not need changing.
 <p> Compiling with -DQT1COMPATIBILITY will help you get going with Qt 2.x
 - it allows all the old "dirty namespace" identifiers from Qt 1.x to
diff --git a/doc/html/qt.dcf b/doc/html/qt.dcf
index 0882ceb..1a8617c 100644
--- a/doc/html/qt.dcf
+++ b/doc/html/qt.dcf
@@ -9984,8 +9984,8 @@
 <section ref="tutorial2-04.html" title="Mainly Easy">
     <keyword ref="tutorial2-04.html">Mainly Easy</keyword>
 </section>
-<section ref="makeqpf.html" title="makeqpf">
-    <keyword ref="makeqpf.html">makeqpf</keyword>
+<section ref="maketqpf.html" title="maketqpf">
+    <keyword ref="maketqpf.html">maketqpf</keyword>
 </section>
 <section ref="functions.html" title="Member Function Index">
     <keyword ref="functions.html">Member Function Index</keyword>
@@ -10269,8 +10269,8 @@
 <section ref="emb-pointer.html" title="Qt/Embedded Pointer Handling">
     <keyword ref="emb-pointer.html">Qt/Embedded Pointer Handling</keyword>
 </section>
-<section ref="emb-qvfb.html" title="Qt/Embedded Virtual Framebuffer">
-    <keyword ref="emb-qvfb.html">Qt/Embedded Virtual Framebuffer</keyword>
+<section ref="emb-tqvfb.html" title="Qt/Embedded Virtual Framebuffer">
+    <keyword ref="emb-tqvfb.html">Qt/Embedded Virtual Framebuffer</keyword>
 </section>
 <section ref="qtmac-as-native.html" title="Qt/Mac is Mac OS X Native">
     <keyword ref="qtmac-as-native.html">Qt/Mac is Mac OS X Native</keyword>
diff --git a/doc/html/titleindex b/doc/html/titleindex
index 28a1f3a..5addadb 100644
--- a/doc/html/titleindex
+++ b/doc/html/titleindex
@@ -1061,7 +1061,7 @@ Qt's Tools | tools-list.html
 Qt/Embedded | qws.html
 Qt/Embedded Performance Tuning | emb-performance.html
 Qt/Embedded Pointer Handling | emb-pointer.html
-Qt/Embedded Virtual Framebuffer | emb-qvfb.html
+Qt/Embedded Virtual Framebuffer | emb-tqvfb.html
 Qt/Embedded as a VNC Server | emb-vnc.html
 Qt/Embedded environment variables | emb-envvars.html
 Qt/Mac Issues | mac-differences.html
@@ -1175,7 +1175,7 @@ chart/setdataform.cpp Example File | chart-setdataform-cpp.html
 chart/setdataform.h Example File | chart-setdataform-h.html
 iconview/simple_dd/main.cpp Example File | iconview-simple_dd-main-cpp.html
 iconview/simple_dd/main.h Example File | iconview-simple_dd-main-h.html
-makeqpf | makeqpf.html
+maketqpf | maketqpf.html
 qaccel.h Include File | qaccel-h.html
 qaccessible.h Include File | qaccessible-h.html
 qaction.h Include File | qaction-h.html
diff --git a/doc/html/tools-list.html b/doc/html/tools-list.html
index 15657e0..6f0dec8 100644
--- a/doc/html/tools-list.html
+++ b/doc/html/tools-list.html
@@ -46,9 +46,9 @@ help you need
 <li> <a href="qmake-manual.html">qmake</a> - create Makefiles from
 simple platform-independent project files
 <li> <a href="qembed.html">qembed</a> - convert data, e.g. images, into C++ code
-<li> <a href="emb-qvfb.html">qvfb</a> - run and test embedded
+<li> <a href="emb-tqvfb.html">tqvfb</a> - run and test embedded
 applications on the desktop
-<li> <a href="makeqpf.html">makeqpf</a> - create pre-rendered fonts
+<li> <a href="maketqpf.html">maketqpf</a> - create pre-rendered fonts
 for embedded devices
 <li> <a href="moc.html">moc</a> - the Meta Object Compiler
 <li> <a href="uic.html">uic</a> - the User Interface Compiler
diff --git a/doc/i18n.doc b/doc/i18n.doc
index 02bb195..c1800af 100644
--- a/doc/i18n.doc
+++ b/doc/i18n.doc
@@ -372,8 +372,8 @@ In your application, you must \l QTranslator::load() the translation
 files appropriate for the user's language, and install them using \l
 QApplication::installTranslator().
 
-If you have been using the old Qt tools (\c findtr, \c msg2qm and \c
-mergetr), you can use \e qm2ts to convert your old \c .qm files.
+If you have been using the old Qt tools (\c tqtfindtr, \c msg2tqm and \c
+tqtmergetr), you can use \e tqm2ts to convert your old \c .qm files.
 
 \e linguist, \e lupdate and \e lrelease are installed in the \c bin
 subdirectory of the base directory Qt is installed into. Click Help|Manual
diff --git a/doc/makeqpf.doc b/doc/makeqpf.doc
index 74600ba..b293c95 100644
--- a/doc/makeqpf.doc
+++ b/doc/makeqpf.doc
@@ -37,16 +37,16 @@
 **********************************************************************/
 
 /*!
-    \page makeqpf.html
+    \page maketqpf.html
 
-    \title makeqpf
+    \title maketqpf
 
 Saves QPF font files by rendering and saving fonts.
 
 \section1 Usage
 
 \code
-makeqpf [-A] [-f spec-file] [font ...]
+maketqpf [-A] [-f spec-file] [font ...]
 \endcode
 
 \list
diff --git a/doc/man/README b/doc/man/README
index de4ddcd..e9e38cf 100644
--- a/doc/man/README
+++ b/doc/man/README
@@ -36,14 +36,14 @@ Debian distribution
     (http://ftp.de.debian.org/debian/pool/main/q/qt-x11-free/)
         qt-x11-free_3.3.8b-11.*
         qt-x11-free_3.3.8b.orig.tar.gz
-  man1/createcw.1
+  man1/tqtcreatecw.1
   man1/designer.1
-  man1/findtr.1
+  man1/tqtfindtr.1
   man1/linguist.1
-  man1/makeqpf.1
-  man1/mergetr.1
-  man1/msg2qm.1
+  man1/maketqpf.1
+  man1/tqtmergetr.1
+  man1/msg2tqm.1
   man1/qembed.1
-  man1/qt20fix.1
+  man1/tqt20fix.1
   man1/qtconfig.1
-  man1/qvfb.1
+  man1/tqvfb.1
diff --git a/doc/man/man1/createcw.1 b/doc/man/man1/createcw.1
index 0959a2d..4567e5f 100644
--- a/doc/man/man1/createcw.1
+++ b/doc/man/man1/createcw.1
@@ -1,10 +1,10 @@
-.TH "createcw" "1" "3.0.3" "Troll Tech AS, Norway." ""
+.TH "tqtcreatecw" "1" "3.0.3" "Troll Tech AS, Norway." ""
 .SH "NAME"
 .LP 
-createcw \- custom widget description creater for Qt Designer
+tqtcreatecw \- custom widget description creater for Qt Designer
 .SH "SYNTAX"
 .LP 
-createcw <\fIfilename.cw\fP>
+tqtcreatecw <\fIfilename.cw\fP>
 .SH "DESCRIPTION"
 .LP 
 This small application makes it much easier to create
@@ -44,8 +44,8 @@ would write here
 After that compile the program, link it with your custom
 widget (library or object file) and run it like this:
 
- (unix): ./createcw mywidgets.cw
- (win32): createcw mywidgets.cw
+ (unix): ./tqtcreatecw mywidgets.cw
+ (win32): tqtcreatecw mywidgets.cw
 
 After that you can import this description file into the
 Qt Designer using the Custom\-Widget Dialog (See
diff --git a/doc/man/man1/findtr.1 b/doc/man/man1/findtr.1
index f1d3a87..163af79 100644
--- a/doc/man/man1/findtr.1
+++ b/doc/man/man1/findtr.1
@@ -1,10 +1,10 @@
-.TH "findtr" "1" "3.0.3" "Troll Tech AS, Norway." ""
+.TH "tqtfindtr" "1" "3.0.3" "Troll Tech AS, Norway." ""
 .SH "NAME"
 .LP 
-findtr \- Extracts information about text to be translated
+tqtfindtr \- Extracts information about text to be translated
 .SH "SYNTAX"
 .LP 
-findtr *.cpp *.h >myapp.po
+tqtfindtr *.cpp *.h >myapp.po
 .SH "DESCRIPTION"
 .LP 
 
@@ -17,7 +17,7 @@ translated versions of the file would then be
 myapp_de.po, myapp_fr.po, and myapp_ja.po for
 translations in German, French and Japanese respectively.
 
-  findtr *.cpp *.h >myapp.po
+  tqtfindtr *.cpp *.h >myapp.po
   copy myapp.po myapp_de.po
   edit myapp_de.po
 .SH "AUTHORS"
diff --git a/doc/man/man1/makeqpf.1 b/doc/man/man1/makeqpf.1
index 37ddcfd..641639c 100644
--- a/doc/man/man1/makeqpf.1
+++ b/doc/man/man1/makeqpf.1
@@ -1,11 +1,11 @@
-.TH "makeqpf" "1" "3.0.3" "Troll Tech AS, Norway." ""
+.TH "maketqpf" "1" "3.0.3" "Troll Tech AS, Norway." ""
 .SH "NAME"
 .LP 
-makeqpf \- Create qpf files from TTF and BDF files.
+maketqpf \- Create qpf files from TTF and BDF files.
 .SH "DESCRIPTION"
 .LP 
 Qt Prerendered Font (QPF) is a light\-weight non\-scalable
-font format specific to Qt/Embedded.  makeqpf is a tool
+font format specific to Qt/Embedded.  maketqpf is a tool
 that assists producing QPF files from TTF and BDF files.
 
 
diff --git a/doc/man/man1/mergetr.1 b/doc/man/man1/mergetr.1
index 9ed2a9f..a2c574f 100644
--- a/doc/man/man1/mergetr.1
+++ b/doc/man/man1/mergetr.1
@@ -1,21 +1,21 @@
-.TH "mergetr" "1" "3.0.3" "Troll Tech AS, Norway." ""
+.TH "tqtmergetr" "1" "3.0.3" "Troll Tech AS, Norway." ""
 .SH "NAME"
 .LP 
-mergetr \- Merge changes in translations
+tqtmergetr \- Merge changes in translations
 .SH "SYNTAX"
 .LP 
-mergetr myapp_de.po myapp.po
+tqtmergetr myapp_de.po myapp.po
 
 .SH "DESCRIPTION"
 .LP 
 When the texts in your program change as it is developed,
-a the base .po file can be regenerated using findtr,
-then mergetr can be used to merge the changes into the
+a the base .po file can be regenerated using tqtfindtr,
+then tqtmergetr can be used to merge the changes into the
 other .po files: 
 
-                mergetr myapp_de.po myapp.po
-                mergetr myapp_fr.po myapp.po
-                mergetr myapp_ja.po myapp.po
+                tqtmergetr myapp_de.po myapp.po
+                tqtmergetr myapp_fr.po myapp.po
+                tqtmergetr myapp_ja.po myapp.po
 
 
 The translation team then edits the new .po files to
diff --git a/doc/man/man1/msg2qm.1 b/doc/man/man1/msg2qm.1
index 7d22bbb..c350854 100644
--- a/doc/man/man1/msg2qm.1
+++ b/doc/man/man1/msg2qm.1
@@ -1,10 +1,10 @@
-.TH "msg2qm" "1" "3.0.3" "Troll Tech AS, Norway." ""
+.TH "msg2tqm" "1" "3.0.3" "Troll Tech AS, Norway." ""
 .SH "NAME"
 .LP 
-msg2qm \- Converts translated .po files to a Qt\-specific binary format.
+msg2tqm \- Converts translated .po files to a Qt\-specific binary format.
 .SH "SYNTAX"
 .LP 
-msg2qm myapp_de.po myapp_de.qm
+msg2tqm myapp_de.po myapp_de.qm
 .SH "DESCRIPTION"
 .LP 
 
@@ -14,9 +14,9 @@ are platform and locale independent, containing
 translations in Unicode and various hash tables to
 provide fast look\-up. 
 
-                msg2qm myapp_de.po myapp_de.qm
-                msg2qm myapp_fr.po myapp_fr.qm
-                msg2qm myapp_ja.po myapp_ja.qm
+                msg2tqm myapp_de.po myapp_de.qm
+                msg2tqm myapp_fr.po myapp_fr.qm
+                msg2tqm myapp_ja.po myapp_ja.qm
 
 
 In your application, use QTranslator::load() to load
diff --git a/doc/man/man1/qt20fix.1 b/doc/man/man1/qt20fix.1
index 352921b..247bb74 100644
--- a/doc/man/man1/qt20fix.1
+++ b/doc/man/man1/qt20fix.1
@@ -1,10 +1,10 @@
-.TH "qt20fix" "1" "3.0.3" "Troll Tech AS, Norway." ""
+.TH "tqt20fix" "1" "3.0.3" "Troll Tech AS, Norway." ""
 .SH "NAME"
 .LP 
-qt20fix \- Helps clean namespace when porting an app from Qt1 to Qt2
+tqt20fix \- Helps clean namespace when porting an app from Qt1 to Qt2
 .SH "SYNTAX"
 .LP 
-qt20fix myapp.cpp
+tqt20fix myapp.cpp
 
 .SH "DESCRIPTION"
 .LP 
@@ -19,7 +19,7 @@ functions of classes inherited from Qt, you must qualify
 these identifiers like this: Qt::red, Qt::LeftButton,
 Qt::AlignRight, etc. 
 
-The qt/bin/qt20fix script helps to fix the code that
+The qt/bin/tqt20fix script helps to fix the code that
 needs adaption, though most code does not need changing.
 
 Compiling with \-DQT1COMPATIBILITY will help you get going
diff --git a/doc/man/man1/qvfb.1 b/doc/man/man1/qvfb.1
index 0ae800d..acf02e1 100644
--- a/doc/man/man1/qvfb.1
+++ b/doc/man/man1/qvfb.1
@@ -1,7 +1,7 @@
-.TH "qvfb" "1" "3.0.3" "Troll Tech AS, Norway." ""
+.TH "tqvfb" "1" "3.0.3" "Troll Tech AS, Norway." ""
 .SH "NAME"
 .LP 
-qvfb \- Virtual framebuffer for Qt
+tqvfb \- Virtual framebuffer for Qt
 .SH "DESCRIPTION"
 .LP 
 The virtual framebuffer allows Qt/Embedded programs to be
@@ -19,7 +19,7 @@ driver, e.g.:
 You may prefer to set the QWS_DISPLAY environment
 variable to be QVFb:0. 
 
-qvfb supports the following command line options: 
+tqvfb supports the following command line options: 
 
  \-width width: the width of the virtual framebuffer
   (default: 240). 
@@ -36,7 +36,7 @@ qvfb supports the following command line options:
 
 The virtual framebuffer emulates a framebuffer using a
 shared memory region (the virtual frame buffer) and a
-utility to display the framebuffer in a window (qvfb).
+utility to display the framebuffer in a window (tqvfb).
 The regions of the display that have changed are updated
 periodically, so you will see discrete snapshots of the
 framebuffer rather than each individual drawing
@@ -45,12 +45,12 @@ flickering may not be apparent until the program is run
 using a real framebuffer. 
 
 The target refresh rate can be set via the "View|Refresh
-Rate" menu item. This will cause qvfb to check for
+Rate" menu item. This will cause tqvfb to check for
 updated regions more quickly. The rate is a target only.
 If little drawing is being done, the framebuffer will not
 show any updates between drawing events. If an
 application is displaying an animation the updates will
-be frequent, and the application and qvfb will compete
+be frequent, and the application and tqvfb will compete
 for processor time. 
 
 Mouse and keyboard events are passed to the Qt/Embedded
diff --git a/doc/overviews-list.doc b/doc/overviews-list.doc
index 9cfe3cd..4f36978 100644
--- a/doc/overviews-list.doc
+++ b/doc/overviews-list.doc
@@ -113,7 +113,7 @@
 
 \i
     \list
-    \i \link emb-qvfb.html  QVFb tool - virtual framebuffer for Qt/Embedded \endlink
+    \i \link emb-tqvfb.html  QVFb tool - virtual framebuffer for Qt/Embedded \endlink
     <p>&nbsp;</p>
     \i \link emb-install.html Installing Qt/Embedded \endlink
     \i \link emb-features.html The Feature Definition File \endlink
diff --git a/doc/porting2.doc b/doc/porting2.doc
index 1877446..1ce8f51 100644
--- a/doc/porting2.doc
+++ b/doc/porting2.doc
@@ -157,7 +157,7 @@ etc. are totally unaffected, but code that is
 you must qualify these identifiers like this: <code>Qt::red,
 Qt::LeftButton, Qt::AlignRight</code>, etc.
 
-<p>The <code>qt/bin/qt20fix</code> script helps to fix the code that
+<p>The <code>qt/bin/tqt20fix</code> script helps to fix the code that
 needs adaption, though most code does not need changing.
 
 Compiling with -DQT1COMPATIBILITY will help you get going with Qt 2.x
diff --git a/doc/qvfb.doc b/doc/qvfb.doc
index 7bc1546..e63ba51 100644
--- a/doc/qvfb.doc
+++ b/doc/qvfb.doc
@@ -36,24 +36,24 @@
 **
 **********************************************************************/
  
-/*! \page emb-qvfb.html
+/*! \page emb-tqvfb.html
 
 \title Qt/Embedded Virtual Framebuffer
 
 The virtual framebuffer allows Qt/Embedded programs to be developed on
 a desktop machine, without switching between consoles and X11.
 
-The virtual framebuffer is located in \c $QTDIR/tools/qvfb.
+The virtual framebuffer is located in \c $QTDIR/tools/tqvfb.
 
 \section1 Using the Virtual Framebuffer
 
 \list 1 
-\i Configure Qt/Embedded with the \c -qvfb argument and compile the library:
+\i Configure Qt/Embedded with the \c -tqvfb argument and compile the library:
     \code
-    ./configure -qvfb
+    ./configure -tqvfb
     make
     \endcode
-\i Compile \c qvfb as a normal Qt/X11 application and run it. Do \e not
+\i Compile \c tqvfb as a normal Qt/X11 application and run it. Do \e not
     compile it as a Qt/Embedded application.
 \i Start a Qt/Embedded master application (i.e., construct
     QApplication with the QApplication::GuiServer flag or use the \c
@@ -62,15 +62,15 @@ The virtual framebuffer is located in \c $QTDIR/tools/qvfb.
     \code
     masterapp -qws -display QVFb:0
     \endcode
-\i Qt/Embedded will autodetect qvfb, so you can omit the \c -display
-   command line parameter if you know that qvfb is running, and that
-   the Qt/Embedded library supports qvfb. (If this is not the case,
+\i Qt/Embedded will autodetect tqvfb, so you can omit the \c -display
+   command line parameter if you know that tqvfb is running, and that
+   the Qt/Embedded library supports tqvfb. (If this is not the case,
    Qt/Embedded will write to the real framebuffer, and your X11
    display will be corrupted.)
 
 \endlist
 
-\c qvfb supports the following command line options:
+\c tqvfb supports the following command line options:
  
 \table
 \header \i Option \i Meaning
@@ -95,18 +95,18 @@ The virtual framebuffer is located in \c $QTDIR/tools/qvfb.
 
 The virtual framebuffer emulates a framebuffer using a shared memory region
 (the virtual frame buffer) and a utility to display the framebuffer in a
-window (\c qvfb). The regions of the display that have changed are updated
+window (\c tqvfb). The regions of the display that have changed are updated
 periodically, so you will see discrete snapshots of the framebuffer rather
 than each individual drawing operation. For this reason drawing problems
 such as flickering may not be apparent until the program is run using a real
 framebuffer.
 
 The target refresh rate can be set via the <b>View|Refresh Rate</b>
-menu item. This will cause \c qvfb to check for updated regions more
+menu item. This will cause \c tqvfb to check for updated regions more
 frequently. The rate is a target only. If little drawing is being
 done, the framebuffer will not show any updates between drawing
 events. If an application is displaying an animation the updates will
-be frequent, then the application and \c qvfb will compete for
+be frequent, then the application and \c tqvfb will compete for
 processor time.
 
 Mouse and keyboard events are passed to the Qt/Embedded master process via
@@ -114,6 +114,6 @@ named pipes.
 
 The virtual framebuffer is a development tool only. No security issues have
 been considered in the virtual framebuffer design. It should be avoided
-in a production environment; do not configure production libraries with \c -qvfb.
+in a production environment; do not configure production libraries with \c -tqvfb.
 
 */
diff --git a/doc/qws.doc b/doc/qws.doc
index 746baa9..6f82d31 100644
--- a/doc/qws.doc
+++ b/doc/qws.doc
@@ -178,7 +178,7 @@ make, edit \c $QTDIR/include/qconfig.h and change the definition of
 
 \i This document shows how to use Qt/Embedded with the Linux framebuffer. For
 development and debugging purposes it is often easier to use the \link
-emb-qvfb.html Qt/Embedded virtual framebuffer\endlink instead.
+emb-tqvfb.html Qt/Embedded virtual framebuffer\endlink instead.
 
 
 \endlist
@@ -222,7 +222,7 @@ support in Qt/Embedded for writing a QPF font file from any font, so
 you can initially enable TTF and BDF formats, save QPF files for the
 fonts and sizes you need, then remove TTF and BDF support.
 
-See \link makeqpf.html tools/makeqpf\endlink for a tool that helps
+See \link maketqpf.html tools/maketqpf\endlink for a tool that helps
 produce QPF files from the TTF and BDF, or just run your application
 with the \c -savefonts option.
 
@@ -326,7 +326,7 @@ generate all 4 rotations of fonts would be to run the following at a real frameb
 <pre>
 for dpy in LinuxFb Transformed:Rot90 Transformed:Rot180 Transformed:Rot270
 do
-    QWS_DISPLAY=$dpy ./makeqpf "$@"
+    QWS_DISPLAY=$dpy ./maketqpf "$@"
 done
 </pre>
 If programs are only ever run in one orientation on a device, only the one
@@ -354,7 +354,7 @@ command line option.
 This document assumes you have the Linux framebuffer configured correctly
 and no master process is running. If you do not have a working Linux
 framebuffer you can use the
-\link emb-qvfb.html Qt/Embedded virtual framebuffer\endlink, or you can
+\link emb-tqvfb.html Qt/Embedded virtual framebuffer\endlink, or you can
 run Qt/Embedded as a \link emb-vnc.html VNC server\endlink.
 
 Change to a Linux console and select an example to run, e.g. \c
@@ -663,7 +663,7 @@ another size, e.g. \c QWS_SIZE=240x320.
 VNC clients are available for a vast array of display systems: X11,
 Windows, Amiga, DOS, VMS, and dozens of others.
 
-The \link emb-qvfb.html Qt Virtual Framebuffer \endlink is an alternative
+The \link emb-tqvfb.html Qt Virtual Framebuffer \endlink is an alternative
 technique. It uses shared memory and thus is much faster and smoother, but
 it does not operate over a network.
 
diff --git a/doc/tools-list.doc b/doc/tools-list.doc
index 096417a..e3e16a0 100644
--- a/doc/tools-list.doc
+++ b/doc/tools-list.doc
@@ -16,9 +16,9 @@
     \i \link qmake-manual.book  qmake \endlink - create Makefiles from
     simple platform-independent project files
     \i \link qembed.html  qembed\endlink - convert data, e.g. images, into C++ code
-    \i \link emb-qvfb.html  qvfb\endlink - run and test embedded
+    \i \link emb-tqvfb.html  tqvfb\endlink - run and test embedded
     applications on the desktop
-    \i \link makeqpf.html makeqpf\endlink - create pre-rendered fonts
+    \i \link maketqpf.html maketqpf\endlink - create pre-rendered fonts
     for embedded devices
     \i \link moc.html moc\endlink - the Meta Object Compiler
     \i \link uic.html uic\endlink - the User Interface Compiler