Rename text nt* related files to equivalent tq*

Signed-off-by: Michele Calgaro <michele.calgaro@yahoo.it>

1 files changed, 14 insertions, 14 deletions

diff --git a/doc/i18n.doc b/doc/i18n.doc
index 6ff7ce4a6..fec6ef570 100644
--- a/doc/i18n.doc
+++ b/doc/i18n.doc
@@ -121,7 +121,7 @@ the fl and fi ligatures used in typesetting US and European books.
 
 Qt tries to take care of all the special features listed above. You
 usually don't have to worry about these features so long as you use
-Qt's input widgets (e.g. QLineEdit, QTextEdit, and derived classes)
+Qt's input widgets (e.g. QLineEdit, TQTextEdit, and derived classes)
 and Qt's display widgets (e.g. QLabel).
 
 Support for these writing systems is transparent to the programmer
@@ -143,7 +143,7 @@ string. In some languages (e.g. Arabic or languages from the Indian
 subcontinent), the width and shape of a glyph changes depending on the
 surrounding characters. Writing input controls usually requires a
 certain knowledge of the scripts it is going to be used in. Usually
-the easiest way is to subclass QLineEdit or QTextEdit.
+the easiest way is to subclass QLineEdit or TQTextEdit.
 
 \endlist
 
@@ -403,12 +403,12 @@ Typically, your application's main() function will look like this:
 
         // translation file for Qt
         QTranslator qt( 0 );
-        qt.load( TQString( "qt_" ) + QTextCodec::locale(), "." );
+        qt.load( TQString( "qt_" ) + TQTextCodec::locale(), "." );
         app.installTranslator( &qt );
 
         // translation file for application strings
         QTranslator myapp( 0 );
-        myapp.load( TQString( "myapp_" ) + QTextCodec::locale(), "." );
+        myapp.load( TQString( "myapp_" ) + TQTextCodec::locale(), "." );
         app.installTranslator( &myapp );
 
         ...
@@ -419,7 +419,7 @@ Typically, your application's main() function will look like this:
 
 \section2 Support for Encodings
 
-The QTextCodec class and the facilities in QTextStream make it easy to
+The TQTextCodec class and the facilities in TQTextStream make it easy to
 support many input and output encodings for your users' data. When an
 application starts, the locale of the machine will determine the 8-bit
 encoding used when dealing with 8-bit data: such as for font
@@ -434,7 +434,7 @@ would be:
 \code
     TQString string = ...; // some Unicode text
 
-    QTextCodec* codec = QTextCodec::codecForName( "ISO 8859-5" );
+    TQTextCodec* codec = TQTextCodec::codecForName( "ISO 8859-5" );
     QCString encoded_string = codec->fromUnicode( string );
 
     ...; // use encoded_string in 8-bit operations
@@ -455,7 +455,7 @@ conversion:
 \code
     QCString encoded_string = ...; // Some ISO 8859-5 encoded text.
 
-    QTextCodec* codec = QTextCodec::codecForName("ISO 8859-5");
+    TQTextCodec* codec = TQTextCodec::codecForName("ISO 8859-5");
     TQString string = codec->toUnicode(encoded_string);
 
     ...; // Use string in all of Qt's TQString operations.
@@ -468,23 +468,23 @@ need to process existing documents. In general, Unicode (UTF-16 or
 UTF-8) is best for information transferred between arbitrary people,
 while within a language or national group, a local standard is often
 more appropriate. The most important encoding to support is the one
-returned by QTextCodec::codecForLocale(), as this is the one the user
+returned by TQTextCodec::codecForLocale(), as this is the one the user
 is most likely to need for communicating with other people and
 applications (this is the codec used by local8Bit()).
 
 Qt supports most of the more frequently used encodings natively. For a
-complete list of supported encodings see the \l QTextCodec
+complete list of supported encodings see the \l TQTextCodec
 documentation.
 
 In some cases and for less frequently used encodings it may be
-necessary to write your own QTextCodec subclass. Depending on the
+necessary to write your own TQTextCodec subclass. Depending on the
 urgency, it may be useful to contact Trolltech technical support or
 ask on the \c qt-interest mailing list to see if someone else is
 already working on supporting the encoding. A useful interim measure
-can be to use the QTextCodec::loadCharmapFile() function to build a
+can be to use the TQTextCodec::loadCharmapFile() function to build a
 data-driven codec, although this approach has a memory and speed
 penalty, especially with dynamically loaded libraries. For details of
-writing your own QTextCodec, see the main QTextCodec class
+writing your own TQTextCodec, see the main TQTextCodec class
 documentation.
 
 \keyword localization
@@ -561,7 +561,7 @@ not be too concerned with platform-specific limitations.
     (see QFile::setEncodingFunction()
         to explore alternative encodings).
 \i File I/O defaults to the local 8-bit encoding,
-    with Unicode options in QTextStream.
+    with Unicode options in TQTextStream.
 \endlist
 
 \section2 Windows
@@ -569,7 +569,7 @@ not be too concerned with platform-specific limitations.
 \list
 \i TQt provides full Unicode support, including input methods, fonts,
     clipboard, drag-and-drop and file names.
-\i File I/O defaults to Latin-1, with Unicode options in QTextStream.
+\i File I/O defaults to Latin-1, with Unicode options in TQTextStream.
     Note that some Windows programs do not understand big-endian
     Unicode text files even though that is the order prescribed by
     the Unicode Standard in the absence of higher-level protocols.