13 files changed, 39 insertions, 39 deletions
diff --git a/doc/man/man1/moc.1 b/doc/man/man1/moc.1
index 749b3de5..5e524454 100644
--- a/doc/man/man1/moc.1
+++ b/doc/man/man1/moc.1
@@ -116,7 +116,7 @@ like this:
 .in +4
 .nf
 class YourClass : public QObject {
-    Q_OBJECT
+    TQ_OBJECT
     Q_PROPERTY( ... )
     Q_CLASSINFO( ... )
 
@@ -215,7 +215,7 @@ example:
 .in +4
 .nf
 class SomeTemplate<int> : public QFrame {
-    Q_OBJECT
+    TQ_OBJECT
     ....
 signals:
     void bugInMocDetected( int );
@@ -255,7 +255,7 @@ better alternative.  Here is an example of illegal syntax:
 .in +4
 .nf
 class SomeClass : public QObject {
-    Q_OBJECT
+    TQ_OBJECT
     ...
 public slots:
     // illegal
@@ -271,7 +271,7 @@ You can work around this restriction like this:
 typedef void (*ApplyFunctionType)( List *, void * );
 
 class SomeClass : public QObject {
-    Q_OBJECT
+    TQ_OBJECT
     ...
 public slots:
     void apply( ApplyFunctionType, char * );
@@ -296,7 +296,7 @@ sections instead.  Here is an example of the illegal syntax:
 .in +4
 .nf
 class SomeClass : public QObject {
-    Q_OBJECT
+    TQ_OBJECT
     ...
 signals:
     friend class ClassTemplate<char>; // illegal
@@ -358,7 +358,7 @@ Here's an example:
 .in +4
 .nf
 class A {
-    Q_OBJECT
+    TQ_OBJECT
 public:
     class B {
     public slots: // illegal
@@ -389,7 +389,7 @@ sections, where they belong.  Here is an example of the illegal syntax:
 .in +4
 .nf
 class SomeClass : public QObject {
-    Q_OBJECT
+    TQ_OBJECT
 public slots:
     SomeClass( QObject *parent, const char *name )
         : QObject( parent, name ) {} // illegal
@@ -410,7 +410,7 @@ illegal syntax:
 .in +4
 .nf
 class SomeClass : public QObject {
-    Q_OBJECT
+    TQ_OBJECT
 public:
     ...
     // illegal
@@ -425,12 +425,12 @@ public:
 .in -4
 .PP
 Work around this limitation by declaring all properties at the
-beginning of the class declaration, right after Q_OBJECT:
+beginning of the class declaration, right after TQ_OBJECT:
 .PP
 .in +4
 .nf
 class SomeClass : public QObject {
-    Q_OBJECT
+    TQ_OBJECT
     Q_PROPERTY( Priority priority READ priority WRITE setPriority )
     Q_ENUMS( Priority )
 public:
diff --git a/doc/man/man3/qapplication.3qt b/doc/man/man3/qapplication.3qt
index d75fb46b..10d6bb92 100644
--- a/doc/man/man3/qapplication.3qt
+++ b/doc/man/man3/qapplication.3qt
@@ -409,7 +409,7 @@ Inherits QObject.
 .BI "void \fBQ_ASSERT\fR ( bool test )"
 .br
 .ti -1c
-.BI "void \fBQ_CHECK_PTR\fR ( void * p )"
+.BI "void \fBTQ_CHECK_PTR\fR ( void * p )"
 .br
 .ti -1c
 .BI "QtMsgHandler \fBqInstallMsgHandler\fR ( QtMsgHandler h )"
@@ -1705,7 +1705,7 @@ If \fCb\fR is zero, the Q_ASSERT statement will output the following message usi
 .fi
 .PP
 See also qWarning() and Debugging.
-.SH "void Q_CHECK_PTR ( void * p )"
+.SH "void TQ_CHECK_PTR ( void * p )"
 If \fIp\fR is 0, prints a warning message containing the source code file name and line number, saying that the program ran out of memory.
 .PP
 This is really a macro defined in ntqglobal.h.
@@ -1717,12 +1717,12 @@ Example:
         int *a;
 .br
 .br
-        Q_CHECK_PTR( a = new int[80] );  // WRONG!
+        TQ_CHECK_PTR( a = new int[80] );  // WRONG!
 .br
 .br
         a = new (nothrow) int[80];       // Right
 .br
-        Q_CHECK_PTR( a );
+        TQ_CHECK_PTR( a );
 .br
 .fi
 .PP
@@ -1934,7 +1934,7 @@ This function does nothing when Qt is built with \fCQT_NO_DEBUG\fR defined.
 .SH "const char * qVersion ()"
 Returns the Qt version number as a string, for example, "2.3.0" or" 3.0.5".
 .PP
-The \fCQT_VERSION\fR define has the numeric value in the form: 0xmmiibb (m = major, i = minor, b = bugfix). For example, Qt 3.0.5's \fCQT_VERSION\fR is 0x030005.
+The \fCTQT_VERSION\fR define has the numeric value in the form: 0xmmiibb (m = major, i = minor, b = bugfix). For example, Qt 3.0.5's \fCTQT_VERSION\fR is 0x030005.
 .SH "void qWarning ( const char * msg, ... )"
 Prints a warning message \fImsg\fR, or calls the message handler (if it has been installed).
 .PP
diff --git a/doc/man/man3/qaxbindable.3qt b/doc/man/man3/qaxbindable.3qt
index 756b1514..919bb512 100644
--- a/doc/man/man3/qaxbindable.3qt
+++ b/doc/man/man3/qaxbindable.3qt
@@ -56,7 +56,7 @@ The functions provided by this class allow an ActiveX control to communicate pro
 .br
     {
 .br
-        Q_OBJECT
+        TQ_OBJECT
 .br
         Q_PROPERTY( int value READ value WRITE setValue )
 .br
diff --git a/doc/man/man3/qaxobject.3qt b/doc/man/man3/qaxobject.3qt
index 40413832..f1b60674 100644
--- a/doc/man/man3/qaxobject.3qt
+++ b/doc/man/man3/qaxobject.3qt
@@ -53,7 +53,7 @@ A QAxObject can be instantiated as an empty object, with the name of the COM obj
 .PP
 QAxObject is a QObject and can be used as such, e.g. it can be organized in an object hierarchy, receive events and connect to signals and slots.
 .PP
-\fBWarning:\fR You can subclass QAxObject, but you cannot use the Q_OBJECT macro in the subclass (the generated moc-file will not compile), so you cannot add further signals, slots or properties. This limitation is due to the metaobject information generated in runtime. To work around this problem, aggregate the QAxObject as a member of the QObject subclass.
+\fBWarning:\fR You can subclass QAxObject, but you cannot use the TQ_OBJECT macro in the subclass (the generated moc-file will not compile), so you cannot add further signals, slots or properties. This limitation is due to the metaobject information generated in runtime. To work around this problem, aggregate the QAxObject as a member of the QObject subclass.
 .PP
 .SH MEMBER FUNCTION DOCUMENTATION
 .SH "QAxObject::QAxObject ( QObject * parent = 0, const char * name = 0 )"
diff --git a/doc/man/man3/qaxwidget.3qt b/doc/man/man3/qaxwidget.3qt
index 5aaf3c98..c153b3cf 100644
--- a/doc/man/man3/qaxwidget.3qt
+++ b/doc/man/man3/qaxwidget.3qt
@@ -60,7 +60,7 @@ A QAxWidget can be instantiated as an empty object, with the name of the ActiveX
 .PP
 QAxWidget is a QWidget and can be used as such, e.g. it can be organized in a widget hierarchy, receive events or act as an event filter. Standard widget properties, e.g. enabled are supported, but it depends on the ActiveX control to implement support for ambient properties like e.g. palette or font. QAxWidget tries to provide the necessary hints.
 .PP
-\fBWarning:\fR You can subclass QAxWidget, but you cannot use the Q_OBJECT macro in the subclass (the generated moc-file will not compile), so you cannot add further signals, slots or properties. This limitation is due to the metaobject information generated in runtime. To work around this problem, aggregate the QAxWidget as a member of the QObject subclass.
+\fBWarning:\fR You can subclass QAxWidget, but you cannot use the TQ_OBJECT macro in the subclass (the generated moc-file will not compile), so you cannot add further signals, slots or properties. This limitation is due to the metaobject information generated in runtime. To work around this problem, aggregate the QAxWidget as a member of the QObject subclass.
 .PP
 .SH MEMBER FUNCTION DOCUMENTATION
 .SH "QAxWidget::QAxWidget ( QWidget * parent = 0, const char * name = 0, WFlags f = 0 )"
diff --git a/doc/man/man3/qbytearray.3qt b/doc/man/man3/qbytearray.3qt
index 72b3b1e4..071b0ee7 100644
--- a/doc/man/man3/qbytearray.3qt
+++ b/doc/man/man3/qbytearray.3qt
@@ -56,18 +56,18 @@ Constructs a QByteArray of size \fIsize\fR.
 .SH "QByteArray qCompress ( const QByteArray & data )"
 Compresses the array \fIdata\fR and returns the compressed byte array using zlib.
 .PP
-See also qUncompress().
+See also tqUncompress().
 .SH "QByteArray qCompress ( const uchar * data, int nbytes )"
 This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
 .PP
 Compresses the array \fIdata\fR which is \fInbytes\fR long and returns the compressed byte array.
-.SH "QByteArray qUncompress ( const QByteArray & data )"
+.SH "QByteArray tqUncompress ( const QByteArray & data )"
 Uncompresses the array \fIdata\fR and returns the uncompressed byte array.
 .PP
 Returns an empty QByteArray if the input data was corrupt.
 .PP
 See also qCompress().
-.SH "QByteArray qUncompress ( const uchar * data, int nbytes )"
+.SH "QByteArray tqUncompress ( const uchar * data, int nbytes )"
 This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
 .PP
 Uncompresses the array \fIdata\fR which is \fInbytes\fR long and returns
diff --git a/doc/man/man3/qcstring.3qt b/doc/man/man3/qcstring.3qt
index 9e81755c..2b291cfb 100644
--- a/doc/man/man3/qcstring.3qt
+++ b/doc/man/man3/qcstring.3qt
@@ -1054,7 +1054,7 @@ Special case I: Returns 0 if \fIstr1\fR and \fIstr2\fR are both 0.
 .PP
 Special case II: Returns a random nonzero value if \fIstr1\fR is 0 or \fIstr2\fR is 0 (but not both).
 .PP
-See also qstrncmp(), qstricmp(), qstrnicmp(), and Note on character comparisons.
+See also tqstrncmp(), qstricmp(), qstrnicmp(), and Note on character comparisons.
 .SH "char * qstrcpy ( char * dst, const char * src )"
 A safe strcpy() function.
 .PP
@@ -1076,12 +1076,12 @@ Special case I: Returns 0 if \fIstr1\fR and \fIstr2\fR are both 0.
 .PP
 Special case II: Returns a random nonzero value if \fIstr1\fR is 0 or \fIstr2\fR is 0 (but not both).
 .PP
-See also qstrcmp(), qstrncmp(), qstrnicmp(), and Note on character comparisons.
-.SH "uint qstrlen ( const char * str )"
+See also qstrcmp(), tqstrncmp(), qstrnicmp(), and Note on character comparisons.
+.SH "uint tqstrlen ( const char * str )"
 A safe strlen function.
 .PP
 Returns the number of characters that precede the terminating '&#92;0'. or 0 if \fIstr\fR is 0.
-.SH "int qstrncmp ( const char * str1, const char * str2, uint len )"
+.SH "int tqstrncmp ( const char * str1, const char * str2, uint len )"
 A safe strncmp() function.
 .PP
 Compares at most \fIlen\fR bytes of \fIstr1\fR and \fIstr2\fR.
@@ -1110,7 +1110,7 @@ Special case I: Returns 0 if \fIstr1\fR and \fIstr2\fR are both 0.
 .PP
 Special case II: Returns a random nonzero value if \fIstr1\fR is 0 or \fIstr2\fR is 0 (but not both).
 .PP
-See also qstrcmp(), qstrncmp(), qstricmp(), and Note on character comparisons.
+See also qstrcmp(), tqstrncmp(), qstricmp(), and Note on character comparisons.
 
 .SH "SEE ALSO"
 .BR http://doc.trolltech.com/ntqcstring.html
diff --git a/doc/man/man3/qfile.3qt b/doc/man/man3/qfile.3qt
index c47a8fde..841ef89f 100644
--- a/doc/man/man3/qfile.3qt
+++ b/doc/man/man3/qfile.3qt
@@ -372,7 +372,7 @@ Example:
 .br
         f.open( IO_WriteOnly, stderr );
 .br
-        f.writeBlock( msg, qstrlen(msg) );      // write to stderr
+        f.writeBlock( msg, tqstrlen(msg) );      // write to stderr
 .br
         f.close();
 .br
diff --git a/doc/man/man3/qglwidget.3qt b/doc/man/man3/qglwidget.3qt
index a6b94bf6..c1282249 100644
--- a/doc/man/man3/qglwidget.3qt
+++ b/doc/man/man3/qglwidget.3qt
@@ -157,7 +157,7 @@ Here is a rough outline of how a QGLWidget subclass might look:
 .br
     {
 .br
-        Q_OBJECT        // must include this if you use Qt signals/slots
+        TQ_OBJECT        // must include this if you use Qt signals/slots
 .br
 .br
     public:
diff --git a/doc/man/man3/qobject.3qt b/doc/man/man3/qobject.3qt
index 8725b085..f83c0ab1 100644
--- a/doc/man/man3/qobject.3qt
+++ b/doc/man/man3/qobject.3qt
@@ -209,7 +209,7 @@ QObjects can receive events through event() and filter the events of other objec
 .PP
 Last but not least, QObject provides the basic timer support in Qt; see QTimer for high-level support for timers.
 .PP
-Notice that the Q_OBJECT macro is mandatory for any object that implements signals, slots or properties. You also need to run the moc program (Meta Object Compiler) on the source file. We strongly recommend the use of this macro in \fIall\fR subclasses of QObject regardless of whether or not they actually use signals, slots and properties, since failure to do so may lead certain functions to exhibit undefined behaviour.
+Notice that the TQ_OBJECT macro is mandatory for any object that implements signals, slots or properties. You also need to run the moc program (Meta Object Compiler) on the source file. We strongly recommend the use of this macro in \fIall\fR subclasses of QObject regardless of whether or not they actually use signals, slots and properties, since failure to do so may lead certain functions to exhibit undefined behaviour.
 .PP
 All Qt widgets inherit QObject. The convenience function isWidgetType() returns whether an object is actually a widget. It is much faster than inherits( "QWidget" ).
 .PP
@@ -290,7 +290,7 @@ Returns the class name of this object.
 .PP
 This function is generated by the Meta Object Compiler.
 .PP
-\fBWarning:\fR This function will return the wrong name if the class definition lacks the Q_OBJECT macro.
+\fBWarning:\fR This function will return the wrong name if the class definition lacks the TQ_OBJECT macro.
 .PP
 See also name, inherits(), isA(), and isWidgetType().
 .PP
@@ -322,7 +322,7 @@ A signal can also be connected to another signal:
 .br
     {
 .br
-        Q_OBJECT
+        TQ_OBJECT
 .br
     public:
 .br
@@ -741,7 +741,7 @@ See also timerEvent(), startTimer(), and killTimer().
 .SH "QMetaObject * QObject::metaObject () const\fC [virtual]\fR"
 Returns a pointer to the meta object of this object.
 .PP
-A meta object contains information about a class that inherits QObject, e.g. class name, superclass name, properties, signals and slots. Every class that contains the Q_OBJECT macro will also have a meta object.
+A meta object contains information about a class that inherits QObject, e.g. class name, superclass name, properties, signals and slots. Every class that contains the TQ_OBJECT macro will also have a meta object.
 .PP
 The meta object information is required by the signal/slot connection mechanism and the property system. The functions isA() and inherits() also make use of the meta object.
 .SH "const char * QObject::name () const"
@@ -870,7 +870,7 @@ Example:
 .br
     {
 .br
-        Q_OBJECT
+        TQ_OBJECT
 .br
     public:
 .br
@@ -924,7 +924,7 @@ See also startTimer(), killTimer(), killTimers(), and event().
 Examples:
 .)l biff/biff.cpp, dclock/dclock.cpp, forever/forever.cpp, grapher/grapher.cpp, qmag/qmag.cpp, and xform/xform.cpp.
 .SH "QString QObject::tr ( const char * sourceText, const char * comment )\fC [static]\fR"
-Returns a translated version of \fIsourceText\fR, or \fIsourceText\fR itself if there is no appropriate translated version. The translation context is QObject with \fIcomment\fR (0 by default). All QObject subclasses using the Q_OBJECT macro automatically have a reimplementation of this function with the subclass name as context.
+Returns a translated version of \fIsourceText\fR, or \fIsourceText\fR itself if there is no appropriate translated version. The translation context is QObject with \fIcomment\fR (0 by default). All QObject subclasses using the TQ_OBJECT macro automatically have a reimplementation of this function with the subclass name as context.
 .PP
 \fBWarning:\fR This method is reentrant only if all translators are installed \fIbefore\fR calling this method. Installing or removing translators while performing translations is not supported. Doing so will probably result in crashes or other undesirable behavior.
 .PP
diff --git a/doc/man/man3/qspinbox.3qt b/doc/man/man3/qspinbox.3qt
index 0d4d34d7..f4b92223 100644
--- a/doc/man/man3/qspinbox.3qt
+++ b/doc/man/man3/qspinbox.3qt
@@ -224,7 +224,7 @@ For example, these functions could be changed so that the user provided values f
 .br
         {
 .br
-            Q_OBJECT
+            TQ_OBJECT
 .br
         public:
 .br
diff --git a/doc/man/man3/qvaluelist.3qt b/doc/man/man3/qvaluelist.3qt
index 43cfe8fd..c42a7677 100644
--- a/doc/man/man3/qvaluelist.3qt
+++ b/doc/man/man3/qvaluelist.3qt
@@ -333,7 +333,7 @@ Notice that the latest changes to Mary's salary did not affect the value in the
 .PP
 There are several ways to find items in the list. The begin() and end() functions return iterators to the beginning and end of the list. The advantage of getting an iterator is that you can move forward or backward from this position by incrementing/decrementing the iterator. The iterator returned by end() points to the item which is one \fIpast\fR the last item in the container. The past-the-end iterator is still associated with the list it belongs to, however it is \fInot\fR dereferenceable; operator*() will not return a well-defined value. If the list is empty(), the iterator returned by begin() will equal the iterator returned by end().
 .PP
-Another way to find an item in the list is by using the qFind() algorithm. For example:
+Another way to find an item in the list is by using the tqFind() algorithm. For example:
 .PP
 .nf
 .br
@@ -341,7 +341,7 @@ Another way to find an item in the list is by using the qFind() algorithm. For e
 .br
     ...
 .br
-    QValueList<int>::iterator it = qFind( list.begin(), list.end(), 3 );
+    QValueList<int>::iterator it = tqFind( list.begin(), list.end(), 3 );
 .br
     if ( it != list.end() )
 .br
diff --git a/doc/man/man3/qvaluevector.3qt b/doc/man/man3/qvaluevector.3qt
index 4c0fd516..8999a4be 100644
--- a/doc/man/man3/qvaluevector.3qt
+++ b/doc/man/man3/qvaluevector.3qt
@@ -337,7 +337,7 @@ Whenever inserting, removing or referencing elements in a vector, always make su
 .PP
 The iterators provided by vector are random access iterators, therefore you can use them with many generic algorithms, for example, algorithms provided by the STL or the QTL.
 .PP
-Another way to find an element in the vector is by using the std::find() or qFind() algorithms. For example:
+Another way to find an element in the vector is by using the std::find() or tqFind() algorithms. For example:
 .PP
 .nf
 .br
@@ -345,7 +345,7 @@ Another way to find an element in the vector is by using the std::find() or qFin
 .br
     ...
 .br
-    QValueVector<int>::const_iterator it = qFind( vec.begin(), vec.end(), 3 );
+    QValueVector<int>::const_iterator it = tqFind( vec.begin(), vec.end(), 3 );
 .br
     if ( it != vector.end() )
 .br