summaryrefslogtreecommitdiffstats
path: root/doc/unicode.doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc/unicode.doc')
-rw-r--r--doc/unicode.doc6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/unicode.doc b/doc/unicode.doc
index 405320d3d..461223213 100644
--- a/doc/unicode.doc
+++ b/doc/unicode.doc
@@ -90,7 +90,7 @@ strings are stored using Unicode. TQt provides:
\list
\i Translation to/from legacy encodings for file I/O: see \l
-QTextCodec and \l QTextStream.
+TQTextCodec and \l TQTextStream.
\i Translation from Input Methods and 8-bit keyboard input.
\i Translation to legacy character sets for on-screen display.
\i A string class, \l TQString, that stores Unicode characters, with
@@ -105,7 +105,7 @@ even on Windows platforms that do not support it natively.
To fully benefit from Unicode, we recommend using TQString for storing
all user-visible strings, and performing all text file I/O using
-QTextStream. Use \l QKeyEvent::text() for keyboard input in any custom
+TQTextStream. Use \l QKeyEvent::text() 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.
@@ -127,7 +127,7 @@ tr() (simplifying somewhat) maps from \c{const char *} to a
Unicode string, and uses installable \l QTranslator objects to do the
mapping.
-Qt provides a number of built-in \l QTextCodec classes, that is,
+Qt provides a number of built-in \l TQTextCodec classes, that is,
classes that know how to translate between Unicode and legacy
encodings to support programs that must talk to other programs or
read/write files in legacy file formats.