Rename str nt* related files to equivalent tq*

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

1 files changed, 18 insertions, 18 deletions

diff --git a/doc/html/i18n.html b/doc/html/i18n.html
index ccd9b771f..6c09191bf 100644
--- a/doc/html/i18n.html
+++ b/doc/html/i18n.html
@@ -140,7 +140,7 @@ and completely encapsulated in TQt's text engine. This means that you
 don't need to have any knowledge about the writing system used in a
 particular language, except for the following small points:
 <ul>
-<p> <li> <a href="ntqpainter.html#drawText">TQPainter::drawText</a>( int x, int y, const <a href="ntqstring.html">TQString</a> &str ) will always
+<p> <li> <a href="ntqpainter.html#drawText">TQPainter::drawText</a>( int x, int y, const <a href="tqstring.html">TQString</a> &str ) will always
 draw the string with it's left edge at the position specified with
 the x, y parameters. This will usually give you left aligned strings.
 Arabic and Hebrew application strings are usually right
@@ -161,7 +161,7 @@ of the internationalization (i18n) support in TQt.
 <a name="1"></a><p> Writing multi-platform international software with TQt is a gentle,
 incremental process. Your software can become internationalized in
 the following stages:
-<p> <h3> Use <a href="ntqstring.html">TQString</a> for all User-visible Text
+<p> <h3> Use <a href="tqstring.html">TQString</a> for all User-visible Text
 </h3>
 <a name="1-1"></a><p> Since TQString uses the Unicode encoding internally, every
 language in the world can be processed transparently using
@@ -238,17 +238,17 @@ The macros expand to just the text (without the context).
         return tr( greeting_strings[greet_type] );
     }
 
-    <a href="ntqstring.html">TQString</a> global_greeting( int greet_type )
+    <a href="tqstring.html">TQString</a> global_greeting( int greet_type )
     {
         return tqApp-&gt;<a href="ntqapplication.html#translate">translate</a>( "FriendlyConversation",
                                 greeting_strings[greet_type] );
     }
 </pre>
  
-<p> If you disable the const char* to <a href="ntqstring.html">TQString</a> automatic conversion
+<p> If you disable the const char* to <a href="tqstring.html">TQString</a> automatic conversion
 by compiling your software with the macro TQT_NO_CAST_ASCII
 defined, you'll be very likely to catch any strings you are
-missing. See <a href="ntqstring.html#fromLatin1">TQString::fromLatin1</a>() for more information.
+missing. See <a href="tqstring.html#fromLatin1">TQString::fromLatin1</a>() for more information.
 Disabling the conversion can make programming a bit cumbersome.
 <p> If your source language uses characters outside Latin-1, you
 might find <a href="tqobject.html#trUtf8">TQObject::trUtf8</a>() more convenient than
@@ -267,13 +267,13 @@ it. The correct idiom is
                       TQKeySequence(tr("Ctrl+Q", "File|Quit")) );
 </pre>
  
-<p> <h3> Use <a href="ntqstring.html#arg">TQString::arg</a>() for Dynamic Text
+<p> <h3> Use <a href="tqstring.html#arg">TQString::arg</a>() for Dynamic Text
 </h3>
 <a name="1-4"></a><p> The TQString::arg() functions offer a simple means for substituting
 arguments:
 <pre>
     void FileCopier::showProgress( int done, int total,
-                                   const <a href="ntqstring.html">TQString</a>&amp; current_file )
+                                   const <a href="tqstring.html">TQString</a>&amp; current_file )
     {
         label.setText( tr("%1 of %2 files copied.\nCopying: %3")
                         .arg(done)
@@ -286,11 +286,11 @@ arguments:
 can easily be achieved by changing the order of the % arguments. For
 example:
 <pre>
-    <a href="ntqstring.html">TQString</a> s1 = "%1 of %2 files copied. Copying: %3";
-    <a href="ntqstring.html">TQString</a> s2 = "Kopierer nu %3. Av totalt %2 filer er %1 kopiert.";
+    <a href="tqstring.html">TQString</a> s1 = "%1 of %2 files copied. Copying: %3";
+    <a href="tqstring.html">TQString</a> s2 = "Kopierer nu %3. Av totalt %2 filer er %1 kopiert.";
 
-    <a href="ntqapplication.html#qDebug">tqDebug</a>( s1.<a href="ntqstring.html#arg">arg</a>(5).arg(10).arg("somefile.txt").ascii() );
-    <a href="ntqapplication.html#qDebug">tqDebug</a>( s2.<a href="ntqstring.html#arg">arg</a>(5).arg(10).arg("somefile.txt").ascii() );
+    <a href="ntqapplication.html#qDebug">tqDebug</a>( s1.<a href="tqstring.html#arg">arg</a>(5).arg(10).arg("somefile.txt").ascii() );
+    <a href="ntqapplication.html#qDebug">tqDebug</a>( s2.<a href="tqstring.html#arg">arg</a>(5).arg(10).arg("somefile.txt").ascii() );
 </pre>
  
 <p> produces the correct output in English and Norwegian:
@@ -400,7 +400,7 @@ Cyrillic KOI8-R locale (the de-facto standard locale in Russia) might
 need to output Cyrillic in the ISO 8859-5 encoding. Code for this
 would be:
 <p> <pre>
-    <a href="ntqstring.html">TQString</a> string = ...; // some Unicode text
+    <a href="tqstring.html">TQString</a> string = ...; // some Unicode text
 
     <a href="ntqtextcodec.html">TQTextCodec</a>* codec = TQTextCodec::<a href="ntqtextcodec.html#codecForName">codecForName</a>( "ISO 8859-5" );
     <a href="ntqcstring.html">TQCString</a> encoded_string = codec-&gt;<a href="ntqtextcodec.html#fromUnicode">fromUnicode</a>( string );
@@ -409,20 +409,20 @@ would be:
 </pre>
  
 <p> For converting Unicode to local 8-bit encodings, a shortcut is
-available: the <a href="ntqstring.html#local8Bit">local8Bit</a>() method
-of <a href="ntqstring.html">TQString</a> returns such 8-bit data. Another useful shortcut is the
-<a href="ntqstring.html#utf8">utf8</a>() method, which returns text in the
+available: the <a href="tqstring.html#local8Bit">local8Bit</a>() method
+of <a href="tqstring.html">TQString</a> returns such 8-bit data. Another useful shortcut is the
+<a href="tqstring.html#utf8">utf8</a>() method, which returns text in the
 8-bit UTF-8 encoding: this perfectly preserves Unicode information
 while looking like plain US-ASCII if the text is wholly US-ASCII.
-<p> For converting the other way, there are the <a href="ntqstring.html#fromUtf8">TQString::fromUtf8</a>() and
-<a href="ntqstring.html#fromLocal8Bit">TQString::fromLocal8Bit</a>() convenience functions, or the general code,
+<p> For converting the other way, there are the <a href="tqstring.html#fromUtf8">TQString::fromUtf8</a>() and
+<a href="tqstring.html#fromLocal8Bit">TQString::fromLocal8Bit</a>() convenience functions, or the general code,
 demonstrated by this conversion from ISO 8859-5 Cyrillic to Unicode
 conversion:
 <p> <pre>
     <a href="ntqcstring.html">TQCString</a> encoded_string = ...; // Some ISO 8859-5 encoded text.
 
     <a href="ntqtextcodec.html">TQTextCodec</a>* codec = TQTextCodec::<a href="ntqtextcodec.html#codecForName">codecForName</a>("ISO 8859-5");
-    <a href="ntqstring.html">TQString</a> string = codec-&gt;<a href="ntqtextcodec.html#toUnicode">toUnicode</a>(encoded_string);
+    <a href="tqstring.html">TQString</a> string = codec-&gt;<a href="ntqtextcodec.html#toUnicode">toUnicode</a>(encoded_string);
 
     ...; // Use string in all of TQt's TQString operations.
 </pre>