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


italovignoli wrote
OOXML Strict is supported only by MS Office 2013, while all other MS
Office incarnations will not open it (and will tell the user that the
file is corrupted).

This statement is not accurate. ISO/IEC 29500 Strict can be opened / edited
by MSO 2010 and opened / edited / saved by MSO 2013 and MSO 365. This was
blogged about back in 2012 (where "New Office" implies MSO 2013 and MSO
365):

http://blogs.office.com/2012/08/13/new-file-format-options-in-the-new-office/

The *default* file format used by both MSO 2013 and MSO 365 is ISO/IEC 29500
Transitional. This can be changed to ISO/IEC 29500 Strict if necessary:

http://social.technet.microsoft.com/Forums/en-US/e969fc0a-9fcd-4efe-bf6d-79ea8c34360f/what-is-the-default-file-format-for-saving-in-ms-office-2013-is-it-still-the-transitional-ooxml-or?forum=officeitpro




-----
Best wishes, Owen.
--
View this message in context: 
http://nabble.documentfoundation.org/What-version-tp4118061p4118374.html
Sent from the Users mailing list archive at Nabble.com.

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