summaryrefslogtreecommitdiffabout
path: root/bin/kdepim/korganizer/howtoSYNC.txt
Unidiff
Diffstat (limited to 'bin/kdepim/korganizer/howtoSYNC.txt') (more/less context) (ignore whitespace changes)
-rw-r--r--bin/kdepim/korganizer/howtoSYNC.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/bin/kdepim/korganizer/howtoSYNC.txt b/bin/kdepim/korganizer/howtoSYNC.txt
index c4e80f5..3cab446 100644
--- a/bin/kdepim/korganizer/howtoSYNC.txt
+++ b/bin/kdepim/korganizer/howtoSYNC.txt
@@ -287,49 +287,49 @@ b) Pi-Sync (direct Kx/Pi to Kx/Pi sync)
287 Fill in the needed values: 287 Fill in the needed values:
288 - Password for remote access: 288 - Password for remote access:
289 The password you specified on the remote device. 289 The password you specified on the remote device.
290 - Remote IP address: 290 - Remote IP address:
291 The IP address of the remote device. 291 The IP address of the remote device.
292 - Remote port number: 292 - Remote port number:
293 The port number you specified on the remote device. 293 The port number you specified on the remote device.
294 294
295 Now you can syncronize your local device easily with your 295 Now you can syncronize your local device easily with your
296 remote device. This works well for all platforms KO/Pi is 296 remote device. This works well for all platforms KO/Pi is
297 running on, e.g. syncing a KO/Pi on Zaurus with KO/Pi on Windows 297 running on, e.g. syncing a KO/Pi on Zaurus with KO/Pi on Windows
298 is now very easy. 298 is now very easy.
299 299
300c) Remote file 300c) Remote file
301 Syncing with the profile kind "Remote file" is performed in three steps: 301 Syncing with the profile kind "Remote file" is performed in three steps:
302 i) download the remote file to your local machine to a temp file 302 i) download the remote file to your local machine to a temp file
303 ii) sync with this temp file 303 ii) sync with this temp file
304 iii) upload the synced file to the remote device 304 iii) upload the synced file to the remote device
305 305
306 The down-/uploading if i) and iii) is done via a command line command. 306 The down-/uploading if i) and iii) is done via a command line command.
307 Please specify the download/upload command ( like scp, ftp, ...) and the 307 Please specify the download/upload command ( like scp, ftp, ...) and the
308 file name of the temp file in the corresponding fields. 308 file name of the temp file in the corresponding fields.
309 309
310d) Mobile device (cell phone) 310d) Mobile device (cell phone)
311 Note: On the Zaurus you have to install the kammu_xxx_arm.ipk package 311 Note: On the Zaurus you have to install the phoneaccess_xxx_arm.ipk package
312 to be able to access mobile phones. 312 to be able to access mobile phones.
313 We mention here only KO/Pi, but the same is valid for KA/Pi. 313 We mention here only KO/Pi, but the same is valid for KA/Pi.
314 Note: 314 Note:
315 It is only possible to sync a mobile phone with one particular device 315 It is only possible to sync a mobile phone with one particular device
316 running KO/Pi. If you want to be able to write data of more than one device 316 running KO/Pi. If you want to be able to write data of more than one device
317 to the mobile phone (e.g. from your Zaurus and from your Windows Laptop) 317 to the mobile phone (e.g. from your Zaurus and from your Windows Laptop)
318 do not sync with the mobile phone at all, but use the 318 do not sync with the mobile phone at all, but use the
319 "Export to phone" functionality from the different devices. 319 "Export to phone" functionality from the different devices.
320 Using "Export to phone" makes it not possible to get back data from the 320 Using "Export to phone" makes it not possible to get back data from the
321 phone, if it was changed there, of course. 321 phone, if it was changed there, of course.
322 If you sync with the phone, do not use "Export to phone" from any device. 322 If you sync with the phone, do not use "Export to phone" from any device.
323 (And do not sync, as mentioned above, from any other device with that phone). 323 (And do not sync, as mentioned above, from any other device with that phone).
324 It would delete the needed information for syncing with that phone! 324 It would delete the needed information for syncing with that phone!
325 325
326 We are using Gammu (Version: 0.98.9) ( http://freshmeat.net/projects/gammu/ ) 326 We are using Gammu (Version: 0.98.9) ( http://freshmeat.net/projects/gammu/ )
327 for accessing the phones. 327 for accessing the phones.
328 Note: You cannot use the original Gammu for syncing KDE-Pim/Pi, because 328 Note: You cannot use the original Gammu for syncing KDE-Pim/Pi, because
329 we have modified the original version to make it useable for syncing! 329 we have modified the original version to make it useable for syncing!
330 Gammu allows access to many phones in many ways (Irda, Bluetooth, serial,...). 330 Gammu allows access to many phones in many ways (Irda, Bluetooth, serial,...).
331 The recommended phone access using Gammu with KDE-Pim/Pi is Irda (infrared). 331 The recommended phone access using Gammu with KDE-Pim/Pi is Irda (infrared).
332 Bluetooth access is disabled on the Zaurus, but may work on Windows. 332 Bluetooth access is disabled on the Zaurus, but may work on Windows.
333 Please look at the Gammu homepage and documentation about more details 333 Please look at the Gammu homepage and documentation about more details
334 configuring Gammu how to access your phone. 334 configuring Gammu how to access your phone.
335 If you have problems accessing your phone, start KO/Pi from the konsole 335 If you have problems accessing your phone, start KO/Pi from the konsole