summaryrefslogtreecommitdiffstats
path: root/doc/unicode.doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc/unicode.doc')
-rw-r--r--doc/unicode.doc12
1 files changed, 6 insertions, 6 deletions
diff --git a/doc/unicode.doc b/doc/unicode.doc
index d4e5a273..405320d3 100644
--- a/doc/unicode.doc
+++ b/doc/unicode.doc
@@ -93,7 +93,7 @@ strings are stored using Unicode. TQt provides:
QTextCodec and \l QTextStream.
\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 QString, that stores Unicode characters, with
+\i A string class, \l TQString, 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.
@@ -103,7 +103,7 @@ even on Windows platforms that do not support it natively.
\endlist
-To fully benefit from Unicode, we recommend using QString for storing
+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
widgets you write; it does not make much difference for slow typists
@@ -111,13 +111,13 @@ in Western Europe or North America, but for fast typists or people
using special input methods using text() is beneficial.
All the function arguments in TQt that may be user-visible strings, \l
-QLabel::setText() and a many others, take \c{const QString &}s.
-\l QString provides implicit casting from \c{const char *}
+QLabel::setText() and a many others, take \c{const TQString &}s.
+\l TQString provides implicit casting from \c{const char *}
so that things like
\code
myLabel->setText( "Hello, Dolly!" );
\endcode
-will work. There is also a function, \l QObject::tr(), that provides
+will work. There is also a function, \l TQObject::tr(), that provides
translation support, like this:
\code
myLabel->setText( tr("Hello, Dolly!") );
@@ -143,7 +143,7 @@ Since US-ASCII and ISO-8859-1 are so common, there are also especially
fast functions for mapping to and from them. For example, to open an
application's icon one might do this:
\code
- QFile f( QString::fromLatin1("appicon.png") );
+ QFile f( TQString::fromLatin1("appicon.png") );
\endcode
Regarding output, TQt will do a best-effort conversion from