Issue 120823

Summary: meta tracking issue for MS interoperability issues in current focus
Product: General Reporter: jsc
Component: codeAssignee: AOO issues mailing list <issues>
Status: UNCONFIRMED --- QA Contact:
Severity: Normal    
Priority: P3 CC: elish, hdu, orcmid, orw
Version: 4.0.0-dev   
Target Milestone: 4.0.0   
Hardware: All   
OS: All   
Issue Type: DEFECT Latest Confirmation in: 3.4.1
Developer Difficulty: ---
Issue Depends on: 119232, 119428, 119429, 119430, 119431, 119432, 119434, 119482, 119503, 119511, 119589, 119590, 119610, 119611, 119616, 119617, 119618, 119625, 119639, 119659, 119661, 119692, 119701, 119706, 119710, 119715, 119717, 119719, 119720, 119723, 119725, 119726, 119727, 119736, 119739, 119741, 119749, 119752, 119754, 119757, 119758, 119760, 119769, 119771, 119773, 119774, 119777, 119785, 119794, 119801, 119809, 119810, 119811, 119812, 119814, 119815, 119816, 119822, 119824, 119826, 119827, 119828, 119829, 119833, 119834, 119836, 119848, 119849, 119852, 119857, 119859, 119865, 119869, 119876, 119896, 119899, 119904, 119905, 119906, 119908, 119910, 119913, 119914, 119916, 119921, 119925, 120995, 115922, 119284, 119415, 119422, 119548, 119563, 119626, 119627, 119634, 119652, 119660, 119686, 119703, 119707, 119714, 119738, 119750, 119766, 119825, 119831, 119863, 119885, 119915, 119920, 119945, 119952, 119953, 119954, 119957, 119960, 119963, 119964, 119972, 119985    
Issue Blocks:    

Description jsc 2012-09-05 12:14:37 UTC
This issue is intended to track some MS interoperability issues easily where a query is much more complicate.
Comment 1 jsc 2012-09-05 12:15:53 UTC
add some issues
Comment 2 Oliver-Rainer Wittmann 2012-09-05 12:29:59 UTC
adding issue 119634 for its duplicate 119563
Comment 3 hdu@apache.org 2012-09-05 12:42:33 UTC
Referencing blocking bug 115922 for its duplicate bug 119738.
Comment 4 orcmid 2012-09-05 17:27:56 UTC
This is a pretty daunting list, although I see that 17 of the 120 are resolved.

Since AOO 3.5.0 is targetted, could we say that a significant feature of 3.5 is enhanced MS interoperability?

In that case, would it be good to also consider interoperability with MS support of ODF 1.2 in the forthcoming Office 2013/365 and Skydrive on-line implementations?

I can imagine that there are limitations based on different degrees and different approaches to ODF 1.2 features support between AOO, LibO, and MSO and it would be great to comprehend them and see what could improve feature coincidence.

I suspect that this might inform improvement of interchange with OOXML as well.  I assume it is clear by now that OOXML is not going away.
Comment 5 Edwin Sharp 2014-03-03 18:55:57 UTC
Is this issue still in use?