I've used Open Office in conjunction with MS Office for a number of years. In switching to Libre Office, I chose the Typical Install as I've done a number of times before with OO. Unlike OO, Libre Office took over many of the MS Office file types. In looking at the documentation more closely, I saw that I could have avoided this if I'd used the Custom Install. I can probably remove and reinstall Libre Office to correct this but it would be nice if there was an indication when you pick Typical/Custom that helps direct you OR a check box in the Typical Install path to choose the behavior.
I can see why this would be annoying for people making the transition from MS Office to LO and still using both or those who have to use both for other reasons. Going to mark this as a HIGHEST priority Enhancement as I think it's not great policy to auto "hijack" MS formats. Thanks a lot for the suggestion
There is a custom action in installer that checks if Microsoft Office filetypes are registered, and if they are, installer will not associate them to LibreOffice by default. The problem is that this custom action does not work properly. I want to fix this before 3.6.0.
I wonder whether this bug is a duplicate of bug 39791. Reporter wrote: "Unlike OO, Libre Office took over many of the MS Office file types." But we do not know what file types were that exactly. Maybe only .rtf and .doc?
It hijacks all the extensions, for Word, Excel and Powerpoint. Please solve. I try to keep software updated in a computer lab, every time I upgrade LibreOffice (I cannot run custom update, the update is done in batch for a bunch of programs) it hijacks all the MS Office extensions, I have to go on and either repair MS Office or associate all the extensions back with MS Office.
I have to revise my previous statement, it looks (latest version anyway) like it hijacks only .docx
This is rather old and marked for 3.5.x. This is likely a duplicate of Bug 39791 but anyway it works fine with LO 3.6, although there are some other problems.
*** This bug has been marked as a duplicate of bug 39791 ***