Date: prev next · Thread: first prev next last
2010 Archives by date, by thread · List index 

Installing LibORC1on a Windwows system[1] creates an issue with a
co-installed OOo install. Once LibO is installed it takes over all .odt
etc file properties associations.

- LO takes over all OOo application defaults & icons.
- LO uses the same executable names as OOo (soffice.exe, swriter.exe,
etc). This makes it impossible to select an .odt and re-associate it
with OOo on the same system.

Sorry, I can't provide screenshots as I only test WinXP in a Virtual
Machine.

*Please* correct this issue in the RC2 release. swriter et al are OOo
executable/shell(linux) names; change them to libowriter etc and you'll
avoid this issue. As long as this issue exists the user is unlikely to
install LibO in any production system that also has OOo installed.

Context

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.