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


I always recommend older pre-OOXML formats (2003 Office formats, .doc, .xls, etc....) because even Microsoft can't keep up with OOXML.


On 9/8/2016 8:53 PM, Zenaan Harkness wrote:
Have been trying to determine what to suggest as preferred/ default file
save format for users stuck in MSO Word, wrt feature support and LO
cross compatibility:

.docx actually has two save file type options for the one extension in
MSO Word:
  - Word Document
  - Strict Open XML Document

I have been searching, reading Wikipedia on the format,
https://en.wikipedia.org/wiki/OpenXML
and as yet have not been able to find definite answers:

a) which is best for LO compatibility ?

b) are there any more/less features in one format or the other:
    - in LO ?
    - in Word ?


The strict format is an ISO standard and is younger, and may have some
issues on that basis:
https://bugs.documentfoundation.org/show_bug.cgi?id=83571

But perhaps it is better anyway?

Thanks for any insight and links you can share,
Zenaan



--
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.