Automated update from Qt3

1 files changed, 6 insertions, 6 deletions

diff --git a/doc/man/man3/tqchar.3qt b/doc/man/man3/tqchar.3qt
index 0aa39faca..f91af9ef5 100644
--- a/doc/man/man3/tqchar.3qt
+++ b/doc/man/man3/tqchar.3qt
@@ -9,7 +9,7 @@
 .SH NAME
 QChar \- Lightweight Unicode character
 .SH SYNOPSIS
-Almost all the functions in this class are reentrant when Qt is built with thread support. The exception is \fBdecomposition\fR(). </p>
+Almost all the functions in this class are reentrant when TQt is built with thread support. The exception is \fBdecomposition\fR(). </p>
 .PP
 \fC#include <ntqstring.h>\fR
 .PP
@@ -215,7 +215,7 @@ QChar further provides direction(), which indicates the "natural" writing direct
 .PP
 Composed Unicode characters (like &aring;) can be converted to decomposed Unicode ("a" followed by "ring above") by using decomposition().
 .PP
-In Unicode, comparison is not necessarily possible and case conversion is very difficult at best. Unicode, covering the" entire" world, also includes most of the world's case and sorting problems. Qt tries, but not very hard: operator==() and friends will do comparison based purely on the numeric Unicode value (code point) of the characters, and upper() and lower() will do case changes when the character has a well-defined upper/lower-case equivalent. There is no provision for locale-dependent case folding rules or comparison; these functions are meant to be fast so they can be used unambiguously in data structures. (See QString::localeAwareCompare() though.)
+In Unicode, comparison is not necessarily possible and case conversion is very difficult at best. Unicode, covering the" entire" world, also includes most of the world's case and sorting problems. TQt tries, but not very hard: operator==() and friends will do comparison based purely on the numeric Unicode value (code point) of the characters, and upper() and lower() will do case changes when the character has a well-defined upper/lower-case equivalent. There is no provision for locale-dependent case folding rules or comparison; these functions are meant to be fast so they can be used unambiguously in data structures. (See QString::localeAwareCompare() though.)
 .PP
 The conversion functions include unicode() (to a scalar), latin1() (to scalar, but converts all non-Latin-1 characters to 0), row() (gives the Unicode row), cell() (gives the Unicode cell), digitValue() (gives the integer value of any of the numerous digit characters), and a host of constructors.
 .PP
@@ -292,7 +292,7 @@ The following categories are informative in Unicode:
 .PP
 There are two categories that are specific to Qt:
 .TP
-\fCQChar::NoCategory\fR - used when Qt is dazed and confused and cannot make sense of anything.
+\fCQChar::NoCategory\fR - used when TQt is dazed and confused and cannot make sense of anything.
 .TP
 \fCQChar::Punctuation_Dask\fR - old typo alias for Punctuation_Dash
 .SH "QChar::CombiningClass"
@@ -333,7 +333,7 @@ Returns the cell (least significant byte) of the Unicode character.
 .SH "unsigned char QChar::combiningClass () const"
 Returns the combining class for the character as defined in the Unicode standard. This is mainly useful as a positioning hint for marks attached to a base character.
 .PP
-The Qt text rendering engine uses this information to correctly position non spacing marks around a base character.
+The TQt text rendering engine uses this information to correctly position non spacing marks around a base character.
 .SH "const QString & QChar::decomposition () const"
 \fBWarning:\fR This function is \fInot\fR reentrant.</p>
 .PP
@@ -478,8 +478,8 @@ If you find a bug in Qt, please report it as described in
 .BR http://doc.trolltech.com/bughowto.html .
 Good bug reports help us to help you. Thank you.
 .P
-The definitive Qt documentation is provided in HTML format; it is
-located at $QTDIR/doc/html and can be read using Qt Assistant or with
+The definitive TQt documentation is provided in HTML format; it is
+located at $QTDIR/doc/html and can be read using TQt Assistant or with
 a web browser. This man page is provided as a convenience for those
 users who prefer man pages, although this format is not officially
 supported by Trolltech.