Mailing-List: contact ooo-issues-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-issues@incubator.apache.org
From: bugzilla@apache.org
To: ooo-issues@incubator.apache.org
Subject: DO NOT REPLY [Bug 119164] File extension association doesn't work
 after I install other ODF editor and then upgrade to AOO 3.4
Date: Thu, 05 Apr 2012 02:10:58 +0000
Message-ID: <bug-119164-248469-cKPIeb6gGA@https.issues.apache.org/ooo/>
In-Reply-To: <bug-119164-248469@https.issues.apache.org/ooo/>
References: <bug-119164-248469@https.issues.apache.org/ooo/>
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0

https://issues.apache.org/ooo/show_bug.cgi?id=119164

--- Comment #6 from orcmid <orcmid@apache.org> 2012-04-05 02:10:58 UTC ---
(In reply to comment #5)
[ ... ]
Then I install Symphony, now, the ODF file will be opened by
> Symphony by default. And then I upgrade to AOO 3.4 r1303653, here the ODF file
> association should back to AOO, means the files with ODF file extension should
> be opened by AOO if I double click them.
> This issue nothing with language package, I uninstall these language packages
> and check, same problem.
[ ... ]

To be clear, are you saying that Symphony associations remain after you install
AOO?  Since the OO.o no longer possessed the associations, I suspect that AOO
did not seize them.

In general, polite installation of packages tends to leave any associations
that already exist alone.  Some software will ask if you want to change the
associations anyhow.  I don't think AOO does that for anything but the
extensions associated with Microsoft Office files.

Is your request that AOO, on installation, should associate the ODF-format file
extensions to it, even if they are already assigned to an application that has
not been removed?

-- 
Configure bugmail: https://issues.apache.org/ooo/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.