News for hackers. Stuff that matters.
Re:LibreOffice leverages Google’s OSS-Fuzz to improve quali... by PeterisP on Monday May 29, 2017 @02:30PM (#14440586)
I could have agreed with your claim 10 years ago, but not now. I've had such problems with MS software back in office97/2000 era, but not now - on the other hand, I have had interop issues with Libreoffice back when I used it last year, so it's currently not good enough (yet?) to be used safely.

To be clear on definitions, my understanding of "interoperability" involves the following workflow - if I open a complex document made by someone else in MS Excel or Word, change one word in it, save it (in MS format) and send it back, then I have to be sure that I haven't corrupted anything else in that document - layout nuances, styles,references, pagination, whatever. Currently it's not the case, and it makes it unusable, since I can't even verify if something looks different on my computer than it had looked in MS Office.

I mean, it's a simple test - if opening ("importing"? "converting"? technically that might be more appropriate than merely opening) a document and immediately saving it changes it somehow, it's not ok.

Re:LibreOffice leverages Google’s OSS-Fuzz to improve quali... by soperj on Monday May 29, 2017 @04:42PM (#14441311)
Use a open standard. Save it as an odt.
Re:LibreOffice leverages Google’s OSS-Fuzz to improve quali... by PeterisP on Monday May 29, 2017 @04:59PM (#14441391)
That's switching to another workflow, not interoperability with the existing one.