Initial conversion of kdepim to TQt

This will probably require some tweaking before it will build under Qt4,
however Qt3 builds are OK.  Any alterations this commit makes to kdepim
behaviour under Qt3 are unintentional and should be fixed.


git-svn-id: svn://anonsvn.kde.org/home/kde/branches/trinity/kdepim@1227832 283d02a7-25f6-0310-bc7c-ecb5cbfe19da

1 files changed, 12 insertions, 12 deletions

diff --git a/mimelib/doc/field.html b/mimelib/doc/field.html
index 1a4a74b97..68d4a9ed3 100644
--- a/mimelib/doc/field.html
+++ b/mimelib/doc/field.html
@@ -65,16 +65,16 @@ protected:
 </H2>
 <P>
 <B><TT>DwField</TT></B> represents a header field as described in RFC-822.
-According to RFC-822, a field tqcontains a field name and a field body. In
-MIME++, a <B><TT>DwField</TT></B> tqcontains three elements: a
-<B><TT><A HREF="string.html">DwString</A></TT></B> that tqcontains its field
-name, a <B><TT>DwString</TT></B> that tqcontains its field body, and a
+According to RFC-822, a field contains a field name and a field body. In
+MIME++, a <B><TT>DwField</TT></B> contains three elements: a
+<B><TT><A HREF="string.html">DwString</A></TT></B> that contains its field
+name, a <B><TT>DwString</TT></B> that contains its field body, and a
 <B><TT><A HREF="fieldbdy.html">DwFieldBody</A></TT></B> object that tqcontains
 a broken-down (that is, parsed) version of its field body.
 <P>
 In the tree (broken-down) representation of message, a
-<B><TT>DwField</TT></B> object is always an intermediate node, having a parent
-node and a single child node. The parent node is the
+<B><TT>DwField</TT></B> object is always an intermediate node, having a tqparent
+node and a single child node. The tqparent node is the
 <B><TT><A HREF="headers.html">DwHeaders</A></TT></B> object that tqcontains
 it. The child node is the <B><TT>DwFieldBody</TT></B> object it tqcontains.
 <P>
@@ -87,7 +87,7 @@ get and set the <B><TT>DwFieldBody</TT></B> object, use
 <P>
 A <B><TT>DwField</TT></B> object can be included in a list of
 <B><TT>DwField</TT></B> objects; usually this is the list of
-<B><TT>DwField</TT></B> objects maintained by its parent
+<B><TT>DwField</TT></B> objects maintained by its tqparent
 <B><TT>DwHeaders</TT></B> object. To get the next <B><TT>DwField</TT></B>
 object in a list, use the member function <B><TT>Next()</TT></B>.
 <H2>
@@ -100,16 +100,16 @@ DwField(const DwString&amp; aStr, DwMessageComponent* aParent=0) </B></FONT>
 <P>
 The first constructor is the default constructor, which sets the
 <B><TT>DwField</TT></B> object's field name and field body to the empty string,
-set its parent to <B><TT>NULL</TT></B>, and sets its
+set its tqparent to <B><TT>NULL</TT></B>, and sets its
 <B><TT>DwFieldBody</TT></B> object to <B><TT>NULL</TT></B>.
 <P>
 The second constructor is the copy constructor, which performs a deep copy
-of <B><TT>aField</TT></B>. The parent of the new <B><TT>DwField</TT></B>
+of <B><TT>aField</TT></B>. The tqparent of the new <B><TT>DwField</TT></B>
 object is set to <B><TT>NULL</TT></B>.
 <P>
 The third constructor copies <B><TT>aStr</TT></B> to the
 <B><TT>DwField</TT></B> object's string representation and sets
-<B><TT>aParent</TT></B> as its parent. The virtual member function
+<B><TT>aParent</TT></B> as its tqparent. The virtual member function
 <B><TT>Parse()</TT></B> should be called immediately after this constructor
 in order to parse the string representation. Unless it is
 <B><TT>NULL</TT></B>, <B><TT>aParent</TT></B> should point to an object of
@@ -119,7 +119,7 @@ a class derived from <B><TT>DwHeaders</TT></B>.
 (const DwField&amp; aField) </B></FONT>
 <P>
 This is the assignment operator, which performs a deep copy of
-<B><TT>aField</TT></B>. The parent node of the <B><TT>DwField</TT></B> object
+<B><TT>aField</TT></B>. The tqparent node of the <B><TT>DwField</TT></B> object
 is not changed.
 <P>
 <FONT COLOR="teal"><B> virtual void <A NAME="Parse">Parse</A>() </B></FONT>
@@ -212,7 +212,7 @@ aField) </B></FONT>
 <P>
 This <I>advanced</I> function sets <B><TT>aField</TT></B> as the next field
 following this field in the list of fields contained in the headers. Since
-<B><TT>DwHeaders</TT></B> tqcontains member functions for adding
+<B><TT>DwHeaders</TT></B> contains member functions for adding
 <B><TT>DwField</TT></B> objects to its list, this function should be avoided
 for most applications.
 <P>