I recently installed LO on a Windows XP machine on which I had Open Office
installed. I did not select the option to have file associations set up for
MS Office extensions to LO. I then started all the LO applications, thinking
they may be importing settings from OO like they did on my Linux machine.
Then I uninstalled OO. Now, I found the file associations are lost. Trying
to manually assign them has failed. From Windows Explorer, I can right
click, select Open With, then navigate to the LO executable via the browse
button (it is not listed on the applications list) and select the right one,
but when I click OK, it goes back to a MSO association (like Excel for
.ODS). I used to have those associations working to open the OO apps. I
didn't find a way in Tools/Options to reset the file associations. I can
probably reinstall to see if that fixes it. I wanted to check here to see if
anyone else knows what is going on and if a bug has been reported.
--
View this message in context:
http://nabble.documentfoundation.org/Troubles-with-file-associations-Win-XP-tp2990861p2990861.html
Sent from the Discuss mailing list archive at Nabble.com.
--
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/discuss/
All messages sent to this list will be publicly archived and cannot be deleted
Context
- [tdf-discuss] Troubles with file associations - Win XP · buchs
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.