1 files changed, 3 insertions, 0 deletions
diff --git a/bin/kdepim/WhatsNew.txt b/bin/kdepim/WhatsNew.txt
index 06d630a..52590d8 100644
--- a/bin/kdepim/WhatsNew.txt
+++ b/bin/kdepim/WhatsNew.txt
@@ -1,73 +1,76 @@
 Info about the changes in new versions of KDE-Pim/Pi
 ********** VERSION 2.1.17 ************
 KO/Pi:
 Added option to display times in What's Next View on two lines.
 (Useful for display on the Zaurus with 240x320 screen)
 Removed "Allday" for allday events of one day duration in What's Next View.
 Added date range for allday events of more than one day duration in What's Next View.
+Fixed two problems in the data importing from Outlook:
+  Fixed the duplicated import if the summary, location or description had whitespaces at the end.
+  Fixed a problem importing certain recurrence rules.  
 ********** VERSION 2.1.16 ************
 Fixed a problem with the menu bar in KO/Pi and using the "Menu" hardware key on the Zaurus.
 Added columns for datetime in todo view: Last modified, created and last modified subtodo
 Fixed a bug in agenda view displaying recurring multiday events which are longer than two days.
 Made conflict detection up to 4 times faster.
 ********** VERSION 2.1.15 ************
 Fixed two layout problems on the Z:
 Made the with of the newly added buttons on the Quick-Todo smaller.
 Made listweek layout in 2 columns on the Z760 in portait screen and full menubar visible.
 ********** VERSION 2.1.14 ************
 Added some buttons to the KO/Pi Quick-todo line to make it possible to quickly access some todo view layout settings like display all flat/open/close and hide/show running/done.
 Added a button to add a subtodo quickly.
 Added a possibility to search for conflicting events. (In the Action menu. Keyboard shortcut "q", shift+q or ctrl +q ).
 Added an option to change the layout of the list week to column mode.
 Fixed some usability problems in pi-sync mode by adding some progress information about file transfer.
 Fixed pi-sync problems with the new multi calendar feature.
 Now pi-sync behaviour should be:
 1) Local sends file request ( as usual )
 2) Remote sends file which contains data of all enabled ( the calendar where the "eye" column is checked ) calendars.
 3) Local syncs with data, adds new entries to default calendar and sends file back ( as usual ).
   If the data which local receives contains entries which are on disabled calendars on local this entries are updated and not added as duplicates to the default calendar.
 4) Remote updates the data and adds new entries to default calendar. Readonly entries are not changed on remote.
   If the data which remote receives contains entries which are on disabled calendars on remote this entries are updated and not added as duplicates to the default calendar.
 Summary: 
 No new item ( new created after the last sync ) in a disabled calendar is propagated to the sync partner. Readonly items are synced and added/changed on the sync partner if it is not readonly on the sync partner.
 If you have different calendars on remote and local and some of them disabled you may get some "strange" bahaviour.
 Well, the syncing has become quite complicated ... you should have no problems if you enable all calendars. 
 ********** VERSION 2.1.13 ************
 Fixed a problem in KA/Pi search.
 Fixed some minor problems in KO/Pi.
 Added calendar selection possibility to the todo view popup and to the event/todo/journal editor.
 Fixed memory usage problems in KA/Pi:
 When loading data KA/Pi did load the file data twice.
 Example:
  A 600k file did consume 1200k memory during loading process.
  This is fixed, it does now consume only  600k during loading process.
 When saving data KA/Pi did consume a lot of memory for the data parsing during the save process.
 This is fixed.
 Example:
  Before saving a 600k file KA/Pi did consume 21.7 Meg of Ram.
  When saving  KA/Pi did consume 28.6 Meg of Ram. That causes a crash on the Zaurus because there was no memeory left in the system.
  Now  KA/Pi is consuming on saving the same data 22.0 Meg of Ram during the save process. 
 Note: The memory usage of KA/Pi after the data is loaded/saved has not changed.
 The saving of data may be a bit slower now.
 Fixed memory usage problems in KO/Pi:
 When KO/Pi did save the data to file, it did not release the used buffers after saving.
 The used buffer was released after saving the next time, but there was new buffer space allocated again on that save operation.
 This is fixed.
 Example:

diff --git a/bin/kdepim/WhatsNew.txt b/bin/kdepim/WhatsNew.txt index 06d630a..52590d8 100644 --- a/bin/kdepim/WhatsNew.txt +++ b/bin/kdepim/WhatsNew.txt
@@ -1,73 +1,76 @@
1	Info about the changes in new versions of KDE-Pim/Pi	1	Info about the changes in new versions of KDE-Pim/Pi
2		2
3	******** VERSION 2.1.17 **********	3	******** VERSION 2.1.17 **********
4		4
5	KO/Pi:	5	KO/Pi:
6	Added option to display times in What's Next View on two lines.	6	Added option to display times in What's Next View on two lines.
7	(Useful for display on the Zaurus with 240x320 screen)	7	(Useful for display on the Zaurus with 240x320 screen)
8	Removed "Allday" for allday events of one day duration in What's Next View.	8	Removed "Allday" for allday events of one day duration in What's Next View.
9	Added date range for allday events of more than one day duration in What's Next View.	9	Added date range for allday events of more than one day duration in What's Next View.
		10	Fixed two problems in the data importing from Outlook:
		11	Fixed the duplicated import if the summary, location or description had whitespaces at the end.
		12	Fixed a problem importing certain recurrence rules.
10		13
11	******** VERSION 2.1.16 **********	14	******** VERSION 2.1.16 **********
12		15
13	Fixed a problem with the menu bar in KO/Pi and using the "Menu" hardware key on the Zaurus.	16	Fixed a problem with the menu bar in KO/Pi and using the "Menu" hardware key on the Zaurus.
14	Added columns for datetime in todo view: Last modified, created and last modified subtodo	17	Added columns for datetime in todo view: Last modified, created and last modified subtodo
15	Fixed a bug in agenda view displaying recurring multiday events which are longer than two days.	18	Fixed a bug in agenda view displaying recurring multiday events which are longer than two days.
16	Made conflict detection up to 4 times faster.	19	Made conflict detection up to 4 times faster.
17		20
18	******** VERSION 2.1.15 **********	21	******** VERSION 2.1.15 **********
19		22
20	Fixed two layout problems on the Z:	23	Fixed two layout problems on the Z:
21	Made the with of the newly added buttons on the Quick-Todo smaller.	24	Made the with of the newly added buttons on the Quick-Todo smaller.
22	Made listweek layout in 2 columns on the Z760 in portait screen and full menubar visible.	25	Made listweek layout in 2 columns on the Z760 in portait screen and full menubar visible.
23		26
24		27
25	******** VERSION 2.1.14 **********	28	******** VERSION 2.1.14 **********
26		29
27	Added some buttons to the KO/Pi Quick-todo line to make it possible to quickly access some todo view layout settings like display all flat/open/close and hide/show running/done.	30	Added some buttons to the KO/Pi Quick-todo line to make it possible to quickly access some todo view layout settings like display all flat/open/close and hide/show running/done.
28	Added a button to add a subtodo quickly.	31	Added a button to add a subtodo quickly.
29		32
30	Added a possibility to search for conflicting events. (In the Action menu. Keyboard shortcut "q", shift+q or ctrl +q ).	33	Added a possibility to search for conflicting events. (In the Action menu. Keyboard shortcut "q", shift+q or ctrl +q ).
31	Added an option to change the layout of the list week to column mode.	34	Added an option to change the layout of the list week to column mode.
32		35
33	Fixed some usability problems in pi-sync mode by adding some progress information about file transfer.	36	Fixed some usability problems in pi-sync mode by adding some progress information about file transfer.
34		37
35	Fixed pi-sync problems with the new multi calendar feature.	38	Fixed pi-sync problems with the new multi calendar feature.
36	Now pi-sync behaviour should be:	39	Now pi-sync behaviour should be:
37	1) Local sends file request ( as usual )	40	1) Local sends file request ( as usual )
38	2) Remote sends file which contains data of all enabled ( the calendar where the "eye" column is checked ) calendars.	41	2) Remote sends file which contains data of all enabled ( the calendar where the "eye" column is checked ) calendars.
39	3) Local syncs with data, adds new entries to default calendar and sends file back ( as usual ).	42	3) Local syncs with data, adds new entries to default calendar and sends file back ( as usual ).
40	If the data which local receives contains entries which are on disabled calendars on local this entries are updated and not added as duplicates to the default calendar.	43	If the data which local receives contains entries which are on disabled calendars on local this entries are updated and not added as duplicates to the default calendar.
41	4) Remote updates the data and adds new entries to default calendar. Readonly entries are not changed on remote.	44	4) Remote updates the data and adds new entries to default calendar. Readonly entries are not changed on remote.
42	If the data which remote receives contains entries which are on disabled calendars on remote this entries are updated and not added as duplicates to the default calendar.	45	If the data which remote receives contains entries which are on disabled calendars on remote this entries are updated and not added as duplicates to the default calendar.
43		46
44	Summary:	47	Summary:
45	No new item ( new created after the last sync ) in a disabled calendar is propagated to the sync partner. Readonly items are synced and added/changed on the sync partner if it is not readonly on the sync partner.	48	No new item ( new created after the last sync ) in a disabled calendar is propagated to the sync partner. Readonly items are synced and added/changed on the sync partner if it is not readonly on the sync partner.
46	If you have different calendars on remote and local and some of them disabled you may get some "strange" bahaviour.	49	If you have different calendars on remote and local and some of them disabled you may get some "strange" bahaviour.
47	Well, the syncing has become quite complicated ... you should have no problems if you enable all calendars.	50	Well, the syncing has become quite complicated ... you should have no problems if you enable all calendars.
48		51
49	******** VERSION 2.1.13 **********	52	******** VERSION 2.1.13 **********
50		53
51	Fixed a problem in KA/Pi search.	54	Fixed a problem in KA/Pi search.
52	Fixed some minor problems in KO/Pi.	55	Fixed some minor problems in KO/Pi.
53	Added calendar selection possibility to the todo view popup and to the event/todo/journal editor.	56	Added calendar selection possibility to the todo view popup and to the event/todo/journal editor.
54		57
55	Fixed memory usage problems in KA/Pi:	58	Fixed memory usage problems in KA/Pi:
56	When loading data KA/Pi did load the file data twice.	59	When loading data KA/Pi did load the file data twice.
57	Example:	60	Example:
58	A 600k file did consume 1200k memory during loading process.	61	A 600k file did consume 1200k memory during loading process.
59	This is fixed, it does now consume only 600k during loading process.	62	This is fixed, it does now consume only 600k during loading process.
60	When saving data KA/Pi did consume a lot of memory for the data parsing during the save process.	63	When saving data KA/Pi did consume a lot of memory for the data parsing during the save process.
61	This is fixed.	64	This is fixed.
62	Example:	65	Example:
63	Before saving a 600k file KA/Pi did consume 21.7 Meg of Ram.	66	Before saving a 600k file KA/Pi did consume 21.7 Meg of Ram.
64	When saving KA/Pi did consume 28.6 Meg of Ram. That causes a crash on the Zaurus because there was no memeory left in the system.	67	When saving KA/Pi did consume 28.6 Meg of Ram. That causes a crash on the Zaurus because there was no memeory left in the system.
65	Now KA/Pi is consuming on saving the same data 22.0 Meg of Ram during the save process.	68	Now KA/Pi is consuming on saving the same data 22.0 Meg of Ram during the save process.
66	Note: The memory usage of KA/Pi after the data is loaded/saved has not changed.	69	Note: The memory usage of KA/Pi after the data is loaded/saved has not changed.
67	The saving of data may be a bit slower now.	70	The saving of data may be a bit slower now.
68		71
69	Fixed memory usage problems in KO/Pi:	72	Fixed memory usage problems in KO/Pi:
70	When KO/Pi did save the data to file, it did not release the used buffers after saving.	73	When KO/Pi did save the data to file, it did not release the used buffers after saving.
71	The used buffer was released after saving the next time, but there was new buffer space allocated again on that save operation.	74	The used buffer was released after saving the next time, but there was new buffer space allocated again on that save operation.
72	This is fixed.	75	This is fixed.
73	Example:	76	Example: