On 28/07/2011 21:54, Olivier Hallot wrote:
IMHO that's a very shortsighted view. One of the main advantages (in my
experience) is the ability of LO to export direct to email in MSO format.
I would prefer that LO import MSO format flawlessly but not export them at
Consider the following scenario.
A user uses MSO 2007 or 2010 and they use the OOXML format by default or
by choice. If they then send a document to someone else that only uses
MSO 2003 or earlier, and the sender is not certain whether the recipient
has the Compatibility pack installed, they have to save their document
as a 97-2003 version and thus rapidly build up duplicated documents on
their machine in both OOXML format and 97-2003 format.
Now consider the LO user. Creates and saves documents in ODF format -
sends to an MSO user just by doing the Send As .Doc format. No
duplication of documents at all.
A really great feature, and one that assumes MSO document type support.
IMHO, a necessity in the current climate (particularly looking at the
growing practice of computer Vendors installing a trial version of
Office 2010 which reverts to a Starter edition if not purchased. That's
the danger as far as I can see....)
Unsubscribe instructions: E-mail to firstname.lastname@example.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/discuss/
All messages sent to this list will be publicly archived and cannot be deleted
Re: [tdf-discuss] ignore m$ legacy? · e-letter
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