diff options
author | Aaron Weber <aaron@src.gnome.org> | 2001-06-02 01:03:52 +0800 |
---|---|---|
committer | Aaron Weber <aaron@src.gnome.org> | 2001-06-02 01:03:52 +0800 |
commit | 53e160a7713f73f14a9fc0e400c2304f7e91ae5f (patch) | |
tree | 8322e3db49a9eb22f1cbd3be3178ed4572fada14 /doc/C | |
parent | 0372c03d3894deecb6e276e12401d8d2fd9a5e1c (diff) | |
download | gsoc2013-evolution-53e160a7713f73f14a9fc0e400c2304f7e91ae5f.tar gsoc2013-evolution-53e160a7713f73f14a9fc0e400c2304f7e91ae5f.tar.gz gsoc2013-evolution-53e160a7713f73f14a9fc0e400c2304f7e91ae5f.tar.bz2 gsoc2013-evolution-53e160a7713f73f14a9fc0e400c2304f7e91ae5f.tar.lz gsoc2013-evolution-53e160a7713f73f14a9fc0e400c2304f7e91ae5f.tar.xz gsoc2013-evolution-53e160a7713f73f14a9fc0e400c2304f7e91ae5f.tar.zst gsoc2013-evolution-53e160a7713f73f14a9fc0e400c2304f7e91ae5f.zip |
added questions about KDE, redid other questions.
svn path=/trunk/; revision=10081
Diffstat (limited to 'doc/C')
-rw-r--r-- | doc/C/evolution-faq.sgml | 960 |
1 files changed, 516 insertions, 444 deletions
diff --git a/doc/C/evolution-faq.sgml b/doc/C/evolution-faq.sgml index a497b98da2..dcee6b5b07 100644 --- a/doc/C/evolution-faq.sgml +++ b/doc/C/evolution-faq.sgml @@ -3,19 +3,347 @@ --> <appendix id="evolution-faq"> <title>Frequently Asked Questions About Ximian Evolution</title> - <para> - Here are some frequently asked questions about the - <application>Evolution</application> groupware suite from - Ximian. - </para> - + <para> + Here are some frequently asked questions about the + <application>Evolution</application> groupware suite from + Ximian. If you have a question that's not listed, you can + contact us at evolve@ximian.com. + </para> + + <sect1 id="faq-features"> + <title>Features</title> + + <qandaset> + + <qandaentry> + <question> + <para> + How can I use Evolution with Microsoft Exchange or Lotus Notes? + </para> + </question> + <answer> + <para> + If your server uses standard open protocols like IMAP, + POP, and SMTP, you can use Evolution with it. You can + share addresses with vCards and calendar items with iCal + appointments. We hope to have support for the + proprietary segments of Exchange and Notes severs + eventually, but this will come after Evolution 1.0. + </para> + </answer> + </qandaentry> + + <qandaentry> + <question> + <para> + Can I use Evolution with KDE? + </para> + </question> + <answer> + <para> + Evolution will work fine in KDE. You will need to + install all of the GNOME libraries that it depends on. + Also, certain configuration options, such as default + fonts and the message editor keybinding behavior, must be + changed using the GNOME Control Center application (this + will also run from within KDE). + </para> + </answer> + </qandaentry> + + <qandaentry> + <question> + <para> + How can I remove or rename a folder? + </para> + </question> + <answer> + <para> + We're going to add a good way to do this soon. In the + mean time, you have to remove it by hand. + </para> + + <para> + All the folders are stored in + <filename>~/evolution/local</filename>. Each folder is a + directory containing the data files, as well as a + <filename>subfolders</filename> directory that contains + all its subfolders. So for example if you have a + subfolder of the <filename>Inbox</filename> called + <filename>Foo</filename>, you can run the following + command to get rid of it (and all it subfolders): + </para> + + <programlisting> +rm -rf ~/evolution/local/Inbox/subfolders/Foo + </programlisting> + + <para> + You should do this after exiting Evolution. + </para> + </answer> + </qandaentry> + + <qandaentry> + <question> + <para> + Why doesn't drag and drop between folders seem to work? + </para> + </question> + <answer> + <para> + The implementation isn't finished, although it's planned + to be finished soon. + </para> + + <para> + In the meantime, you can copy the folders' contents by + hand from the shell (please do this after quitting + Evolution). For example: + </para> + + <programlisting> +cp -r ~/evolution/local/Inbox/subfolders/Foo ~/evolution/local/Inbox/subfolders/Bar + </programlisting> + + <para> + Likewise, you can use <command>mv</command> to rename or + move folders. + </para> + </answer> + </qandaentry> + + <qandaentry> + <question> + <para> + Can I read mail from a mailbox file created by some other + application (e.g. Mutt) without importing mail from it? + </para> + </question> + <answer> + <para> + No, but it's a planned feature. + </para> + </answer> + </qandaentry> + + <qandaentry> + <question> + <para> + Can Evolution sync with my Palm OS (tm) device? + </para> + </question> + <answer> + <para> + Yes. However, it is not yet stable enough for general + release and we do not yet ship Evolution with Palm + synchronization enabled default. Until we do, you will + need to compile this in yourself. Check the + <filename>README</filename> file for additional + information on the requirements. Full compatibility and + synchronization for calendar and addressbook applications + on Palm devices will be implemented and shipped soon. + </para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para> + What is the difference between a virtual folder (vfolder) + and a regular folder? + </para> + </question> + <answer> + <para> + A virtual folder is like a saved search: it is a view of + your mail. Regular folders actually contain the mail + messages. You can have one message be in multiple virtual + folders, but only in one regular folder. See the section + in the Evolution manual about virtual folders for more + information. + </para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para> + Can Evolution spell-check messages while I compose them? + </para> + </question> + <answer> + <para> + Yes. The Evolution composer is able to highlight + mis-spelled word on the fly as you type them, and also + give you suggestions for possible corrections. In order + for this to work you need the + <filename>gnome-spell</filename> component, which is not + shipped with Ximian GNOME yet. + </para> + + <para> + If you are brave enough, you can check out module + <filename>gnome-spell</filename> from the GNOME CVS and + compile it yourself. Check out its README file for a list + of <filename>gnome-spell</filename>'s requirements for + compilation. + </para> + + <para> + Note that you don't need to recompile Evolution after + installing <filename>gnome-spell</filename>; it will be + picked up automatically. + </para> + </answer> + </qandaentry> + + <qandaentry> + <question> + <para> + Why can't I see the images that are contained in some HTML + mail messages. + </para> + </question> + <answer> + <para> + Evolution currently doesn't support this, but it's a + planned feature. It will be an option: many people like + to turn off the images because they use up bandwidth and can + be used to spy on your email reading habits. + </para> + </answer> + </qandaentry> + + <qandaentry> + <question> + <para> + Can I change the font that Evolution uses to compose and + display mail messages? + </para> + </question> + <answer> + <para> + You have to change the GtkHTML settings for that: in the + GNOME Control Center, go to the "HTML Viewer" + configuration page, which is under the "Document Handlers" + category. + </para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para> + How do I import my Outlook <filename>.pst</filename> files into Evolution? + </para> + </question> + <answer> + <para> + You cannot import these files directly into Evolution + because the <filename>.pst</filename> format is a + proprietary format. However, Mozilla Mail on Windows can + convert them into the <type>mbox</type> format, which can + then be imported by Evolution. + </para> + + <para> + To start importing your Outlook mail to Evolution, run + Mozilla Mail on Windows and select the + <menuchoice><guimenu>File</guimenu><guimenuitem>Import...</guimenuitem></menuchoice> + to begin. Then select that you wish to import Mail from + Outlook. Once Mozilla has imported all your mail, reboot + your computer into Linux. + </para> + + <para> + Mount your Windows partition in Linux and run Evolution to + begin importing your mail. Select + <menuchoice><guimenu>File</guimenu><guimenuitem>Import + File...</guimenuitem></menuchoice> to start importing. Set + the file type to MBox (mbox) and click on + <guibutton>Browse</guibutton> to select the mail you want + to import. + </para> + + <para> + If you are the only user on Windows, the mail files will + be stored in <filename>/mnt/c/windows/Application + Data/Mozilla/Profiles/default/XXXX/Mail/imported.mail/</filename> + where <filename>/mnt/c/</filename> is your windows + partition mount point and XXXX is some collection of + numbers and digits ending in <filename>.slt</filename>. + </para> + + <para> + If there is more than one user, the file will be in + <filename>/mnt/c/windows/Profiles/USERNAME/XXXX/Mail/imported.mail/</filename> + where USERNAME is your Windows username. + </para> + + <para> + For each mail folder in Outlook, Mozilla will convert the + folder into one mbox file. To import all your mail, import + all the files without a <filename>.msf</filename> + extension. + </para> + </answer> + </qandaentry> + + <qandaentry> + <question> + <para> + If Mozilla can import <filename>.pst</filename> files, why can't Evolution? + </para> + </question> + <answer> + <para> + Mozilla on Windows accesses the <filename>.pst</filename> + files through the <filename>MAPI.DLL</filename>, which is + only avaliable on Windows. <filename>MAPI.DLL</filename> + is the only way to access <filename>.pst</filename> files + and Evolution cannot use this DLL in Linux. + </para> + </answer> + </qandaentry> + <qandaentry> + <question> + <para> + Will there be a server? How about a text-based or web-based front end? + </para> + </question> + <answer> + <para> + Of course, we can't comment on unannounced future product + plans, but Evolution's architecture would permit the + existence of that kind of software. If there is enough + demand for such software we will consider moving in that + direction. + </para> + </answer> + </qandaentry> + + <qandaentry> + <question> + <para> + Will Evolution make a good mocha? + </para> + </question> + <answer> + <para> + Only espresso is planned, but you can easily plug in a chocolate component. + </para> + </answer> + </qandaentry> + + </qandaset> + </sect1> + + <!-- Section: Getting and compiling --> <sect1 id="get-and-compile"> <title> Getting and Compiling Evolution </title> - <qandaset> + <qandaset> <qandaentry> <question> <para> @@ -125,6 +453,24 @@ </programlisting> </answer> </qandaentry> + + <qandaentry> + <question> + <para> + If Mozilla can import <filename>.pst</filename> files, why can't Evolution? + </para> + </question> + <answer> + <para> + Mozilla on Windows accesses the <filename>.pst</filename> + files through the <filename>MAPI.DLL</filename>, which is + only available on Windows. <filename>MAPI.DLL</filename> + is the only way to access <filename>.pst</filename> files + and Evolution cannot use this DLL in Linux. + </para> + </answer> + </qandaentry> + <qandaentry> <question> <para> @@ -169,7 +515,8 @@ <qandaentry> <question> <para> - I get <computeroutput>make: *** No rule to make target + I get the error message: <computeroutput>make: *** No rule + to make target `all-no-@BUILD_INCLUDED_LIBINTL@'</computeroutput> </para> </question> @@ -185,59 +532,77 @@ </qandaset> </sect1> - <sect1 id="faq-trouble"> - <title>Troubleshooting</title> + <sect1 id="faq-trouble"> + <title>Troubleshooting</title> <qandaset> <qandaentry> - <question> - <para> - I get <computeroutput>Cannot initialize the Evolution - shell</computeroutput>. - </para> - </question> - <answer> - <para> - Check that: - </para> - - <itemizedlist> - <listitem> - <para> - <filename>oafd</filename> is listen in your <envar>PATH</envar> - environment variable. - </para> - </listitem> - - <listitem> - <para> - <filename>GNOME_Evolution_Shell.oaf</filename> and - the other - <filename>GNOME_Evolution_*.oaf</filename> files are - readable and installed in - <filename>$prefix/share/oaf</filename>, where - <filename>$prefix</filename> is one of the prefixes - listed in <envar>GNOME_PATH</envar> or - <envar>OAF_INFO_PATH</envar>. (These variables are - supposed to contain $PATH-like colon-separated lists of - paths. If the installation prefix for Evolution is - different from that). Run `oaf-slay' once before running - `evolution' again if you change $GNOME_PATH or - $OAF_INFO_PATH. - </para> - </listitem> - - <listitem> - <para> - <filename>evolution</filename>, - <filename>evolution-mail</filename> and the other - <filename>evolution-*</filename> executables are in your - $PATH. - </para> - </listitem> - </itemizedlist> - </answer> + <question> + <para> + I get <computeroutput>Cannot initialize the Evolution + shell</computeroutput>. + </para> + </question> + <answer> + <para> + There are a number of things that can cause this error. + Check that: + </para> + + <itemizedlist> + <listitem> + <para> + <filename>oafd</filename> is listen in your <envar>PATH</envar> + environment variable. + </para> + </listitem> + + <listitem> + <para> + <filename>GNOME_Evolution_Shell.oaf</filename> and + the other + <filename>GNOME_Evolution_*.oaf</filename> files are + readable and installed in + <filename>$prefix/share/oaf</filename>, where + <filename>$prefix</filename> is one of the prefixes + listed in <envar>GNOME_PATH</envar> or + <envar>OAF_INFO_PATH</envar>. (These variables are + supposed to contain $PATH-like colon-separated lists of + paths. If the installation prefix for Evolution is + different from that). Run `oaf-slay' once before running + `evolution' again if you change $GNOME_PATH or + $OAF_INFO_PATH. + </para> + </listitem> + + <listitem> + <para> + <filename>evolution</filename>, + <filename>evolution-mail</filename> and the other + <filename>evolution-*</filename> executables are in your + $PATH. + </para> + </listitem> + </itemizedlist> + </answer> </qandaentry> - + + <qandaentry> + <question> + <para> + I get <computeroutput>Cannot open composer window</computeroutput>. + </para> + </question> + <answer> + <para> + This actually means that Evolution cannot activate the HTML + editor component from GtkHTML. The comments in the previous + answer still apply; also make sure that + <command>gnome-gtkhtml-editor</command> is in your + <envar>PATH</envar>. + </para> + </answer> + </qandaentry> + <qandaentry> <question> <para> @@ -258,8 +623,8 @@ <qandaentry> <question> <para> - I updated my Evolution, but my addressbook contacts are no - longer there, what should I do? + I updated Evolution and now my addressbook information is gone! + What should I do? </para> </question> <answer> @@ -369,7 +734,7 @@ </programlisting> <para> - Yes, we know this is a problem. It will be fixed eventually. + We're working on a solution to this problem now. </para> </answer> </qandaentry> @@ -391,7 +756,7 @@ </para> <para> - So, if this occurs to you, make sure all the components + If you run into this problem, make sure all the components are compiled and installed at the same time. This also applies to GtkHTML upgrades; after upgrading and installing a newer GtkHTML, always re-compile and @@ -441,13 +806,6 @@ </para> <para> - Normally, you shouldn't need to run - <command>oaf-slay</command>, unless <command>oafd</command> - gets stuck or confused. For example, it might help in case - Evolution cannot activate components. - </para> - - <para> Using <command>oaf-slay</command> <command>oaf-slay</command> is quite drastic and can cause problems with other programs that use oaf, especially with @@ -500,394 +858,108 @@ </para> </answer> </qandaentry> - <qandaentry> <question> <para> - What is a stack trace (backtrace) and how do I get one? - </para> + What is a stack trace (backtrace) and how do I get one? + </para> </question> <answer> <para> - A stack trace is a list of the chain of function calls that - lead to some point in the program. Typically, you want to - get a stack trace when Evolution crashes or hangs and you - want to try to figure out where in the code that happened - and why. For this reason, stack traces are extremely - useful for the Evolution developers, so it's important that - you learn how to get them, and include them in crash - reports. Once we have <command>bug-buddy</command> working - with our bug database, it will be much easier to do - this. Until then, here's how: + A stack trace is a list of the chain of function calls + that lead to some point in the program. Typically, you + want to get a stack trace when Evolution crashes or + hangs and you want to try to figure out where in the + code that happened and why. For this reason, stack + traces are extremely useful for the Evolution + developers, so it's important that you learn how to get + them, and include them in crash reports. Once we have + <application>bug-buddy</application> working with our + bug database, it will be much easier to do this. Until + then, here's how: </para> - <para> - First of all, in order to get a stack trace, your executable - (and possibly the libraries) must be compiled with debugging - symbols. Debugging symbols are created by default if you - compile from CVS, and are included in the snapshot builds. - If you decide to compile by yourself with some custom CFLAGS - value, make sure <command>-g</command> is included in them. + First of all, in order to get a stack trace, your + executable (and possibly the libraries) must be compiled + with debugging symbols. Debugging symbols are created by + default if you compile from CVS, and are included in the + snapshot builds. If you decide to compile by yourself + with some custom CFLAGS value, make sure -g is included + in them. </para> - <para> Finally, you must put the component that crashes through - <command>gdb</command>. Make sure all the components are - dead (exit Evolution and <command>killev</command>), then - run the following command: - </para> - - <programlisting> - gdb name-of-component - </programlisting> - - <para> - Then, at the gdb prompt, type <userinput>r</userinput> (for - "run") and wait a few seconds to make sure the component has - registered with the name service. Then start Evolution - normally from a different terminal. - </para> - - <para> - Then, reproduce the crash, and go back to the terminal where - you ran <command>gdb</command>. If the component crashed, - you should have a prompt there; otherwise, just hit - <keycombo action=simul> - <keycap>Control</keycap> - <keycap>C</keycap> - </keycombo>. - At the prompt, type: - </para> - - <programlisting> - info threads - </programlisting> - - <para> - This will give you a list of the current running threads, - e.g. - </para> - - <screen> - (gdb) info threads - 8 Thread 6151 (LWP 14908) 0x409778fe in sigsuspend () from /lib/libc.so.6 - 7 Thread 5126 (LWP 14907) 0x409778fe in sigsuspend () from /lib/libc.so.6 - 6 Thread 4101 (LWP 1007) 0x409778fe in sigsuspend () from /lib/libc.so.6 - 5 Thread 3076 (LWP 1006) 0x409778fe in sigsuspend () from /lib/libc.so.6 - 4 Thread 2051 (LWP 1005) 0x409778fe in sigsuspend () from /lib/libc.so.6 - 3 Thread 1026 (LWP 1004) 0x409778fe in sigsuspend () from /lib/libc.so.6 - 2 Thread 2049 (LWP 1003) 0x40a10d90 in poll () from /lib/libc.so.6 - 1 Thread 1024 (LWP 995) 0x40a10d90 in poll () from /lib/libc.so.6 - </screen> - - <para> - (Notice that, normally, only - <command>evolution-mail</command> will have more than one - thread.) - </para> - - <para> - Now, for each of the thread listed, type the following - commands: - </para> - - <programlisting> - thread N - bt - </programlisting> - - <para> - Where `N' is the thread number. (In this example, you would - have to do it with N as 1, 2, 3... 8.) Then cut and paste - all the output into some text file, and quit - <command>gdb</command> by typing - <userinput>quit</userinput>. - </para> - - <para> - You can also get a stack trace from a running component or a - component that has just crashed. Just start - <command>gdb</command> normally and, instead of using the - <userinput>r</userinput> command, use - <userinput>attach</userinput> to attach to the running - process: - </para> - - <programlisting> - attach PID - </programlisting> - - <para> - Where <userinput>PID</userinput> is the PID of the - component. Notice that this also works if you attach - right after a crash dialog appears, before hitting "OK" or - "Submit bug report". - </para> - </answer> - </qandaentry> - </qandaset> - </sect1> - - <sect1 id="faq-features"> - <title>Features</title> - <para> - Following is a list of questions about the features in - <application>Evolution</application>. - </para> - - <qandaset> - <qandaentry> - <question> - <para> - How can I remove a folder? - </para> - </question> - <answer> - <para> - Currently there is no command in Evolution to remove a - folder, so you have to remove it by hand. - </para> - - <para> - All the folders are stored in - <filename>~/evolution/local</filename>. Each folder is a - directory containing the data files, as well as a - <filename>subfolders</filename> directory that contains - all its subfolders. So for example if you have a - subfolder of the <filename>Inbox</filename> called - <filename>Foo</filename>, you can run the following - command to get rid of it (and all it subfolders): - </para> - - <programlisting> - rm -rf ~/evolution/local/Inbox/subfolders/Foo - </programlisting> - - <para> - You should do this after exiting Evolution. - </para> - </answer> - </qandaentry> - - <qandaentry> - <question> - <para> - Why doesn't drag and drop between folders seem to work? - </para> - </question> - <answer> - <para> - The implementation isn't finished, although it's planned - to be finished soon. - </para> - - <para> - In the meantime, you can copy the folders' contents by - hand from the shell (please do this after quitting - Evolution). For example: - </para> - - <programlisting> - cp -r ~/evolution/local/Inbox/subfolders/Foo ~/evolution/local/Inbox/subfolders/Bar - </programlisting> - - <para> - Likewise, you can use <command>mv</command> to rename or - move folders. - </para> - </answer> - </qandaentry> - - <qandaentry> - <question> - <para> - Can I read mail from a mailbox file created by some other - application (e.g. Mutt) without importing mail from it? - </para> - </question> - <answer> - <para> - No, but it's a planned feature. - </para> - </answer> - </qandaentry> - - <qandaentry> - <question> - <para> - Can Evolution sync to my Palm OS (tm) device? - </para> - </question> - <answer> - <para> - Yes. Evolution needs to be compiled with Palm syncing - support for this to work though. Please refer to the - <filename>README</filename> file for additional - information on the requirements. - </para> - </answer> - </qandaentry> - <qandaentry> - <question> - <para> - What is the difference between a virtual folder (vfolder) - and a regular folder? - </para> - </question> - <answer> - <para> - A virtual folder is like a saved search: it is a view of - your mail. Regular folders actually contain the mail - messages. You can have one message be in multiple virtual - folders, but only in one regular folder. See the section - in the Evolution manual about virtual folders for more - information. - </para> - </answer> - </qandaentry> - <qandaentry> - <question> - <para> - Can Evolution spell-check the messages while I compose them? - </para> - </question> - <answer> - <para> - Yes. The Evolution composer is able to highlight - mis-spelled word on the fly as you type them, and also - give you suggestions for possible corrections. In order - for this to work you need the - <filename>gnome-spell</filename> component, which is not - shipped with Ximian GNOME yet. - </para> - - <para> - If you are brave enough, you can check out module - <filename>gnome-spell</filename> from the GNOME CVS and - compile it yourself. Check out its README file for a list - of <filename>gnome-spell</filename>'s requirements for - compilation. - </para> - - <para> - Note that you don't need to recompile Evolution after - installing <filename>gnome-spell</filename>; it will be - picked up automatically. + <application>gdb</application>, the GNU debugging tool. + To do so, make sure all the components are dead (exit + Evolution and run <command>killev</command>), then run the + following command: + <programlisting> + <command>gdb name-of-component</command> + </programlisting> + + Where "name-of-component" is the name of the component that + crashed. + </para> + <para> + Then, at the gdb prompt, type r (for "run") and wait a + few seconds to make sure the component has registered + with the name service. Then start + <application>Evolution</application> normally from a + different terminal. + </para> + <para> + When you have started + <application>Evolution</application>, reproduce the + crash, and go back to the terminal where you ran gdb. If + the component crashed, you should have a prompt there; + otherwise, just hit Control+C. At the prompt, type + <command>info threads</command>. This will give you a + screen that looks like this: + </para> + <para> + <programlisting> +(gdb) info threads + 8 Thread 6151 (LWP 14908) 0x409778fe in sigsuspend () from /lib/libc.so.6 + 7 Thread 5126 (LWP 14907) 0x409778fe in sigsuspend () from /lib/libc.so.6 + 6 Thread 4101 (LWP 1007) 0x409778fe in sigsuspend () from /lib/libc.so.6 + 5 Thread 3076 (LWP 1006) 0x409778fe in sigsuspend () from /lib/libc.so.6 + 4 Thread 2051 (LWP 1005) 0x409778fe in sigsuspend () from /lib/libc.so.6 + 3 Thread 1026 (LWP 1004) 0x409778fe in sigsuspend () from /lib/libc.so.6 + 2 Thread 2049 (LWP 1003) 0x40a10d90 in poll () from /lib/libc.so.6 + 1 Thread 1024 (LWP 995) 0x40a10d90 in poll () from /lib/libc.so.6 + </programlisting> + + For the most part, only + <application>evolution-mail</application> will have more + than one thread. + </para> + <para> + Now, for each of the threads listed, type the following commands: +<programlisting> +thread N +bt +</programlisting> + Where 'N' is the number of the thread (in this example, 1 + through 8). + </para> + <para> + Cut and paste all the output gdb gives you into a text + file. You can quit gdb by typing + <userinput>quit</userinput> + </para> + <para> + If you prefer, you can start gdb while a process is + running. You'll want to do this right after a crash dialog + appears, but before hitting "OK" or "Submit bug report". + Start <application>gdb</application> as above, but instead + of using <userinput>r</userinput>, type <userinput>attach + PID</userinput> where PID is the process ID of the + component you want to debug. </para> </answer> </qandaentry> - - <qandaentry> - <question> - <para> - I cannot see the images that are contained in some HTML - mail message I am getting. Why? - </para> - </question> - <answer> - <para> - Evolution currently doesn't support this, but it's a - planned feature. It will be an option: many people like - to turn off the images because they use up bandwidth and can - be used to spy on your email reading habits. - </para> - </answer> - </qandaentry> - - <qandaentry> - <question> - <para> - Can I change the font that Evolution uses for compose and - displaying mail messages? - </para> - </question> - <answer> - <para> - You have to change the GtkHTML settings for that: in the - GNOME Control Center, go to the "HTML Viewer" - configuration page, which is under the "Document Handlers" - category. - </para> - </answer> - </qandaentry> - <qandaentry> - <question> - <para> - How do I import my Outlook <filename>.pst</filename> files into Evolution? - </para> - </question> - <answer> - <para> - You cannot import these files directly into Evolution - because the <filename>.pst</filename> format is a - proprietry format. However, Mozilla Mail on Windows can - convert them into the <type>mbox</type> format, which can - then be imported by Evolution. - </para> - - <para> - To start importing your Outlook mail to Evolution, run - Mozilla Mail on Windows and select the - <menuchoice><guimenu>File</guimenu><guimenuitem>Import...</guimenuitem></menuchoice> - to begin. Then select that you wish to import Mail from - Outlook. Once Mozilla has imported all your mail, reboot - your computer into Linux. - </para> - - <para> - Mount your Windows partition in Linux and run Evolution to - begin importing your mail. Select - <menuchoice><guimenu>File</guimenu><guimenuitem>Import - File...</guimenuitem></menuchoice> to start importing. Set - the file type to MBox (mbox) and click on - <guibutton>Browse</guibutton> to select the mail you want - to import. - </para> - - <para> - If you are the only user on Windows, the mail files will - be stored in <filename>/mnt/c/windows/Application - Data/Mozilla/Profiles/default/XXXX/Mail/imported.mail/</filename> - where <filename>/mnt/c/</filename> is your windows - partition mount point and XXXX is some collection of - numbers and digits ending in <filename>.slt</filename>. - </para> - - <para> - If there is more than one user, the file will be in - <filename>/mnt/c/windows/Profiles/USERNAME/XXXX/Mail/imported.mail/</filename> - where USERNAME is your Windows username. - </para> - - <para> - For each mail folder in Outlook, Mozilla will convert the - folder into one mbox file. To import all your mail, import - all the files without a <filename>.msf</filename> - extension. - </para> - </answer> - </qandaentry> - - <qandaentry> - <question> - <para> - If Mozilla can import <filename>.pst</filename> files, why can't Evolution? - </para> - </question> - <answer> - <para> - Mozilla on Windows accesses the <filename>.pst</filename> - files through the <filename>MAPI.DLL</filename>, which is - only avaliable on Windows. <filename>MAPI.DLL</filename> - is the only way to access <filename>.pst</filename> files - and Evolution cannot use this DLL in Linux. - </para> - </answer> - </qandaentry> </qandaset> - </sect1> -</appendix> + </sect1> + </appendix> -<!-- Local Variables: --> -<!-- indent-tabs-mode:nil --> -<!-- End: -->
\ No newline at end of file +<!-- Local Variables: --> <!-- indent-tabs-mode:nil --> <!-- End: --> |