There are two different issues in https://bugs.freedesktop.org/show_bug.cgi?id=44498
One issue is a Catch 22 around the ODF 1.2 manifest:version attribute that is required for ODF 1.2 packages and that is not recognized by ODF 1.0/1.1 consumers and ODF 1.2 consumers produced prior to introduction of the requirement. (Some older implementations ignore attributes that are not understood in ODF package manifests, others may simply fail. Microsoft Word ODF 1.0/1.1 reports a problem and the option to attempt "repair.") [I've gone into this one in a previous message.] The other problem has to do with a border not being preserved between the OOo producer and an MS Word consumer. (Word produces the border in a form that round-trips successfully via ODF, which is what makes this kind of interop detective-work so exciting. There are a number of asymmetrical interop cases between MS Office and OpenOffice, whether via ODF format, OOXML format, or Office binary-format inerchange.) - Dennis -----Original Message----- From: Simon Phipps [mailto:[email protected]] Sent: Friday, January 13, 2012 15:15 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 13 Jan 2012, at 23:09, Dave Fisher wrote: > Has the TDF contacted Microsoft to report this bug? > > On two occasions where the Apache POI community discovered trouble we've been > able to contact them. In the first case they patched the problem in less than > one month. I can ask, but I'd suspect not as, unlike at Apache, Microsoft is not involved with TDF. Do you have a suitable pathway to reliably contact a suitable staff member? I can add a note to bug 44498* or, even better, you could :-) Thanks, S. * https://bugs.freedesktop.org/show_bug.cgi?id=44498 --------------------------------------------------------------------- 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]
