To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=45477





------- Additional comments from [EMAIL PROTECTED] Mon Jan 16 19:37:53 -0800 
2006 -------
2.0 has been out for a while now.

Perhaps it is time to consider a way of sanitising the registry when upgrading
OOo to avoid all the issues people will be having now with opening Office
documents since upgrading from 1.x to 2.0?

For those not convinced of the need to address this bug, try the following
simple demonstration.

1) Install OOo-1.1.4 on a clean system, using the default options for everything
2) 'Train' Windows Explorer ( right-click and 'open with...', select OOo ) and
other apps ( eg Thunderbird ) how to open common Office documents.
3) Uninstall OOo-1.1.4.
4) Install OOo-2.0.1, using the default options for everything.
5) Try to open Office documents from Windows Explorer and Thunderbird.

Explorer / Thunderbird try to use the old 1.1.4. They're looking in the
registry. We should make sure that the registry contains valid data while
installing.

I have to manually do the following on 20 or so systems every time I upgrade:

1) Uninstall OOo.
2) Open regedit.exe
3) Search for 'soffice'.
4) Delete all entries found.
5) Search for 'oowriter'.
6) Delete all entries found.
7) Search for 'oocalc'.
8) Delete all entries found.
9) Search for 'ooimpress'.
10) Delete all entries found.
11) Install OOo.

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to