From 58c928d92dc975b777bd8a40bea5945a47f3570b Mon Sep 17 00:00:00 2001 From: Kjartan Maraas Date: Thu, 17 Aug 2006 13:19:54 +0000 Subject: Fix som typos svn path=/trunk/; revision=32567 --- devel-docs/misc/ref_and_id_proposition.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'devel-docs/misc') diff --git a/devel-docs/misc/ref_and_id_proposition.txt b/devel-docs/misc/ref_and_id_proposition.txt index 2127b45a57..9d790ffd8e 100644 --- a/devel-docs/misc/ref_and_id_proposition.txt +++ b/devel-docs/misc/ref_and_id_proposition.txt @@ -56,7 +56,7 @@ folder caching or message referencing if messages are referenced only by their position within their parent folder. -We thus have to find a general way to identify and retreive a message +We thus have to find a general way to identify and retrieve a message within its folder. One thing is sure, however: all folders implementation won't allow this method. Pop3 stores will always access messages using their rank on the server. MUA using Camel will thus @@ -181,7 +181,7 @@ gboolean camel_folder_uid_is_reference (CamelFolder *folder, gchar *uid) Then all usual operations on the folder act if the message was actually physically stored in this folder. For example, when the mailer uses camel_folder_get_message_by_uid onto the (v)folder, the actual -message is retreived from its physical store. +message is retrieved from its physical store. As you can see, the uid of the message within its physical parent folder is different than its uid within the (v)folder. This is because -- cgit