Replace QObject, QWidget, QImage, QPair, QRgb, QColor, QChar, QString, QIODevice with TQ* versionr14.1.1

Signed-off-by: Michele Calgaro <[email protected]>
(cherry picked from commit b35e0845dc9b3c8b9a5e52a682c769f383933fae)

1 files changed, 3 insertions, 3 deletions

diff --git a/doc/shclass.doc b/doc/shclass.doc
index 4d7ccadbb..02bb129ab 100644
--- a/doc/shclass.doc
+++ b/doc/shclass.doc
@@ -194,7 +194,7 @@ These classes have a detach() function that can be called if you want
 your object to get a private copy of the shared data. They also have a
 copy() function that returns a deep copy with a reference count of 1.
 
-The same is true for \l QImage, which does not inherit QMemArray. \l
+The same is true for \l TQImage, which does not inherit QMemArray. \l
 QMovie is also explicitly shared, but it does not support detach() or
 copy().
 
@@ -216,7 +216,7 @@ The TQt classes that are implicitly shared are:
 \i \l QPixmap
 \i \l QRegion
 \i \l QRegExp
-\i \l QString
+\i \l TQString
 \i \l QStringList
 \i \l QValueList
 \i \l QValueStack
@@ -255,6 +255,6 @@ QValueVector, etc.) while you are iterating over it.
 inherited from QByteArray, such as data(), employ explicit sharing, while
 those only in QCString detach automatically. Thus, QCString is rather an
 "experts only" class, provided mainly to ease porting from TQt 1.x to TQt 2.0.
-We recommend that you use \l QString, a purely implicitly shared class.
+We recommend that you use \l TQString, a purely implicitly shared class.
 
 */