Hacker News new | past | comments | ask | show | jobs | submit login

Hope this encourage them to invest in improving OOXML compatibility. I think right now this is the biggest reason people avoid LibreOffice.

Also, some action must be taken about MS behavior. They are the same company they were in the 90's. It is easy to find commit messages in LO explaining things like 'this is what MSO does but not what the specification says'. They recently change the algorithm the justifies text in MSO and it is not explained in the specification. So, even a simple text file without any especial formatting may not be viewed correctly with anything but MSO.

This is ridiculous. The use of such a format should be forbidden for governments. ISO shouldn't have ratified it.




This being the government, they have the power to flip this around. Why invest in compatibility with Microsoft Office when you can use the good old native OpenOffice formats instead? When the state is working in LibreOffice, there's no need to save files in Microsoft's format anymore.


Makes sense. That would be even better.


Does anyone know of any large-scale implementations of https://www.onlyoffice.com/ ? I wonder if that suite would be a better solution than LO simply because it is OOXML native (unlike LO which AFIK is ODF native and has a conversion layer to be compatible with OOXML). I think that OO's feature set is still limited in comparison to LO, but they are making a lot of progress (and being web-native seems like a huge advantage as well).


They have a list of costumers but I really don't know of any large-scale implementation.

I've been testing it on my notebook and its compatibility with OOXML is much better than LO. Of course, harder cases break on both. So, even combining both, something I've tried to do, is not enough to achieve good compatility with MSO.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: