LibO install in Windows currently follows the go-oo practice of removing existing OOo installs (without warning). It can of course be installed in parallel (see my thread "[libreoffice-users] [Windows] LibO in parallel w/OOo?" on the users list, but that provides several distinct disadvantages:
1. No system file association or icons. 2. No menu items (user must create their own + desktop icon) 3. Program file names are the same as OOo (soffice, scalc etc) so there is no easy way to distinguish between _which_ soffice et al that you are running. Given that LibO is a "fresh start", it would be nice if LibO can, in the future, behave in a responsible manner on Windows installs and not trash a user's version of OOo. After all, the user should have the freedom (Libre?) of being able to have both OOo and LibO installed on their system (in the same way one can on linux). I think that new (Windows) users to LibO might get pretty upset when they find that the install has trashed their OOo. I'm familiar with the issue of go-oo & Kami's OxygenOffice version trashing OOo in the install process, but new users/converts from OOo will not. Also recommend that the bins be changed from soffice to loffice etc., so that it's easy to determine which is which on the system. Disclaimer: I primarily use only linux, but I also use WinXP/7 for testing OOo, and now LibO. -- To unsubscribe, e-mail to discuss+h...@documentfoundation.org All messages you send to this list will be publicly archived and cannot be deleted. List archives are available at http://www.documentfoundation.org/lists/discuss/
