You will find this and the related discussion of interest as well, <http://tools.oasis-open.org/issues/browse/OFFICE-3740>.
Note that this is about the spurious notion that the ODF 1.1 consumer in Microsoft Office is in error because of a package <manifest:manifest> start-tag attribute that was not introduced for that element until relatively late in the ODF 1.2 progression. It is also the case that all documents produced by OpenOffice.org and LibreOffice.org as ODF 1.2 documents prior to the "bug fix" will now be reported as not conforming by later versions of the ODF validator. (OO.o has never had a stable release with the "fix.") My recommendation is that, regardless of what the ODF TC does or does not do, the behavior of Apache OpenOffice be updated to treat the <manifest:manifest> start-tag attribute manifest:version="1.2" as optional and not produce it. (This has nothing to do with the optional appearance of manifest:version attributes on <manifest:file-entry> elements.) - Dennis -----Original Message----- From: Andrea Pescetti [mailto:[email protected]] Sent: Sunday, January 29, 2012 09:45 To: [email protected] Subject: Re: OOo, ODF 1.2 extended format and Word: is the possibility to open OOo generated file by word ed as bug? On 17/01/2012 Rob Weir wrote: > Think of it from the user's perspective. Are they really going to be > satisfied with the argument "The standard told me to do it" when their > documents show up as corrupt in MS Office 2007? I don't think so. Regardless of other discussions, do we have an issue in https://issues.apache.org/ooo/ to track this problem? The issue should probably include a reference to https://bugs.freedesktop.org/show_bug.cgi?id=44498#c17 since the analysis there is probably useful to discussing the issue for Apache OpenOffice too, and to https://issues.apache.org/ooo/show_bug.cgi?id=115789 i.e., the bugfix in OpenOffice.org that triggered the error in Word. Regards, Andrea. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
