Closed Bug 218558 Opened 22 years ago Closed 12 years ago

Change Default "Reply Header" to show Name First

Categories

(MailNews Core :: Composition, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: Peter, Unassigned)

References

(Depends on 1 open bug)

Details

An annoying thing on the current reply header, is that it shows the Date first. So when you see a message with several replies listed (and nested) at the top, you see a bunch of dates, and hav to read INTO the "Reply Header" to FIND the name of the person that previously posted. since the Name is (IMO) more relevant than the date, the name should be at the BEGINNING of the reply header. Suggest to change the reply header to: 1. have the name first 2. have the date second 3. to keep the header line as SHORT as possible Suggested Reply Header: Peter@Lairo said on 06.09.03 23:31: > bla bla bla Implementation could be as easy as making the following the defaul: // Change the reply header // 0 - No Reply-Text // 1 - "[Author] wrote:" // 2 - "On [date] [author] wrote:" // 3 - User-defined reply header. Use the prefs below in conjuction with this: user_pref("mailnews.reply_header_type", 3); // If you set 3 for the pref above then you may set the following prefs. user_pref("mailnews.reply_header_authorwrote", "%s said"); user_pref("mailnews.reply_header_ondate", "on %s"); user_pref("mailnews.reply_header_separator", " "); user_pref("mailnews.reply_header_colon", ":"); // The end result will be [authorwrote][separator][ondate][colon]
QA Contact: asa
Setting the reply_header_type value to 3 does put the name first. Those other prefs mentioned apply for modes 1, 2, and 3. http://www.holgermetzger.de/efaqmailnews.html#6
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
This bug is asking to change the *default* setting. Reopening. BTW: We should add "at" before the time. Reason: The "on" before the date doesn't realy apply to "time" (i.e., "on 16:45" is incorrect). It would also make it much easier to read (i.e., visually differentiate between the date "numbers" and the time "numbers"). This should happen regardless if "reply_header_type", 3" becomes the default (this bug) or not. So the header should read: Peter@Lairo said on 06.09.03 at 23:31:
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Reply headers are core functionality, moving.
Component: Message Compose Window → MailNews: Composition
Product: Thunderbird → Core
Version: unspecified → Trunk
Assignee: mscott → nobody
Status: REOPENED → NEW
QA Contact: composition
Product: Core → MailNews Core
Flags: wanted1.9.2?
Flags: wanted-thunderbird3?
Flags: wanted-seamonkey2?
Not a priority.
Flags: wanted-seamonkey2? → wanted-seamonkey2-
(In reply to comment #4) > Not a priority. Agreed
Flags: wanted1.9.2?
Flags: wanted-thunderbird3?
The BTW in comment 2 going to be allowed by bug 995797. This bug with current summary is about which of the options should be the default: // 0 - No Reply-Text (the -- // 1 - "[Author] wrote:" // 2 - "On [date] [time], [author] wrote:" // 3 - "[author] wrote on [date] [time]:" If we want to change it to "On [date] at [time]" for English version then we can also do it in this bug. UX thoughts?
Assignee: nobody → acelists
Flags: needinfo?(josiah)
Flags: needinfo?(bwinton)
I don't want to change the default, but I'm neutral on the "at" addition. (Mainly because the the wording of 3 is really awkward.)
I'm also -1 on changing the default, and neutral on the "at" addition.
Flags: needinfo?(bwinton)
Yep, I disagree with changing the default as well and am not a fan of the "at" addition. Therefore, I'm going to go ahead and WONTFIX the bug. People can always change the prefs if it bothers them.
Status: NEW → RESOLVED
Closed: 21 years ago12 years ago
Flags: needinfo?(josiah)
Resolution: --- → WONTFIX
OK, thanks. The biggest improvement is that bug 995797 will allow to add that 'at' for users and whole languages where it is more important than in English.
Assignee: acelists → nobody
You need to log in before you can comment on or make changes to this bug.