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


On Sat, Dec 18, 2010 at 2:18 AM, NoOp <glgxg@sbcglobal.net> wrote:
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.

Your argument is misleading. You can associate an extension with any
program you want and It doesn't matter if they have the same name or
not. In this case, you probably have select the path of the program so
it's a bit more work to do it, but in any any way it's *impossible* to
do it.

That being said, i think it's a good idea to change the program names,
but i don't consider it a blocker for 3.3.

Cheers,

-- 
Jesús Corrius <jesus@softcatala.org>
Document Foundation founding member
Skype: jcorrius | Twitter: @jcorrius

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.