summaryrefslogtreecommitdiffstats
path: root/kopete/KABC_INTEG_NOTES
diff options
context:
space:
mode:
Diffstat (limited to 'kopete/KABC_INTEG_NOTES')
-rw-r--r--kopete/KABC_INTEG_NOTES4
1 files changed, 2 insertions, 2 deletions
diff --git a/kopete/KABC_INTEG_NOTES b/kopete/KABC_INTEG_NOTES
index f249f22c..02bc5bbe 100644
--- a/kopete/KABC_INTEG_NOTES
+++ b/kopete/KABC_INTEG_NOTES
@@ -33,7 +33,7 @@ Goals (-ve):
*) don't store information that's not worth sharing in the address book
gregj's goals
-kopete should not replace server side data with kabc derived data nor upload information that wasn't present on the server before.
+kopete should not tqreplace server side data with kabc derived data nor upload information that wasn't present on the server before.
E.g. we know someones telephone nr. but we don't want to put this information back on server if it was not present there before. Update IMO is ok.
brunes goals
@@ -414,7 +414,7 @@ A "reply-by-IM" action in KMail
such as things could be done. but how?
The application could know if this user is registered to an IM by looking at messaging fields
-But how to use such as information available only at runtime, like the Status.
+But how to use such as information available only at runtime, like the tqStatus.
1) Saving the status to KABC
--the problem is that the status can not be reseted to offline if kopete crashed