Closed Bug 51153 Opened 25 years ago Closed 17 years ago

Inconsistency in describing the mail/news part of Mozilla

Categories

(SeaMonkey :: MailNews: Message Display, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: bugzilla, Unassigned)

References

Details

(Keywords: helpwanted)

There seems to be some problems in naming the mail part of Mozilla: In "pref->appearance" it's called "Mozilla Mail" In "pref->Mail and Newsgroups" it's called "Mail" In "pref->Advanced" it's called "Mail and News" Please find one term. This bug has some other references: http://bugzilla.mozilla.org/show_bug.cgi?id=46314
lisa, could someone in mailnews fix these, or should this go to UI?
Assignee: matt → putterman
Component: Preferences → Mail Window Front End
Product: Browser → MailNews
QA Contact: sairuh → lchiang
wow, deja vu (after looking at bug 51154) --blake, would you like to own this, or should this stay in mailnews (or go to ui)?
Component: Mail Window Front End → Preferences
Product: MailNews → Browser
Summary: Inconsistency in describing the mail part of Mozilla → Inconsistency in describing the mail/news part of Mozilla
in both mac and win32 installer the component is called "Mail & News"
cc'ing jglick
Adding Robin Foster from Tech Pubs. Where ever possible, generic terms should be used. - If just referring to Mail, "Mail" should be used. - If just referring to Newsgroups, "Newsgroups" should be used. - If referring to the combined Mail/News component, "Mail and Newsgroups" should be used. If a qualifying product name is required "Netscape" or "Mozilla" should appear in front of the items mentioned above as appropriate.
okay
Assignee: putterman → blakeross
Are these the final names? So I can start making diff patch files to fix the inconsistency?
> Where ever possible, generic terms should be used. Really? If we are going to rename Messenger to `Mail and Newsgroups', are we also going to rename Navigator to `Web', and rename Composer to `HTML'? I can understand Netscape renaming their mailer, because `Netscape Messenger' is too close to `Netscape Instant Messenger'. And they have wittily decided to call their mail/news component `Mail', regardless of the fact that it also does news. Fine, that's up to them. But the same problem does not apply to Mozilla, since we don't have an IM app in the suite. (And if one was included, it would have an interesting brand name, like `Jabber' or something.) Ideally, Navigator, Composer, and {insert Mozilla mail/news component name here} will be distinct applications in future -- relying on the Mozilla base in library form only. And when someone asks me `What e-mail program do you use?', I don't want to have to say `I use Mail and Newsgroups'. They'll think I'm an idiot.
Matt, what newsreader do you use? ;)
I use Netscape Messenger right now, and I hope to upgrade to Mozilla Messenger in the near future. :-) If Mozilla's mail/news app is not going to be called `Messenger' any more, we should probably have a competition (along the lines of the one for the throbber) to decide on a new name which doesn't suck. And the Web pages on mozilla.org which refer to Messenger in relation to Mozilla (as opposed to 4.x) will need to be updated (I count about 110 such pages). And the `Mozilla Messenger' shortcut in the Mac Mozilla installation will need to be renamed. And the chrome/packages/messenger/ directory in a Mozilla installation will need to be renamed (causing all sorts of packaging fun, no doubt). And so on.
I never seen any mention about "Mozilla Messenger" inside the mozilla program...
Blocks: 47959
Perhaps that's because those inserting the wording have been concentrating on Netscape, rather than Mozilla, and (as this bug makes painfully obvious) the UI hasn't been inheriting product name &entities; from a single place.
Sorry if I wasn't clear before. Cc'ing Product Management to confirm naming conventions. For the Commercial product the *official* names of components are: Netscape Navigator, Netscape Mail, Netscape Instant Messenger, Netscape Address Book, Netscape Composer. I'm assuming for Mozilla the same is true but replacing "Netscape" with "Mozilla". So yes, someone could say "I use Netscape Mail" for email." The question raised by this bug was that we should we using consist terms in the products menus and dialogs. Within the product's menus and dialogs, it is not necessary to qualify with "Netscape" or "Mozilla" in front of the component names since that is a given. For example, the Tasks menu just says "Navigator", "Mail", etc., not "Netscape Navigator", "Netscape Mail", etc. Where ever possible, we should keep the names "Netscape" and "Mozilla" out of the menus and dialogs so more of these items can be shared without having to swap out names. Conventions used in the product: Tasks Menu: Navigator, Mail, Instant Messenger, Address Book, Composer. Search Menu: Search the Web, Search Bookmarks/History, Search Mail/News Messages Preferences: Navigator, Composer, Mail and Newsgroups
Sorry to be such a nuisance, but ... Does this mean that whenever Netscape decides to change the brand name of one of its applications (as it has for the mail/news application in this version), Mozilla will have to change the brand name of its own application to match??? If so, why? And if not, why are we doing so in this case?
My *opinion* would be that Mozilla can use whatever names they like, in this version and in future versions. If names can remain the same (in menus and dialogs where the "Netscape" or "Mozilla" qualifier aren't necessary), it just means less code changes between the two, if that is a concern.
Jen, your recommendations are solid. blakeross@telocity.com, please make it so...
p4 for M19
Status: NEW → ASSIGNED
Priority: P3 → P4
Target Milestone: --- → M19
jglick/kmurray - keep in mind that blake assigned this for M19. Netscape's UI freeze is before M19. The freeze is 9/14/00, I believe, so these changes will not be able to be made for Netscape's commercial build. I am not sure what applies to Mozilla so my comments don't apply there.
I vote for Messenger. We should bring this up in the newsgroup (.mail-news). Re code sharing: what Matthew said. We have functions to sets the brand name in one place. It is very important for Mozilla to actually use them everywhere, as an important target group for it are vendors. So, having different names for in Mozilla and Netscape helps Mozilla. I can see that this is not really necessary for N6.00. But if you fix this bug, please use the variables instead of hardcoding the name.
I can try to look at this this weekend. But if you want it ensure that it is immediately, it'll have to be nsbeta3+, as I have other, higher priority '+' bugs. Sorry.
Priority: P4 → P3
No problem, Blake. I thought the "+" for bugs are for helping schedule which bugs Netscape employees worked on.
*** Bug 52774 has been marked as a duplicate of this bug. ***
No time for this right now.
Assignee: blakeross → matt
Status: ASSIGNED → NEW
QA Contact: lchiang → sairuh
Target Milestone: M19 → ---
cc'ing mailnews folx who might be interested.
I've seen placeholder (technically: entities) all over the product, including pref overlays. Please use a placeholder like |&brandShortnameMailnews;|.
yes, entites eg shortname make sense.
Keywords: helpwanted
nav triage: not a netscape beta stopper.
Assignee: matt → blakeross
Keywords: nsbeta1nsbeta1-
passing back...
Assignee: blakeross → matt
-> mailnews.
Assignee: matt → sspitzer
Component: Preferences → Mail Window Front End
Product: Browser → MailNews
QA Contact: sairuh → esther
QA Contact: esther → nbaca
So, can we make a decision here? Or will this discussion go on forever?
Decide what? What the name of Mailnews will be? If so, do that on the newsgroups. But I don't think, we had good enough suggestions yet to make a final decision. The main thing to do in this bug is remove any name and replace it with a placeholder. That way, we can easily have "Mozilla Messenger" and "Netscape Mail and News", for example. No decision on the name needed to fix this bug.
After reading this bug is seems like we've settled on "Messenger", and when we need to be more specific: "Mozilla Messenger". This problem is too ugly to be in 1.0, so we gotta fix it before then.
Hakan, we don't need to settle on any name in order to fix this bug. See bug 84851.
Blocks: 84851
Just fix bug 84851 and then we can reconsider our choice of email client name. The most important thing right now is that we should not hardcode a name, and it should be consistent.
Hakan, I don't understand. Bug 84851 is a meta-bug, of which this bug (bug 51153) is a part. I.e. in order for bug 84851, we need to fix this one.
Product: Browser → Seamonkey
Assignee: sspitzer → mail
Assignee: mail → nobody
Priority: P3 → --
QA Contact: nbaca → message-display
All three are now "Mail & Newsgroups"
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.