Automated update from Qt3

1 files changed, 22 insertions, 22 deletions

diff --git a/doc/man/man3/tqwidget.3qt b/doc/man/man3/tqwidget.3qt
index a654663b3..96dec5719 100644
--- a/doc/man/man3/tqwidget.3qt
+++ b/doc/man/man3/tqwidget.3qt
@@ -1005,7 +1005,7 @@ A widget that isn't embedded in a parent widget is called a top-level widget. Us
 .PP
 A widget without a parent widget is always a top-level widget.
 .PP
-Non-top-level widgets are child widgets. These are child windows in their parent widgets. You cannot usually distinguish a child widget from its parent visually. Most other widgets in Qt are useful only as child widgets. (It is possible to make, say, a button into a top-level widget, but most people prefer to put their buttons inside other widgets, e.g. QDialog.)
+Non-top-level widgets are child widgets. These are child windows in their parent widgets. You cannot usually distinguish a child widget from its parent visually. Most other widgets in TQt are useful only as child widgets. (It is possible to make, say, a button into a top-level widget, but most people prefer to put their buttons inside other widgets, e.g. QDialog.)
 .PP
 If you want to use a QWidget to hold child widgets you will probably want to add a layout to the parent QWidget. (See Layouts.)
 .PP
@@ -1143,7 +1143,7 @@ The widget flags argument, \fIf\fR, is normally 0, but it can be set to customiz
 .PP
 If you add a child widget to an already visible widget you must explicitly show the child to make it visible.
 .PP
-Note that the X11 version of Qt may not be able to deliver all combinations of style flags on all systems. This is because on X11, Qt can only ask the window manager, and the window manager can override the application's settings. On Windows, Qt can set whatever flags you want.
+Note that the X11 version of TQt may not be able to deliver all combinations of style flags on all systems. This is because on X11, TQt can only ask the window manager, and the window manager can override the application's settings. On Windows, TQt can set whatever flags you want.
 .PP
 Example:
 .PP
@@ -1489,7 +1489,7 @@ This widget receives all mouse events until releaseMouse() is called; other widg
 .PP
 \fBWarning:\fR Bugs in mouse-grabbing applications very often lock the terminal. Use this function with extreme caution, and consider using the \fC-nograb\fR command line option while debugging.
 .PP
-It is almost never necessary to grab the mouse when using Qt, as Qt grabs and releases it sensibly. In particular, Qt grabs the mouse when a mouse button is pressed and keeps it until the last button is released.
+It is almost never necessary to grab the mouse when using Qt, as TQt grabs and releases it sensibly. In particular, TQt grabs the mouse when a mouse button is pressed and keeps it until the last button is released.
 .PP
 Note that only visible widgets can grab mouse input. If isVisible() returns FALSE for a widget, that widget cannot call grabMouse().
 .PP
@@ -1673,7 +1673,7 @@ See also raise() and stackUnder().
 .SH "bool QWidget::macEvent ( MSG * )\fC [virtual protected]\fR"
 This special event handler can be reimplemented in a subclass to receive native Macintosh events.
 .PP
-In your reimplementation of this function, if you want to stop the event being handled by Qt, return TRUE. If you return FALSE, this native event is passed back to Qt, which translates the event into a Qt event and sends it to the widget.
+In your reimplementation of this function, if you want to stop the event being handled by Qt, return TRUE. If you return FALSE, this native event is passed back to Qt, which translates the event into a TQt event and sends it to the widget.
 .PP
 \fBWarning:\fR This function is not portable.
 .PP
@@ -1804,7 +1804,7 @@ A paint event is a request to repaint all or part of the widget. It can happen a
 .PP
 Many widgets can simply repaint their entire surface when asked to, but some slow widgets need to optimize by painting only the requested region: QPaintEvent::region(). This speed optimization does not change the result, as painting is clipped to that region during event processing. QListView and QCanvas do this, for example.
 .PP
-Qt also tries to speed up painting by merging multiple paint events into one. When update() is called several times or the window system sends several paint events, Qt merges these events into one event with a larger region (see QRegion::unite()). repaint() does not permit this optimization, so we suggest using update() when possible.
+Qt also tries to speed up painting by merging multiple paint events into one. When update() is called several times or the window system sends several paint events, TQt merges these events into one event with a larger region (see QRegion::unite()). repaint() does not permit this optimization, so we suggest using update() when possible.
 .PP
 When the paint event occurs, the update region has normally been erased, so that you're painting on the widget's background. There are a couple of exceptions and QPaintEvent::erased() tells you whether the widget has been erased or not.
 .PP
@@ -1853,7 +1853,7 @@ Returns the position of the widget within its parent widget. See the "pos" prope
 .SH "bool QWidget::qwsEvent ( QWSEvent * )\fC [virtual protected]\fR"
 This special event handler can be reimplemented in a subclass to receive native Qt/Embedded events.
 .PP
-In your reimplementation of this function, if you want to stop the event being handled by Qt, return TRUE. If you return FALSE, this native event is passed back to Qt, which translates the event into a Qt event and sends it to the widget.
+In your reimplementation of this function, if you want to stop the event being handled by Qt, return TRUE. If you return FALSE, this native event is passed back to Qt, which translates the event into a TQt event and sends it to the widget.
 .PP
 \fBWarning:\fR This function is not portable.
 .PP
@@ -1869,7 +1869,7 @@ Example: showimg/showimg.cpp.
 .SH "void QWidget::recreate ( QWidget * parent, WFlags f, const QPoint & p, bool showIt = FALSE )"
 \fBThis function is obsolete.\fR It is provided to keep old source working. We strongly advise against using it in new code.
 .PP
-This method is provided to aid porting from Qt 1.0 to 2.0. It has been renamed reparent() in Qt 2.0.
+This method is provided to aid porting from TQt 1.0 to 2.0. It has been renamed reparent() in TQt 2.0.
 .SH "QRect QWidget::rect () const"
 Returns the internal geometry of the widget excluding any window frame. See the "rect" property for details.
 .SH "void QWidget::releaseKeyboard ()"
@@ -1883,11 +1883,11 @@ See also grabMouse(), grabKeyboard(), and releaseKeyboard().
 .SH "void QWidget::repaint ( int x, int y, int w, int h, bool erase = TRUE )\fC [slot]\fR"
 Repaints the widget directly by calling paintEvent() immediately, unless updates are disabled or the widget is hidden.
 .PP
-If \fIerase\fR is TRUE, Qt erases the area \fI(x, y, w, h)\fR before the paintEvent() call.
+If \fIerase\fR is TRUE, TQt erases the area \fI(x, y, w, h)\fR before the paintEvent() call.
 .PP
 If \fIw\fR is negative, it is replaced with \fCwidth() - x\fR, and if \fIh\fR is negative, it is replaced width \fCheight() - y\fR.
 .PP
-We suggest only using repaint() if you need an immediate repaint, for example during animation. In almost all circumstances update() is better, as it permits Qt to optimize for speed and minimize flicker.
+We suggest only using repaint() if you need an immediate repaint, for example during animation. In almost all circumstances update() is better, as it permits TQt to optimize for speed and minimize flicker.
 .PP
 \fBWarning:\fR If you call repaint() in a function which may itself be called from paintEvent(), you may get infinite recursion. The update() function never causes recursion.
 .PP
@@ -2112,7 +2112,7 @@ Sets enables or disables the use of input methods for this widget to \fIb\fR. Se
 .SH "void QWidget::setKeyCompression ( bool compress )\fC [virtual protected]\fR"
 Enables key event compression, if \fIcompress\fR is TRUE, and disables it if \fIcompress\fR is FALSE.
 .PP
-Key compression is off by default (except for QLineEdit and QTextEdit), so widgets receive one key press event for each key press (or more, since autorepeat is usually on). If you turn it on and your program doesn't keep up with key input, Qt may try to compress key events so that more than one character can be processed in each event.
+Key compression is off by default (except for QLineEdit and QTextEdit), so widgets receive one key press event for each key press (or more, since autorepeat is usually on). If you turn it on and your program doesn't keep up with key input, TQt may try to compress key events so that more than one character can be processed in each event.
 .PP
 For example, a word processor widget might receive 2, 3 or more characters in each QKeyEvent::text(), if the layout recalculation takes too long for the CPU.
 .PP
@@ -2289,7 +2289,7 @@ See also Qt::WindowState and windowState().
 .SH "void QWidget::show ()\fC [virtual slot]\fR"
 Shows the widget and its child widgets.
 .PP
-If its size or position has changed, Qt guarantees that a widget gets move and resize events just before it is shown.
+If its size or position has changed, TQt guarantees that a widget gets move and resize events just before it is shown.
 .PP
 You almost never have to reimplement this function. If you need to change some settings before a widget is shown, use showEvent() instead. If you need to do some delayed initialization use polish().
 .PP
@@ -2427,7 +2427,7 @@ Resets the widget's palette. See the "palette" property for details.
 .SH "void QWidget::update ()\fC [slot]\fR"
 Updates the widget unless updates are disabled or the widget is hidden.
 .PP
-This function does not cause an immediate repaint; instead it schedules a paint event for processing when Qt returns to the main event loop. This permits Qt to optimize for more speed and less flicker than a call to repaint() does.
+This function does not cause an immediate repaint; instead it schedules a paint event for processing when TQt returns to the main event loop. This permits TQt to optimize for more speed and less flicker than a call to repaint() does.
 .PP
 Calling update() several times normally results in just one paintEvent() call.
 .PP
@@ -2442,7 +2442,7 @@ This is an overloaded member function, provided for convenience. It behaves esse
 .PP
 Updates a rectangle (\fIx\fR, \fIy\fR, \fIw\fR, \fIh\fR) inside the widget unless updates are disabled or the widget is hidden.
 .PP
-This function does not cause an immediate repaint; instead it schedules a paint event for processing when Qt returns to the main event loop. This permits Qt to optimize for more speed and less flicker and a call to repaint() does.
+This function does not cause an immediate repaint; instead it schedules a paint event for processing when TQt returns to the main event loop. This permits TQt to optimize for more speed and less flicker and a call to repaint() does.
 .PP
 Calling update() several times normally results in just one paintEvent() call.
 .PP
@@ -2456,7 +2456,7 @@ This is an overloaded member function, provided for convenience. It behaves esse
 .PP
 Updates a rectangle \fIr\fR inside the widget unless updates are disabled or the widget is hidden.
 .PP
-This function does not cause an immediate repaint; instead it schedules a paint event for processing when Qt returns to the main event loop. This permits Qt to optimize for more speed and less flicker and a call to repaint() does.
+This function does not cause an immediate repaint; instead it schedules a paint event for processing when TQt returns to the main event loop. This permits TQt to optimize for more speed and less flicker and a call to repaint() does.
 .PP
 Calling update() several times normally results in just one paintEvent() call.
 .SH "void QWidget::updateGeometry ()"
@@ -2484,7 +2484,7 @@ Returns the width of the widget excluding any window frame. See the "width" prop
 .SH "bool QWidget::winEvent ( MSG * )\fC [virtual protected]\fR"
 This special event handler can be reimplemented in a subclass to receive native Windows events.
 .PP
-In your reimplementation of this function, if you want to stop the event being handled by Qt, return TRUE. If you return FALSE, this native event is passed back to Qt, which translates the event into a Qt event and sends it to the widget.
+In your reimplementation of this function, if you want to stop the event being handled by Qt, return TRUE. If you return FALSE, this native event is passed back to Qt, which translates the event into a TQt event and sends it to the widget.
 .PP
 \fBWarning:\fR This function is not portable.
 .PP
@@ -2514,7 +2514,7 @@ Returns the x coordinate of the widget relative to its parent including any wind
 .SH "bool QWidget::x11Event ( XEvent * )\fC [virtual protected]\fR"
 This special event handler can be reimplemented in a subclass to receive native X11 events.
 .PP
-In your reimplementation of this function, if you want to stop the event being handled by Qt, return TRUE. If you return FALSE, this native event is passed back to Qt, which translates the event into a Qt event and sends it to the widget.
+In your reimplementation of this function, if you want to stop the event being handled by Qt, return TRUE. If you return FALSE, this native event is passed back to Qt, which translates the event into a TQt event and sends it to the widget.
 .PP
 \fBWarning:\fR This function is not portable.
 .PP
@@ -2751,7 +2751,7 @@ When changing the geometry, the widget, if visible, receives a move event (moveE
 .PP
 The size component is adjusted if it lies outside the range defined by minimumSize() and maximumSize().
 .PP
-setGeometry() is virtual, and all other overloaded setGeometry() implementations in Qt call it.
+setGeometry() is virtual, and all other overloaded setGeometry() implementations in TQt call it.
 .PP
 \fBWarning:\fR Calling setGeometry() inside resizeEvent() or moveEvent() can lead to infinite recursion.
 .PP
@@ -2859,7 +2859,7 @@ This property holds whether this widget is maximized.
 .PP
 This property is only relevant for top-level widgets.
 .PP
-Note that due to limitations in some window-systems, this does not always report the expected results (e.g. if the user on X11 maximizes the window via the window manager, Qt has no way of distinguishing this from any other resize). This is expected to improve as window manager protocols evolve.
+Note that due to limitations in some window-systems, this does not always report the expected results (e.g. if the user on X11 maximizes the window via the window manager, TQt has no way of distinguishing this from any other resize). This is expected to improve as window manager protocols evolve.
 .PP
 See also windowState(), showMaximized(), visible, show(), hide(), showNormal(), and minimized.
 .PP
@@ -3019,7 +3019,7 @@ If the widget is a top-level widget, the position is that of the widget on the d
 .PP
 When changing the position, the widget, if visible, receives a move event (moveEvent()) immediately. If the widget is not currently visible, it is guaranteed to receive an event before it is shown.
 .PP
-move() is virtual, and all other overloaded move() implementations in Qt call it.
+move() is virtual, and all other overloaded move() implementations in TQt call it.
 .PP
 \fBWarning:\fR Calling move() or setGeometry() inside moveEvent() can lead to infinite recursion.
 .PP
@@ -3055,7 +3055,7 @@ The size is adjusted if it lies outside the range defined by minimumSize() and m
 .PP
 If you want a top-level window to have a fixed size, call setResizeMode( QLayout::FreeResize ) on its layout.
 .PP
-resize() is virtual, and all other overloaded resize() implementations in Qt call it.
+resize() is virtual, and all other overloaded resize() implementations in TQt call it.
 .PP
 \fBWarning:\fR Calling resize() or setGeometry() inside resizeEvent() can lead to infinite recursion.
 .PP
@@ -3207,8 +3207,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.