From f4fae92b6768541e2952173c3d4b09040f95bf7e Mon Sep 17 00:00:00 2001 From: tpearson Date: Wed, 16 Feb 2011 20:17:18 +0000 Subject: 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 --- mimelib/doc/addrlist.html | 2 +- mimelib/doc/body.html | 16 ++++++++-------- mimelib/doc/bodypart.html | 4 ++-- mimelib/doc/entity.html | 6 +++--- mimelib/doc/field.html | 18 +++++++++--------- mimelib/doc/fieldbdy.html | 2 +- mimelib/doc/group.html | 4 ++-- mimelib/doc/headers.html | 8 ++++---- mimelib/doc/mailbox.html | 6 +++--- mimelib/doc/mboxlist.html | 2 +- mimelib/doc/mediatyp.html | 2 +- mimelib/doc/message.html | 6 +++--- mimelib/doc/msgcmp.html | 2 +- mimelib/doc/msgid.html | 2 +- mimelib/doc/string.html | 26 +++++++++++++------------- 15 files changed, 53 insertions(+), 53 deletions(-) (limited to 'mimelib/doc') 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:

DwAddressList represents a list of addresses as described in RFC-822. In MIME++, DwAddressList is a container for objects -of type DwAddress, and it contains +of type DwAddress, and it tqcontains various member functions to manage its contained objects. DwAddressList is also a DwFieldBody. 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 entity, which could be either a message or a body part. An entity has a collection of header fields 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.

In MIME++, a DwBody object is contained in a DwEntity object. The @@ -79,7 +79,7 @@ or a single contained way to determine the type of DwBody is to access the Content-Type header field from the DwHeaders object of the -DwEntity that contains it. For this reason, a +DwEntity that tqcontains it. For this reason, a DwBody should always be part of a DwEntity.

@@ -87,7 +87,7 @@ In the tree (broken-down) representation of a message, a DwBody 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 -DwEntity object that contains it. If it is an intermediate +DwEntity object that tqcontains it. If it is an intermediate node, it must be of type multipart with DwBodyPart objects as child nodes, or of type message with a single DwMessage object as its child node. @@ -169,14 +169,14 @@ method creates or updates the string representation from the broken-down representation. Only DwBody objects with content type of multipart or message require assembling. In either case, the DwBody object must be able to find the headers of the message -or body part that contains it. Therefore, if the DwBody object +or body part that tqcontains it. Therefore, if the DwBody object is not the child of a DwEntity (i.e., DwMessage or DwBodyPart) object, the DwBody cannot be assembled because the content type cannot be determined.

This function calls the Parse() member function of any -DwBodyPart or DwMessage object it contains. +DwBodyPart or DwMessage object it tqcontains.

You should call this member function after you add a DwBodyPart object to a multipart body, or add a @@ -219,7 +219,7 @@ returns the DwMessage encapsulated in it. aMessage)

For a DwBody with content type of message, this member function -sets the DwMessage object it contains. +sets the DwMessage object it tqcontains.

static DwBody* NewBody(const DwString& aStr, DwMessageComponent* aParent) 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 body. A body part is different from a message in that a body part is part of a multipart body.

In MIME++, a DwBodyPart is a subclass of -DwEntity; therefore, it contains +DwEntity; therefore, it tqcontains both a DwHeaders object and a DwBody object, and it is contained in a multipart DwBody object. @@ -120,7 +120,7 @@ This advanced function sets aPart as the next DwBodyPart object following this DwBodyPart in the list of DwBodyPart objects contained in a multipart DwBody. Since -DwBody contains a member function for adding a +DwBody tqcontains a member function for adding a DwBodyPart object to its list, this function should be avoided for most applications.

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 entity as either a message or a body part, both of which have a collection of headers and a body. In MIME++, an entity is represented by the class DwEntity, which -contains both a DwHeaders object +tqcontains both a DwHeaders object and a DwBody object.

In the tree (broken-down) representation of message, a @@ -58,7 +58,7 @@ be a DwMessage object. If a DwEntity object is an intermediate node, its parent must be a DwBody object. The child nodes of a DwEntity object are the DwHeaders and -DwBody objects it contains. +DwBody objects it tqcontains.

Since DwEntity is an abstract base class, you cannot create instances of it directly. DwEntity has two derived classes, @@ -108,7 +108,7 @@ executes the parse method for DwEntity objects. The parse method creates or updates the broken-down representation from the string representation. For DwEntity objects, the parse method parses the string representation and sets the values of the -DwHeaders and DwBody objects it contains. +DwHeaders and DwBody objects it tqcontains. This member function also calls the Parse() member functions of the contained DwHeaders and DwBody objects.

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:

DwField 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 DwField contains three elements: a -DwString that contains its field -name, a DwString that contains its field body, and a -DwFieldBody object that contains +According to RFC-822, a field tqcontains a field name and a field body. In +MIME++, a DwField tqcontains three elements: a +DwString that tqcontains its field +name, a DwString that tqcontains its field body, and a +DwFieldBody object that tqcontains a broken-down (that is, parsed) version of its field body.

In the tree (broken-down) representation of message, a DwField object is always an intermediate node, having a parent node and a single child node. The parent node is the -DwHeaders object that contains -it. The child node is the DwFieldBody object it contains. +DwHeaders object that tqcontains +it. The child node is the DwFieldBody object it tqcontains.

To get and set the field name, use the member functions FieldNameStr() and SetFieldNameStr(). To @@ -212,7 +212,7 @@ aField)

This advanced function sets aField as the next field following this field in the list of fields contained in the headers. Since -DwHeaders contains member functions for adding +DwHeaders tqcontains member functions for adding DwField objects to its list, this function should be avoided for most applications.

@@ -234,7 +234,7 @@ The static member function CreateFieldBody() is called from the Parse() member function and is responsible for creating a DwFieldBody 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 DwAddressList object to contain the field body, calls the Parse() member function for the DwAddressList, and sets the DwAddressList 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 DwFieldBody 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 -DwField object that contains it. +DwField object that tqcontains it. Child nodes, if present, depend on the particular subclass of DwFieldBody that is instantiated. A DwAddressList 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:

DwGroup represents a group as described in RFC-822. -A group contains a group name and a (possibly empty) list of -mailboxes. In MIME++, a DwGroup object contains a +A group tqcontains a group name and a (possibly empty) list of +mailboxes. In MIME++, a DwGroup object tqcontains a string for the group name and a DwMailboxList 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 DwHeaders object is an intermediate node, having both a parent node and several child nodes. The parent node is the -DwEntity object that contains it. +DwEntity object that tqcontains it. The child nodes are the DwField objects in the list it manages. (See the man page for DwMessageComponent for a discussion @@ -167,7 +167,7 @@ but you access it through the Headers() member function of for you.

While DwHeaders has public member functions for managing -the list of DwField objects it contains, you will normally +the list of DwField 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

Adds a DwField 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.

DwHeaders takes responsibility for deleting the added DwField object. @@ -430,7 +430,7 @@ to add header fields.

Adds a DwField object to the list. If a header field with -the same field name already exists, it is not replaced; thus, duplicate +the same field name already exists, it is not 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).

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:

RFC-822 defines a mailbox as an entity that can be the recipient of a message. A mailbox is more specific than an address, which may be -either a mailbox or a group. An RFC-822 mailbox contains a full name, +either a mailbox or a group. An RFC-822 mailbox tqcontains a full name, a local-part, an optional route, and a domain. For example, in the mailbox

@@ -66,7 +66,7 @@ deprecated according to RFC-1123. In MIME++, an RFC-822 mailbox is represented by a DwMailbox object. DwMailbox is a subclass of DwAddress, which reflects the -fact that a mailbox is also an address. A DwMailbox contains +fact that a mailbox is also an address. A DwMailbox tqcontains strings representing the full name, local-part, route, and domain of a mailbox.

In the tree (broken-down) representation of message, a @@ -77,7 +77,7 @@ but no child nodes. Its parent node must be a DwMailboxList object.

DwMailbox has member functions for getting or setting the -strings it contains. +strings it tqcontains.

DwMailbox object can be included in a list of DwMailbox 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:

DwMailboxList represents a list of mailboxes as described in RFC-822. In MIME++, DwMailboxList is a container for objects -of type DwMailbox, and it contains +of type DwMailbox, and it tqcontains various member functions to manage its contained objects. DwAddressList is also a DwFieldBody. 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.

DwMediaType 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 DwParameter 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:

DwMessage represents an RFC-822/MIME message.

-A message contains both a collection of header fields and a +A message tqcontains both a collection of header fields and a body. In the terminology of RFC-2045, the general term for the headers-body combination is entity. In MIME++, DwMessage is a direct subclass of -DwEntity, and therefore contains +DwEntity, and therefore tqcontains both a DwHeaders object and a DwBody object.

@@ -52,7 +52,7 @@ In the tree (broken-down) representation of message, a DwMessage object is almost always a root node, having child nodes but no parent node. The child nodes are the DwHeaders object and the DwBody object it -contains. A DwMessage may sometimes be an intermediate node. +tqcontains. A DwMessage may sometimes be an intermediate node. In this special case, the parent node is a DwBody object of type "message/*" and the DwMessage 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:

DwMsgId represents a msg-id as described in RFC-822. In the BNF grammar in RFC-822, a msg-id has a local-part and a -domain. In MIME++, a DwMsgId contains strings that +domain. In MIME++, a DwMsgId tqcontains strings that contain the local-part and the domain.

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& insert(size_t aPos1, const char* aCstr); DwString& insert(size_t aPos1, size_t aLen2, char aChar); DwString& erase(size_t aPos=0, size_t aLen=npos); - DwString& replace(size_t aPos1, size_t aLen1, const DwString& aStr); - DwString& replace(size_t aPos1, size_t aLen1, const DwString& aStr, + DwString& tqreplace(size_t aPos1, size_t aLen1, const DwString& aStr); + DwString& tqreplace(size_t aPos1, size_t aLen1, const DwString& aStr, size_t aPos2, size_t aLen2); - DwString& replace(size_t aPos1, size_t aLen1, const char* aBuf, + DwString& tqreplace(size_t aPos1, size_t aLen1, const char* aBuf, size_t aLen2); - DwString& replace(size_t aPos1, size_t aLen1, const char* aCstr); - DwString& replace(size_t aPos1, size_t aLen1, size_t aLen2, char aChar); + DwString& tqreplace(size_t aPos1, size_t aLen1, const char* aCstr); + DwString& tqreplace(size_t aPos1, size_t aLen1, size_t aLen2, char aChar); size_t copy(char* aBuf, size_t aLen, size_t aPos=0) const; void swap(DwString& aStr); const char* c_str() 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 aLen characters beginning at position aPos from this string. The function will not erase more characters than what are available. Returns *this.

- DwString& replace(size_t + DwString& tqreplace(size_t aPos1, size_t aLen1, const DwString& aStr)
-DwString& replace(size_t aPos1, size_t aLen1, const DwString& aStr, +DwString& tqreplace(size_t aPos1, size_t aLen1, const DwString& aStr, size_t aPos2, size_t aLen2)
-DwString& replace(size_t aPos1, size_t aLen1, const char* aBuf, size_t +DwString& tqreplace(size_t aPos1, size_t aLen1, const char* aBuf, size_t aLen2)
-DwString& replace(size_t aPos1, size_t aLen1, const char* aCstr)
-DwString& replace(size_t aPos1, size_t aLen1, size_t aLen2, char aChar) +DwString& tqreplace(size_t aPos1, size_t aLen1, const char* aCstr)
+DwString& tqreplace(size_t aPos1, size_t aLen1, size_t aLen2, char aChar)

Removes aLen1 characters beginning at position @@ -579,7 +579,7 @@ The third version searches for any character not in the NUL-terminated string DwString substr(size_t aPos=0, size_t aLen=npos) const

-Returns a string that contains at most aLen characters from +Returns a string that tqcontains at most aLen characters from the DwString object beginning at position aPos. The returned substring will not contain more characters than what are available in the superstring DwString object. -- cgit v1.2.1