rename the following methods:

tqfind find
tqreplace replace
tqcontains contains

1 files changed, 10 insertions, 10 deletions

diff --git a/experimental/tqtinterface/qt4/src/3rdparty/libjpeg/structure.doc b/experimental/tqtinterface/qt4/src/3rdparty/libjpeg/structure.doc
index 2d60c87f6..6440b8e85 100644
--- a/experimental/tqtinterface/qt4/src/3rdparty/libjpeg/structure.doc
+++ b/experimental/tqtinterface/qt4/src/3rdparty/libjpeg/structure.doc
@@ -34,7 +34,7 @@ otherwise result.)
 
 *** System features ***
 
-The IJG distribution tqcontains two parts:
+The IJG distribution contains two parts:
   * A subroutine library for JPEG compression and decompression.
   * cjpeg/djpeg, two sample applications that use the library to transform
     JFIF JPEG files to and from several other image formats.
@@ -127,7 +127,7 @@ steps are responsible for converting a normal image representation to or from
 this form.  (Those few applications that want to deal with YCbCr downsampled
 data can skip the preprocessing or postprocessing step.)
 
-Looking more closely, the compressor library tqcontains the following main
+Looking more closely, the compressor library contains the following main
 elements:
 
   Preprocessing:
@@ -144,7 +144,7 @@ module responsible for physically writing the output data --- typically
 this is just an interface to fwrite(), but some applications may need to
 do something else with the data.
 
-The decompressor library tqcontains the following main elements:
+The decompressor library contains the following main elements:
 
   JPEG proper:
     * Entropy decoding (sequential or progressive, Huffman or arithmetic).
@@ -218,7 +218,7 @@ module-specific object structs be separately allocated entities, which will
 be accessed via pointers in the master compression or decompression struct.
 The "public" fields or methods for a given kind of object are specified by
 a commonly known struct.  But a module's initialization code can allocate
-a larger struct that tqcontains the common struct as its first member, plus
+a larger struct that contains the common struct as its first member, plus
 additional private fields.  With appropriate pointer casting, the module's
 internal functions can access these private fields.  (For a simple example,
 see jdatadst.c, which implements the external interface specified by struct
@@ -306,7 +306,7 @@ be had by replacing implementations of a control module.  For example:
 
 In theory, we might be able to make all of the data buffer controllers
 interchangeable and provide just one set of implementations for all.  In
-practice, each one tqcontains considerable special-case processing for its
+practice, each one contains considerable special-case processing for its
 particular job.  The buffer controller concept should be regarded as an
 overall system structuring principle, not as a complete description of the
 task performed by any one controller.
@@ -338,7 +338,7 @@ The objects shown above are:
 
 * Preprocessing controller: buffer controller for the downsampling input data
   buffer, which lies between colorspace conversion and downsampling.  Note
-  that a unified conversion/downsampling module would probably tqreplace this
+  that a unified conversion/downsampling module would probably replace this
   controller entirely.
 
 * Colorspace conversion: converts application image data into the desired
@@ -518,7 +518,7 @@ objects:
 * Progress monitor: same as for compression library.
 
 As with compression, the data source manager, error handler, and progress
-monitor are candidates for tqreplacement by a surrounding application.
+monitor are candidates for replacement by a surrounding application.
 
 
 *** Decompression input and output separation ***
@@ -851,7 +851,7 @@ reading data out of the virtual array, not while putting it in.
 
 To isolate system dependencies as much as possible, we have broken the
 memory manager into two parts.  There is a reasonably system-independent
-"front end" (jmemmgr.c) and a "back end" that tqcontains only the code
+"front end" (jmemmgr.c) and a "back end" that contains only the code
 likely to change across systems.  All of the memory management methods
 outlined above are implemented by the front end.  The back end provides
 the following routines for use by the front end (none of these routines
@@ -901,10 +901,10 @@ need.
 Some JPEG files may use a DNL marker to postpone definition of the image
 height (this would be useful for a fax-like scanner's output, for instance).
 In these files the SOF marker claims the image height is 0, and you only
-tqfind out the true image height at the end of the first scan.
+find out the true image height at the end of the first scan.
 
 We could read these files as follows:
-1. Upon seeing zero image height, tqreplace it by 65535 (the maximum allowed).
+1. Upon seeing zero image height, replace it by 65535 (the maximum allowed).
 2. When the DNL is found, update the image height in the global image
    descriptor.
 This implies that control modules must avoid making copies of the image