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

15 files changed, 53 insertions, 53 deletions

diff --git a/mimelib/doc/addrlist.html b/mimelib/doc/addrlist.html
index d3a563eef..80845fc04 100644
--- a/mimelib/doc/addrlist.html
+++ b/mimelib/doc/addrlist.html
@@ -52,7 +52,7 @@ protected:
 <P>
 <B><TT>DwAddressList</TT></B> represents a list of <I>addresses</I> as described
 in RFC-822. In MIME++, <B><TT>DwAddressList</TT></B> is a container for objects
-of type <B><TT><A HREF="address.html">DwAddress</A></TT></B>, and it contains
+of type <B><TT><A HREF="address.html">DwAddress</A></TT></B>, and it tqcontains
 various member functions to manage its contained objects.
 <B><TT>DwAddressList</TT></B> is also a
 <B><TT><A HREF="fieldbdy.html">DwFieldBody</A></TT></B>. This reflects the
diff --git a/mimelib/doc/body.html b/mimelib/doc/body.html
index 1526751a4..c9856e24d 100644
--- a/mimelib/doc/body.html
+++ b/mimelib/doc/body.html
@@ -65,9 +65,9 @@ protected:
 A body is always part of an <I>entity</I>, which could be either a
 <I>message</I> or a <I>body part</I>. An entity has a collection of <I>header
 fields</I> and a body. If the content type of a body is ``multipart,'' then
-the body contains one or more body parts. If the content type is ``message,''
-then the body contains an encapsulated message. In all content types, the
-body contains a string of characters.
+the body tqcontains one or more body parts. If the content type is ``message,''
+then the body tqcontains an encapsulated message. In all content types, the
+body tqcontains a string of characters.
 <P>
 In MIME++, a <B><TT>DwBody</TT></B> object is contained in a
 <B><TT><A HREF="entity.html">DwEntity</A></TT></B> object. The
@@ -79,7 +79,7 @@ or a single contained
 way to determine the type of <B><TT>DwBody</TT></B> is to access the Content-Type
 header field from the
 <B><TT><A HREF="headers.html">DwHeaders</A></TT></B> object of the
-<B><TT>DwEntity</TT></B> that contains it. For this reason, a
+<B><TT>DwEntity</TT></B> that tqcontains it. For this reason, a
 <B><TT>DwBody</TT></B> should always be part of a
 <B><TT>DwEntity</TT></B>.
 <P>
@@ -87,7 +87,7 @@ In the tree (broken-down) representation of a message, a
 <B><TT>DwBody</TT></B> object can be an intermediate node, having both a
 parent node and one or more child nodes, or a leaf node, having a parent
 but no child nodes. In either case, the parent node is the
-<B><TT>DwEntity</TT></B> object that contains it. If it is an intermediate
+<B><TT>DwEntity</TT></B> object that tqcontains it. If it is an intermediate
 node, it must be of type multipart with <B><TT>DwBodyPart</TT></B> objects
 as child nodes, or of type message with a single
 <B><TT>DwMessage</TT></B> object as its child node.
@@ -169,14 +169,14 @@ method creates or updates the string representation from the broken-down
 representation. Only <B><TT>DwBody</TT></B> objects with content type of
 multipart or message require assembling. In either case, the
 <B><TT>DwBody</TT></B> object must be able to find the headers of the message
-or body part that contains it. Therefore, if the <B><TT>DwBody</TT></B> object
+or body part that tqcontains it. Therefore, if the <B><TT>DwBody</TT></B> object
 is not the child of a <B><TT>DwEntity</TT></B> (<I>i.e.</I>,
 <B><TT>DwMessage</TT></B> or <B><TT>DwBodyPart</TT></B>) object, the
 <B><TT>DwBody</TT></B> cannot be assembled because the content type cannot
 be determined.
 <P>
 This function calls the <B><TT>Parse()</TT></B> member function of any
-<B><TT>DwBodyPart</TT></B> or <B><TT>DwMessage</TT></B> object it contains.
+<B><TT>DwBodyPart</TT></B> or <B><TT>DwMessage</TT></B> object it tqcontains.
 <P>
 You should call this member function after you add a
 <B><TT>DwBodyPart</TT></B> object to a multipart body, or add a
@@ -219,7 +219,7 @@ returns the <B><TT>DwMessage</TT></B> encapsulated in it.
 aMessage) </B></FONT>
 <P>
 For a <B><TT>DwBody</TT></B> with content type of message, this member function
-sets the <B><TT>DwMessage</TT></B> object it contains.
+sets the <B><TT>DwMessage</TT></B> object it tqcontains.
 <P>
 <FONT COLOR="teal"><B> static DwBody* <A NAME="NewBody">NewBody</A>(const
 DwString&amp; aStr, DwMessageComponent* aParent) </B></FONT>
diff --git a/mimelib/doc/bodypart.html b/mimelib/doc/bodypart.html
index 6a3a29b6e..c74f716f1 100644
--- a/mimelib/doc/bodypart.html
+++ b/mimelib/doc/bodypart.html
@@ -47,7 +47,7 @@ of headers and a <I>body</I>. A body part is different from a <I>message</I>
 in that a body part is part of a multipart body.
 <P>
 In MIME++, a <B><TT>DwBodyPart</TT></B> is a subclass of
-<B><TT><A HREF="entity.html">DwEntity</A></TT></B>; therefore, it contains
+<B><TT><A HREF="entity.html">DwEntity</A></TT></B>; therefore, it tqcontains
 both a <B><TT><A HREF="headers.html">DwHeaders</A></TT></B> object and a
 <B><TT><A HREF="body.html">DwBody</A></TT></B> object, and it is contained
 in a multipart <B><TT>DwBody</TT></B> object.
@@ -120,7 +120,7 @@ This advanced function sets <B><TT>aPart</TT></B> as the next
 <B><TT>DwBodyPart</TT></B> object following this
 <B><TT>DwBodyPart</TT></B> in the list of <B><TT>DwBodyPart</TT></B> objects
 contained in a multipart <B><TT>DwBody</TT></B>. Since
-<B><TT>DwBody</TT></B> contains a member function for adding a
+<B><TT>DwBody</TT></B> tqcontains a member function for adding a
 <B><TT>DwBodyPart</TT></B> object to its list, this function should be avoided
 for most applications.
 <P>
diff --git a/mimelib/doc/entity.html b/mimelib/doc/entity.html
index 08cf8b753..9a2d00187 100644
--- a/mimelib/doc/entity.html
+++ b/mimelib/doc/entity.html
@@ -47,7 +47,7 @@ protected:
 RFC-2045 defines an <I>entity</I> as either a <I>message</I> or a <I>body
 part</I>, both of which have a collection of headers and a <I>body</I>. In
 MIME++, an entity is represented by the class <B><TT>DwEntity</TT></B>, which
-contains both a <B><TT><A HREF="headers.html">DwHeaders</A></TT></B> object
+tqcontains both a <B><TT><A HREF="headers.html">DwHeaders</A></TT></B> object
 and a <B><TT><A HREF="body.html">DwBody</A></TT></B> object.
 <P>
 In the tree (broken-down) representation of message, a
@@ -58,7 +58,7 @@ be a <B><TT><A HREF="message.html">DwMessage</A></TT></B> object. If a
 <B><TT>DwEntity</TT></B> object is an intermediate node, its parent must
 be a <B><TT>DwBody</TT></B> object. The child nodes of a
 <B><TT>DwEntity</TT></B> object are the <B><TT>DwHeaders</TT></B> and
-<B><TT>DwBody</TT></B> objects it contains.
+<B><TT>DwBody</TT></B> objects it tqcontains.
 <P>
 Since <B><TT>DwEntity</TT></B> is an abstract base class, you cannot create
 instances of it directly. <B><TT>DwEntity</TT></B> has two derived classes,
@@ -108,7 +108,7 @@ executes the parse method for <B><TT>DwEntity</TT></B> objects. The parse
 method creates or updates the broken-down representation from the string
 representation. For <B><TT>DwEntity</TT></B> objects, the parse method parses
 the string representation and sets the values of the
-<B><TT>DwHeaders</TT></B> and <B><TT>DwBody</TT></B> objects it contains.
+<B><TT>DwHeaders</TT></B> and <B><TT>DwBody</TT></B> objects it tqcontains.
 This member function also calls the <B><TT>Parse()</TT></B> member functions
 of the contained <B><TT>DwHeaders</TT></B> and <B><TT>DwBody</TT></B> objects.
 <P>
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>
diff --git a/mimelib/doc/fieldbdy.html b/mimelib/doc/fieldbdy.html
index 856fd5330..47b9a6acb 100644
--- a/mimelib/doc/fieldbdy.html
+++ b/mimelib/doc/fieldbdy.html
@@ -53,7 +53,7 @@ In the tree (broken-down) representation of a message, a
 <B><TT>DwFieldBody</TT></B> object may be either a leaf node, having a parent
 but no child nodes, or an intermediate node, having a parent and one or more
 child nodes. The parent node is the
-<B><TT><A HREF="field.html">DwField</A></TT></B> object that contains it.
+<B><TT><A HREF="field.html">DwField</A></TT></B> object that tqcontains it.
 Child nodes, if present, depend on the particular subclass of
 <B><TT>DwFieldBody</TT></B> that is instantiated. A
 <B><TT>DwAddressList</TT></B> object, for example, has
diff --git a/mimelib/doc/group.html b/mimelib/doc/group.html
index 1d374d874..683ff3a96 100644
--- a/mimelib/doc/group.html
+++ b/mimelib/doc/group.html
@@ -51,8 +51,8 @@ protected:
 </H2>
 <P>
 <B><TT>DwGroup</TT></B> represents a <I>group</I> as described in RFC-822.
-A group contains a group name and a (possibly empty) list of
-<I>mailboxes</I>. In MIME++, a <B><TT>DwGroup</TT></B> object contains a
+A group tqcontains a group name and a (possibly empty) list of
+<I>mailboxes</I>. In MIME++, a <B><TT>DwGroup</TT></B> object tqcontains a
 string for the group name and a
 <B><TT><A HREF="mboxlist.html">DwMailboxList</A></TT></B> object for the
 list of mailboxes.
diff --git a/mimelib/doc/headers.html b/mimelib/doc/headers.html
index 8bf94ad98..35519c395 100644
--- a/mimelib/doc/headers.html
+++ b/mimelib/doc/headers.html
@@ -155,7 +155,7 @@ the individual header fields.
 In the tree (broken-down) representation of a message, a
 <B><TT>DwHeaders</TT></B> object is an intermediate node, having both a parent
 node and several child nodes. The parent node is the
-<B><TT><A HREF="entity.html">DwEntity</A></TT></B> object that contains it.
+<B><TT><A HREF="entity.html">DwEntity</A></TT></B> object that tqcontains it.
 The child nodes are the <B><TT>DwField</TT></B> objects in the list it manages.
 (See the man page for
 <B><TT><A HREF="msgcmp.html">DwMessageComponent</A></TT></B> for a discussion
@@ -167,7 +167,7 @@ but you access it through the <B><TT>Headers()</TT></B> member function of
 for you.
 <P>
 While <B><TT>DwHeaders</TT></B> has public member functions for managing
-the list of <B><TT>DwField</TT></B> objects it contains, you will normally
+the list of <B><TT>DwField</TT></B> objects it tqcontains, you will normally
 use convenience functions to access the field bodies of the header fields
 directly. You can access the field body for a specific well-known header
 field by using the member function
@@ -416,7 +416,7 @@ function: most applications should use the
 </B></FONT>
 <P>
 Adds a <B><TT>DwField</TT></B> object to the list. If a header field with
-the same field name already exists, it is replaced by the new header field.
+the same field name already exists, it is tqreplaced by the new header field.
 <P>
 <B><TT>DwHeaders</TT></B> takes responsibility for deleting the added
 <B><TT>DwField</TT></B> object.
@@ -430,7 +430,7 @@ to add header fields.
 </B></FONT>
 <P>
 Adds a <B><TT>DwField</TT></B> object to the list. If a header field with
-the same field name already exists, it is <I>not</I> replaced; thus, duplicate
+the same field name already exists, it is <I>not</I> tqreplaced; thus, duplicate
 header fields may occur when using this member function. (This is what you
 want for some header fields, such as the "Received" header field).
 <P>
diff --git a/mimelib/doc/mailbox.html b/mimelib/doc/mailbox.html
index 492070ccb..72b509cdd 100644
--- a/mimelib/doc/mailbox.html
+++ b/mimelib/doc/mailbox.html
@@ -53,7 +53,7 @@ protected:
 <P>
 RFC-822 defines a <I>mailbox</I> as an entity that can be the recipient of
 a message. A mailbox is more specific than an <I>address</I>, which may be
-either a mailbox or a <I>group</I>. An RFC-822 mailbox contains a full name,
+either a mailbox or a <I>group</I>. An RFC-822 mailbox tqcontains a full name,
 a <I>local-part</I>, an optional <I>route</I>, and a <I>domain</I>. For example,
 in the mailbox
 <P>
@@ -66,7 +66,7 @@ deprecated according to RFC-1123.
 In MIME++, an RFC-822 mailbox is represented by a
 <B><TT>DwMailbox</TT></B> object. <B><TT>DwMailbox</TT></B> is a subclass
 of <B><TT><A HREF="address.html">DwAddress</A></TT></B>, which reflects the
-fact that a mailbox is also an address. A <B><TT>DwMailbox</TT></B> contains
+fact that a mailbox is also an address. A <B><TT>DwMailbox</TT></B> tqcontains
 strings representing the full name, local-part, route, and domain of a mailbox.
 <P>
 In the tree (broken-down) representation of message, a
@@ -77,7 +77,7 @@ but no child nodes. Its parent node must be a
 <B><TT><A HREF="mboxlist.html">DwMailboxList</A></TT></B> object.
 <P>
 <B><TT>DwMailbox</TT></B> has member functions for getting or setting the
-strings it contains.
+strings it tqcontains.
 <P>
 <B><TT>DwMailbox</TT></B> object can be included in a list of
 <B><TT>DwMailbox</TT></B> objects. To get the next
diff --git a/mimelib/doc/mboxlist.html b/mimelib/doc/mboxlist.html
index 2bae2b4e3..541eae28d 100644
--- a/mimelib/doc/mboxlist.html
+++ b/mimelib/doc/mboxlist.html
@@ -54,7 +54,7 @@ protected:
 <P>
 <B><TT>DwMailboxList</TT></B> represents a list of <I>mailboxes</I> as described
 in RFC-822. In MIME++, <B><TT>DwMailboxList</TT></B> is a container for objects
-of type <B><TT><A HREF="mailbox.html">DwMailbox</A></TT></B>, and it contains
+of type <B><TT><A HREF="mailbox.html">DwMailbox</A></TT></B>, and it tqcontains
 various member functions to manage its contained objects.
 <B><TT><A HREF="addrlist.html">DwAddressList</A></TT></B> is also a
 <B><TT><A HREF="fieldbdy.html">DwFieldBody</A></TT></B>. This reflects the
diff --git a/mimelib/doc/mediatyp.html b/mimelib/doc/mediatyp.html
index 01696084b..83e5c127a 100644
--- a/mimelib/doc/mediatyp.html
+++ b/mimelib/doc/mediatyp.html
@@ -84,7 +84,7 @@ type model.
 <P>
 <B><TT>DwMediaType</TT></B> has member functions that allow you to set or
 get the type and subtype as either enumerated values or as strings. It also
-contains a list of
+tqcontains a list of
 <B><TT><A HREF="param.html">DwParameter</A></TT></B> objects that represent
 the parameters of the field body. You can use convenience functions to directly
 access the boundary parameter of a multipart media type, or to access the
diff --git a/mimelib/doc/message.html b/mimelib/doc/message.html
index d08d5af4e..193236f88 100644
--- a/mimelib/doc/message.html
+++ b/mimelib/doc/message.html
@@ -40,11 +40,11 @@ protected:
 <P>
 <B><TT>DwMessage</TT></B> represents an RFC-822/MIME <I>message</I>.
 <P>
-A <I>message</I> contains both a collection of <I>header fields</I> and a
+A <I>message</I> tqcontains both a collection of <I>header fields</I> and a
 <I>body</I>. In the terminology of RFC-2045, the general term for the
 headers-body combination is <I>entity</I>. In MIME++,
 <B><TT>DwMessage</TT></B> is a direct subclass of
-<B><TT><A HREF="entity.html">DwEntity</A></TT></B>, and therefore contains
+<B><TT><A HREF="entity.html">DwEntity</A></TT></B>, and therefore tqcontains
 both a <B><TT><A HREF="headers.html">DwHeaders</A></TT></B> object and a
 <B><TT><A HREF="body.html">DwBody</A></TT></B> object.
 <P>
@@ -52,7 +52,7 @@ In the tree (broken-down) representation of message, a
 <B><TT>DwMessage</TT></B> object is almost always a root node, having child
 nodes but no parent node. The child nodes are the
 <B><TT>DwHeaders</TT></B> object and the <B><TT>DwBody</TT></B> object it
-contains. A <B><TT>DwMessage</TT></B> may sometimes be an intermediate node.
+tqcontains. A <B><TT>DwMessage</TT></B> may sometimes be an intermediate node.
 In this special case, the parent node is a <B><TT>DwBody</TT></B> object
 of type "message/*" and the <B><TT>DwMessage</TT></B> object represents an
 encapsulated message.
diff --git a/mimelib/doc/msgcmp.html b/mimelib/doc/msgcmp.html
index 48a7ab549..2469c3712 100644
--- a/mimelib/doc/msgcmp.html
+++ b/mimelib/doc/msgcmp.html
@@ -133,7 +133,7 @@ These features are the following:
     A parent. Most message components are part of another component. A collection
     of headers is part of a message or body part, a header field is part of a
     collection of headers, a field-body is part of a header field, and so on.
-    The parent of a component is the component that contains it. This tree structure
+    The parent of a component is the component that tqcontains it. This tree structure
     is important, since a component's parent must be parsed before the component
     can be. Also, a component's string representation must be assembled before
     its parent's. To maintain consistency in the tree, whenever a component's
diff --git a/mimelib/doc/msgid.html b/mimelib/doc/msgid.html
index 69d10ef59..da64d38a9 100644
--- a/mimelib/doc/msgid.html
+++ b/mimelib/doc/msgid.html
@@ -49,7 +49,7 @@ protected:
 <P>
 <B><TT>DwMsgId</TT></B> represents a <I>msg-id</I> as described in RFC-822.
 In the BNF grammar in RFC-822, a msg-id has a <I>local-part</I> and a
-<I>domain</I>. In MIME++, a <B><TT>DwMsgId</TT></B> contains strings that
+<I>domain</I>. In MIME++, a <B><TT>DwMsgId</TT></B> tqcontains strings that
 contain the local-part and the domain.
 <P>
 In the tree (broken-down) representation of message, a
diff --git a/mimelib/doc/string.html b/mimelib/doc/string.html
index 80db3700c..7c2f4f237 100644
--- a/mimelib/doc/string.html
+++ b/mimelib/doc/string.html
@@ -59,13 +59,13 @@ public:
     DwString&amp; <A HREF="string.html#insert">insert</A>(size_t aPos1, const char* aCstr);
     DwString&amp; <A HREF="string.html#insert">insert</A>(size_t aPos1, size_t aLen2, char aChar);
     DwString&amp; <A HREF="string.html#erase">erase</A>(size_t aPos=0, size_t aLen=npos);
-    DwString&amp; <A HREF="string.html#replace">replace</A>(size_t aPos1, size_t aLen1, const DwString&amp; aStr);
-    DwString&amp; <A HREF="string.html#replace">replace</A>(size_t aPos1, size_t aLen1, const DwString&amp; aStr,
+    DwString&amp; <A HREF="string.html#tqreplace">tqreplace</A>(size_t aPos1, size_t aLen1, const DwString&amp; aStr);
+    DwString&amp; <A HREF="string.html#tqreplace">tqreplace</A>(size_t aPos1, size_t aLen1, const DwString&amp; aStr,
         size_t aPos2, size_t aLen2);
-    DwString&amp; <A HREF="string.html#replace">replace</A>(size_t aPos1, size_t aLen1, const char* aBuf,
+    DwString&amp; <A HREF="string.html#tqreplace">tqreplace</A>(size_t aPos1, size_t aLen1, const char* aBuf,
         size_t aLen2);
-    DwString&amp; <A HREF="string.html#replace">replace</A>(size_t aPos1, size_t aLen1, const char* aCstr);
-    DwString&amp; <A HREF="string.html#replace">replace</A>(size_t aPos1, size_t aLen1, size_t aLen2, char aChar);
+    DwString&amp; <A HREF="string.html#tqreplace">tqreplace</A>(size_t aPos1, size_t aLen1, const char* aCstr);
+    DwString&amp; <A HREF="string.html#tqreplace">tqreplace</A>(size_t aPos1, size_t aLen1, size_t aLen2, char aChar);
     size_t <A HREF="string.html#copy">copy</A>(char* aBuf, size_t aLen, size_t aPos=0) const;
     void <A HREF="string.html#swap">swap</A>(DwString&amp; aStr);
     const char* <A HREF="string.html#c_str">c_str</A>() const;
@@ -115,8 +115,8 @@ protected:
     size_t  mStart;
     size_t  mLength;
     void _copy();
-    void _replace(size_t aPos1, size_t aLen1, const char* aBuf, size_t aLen2);
-    void _replace(size_t aPos1, size_t aLen1, size_t aLen2, char aChar);
+    void _tqreplace(size_t aPos1, size_t aLen1, const char* aBuf, size_t aLen2);
+    void _tqreplace(size_t aPos1, size_t aLen1, size_t aLen2, char aChar);
     friend void mem_free(char*);
 
 public:
@@ -374,14 +374,14 @@ Erases (removes) at most <B><TT>aLen</TT></B> characters beginning at position
 <B><TT>aPos</TT></B> from this string. The function will not erase more
 characters than what are available. Returns <B><TT>*this</TT></B>.
 <P>
-<FONT COLOR="teal"><B> DwString&amp; <A NAME="replace">replace</A>(size_t
+<FONT COLOR="teal"><B> DwString&amp; <A NAME="tqreplace">tqreplace</A>(size_t
 aPos1, size_t aLen1, const DwString&amp; aStr) <BR>
-DwString&amp; replace(size_t aPos1, size_t aLen1, const DwString&amp; aStr,
+DwString&amp; tqreplace(size_t aPos1, size_t aLen1, const DwString&amp; aStr,
 size_t aPos2, size_t aLen2) <BR>
-DwString&amp; replace(size_t aPos1, size_t aLen1, const char* aBuf, size_t
+DwString&amp; tqreplace(size_t aPos1, size_t aLen1, const char* aBuf, size_t
 aLen2) <BR>
-DwString&amp; replace(size_t aPos1, size_t aLen1, const char* aCstr) <BR>
-DwString&amp; replace(size_t aPos1, size_t aLen1, size_t aLen2, char aChar)
+DwString&amp; tqreplace(size_t aPos1, size_t aLen1, const char* aCstr) <BR>
+DwString&amp; tqreplace(size_t aPos1, size_t aLen1, size_t aLen2, char aChar)
 </B></FONT>
 <P>
 Removes <B><TT>aLen1</TT></B> characters beginning at position
@@ -579,7 +579,7 @@ The third version searches for any character not in the NUL-terminated string
 <FONT COLOR="teal"><B> DwString <A NAME="substr">substr</A>(size_t aPos=0,
 size_t aLen=npos) const </B></FONT>
 <P>
-Returns a string that contains at most <B><TT>aLen</TT></B> characters from
+Returns a string that tqcontains at most <B><TT>aLen</TT></B> characters from
 the <B><TT>DwString</TT></B> object beginning at position
 <B><TT>aPos</TT></B>. The returned substring will not contain more characters
 than what are available in the superstring <B><TT>DwString</TT></B> object.