239119 - Date displayed in wrong format

Status: RESOLVED EXPIRED

(MailNews Core :: Internationalization, defect)

Description

[John]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030716 Debian/1.4-2.0.1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030716 Debian/1.4-2.0.1

In Mozilla Mail, I have a list of mail in one of my mail boxes.

My system is localised to Perth, Western Australia, and I expect to see the
timezone as WST, paper size A4, currency Dollars and dates as dd/mm/yy.

Instead, dates are formatted mm/dd/yy and this is extrememly confusing.



Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Comment 1

[R.K.Aa.]

what does "echo $LC_TIME" show?
If nothing (or a locale with wrong time) put this in your .bashrc or whatever:

export LC_TIME="en_UK"

After logging out and in again, time should display correct:
Mozilla - like old Netscape - honor locales.

Comment 2

[R.K.Aa.]

or even better:

export LC_TIME="en_AU"

Comment 3

[Christian :Biesinger (don't email me, ping me on IRC)]

What does "locale" output?

Comment 4

[Shoshannah Forbes]

perhaps this is similar to bug #236147?

Comment 5

[Constantine A. Murenin]

I think, we need to write a document about Date/Time handling in Mozilla,
including trouble-shooting. :-)

John, from the same place you start Mozilla (i.e., from the same console),
please write the output of the following command: 

date +"%c --- %x %X"

If the thing in place of %x shows the date incorrectly, then this bug most
likely needs to be closed as invalid (and the problem needs to be reported to
the vendor of the OS/distribution) or as a duplicate of bug #238109 (Mozilla
does not honour KDE settings).

Mozilla just uses the same value as the preceding command uses, therefore, if
the command's output is incorrect, so will mozilla's date and time be. 

Comment 6

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 7

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.