[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[commit-cp] Re: [bugs #11780] zoneStrings in gnu/java/locale/LocaleInfor
From: |
Ito Kazumitsu |
Subject: |
[commit-cp] Re: [bugs #11780] zoneStrings in gnu/java/locale/LocaleInformation* seem to be broken |
Date: |
31 Jan 2005 10:02:07 +0900 |
User-agent: |
SEMI/1.14.6 (Maruoka) FLIM/1.14.7 (Sanjō) APEL/10.6 Emacs/21.3.50 (i686-pc-cygwin) MULE/5.0 (SAKAKI) |
In message "[bugs #11780] zoneStrings in gnu/java/locale/LocaleInformation*
seem to be broken"
on 05/01/30, Andrew John Hughes <address@hidden> writes:
> At present, lots of sets with empty strings for all but the id are generated
> (e.g. "America/Los Angeles", "", "", "", ""). Is this correct, or should
> this be filtered out of the finished version?
Let's see what Sun's JDK outputs.
import java.text.DateFormatSymbols;
public class ListZoneStrings {
public static void main(String[] main) {
DateFormatSymbols dfs = new DateFormatSymbols();
String[][] ss = dfs.getZoneStrings();
for (int i=0; i < ss.length; i++) {
for (int j=0; j < ss[i].length; j++) {
System.out.print(ss[i][j] + "\t");
}
System.out.println();
System.out.println("-------");
}
}
}
The output has both
PST Pacific Standard Time PST Pacific Daylight Time PDT
and
America/Los_Angeles Pacific Standard Time PST Pacific Daylight Time
PDT