-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P3
-
Affects Version/s: 1.2.0, 1.3.0, 1.3.0_02
-
Component/s: core-libs
-
beta2
-
generic, x86, sparc
-
generic, solaris_2.5, windows_nt, windows_2000
TimeZone spec:
If the time zone you want is not represented by one of the supported IDs,
then you can create a custom time zone ID with the following syntax:
GMT[+|-]hh[[:]mm]
However, the specified custom ID value is not used for a custom TimeZone object, but "Custom" is always given as its ID. So, there is no way to identify a custom TimeZone object using the custom ID.
Also, the syntax should be:
GMT{+|-}hh[[:]mm]
'+' or '-' is required after "GMT".
SimpleDateFormat spec:
For time zones that have no names, use strings GMT+hours:minutes or
GMT-hours:minutes.
However, SimpleDateFormat.parse accepts other formats, such as GMT+hhmm, +hhmm (RFC822-style), etc. It needs to clarify the spec.
If the time zone you want is not represented by one of the supported IDs,
then you can create a custom time zone ID with the following syntax:
GMT[+|-]hh[[:]mm]
However, the specified custom ID value is not used for a custom TimeZone object, but "Custom" is always given as its ID. So, there is no way to identify a custom TimeZone object using the custom ID.
Also, the syntax should be:
GMT{+|-}hh[[:]mm]
'+' or '-' is required after "GMT".
SimpleDateFormat spec:
For time zones that have no names, use strings GMT+hours:minutes or
GMT-hours:minutes.
However, SimpleDateFormat.parse accepts other formats, such as GMT+hhmm, +hhmm (RFC822-style), etc. It needs to clarify the spec.
- duplicates
-
-
- Closed
-
-
-
- Closed
-
- relates to
-
-
- Resolved
-
-
-
- Closed
-