Closed Bug 365868 Opened 18 years ago Closed 18 years ago

Thunderbird partially ignores OS date and time format from international settings

Categories

(Thunderbird :: Mail Window Front End, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 360018

People

(Reporter: s.marshall, Assigned: mscott)

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1
Build Identifier: version 1.5.0.9 (20061207)

(This may be a duplicate of bug 253883, but I wasn't sure; I think this particular issue might be Mac-specific, maybe even 10.3-specific.)

I am using Mac OS X 10.3. In System Preferences under 'International / Formats', my date format is shown as follows:

Region: United Kingdom

Dates: 
Tuesday, 2 January 2007 
2 Jan 2007
02/01/2007

Times:
00:34   16:56

Most applications follow this format or some variant of it. For example, the system clock says 'Thu 01:26'.


Thunderbird, however, displays message dates as follows:

3/1/07 8:58 pm 
(message from 3 January)

10:36 pm
(message today)

If I alter configuration using about:config I can also access the third 'full date' option, which looks like:

Thu, Sep 30, 2004 10:47 am

In all cases the time is incorrectly displayed with am/pm. However, in the first example above the date is ordered according to UK style (d/m/yy), so *something* appears to be working.

Reproducible: Always

Steps to Reproduce:
With international settings as described, look at message date.
Actual Results:  
3/1/07 8:58 pm 

Expected Results:  
3/1/07 20:58, or 03/01/2007 20:58, or somesuch - definitely no AM/PM.

I have no extensions installed. I haven't tried to reproduce this with a clean profile or anything (not sure how to, to be honest).
Perhaps, it is dup to bug360018. 
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
This is not quite the same as bug 360018 because in this bug, the order of the date fields (DD/MM/YYYY) is correct. It is the time field that's displayed incorrectly (am/pm). However it is probably the same root problem so I'm not going to argue with the dup marking.
You need to log in before you can comment on or make changes to this bug.