From 67e29a054cfcb1b0d2fe6b0a316cf6b3eec087b7 Mon Sep 17 00:00:00 2001 From: tpearson Date: Wed, 13 Apr 2011 00:46:47 +0000 Subject: 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 --- mimelib/doc/field.html | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) (limited to 'mimelib/doc/field.html') 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:

DwField 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 DwField tqcontains three elements: a -DwString that tqcontains its field -name, a DwString that tqcontains its field body, and a +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 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 +DwField object is always an intermediate node, having a tqparent +node and a single child node. The tqparent node is the DwHeaders object that tqcontains it. The child node is the DwFieldBody object it tqcontains.

@@ -87,7 +87,7 @@ get and set the DwFieldBody object, use

A DwField object can be included in a list of DwField objects; usually this is the list of -DwField objects maintained by its parent +DwField objects maintained by its tqparent DwHeaders object. To get the next DwField object in a list, use the member function Next().

@@ -100,16 +100,16 @@ DwField(const DwString& aStr, DwMessageComponent* aParent=0)

The first constructor is the default constructor, which sets the DwField object's field name and field body to the empty string, -set its parent to NULL, and sets its +set its tqparent to NULL, and sets its DwFieldBody object to NULL.

The second constructor is the copy constructor, which performs a deep copy -of aField. The parent of the new DwField +of aField. The tqparent of the new DwField object is set to NULL.

The third constructor copies aStr to the DwField object's string representation and sets -aParent as its parent. The virtual member function +aParent as its tqparent. The virtual member function Parse() should be called immediately after this constructor in order to parse the string representation. Unless it is NULL, aParent should point to an object of @@ -119,7 +119,7 @@ a class derived from DwHeaders. (const DwField& aField)

This is the assignment operator, which performs a deep copy of -aField. The parent node of the DwField object +aField. The tqparent node of the DwField object is not changed.

virtual void Parse() @@ -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 tqcontains member functions for adding +DwHeaders contains member functions for adding DwField objects to its list, this function should be avoided for most applications.

-- cgit v1.2.1