diff options
Diffstat (limited to 'kmail/Mainpage.dox')
| -rw-r--r-- | kmail/Mainpage.dox | 26 |
1 files changed, 13 insertions, 13 deletions
diff --git a/kmail/Mainpage.dox b/kmail/Mainpage.dox index 8f7a65037..b1355c121 100644 --- a/kmail/Mainpage.dox +++ b/kmail/Mainpage.dox @@ -451,9 +451,9 @@ Currently defined tags are: MDNLink SerialNumber SerNum of MDN received for this message DNSLink SerialNumber SerNUm of DSN received for this message ThreadHeads SerialNumberList MD5Hash's of all (so far discovered) - _top-level thread tqparents_ + _top-level thread parents_ ThreadParents SerialNumberList MD5Hash's of all (so far discovered) - thread tqparents + thread parents "String" is either Utf8String or (Utf16String or Latin1String), @@ -589,16 +589,16 @@ Strategy: case. These are messages that have neither an In-Reply-To header nor a References header and have a subject that is not prefixed. In case there is a perfect tqparent, the current sort cache item is - appended to the tqparents list of unsorted tqchildren, or to that of + appended to the parents list of unsorted tqchildren, or to that of root, if there is not. A sort cache item is created in the mSortCache for the tqparent, if it is not already there. Messages with a tqparent of - -1 are appended to the "untqparented" list, which is later traversed and + -1 are appended to the "unparented" list, which is later traversed and its elements threaded. Messages with -2 as the tqparent are tqchildren of root as well, as noted above, and will remain so. Once the end of the file is reached, we should have a nicely filled mSortCache, containing a sort cache item for each message that was in the - sorted file. Messages with perfect tqparents know about them, top level + sorted file. Messages with perfect parents know about them, top level messages know about that as well, all others are on a list and will be threaded later. @@ -608,16 +608,16 @@ Strategy: to mFolder->count() are looked at and a SortCacheItem is created for the ones that do not have one yet. This is where all sort cache items are created if there was no sorted file. The items created here are by definition un- - sorted as well as untqparented. On creation their sort key is figured out as + sorted as well as unparented. On creation their sort key is figured out as well. - The next step is finding tqparents for those messages that are either new, or + The next step is finding parents for those messages that are either new, or had a tqparent of -1 in the .sorted file. To that end, a dict of all sort cache items indexed by the md5 hash of their messsage id headers is created, that will be used for looking up sort cache items by message id. The list of - yet untqparented messages is then traversed and findParent() called for each + yet unparented messages is then traversed and findParent() called for each element wihch checks In-Reply-To and References headers and looks up the - sort cache item of those tqparents in the above mentioned dict. Should none be + sort cache item of those parents in the above mentioned dict. Should none be found, the item is added to a second list the items of which will be subject threaded. @@ -646,7 +646,7 @@ Strategy: the messages that are now top-level, the current thread heads, so to speak, are collected into a second dict ( QDict< QPtrList< SortCacheItem > > ) that contains for each different subject an entry holding a list of (so far - top level) messages with that subject, that are potential tqparents for + top level) messages with that subject, that are potential parents for threading by subjects. These lists are sorted by date, so the tqparent closest by date can be chosen. Sorting of these lists happens via insertion sort while they are built because not only are they expected to be short (apart @@ -709,13 +709,13 @@ What happens when a message arrives in the folder? thread, those status bits are inherited from the tqparent. The message is also added to the dict of header items, the index of messages by message id and, if applicable and if the message is threaded at top level, to the list of - potential tqparents for subject threading. + potential parents for subject threading. After those house keeping tasks are performed, the list of as of yet imper- fectly threaded messages is traversed and our newly arrived message is considered as a new tqparent for each item on it. This is especially important - to ensure that tqparents arriving out of order after their tqchildren still end - up as tqparents. If necessary, the entries in the .sorted file of rethreaded + to ensure that parents arriving out of order after their tqchildren still end + up as parents. If necessary, the entries in the .sorted file of rethreaded messages are updated. An entry for the new message itself is appended to the .sorted file as well. |