Joel Madero wrote on 8/8/2014 2:12 PM:
On Fri, Aug 8, 2014 at 11:09 AM, Pikov Andropov <pikov22@gmail.com
<mailto:pikov22@gmail.com>> wrote:
jonathon wrote on 8/8/2014 1:49 PM:
> On August 8, 2014 9:47:51 AM PDT, Pikov Andropov wrote:
>
>>What difference does it make that a file was produced by a proprietary program?
>
> The issue s whether or not the end user can, in theory at least, go in and fix whatever is
causing the incompatibility with the documents
I don't expect the user to fix anything. The person who sent the file
should be asked to resend it in a more commo format. (Can the latest
MSO save as ODT files?)
> From my POV, MSO 2013 is too incompatible with MSO 2013, to be useful for anything more
sophisticated than constructing a document that will never be read, much less printed out.
MSO 2013 is incompatible with itself????
I think he meant that MSO 2013 isn't fully compatible with MSO2010 or
MSO2007 despite all three using "docx" - because each version
is different and Microsoft just hides this to the average user.
I didn't know that. So if I have MSO 2007 and get a DOCX file from
someone with MSO 10 or 13, can I expect to have trouble opening it?
--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
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
Context
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.