author | zautrix <zautrix> | 2004-10-09 02:17:06 (UTC) |
---|---|---|
committer | zautrix <zautrix> | 2004-10-09 02:17:06 (UTC) |
commit | c2165f4e14bc2f7ab2ef19f5c35497dde5e87a0d (patch) (unidiff) | |
tree | b83f7cfe5d4bb681b756fe95446e5e3fc193bc36 /bin | |
parent | 07fdef2c2ea1153d39d7114b3d5bd4abc4f4c861 (diff) | |
download | kdepimpi-c2165f4e14bc2f7ab2ef19f5c35497dde5e87a0d.zip kdepimpi-c2165f4e14bc2f7ab2ef19f5c35497dde5e87a0d.tar.gz kdepimpi-c2165f4e14bc2f7ab2ef19f5c35497dde5e87a0d.tar.bz2 |
import ir fixes
-rw-r--r-- | bin/kdepim/korganizer/kopiWhatsNew.txt | 8 |
1 files changed, 7 insertions, 1 deletions
diff --git a/bin/kdepim/korganizer/kopiWhatsNew.txt b/bin/kdepim/korganizer/kopiWhatsNew.txt index eea860c..3f95dcf 100644 --- a/bin/kdepim/korganizer/kopiWhatsNew.txt +++ b/bin/kdepim/korganizer/kopiWhatsNew.txt | |||
@@ -5,29 +5,35 @@ and KDE-Pim/Pi | |||
5 | 5 | ||
6 | KO/Pi - KA/Pi on Windows: | 6 | KO/Pi - KA/Pi on Windows: |
7 | Now a directory can be defined by the user, where the | 7 | Now a directory can be defined by the user, where the |
8 | application/config data should be saved. | 8 | application/config data should be saved. |
9 | Define your desired path in the evironment variable | 9 | Define your desired path in the evironment variable |
10 | MICROKDEHOME | 10 | MICROKDEHOME |
11 | before starting KO/Pi or KA/Pi. | 11 | before starting KO/Pi or KA/Pi. |
12 | 12 | ||
13 | An easy Kx/Pi to Kx/Pi syncing is now possible | 13 | An easy Kx/Pi to Kx/Pi syncing is now possible |
14 | (it is called Pi-Sync) via network. | 14 | (it is called Pi-Sync) via network. |
15 | Please look at the Sync Howto. | 15 | Please look at the Sync Howto. |
16 | 16 | ||
17 | Exporting of data to mobile phones is now possible. | 17 | Exporting of calendar data and contacts to mobile phones is now possible. |
18 | The SyncHowto is updated with information howto | 18 | The SyncHowto is updated with information howto |
19 | access/sync mobile phones. | 19 | access/sync mobile phones. |
20 | Please look at the Sync Howto. | 20 | Please look at the Sync Howto. |
21 | 21 | ||
22 | Now KO/Pi and KA/Pi on the Zaurus can receive data via infrared directly. | ||
23 | Please disable Fastload for the original contact/calendar applications | ||
24 | and close them. | ||
25 | KO/Pi and KA/Pi must be running in order to receive the data. | ||
26 | (KO/Pi and KA/Pi are always running if Fastload for them is enabled!) | ||
27 | |||
22 | 28 | ||
23 | ********** VERSION 1.9.6 ************ | 29 | ********** VERSION 1.9.6 ************ |
24 | 30 | ||
25 | Changes in the external application communication on the Zaurus | 31 | Changes in the external application communication on the Zaurus |
26 | in order to use less RAM when the apps are running. | 32 | in order to use less RAM when the apps are running. |
27 | First syncing of addressbooks (KA/Pi) is possible. | 33 | First syncing of addressbooks (KA/Pi) is possible. |
28 | 34 | ||
29 | 35 | ||
30 | ********** VERSION 1.9.5a ************ | 36 | ********** VERSION 1.9.5a ************ |
31 | 37 | ||
32 | Fixed a bug in KO/Pi in the SharpDTM sync of version 1.9.5. | 38 | Fixed a bug in KO/Pi in the SharpDTM sync of version 1.9.5. |
33 | Fixed some small bugs. | 39 | Fixed some small bugs. |