Initial TQt conversion

1 files changed, 4 insertions, 4 deletions

diff --git a/dcoppython/README b/dcoppython/README
index e5b8c3e8..e5ea18cd 100644
--- a/dcoppython/README
+++ b/dcoppython/README
@@ -19,13 +19,13 @@ pcop.cpp includes a header file marshal_funcs.h, which is generated from
 a data file called marshal_funcs.data by a converter script, gen_marshal_funcs.py
 
 marshal_funcs.data contains the basic code necessary to marshal and demarshal the different
-types that DCOP can handle. For example, it codes how to convert a QString for use by Python
+types that DCOP can handle. For example, it codes how to convert a TQString for use by Python
 (in this case, a Python string) and the reverse - what the user may supply in Python when
-DCOP requires a QString. In addition to the fundemental types, more complex QT classes are
-coded, such as QRect (which converts to a Python tuple ( (x1,y1), (x2,y2) ) ).
+DCOP retquires a TQString. In addition to the fundemental types, more complex QT classes are
+coded, such as TQRect (which converts to a Python tuple ( (x1,y1), (x2,y2) ) ).
 
 Documentation is auto-generated out of marshal_funcs.data, creating file marshal_funcs_doc.html,
-which details how each DCOP type (e.g. QString, QRect, int, QCStringList) is represented in Python.
+which details how each DCOP type (e.g. TQString, TQRect, int, TQCStringList) is represented in Python.
 
 In this implementation, each DCOP type is represented by a basic Python type - numeric, tuple, etc.
 There are no "QT bindings" necessary.