4 ms·
> Improved MS Office Interoperability The problem is that this is a moving target (and event more in motion due to Microsoft's need to port this to some mobile
by _pmf_ 13y ago
> Improved MS Office Interoperability
The problem is that this is a moving target (and event more in motion due to Microsoft's need to port this to some mobile platform, so no matter how much is invested in this issue, they will never get close to acceptable.
- ZeroMinx 13y agoYes, it is a moving target, but you can still get it to a very solid good level. In the past it's always been a few years between updates, and they have version details in the files, so you can say "Supports Word 2007 files" and not worry about Word 2016. I've written a bunch of Perl code (that I should open source.. maybe some day. anyone here'd find that useful?) for creating and editing docx files. It's not that hard -- it's all XML! EDIT: I was using a LibreOffice daemon before, but I did this code just because Libre had so many bugs / missing features when converting a document to docx.
- slacka 13y agoAgreed MS 97-2003 .doc is NOT a moving target. Back in 2008 when we were considering moving from MSO 2003 to OO or SoftMaker Office, SoftMaker had near perfect MSO import filters. 5 years later, and only 3 of the 14 .doc import bugs that I filed with OO (now on AOO tracker) have been fixed. It's too bad the Oracle didn't take OO under their wings. With their resources they could have turned it into a true competitor to MSO. As it stands now, volunteers enjoy adding new features not bug fixing or scouring the 200 page OpenXML spec. sheet.