Replace QObject, QWidget, QImage, QPair, QRgb, QColor, QChar, QString, QIODevice with TQ* version

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

doc/artsbuilder/detail.docbook

@@ -1415,7 +1415,7 @@ once you assigned something else (like a null reference).
 <para>
 The equivalent C++ terms would be
 <programlisting>
-   QWidget* w;
+   TQWidget* w;
    w-&gt;show();
 </programlisting>
 

doc/artsbuilder/mcop.docbook

@@ -2197,11 +2197,11 @@ that, I am certainly proven wrong.
 While I do know that &DCOP; basically doesn't know about the data types
 it sends, so that you could use &DCOP; without using &Qt;, look at how
 it is used in daily &kde; usage: people send types like
-<classname>QString</classname>, <classname>QRect</classname>,
+<classname>TQString</classname>, <classname>QRect</classname>,
 <classname>QPixmap</classname>, <classname>QCString</classname>, ...,
 around. These use &Qt;-serialization. So if somebody choose to support
 &DCOP; in a GNOME program, they would either have to claim to use
-<classname>QString</classname>,...  types (although they don't do so),
+<classname>TQString</classname>,...  types (although they don't do so),
 and emulate the way &Qt; does the streaming, or they would send other
 string, pixmap and rect types around, and thus not be interoperable.
 </para>

noatun/modules/making_plugins

@@ -6,7 +6,7 @@ You're free to use the net plugin as a base, I've licensed it under the
 public domain, so you can relicense it however you wish (preferably not
 GPL, though :)
 
-Remember that QObject must derive first.
+Remember that TQObject must derive first.
 
 Do a "return this;" in the PlayList *playlist() const; function, if your class
 is a playlist, otherwise, don't even override that function.