Date: prev next · Thread: first prev next last
2015 Archives by date, by thread · List index

       You're right, that was probably not the best word to choose;
           although I think I explained my meaning -
          I note you deleted that part of the e-message  ;-)

       I merely meant that when saving an LO document to MsFt, the versions
will not appear the same ...
          the spacing may be off, the images may be skewed, any tables are
out of alignment, ... ... ...
         and the MsFt document has increased in size due to all the excess
gobbledygook  ;-)

From: Joel Madero <>
Date: Fri, Jul 24, 2015 at 4:08 PM
Subject: Re: [libreoffice-users] Question about LO Writer and "complex
To: anne-ology <>
Cc: "" <>

On Fri, Jul 24, 2015 at 1:59 PM, anne-ology <> wrote:

       As for me, I much prefer to use LO.

       Although it's not compatible with MSFT; this makes it difficult to
send a document to someone.

This is simply a false statement. "It's not compatible." Please don't give
new users a false impression of the product. It is compatible in the
majority of cases, yes there are *some* issues but often times (including
with "complex documents") everything works fine. LibreOffice can open and
save to proprietary OOXML formats and in most cases it's seamless or close
to seamless.


*Joel Madero*
LibreOffice QA Volunteer

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: 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.