FULL PRODUCT VERSION :
JD version 1.4.2_06

ADDITIONAL OS VERSION INFORMATION :
N/A
SUSE Linux 9.2, Kernel 2.6.9

A DESCRIPTION OF THE PROBLEM :
The time formatting strings for the en_au locale are for a 24 hour time format, which is wrong.

Review of localization data contained at the Unicode Consortion Common Locale Data Repository indicates that the locale should use 12 hour formatting strings with AM/PM indicators.

The IBM Globalization site, which had the original Talligent/Pink locale data contribution had the time format as 12 hour, but the time strings in 24 hour format. Consultation with

Thierry Mayeur
Senior Product Marketing Manager, Corporate Globalization Team
IBM Software Group, IBM Toronto Lab
8200 Warden Avenue
Markham, Ontario, L6G 1C7, Canada
Phone: (416) 410-5701

indicates the Talligent/Pink time format strings were in error. They should be in 12 hour format. IBM has indicated they will be correcting their document:

ftp://ftp.software.ibm.com/software/globalization/locales/Australia-English_Date.pdf



Additional information provided by residents of Australia indicate to me that the local custom is to display time formats in 12 hour format.



STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Use a DateForrmatter object for the locale en_AU to format a time variable.

EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
Time strings should be formatted per the custom of the locale, which is 12 hour format.
ACTUAL -
Time strings are formatted in 24 hour format.

REPRODUCIBILITY :
This bug can be reproduced always.

---------- BEGIN SOURCE ----------
{ "DateTimePatterns",
new String[] {
"hh:mm:ss a z", // full time pattern
"H:mm:ss", // long time pattern
"HH:mm:ss", // medium time pattern
"HH:mm", // short time pattern
"EEEE, d MMMM yyyy", // full date pattern
"d MMMM yyyy", // long date pattern
"d/MM/yyyy", // medium date pattern
"d/MM/yy", // short date pattern
"{1} {0}" // date-time pattern
}
---------- END SOURCE ----------