"Dennis E. Hamilton" <dennis.hamilton@acm.org> writes:
I've looked into this.
Thanks for your research. If I ever step into this, I now know what it's
about!
FOR THE ODT FILES ONLY:
The problem is that Microsoft supports ODF 1.1. The later versions of
LO (and OO.o) anticipate ODF 1.2 and by default use ODF 1.2-only
features of the manifest in the ODT package. The Microsoft ODF 1.1
implementations do not recognize those features and considers there to
be something wrong. If you let Word "attempt to correct" the document
it will, and it will be fine.
Heh, I wonder if they could instead check for the format version and
instead say "This document was saved in a newer version of ODF, which
might contain features Microsoft Office System does not support."
But as both issues (MSO->LibO and LibO->MSO) are about the manifest, it
is understandable that both LibO and MSO claim the files are corrupted.
--
Nuno J. Silva (aka njsg)
gopher://sdf-eu.org/1/users/njsg
--
Unsubscribe instructions: E-mail to users+help@libreoffice.org
In case of problems unsubscribing, write to postmaster@documentfoundation.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/www/users/
All messages sent to this list will be publicly archived and cannot be deleted
Context
- Re: [libreoffice-users] Re: LO Writer 3.4.0 --- basic .doc/.odt files not understood properly by MS Office 2010 (continued)
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.