summaryrefslogtreecommitdiffabout
Unidiff
Diffstat (more/less context) (ignore whitespace changes)
-rw-r--r--bin/kdepim/korganizer/howtoSYNC.txt2
1 files changed, 2 insertions, 0 deletions
diff --git a/bin/kdepim/korganizer/howtoSYNC.txt b/bin/kdepim/korganizer/howtoSYNC.txt
index ad765d3..d3046de 100644
--- a/bin/kdepim/korganizer/howtoSYNC.txt
+++ b/bin/kdepim/korganizer/howtoSYNC.txt
@@ -280,32 +280,34 @@ b) Pi-Sync (direct Kx/Pi to Kx/Pi sync)
280 Now you can syncronize your local device easily with your 280 Now you can syncronize your local device easily with your
281 remote device. This works well for all platforms KO/Pi is 281 remote device. This works well for all platforms KO/Pi is
282 running on, e.g. syncing a KO/Pi on Zaurus with KO/Pi on Windows 282 running on, e.g. syncing a KO/Pi on Zaurus with KO/Pi on Windows
283 is now very easy. 283 is now very easy.
284 284
285c) Remote file 285c) Remote file
286 Syncing with the profile kind "Remote file" is performed in three steps: 286 Syncing with the profile kind "Remote file" is performed in three steps:
287 i) download the remote file to your local machine to a temp file 287 i) download the remote file to your local machine to a temp file
288 ii) sync with this temp file 288 ii) sync with this temp file
289 iii) upload the synced file to the remote device 289 iii) upload the synced file to the remote device
290 290
291 The down-/uploading if i) and iii) is done via a command line command. 291 The down-/uploading if i) and iii) is done via a command line command.
292 Please specify the download/upload command ( like scp, ftp, ...) and the 292 Please specify the download/upload command ( like scp, ftp, ...) and the
293 file name of the temp file in the corresponding fields. 293 file name of the temp file in the corresponding fields.
294 294
295d) Mobile device (cell phone) 295d) Mobile device (cell phone)
296 Note: On the Zaurus you have to install the kammu_xxx_arm.ipk package
297 to be able to access mobile phones.
296 We mention here only KO/Pi, but the same is valid for KA/Pi. 298 We mention here only KO/Pi, but the same is valid for KA/Pi.
297 Note: 299 Note:
298 It is only possible to sync a mobile phone with one particular device 300 It is only possible to sync a mobile phone with one particular device
299 running KO/Pi. If you want to be able to write data of more than one device 301 running KO/Pi. If you want to be able to write data of more than one device
300 to the mobile phone (e.g. from your Zaurus and from your Windows Laptop) 302 to the mobile phone (e.g. from your Zaurus and from your Windows Laptop)
301 do not sync with the mobile phone at all, but use the 303 do not sync with the mobile phone at all, but use the
302 "Export to phone" functionality from the different devices. 304 "Export to phone" functionality from the different devices.
303 Using "Export to phone" makes it not possible to get back data from the 305 Using "Export to phone" makes it not possible to get back data from the
304 phone, if it was changed there, of course. 306 phone, if it was changed there, of course.
305 If you sync with the phone, do not use "Export to phone" from any device. 307 If you sync with the phone, do not use "Export to phone" from any device.
306 (And do not sync, as mentioned above, from any other device with that phone). 308 (And do not sync, as mentioned above, from any other device with that phone).
307 It would delete the needed information for syncing with that phone! 309 It would delete the needed information for syncing with that phone!
308 310
309 We are using Gammu (Version: 0.98.9) ( http://freshmeat.net/projects/gammu/ ) 311 We are using Gammu (Version: 0.98.9) ( http://freshmeat.net/projects/gammu/ )
310 for accessing the phones. 312 for accessing the phones.
311 Note: You cannot use the original Gammu for syncing KDE-Pim/Pi, because 313 Note: You cannot use the original Gammu for syncing KDE-Pim/Pi, because