14 files changed, 36 insertions, 36 deletions
diff --git a/doc/html/emb-fonts.html b/doc/html/emb-fonts.html
index 234c53f..6583963 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="maketqpf.html">tools/maketqpf</a> for a tool that helps
+<p> See <a href="makeqpf.html">tools/makeqpf</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 ./maketqpf "$@"
+    QWS_DISPLAY=$dpy ./makeqpf "$@"
 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 d04a04a..47ae22a 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-tqvfb.html">Qt/Embedded virtual framebuffer</a> instead.
+development and debugging purposes it is often easier to use the <a href="emb-qvfb.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 c2a301e..df971cc 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/tqvfb.doc:36 -->
+<!-- /home/espenr/tmp/qt-3.3.8-espenr-2499/qt-x11-free-3.3.8/doc/qvfb.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/tqvfb</tt>.
+<p> The virtual framebuffer is located in <tt>$QTDIR/tools/qvfb</tt>.
 <p> <h2> Using the Virtual Framebuffer
 </h2>
 <a name="1"></a><p> <ol type=1> 
-<li> Configure Qt/Embedded with the <tt>-tqvfb</tt> argument and compile the library:
+<li> Configure Qt/Embedded with the <tt>-qvfb</tt> argument and compile the library:
 <pre>
-    ./configure -tqvfb
+    ./configure -qvfb
     make
     </pre>
  
-<li> Compile <tt>tqvfb</tt> as a normal Qt/X11 application and run it. Do <em>not</em>
+<li> Compile <tt>qvfb</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 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,
+<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,
 Qt/Embedded will write to the real framebuffer, and your X11
 display will be corrupted.)
 <p> </ol>
-<p> <tt>tqvfb</tt> supports the following command line options:
+<p> <tt>qvfb</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>tqvfb</tt>). The regions of the display that have changed are updated
+window (<tt>qvfb</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>tqvfb</tt> to check for updated regions more
+menu item. This will cause <tt>qvfb</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>tqvfb</tt> will compete for
+be frequent, then the application and <tt>qvfb</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>-tqvfb</tt>.
+in a production environment; do not configure production libraries with <tt>-qvfb</tt>.
 <p> 
 <!-- eof -->
 <p><address><hr><div align=center>
diff --git a/doc/html/emb-running.html b/doc/html/emb-running.html
index 499d99e..fae839b 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-tqvfb.html">Qt/Embedded virtual framebuffer</a>, or you can
+<a href="emb-qvfb.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 8a1a09a..6d88dba 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-tqvfb.html">Qt Virtual Framebuffer</a> is an alternative
+<p> The <a href="emb-qvfb.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 3efb156..2b3803a 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>tqtfindtr</tt>, <tt>msg2tqm</tt> and <tt>tqtmergetr</tt>), you can use <em>tqm2ts</em> to convert your old <tt>.qm</tt> files.
+<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> <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 c98b4c2..cc7ca30 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-tqvfb.html
+"Qt/Embedded Virtual Framebuffer" emb-qvfb.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
-"maketqpf" maketqpf.html
+"makeqpf" makeqpf.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 79dc168..e95e386 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>tqm2ts</tt>, can be used for converting Qt 2.x message files to <tt>.ts</tt> files.</p>
+<p>A third tool, <tt>qm2ts</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 e56614f..54e1c11 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/maketqpf.doc:36 -->
+<!-- /home/espenr/tmp/qt-3.3.8-espenr-2499/qt-x11-free-3.3.8/doc/makeqpf.doc:36 -->
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<title>maketqpf</title>
+<title>makeqpf</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>maketqpf</h1>
+<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>
 
 
 
@@ -37,7 +37,7 @@ body { background: #ffffff; color: black; }
 <p> <h2> Usage
 </h2>
 <a name="1"></a><p> <pre>
-maketqpf [-A] [-f spec-file] [font ...]
+makeqpf [-A] [-f spec-file] [font ...]
 </pre>
  
 <p> <ul>
diff --git a/doc/html/overviews-list.html b/doc/html/overviews-list.html
index c47d38b..8630ec1 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-tqvfb.html">QVFb tool - virtual framebuffer for Qt/Embedded</a>
+<li> <a href="emb-qvfb.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 70dbcb5..cfa84fd 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/tqt20fix</code> script helps to fix the code that
+<p> <p>The <code>qt/bin/qt20fix</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 1a8617c..0882ceb 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="maketqpf.html" title="maketqpf">
-    <keyword ref="maketqpf.html">maketqpf</keyword>
+<section ref="makeqpf.html" title="makeqpf">
+    <keyword ref="makeqpf.html">makeqpf</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-tqvfb.html" title="Qt/Embedded Virtual Framebuffer">
-    <keyword ref="emb-tqvfb.html">Qt/Embedded Virtual Framebuffer</keyword>
+<section ref="emb-qvfb.html" title="Qt/Embedded Virtual Framebuffer">
+    <keyword ref="emb-qvfb.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 5addadb..28a1f3a 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-tqvfb.html
+Qt/Embedded Virtual Framebuffer | emb-qvfb.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
-maketqpf | maketqpf.html
+makeqpf | makeqpf.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 6f0dec8..15657e0 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-tqvfb.html">tqvfb</a> - run and test embedded
+<li> <a href="emb-qvfb.html">qvfb</a> - run and test embedded
 applications on the desktop
-<li> <a href="maketqpf.html">maketqpf</a> - create pre-rendered fonts
+<li> <a href="makeqpf.html">makeqpf</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