From 0cf411b09cf5d8970b873a338a69eae98d5ce5d8 Mon Sep 17 00:00:00 2001 From: Michele Calgaro Date: Sat, 8 Jun 2024 12:56:43 +0900 Subject: Rename text nt* related files to equivalent tq* Signed-off-by: Michele Calgaro --- doc/html/unicode.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'doc/html/unicode.html') diff --git a/doc/html/unicode.html b/doc/html/unicode.html index 5de9d2d46..075e04862 100644 --- a/doc/html/unicode.html +++ b/doc/html/unicode.html @@ -63,7 +63,7 @@ update and

In TQt, and in most applications that use TQt, most or all user-visible strings are stored using Unicode. TQt provides:

To fully benefit from Unicode, we recommend using TQString for storing all user-visible strings, and performing all text file I/O using -TQTextStream. Use TQKeyEvent::text() for keyboard input in any custom +TQTextStream. Use TQKeyEvent::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. @@ -96,7 +96,7 @@ translation support, like this:

tr() (simplifying somewhat) maps from const char * to a Unicode string, and uses installable TQTranslator objects to do the mapping. -

TQt provides a number of built-in TQTextCodec classes, that is, +

TQt provides a number of built-in 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. -- cgit v1.2.3