Closed Bug 58740 Opened 24 years ago Closed 15 years ago

use mailnews instead of messenger - messenger is a Netscape product name

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
All
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: mkaply, Unassigned)

Details

Attachments

(2 files)

This is just a humble request. All the jars are 8.3 except messenger. Could we possibly call it mailnews.jar? Thanks
There's no reason that I know of not to.
Attached patch proposed patch. (deleted) — Splinter Review
putterman: Could we get an r= on this?
Keywords: patch, review
Assignee: putterman → sspitzer
reassigning to sspitzer.
testing and reviewing this now. thanks for the patch.
Status: NEW → ASSIGNED
this patch is incomplete, we need to fix the mozilla/xpinstall/packager/packages-* files too. I'll post a new patch as soon as I'm done testing & reviewing this one.
there are a few other places we may need to change as well. note, even if we make messenger.jar mailnews.jar, we'll still be extracting to a folder named "messenger". is that a problem for OS/2?
I think more work needs to be done. for example, what about the mozilla/xpinstall/packager/package-* and mozilla/xpinstall/packager/*/mail.jst files?
Attached patch patch for mailnews.jar (deleted) — Splinter Review
apologies to timeless (for not getting to his patch yet). I need to work on all three platforms and fix the commercial tree to fix this. I'll get to it, I promise. mkaply, without this fix will mail not work on OS/2?
Right now, the OS/2 version requires a long file name system, but we are in the planning stages for possibly creating a version that works on 8.3. So the more files we have 8.3 to begin with, the better off we are. The reason I picked on this JAR was twofold - 1. It's the only non 8.3 JAR, and 2. Messenger is the Netscape name, mailnews is the Mozilla name. :) So this is mainly a convenience issue, but we would really like it.
Michael Kaply, what's the status of the 8.3 version for OS/2? There are now more non-8.3 jars around ('chatzilla.jar',...). Does this bug still make sense? I guess if at all, then because of comment #11: "Messenger is the Netscape name, mailnews is the Mozilla name."...
We don't need this anymore, we have given up on an 8.3. I agree with the comment 11 statement though. Messenger is a product name. It should really be called mailnews.jar
Then maybe the summary of this bug should be changed...
Attachment #21002 - Flags: superreview?(sspitzer)
Attachment #21002 - Flags: review?(sspitzer)
Summary: Please use an 8.3 name for messenger.jar → use mailnews instead of messenger - messenger is a Netscape product name
Shall this still be done, now that Netscape isn't anymore?
Attachment #21002 - Flags: superreview?(sspitzer)
Attachment #21002 - Flags: review?(sspitzer)
Don't forget the packaging - chrome://messenger/content/messenger.xul becomes chrome://mailnews/content/mailnews.xul and similarly for skin/messenger.css locale/messenger.dtd and locale/messenger.properties And you get to break every extension at once :-)
Product: Browser → Seamonkey
Assignee: sspitzer → mail
Status: ASSIGNED → NEW
Assignee: mail → nobody
Priority: P3 → --
QA Contact: esther → message-display
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago. Because of this, we're resolving the bug as EXPIRED. If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component. Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → EXPIRED
No point in doing this. Xref bug 513527.
Resolution: EXPIRED → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: