diff options
Diffstat (limited to 'doc/no/config-sync.sgml')
| -rw-r--r-- | doc/no/config-sync.sgml | 128 |
1 files changed, 128 insertions, 0 deletions
diff --git a/doc/no/config-sync.sgml b/doc/no/config-sync.sgml new file mode 100644 index 0000000000..8f3b30d1f0 --- /dev/null +++ b/doc/no/config-sync.sgml @@ -0,0 +1,128 @@ + <chapter id="config-sync"> + <title>Setting up your synchronization system</title> + <para> + Synchronization presents you with two issues you'll need to + address. + <simplelist> + <member> + Your computer needs to recognize and access your handheld. + At this time, <application>Evolution</application> only + supports Palm-OS devices like the PalmPilot and the + Handspring Visor. + </member> + <member> + You should decide what sort of synchronization behavior you + want. + </member> + </simplelist> + + </para> + + <para> + If you haven't used a handheld device with your computer + before, you'll need to run the GNOME <application>Control + Center</application> and make sure that <application>Pilot + Link</application> is properly configured. Then, select the + <application>Evolution</application> <glossterm + linkend="conduit">conduits</glossterm> under the + <guilabel>Pilot Conduits</guilabel> section of the Control + Center. + </para> + + <para> + Once your computer and your Palm-OS device are talking happily + to each other, you'll have to decide what exactly you want + them to do with the data they exchange. To enable a conduit, click the + <guibutton>Enable</guibutton> to enable it and click + <guibutton>Settings</guibutton>. Your options may vary + depending on the conduit, but typically they will be: + + <variablelist> + <varlistentry> + <term>Disabled </term> + <listitem> + <para> + Do nothing. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Synchronize</term> + <listitem> + <para> + Copy new data from the computer to the handheld, and + from the handheld to the computer. Remove items + that were on both systems but have been deleted on + one. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Copy From Pilot</term> + <listitem> + <para> + If there is any new data on the the handheld device, + copy it to the computer. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Copy To Pilot</term> + <listitem> + <para> + Copy new data from the computer to the handheld. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Merge From Pilot</term> + <listitem> + <para> + Copy new data from the handheld to the computer, and + remove any information from the computer that has + been deleted on the handheld. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Merge To Pilot</term> + <listitem> + <para> + Copy new data from the computer to the handheld, and + remove any information from the handheld that has + been deleted on the computer. + </para> + </listitem> + </varlistentry> + </variablelist> + </para> + + <para> + Select a behavior for each conduit available. For the most + part, you'll want to stick with + <guilabel>Synchronize</guilabel>. Then, put your handheld on + its cradle and press the synchronization button. + </para> + + + <para> + <tip> + <title>Data Loss Prevention</title> + <para> + It's always a good idea to make a backup. To do that, + make a copy of your <systemitem> + <filename>~/evolution</filename> </systemitem> directory. + </para> + </tip> + </para> + + </chapter> + + + + |