diff options
Diffstat (limited to 'doc/man/man3')
83 files changed, 131 insertions, 131 deletions
diff --git a/doc/man/man3/qapplication.3qt b/doc/man/man3/qapplication.3qt index 19693773..a62a6d9e 100644 --- a/doc/man/man3/qapplication.3qt +++ b/doc/man/man3/qapplication.3qt @@ -830,7 +830,7 @@ The default implementation requests interaction and sends a close event to all v .PP See also isSessionRestored(), sessionId(), saveState(), and the Session Management overview. .SH "int QApplication::cursorFlashTime ()\fC [static]\fR" -Returns the text cursor's flash (blink) time in milliseconds. The flash time is the time retquired to display, invert and restore the caret display. +Returns the text cursor's flash (blink) time in milliseconds. The flash time is the time required to display, invert and restore the caret display. .PP The default value on X11 is 1000 milliseconds. On Windows, the control panel value is used. .PP @@ -1258,7 +1258,7 @@ QApplication::NormalColor. This is the default color allocation strategy. Use th .TP QApplication::CustomColor. Use this option if your application needs a small number of custom colors. On X11, this option is the same as NormalColor. On Windows, Qt creates a Windows palette, and allocates colors to it on demand. .TP -QApplication::ManyColor. Use this option if your application is very color hungry (e.g. it retquires thousands of colors). Under X11 the effect is: +QApplication::ManyColor. Use this option if your application is very color hungry (e.g. it requires thousands of colors). Under X11 the effect is: .TP For 256-color displays which have at best a 256 color true color visual, the default visual is used, and colors are allocated from a color cube. The color cube is the 6x6x6 (216 color) "Web palette"<sup>*</sup>, but the number of colors can be changed by the \fI-ncols\fR option. The user can force the application to use the true color visual with the -visual option. .TP @@ -1295,7 +1295,7 @@ See also colorSpec(), QColor::numBitPlanes(), and QColor::enterAllocContext(). Examples: .)l helpviewer/main.cpp, opengl/main.cpp, showimg/main.cpp, t9/main.cpp, tetrax/tetrax.cpp, tetrix/tetrix.cpp, and themes/main.cpp. .SH "void QApplication::setCursorFlashTime ( int msecs )\fC [static]\fR" -Sets the text cursor's flash (blink) time to \fImsecs\fR milliseconds. The flash time is the time retquired to display, invert and restore the caret display. Usually the text cursor is displayed for \fImsecs/2\fR milliseconds, then hidden for \fImsecs/2\fR milliseconds, but this may vary. +Sets the text cursor's flash (blink) time to \fImsecs\fR milliseconds. The flash time is the time required to display, invert and restore the caret display. Usually the text cursor is displayed for \fImsecs/2\fR milliseconds, then hidden for \fImsecs/2\fR milliseconds, but this may vary. .PP Note that on Microsoft Windows, calling this function sets the cursor flash time for all windows. .PP @@ -1451,7 +1451,7 @@ See also QWidget::palette, palette(), and QStyle::polish(). Examples: .)l i18n/main.cpp, themes/metal.cpp, themes/themes.cpp, and themes/wood.cpp. .SH "void QApplication::setReverseLayout ( bool b )\fC [static]\fR" -If \fIb\fR is TRUE, all dialogs and widgets will be laid out in a mirrored fashion, as retquired by right to left languages such as Arabic and Hebrew. If \fIb\fR is FALSE, dialogs and widgets are laid out left to right. +If \fIb\fR is TRUE, all dialogs and widgets will be laid out in a mirrored fashion, as required by right to left languages such as Arabic and Hebrew. If \fIb\fR is FALSE, dialogs and widgets are laid out left to right. .PP Changing this flag in runtime does not cause a relayout of already instantiated widgets. .PP diff --git a/doc/man/man3/qassistantclient.3qt b/doc/man/man3/qassistantclient.3qt index a48f2ebd..cc22b529 100644 --- a/doc/man/man3/qassistantclient.3qt +++ b/doc/man/man3/qassistantclient.3qt @@ -63,7 +63,7 @@ The QAssistantClient class provides a means of using Qt Assistant as an applicat .PP Using Qt Assistant is simple: Create a QAssistantClient instance, then call showPage() as often as necessary to show your help pages. When you call showPage(), Qt Assistant will be launched if it isn't already running. .PP -The QAssistantClient instance can open (openAssistant()) or close (closeAssistant()) Qt Assistant whenever retquired. If Qt Assistant is open, isOpen() returns TRUE. +The QAssistantClient instance can open (openAssistant()) or close (closeAssistant()) Qt Assistant whenever required. If Qt Assistant is open, isOpen() returns TRUE. .PP One QAssistantClient instance interacts with one Qt Assistant instance, so every time you call openAssistant(), showPage() or closeAssistant() they are applied to the particular Qt Assistant instance associated with the QAssistantClient. .PP diff --git a/doc/man/man3/qaxbase.3qt b/doc/man/man3/qaxbase.3qt index 7c17b261..154031b5 100644 --- a/doc/man/man3/qaxbase.3qt +++ b/doc/man/man3/qaxbase.3qt @@ -263,7 +263,7 @@ If you reimplement this function you must also reimplement the destructor to cal .SH "QString QAxBase::control () const" Returns the name of the COM object wrapped by this QAxBase object. See the "control" property for details. .SH "void QAxBase::disableClassInfo ()" -Disables the class info generation for this ActiveX container. If you don't retquire any class information about the ActiveX control use this function to speed up the meta object generation. +Disables the class info generation for this ActiveX container. If you don't require any class information about the ActiveX control use this function to speed up the meta object generation. .PP Note that this function must be called immediately after construction of the object (without passing an object identifier), and before calling QAxWidget->setControl(). .SH "void QAxBase::disableEventSink ()" diff --git a/doc/man/man3/qaxbindable.3qt b/doc/man/man3/qaxbindable.3qt index 186e7f6c..756b1514 100644 --- a/doc/man/man3/qaxbindable.3qt +++ b/doc/man/man3/qaxbindable.3qt @@ -48,7 +48,7 @@ This class is defined in the \fBQt ActiveQt Extension\fR, which can be found in .PP The QAxBindable class provides an interface between a QWidget and an ActiveX client. .PP -The functions provided by this class allow an ActiveX control to communicate property changes to a client application. Inherit your control class from both QWidget (directly or indirectly) and this class to get access to this class's functions. The meta object compiler retquires you to inherit from QWidget \fIfirst\fR. +The functions provided by this class allow an ActiveX control to communicate property changes to a client application. Inherit your control class from both QWidget (directly or indirectly) and this class to get access to this class's functions. The meta object compiler requires you to inherit from QWidget \fIfirst\fR. .PP .nf .br diff --git a/doc/man/man3/qaxwidget.3qt b/doc/man/man3/qaxwidget.3qt index dda250d9..5aaf3c98 100644 --- a/doc/man/man3/qaxwidget.3qt +++ b/doc/man/man3/qaxwidget.3qt @@ -187,7 +187,7 @@ l - l. WM_SYSKEYDOWN WM_SYSKEYUP WM_KEYDOWN All keycodes VK_MENU .PP This table is the result of experimenting with popular ActiveX controls, ie. Internet Explorer and Microsoft Office applications, but for some -controls it might retquire modification. +controls it might require modification. .SH "SEE ALSO" .BR http://doc.trolltech.com/qaxwidget.html diff --git a/doc/man/man3/qbitarray.3qt b/doc/man/man3/qbitarray.3qt index 3f7777a4..5b155f89 100644 --- a/doc/man/man3/qbitarray.3qt +++ b/doc/man/man3/qbitarray.3qt @@ -106,7 +106,7 @@ Because QBitArray is a QMemArray, it uses explicit sharing with a reference coun .PP A QBitArray is a special byte array that can access individual bits and perform bit-operations (AND, OR, XOR and NOT) on entire arrays or bits. .PP -Bits can be manipulated by the setBit() and clearBit() functions, but it is also possible to use the indexing [] operator to test and set individual bits. The [] operator is a little slower than setBit() and clearBit() because some tricks are retquired to implement single-bit assignments. +Bits can be manipulated by the setBit() and clearBit() functions, but it is also possible to use the indexing [] operator to test and set individual bits. The [] operator is a little slower than setBit() and clearBit() because some tricks are required to implement single-bit assignments. .PP Example: .PP diff --git a/doc/man/man3/qbitval.3qt b/doc/man/man3/qbitval.3qt index d3778e42..6f23a0f6 100644 --- a/doc/man/man3/qbitval.3qt +++ b/doc/man/man3/qbitval.3qt @@ -31,7 +31,7 @@ All the functions in this class are reentrant when Qt is built with thread suppo .SH DESCRIPTION The QBitVal class is an internal class, used with QBitArray. .PP -The QBitVal is retquired by the indexing [] operator on bit arrays. It is not for use in any other context. +The QBitVal is required by the indexing [] operator on bit arrays. It is not for use in any other context. .PP See also Collection Classes. .SH MEMBER FUNCTION DOCUMENTATION diff --git a/doc/man/man3/qcanvas.3qt b/doc/man/man3/qcanvas.3qt index eade4e78..4067e90b 100644 --- a/doc/man/man3/qcanvas.3qt +++ b/doc/man/man3/qcanvas.3qt @@ -240,7 +240,7 @@ Destroys the canvas and all the canvas's canvas items. .SH "void QCanvas::advance ()\fC [virtual slot]\fR" Moves all QCanvasItem::animated() canvas items on the canvas and refreshes all changes to all views of the canvas. (An `animated' item is an item that is in motion; see setVelocity().) .PP -The advance takes place in two phases. In phase 0, the QCanvasItem::advance() function of each QCanvasItem::animated() canvas item is called with paramater 0. Then all these canvas items are called again, with parameter 1. In phase 0, the canvas items should not change position, merely examine other items on the canvas for which special processing is retquired, such as collisions between items. In phase 1, all canvas items should change positions, ignoring any other items on the canvas. This two-phase approach allows for considerations of "fairness", although no QCanvasItem subclasses supplied with Qt do anything interesting in phase 0. +The advance takes place in two phases. In phase 0, the QCanvasItem::advance() function of each QCanvasItem::animated() canvas item is called with paramater 0. Then all these canvas items are called again, with parameter 1. In phase 0, the canvas items should not change position, merely examine other items on the canvas for which special processing is required, such as collisions between items. In phase 1, all canvas items should change positions, ignoring any other items on the canvas. This two-phase approach allows for considerations of "fairness", although no QCanvasItem subclasses supplied with Qt do anything interesting in phase 0. .PP The canvas can be configured to call this function periodically with setAdvancePeriod(). .PP @@ -331,7 +331,7 @@ This signal is emitted whenever the canvas is resized. Each QCanvasView connects .SH "void QCanvas::retune ( int chunksze, int mxclusters = 100 )\fC [virtual]\fR" Change the efficiency tuning parameters to \fImxclusters\fR clusters, each of size \fIchunksze\fR. This is a slow operation if there are many objects on the canvas. .PP -The canvas is divided into chunks which are rectangular areas \fIchunksze\fR wide by \fIchunksze\fR high. Use a chunk size which is about the average size of the canvas items. If you choose a chunk size which is too small it will increase the amount of calculation retquired when drawing since each change will affect many chunks. If you choose a chunk size which is too large the amount of drawing retquired will increase because for each change, a lot of drawing will be retquired since there will be many (unchanged) canvas items which are in the same chunk as the changed canvas items. +The canvas is divided into chunks which are rectangular areas \fIchunksze\fR wide by \fIchunksze\fR high. Use a chunk size which is about the average size of the canvas items. If you choose a chunk size which is too small it will increase the amount of calculation required when drawing since each change will affect many chunks. If you choose a chunk size which is too large the amount of drawing required will increase because for each change, a lot of drawing will be required since there will be many (unchanged) canvas items which are in the same chunk as the changed canvas items. .PP Internally, a canvas uses a low-resolution "chunk matrix" to keep track of all the items in the canvas. A 64x64 chunk matrix is the default for a 1024x1024 pixel canvas, where each chunk collects canvas items in a 16x16 pixel square. This default is also affected by setTiles(). You can tune this default using this function. For example if you have a very large canvas and want to trade off speed for memory then you might set the chunk size to 32 or 64. .PP diff --git a/doc/man/man3/qcanvaspolygonalitem.3qt b/doc/man/man3/qcanvaspolygonalitem.3qt index f622d513..8d417628 100644 --- a/doc/man/man3/qcanvaspolygonalitem.3qt +++ b/doc/man/man3/qcanvaspolygonalitem.3qt @@ -74,7 +74,7 @@ The QCanvasPolygonalItem class provides a polygonal canvas item on a QCanvas. .PP The mostly rectangular classes, such as QCanvasSprite and QCanvasText, use the object's bounding rectangle for movement, repainting and collision calculations. For most other items, the bounding rectangle can be far too large -- a diagonal line being the worst case, and there are many other cases which are also bad. QCanvasPolygonalItem provides polygon-based bounding rectangle handling, etc., which is much faster for non-rectangular items. .PP -Derived classes should try to define as small an area as possible to maximize efficiency, but the polygon must \fIdefinitely\fR be contained completely within the polygonal area. Calculating the exact retquirements is usually difficult, but if you allow a small overestimate it can be easy and tquick, while still getting almost all of QCanvasPolygonalItem's speed. +Derived classes should try to define as small an area as possible to maximize efficiency, but the polygon must \fIdefinitely\fR be contained completely within the polygonal area. Calculating the exact requirements is usually difficult, but if you allow a small overestimate it can be easy and tquick, while still getting almost all of QCanvasPolygonalItem's speed. .PP Note that all subclasses \fImust\fR call hide() in their destructor since hide() needs to be able to access areaPoints(). .PP diff --git a/doc/man/man3/qcanvasspline.3qt b/doc/man/man3/qcanvasspline.3qt index 349eb042..7f5f296c 100644 --- a/doc/man/man3/qcanvasspline.3qt +++ b/doc/man/man3/qcanvasspline.3qt @@ -70,9 +70,9 @@ Reimplemented from QCanvasPolygon. .SH "void QCanvasSpline::setControlPoints ( QPointArray ctrl, bool close = TRUE )" Set the spline control points to \fIctrl\fR. .PP -If \fIclose\fR is TRUE, then the first point in \fIctrl\fR will be re-used as the last point, and the number of control points must be a multiple of 3. If \fIclose\fR is FALSE, one additional control point is retquired, and the number of control points must be one of (4, 7, 10, 13, ...). +If \fIclose\fR is TRUE, then the first point in \fIctrl\fR will be re-used as the last point, and the number of control points must be a multiple of 3. If \fIclose\fR is FALSE, one additional control point is required, and the number of control points must be one of (4, 7, 10, 13, ...). .PP -If the number of control points doesn't meet the above conditions, the number of points will be truncated to the largest number of points that do meet the retquirement. +If the number of control points doesn't meet the above conditions, the number of points will be truncated to the largest number of points that do meet the requirement. .PP Example: canvas/canvas.cpp. diff --git a/doc/man/man3/qcolor.3qt b/doc/man/man3/qcolor.3qt index d493a402..ff039730 100644 --- a/doc/man/man3/qcolor.3qt +++ b/doc/man/man3/qcolor.3qt @@ -285,7 +285,7 @@ See also enterAllocContext(). .SH "int QColor::blue () const" Returns the B (blue) component of the RGB value. .SH "void QColor::cleanup ()\fC [static]\fR" -Internal clean up retquired for QColor. This function is called from the QApplication destructor. +Internal clean up required for QColor. This function is called from the QApplication destructor. .PP See also initialize(). .SH "QStringList QColor::colorNames ()\fC [static]\fR" @@ -408,7 +408,7 @@ Returns the G (green) component of the RGB value. .PP Example: themes/metal.cpp. .SH "void QColor::initialize ()\fC [static]\fR" -Internal initialization retquired for QColor. This function is called from the QApplication constructor. +Internal initialization required for QColor. This function is called from the QApplication constructor. .PP See also cleanup(). .SH "bool QColor::isValid () const" diff --git a/doc/man/man3/qcopchannel.3qt b/doc/man/man3/qcopchannel.3qt index f621d319..2a3515c5 100644 --- a/doc/man/man3/qcopchannel.3qt +++ b/doc/man/man3/qcopchannel.3qt @@ -109,7 +109,7 @@ Example: .fi This example assumes that the \fImsg\fR is a DCOP-style function signature and the \fIdata\fR contains the function's arguments. (See send().) .PP -Using the DCOP convention is a recommendation, but not a retquirement. Whatever convention you use the sender and receiver \fImust\fR agree on the argument types. +Using the DCOP convention is a recommendation, but not a requirement. Whatever convention you use the sender and receiver \fImust\fR agree on the argument types. .PP See also send(). .SH "void QCopChannel::received ( const QCString & msg, const QByteArray & data )\fC [signal]\fR" @@ -134,7 +134,7 @@ Example: .fi Here the channel is "System/Shell". The \fImsg\fR is an arbitrary string, but in the example we've used the DCOP convention of passing a function signature. Such a signature is formatted as functionname(types) where types is a list of zero or more comma-separated type names, with no whitespace, no consts and no pointer or reference marks, i.e. no "*" or "&". .PP -Using the DCOP convention is a recommendation, but not a retquirement. Whatever convention you use the sender and receiver \fImust\fR agree on the argument types. +Using the DCOP convention is a recommendation, but not a requirement. Whatever convention you use the sender and receiver \fImust\fR agree on the argument types. .PP See also receive(). .SH "bool QCopChannel::send ( const QCString & channel, const QCString & msg )\fC [static]\fR" diff --git a/doc/man/man3/qdatastream.3qt b/doc/man/man3/qdatastream.3qt index 9e895033..8b8b7edd 100644 --- a/doc/man/man3/qdatastream.3qt +++ b/doc/man/man3/qdatastream.3qt @@ -288,7 +288,7 @@ Then read it in with: .br .fi .PP -You can select which byte order to use when serializing data. The default setting is big endian (MSB first). Changing it to little endian breaks the portability (unless the reader also changes to little endian). We recommend keeping this setting unless you have special retquirements. +You can select which byte order to use when serializing data. The default setting is big endian (MSB first). Changing it to little endian breaks the portability (unless the reader also changes to little endian). We recommend keeping this setting unless you have special requirements. .SH "Reading and writing raw binary data" You may wish to read/write your own raw binary data to/from the data stream directly. Data may be read from the stream into a preallocated char* using readRawBytes(). Similarly data can be written to the stream using writeRawBytes(). Notice that any encoding/decoding of the data must be done by you. .PP @@ -488,7 +488,7 @@ Sets the serialization byte order to \fIbo\fR. .PP The \fIbo\fR parameter can be QDataStream::BigEndian or QDataStream::LittleEndian. .PP -The default setting is big endian. We recommend leaving this setting unless you have special retquirements. +The default setting is big endian. We recommend leaving this setting unless you have special requirements. .PP See also byteOrder(). .SH "void QDataStream::setDevice ( QIODevice * d )" diff --git a/doc/man/man3/qdialog.3qt b/doc/man/man3/qdialog.3qt index 7d23207f..adaaa29d 100644 --- a/doc/man/man3/qdialog.3qt +++ b/doc/man/man3/qdialog.3qt @@ -116,7 +116,7 @@ If the user presses the Esc key in a dialog, QDialog::reject() will be called. T .SH "Extensibility" Extensibility is the ability to show the dialog in two ways: a partial dialog that shows the most commonly used options, and a full dialog that shows all the options. Typically an extensible dialog will initially appear as a partial dialog, but with a" More" toggle button. If the user presses the "More" button down, the full dialog will appear. The extension widget will be resized to its sizeHint(). If orientation is Horizontal the extension widget's height() will be expanded to the height() of the dialog. If the orientation is Vertical the extension widget's width() will be expanded to the width() of the dialog. Extensibility is controlled with setExtension(), setOrientation() and showExtension(). .SH "Return value (modal dialogs)" -Modal dialogs are often used in situations where a return value is retquired, e.g. to indicate whether the user pressed "OK" or" Cancel". A dialog can be closed by calling the accept() or the reject() slots, and exec() will return Accepted or Rejected as appropriate. The exec() call returns the result of the dialog. The result is also available from result() if the dialog has not been destroyed. If the WDestructiveClose flag is set, the dialog is deleted after exec() returns. +Modal dialogs are often used in situations where a return value is required, e.g. to indicate whether the user pressed "OK" or" Cancel". A dialog can be closed by calling the accept() or the reject() slots, and exec() will return Accepted or Rejected as appropriate. The exec() call returns the result of the dialog. The result is also available from result() if the dialog has not been destroyed. If the WDestructiveClose flag is set, the dialog is deleted after exec() returns. .SH "Examples" A modal dialog. .PP diff --git a/doc/man/man3/qdockwindow.3qt b/doc/man/man3/qdockwindow.3qt index 8af28b6e..013f260a 100644 --- a/doc/man/man3/qdockwindow.3qt +++ b/doc/man/man3/qdockwindow.3qt @@ -390,7 +390,7 @@ Set this property's value with setMovingEnabled() and get this property's value .SH "bool newLine" This property holds whether the dock window prefers to start a new line in the dock area. .PP -The default is FALSE, i.e. the dock window doesn't retquire a new line in the dock area. +The default is FALSE, i.e. the dock window doesn't require a new line in the dock area. .PP Set this property's value with setNewLine() and get this property's value with newLine(). .SH "int offset" diff --git a/doc/man/man3/qdomdocument.3qt b/doc/man/man3/qdomdocument.3qt index d70f67b4..5651e040 100644 --- a/doc/man/man3/qdomdocument.3qt +++ b/doc/man/man3/qdomdocument.3qt @@ -345,7 +345,7 @@ Assigns \fIx\fR to this DOM document. .PP The data of the copy is shared (shallow copy): modifying one node will also change the other. If you want to make a deep copy, use cloneNode(). .SH "bool QDomDocument::setContent ( const QByteArray & buffer, bool namespaceProcessing, QString * errorMsg = 0, int * errorLine = 0, int * errorColumn = 0 )" -This function parses the XML document from the byte array \fIbuffer\fR and sets it as the content of the document. It tries to detect the encoding of the document as retquired by the XML specification. +This function parses the XML document from the byte array \fIbuffer\fR and sets it as the content of the document. It tries to detect the encoding of the document as required by the XML specification. .PP If \fInamespaceProcessing\fR is TRUE, the parser recognizes namespaces in the XML file and sets the prefix name, local name and namespace URI to appropriate values. If \fInamespaceProcessing\fR is FALSE, the parser does no namespace processing when it reads the XML file. .PP diff --git a/doc/man/man3/qdomnodelist.3qt b/doc/man/man3/qdomnodelist.3qt index e65dabc2..bb787935 100644 --- a/doc/man/man3/qdomnodelist.3qt +++ b/doc/man/man3/qdomnodelist.3qt @@ -46,7 +46,7 @@ All the functions in this class are reentrant when Qt is built with thread suppo .SH DESCRIPTION The QDomNodeList class is a list of QDomNode objects. .PP -Lists can be obtained by QDomDocument::elementsByTagName() and QDomNode::childNodes(). The Document Object Model (DOM) retquires these lists to be "live": whenever you change the underlying document, the contents of the list will get updated. +Lists can be obtained by QDomDocument::elementsByTagName() and QDomNode::childNodes(). The Document Object Model (DOM) requires these lists to be "live": whenever you change the underlying document, the contents of the list will get updated. .PP You can get a particular node from the list with item(). The number of items in the list is returned by count() (and by length()). .PP diff --git a/doc/man/man3/qfiledialog.3qt b/doc/man/man3/qfiledialog.3qt index 34f0b1cb..f4683ed2 100644 --- a/doc/man/man3/qfiledialog.3qt +++ b/doc/man/man3/qfiledialog.3qt @@ -479,7 +479,7 @@ See also addToolButton(), addLeftWidget(), and addRightWidget(). .SH "const QDir * QFileDialog::dir () const" Returns the current directory shown in the file dialog. .PP -The ownership of the QDir pointer is transferred to the caller, so it must be deleted by the caller when no longer retquired. +The ownership of the QDir pointer is transferred to the caller, so it must be deleted by the caller when no longer required. .PP See also setDir(). .SH "void QFileDialog::dirEntered ( const QString & )\fC [signal]\fR" diff --git a/doc/man/man3/qfont.3qt b/doc/man/man3/qfont.3qt index d3c413ff..ce1bfac7 100644 --- a/doc/man/man3/qfont.3qt +++ b/doc/man/man3/qfont.3qt @@ -679,7 +679,7 @@ See also pointSize(), setPointSizeFloat(), pixelSize(), QFontInfo::pointSize(), .SH "void QFont::qwsRenderToDisk ( bool all = TRUE )" Saves the glyphs in the font that have previously been accessed as a QPF file. If \fIall\fR is TRUE (the default), then before saving, all glyphs are marked as used. .PP -If the font is large and you are sure that only a subset of characters will ever be retquired on the target device, passing FALSE for the \fIall\fR parameter can save a significant amount of disk space. +If the font is large and you are sure that only a subset of characters will ever be required on the target device, passing FALSE for the \fIall\fR parameter can save a significant amount of disk space. .PP Note that this function is only applicable on Qt/Embedded. .SH "bool QFont::rawMode () const" diff --git a/doc/man/man3/qglcontext.3qt b/doc/man/man3/qglcontext.3qt index 13ff2fbc..0207b2f1 100644 --- a/doc/man/man3/qglcontext.3qt +++ b/doc/man/man3/qglcontext.3qt @@ -131,7 +131,7 @@ On Windows, it calls the virtual function choosePixelFormat(), which finds a mat .SH "void * QGLContext::chooseMacVisual ( GDHandle device )\fC [virtual protected]\fR" \fBMac only\fR: This virtual function tries to find a visual that matches the format using the given \fIdevice\fR handle, reducing the demands if the original request cannot be met. .PP -The algorithm for reducing the demands of the format is quite simple-minded, so override this method in your subclass if your application has specific retquirements on visual selection. +The algorithm for reducing the demands of the format is quite simple-minded, so override this method in your subclass if your application has specific requirements on visual selection. .PP See also chooseContext(). .SH "int QGLContext::choosePixelFormat ( void * dummyPfd, HDC pdc )\fC [virtual protected]\fR" @@ -143,7 +143,7 @@ See also chooseContext(). .SH "void * QGLContext::chooseVisual ()\fC [virtual protected]\fR" \fBX11 only\fR: This virtual function tries to find a visual that matches the format, reducing the demands if the original request cannot be met. .PP -The algorithm for reducing the demands of the format is quite simple-minded, so override this method in your subclass if your application has spcific retquirements on visual selection. +The algorithm for reducing the demands of the format is quite simple-minded, so override this method in your subclass if your application has spcific requirements on visual selection. .PP See also chooseContext(). .SH "bool QGLContext::create ( const QGLContext * shareContext = 0 )\fC [virtual]\fR" diff --git a/doc/man/man3/qglformat.3qt b/doc/man/man3/qglformat.3qt index dd250082..34d43ebb 100644 --- a/doc/man/man3/qglformat.3qt +++ b/doc/man/man3/qglformat.3qt @@ -184,7 +184,7 @@ After the widget has been created, you can find out which of the requested featu .br if ( !w->format().hasOverlay() ) { .br - qFatal( "Cool hardware retquired" ); + qFatal( "Cool hardware required" ); .br } .br diff --git a/doc/man/man3/qglwidget.3qt b/doc/man/man3/qglwidget.3qt index 177fdc51..c818b08f 100644 --- a/doc/man/man3/qglwidget.3qt +++ b/doc/man/man3/qglwidget.3qt @@ -371,13 +371,13 @@ Depending on your hardware, you can explicitly select which color buffer to grab .SH "void QGLWidget::initializeGL ()\fC [virtual protected]\fR" This virtual function is called once before the first call to paintGL() or resizeGL(), and then once whenever the widget has been assigned a new QGLContext. Reimplement it in a subclass. .PP -This function should set up any retquired OpenGL context rendering flags, defining display lists, etc. +This function should set up any required OpenGL context rendering flags, defining display lists, etc. .PP There is no need to call makeCurrent() because this has already been done when this function is called. .SH "void QGLWidget::initializeOverlayGL ()\fC [virtual protected]\fR" This virtual function is used in the same manner as initializeGL() except that it operates on the widget's overlay context instead of the widget's main context. This means that initializeOverlayGL() is called once before the first call to paintOverlayGL() or resizeOverlayGL(). Reimplement it in a subclass. .PP -This function should set up any retquired OpenGL context rendering flags, defining display lists, etc. for the overlay context. +This function should set up any required OpenGL context rendering flags, defining display lists, etc. for the overlay context. .PP There is no need to call makeOverlayCurrent() because this has already been done when this function is called. .SH "bool QGLWidget::isSharing () const" diff --git a/doc/man/man3/qguardedptr.3qt b/doc/man/man3/qguardedptr.3qt index 6e8d7350..7f13f897 100644 --- a/doc/man/man3/qguardedptr.3qt +++ b/doc/man/man3/qguardedptr.3qt @@ -85,7 +85,7 @@ The functions and operators available with a QGuardedPtr are the same as those a .PP For creating guarded pointers, you can construct or assign to them from an X* or from another guarded pointer of the same type. You can compare them with each other using operator==() and operator!=(), or test for 0 with isNull(). And you can dereference them using either the \fC*x\fR or the \fCx->member\fR notation. .PP -A guarded pointer will automatically cast to an X*, so you can freely mix guarded and unguarded pointers. This means that if you have a QGuardedPtr<QWidget>, you can pass it to a function that retquires a QWidget*. For this reason, it is of little value to declare functions to take a QGuardedPtr as a parameter; just use normal pointers. Use a QGuardedPtr when you are storing a pointer over time. +A guarded pointer will automatically cast to an X*, so you can freely mix guarded and unguarded pointers. This means that if you have a QGuardedPtr<QWidget>, you can pass it to a function that requires a QWidget*. For this reason, it is of little value to declare functions to take a QGuardedPtr as a parameter; just use normal pointers. Use a QGuardedPtr when you are storing a pointer over time. .PP Note again that class \fIX\fR must inherit QObject, or a compilation or link error will result. .PP @@ -104,7 +104,7 @@ Destroys the guarded pointer. Just like a normal pointer, destroying a guarded p .SH "bool QGuardedPtr::isNull () const" Returns \fCTRUE\fR if the referenced object has been destroyed or if there is no referenced object; otherwise returns FALSE. .SH "QGuardedPtr::operator T * () const" -Cast operator; implements pointer semantics. Because of this function you can pass a QGuardedPtr<X> to a function where an X* is retquired. +Cast operator; implements pointer semantics. Because of this function you can pass a QGuardedPtr<X> to a function where an X* is required. .SH "bool QGuardedPtr::operator!= ( const QGuardedPtr<T> & p ) const" Inequality operator; implements pointer semantics, the negation of operator==(). Returns TRUE if \fIp\fR and this guarded pointer are not pointing to the same object; otherwise returns FALSE. .SH "T & QGuardedPtr::operator* () const" diff --git a/doc/man/man3/qhttp.3qt b/doc/man/man3/qhttp.3qt index dee48b68..13482370 100644 --- a/doc/man/man3/qhttp.3qt +++ b/doc/man/man3/qhttp.3qt @@ -342,7 +342,7 @@ See also hasPendingRequests() and abort(). .SH "int QHttp::closeConnection ()" Closes the connection; this is useful if you have a keep-alive connection and want to close it. .PP -For the requests issued with get(), post() and head(), QHttp sets the connection to be keep-alive. You can also do this using the header you pass to the request() function. QHttp only closes the connection to the HTTP server if the response header retquires it to do so. +For the requests issued with get(), post() and head(), QHttp sets the connection to be keep-alive. You can also do this using the header you pass to the request() function. QHttp only closes the connection to the HTTP server if the response header requires it to do so. .PP The function does not block and returns immediately. The request is scheduled, and its execution is performed asynchronously. The function returns a unique identifier which is passed by requestStarted() and requestFinished(). .PP diff --git a/doc/man/man3/qiconset.3qt b/doc/man/man3/qiconset.3qt index cf040303..70f9d92c 100644 --- a/doc/man/man3/qiconset.3qt +++ b/doc/man/man3/qiconset.3qt @@ -88,7 +88,7 @@ The QIconSet class provides a set of icons with different styles and sizes. .PP A QIconSet can generate smaller, larger, active, and disabled pixmaps from the set of icons it is given. Such pixmaps are used by QToolButton, QHeader, QPopupMenu, etc. to show an icon representing a particular action. .PP -The simplest use of QIconSet is to create one from a QPixmap and then use it, allowing Qt to work out all the retquired icon styles and sizes. For example: +The simplest use of QIconSet is to create one from a QPixmap and then use it, allowing Qt to work out all the required icon styles and sizes. For example: .PP .nf .br @@ -165,7 +165,7 @@ This enum type describes the size at which a pixmap is intended to be used. The .TP \fCQIconSet::Large\fR - The pixmap is the larger of two. .PP -If a Small pixmap is not set by QIconSet::setPixmap(), the Large pixmap will be automatically scaled down to the size of a small pixmap to generate the Small pixmap when retquired. Similarly, a Small pixmap will be automatically scaled up to generate a Large pixmap. The preferred sizes for large/small generated icons can be set using setIconSize(). +If a Small pixmap is not set by QIconSet::setPixmap(), the Large pixmap will be automatically scaled down to the size of a small pixmap to generate the Small pixmap when required. Similarly, a Small pixmap will be automatically scaled up to generate a Large pixmap. The preferred sizes for large/small generated icons can be set using setIconSize(). .PP See also setIconSize(), iconSize(), setPixmap(), pixmap(), and QMainWindow::usesBigPixmaps. .SH "QIconSet::State" diff --git a/doc/man/man3/qimage.3qt b/doc/man/man3/qimage.3qt index 2b26b1f6..27920b0d 100644 --- a/doc/man/man3/qimage.3qt +++ b/doc/man/man3/qimage.3qt @@ -390,7 +390,7 @@ This enum type is used to describe the endianness of the CPU and graphics hardwa .TP \fCQImage::LittleEndian\fR - PC/Alpha byte order. .SH "QImage::ScaleMode" -The functions scale() and smoothScale() use different modes for scaling the image. The purpose of these modes is to retain the ratio of the image if this is retquired. +The functions scale() and smoothScale() use different modes for scaling the image. The purpose of these modes is to retain the ratio of the image if this is required. .PP <center> .ce 1 diff --git a/doc/man/man3/qimagedecoder.3qt b/doc/man/man3/qimagedecoder.3qt index 3f9c811b..9b2e3282 100644 --- a/doc/man/man3/qimagedecoder.3qt +++ b/doc/man/man3/qimagedecoder.3qt @@ -53,9 +53,9 @@ A QImageDecoder is a machine that decodes images. It takes encoded image data vi .PP QImageFormatType and QImageFormat are the classes that you might need to implement support for additional image formats. .PP -Qt supports GIF reading if it is configured that way during installation (see qgif.h). If it is, we are retquired to state that" The Graphics Interchange Format(c) is the Copyright property of CompuServe Incorporated. GIF(sm) is a Service Mark property of CompuServe Incorporated." +Qt supports GIF reading if it is configured that way during installation (see qgif.h). If it is, we are required to state that" The Graphics Interchange Format(c) is the Copyright property of CompuServe Incorporated. GIF(sm) is a Service Mark property of CompuServe Incorporated." .PP -\fBWarning:\fR If you are in a country that recognizes software patents and in which Unisys holds a patent on LZW compression and/or decompression and you want to use GIF, Unisys may retquire you to license that technology. Such countries include Canada, Japan, the USA, France, Germany, Italy and the UK. +\fBWarning:\fR If you are in a country that recognizes software patents and in which Unisys holds a patent on LZW compression and/or decompression and you want to use GIF, Unisys may require you to license that technology. Such countries include Canada, Japan, the USA, France, Germany, Italy and the UK. .PP GIF support may be removed completely in a future version of Qt. We recommend using the MNG or PNG format. .PP diff --git a/doc/man/man3/qimageio.3qt b/doc/man/man3/qimageio.3qt index b448a6b5..746f934e 100644 --- a/doc/man/man3/qimageio.3qt +++ b/doc/man/man3/qimageio.3qt @@ -117,7 +117,7 @@ For image files that contain sequences of images, only the first is read. See QM .PP PBM, PGM, and PPM format \fIoutput\fR is always in the more condensed raw format. PPM and PGM files with more than 256 levels of intensity are scaled down when reading. .PP -\fBWarning:\fR If you are in a country which recognizes software patents and in which Unisys holds a patent on LZW compression and/or decompression and you want to use GIF, Unisys may retquire you to license the technology. Such countries include Canada, Japan, the USA, France, Germany, Italy and the UK. +\fBWarning:\fR If you are in a country which recognizes software patents and in which Unisys holds a patent on LZW compression and/or decompression and you want to use GIF, Unisys may require you to license the technology. Such countries include Canada, Japan, the USA, France, Germany, Italy and the UK. .PP GIF support may be removed completely in a future version of Qt. We recommend using the PNG format. .PP @@ -289,7 +289,7 @@ Sets the image to \fIimage\fR. .PP See also image(). .SH "void QImageIO::setParameters ( const char * parameters )" -Sets the image's parameter string to \fIparameters\fR. This is for image handlers that retquire special parameters. +Sets the image's parameter string to \fIparameters\fR. This is for image handlers that require special parameters. .PP Although the current image formats supported by Qt ignore the parameters string, it may be used in future extensions or by contributions (for example, JPEG). .PP diff --git a/doc/man/man3/qlibrary.3qt b/doc/man/man3/qlibrary.3qt index 48431dc6..a93e6e71 100644 --- a/doc/man/man3/qlibrary.3qt +++ b/doc/man/man3/qlibrary.3qt @@ -169,7 +169,7 @@ Returns the address of the exported symbol \fIsymb\fR. The library is loaded if .br .fi .PP -The symbol must be exported as a C-function from the library. This retquires the \fCextern "C"\fR notation if the library is compiled with a C++ compiler. On Windows you also have to explicitly export the function from the DLL using the \fC__declspec(dllexport)\fR compiler directive. +The symbol must be exported as a C-function from the library. This requires the \fCextern "C"\fR notation if the library is compiled with a C++ compiler. On Windows you also have to explicitly export the function from the DLL using the \fC__declspec(dllexport)\fR compiler directive. .PP .nf .br diff --git a/doc/man/man3/qlineedit.3qt b/doc/man/man3/qlineedit.3qt index f3a84b8f..413a5382 100644 --- a/doc/man/man3/qlineedit.3qt +++ b/doc/man/man3/qlineedit.3qt @@ -666,7 +666,7 @@ Unset the mask and return to normal QLineEdit operation by passing an empty stri .PP The mask format understands these mask characters: <center>.nf .TS -l - l. Character Meaning ASCII alphabetic character retquired. A-Z, a-z. ASCII alphabetic character permitted but not retquired. ASCII alphanumeric character retquired. A-Z, a-z, 0-9. ASCII alphanumeric character permitted but not retquired. Any character retquired. x Any character permitted but not retquired. ASCII digit retquired. 0-9. ASCII digit permitted but not retquired. ASCII digit retquired. 1-9. ASCII digit permitted but not retquired (1-9). ASCII digit or plus/minus sign permitted but not retquired. All following alphabetic characters are uppercased. All following alphabetic characters are lowercased. Switch off case conversion. Use +l - l. Character Meaning ASCII alphabetic character required. A-Z, a-z. ASCII alphabetic character permitted but not required. ASCII alphanumeric character required. A-Z, a-z, 0-9. ASCII alphanumeric character permitted but not required. Any character required. x Any character permitted but not required. ASCII digit required. 0-9. ASCII digit permitted but not required. ASCII digit required. 1-9. ASCII digit permitted but not required (1-9). ASCII digit or plus/minus sign permitted but not required. All following alphabetic characters are uppercased. All following alphabetic characters are lowercased. Switch off case conversion. Use .TE .fi </center> diff --git a/doc/man/man3/qlistbox.3qt b/doc/man/man3/qlistbox.3qt index 7608d627..b44858d3 100644 --- a/doc/man/man3/qlistbox.3qt +++ b/doc/man/man3/qlistbox.3qt @@ -423,7 +423,7 @@ There are a variety of selection modes described in the QListBox::SelectionMode .PP Because QListBox offers multiple selection it must display keyboard focus and selection state separately. Therefore there are functions both to set the selection state of an item, i.e. setSelected(), and to set which item displays keyboard focus, i.e. setCurrentItem(). .PP -The list box normally arranges its items in a single column and adds a vertical scroll bar if retquired. It is possible to have a different fixed number of columns (setColumnMode()), or as many columns as will fit in the list box's assigned screen space (setColumnMode(FitToWidth)), or to have a fixed number of rows (setRowMode()) or as many rows as will fit in the list box's assigned screen space (setRowMode(FitToHeight)). In all these cases QListBox will add scroll bars, as appropriate, in at least one direction. +The list box normally arranges its items in a single column and adds a vertical scroll bar if required. It is possible to have a different fixed number of columns (setColumnMode()), or as many columns as will fit in the list box's assigned screen space (setColumnMode(FitToWidth)), or to have a fixed number of rows (setRowMode()) or as many rows as will fit in the list box's assigned screen space (setRowMode(FitToHeight)). In all these cases QListBox will add scroll bars, as appropriate, in at least one direction. .PP If multiple rows are used, each row can be as high as necessary (the normal setting), or you can request that all items will have the same height by calling setVariableHeight(FALSE). The same applies to a column's width, see setVariableWidth(). .PP @@ -467,7 +467,7 @@ This enum type is used to specify how QListBox lays out its rows and columns. .TP \fCQListBox::FitToHeight\fR - There are as many rows as will fit on-screen. .TP -\fCQListBox::Variable\fR - There are as many rows as are retquired by the column mode. (Or as many columns as retquired by the row mode.) +\fCQListBox::Variable\fR - There are as many rows as are required by the column mode. (Or as many columns as required by the row mode.) .PP Example: When you call setRowMode( FitToHeight ), columnMode() automatically becomes Variable to accommodate the row mode you've set. .SH "QListBox::SelectionMode" diff --git a/doc/man/man3/qlistview.3qt b/doc/man/man3/qlistview.3qt index 5de30c75..f9975c5b 100644 --- a/doc/man/man3/qlistview.3qt +++ b/doc/man/man3/qlistview.3qt @@ -659,7 +659,7 @@ If the user presses the mouse on an item and starts moving the mouse, and the it .PP By default this function returns 0. You should reimplement it and create a QDragObject depending on the selected items. .SH "void QListView::drawContentsOffset ( QPainter * p, int ox, int oy, int cx, int cy, int cw, int ch )\fC [virtual protected]\fR" -Calls QListViewItem::paintCell() and QListViewItem::paintBranches() as necessary for all list view items that retquire repainting in the \fIcw\fR pixels wide and \fIch\fR pixels high bounding rectangle starting at position \fIcx\fR, \fIcy\fR with offset \fIox\fR, \fIoy\fR. Uses the painter \fIp\fR. +Calls QListViewItem::paintCell() and QListViewItem::paintBranches() as necessary for all list view items that require repainting in the \fIcw\fR pixels wide and \fIch\fR pixels high bounding rectangle starting at position \fIcx\fR, \fIcy\fR with offset \fIox\fR, \fIoy\fR. Uses the painter \fIp\fR. .PP Reimplemented from QScrollView. .SH "void QListView::dropped ( QDropEvent * e )\fC [signal]\fR" @@ -667,7 +667,7 @@ This signal is emitted, when a drop event occurred on the viewport (not onto an .PP \fIe\fR provides all the information about the drop. .SH "void QListView::ensureItemVisible ( const QListViewItem * i )" -Ensures that item \fIi\fR is visible, scrolling the list view vertically if necessary and opening (expanding) any parent items if this is retquired to show the item. +Ensures that item \fIi\fR is visible, scrolling the list view vertically if necessary and opening (expanding) any parent items if this is required to show the item. .PP See also itemRect() and QScrollView::ensureVisible(). .SH "bool QListView::eventFilter ( QObject * o, QEvent * e )\fC [virtual]\fR" diff --git a/doc/man/man3/qlistviewitem.3qt b/doc/man/man3/qlistviewitem.3qt index 56b91109..976b2a7e 100644 --- a/doc/man/man3/qlistviewitem.3qt +++ b/doc/man/man3/qlistviewitem.3qt @@ -688,7 +688,7 @@ Functions which can affect the total height are, setHeight() which is used to se .PP See also height(). .SH "int QListViewItem::width ( const QFontMetrics & fm, const QListView * lv, int c ) const\fC [virtual]\fR" -Returns the number of pixels of width retquired to draw column \fIc\fR of list view \fIlv\fR, using the metrics \fIfm\fR without cropping. The list view containing this item may use this information depending on the QListView::WidthMode settings for the column. +Returns the number of pixels of width required to draw column \fIc\fR of list view \fIlv\fR, using the metrics \fIfm\fR without cropping. The list view containing this item may use this information depending on the QListView::WidthMode settings for the column. .PP The default implementation returns the width of the bounding rectangle of the text of column \fIc\fR. .PP diff --git a/doc/man/man3/qmainwindow.3qt b/doc/man/man3/qmainwindow.3qt index 897f1670..711f04a7 100644 --- a/doc/man/man3/qmainwindow.3qt +++ b/doc/man/man3/qmainwindow.3qt @@ -374,7 +374,7 @@ QMainWindow provides a QToolTipGroup connected to the status bar. The function t .PP New dock windows and toolbars can be added to a QMainWindow using addDockWindow(). Dock windows can be moved using moveDockWindow() and removed with removeDockWindow(). QMainWindow allows default dock window (toolbar) docking in all its dock areas (Top, Left, Right, Bottom). You can use setDockEnabled() to enable and disable docking areas for dock windows. When adding or moving dock windows you can specify their 'edge' (dock area). The currently available edges are: Top, Left, Right, Bottom, Minimized (effectively a 'hidden' dock area) and TornOff (floating). See Qt::Dock for an explanation of these areas. Note that the *ToolBar functions are included for backward compatibility; all new code should use the *DockWindow functions. QToolbar is a subclass of QDockWindow so all functions that work with dock windows work on toolbars in the same way. .PP -If the user clicks the close button, then the dock window is hidden. A dock window can be hidden or unhidden by the user by right clicking a dock area and clicking the name of the relevant dock window on the pop up dock window menu. This menu lists the names of every dock window; visible dock windows have a tick beside their names. The dock window menu is created automatically as retquired by createDockWindowMenu(). Since it may not always be appropriate for a dock window to appear on this menu the setAppropriate() function is used to inform the main window whether or not the dock window menu should include a particular dock window. Double clicking a dock window handle (usually on the left-hand side of the dock window) undocks (floats) the dock window. Double clicking a floating dock window's titlebar will dock the floating dock window. (See also QMainWindow::DockWindows.) +If the user clicks the close button, then the dock window is hidden. A dock window can be hidden or unhidden by the user by right clicking a dock area and clicking the name of the relevant dock window on the pop up dock window menu. This menu lists the names of every dock window; visible dock windows have a tick beside their names. The dock window menu is created automatically as required by createDockWindowMenu(). Since it may not always be appropriate for a dock window to appear on this menu the setAppropriate() function is used to inform the main window whether or not the dock window menu should include a particular dock window. Double clicking a dock window handle (usually on the left-hand side of the dock window) undocks (floats) the dock window. Double clicking a floating dock window's titlebar will dock the floating dock window. (See also QMainWindow::DockWindows.) .PP Some functions change the appearance of a QMainWindow globally: .TP diff --git a/doc/man/man3/qmap.3qt b/doc/man/man3/qmap.3qt index 8498190b..356e78d1 100644 --- a/doc/man/man3/qmap.3qt +++ b/doc/man/man3/qmap.3qt @@ -186,7 +186,7 @@ A default constructor, i.e. a constructor that does not take any arguments. .PP Note that C++ defaults to field-by-field assignment operators and copy constructors if no explicit version is supplied. In many cases, this is sufficient. .PP -The class used for the key retquires that the \fCoperator<\fR is implemented to define ordering of the keys. +The class used for the key requires that the \fCoperator<\fR is implemented to define ordering of the keys. .PP QMap's function naming is consistent with the other Qt classes (e.g., count(), isEmpty()). QMap also provides extra functions for compatibility with STL algorithms, such as size() and empty(). Programmers already familiar with the STL \fCmap\fR can use these the STL-like functions if preferred. .PP diff --git a/doc/man/man3/qmemarray.3qt b/doc/man/man3/qmemarray.3qt index 344e0a78..40f2c207 100644 --- a/doc/man/man3/qmemarray.3qt +++ b/doc/man/man3/qmemarray.3qt @@ -161,7 +161,7 @@ The QPtrVector collection class is also a kind of array. Like most collection cl .PP QMemArray uses explicit sharing with a reference count. If more than one array shares common data and one of the arrays is modified, all the arrays are modified. .PP -The benefit of sharing is that a program does not need to duplicate data when it is not retquired, which results in lower memory use and less copying of data. +The benefit of sharing is that a program does not need to duplicate data when it is not required, which results in lower memory use and less copying of data. .PP An alternative to QMemArray is QValueVector. The QValueVector class also provides an array of objects, but can deal with objects that have constructors (specifically a copy constructor and a default constructor). QValueVector provides an STL-compatible syntax and is implicitly shared. .PP @@ -281,7 +281,7 @@ You can make a shallow copy of the array with assign() (or operator=()) and a de .PP Search for values in the array with find() and contains(). For sorted arrays (see sort()) you can search using bsearch(). .PP -You can set the data directly using setRawData() and resetRawData(), although this retquires care. +You can set the data directly using setRawData() and resetRawData(), although this requires care. .PP See also Shared Classes and Non-GUI Classes. .SS "Member Type Documentation" diff --git a/doc/man/man3/qmessagebox.3qt b/doc/man/man3/qmessagebox.3qt index 4785bbc6..9124b7fe 100644 --- a/doc/man/man3/qmessagebox.3qt +++ b/doc/man/man3/qmessagebox.3qt @@ -724,11 +724,11 @@ Sets the message box text to be displayed. See the "text" property for details. .SH "void QMessageBox::setTextFormat ( TextFormat )" Sets the format of the text displayed by the message box. See the "textFormat" property for details. .SH "QPixmap QMessageBox::standardIcon ( Icon icon )\fC [static]\fR" -Returns the pixmap used for a standard icon. This allows the pixmaps to be used in more complex message boxes. \fIicon\fR specifies the retquired icon, e.g. QMessageBox::Question, QMessageBox::Information, QMessageBox::Warning or QMessageBox::Critical. +Returns the pixmap used for a standard icon. This allows the pixmaps to be used in more complex message boxes. \fIicon\fR specifies the required icon, e.g. QMessageBox::Question, QMessageBox::Information, QMessageBox::Warning or QMessageBox::Critical. .SH "QPixmap QMessageBox::standardIcon ( Icon icon, GUIStyle style )\fC [static]\fR" \fBThis function is obsolete.\fR It is provided to keep old source working. We strongly advise against using it in new code. .PP -Returns the pixmap used for a standard icon. This allows the pixmaps to be used in more complex message boxes. \fIicon\fR specifies the retquired icon, e.g. QMessageBox::Information, QMessageBox::Warning or QMessageBox::Critical. +Returns the pixmap used for a standard icon. This allows the pixmaps to be used in more complex message boxes. \fIicon\fR specifies the required icon, e.g. QMessageBox::Information, QMessageBox::Warning or QMessageBox::Critical. .PP \fIstyle\fR is unused. .SH "QString QMessageBox::text () const" diff --git a/doc/man/man3/qmetaobject.3qt b/doc/man/man3/qmetaobject.3qt index e7c8844b..e651283a 100644 --- a/doc/man/man3/qmetaobject.3qt +++ b/doc/man/man3/qmetaobject.3qt @@ -64,7 +64,7 @@ The QMetaObject class contains meta information about Qt objects. .PP The Meta Object System in Qt is responsible for the signals and slots inter-object communication mechanism, runtime type information and the property system. All meta information in Qt is kept in a single instance of QMetaObject per class. .PP -This class is not normally retquired for application programming. But if you write meta applications, such as scripting engines or GUI builders, you might find these functions useful: +This class is not normally required for application programming. But if you write meta applications, such as scripting engines or GUI builders, you might find these functions useful: .TP className() to get the name of a class. .TP diff --git a/doc/man/man3/qmotifdialog.3qt b/doc/man/man3/qmotifdialog.3qt index 8f5baa5a..96539cf3 100644 --- a/doc/man/man3/qmotifdialog.3qt +++ b/doc/man/man3/qmotifdialog.3qt @@ -58,7 +58,7 @@ The QMotifDialog class provides the QDialog API for Motif-based dialogs. .PP QMotifDialog provides two separate modes of operation. The application programmer can use QMotifDialog with an existing Motif-based dialog and a QWidget parent, or the application programmer can use QMotifDialog with a custom Qt-based dialog and a Motif-based parent. Modality continues to work as expected. .PP -Motif-based dialogs must have a \fCShell\fR widget parent with a single child, due to retquirements of the Motif toolkit. The \fCShell\fR widget, which is a special subclass of \fCXmDialogShell\fR, is created during construction. It can be accessed using the shell() member function. +Motif-based dialogs must have a \fCShell\fR widget parent with a single child, due to requirements of the Motif toolkit. The \fCShell\fR widget, which is a special subclass of \fCXmDialogShell\fR, is created during construction. It can be accessed using the shell() member function. .PP The single child of the \fCShell\fR can be accessed using the dialog() member function \fIafter\fR it has been created. .PP diff --git a/doc/man/man3/qmovie.3qt b/doc/man/man3/qmovie.3qt index 1d35da9c..2d42419d 100644 --- a/doc/man/man3/qmovie.3qt +++ b/doc/man/man3/qmovie.3qt @@ -134,9 +134,9 @@ The set of data formats supported by QMovie is determined by the decoder factori .PP The supported formats are MNG (if Qt is configured with MNG support enabled) and GIF (if Qt is configured with GIF support enabled, see qgif.h). .PP -If Qt is configured to support GIF reading, we are retquired to state that "The Graphics Interchange Format(c) is the Copyright property of CompuServe Incorporated. GIF(sm) is a Service Mark property of CompuServe Incorporated. +If Qt is configured to support GIF reading, we are required to state that "The Graphics Interchange Format(c) is the Copyright property of CompuServe Incorporated. GIF(sm) is a Service Mark property of CompuServe Incorporated. .PP -\fBWarning:\fR If you are in a country that recognizes software patents and in which Unisys holds a patent on LZW compression and/or decompression and you want to use GIF, Unisys may retquire you to license that technology. Such countries include Canada, Japan, the USA, France, Germany, Italy and the UK. +\fBWarning:\fR If you are in a country that recognizes software patents and in which Unisys holds a patent on LZW compression and/or decompression and you want to use GIF, Unisys may require you to license that technology. Such countries include Canada, Japan, the USA, France, Germany, Italy and the UK. .PP GIF support may be removed completely in a future version of Qt. We recommend using the MNG or PNG format. .PP diff --git a/doc/man/man3/qnpinstance.3qt b/doc/man/man3/qnpinstance.3qt index 6721e938..3b77dfe8 100644 --- a/doc/man/man3/qnpinstance.3qt +++ b/doc/man/man3/qnpinstance.3qt @@ -109,7 +109,7 @@ The QNPInstance class provides a QObject that is a web browser plugin. .PP Deriving from QNPInstance creates an object that represents a single \fC<EMBED>\fR tag in an HTML document. .PP -The QNPInstance is responsible for creating an appropriate QNPWidget window if retquired (not all plugins have windows), and for interacting with the input/output facilities intrinsic to plugins. +The QNPInstance is responsible for creating an appropriate QNPWidget window if required (not all plugins have windows), and for interacting with the input/output facilities intrinsic to plugins. .PP Note that there is \fIabsolutely no guarantee\fR regarding the order in which functions are called. Sometimes the browser will call newWindow() first, at other times, newStreamCreated() will be called first (assuming the \fC<EMBED>\fR tag has a SRC parameter). .PP @@ -180,7 +180,7 @@ Returns the value of the \fIi\fR-th argument. .SH "void * QNPInstance::getJavaPeer () const" Returns the Java object associated with the plugin instance, an object of the plugin's Java class, or 0 if the plug-in does not have a Java class, Java is disabled, or an error occurred. .PP -The return value is actually a \fCjref\fR we use \fCvoid*\fR so as to avoid burdening plugins which do not retquire Java. +The return value is actually a \fCjref\fR we use \fCvoid*\fR so as to avoid burdening plugins which do not require Java. .PP See also QNPlugin::getJavaClass() and QNPlugin::getJavaEnv(). .SH "void QNPInstance::getURL ( const char * url, const char * window = 0 )" @@ -198,13 +198,13 @@ This function is \fInot tested\fR. .PP Requests the creation of a new data stream \fIfrom\fR the plugin. The MIME type and window are passed in \fImimetype\fR and \fIwindow\fR. \fIas_file\fR holds the AsFileOnly flag. It is an interface to the NPN_NewStream function of the Netscape Plugin API. .SH "bool QNPInstance::newStreamCreated ( QNPStream *, StreamMode & smode )\fC [virtual]\fR" -This function is called when a new stream has been created. The instance should return TRUE if it accepts the processing of the stream. If the instance retquires the stream as a file, it should set \fIsmode\fR to AsFileOnly, in which case the data will be delivered some time later to the streamAsFile() function. Otherwise, the data will be delivered in chunks to the write() function, which must consume at least as much data as returned by the most recent call to writeReady(). +This function is called when a new stream has been created. The instance should return TRUE if it accepts the processing of the stream. If the instance requires the stream as a file, it should set \fIsmode\fR to AsFileOnly, in which case the data will be delivered some time later to the streamAsFile() function. Otherwise, the data will be delivered in chunks to the write() function, which must consume at least as much data as returned by the most recent call to writeReady(). .PP Note that the AsFileOnly method is not supported by Netscape 2.0 and MSIE 3.0. .PP The default implementation accepts any stream. .SH "QNPWidget * QNPInstance::newWindow ()\fC [virtual]\fR" -Called at most once, at some time after the QNPInstance is created. If the plugin retquires a window, this function should return a derived class of QNPWidget that provides the retquired interface. +Called at most once, at some time after the QNPInstance is created. If the plugin requires a window, this function should return a derived class of QNPWidget that provides the required interface. .PP Example: grapher/grapher.cpp. .SH "void QNPInstance::notifyURL ( const char * url, Reason r, void * notifyData )\fC [virtual]\fR" diff --git a/doc/man/man3/qnplugin.3qt b/doc/man/man3/qnplugin.3qt index 7d2a7203..33a5feb1 100644 --- a/doc/man/man3/qnplugin.3qt +++ b/doc/man/man3/qnplugin.3qt @@ -80,13 +80,13 @@ Override this function to return a reference to the Java class that represents t .PP If you override this class, you must also override QNPlugin::unuseJavaClass(). .PP -The return value is actually a \fCjref\fR; we use \fCvoid*\fR so as to avoid burdening plugins which do not retquire Java. +The return value is actually a \fCjref\fR; we use \fCvoid*\fR so as to avoid burdening plugins which do not require Java. .PP See also getJavaEnv() and QNPInstance::getJavaPeer(). .SH "void * QNPlugin::getJavaEnv () const" Returns a pointer to the Java execution environment, or 0 if either Java is disabled or an error occurred. .PP -The return value is actually a \fCJRIEnv*\fR; we use \fCvoid*\fR so as to avoid burdening plugins which do not retquire Java. +The return value is actually a \fCJRIEnv*\fR; we use \fCvoid*\fR so as to avoid burdening plugins which do not require Java. .PP See also getJavaClass() and QNPInstance::getJavaPeer(). .SH "const char * QNPlugin::getMIMEDescription () const\fC [pure virtual]\fR" diff --git a/doc/man/man3/qnpwidget.3qt b/doc/man/man3/qnpwidget.3qt index 40ad33ba..ac17887a 100644 --- a/doc/man/man3/qnpwidget.3qt +++ b/doc/man/man3/qnpwidget.3qt @@ -91,7 +91,7 @@ The default implementation is an empty window. .SH "QNPWidget::QNPWidget ()" Creates a QNPWidget. .SH "QNPWidget::~QNPWidget ()" -Destroys the window. This will be called by the plugin binding code when the window is no longer retquired. The web browser will delete windows when they leave the page. The bindings will change the QWidget::winId() of the window when the window is resized, but this should not affect normal widget behavior. +Destroys the window. This will be called by the plugin binding code when the window is no longer required. The web browser will delete windows when they leave the page. The bindings will change the QWidget::winId() of the window when the window is resized, but this should not affect normal widget behavior. .SH "void QNPWidget::enterInstance ()\fC [virtual]\fR" Called when the mouse enters the plugin window. Does nothing by default. .PP diff --git a/doc/man/man3/qobject.3qt b/doc/man/man3/qobject.3qt index e1d36547..fe34d199 100644 --- a/doc/man/man3/qobject.3qt +++ b/doc/man/man3/qobject.3qt @@ -743,7 +743,7 @@ 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. .PP -The meta object information is retquired by the signal/slot connection mechanism and the property system. The functions isA() and inherits() also make use of the meta object. +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" Returns the name of this object. See the "name" property for details. .SH "const char * QObject::name ( const char * defaultName ) const" diff --git a/doc/man/man3/qpaintdevice.3qt b/doc/man/man3/qpaintdevice.3qt index 6001ae75..d8933e2e 100644 --- a/doc/man/man3/qpaintdevice.3qt +++ b/doc/man/man3/qpaintdevice.3qt @@ -189,7 +189,7 @@ Example (scroll widget contents 10 pixels to the right): .br .fi .PP -\fBWarning:\fR Qt retquires that a QApplication object exists before any paint devices can be created. Paint devices access window system resources, and these resources are not initialized before an application object is created. +\fBWarning:\fR Qt requires that a QApplication object exists before any paint devices can be created. Paint devices access window system resources, and these resources are not initialized before an application object is created. .PP See also Graphics Classes and Image Processing Classes. .SH MEMBER FUNCTION DOCUMENTATION diff --git a/doc/man/man3/qpainter.3qt b/doc/man/man3/qpainter.3qt index f44f185b..b94def7a 100644 --- a/doc/man/man3/qpainter.3qt +++ b/doc/man/man3/qpainter.3qt @@ -441,7 +441,7 @@ Inherited by QDirectPainter. .SH DESCRIPTION The QPainter class does low-level painting e.g. on widgets. .PP -The painter provides highly optimized functions to do most of the drawing GUI programs retquire. QPainter can draw everything from simple lines to complex shapes like pies and chords. It can also draw aligned text and pixmaps. Normally, it draws in a "natural" coordinate system, but it can also do view and world transformation. +The painter provides highly optimized functions to do most of the drawing GUI programs require. QPainter can draw everything from simple lines to complex shapes like pies and chords. It can also draw aligned text and pixmaps. Normally, it draws in a "natural" coordinate system, but it can also do view and world transformation. .PP The typical use of a painter is: .TP @@ -695,7 +695,7 @@ Example: .PP See also end(). .SH "QRect QPainter::boundingRect ( int x, int y, int w, int h, int flags, const QString &, int len = -1, QTextParag ** intern = 0 )" -Returns the bounding rectangle of the aligned text that would be printed with the corresponding drawText() function using the first \fIlen\fR characters of the string if \fIlen\fR is > -1, or the whole of the string if \fIlen\fR is -1. The drawing, and hence the bounding rectangle, is constrained to the rectangle that begins at point \fI(x, y)\fR with width \fIw\fR and hight \fIh\fR, or to the rectangle retquired to draw the text, whichever is the larger. +Returns the bounding rectangle of the aligned text that would be printed with the corresponding drawText() function using the first \fIlen\fR characters of the string if \fIlen\fR is > -1, or the whole of the string if \fIlen\fR is -1. The drawing, and hence the bounding rectangle, is constrained to the rectangle that begins at point \fI(x, y)\fR with width \fIw\fR and hight \fIh\fR, or to the rectangle required to draw the text, whichever is the larger. .PP The \fIflags\fR argument is the bitwise OR of the following flags: <center>.nf .TS @@ -714,7 +714,7 @@ See also Qt::TextFlags. .SH "QRect QPainter::boundingRect ( const QRect & r, int flags, const QString & str, int len = -1, QTextParag ** internal = 0 )" This is an overloaded member function, provided for convenience. It behaves essentially like the above function. .PP -Returns the bounding rectangle of the aligned text that would be printed with the corresponding drawText() function using the first \fIlen\fR characters from \fIstr\fR if \fIlen\fR is > -1, or the whole of \fIstr\fR if \fIlen\fR is -1. The drawing, and hence the bounding rectangle, is constrained to the rectangle \fIr\fR, or to the rectangle retquired to draw the text, whichever is the larger. +Returns the bounding rectangle of the aligned text that would be printed with the corresponding drawText() function using the first \fIlen\fR characters from \fIstr\fR if \fIlen\fR is > -1, or the whole of \fIstr\fR if \fIlen\fR is -1. The drawing, and hence the bounding rectangle, is constrained to the rectangle \fIr\fR, or to the rectangle required to draw the text, whichever is the larger. .PP The \fIinternal\fR parameter should not be used. .PP diff --git a/doc/man/man3/qpicture.3qt b/doc/man/man3/qpicture.3qt index ca74215f..2ae1a530 100644 --- a/doc/man/man3/qpicture.3qt +++ b/doc/man/man3/qpicture.3qt @@ -174,7 +174,7 @@ Loads a picture from the file specified by \fIfileName\fR and returns TRUE if su .PP By default, the file will be interpreted as being in the native QPicture format. Specifying the \fIformat\fR string is optional and is only needed for importing picture data stored in a different format. .PP -Currently, the only external format supported is the W3C SVG format which retquires the Qt XML module. The corresponding \fIformat\fR string is "svg". +Currently, the only external format supported is the W3C SVG format which requires the Qt XML module. The corresponding \fIformat\fR string is "svg". .PP See also save(). .PP @@ -203,7 +203,7 @@ Saves a picture to the file specified by \fIfileName\fR and returns TRUE if succ .PP Specifying the file \fIformat\fR string is optional. It's not recommended unless you intend to export the picture data for use by a third party reader. By default the data will be saved in the native QPicture file format. .PP -Currently, the only external format supported is the W3C SVG format which retquires the Qt XML module. The corresponding \fIformat\fR string is "svg". +Currently, the only external format supported is the W3C SVG format which requires the Qt XML module. The corresponding \fIformat\fR string is "svg". .PP See also load(). .PP diff --git a/doc/man/man3/qpngimagepacker.3qt b/doc/man/man3/qpngimagepacker.3qt index 5744ab69..73aa3624 100644 --- a/doc/man/man3/qpngimagepacker.3qt +++ b/doc/man/man3/qpngimagepacker.3qt @@ -33,7 +33,7 @@ Images are added using packImage(). See also Graphics Classes and Image Processing Classes. .SH MEMBER FUNCTION DOCUMENTATION .SH "QPNGImagePacker::QPNGImagePacker ( QIODevice * iod, int storage_depth, int conversionflags )" -Creates an image packer that writes PNG data to IO device \fIiod\fR using a \fIstorage_depth\fR bit encoding (use 8 or 32, depending on the desired quality and compression retquirements). +Creates an image packer that writes PNG data to IO device \fIiod\fR using a \fIstorage_depth\fR bit encoding (use 8 or 32, depending on the desired quality and compression requirements). .PP If the image needs to be modified to fit in a lower-resolution result (e.g. converting from 32-bit to 8-bit), use the \fIconversionflags\fR to specify how you'd prefer this to happen. .PP diff --git a/doc/man/man3/qprinter.3qt b/doc/man/man3/qprinter.3qt index ead2b387..dfd2599f 100644 --- a/doc/man/man3/qprinter.3qt +++ b/doc/man/man3/qprinter.3qt @@ -486,7 +486,7 @@ Examples: .SH "int QPrinter::numCopies () const" Returns the number of copies to be printed. The default value is 1. .PP -This value will return the number of times the application is retquired to print in order to match the number specified in the printer setup dialog. This has been done since some printer drivers are not capable of buffering up the copies and the application in those cases have to make an explicit call to the print code for each copy. +This value will return the number of times the application is required to print in order to match the number specified in the printer setup dialog. This has been done since some printer drivers are not capable of buffering up the copies and the application in those cases have to make an explicit call to the print code for each copy. .PP See also setNumCopies(). .SH "Orientation QPrinter::orientation () const" diff --git a/doc/man/man3/qprocess.3qt b/doc/man/man3/qprocess.3qt index f9e85193..8624d697 100644 --- a/doc/man/man3/qprocess.3qt +++ b/doc/man/man3/qprocess.3qt @@ -223,7 +223,7 @@ Note that if you are expecting a lot of output from the process, you may hit pla .PP Please note that QProcess does not emulate a shell. This means that QProcess does not do any expansion of arguments: a '*' is passed as a '*' to the program and is \fInot\fR replaced by all the files, a '$HOME' is also passed literally and is \fInot\fR replaced by the environment variable HOME and the special characters for IO redirection ('>', '|', etc.) are also passed literally and do \fInot\fR have the special meaning as they have in a shell. .PP -Also note that QProcess does not emulate a terminal. This means that certain programs which need direct terminal control, do not work as expected with QProcess. Such programs include console email programs (like pine and mutt) but also programs which retquire the user to enter a password (like su and ssh). +Also note that QProcess does not emulate a terminal. This means that certain programs which need direct terminal control, do not work as expected with QProcess. Such programs include console email programs (like pine and mutt) but also programs which require the user to enter a password (like su and ssh). .SH "Notes for Windows users" Some Windows commands, for example, \fCdir\fR, are not provided by separate applications, but by the command interpreter. If you attempt to use QProcess to execute these commands directly it won't work. One possible solution is to execute the command interpreter itself (\fCcmd.exe\fR on some Windows systems), and ask the interpreter to execute the desired command. .PP @@ -240,7 +240,7 @@ This enum type defines the communication channels connected to the process. .TP \fCQProcess::Stderr\fR - Data can be read from the process's standard error. .TP -\fCQProcess::DupStderr\fR - Both the process's standard error output \fIand\fR its standard output are written to its standard output. (Like Unix's dup2().) This means that nothing is sent to the standard error output. This is especially useful if your application retquires that the output on standard output and on standard error must be read in the same order that they are produced. This is a flag, so to activate it you must pass \fCStdout|Stderr|DupStderr\fR, or \fCStdin|Stdout|Stderr|DupStderr\fR if you want to provide input, to the setCommunication() call. +\fCQProcess::DupStderr\fR - Both the process's standard error output \fIand\fR its standard output are written to its standard output. (Like Unix's dup2().) This means that nothing is sent to the standard error output. This is especially useful if your application requires that the output on standard output and on standard error must be read in the same order that they are produced. This is a flag, so to activate it you must pass \fCStdout|Stderr|DupStderr\fR, or \fCStdin|Stdout|Stderr|DupStderr\fR if you want to provide input, to the setCommunication() call. .PP See also setCommunication() and communication(). .SH MEMBER FUNCTION DOCUMENTATION @@ -317,7 +317,7 @@ This function also deletes any pending data that has not been written to standar .PP See also wroteToStdin(). .SH "int QProcess::communication () const" -Returns the communication retquired with the process, i.e. some combination of the Communication flags. +Returns the communication required with the process, i.e. some combination of the Communication flags. .PP See also setCommunication(). .SH "int QProcess::exitStatus () const" @@ -441,7 +441,7 @@ Note for Windows users. The standard Windows shells, e.g. \fCcommand.com\fR and .PP See also arguments() and addArgument(). .SH "void QProcess::setCommunication ( int commFlags )" -Sets \fIcommFlags\fR as the communication retquired with the process. +Sets \fIcommFlags\fR as the communication required with the process. .PP \fIcommFlags\fR is a bitwise OR of the flags defined by the Communication enum. .PP diff --git a/doc/man/man3/qprogressdialog.3qt b/doc/man/man3/qprogressdialog.3qt index e45029a0..d7ad2e62 100644 --- a/doc/man/man3/qprogressdialog.3qt +++ b/doc/man/man3/qprogressdialog.3qt @@ -335,7 +335,7 @@ See also totalSteps. .SH "void QProgressDialog::setTotalSteps ( int totalSteps )\fC [slot]\fR" Sets the total number of steps to \fItotalSteps\fR. See the "totalSteps" property for details. .SH "QSize QProgressDialog::sizeHint () const\fC [virtual]\fR" -Returns a size that fits the contents of the progress dialog. The progress dialog resizes itself as retquired, so you should not need to call this yourself. +Returns a size that fits the contents of the progress dialog. The progress dialog resizes itself as required, so you should not need to call this yourself. .SH "int QProgressDialog::totalSteps () const" Returns the total number of steps. See the "totalSteps" property for details. .SH "bool QProgressDialog::wasCanceled () const" diff --git a/doc/man/man3/qptrcollection.3qt b/doc/man/man3/qptrcollection.3qt index cf2f93e5..4ba1ebaf 100644 --- a/doc/man/man3/qptrcollection.3qt +++ b/doc/man/man3/qptrcollection.3qt @@ -58,7 +58,7 @@ The QPtrCollection class is an abstract base class for the Qt collection classes .PP A QPtrCollection only knows about the number of objects in the collection and the deletion strategy (see setAutoDelete()). .PP -A collection is implemented using the Item (generic collection item) type, which is a \fCvoid*\fR. The template classes that create the real collections cast the Item to the retquired type. +A collection is implemented using the Item (generic collection item) type, which is a \fCvoid*\fR. The template classes that create the real collections cast the Item to the required type. .PP See also Collection Classes and Non-GUI Classes. .SS "Member Type Documentation" diff --git a/doc/man/man3/qptrlist.3qt b/doc/man/man3/qptrlist.3qt index 24974a55..e2d747e0 100644 --- a/doc/man/man3/qptrlist.3qt +++ b/doc/man/man3/qptrlist.3qt @@ -357,7 +357,7 @@ This function returns \fIint\fR rather than \fIbool\fR so that reimplementations .TP < 0 (negative integer) if \fIitem1\fR < \fIitem2\fR .PP -inSort() retquires that compareItems() is implemented as described here. +inSort() requires that compareItems() is implemented as described here. .PP This function should not modify the list because some const functions call compareItems(). .PP diff --git a/doc/man/man3/qptrvector.3qt b/doc/man/man3/qptrvector.3qt index 8d771306..fc4ad3ad 100644 --- a/doc/man/man3/qptrvector.3qt +++ b/doc/man/man3/qptrvector.3qt @@ -184,7 +184,7 @@ This function returns \fIint\fR rather than \fIbool\fR so that reimplementations .TP < 0 (negative integer) if \fId1\fR < \fId2\fR .PP -The sort() and bsearch() functions retquire compareItems() to be implemented as described here. +The sort() and bsearch() functions require compareItems() to be implemented as described here. .PP This function should not modify the vector because some const functions call compareItems(). .SH "uint QPtrVector::contains ( const type * d ) const" diff --git a/doc/man/man3/qregexp.3qt b/doc/man/man3/qregexp.3qt index 73f961bd..54013861 100644 --- a/doc/man/man3/qregexp.3qt +++ b/doc/man/man3/qregexp.3qt @@ -151,7 +151,7 @@ Regexps are built up from expressions, quantifiers, and assertions. The simplest .PP Note that in general regexps cannot be used to check for balanced brackets or tags. For example if you want to match an opening html \fC<b>\fR and its closing \fC</b>\fR you can only use a regexp if you know that these tags are not nested; the html fragment, \fC<b>bold <b>bolder</b></b>\fR will not match as expected. If you know the maximum level of nesting it is possible to create a regexp that will match correctly, but for an unknown level of nesting, regexps will fail. .PP -We'll start by writing a regexp to match integers in the range 0 to 99. We will retquire at least one digit so we will start with \fB[0-9]{1,1}\fR which means match a digit exactly once. This regexp alone will match integers in the range 0 to 9. To match one or two digits we can increase the maximum number of occurrences so the regexp becomes \fB[0-9]{1,2}\fR meaning match a digit at least once and at most twice. However, this regexp as it stands will not match correctly. This regexp will match one or two digits \fIwithin\fR a string. To ensure that we match against the whole string we must use the anchor assertions. We need \fB^\fR (caret) which when it is the first character in the regexp means that the regexp must match from the beginning of the string. And we also need \fB$\fR (dollar) which when it is the last character in the regexp means that the regexp must match until the end of the string. So now our regexp is \fB^[0-9]{1,2}$\fR. Note that assertions, such as \fB^\fR and \fB$\fR, do not match any characters. +We'll start by writing a regexp to match integers in the range 0 to 99. We will require at least one digit so we will start with \fB[0-9]{1,1}\fR which means match a digit exactly once. This regexp alone will match integers in the range 0 to 9. To match one or two digits we can increase the maximum number of occurrences so the regexp becomes \fB[0-9]{1,2}\fR meaning match a digit at least once and at most twice. However, this regexp as it stands will not match correctly. This regexp will match one or two digits \fIwithin\fR a string. To ensure that we match against the whole string we must use the anchor assertions. We need \fB^\fR (caret) which when it is the first character in the regexp means that the regexp must match from the beginning of the string. And we also need \fB$\fR (dollar) which when it is the last character in the regexp means that the regexp must match until the end of the string. So now our regexp is \fB^[0-9]{1,2}$\fR. Note that assertions, such as \fB^\fR and \fB$\fR, do not match any characters. .PP If you've seen regexps elsewhere they may have looked different from the ones above. This is because some sets of characters and some quantifiers are so common that they have special symbols to represent them. \fB[0-9]\fR can be replaced with the symbol \fB\\d\fR. The quantifier to match exactly one occurrence, \fB{1,1}\fR, can be replaced with the expression itself. This means that \fBx{1,1}\fR is exactly the same as \fBx\fR alone. So our 0 to 99 matcher could be written \fB^\\d{1,2}$\fR. Another way of writing it would be \fB^\\d\\d{0,1}$\fR, i.e. from the start of the string match a digit followed by zero or one digits. In practice most people would write it \fB^\\d\\d?$\fR. The \fB?\fR is a shorthand for the quantifier \fB{0,1}\fR, i.e. a minimum of no occurrences a maximum of one occurrence. This is used to make an expression optional. The regexp \fB^\\d\\d?$\fR means "from the beginning of the string match one digit followed by zero or one digits and then the end of the string". .PP @@ -285,7 +285,7 @@ Most of the character class abbreviations supported by Perl are supported by QRe .PP In QRegExp, apart from within character classes, \fC^\fR always signifies the start of the string, so carets must always be escaped unless used for that purpose. In Perl the meaning of caret varies automagically depending on where it occurs so escaping it is rarely necessary. The same applies to \fC$\fR which in QRegExp always signifies the end of the string. .PP -QRegExp's quantifiers are the same as Perl's greedy quantifiers. Non-greedy matching cannot be applied to individual quantifiers, but can be applied to all the quantifiers in the pattern. For example, to match the Perl regexp \fBro+?m\fR retquires: +QRegExp's quantifiers are the same as Perl's greedy quantifiers. Non-greedy matching cannot be applied to individual quantifiers, but can be applied to all the quantifiers in the pattern. For example, to match the Perl regexp \fBro+?m\fR requires: .PP .nf .br diff --git a/doc/man/man3/qsettings.3qt b/doc/man/man3/qsettings.3qt index 571d5c4b..f9509cb2 100644 --- a/doc/man/man3/qsettings.3qt +++ b/doc/man/man3/qsettings.3qt @@ -578,7 +578,7 @@ Writes the boolean entry \fIvalue\fR into key \fIkey\fR. The \fIkey\fR is create .PP If an error occurs the settings are left unchanged and FALSE is returned; otherwise TRUE is returned. .PP -\fBWarning:\fR On certain platforms, keys are retquired to contain at least two components (e.g., "/foo/bar"). This limitation does not apply to Qt 4. +\fBWarning:\fR On certain platforms, keys are required to contain at least two components (e.g., "/foo/bar"). This limitation does not apply to Qt 4. .PP See also readListEntry(), readNumEntry(), readDoubleEntry(), readBoolEntry(), and removeEntry(). .PP diff --git a/doc/man/man3/qsocket.3qt b/doc/man/man3/qsocket.3qt index 65072178..05c70d0a 100644 --- a/doc/man/man3/qsocket.3qt +++ b/doc/man/man3/qsocket.3qt @@ -279,7 +279,7 @@ Attempts to make a connection to \fIhost\fR on the specified \fIport\fR and retu .PP Any connection or pending connection is closed immediately, and QSocket goes into the HostLookup state. When the lookup succeeds, it emits hostFound(), starts a TCP connection and goes into the Connecting state. Finally, when the connection succeeds, it emits connected() and goes into the Connected state. If there is an error at any point, it emits error(). .PP -\fIhost\fR may be an IP address in string form, or it may be a DNS name. QSocket will do a normal DNS lookup if retquired. Note that \fIport\fR is in native byte order, unlike some other libraries. +\fIhost\fR may be an IP address in string form, or it may be a DNS name. QSocket will do a normal DNS lookup if required. Note that \fIport\fR is in native byte order, unlike some other libraries. .PP See also state(). .PP diff --git a/doc/man/man3/qsound.3qt b/doc/man/man3/qsound.3qt index 295b1774..4f19488b 100644 --- a/doc/man/man3/qsound.3qt +++ b/doc/man/man3/qsound.3qt @@ -61,7 +61,7 @@ Inherits QObject. .SH DESCRIPTION The QSound class provides access to the platform audio facilities. .PP -Qt provides the most commonly retquired audio operation in GUI applications: asynchronously playing a sound file. This is most easily accomplished with a single call: +Qt provides the most commonly required audio operation in GUI applications: asynchronously playing a sound file. This is most easily accomplished with a single call: .PP .nf .br diff --git a/doc/man/man3/qsqlcursor.3qt b/doc/man/man3/qsqlcursor.3qt index 8b75415b..166665bc 100644 --- a/doc/man/man3/qsqlcursor.3qt +++ b/doc/man/man3/qsqlcursor.3qt @@ -204,7 +204,7 @@ For example: .PP In the above example, a cursor is created specifying a table or view name in the database. Then, select() is called, which can be optionally parameterised to filter and order the records retrieved. Each record in the cursor is retrieved using next(). When next() returns FALSE, there are no more records to process, and the loop terminates. .PP -For editing records (rows of data), a cursor contains a separate edit buffer which is independent of the fields used when browsing. The functions insert(), update() and del() operate on the edit buffer. This allows the cursor to be repositioned to other records while simultaneously maintaining a separate buffer for edits. You can get a pointer to the edit buffer using editBuffer(). The primeInsert(), primeUpdate() and primeDelete() functions also return a pointer to the edit buffer and prepare it for insert, update and delete respectively. Edit operations only affect a single row at a time. Note that update() and del() retquire that the table or view contain a primaryIndex() to ensure that edit operations affect a unique record within the database. +For editing records (rows of data), a cursor contains a separate edit buffer which is independent of the fields used when browsing. The functions insert(), update() and del() operate on the edit buffer. This allows the cursor to be repositioned to other records while simultaneously maintaining a separate buffer for edits. You can get a pointer to the edit buffer using editBuffer(). The primeInsert(), primeUpdate() and primeDelete() functions also return a pointer to the edit buffer and prepare it for insert, update and delete respectively. Edit operations only affect a single row at a time. Note that update() and del() require that the table or view contain a primaryIndex() to ensure that edit operations affect a unique record within the database. .PP For example: .PP diff --git a/doc/man/man3/qsqldatabase.3qt b/doc/man/man3/qsqldatabase.3qt index 5dd745e4..e5c33941 100644 --- a/doc/man/man3/qsqldatabase.3qt +++ b/doc/man/man3/qsqldatabase.3qt @@ -516,7 +516,7 @@ options .TP tty .TP -retquiressl +requiressl .TP service DB2 OCI TDS .TP @@ -551,7 +551,7 @@ Example of usage: .br // PostgreSQL connection .br - db->setConnectOptions( "retquiressl=1" ); // enable PostgreSQL SSL connections + db->setConnectOptions( "requiressl=1" ); // enable PostgreSQL SSL connections .br if ( !db->open() ) { .br @@ -606,7 +606,7 @@ For the QODBC3 driver it can either be a DSN, a DSN filename (the file must have ... .br .fi -("FIL" is the retquired spelling in Microsoft's API.) +("FIL" is the required spelling in Microsoft's API.) .PP There is no default value. .PP diff --git a/doc/man/man3/qsqldriverplugin.3qt b/doc/man/man3/qsqldriverplugin.3qt index 545acfcd..b8211b17 100644 --- a/doc/man/man3/qsqldriverplugin.3qt +++ b/doc/man/man3/qsqldriverplugin.3qt @@ -42,7 +42,7 @@ Destroys the SQL driver plugin. .PP You never have to call this explicitly. Qt destroys a plugin automatically when it is no longer used. .SH "QSqlDriver * QSqlDriverPlugin::create ( const QString & key )\fC [pure virtual]\fR" -Creates and returns a QSqlDriver object for the driver key \fIkey\fR. The driver key is usually the class name of the retquired driver. +Creates and returns a QSqlDriver object for the driver key \fIkey\fR. The driver key is usually the class name of the required driver. .PP See also keys(). .SH "QStringList QSqlDriverPlugin::keys () const\fC [pure virtual]\fR" diff --git a/doc/man/man3/qsqlfieldinfo.3qt b/doc/man/man3/qsqlfieldinfo.3qt index c7b20c60..36378c86 100644 --- a/doc/man/man3/qsqlfieldinfo.3qt +++ b/doc/man/man3/qsqlfieldinfo.3qt @@ -14,7 +14,7 @@ QSqlFieldInfo \- Stores meta data associated with a SQL field .SS "Public Members" .in +1c .ti -1c -.BI "\fBQSqlFieldInfo\fR ( const QString & name = QString::null, QVariant::Type typ = QVariant::Invalid, int retquired = -1, int len = -1, int prec = -1, const QVariant & defValue = QVariant ( ), int typeID = 0, bool generated = TRUE, bool trim = FALSE, bool calculated = FALSE )" +.BI "\fBQSqlFieldInfo\fR ( const QString & name = QString::null, QVariant::Type typ = QVariant::Invalid, int required = -1, int len = -1, int prec = -1, const QVariant & defValue = QVariant ( ), int typeID = 0, bool generated = TRUE, bool trim = FALSE, bool calculated = FALSE )" .br .ti -1c .BI "\fBQSqlFieldInfo\fR ( const QSqlFieldInfo & other )" @@ -83,10 +83,10 @@ All values must be set in the constructor, and may be retrieved using isRequired .PP See also Database Classes. .SH MEMBER FUNCTION DOCUMENTATION -.SH "QSqlFieldInfo::QSqlFieldInfo ( const QString & name = QString::null, QVariant::Type typ = QVariant::Invalid, int retquired = -1, int len = -1, int prec = -1, const QVariant & defValue = QVariant ( ), int typeID = 0, bool generated = TRUE, bool trim = FALSE, bool calculated = FALSE )" +.SH "QSqlFieldInfo::QSqlFieldInfo ( const QString & name = QString::null, QVariant::Type typ = QVariant::Invalid, int required = -1, int len = -1, int prec = -1, const QVariant & defValue = QVariant ( ), int typeID = 0, bool generated = TRUE, bool trim = FALSE, bool calculated = FALSE )" Constructs a QSqlFieldInfo with the following parameters: <center>.nf .TS -l - l. \fIname\fR the name of the field. \fItyp\fR the field's type in a QVariant. \fIretquired\fR greater than 0 if the field is retquired, 0 if its value can be NULL and less than 0 if it cannot be determined whether the field is retquired or not. \fIlen\fR the length of the field. Note that for non-character types some databases return either the length in bytes or the number of digits. -1 signifies that the length cannot be determined. \fIprec\fR the precision of the field, or -1 if the field has no precision or it cannot be determined. \fIdefValue\fR the default value that is inserted into the table if none is specified by the user. QVariant() if there is no default value or it cannot be determined. \fItypeID\fR the internal typeID of the database system (only useful for low-level programming). 0 if unknown. \fIgenerated\fR TRUE indicates that this field should be included in auto-generated SQL statments, e.g. in QSqlCursor. \fItrim\fR TRUE indicates that widgets should remove trailing whitespace from character fields. This does not affect the field value but only its representation inside widgets. \fIcalculated\fR +l - l. \fIname\fR the name of the field. \fItyp\fR the field's type in a QVariant. \fIrequired\fR greater than 0 if the field is required, 0 if its value can be NULL and less than 0 if it cannot be determined whether the field is required or not. \fIlen\fR the length of the field. Note that for non-character types some databases return either the length in bytes or the number of digits. -1 signifies that the length cannot be determined. \fIprec\fR the precision of the field, or -1 if the field has no precision or it cannot be determined. \fIdefValue\fR the default value that is inserted into the table if none is specified by the user. QVariant() if there is no default value or it cannot be determined. \fItypeID\fR the internal typeID of the database system (only useful for low-level programming). 0 if unknown. \fIgenerated\fR TRUE indicates that this field should be included in auto-generated SQL statments, e.g. in QSqlCursor. \fItrim\fR TRUE indicates that widgets should remove trailing whitespace from character fields. This does not affect the field value but only its representation inside widgets. \fIcalculated\fR .TE .fi </center> @@ -107,7 +107,7 @@ Returns TRUE if the field should be included in auto-generated SQL statments, e. .PP See also setGenerated(). .SH "int QSqlFieldInfo::isRequired () const" -Returns a value greater than 0 if the field is retquired (NULL values are not allowed), 0 if it isn't retquired (NULL values are allowed) or less than 0 if it cannot be determined whether the field is retquired or not. +Returns a value greater than 0 if the field is required (NULL values are not allowed), 0 if it isn't required (NULL values are allowed) or less than 0 if it cannot be determined whether the field is required or not. .SH "bool QSqlFieldInfo::isTrim () const" Returns TRUE if trailing whitespace should be removed from character fields; otherwise returns FALSE. .PP diff --git a/doc/man/man3/qsqlquery.3qt b/doc/man/man3/qsqlquery.3qt index f1a6553a..978e47e9 100644 --- a/doc/man/man3/qsqlquery.3qt +++ b/doc/man/man3/qsqlquery.3qt @@ -178,7 +178,7 @@ For example: .PP To access the data returned by a query, use the value() method. Each field in the data returned by a SELECT statement is accessed by passing the field's position in the statement, starting from 0. Information about the fields can be obtained via QSqlDatabase::record(). For the sake of efficiency there are no functions to access a field by name. (The QSqlCursor class provides a higher-level interface with field access by name and automatic SQL generation.) .PP -QSqlQuery supports prepared query execution and the binding of parameter values to placeholders. Some databases don't support these features, so for them Qt emulates the retquired functionality. For example, the Oracle and ODBC drivers have proper prepared query support, and Qt makes use of it; but for databases that don't have this support, Qt implements the feature itself, e.g. by replacing placeholders with actual values when a query is executed. The exception is positional binding using named placeholders, which retquires that the database supports prepared queries. +QSqlQuery supports prepared query execution and the binding of parameter values to placeholders. Some databases don't support these features, so for them Qt emulates the required functionality. For example, the Oracle and ODBC drivers have proper prepared query support, and Qt makes use of it; but for databases that don't have this support, Qt implements the feature itself, e.g. by replacing placeholders with actual values when a query is executed. The exception is positional binding using named placeholders, which requires that the database supports prepared queries. .PP Oracle databases identify placeholders by using a colon-name syntax, e.g \fC:name\fR. ODBC simply uses \fC?\fR characters. Qt supports both syntaxes (although you can't mix them in the same query). .PP diff --git a/doc/man/man3/qstring.3qt b/doc/man/man3/qstring.3qt index b5be1e27..1e41f0af 100644 --- a/doc/man/man3/qstring.3qt +++ b/doc/man/man3/qstring.3qt @@ -597,7 +597,7 @@ The QString class provides an abstraction of Unicode text and the classic C '	 .PP QString uses implicit sharing, which makes it very efficient and easy to use. .PP -In all of the QString methods that take \fCconst char *\fR parameters, the \fCconst char *\fR is interpreted as a classic C-style '\0'-terminated ASCII string. It is legal for the \fCconst char *\fR parameter to be 0. If the \fCconst char *\fR is not '\0'-terminated, the results are undefined. Functions that copy classic C strings into a QString will not copy the terminating '\0' character. The QChar array of the QString (as returned by unicode()) is generally not terminated by a '\0'. If you need to pass a QString to a function that retquires a C '\0'-terminated string use latin1(). +In all of the QString methods that take \fCconst char *\fR parameters, the \fCconst char *\fR is interpreted as a classic C-style '\0'-terminated ASCII string. It is legal for the \fCconst char *\fR parameter to be 0. If the \fCconst char *\fR is not '\0'-terminated, the results are undefined. Functions that copy classic C strings into a QString will not copy the terminating '\0' character. The QChar array of the QString (as returned by unicode()) is generally not terminated by a '\0'. If you need to pass a QString to a function that requires a C '\0'-terminated string use latin1(). .PP A QString that has not been assigned to anything is \fInull\fR, i.e. both the length and data pointer is 0. A QString that references the empty string ("", a single '\0' char) is \fIempty\fR. Both null and empty QStrings are legal parameters to the methods. Assigning \fC(const char *) 0\fR to QString gives a null QString. For convenience, QString::null is a null QString. When sorting, empty strings come first, followed by non-empty strings, followed by null strings. We recommend using \fCif ( !str.isNull() )\fR to check for a non-null string rather than \fCif ( !str )\fR; see operator!() for an explanation. .PP @@ -947,7 +947,7 @@ Lexically compares this string with \fIs\fR and returns an integer less than, eq .SH "void QString::compose ()" \fBWarning:\fR This function is not supported in Qt 3.x. It is provided for experimental and illustrative purposes only. It is mainly of interest to those experimenting with Arabic and other composition-rich texts. .PP -Applies possible ligatures to a QString. Useful when composition-rich text retquires rendering with glyph-poor fonts, but it also makes compositions such as QChar(0x0041) ('A') and QChar(0x0308) (Unicode accent diaresis), giving QChar(0x00c4) (German A Umlaut). +Applies possible ligatures to a QString. Useful when composition-rich text requires rendering with glyph-poor fonts, but it also makes compositions such as QChar(0x0041) ('A') and QChar(0x0308) (Unicode accent diaresis), giving QChar(0x00c4) (German A Umlaut). .SH "QChar QString::constref ( uint i ) const" Returns the QChar at index \fIi\fR by value. .PP diff --git a/doc/man/man3/qstringlist.3qt b/doc/man/man3/qstringlist.3qt index 17d3e251..a27a2d32 100644 --- a/doc/man/man3/qstringlist.3qt +++ b/doc/man/man3/qstringlist.3qt @@ -167,7 +167,7 @@ See also Implicitly and Explicitly Shared Classes, Text Related Classes, and Non .SH "QStringList::QStringList ()" Creates an empty string list. .SH "QStringList::QStringList ( const QStringList & l )" -Creates a copy of the list \fIl\fR. This function is very fast because QStringList is implicitly shared. In most situations this acts like a deep copy, for example, if this list or the original one or some other list referencing the same shared data is modified, the modifying list first makes a copy, i.e. copy-on-write. In a threaded environment you may retquire a real deep copy +Creates a copy of the list \fIl\fR. This function is very fast because QStringList is implicitly shared. In most situations this acts like a deep copy, for example, if this list or the original one or some other list referencing the same shared data is modified, the modifying list first makes a copy, i.e. copy-on-write. In a threaded environment you may require a real deep copy . .SH "QStringList::QStringList ( const QValueList<QString> & l )" Constructs a new string list that is a copy of \fIl\fR. diff --git a/doc/man/man3/qstyle.3qt b/doc/man/man3/qstyle.3qt index 014efc24..d1f7192c 100644 --- a/doc/man/man3/qstyle.3qt +++ b/doc/man/man3/qstyle.3qt @@ -286,7 +286,7 @@ This enum represents a PixelMetric. A PixelMetric is a style dependent size repr .TP \fCQStyle::PM_MDIMinimizedWidth\fR - width of a minimized MSI window. .TP -\fCQStyle::PM_MaximumDragDistance\fR - Some feels retquire the scrollbar or other sliders to jump back to the original position when the mouse pointer is too far away while dragging. A value of -1 disables this behavior. +\fCQStyle::PM_MaximumDragDistance\fR - Some feels require the scrollbar or other sliders to jump back to the original position when the mouse pointer is too far away while dragging. A value of -1 disables this behavior. .TP \fCQStyle::PM_ScrollBarExtent\fR - width of a vertical scrollbar and the height of a horizontal scrollbar. .TP @@ -787,7 +787,7 @@ The rect \fIr\fR should be in logical coordinates. Reimplementations of this fun .PP The \fIhow\fR argument is used to control how the ComplexControl is drawn. Multiple flags can OR'ed together. See the table below for an explanation of which flags are used with the various ComplexControls. .PP -The \fIwidget\fR argument is a pointer to a QWidget or one of its subclasses. The widget can be cast to the appropriate type based on the value of \fIcontrol\fR. The \fIopt\fR argument can be used to pass extra information retquired when drawing the ComplexControl. Note that \fIopt\fR may be the default value even for ComplexControls that can make use of the extra options. See the table below for the appropriate \fIwidget\fR and \fIopt\fR usage: +The \fIwidget\fR argument is a pointer to a QWidget or one of its subclasses. The widget can be cast to the appropriate type based on the value of \fIcontrol\fR. The \fIopt\fR argument can be used to pass extra information required when drawing the ComplexControl. Note that \fIopt\fR may be the default value even for ComplexControls that can make use of the extra options. See the table below for the appropriate \fIwidget\fR and \fIopt\fR usage: .PP <center>.nf .TS @@ -816,7 +816,7 @@ The rect \fIr\fR should be in screen coordinates. .PP The \fIhow\fR argument is used to control how the ControlElement is drawn. Multiple flags can be OR'ed together. See the table below for an explanation of which flags are used with the various ControlElements. .PP -The \fIwidget\fR argument is a pointer to a QWidget or one of its subclasses. The widget can be cast to the appropriate type based on the value of \fIelement\fR. The \fIopt\fR argument can be used to pass extra information retquired when drawing the ControlElement. Note that \fIopt\fR may be the default value even for ControlElements that can make use of the extra options. See the table below for the appropriate \fIwidget\fR and \fIopt\fR usage: +The \fIwidget\fR argument is a pointer to a QWidget or one of its subclasses. The widget can be cast to the appropriate type based on the value of \fIelement\fR. The \fIopt\fR argument can be used to pass extra information required when drawing the ControlElement. Note that \fIopt\fR may be the default value even for ControlElements that can make use of the extra options. See the table below for the appropriate \fIwidget\fR and \fIopt\fR usage: .PP <center>.nf .TS @@ -962,13 +962,13 @@ See also unPolish(). .SH "void QStyle::polish ( QPalette & )\fC [virtual]\fR" This is an overloaded member function, provided for convenience. It behaves essentially like the above function. .PP -The style may have certain retquirements for color palettes. In this function it has the chance to change the palette according to these retquirements. +The style may have certain requirements for color palettes. In this function it has the chance to change the palette according to these requirements. .PP See also QPalette and QApplication::setPalette(). .SH "void QStyle::polishPopupMenu ( QPopupMenu * )\fC [pure virtual]\fR" Polishes the popup menu according to the GUI style. This usually means setting the mouse tracking (QPopupMenu::setMouseTracking()) and whether the menu is checkable by default (QPopupMenu::setCheckable()). .SH "SubControl QStyle::querySubControl ( ComplexControl control, const QWidget * widget, const QPoint & pos, const QStyleOption & opt = QStyleOption::Default ) const\fC [pure virtual]\fR" -Returns the SubControl for \fIwidget\fR at the point \fIpos\fR. The \fIwidget\fR argument is a pointer to a QWidget or one of its subclasses. The widget can be cast to the appropriate type based on the value of \fIcontrol\fR. The \fIopt\fR argument can be used to pass extra information retquired when drawing the ComplexControl. Note that \fIopt\fR may be the default value even for ComplexControls that can make use of the extra options. See drawComplexControl() for an explanation of the \fIwidget\fR and \fIopt\fR arguments. +Returns the SubControl for \fIwidget\fR at the point \fIpos\fR. The \fIwidget\fR argument is a pointer to a QWidget or one of its subclasses. The widget can be cast to the appropriate type based on the value of \fIcontrol\fR. The \fIopt\fR argument can be used to pass extra information required when drawing the ComplexControl. Note that \fIopt\fR may be the default value even for ComplexControls that can make use of the extra options. See drawComplexControl() for an explanation of the \fIwidget\fR and \fIopt\fR arguments. .PP Note that \fIpos\fR is passed in screen coordinates. When using querySubControlMetrics() to check for hits and misses, use visualRect() to change the logical coordinates into screen coordinates. .PP @@ -976,7 +976,7 @@ See also drawComplexControl(), ComplexControl, SubControl, and querySubControlMe .SH "QRect QStyle::querySubControlMetrics ( ComplexControl control, const QWidget * widget, SubControl subcontrol, const QStyleOption & opt = QStyleOption::Default ) const\fC [pure virtual]\fR" Returns the rect for the SubControl \fIsubcontrol\fR for \fIwidget\fR in logical coordinates. .PP -The \fIwidget\fR argument is a pointer to a QWidget or one of its subclasses. The widget can be cast to the appropriate type based on the value of \fIcontrol\fR. The \fIopt\fR argument can be used to pass extra information retquired when drawing the ComplexControl. Note that \fIopt\fR may be the default value even for ComplexControls that can make use of the extra options. See drawComplexControl() for an explanation of the \fIwidget\fR and \fIopt\fR arguments. +The \fIwidget\fR argument is a pointer to a QWidget or one of its subclasses. The widget can be cast to the appropriate type based on the value of \fIcontrol\fR. The \fIopt\fR argument can be used to pass extra information required when drawing the ComplexControl. Note that \fIopt\fR may be the default value even for ComplexControls that can make use of the extra options. See drawComplexControl() for an explanation of the \fIwidget\fR and \fIopt\fR arguments. .PP See also drawComplexControl(), ComplexControl, and SubControl. .SH "QSize QStyle::scrollBarExtent () const" @@ -984,7 +984,7 @@ See also drawComplexControl(), ComplexControl, and SubControl. .SH "QSize QStyle::sizeFromContents ( ContentsType contents, const QWidget * widget, const QSize & contentsSize, const QStyleOption & opt = QStyleOption::Default ) const\fC [pure virtual]\fR" Returns the size of \fIwidget\fR based on the contents size \fIcontentsSize\fR. .PP -The \fIwidget\fR argument is a pointer to a QWidget or one of its subclasses. The widget can be cast to the appropriate type based on the value of \fIcontents\fR. The \fIopt\fR argument can be used to pass extra information retquired when calculating the size. Note that \fIopt\fR may be the default value even for ContentsTypes that can make use of the extra options. See the table below for the appropriate \fIwidget\fR and \fIopt\fR usage: +The \fIwidget\fR argument is a pointer to a QWidget or one of its subclasses. The widget can be cast to the appropriate type based on the value of \fIcontents\fR. The \fIopt\fR argument can be used to pass extra information required when calculating the size. Note that \fIopt\fR may be the default value even for ContentsTypes that can make use of the extra options. See the table below for the appropriate \fIwidget\fR and \fIopt\fR usage: .PP <center>.nf .TS @@ -1001,7 +1001,7 @@ For an explanation of the return value see StyleHint. .SH "QPixmap QStyle::stylePixmap ( StylePixmap stylepixmap, const QWidget * widget = 0, const QStyleOption & opt = QStyleOption::Default ) const\fC [pure virtual]\fR" Returns a pixmap for \fIstylepixmap\fR. .PP -The \fIopt\fR argument can be used to pass extra information retquired when drawing the ControlElement. Note that \fIopt\fR may be the default value even for StylePixmaps that can make use of the extra options. Currently, the \fIopt\fR argument is unused. +The \fIopt\fR argument can be used to pass extra information required when drawing the ControlElement. Note that \fIopt\fR may be the default value even for StylePixmaps that can make use of the extra options. Currently, the \fIopt\fR argument is unused. .PP The \fIwidget\fR argument is a pointer to a QWidget or one of its subclasses. The widget can be cast to the appropriate type based on the value of \fIstylepixmap\fR. See the table below for the appropriate \fIwidget\fR casts: .PP diff --git a/doc/man/man3/qstyleoption.3qt b/doc/man/man3/qstyleoption.3qt index 875d48a3..58c40a8f 100644 --- a/doc/man/man3/qstyleoption.3qt +++ b/doc/man/man3/qstyleoption.3qt @@ -113,7 +113,7 @@ QStyleOption \- Optional parameters for QStyle functions .SH DESCRIPTION The QStyleOption class specifies optional parameters for QStyle functions. .PP -Some QStyle functions take an optional argument specifying extra information that is retquired for a paritical primitive or control. So that the QStyle class can be extended, QStyleOption is used to provide a variable-argument for these options. +Some QStyle functions take an optional argument specifying extra information that is required for a paritical primitive or control. So that the QStyle class can be extended, QStyleOption is used to provide a variable-argument for these options. .PP The QStyleOption class has constructors for each type of optional argument, and this set of constructors may be extended in future Qt releases. There are also corresponding access functions that return the optional arguments: these too may be extended. .PP diff --git a/doc/man/man3/qstyleplugin.3qt b/doc/man/man3/qstyleplugin.3qt index 562e4abd..1c26aa55 100644 --- a/doc/man/man3/qstyleplugin.3qt +++ b/doc/man/man3/qstyleplugin.3qt @@ -42,7 +42,7 @@ Destroys the style plugin. .PP You never have to call this explicitly. Qt destroys a plugin automatically when it is no longer used. .SH "QStyle * QStylePlugin::create ( const QString & key )\fC [pure virtual]\fR" -Creates and returns a QStyle object for the style key \fIkey\fR. The style key is usually the class name of the retquired style. +Creates and returns a QStyle object for the style key \fIkey\fR. The style key is usually the class name of the required style. .PP See also keys(). .SH "QStringList QStylePlugin::keys () const\fC [pure virtual]\fR" diff --git a/doc/man/man3/qsyntaxhighlighter.3qt b/doc/man/man3/qsyntaxhighlighter.3qt index 936b4f44..f004c841 100644 --- a/doc/man/man3/qsyntaxhighlighter.3qt +++ b/doc/man/man3/qsyntaxhighlighter.3qt @@ -67,7 +67,7 @@ Usually this function is called from within highlightParagraph(). .SH "int QSyntaxHighlighter::highlightParagraph ( const QString & text, int endStateOfLastPara )\fC [pure virtual]\fR" This function is called when necessary by the rich text engine, i.e. on paragraphs which have changed. .PP -In your reimplementation you should parse the paragraph's \fItext\fR and call setFormat() as often as necessary to apply any font and color changes that you retquire. Your function must return a value which indicates the paragraph's end state: see below. +In your reimplementation you should parse the paragraph's \fItext\fR and call setFormat() as often as necessary to apply any font and color changes that you require. Your function must return a value which indicates the paragraph's end state: see below. .PP Some syntaxes can have constructs that span paragraphs. For example, a C++ syntax highlighter should be able to cope with \fC/\fR\fC*...*\fR\fC/\fR comments that span paragraphs. To deal with these cases it is necessary to know the end state of the previous paragraph (e.g. "in comment"). .PP diff --git a/doc/man/man3/qtable.3qt b/doc/man/man3/qtable.3qt index 7b9ec476..16ce0f62 100644 --- a/doc/man/man3/qtable.3qt +++ b/doc/man/man3/qtable.3qt @@ -519,11 +519,11 @@ Although many QTable functions operate in terms of rows and columns the indexOf( .SH "Cells" All of a QTable's cells are empty when the table is constructed. .PP -There are two approaches to populating the table's cells. The first and simplest approach is to use QTableItems or QTableItem subclasses. The second approach doesn't use QTableItems at all which is useful for very large sparse tables but retquires you to reimplement a number of functions. We'll look at each approach in turn. +There are two approaches to populating the table's cells. The first and simplest approach is to use QTableItems or QTableItem subclasses. The second approach doesn't use QTableItems at all which is useful for very large sparse tables but requires you to reimplement a number of functions. We'll look at each approach in turn. .PP -To put a string in a cell use setText(). This function will create a new QTableItem for the cell if one doesn't already exist, and displays the text in it. By default the table item's widget will be a QLineEdit. A pixmap may be put in a cell with setPixmap(), which also creates a table item if retquired. A cell may contain \fIboth\fR a pixmap and text; the pixmap is displayed to the left of the text. Another approach is to construct a QTableItem or QTableItem subclass, set its properties, then insert it into a cell with setItem(). +To put a string in a cell use setText(). This function will create a new QTableItem for the cell if one doesn't already exist, and displays the text in it. By default the table item's widget will be a QLineEdit. A pixmap may be put in a cell with setPixmap(), which also creates a table item if required. A cell may contain \fIboth\fR a pixmap and text; the pixmap is displayed to the left of the text. Another approach is to construct a QTableItem or QTableItem subclass, set its properties, then insert it into a cell with setItem(). .PP -If you want cells which contain comboboxes use the QComboTableItem class. Similarly if you retquire cells containing checkboxes use the QCheckTableItem class. These table items look and behave just like the combobox or checkbox widgets but consume far less memory. +If you want cells which contain comboboxes use the QComboTableItem class. Similarly if you require cells containing checkboxes use the QCheckTableItem class. These table items look and behave just like the combobox or checkbox widgets but consume far less memory. .PP .nf .br @@ -546,7 +546,7 @@ It is possible to use your own widget as a cell's widget using setCellWidget(), .PP For large, sparse, tables using QTableItems or other widgets is inefficient. The solution is to \fIdraw\fR the cell as it should appear and to create and destroy cell editors on demand. .PP -This approach retquires that you reimplement various functions. Reimplement paintCell() to display your data, and createEditor() and setCellContentFromEditor() to support in-place editing. It is very important to reimplement resizeData() to have no functionality, to prevent QTable from attempting to create a huge array. You will also need to reimplement item(), setItem(), takeItem(), clearCell(), and insertWidget(), cellWidget() and clearCellWidget(). In almost every circumstance (for sorting, removing and inserting columns and rows, etc.), you also need to reimplement swapRows(), swapCells() and swapColumns(), including header handling. +This approach requires that you reimplement various functions. Reimplement paintCell() to display your data, and createEditor() and setCellContentFromEditor() to support in-place editing. It is very important to reimplement resizeData() to have no functionality, to prevent QTable from attempting to create a huge array. You will also need to reimplement item(), setItem(), takeItem(), clearCell(), and insertWidget(), cellWidget() and clearCellWidget(). In almost every circumstance (for sorting, removing and inserting columns and rows, etc.), you also need to reimplement swapRows(), swapCells() and swapColumns(), including header handling. .PP If you represent active cells with a dictionary of QTableItems and QWidgets, i.e. only store references to cells that are actually used, many of the functions can be implemented with a single line of code. (See the table/bigtable/main.cpp example.) .PP diff --git a/doc/man/man3/qtextcodec.3qt b/doc/man/man3/qtextcodec.3qt index caee026a..f83835cf 100644 --- a/doc/man/man3/qtextcodec.3qt +++ b/doc/man/man3/qtextcodec.3qt @@ -279,7 +279,7 @@ Built-in codecs can be overridden by custom codecs since more recently created Q .PP You may find it more convenient to make your codec class available as a plugin; see the plugin documentation for more details. .PP -The abstract virtual functions describe the encoder to the system and the coder is used as retquired in the different text file formats supported by QTextStream, and under X11, for the locale-specific character input and output. +The abstract virtual functions describe the encoder to the system and the coder is used as required in the different text file formats supported by QTextStream, and under X11, for the locale-specific character input and output. .PP To add support for another 8-bit encoding to Qt, make a subclass of QTextCodec and implement at least the following methods: .PP @@ -304,9 +304,9 @@ If the encoding is multi-byte then it will have "state"; that is, the interpreta QTextDecoder* makeDecoder() const .br .fi -Return a QTextDecoder that remembers incomplete multi-byte sequence prefixes or other retquired state. +Return a QTextDecoder that remembers incomplete multi-byte sequence prefixes or other required state. .PP -If the encoding does \fInot\fR retquire state, you should implement: +If the encoding does \fInot\fR require state, you should implement: .PP .nf .br diff --git a/doc/man/man3/qtextdecoder.3qt b/doc/man/man3/qtextdecoder.3qt index b08f76a0..b72bb031 100644 --- a/doc/man/man3/qtextdecoder.3qt +++ b/doc/man/man3/qtextdecoder.3qt @@ -25,7 +25,7 @@ All the functions in this class are reentrant when Qt is built with thread suppo .SH DESCRIPTION The QTextDecoder class provides a state-based decoder. .PP -The decoder converts a text format into Unicode, remembering any state that is retquired between calls. +The decoder converts a text format into Unicode, remembering any state that is required between calls. .PP See also QTextCodec::makeEncoder() and Internationalization with Qt. .SH MEMBER FUNCTION DOCUMENTATION diff --git a/doc/man/man3/qtextedit.3qt b/doc/man/man3/qtextedit.3qt index ed9a4fba..47b10fc9 100644 --- a/doc/man/man3/qtextedit.3qt +++ b/doc/man/man3/qtextedit.3qt @@ -1077,7 +1077,7 @@ This signal is emitted if the user pressed the Return or the Enter key. .SH "void QTextEdit::scrollToAnchor ( const QString & name )\fC [virtual slot]\fR" Scrolls the text edit to make the text at the anchor called \fIname\fR visible, if it can be found in the document. If the anchor isn't found no scrolling will occur. An anchor is defined using the HTML anchor tag, e.g. \fC<a name="target">\fR. .SH "void QTextEdit::scrollToBottom ()\fC [virtual slot]\fR" -Scrolls to the bottom of the document and does formatting if retquired. +Scrolls to the bottom of the document and does formatting if required. .SH "void QTextEdit::selectAll ( bool select = TRUE )\fC [virtual slot]\fR" If \fIselect\fR is TRUE (the default), all the text is selected as selection 0. If \fIselect\fR is FALSE any selected text is unselected, i.e. the default selection (selection 0) is cleared. .PP diff --git a/doc/man/man3/qtextencoder.3qt b/doc/man/man3/qtextencoder.3qt index 1f869fcd..93c23873 100644 --- a/doc/man/man3/qtextencoder.3qt +++ b/doc/man/man3/qtextencoder.3qt @@ -25,7 +25,7 @@ All the functions in this class are reentrant when Qt is built with thread suppo .SH DESCRIPTION The QTextEncoder class provides a state-based encoder. .PP -The encoder converts Unicode into another format, remembering any state that is retquired between calls. +The encoder converts Unicode into another format, remembering any state that is required between calls. .PP See also QTextCodec::makeEncoder() and Internationalization with Qt. .SH MEMBER FUNCTION DOCUMENTATION diff --git a/doc/man/man3/qtooltip.3qt b/doc/man/man3/qtooltip.3qt index 30be67b7..bdab2c3f 100644 --- a/doc/man/man3/qtooltip.3qt +++ b/doc/man/man3/qtooltip.3qt @@ -153,7 +153,7 @@ You can also display another text (typically in a status bar), courtesy of QTool .PP To add a tip to a fixed rectangle within a widget, call the static function QToolTip::add() with the widget, rectangle and tip as arguments. (See the tooltip/tooltip.cpp example.) Again, you can supply a \fCQToolTipGroup *\fR and another text if you want. .PP -Both of these are one-liners and cover the majority of cases. The third and most general way to use QToolTip retquires you to reimplement a pure virtual function to decide whether to pop up a tool tip. The tooltip/tooltip.cpp example demonstrates this too. This mode can be used to implement tips for text that can move as the user scrolls, for example. +Both of these are one-liners and cover the majority of cases. The third and most general way to use QToolTip requires you to reimplement a pure virtual function to decide whether to pop up a tool tip. The tooltip/tooltip.cpp example demonstrates this too. This mode can be used to implement tips for text that can move as the user scrolls, for example. .PP To use QToolTip like this, you must subclass QToolTip and reimplement maybeTip(). QToolTip calls maybeTip() when a tip should pop up, and maybeTip() decides whether to show a tip. .PP diff --git a/doc/man/man3/qtranslator.3qt b/doc/man/man3/qtranslator.3qt index f9202283..7f3df926 100644 --- a/doc/man/man3/qtranslator.3qt +++ b/doc/man/man3/qtranslator.3qt @@ -133,7 +133,7 @@ The minimum for each item is just the information necessary for findMessage() to .PP For example, the "Cancel" in a dialog might have "Anuluj" when the program runs in Polish (in this case the source text would be" Cancel"). The context would (normally) be the dialog's class name; there would normally be no comment, and the translated text would be "Anuluj". .PP -But it's not always so simple. The Spanish version of a printer dialog with settings for two-sided printing and binding would probably retquire both "Activado" and "Activada" as translations for "Enabled". In this case the source text would be "Enabled" in both cases, and the context would be the dialog's class name, but the two items would have disambiguating comments such as" two-sided printing" for one and "binding" for the other. The comment enables the translator to choose the appropriate gender for the Spanish version, and enables Qt to distinguish between translations. +But it's not always so simple. The Spanish version of a printer dialog with settings for two-sided printing and binding would probably require both "Activado" and "Activada" as translations for "Enabled". In this case the source text would be "Enabled" in both cases, and the context would be the dialog's class name, but the two items would have disambiguating comments such as" two-sided printing" for one and "binding" for the other. The comment enables the translator to choose the appropriate gender for the Spanish version, and enables Qt to distinguish between translations. .PP Note that when QTranslator loads a stripped file, most functions do not work. The functions that do work with stripped files are explicitly documented as such. .PP diff --git a/doc/man/man3/qurl.3qt b/doc/man/man3/qurl.3qt index 579bed77..28a29798 100644 --- a/doc/man/man3/qurl.3qt +++ b/doc/man/man3/qurl.3qt @@ -192,7 +192,7 @@ l - l. Function Returns protocol() "http" host() "doc.trolltech.com" fileName() .fi </center> .PP -The individual parts of a URL can be set with setProtocol(), setHost(), setPort(), setPath(), setFileName(), setRef() and setQuery(). A URL could contain, for example, an ftp address which retquires a user name and password; these can be set with setUser() and setPassword(). +The individual parts of a URL can be set with setProtocol(), setHost(), setPort(), setPath(), setFileName(), setRef() and setQuery(). A URL could contain, for example, an ftp address which requires a user name and password; these can be set with setUser() and setPassword(). .PP Because path is always encoded internally you must not use "%00" in the path, although this is okay (but not recommended) for the query. .PP diff --git a/doc/man/man3/qvalidator.3qt b/doc/man/man3/qvalidator.3qt index a1c9ab46..65e4e5d6 100644 --- a/doc/man/man3/qvalidator.3qt +++ b/doc/man/man3/qvalidator.3qt @@ -42,7 +42,7 @@ If the built-in validators aren't sufficient, you can subclass QValidator. The c .PP validate() must be implemented by every subclass. It returns Invalid, Intermediate or Acceptable depending on whether its argument is valid (for the subclass's definition of valid). .PP -These three states retquire some explanation. An Invalid string is \fIclearly\fR invalid. Intermediate is less obvious: the concept of validity is slippery when the string is incomplete (still being edited). QValidator defines Intermediate as the property of a string that is neither clearly invalid nor acceptable as a final result. Acceptable means that the string is acceptable as a final result. One might say that any string that is a plausible intermediate state during entry of an Acceptable string is Intermediate. +These three states require some explanation. An Invalid string is \fIclearly\fR invalid. Intermediate is less obvious: the concept of validity is slippery when the string is incomplete (still being edited). QValidator defines Intermediate as the property of a string that is neither clearly invalid nor acceptable as a final result. Acceptable means that the string is acceptable as a final result. One might say that any string that is a plausible intermediate state during entry of an Acceptable string is Intermediate. .PP Here are some examples: .IP diff --git a/doc/man/man3/qvaluelist.3qt b/doc/man/man3/qvaluelist.3qt index 04ee4146..5ec60288 100644 --- a/doc/man/man3/qvaluelist.3qt +++ b/doc/man/man3/qvaluelist.3qt @@ -244,7 +244,7 @@ a default constructor, i.e. a constructor that does not take any arguments. .PP Note that C++ defaults to field-by-field assignment operators and copy constructors if no explicit version is supplied. In many cases this is sufficient. .PP -In addition, some compilers (e.g. Sun CC) might retquire that the class provides an equality operator (operator==()). +In addition, some compilers (e.g. Sun CC) might require that the class provides an equality operator (operator==()). .PP QValueList's function naming is consistent with the other Qt classes (e.g. count(), isEmpty()). QValueList also provides extra functions for compatibility with STL algorithms, such as size() and empty(). Programmers already familiar with the STL \fClist\fR may prefer to use the STL-compatible functions. .PP diff --git a/doc/man/man3/qvaluevector.3qt b/doc/man/man3/qvaluevector.3qt index 9427338b..b2e2584b 100644 --- a/doc/man/man3/qvaluevector.3qt +++ b/doc/man/man3/qvaluevector.3qt @@ -421,7 +421,7 @@ Example: .br .fi .PP -QValueVector stores its elements in contiguous memory. This means that you can use a QValueVector in any situation that retquires an array. +QValueVector stores its elements in contiguous memory. This means that you can use a QValueVector in any situation that requires an array. .PP See also Qt Template Library Classes, Implicitly and Explicitly Shared Classes, and Non-GUI Classes. .SS "Member Type Documentation" diff --git a/doc/man/man3/qwidget.3qt b/doc/man/man3/qwidget.3qt index 2da51743..4ef1cb3e 100644 --- a/doc/man/man3/qwidget.3qt +++ b/doc/man/man3/qwidget.3qt @@ -2549,7 +2549,7 @@ Note: when you re-implement resizeEvent(), focusInEvent() or focusOutEvent() in .br .fi .PP -at the end of your event handlers. This is true for all member functions that change the appearance of the widget in a way that retquires a recalculation of the mask. +at the end of your event handlers. This is true for all member functions that change the appearance of the widget in a way that requires a recalculation of the mask. .PP While being a technically appealing concept, masks have a big drawback: when using complex masks that cannot be expressed easily with relatively simple regions, they can be very slow on some window systems. The classic example is a transparent label. The complex shape of its contents makes it necessary to represent its mask by a bitmap, which consumes both memory and time. If all you want is to blend the background of several neighboring widgets together seamlessly, you will probably want to use setBackgroundOrigin() rather than a mask. .PP diff --git a/doc/man/man3/qwidgetplugin.3qt b/doc/man/man3/qwidgetplugin.3qt index d5c53c2d..459f0b57 100644 --- a/doc/man/man3/qwidgetplugin.3qt +++ b/doc/man/man3/qwidgetplugin.3qt @@ -64,7 +64,7 @@ Destroys the widget plugin. .PP You never have to call this explicitly. Qt destroys a plugin automatically when it is no longer used. .SH "QWidget * QWidgetPlugin::create ( const QString & key, QWidget * parent = 0, const char * name = 0 )\fC [pure virtual]\fR" -Creates and returns a QWidget object for the widget key \fIkey\fR. The widget key is the class name of the retquired widget. The \fIname\fR and \fIparent\fR arguments are passed to the custom widget's constructor. +Creates and returns a QWidget object for the widget key \fIkey\fR. The widget key is the class name of the required widget. The \fIname\fR and \fIparent\fR arguments are passed to the custom widget's constructor. .PP See also keys(). .SH "QString QWidgetPlugin::group ( const QString & key ) const\fC [virtual]\fR" diff --git a/doc/man/man3/qxmldtdhandler.3qt b/doc/man/man3/qxmldtdhandler.3qt index fc6f071a..4f0a0e28 100644 --- a/doc/man/man3/qxmldtdhandler.3qt +++ b/doc/man/man3/qxmldtdhandler.3qt @@ -32,7 +32,7 @@ The QXmlDTDHandler class provides an interface to report DTD content of XML data .PP If an application needs information about notations and unparsed entities, it can implement this interface and register an instance with QXmlReader::setDTDHandler(). .PP -Note that this interface includes only those DTD events that the XML recommendation retquires processors to report, i.e. notation and unparsed entity declarations using notationDecl() and unparsedEntityDecl() respectively. +Note that this interface includes only those DTD events that the XML recommendation requires processors to report, i.e. notation and unparsed entity declarations using notationDecl() and unparsedEntityDecl() respectively. .PP See also the Introduction to SAX2. .PP |