Automated update from Qt3

1 files changed, 6 insertions, 6 deletions

diff --git a/doc/man/man3/tqcolor.3qt b/doc/man/man3/tqcolor.3qt
index 041778daa..2537b2037 100644
--- a/doc/man/man3/tqcolor.3qt
+++ b/doc/man/man3/tqcolor.3qt
@@ -179,7 +179,7 @@ In addition to the RGB value, a QColor also has a pixel value and a validity. Th
 .PP
 The validity (isValid()) indicates whether the color is legal at all. For example, a RGB color with RGB values out of range is illegal. For performance reasons, QColor mostly disregards illegal colors. The result of using an invalid color is unspecified and will usually be surprising.
 .PP
-There are 19 predefined QColor objects: \fCwhite\fR, \fCblack\fR, \fCred\fR, \fCdarkRed\fR, \fCgreen\fR, \fCdarkGreen\fR, \fCblue\fR, \fCdarkBlue\fR, \fCcyan\fR, \fCdarkCyan\fR, \fCmagenta\fR, \fCdarkMagenta\fR, \fCyellow\fR, \fCdarkYellow\fR, \fCgray\fR, \fCdarkGray\fR, \fClightGray\fR, \fCcolor0\fR and \fCcolor1\fR, accessible as members of the Qt namespace (ie. \fCQt::red\fR).
+There are 19 predefined QColor objects: \fCwhite\fR, \fCblack\fR, \fCred\fR, \fCdarkRed\fR, \fCgreen\fR, \fCdarkGreen\fR, \fCblue\fR, \fCdarkBlue\fR, \fCcyan\fR, \fCdarkCyan\fR, \fCmagenta\fR, \fCdarkMagenta\fR, \fCyellow\fR, \fCdarkYellow\fR, \fCgray\fR, \fCdarkGray\fR, \fClightGray\fR, \fCcolor0\fR and \fCcolor1\fR, accessible as members of the TQt namespace (ie. \fCQt::red\fR).
 .PP
 <center>
 .ce 1
@@ -225,7 +225,7 @@ V, for value, is 0-255 and represents lightness or brightness of the color. 0 is
 .PP
 Here are some examples: Pure red is H=0, S=255, V=255. A dark red, moving slightly towards the magenta, could be H=350 (equivalent to -10), S=255, V=180. A grayish light red could have H about 0 (say 350-359 or 0-10), S about 50-100, and S=255.
 .PP
-Qt returns a hue value of -1 for achromatic colors. If you pass a too-big hue value, Qt forces it into range. Hue 360 or 720 is treated as 0; hue 540 is treated as 180.
+Qt returns a hue value of -1 for achromatic colors. If you pass a too-big hue value, TQt forces it into range. Hue 360 or 720 is treated as 0; hue 540 is treated as 180.
 .PP
 See also QPalette, QColorGroup, QApplication::setColorSpec(), Color FAQ, Widget Appearance and Style, Graphics Classes, and Image Processing Classes.
 .SS "Member Type Documentation"
@@ -289,7 +289,7 @@ Internal clean up required for QColor. This function is called from the QApplica
 .PP
 See also initialize().
 .SH "QStringList QColor::colorNames ()\fC [static]\fR"
-Returns a QStringList containing the color names Qt knows about.
+Returns a QStringList containing the color names TQt knows about.
 .SH "int QColor::currentAllocContext ()\fC [static]\fR"
 Returns the current color allocation context.
 .PP
@@ -352,7 +352,7 @@ Example:
 .PP
 The example code loads a pixmap from file. It frees up all colors that were allocated the last time loadPixmap() was called.
 .PP
-The initial/default context is 0. Qt keeps a list of colors associated with their allocation contexts. You can call destroyAllocContext() to get rid of all colors that were allocated in a specific context.
+The initial/default context is 0. TQt keeps a list of colors associated with their allocation contexts. You can call destroyAllocContext() to get rid of all colors that were allocated in a specific context.
 .PP
 Calling enterAllocContext() enters an allocation context. The allocation context lasts until you call leaveAllocContext(). QColor has an internal stack of allocation contexts. Each call to enterAllocContex() must have a corresponding leaveAllocContext().
 .PP
@@ -580,8 +580,8 @@ If you find a bug in Qt, please report it as described in
 .BR http://doc.trolltech.com/bughowto.html .
 Good bug reports help us to help you. Thank you.
 .P
-The definitive Qt documentation is provided in HTML format; it is
-located at $QTDIR/doc/html and can be read using Qt Assistant or with
+The definitive TQt documentation is provided in HTML format; it is
+located at $QTDIR/doc/html and can be read using TQt Assistant or with
 a web browser. This man page is provided as a convenience for those
 users who prefer man pages, although this format is not officially
 supported by Trolltech.