From: Fabian Rodriguez <email@example.com>
Sent: Tuesday, 11 December 2012, 14:07
Subject: Re: [libreoffice-users] A Tale of Two Office Suites
-----BEGIN PGP SIGNED MESSAGE-----
Le 12-12-11 07:54 AM, VA a écrit :
I'm obviously not communicating very well.
I haven't had any "conflict between configuration profiles or during
normal usage that leads to a crash or data loss" from running all three
programs, so I currently have no reason to file any bug reports.
So, again, my question.
Why is it not advisable to run LO and AOO on the same system? What
harm does it do to my system?
Because you may have a "conflict between configuration profiles or
during normal usage *that leads to a crash* or data loss".
/**** THAT LEADS TO A CRASH *** <--- POSSIBLE HARM TO YOUR SYSTEM*/ (ie.
software/OS normal operation)
If your data isn't critical, this won't matter much. I run similar
configurations on a Windows test system for example.
I believe in your very first post you also indicated the forks will
differ so much in the future that this won't remain practical/compatible
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: PGP/Mime available upon request
Comment: Using GnuPG with undefined - http://www.enigmail.net/
-----END PGP SIGNATURE-----
For unsubscribe instructions e-mail to: firstname.lastname@example.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
Impressum (Legal Info)
: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (MPLv2
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our trademark policy