summaryrefslogtreecommitdiffstats
path: root/doc/html/unicode.html
diff options
context:
space:
mode:
authorMichele Calgaro <[email protected]>2024-06-06 13:44:12 +0900
committerMichele Calgaro <[email protected]>2024-06-06 13:52:29 +0900
commite6077c30d14e9d662e8843c554db86c0d366d0b6 (patch)
tree672319afee32f0316bad258c0e9a1e0dd737bd61 /doc/html/unicode.html
parent8c029298d9d3f1f84b65ac4a3a16cd1fa28d9cde (diff)
downloadtqt3-e6077c30d14e9d662e8843c554db86c0d366d0b6.tar.gz
tqt3-e6077c30d14e9d662e8843c554db86c0d366d0b6.zip
Rename str nt* related files to equivalent tq*
Signed-off-by: Michele Calgaro <[email protected]>
Diffstat (limited to 'doc/html/unicode.html')
-rw-r--r--doc/html/unicode.html8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/html/unicode.html b/doc/html/unicode.html
index 89f227e3d..5de9d2d46 100644
--- a/doc/html/unicode.html
+++ b/doc/html/unicode.html
@@ -66,7 +66,7 @@ strings are stored using Unicode. TQt provides:
<p> <li> Translation to/from legacy encodings for file I/O: see <a href="ntqtextcodec.html">TQTextCodec</a> and <a href="ntqtextstream.html">TQTextStream</a>.
<li> Translation from Input Methods and 8-bit keyboard input.
<li> Translation to legacy character sets for on-screen display.
-<li> A string class, <a href="ntqstring.html">TQString</a>, that stores Unicode characters, with
+<li> A string class, <a href="tqstring.html">TQString</a>, that stores Unicode characters, with
support for migrating from C strings including fast (cached)
translation to and from US-ASCII, and all the usual string
operations.
@@ -74,14 +74,14 @@ operations.
<li> Unicode support detection on Windows, so that TQt provides Unicode
even on Windows platforms that do not support it natively.
<p> </ul>
-<p> To fully benefit from Unicode, we recommend using <a href="ntqstring.html">TQString</a> for storing
+<p> To fully benefit from Unicode, we recommend using <a href="tqstring.html">TQString</a> for storing
all user-visible strings, and performing all text file I/O using
<a href="ntqtextstream.html">TQTextStream</a>. Use <a href="qkeyevent.html#text">TQKeyEvent::text</a>() for keyboard input in any custom
widgets you write; it does not make much difference for slow typists
in Western Europe or North America, but for fast typists or people
using special input methods using text() is beneficial.
<p> All the function arguments in TQt that may be user-visible strings, <a href="ntqlabel.html#setText">TQLabel::setText</a>() and a many others, take <tt>const TQString &amp;</tt>s.
-<a href="ntqstring.html">TQString</a> provides implicit casting from <tt>const char *</tt>
+<a href="tqstring.html">TQString</a> provides implicit casting from <tt>const char *</tt>
so that things like
<pre>
myLabel-&gt;setText( "Hello, Dolly!" );
@@ -110,7 +110,7 @@ writing, Vietnamese/VISCII is one such example.)
fast functions for mapping to and from them. For example, to open an
application's icon one might do this:
<pre>
- <a href="ntqfile.html">TQFile</a> f( TQString::<a href="ntqstring.html#fromLatin1">fromLatin1</a>("appicon.png") );
+ <a href="ntqfile.html">TQFile</a> f( TQString::<a href="tqstring.html#fromLatin1">fromLatin1</a>("appicon.png") );
</pre>
<p> Regarding output, TQt will do a best-effort conversion from