Moved kpilot from kdepim to applications, as the core Trinity libraries should not contain hardware-dependent software

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

1 files changed, 9 insertions, 9 deletions

diff --git a/mimelib/doc/field.html b/mimelib/doc/field.html
index 19736f271..1a4a74b97 100644
--- a/mimelib/doc/field.html
+++ b/mimelib/doc/field.html
@@ -65,18 +65,18 @@ protected:
 </H2>
 <P>
 <B><TT>DwField</TT></B> represents a header field as described in RFC-822.
-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 contains
+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
+<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><A HREF="headers.html">DwHeaders</A></TT></B> object that contains
-it. The child node is the <B><TT>DwFieldBody</TT></B> object it contains.
+<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>
 To get and set the field name, use the member functions
 <B><TT>FieldNameStr()</TT></B> and <B><TT>SetFieldNameStr()</TT></B>. To
@@ -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> contains member functions for adding
+<B><TT>DwHeaders</TT></B> tqcontains member functions for adding
 <B><TT>DwField</TT></B> objects to its list, this function should be avoided
 for most applications.
 <P>
@@ -234,7 +234,7 @@ The static member function <B><TT>CreateFieldBody()</TT></B> is called from
 the <B><TT>Parse()</TT></B> member function and is responsible for creating
 a <B><TT>DwFieldBody</TT></B> object for this particular field. A typical
 scenario might go as follows: This member function examines the field name
-for this field, finds that it contains "To", creates a
+for this field, finds that it tqcontains "To", creates a
 <B><TT>DwAddressList</TT></B> object to contain the field body, calls the
 <B><TT>Parse()</TT></B> member function for the
 <B><TT>DwAddressList</TT></B>, and sets the <B><TT>DwAddressList</TT></B>