[19860] in Athena Bugs
Re: 14.A02 and acrobat plugins
daemon@ATHENA.MIT.EDU (t. belton)
Wed Oct 3 13:56:49 2001
Date: Wed, 3 Oct 2001 13:54:22 -0400 (EDT)
From: "t. belton" <tbelton@MIT.EDU>
To: John Hawkinson <jhawk@MIT.EDU>
cc: <bug-infoagents@MIT.EDU>, <f_l@MIT.EDU>
In-Reply-To: <Pine.GSO.4.30L.0110031340100.2013-100000@iphigenia.mit.edu>
Message-ID: <Pine.GSO.4.30L.0110031350010.2013-100000@iphigenia.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
The key question I need answered, jhawk, is: With the users who have
reported this problem, are local .mailcap and .mime.types files present?
And if those files are removed (and Netscape restarted), do they get the
plugin version of Acrobat, or the standalone?
When using the global mailcap they should ALWAYS get the standalone. If
that is not the case then I am looking at a completely different level of
problem.
On Wed, 3 Oct 2001, t. belton wrote:
> On Tue, 2 Oct 2001, John Hawkinson wrote:
> > As far as I can tell, netscape-fix doesn't try to touch your MIME types.
> > So, are you suggesting that the plugin was never the default?
> > I am confused.
>
> If a user is using the global mime-types and mailcap, then he should be
> getting the standalone app - that's what they're set to default to, and
> my testing tells me the globals are indeed working right.
>
> If a user has local versions of those files which point to the plugin,
> then that could be a problem. Cleaning up those files is a little more
> complex than cleaning up the preferences file (for one thing, settings
> aren't necessarily 1:1 with the global versions) and frankly I don't know
> how much we should bother messing with local mailcap and mime-types when
> officially we're trying to discourage people from having them AT ALL. If
> nothing else, it will require making a fix-it script that has to ask the
> user a number of questions they might not know the answer to (as opposed
> to fixing prefs, which can be done silently and without destroying
> anything really valuable).
>
>
> > > Oh, and I am sorry to say that plugin-vs-standalone may not help the crash
> > > problem very much; both versions apparently have problems with large
> > > documents. Stay tuned.
> >
> > Hmm. It appeared to help the users who were having the problems I saw.
>
> Oh? That's reassuring. I did a limited test about six months ago when
> someone reported some large-doc problems and I wasn't thrilled with the
> results.
>
>
>
