Closed
Bug 7609
Opened 28 years ago
Closed 24 years ago
text/plain is always handled by SimpleText
Categories
(Core Graveyard :: File Handling, defect, P1)
Tracking
(Not tracked)
VERIFIED
WONTFIX
People
(Reporter: francis, Unassigned)
References
()
Details
(This bug imported from BugSplat, Netscape's internal bugsystem. It
was known there as bug #70202
http://scopus.netscape.com/bugsplat/show_bug.cgi?id=70202
Imported into Bugzilla on 06/04/99 12:16)
text/plain is being passed to SimpleText. The Applications preference does not
permit me to select "Navigator internal" (although that's what's shows up in the
list); the default setting is "Unknown; prompt user"; and the setting is ignored
in any event--I tried telling it to pass it to Emacs instead (since SimpleText
can't handle anything over 32K), and it was still passed to SimpleText.
This is unacceptable because (a) SimpleText cannot handle files over 32K, and
(b) SimpleText does not handle bare LFs (it expects files to be in Mac format,
with bare CRs).
I believe this was with the released PR5.
Comment 1•28 years ago
|
||
Using the 6/4 build, I can set the helper for text/plain to be BBEdit. Perhaps
you are seeing the result of munged preferences. Could you try this with a
clean install? I don't know why you can't set Navigator internal, but I think
that is the subject of another bug, should you care to file it. This one is...
resolved as worksforme
I seriously doubt it was a munged prefs file, since I was running with a
brand-new user profile created just that day, with that same version of
Communicator.
I've still been seeing this happen, but only sometimes, and I finally figured
out the difference: with http: URLs, it works fine; with ftp: URLs, it spawns
off SimpleText. I see it regularly because the IETF stores RFCs and Drafts on
FTP sites instead of Web servers. This leads to the same problems I mentioned
before (no files over 32K, and it doesn't recognize \n).
This is in 4.04.
Comment 5•27 years ago
|
||
I don't think the ftp code can really pick up a mime encoding type from an ftp
server but it sounds like the default ftp handling for a text type file isn't
necessarily what we want. The initial place to look is msv2dsk.cp.
Scott, more pain.
Changing TFV to 5.0.
------- Additional Comments From paulmac Jun-04-1999 11:34 -------
marking resolved won't fix in old codebase - I will check this in seamonkey once
ftp is up to speed on Mac
Updated•25 years ago
|
QA Contact: paulmac → shrir
Comment 7•24 years ago
|
||
mid-air collision ? / bugzilla cleanup
Reopening (current State: resolved and no resolution)
Status: RESOLVED → REOPENED
Comment 8•24 years ago
|
||
wontfix
Status: REOPENED → RESOLVED
Closed: 24 years ago
Resolution: --- → WONTFIX
Assignee: scc-obsolete → nobody
Component: Plug-ins → File Handling
QA Contact: shrir → file-handling
Assignee | ||
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•