Apache OpenOffice (AOO) Bugzilla – Issue 86205
Increase the compabilty based on Microsoft's documents
Last modified: 2013-02-07 22:33:24 UTC
I hope these documents help to increase Microsoft Binary File compability: http://www.microsoft.com/interop/docs/OfficeBinaryFormats.mspx Also some more fileformats: http://www.microsoft.com/interop/docs/supportingtechnologies.mspx License (Microsoft Open Specification Promise): http://www.microsoft.com/interop/osp/default.mspx
The OOo document filter for Microsoft documents belong to each OOo application. So please write an issue for each application or document type. This improvement can't be done at a central place in the office.
What about to convert this to tracking issue with depedndency with component based issues?
Sounds like a plan :-)
Kami, thanks for trying to help, but honestly speaking I don't know what such meta issues can help. Of course nobody prevents you from creating such a "meta" issue but I don't think it will make any sense for the developers and testers. Even currently we have several hundred issues in Word and RTF Import and Export and I'm sure we will get new ones over the years. Putting references to all of them into a single meta issue will create nothing but overhead because someone (guess who ;-)) has to maintain that. Be aware of that befor you embark upon it. :-) Perhaps a query or bug list (or wiki page) *could* make at least some sense but I honestly doubt that also. Nobody felt the need to create one in the meanwhile ~14(?) years of Word filter development we have been doing until today. Why should that change dramatically now just because we got some documentation from Microsoft that more or less does not contain anything new? Especially it doesn't make sense to relate the MS interop bug fixing to the new documentation. As Caolan pointed out in his blog, most of our issues are not caused by missing documentation. And the selection of issues to become fixed is driven by customer and user demand, not by any documentation. So I opt for closing this issue and also those created for the single applications (I did that for Writer). Issue tracker is not a planning tool, and it's full enough already. Kami, I hope you don't mind, I appreciate your will to help us but at the end such tracking work is just overhead.