Closed Bug 38990 Opened 24 years ago Closed 23 years ago

Date format is not in localized format in the msg view pane

Categories

(MailNews Core :: Internationalization, defect, P3)

All
Windows NT
defect

Tracking

(Not tracked)

VERIFIED FIXED
mozilla0.9

People

(Reporter: ji, Assigned: mscott)

References

Details

(Keywords: l12y)

Please mark this as a dup if there is already a bug for it.

The date format in the thread pane is displayed in localized format on a
localized
system. But in the message view pane, the date is always in US format, like Wed,
11 May 2000.
Even with localized beta1, the date format is not correct.
>But in the message view pane, the date is always in US format, 
>like Wed, 11 May 2000.
This is also true for 4.x. Do we want to localize it?
It would be nice if we have the date format in the msg view pane consistent 
with the one displayed in the thread pane. 
If you look at 4.x, there are options "View" -> "Headers". "All", "Normal" and 
"Brief". So the view is supposed to display the headers as is (with MIME 
decoded). I think the same apply to mozilla.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
Yes, 4.x and mozilla are displaying the date in the msg view as it is after
MIME decoded. It might be confusing to display the date in a localized
format in the thread pane while showing the date in US format in the msg view
pane. Is it possible to do something after MIME decoded without bringing in too
much change in the code? I saw Outlook Express English version is displaying the
date in localized format both in the thread pane and msg view pane on a 
localized system.
If the purpose of this view is to show the headers as is then we should not 
localize. 
yes. Some users may just want to see the date and some may want to see more
information about the mail header.
To ji for verification.

We might want to re-open this bug. 
What Comuunicator does is similar in functonalities to 
Outlook Express:

1. Under Normal & Full view options, we show the RFC 822 headers
   as they are excpet for the names of these fields which could
   be localized. The date format is dictated by what the raw message
   has.

2. Under the brief view option, fields like Date, Organization, and
   References are not shown from the source. But if you look on the 
   right side of the view pane, you will see the date in "exactly the same
   format" as the thread pane view.

Outlook Express normally has only the equivalent of (2) above
minus the date. It does not show the date in their standard view
in the message pane. It show dates only in the thread pane. 

To get (1), the user has to open the properties dialog and
look at the "Details" tab for all the headers and source
for both the headers and bodies.

If the goal is to do something similar to Communicator, then
we should re-open this bug. But the header view menu options are
not enabled yet. We probably should check what the core
feature implementation will be like on this.

Looking at the current UI document, it seems that the date
might be visible in the message envelope at all times but
says nothing of the date/time format as far as I can see.

CC'ing jglick who wrote the UI spec for this area.
Jennifer, are you changing the date format to relfect the
system's preference setting in the brief view 
of the Envelope as it was done in Communicator?

http://gooey/client/5.0/specs/mail/messenger/messenger.html#Envelope


    

   
Status: RESOLVED → REOPENED
QA Contact: momoi → ji
Resolution: INVALID → ---
Status: REOPENED → ASSIGNED
Target Milestone: --- → M16
I accidentally accepted this bug. Since I cannot un-accept it at least clear the 
milestone.
Target Milestone: M16 → ---
Target Milestone: --- → M17
This is a REF, put M17 for not.
Can we assign this to whoever is implementing the Message
Envelope? If there is "Brief" view option and if it is to be
equivalent to Communicator, then date format should 
be sensitive to the user preference set for the OS.
>Can we assign this to whoever is implementing the Message Envelope? 
Reassign to selmer, this is RFE.
Assignee: nhotta → selmer
Status: ASSIGNED → NEW
Scott, looks like more fun for you...
Keywords: nsbeta2
I would recommend localizing the date unless the user does the equivalent of 
"view source".  The "Full" view may be such an equivalent, but the "Normal" view 
is not.

Localizing the date in the "Normal" view will reduce the desire for senders to 
violate RFC 822 by putting localized dates in the Date: header.
Putting on [nsbeta2-] radar. rjc, is this your bug?
Keywords: nsbeta3
Whiteboard: [nsbeta2-]
Not sure why this is assigned to me, thought it was mscott.  Did someone change
it back to me for some reason?  Changing owner to MScott (again?)
Assignee: selmer → mscott
Whiteboard: [nsbeta2-] → [nsbeta2-] [nsbeta3-]
Date field is displayed in "YY/MM/DD" in thread pane and
"MM/DD/YYYY" in message pane. It should be unified.

It should not be formatted as "MM/DD/YYYY" in [Headers]-[All] mode.
The other headers are displayed as they are in source file.
To update this bug, I would like to second jgmyers'
suggestion that under normal view we reflect the
system setting of the date format while keeping the
full view as the equivalent of View Source.
Keywords: intl
*** Bug 58198 has been marked as a duplicate of this bug. ***
Keywords: l12y
Keywords: mozilla1.0
Shouldn't the Mozilla locale date format be used, instead of the OS locale date 
format?
*** Bug 66949 has been marked as a duplicate of this bug. ***
Clearing very old milestone (M17) in hope of reevaluation.
Target Milestone: M17 → ---
nominating for nsbeta1
marking nsbeta1-.
Keywords: nsbeta1nsbeta1-
Whiteboard: [nsbeta2-] [nsbeta3-]
Works for me with 2001032704/Win2k.
I fixed this when I changed how we display the date in the message pane. I'm
using the locale when formatting the date.
Status: NEW → RESOLVED
Closed: 24 years ago23 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla0.9
Verified with 04/17 builds.
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.