diff options
author | Aaron Weber <aaron@ximian.com> | 2002-11-05 06:41:05 +0800 |
---|---|---|
committer | Aaron Weber <aaron@src.gnome.org> | 2002-11-05 06:41:05 +0800 |
commit | fab377c503df250439b84aba95db023786d33ee1 (patch) | |
tree | 4fe93ea07618e0a1cc908e49a55df29dca565439 /help/C/config-sync.sgml | |
parent | 877e911cdf220fa6dde24df147b9e8843c42fae9 (diff) | |
download | gsoc2013-evolution-fab377c503df250439b84aba95db023786d33ee1.tar gsoc2013-evolution-fab377c503df250439b84aba95db023786d33ee1.tar.gz gsoc2013-evolution-fab377c503df250439b84aba95db023786d33ee1.tar.bz2 gsoc2013-evolution-fab377c503df250439b84aba95db023786d33ee1.tar.lz gsoc2013-evolution-fab377c503df250439b84aba95db023786d33ee1.tar.xz gsoc2013-evolution-fab377c503df250439b84aba95db023786d33ee1.tar.zst gsoc2013-evolution-fab377c503df250439b84aba95db023786d33ee1.zip |
All sgml files replaced with xml files. XML files validated. Two new XML
2002-11-04 Aaron Weber <aaron@ximian.com>
* C/*.sgml: All sgml files replaced with xml files. XML files
validated. Two new XML files added: apx-fdl.xml and legal.xml
* C/evolution-C.omf: Altered to fit the GDP template. This may now
work with the GNOME 2.0 DTD, although I could be wrong.
* sgmldocs.make: removed and replaced with xmldocs.make. This will
break all translations until they are also ported to XML. I will
probably begin doing that tomorrow, since it's just markup and not
language stuff.
* C/Makefile.am: added two files to the list. Does this
Makefile get included in another, somewhere, or is it just
detected?
svn path=/trunk/; revision=18538
Diffstat (limited to 'help/C/config-sync.sgml')
-rw-r--r-- | help/C/config-sync.sgml | 138 |
1 files changed, 0 insertions, 138 deletions
diff --git a/help/C/config-sync.sgml b/help/C/config-sync.sgml deleted file mode 100644 index 95b0e71603..0000000000 --- a/help/C/config-sync.sgml +++ /dev/null @@ -1,138 +0,0 @@ - <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>Ximian 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> by selecting - <menuchoice><guimenu>System</guimenu><guimenuitem>Settings</guimenuitem></menuchoice>, - and make sure that <application>Pilot Link</application> is - properly configured. You will need to make sure that you have - read and write permissions on the device, which is normally - /dev/pilot. If that does not work, check /dev/ttyS0 if you have - a serial connection, or /dev/ttyUSB0 for a USB connection. You - can do this by becoming root and running the command: - <userinput>chmod 777 /dev/ttyUSB0</userinput>. - </para> - <para> - Once your computer and your Palm-OS device are talking happily - to each other, select the <glossterm - linkend="conduit">conduits</glossterm> you want under the - <guilabel>Pilot Conduits</guilabel> section of the Control - Center. You may use conduits to synchronize data with several - applications; the <application>Ximian Evolution</application> - conduits are labelled <guilabel>EAddress</guilabel>, for the - contacts in your addressbook, <guilabel>ECalendar</guilabel>, - for your calendar, and <guilabel>ETodo</guilabel>, for your - task list. - </para> - <para> - To enable a conduit, click the - <guibutton>Enable</guibutton> to enable it, and click - <guibutton>Settings</guibutton> to change what it will do when - activated. 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 the behavior you want for each conduit you choose to use. - If you're not sure, go ahead and stick with - <guilabel>Synchronize</guilabel>. Then, put your handheld on - its cradle and press the HotSync 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 the <filename>evolution</filename> - directory inside your home directory. - </para> - </tip> - </para> - - </chapter> - - - - |