Cor & Twayne, Thank you for your replies.
Twayne wrote: > > > If you think about the preceding paragraph, it's saying that both OOo and > LO > use the same file types and thus there could be confusion to the program > as > to which program should open a given file. Why should there be confusion? If LibO during installation grabs all ODF file types for itself, then doubleclicking on, say, an .odt file will launch LibO Writer but not OOo Wtiter. OOo could then still open the .odt via File > Open. And vice versa, if the user is given a choice during LibO installation to leave existing file associations intact. Ditto for Microsoft Office file types. Twayne wrote: > > Since you're apparently leaving OOo for LO Not so fast . I'd like to have both OOo and LibO coexisting on my system indefinitely. And I would expect to be able to make either program the default for all (or only some) possible file types via Windows Control Panel at any time. I've searched the bugzilla to see if this has been filed as a bug, did not find one. However, I found this: https://bugs.freedesktop.org/show_bug.cgi?id=33844, which suggests that LibO does not play nicely with OOo (but maybe it's only a problem for Portable LibO?) I wouldn't mind not being able to have both LibO and OOo open and running simultaneously, but I find the suggestion to uninstall OOo before installing LibO mystifying. <snip> -- View this message in context: http://nabble.documentfoundation.org/Side-by-side-install-of-LibO-and-OOo-tp3078835p3080029.html Sent from the Users mailing list archive at Nabble.com. -- Unsubscribe instructions: E-mail to [email protected] In case of problems unsubscribing, write to [email protected] Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
