From c771fc444f2338479b29e0eeea70e94fec13f154 Mon Sep 17 00:00:00 2001 From: Rich Gillam Date: Wed, 13 Mar 2024 17:06:14 -0700 Subject: [PATCH] ICU-22523 Cut down the large tables in the APIs docs for SimpleDateFormat and included a link to the full table in the LDML spec. --- icu4c/source/i18n/unicode/smpdtfmt.h | 372 +---------------- .../com/ibm/icu/text/SimpleDateFormat.java | 377 +----------------- 2 files changed, 35 insertions(+), 714 deletions(-) diff --git a/icu4c/source/i18n/unicode/smpdtfmt.h b/icu4c/source/i18n/unicode/smpdtfmt.h index 31b16bd46b1..a37485a93de 100644 --- a/icu4c/source/i18n/unicode/smpdtfmt.h +++ b/icu4c/source/i18n/unicode/smpdtfmt.h @@ -69,7 +69,8 @@ class SimpleNumberFormatter; * getDateInstance(), getDateInstance(), or getDateTimeInstance() rather than * explicitly constructing an instance of SimpleDateFormat. This way, the client * is guaranteed to get an appropriate formatting pattern for whatever locale the - * program is running in. However, if the client needs something more unusual than + * program is running in. If the client needs more control, they should consider using + * DateFormat::createInstanceForSkeleton(). However, if the client needs something more unusual than * the default patterns in the locales, he can construct a SimpleDateFormat directly * and give it an appropriate pattern (or use one of the factory methods on DateFormat * and modify the pattern after the fact with toPattern() and applyPattern(). @@ -77,46 +78,32 @@ class SimpleNumberFormatter; *

Date and Time Patterns:

* *

Date and time formats are specified by date and time pattern strings. + * The full syntax for date and time patterns can be found at + * https://unicode.org/reports/tr35/tr35-dates.html#Date_Format_Patterns. + * * Within date and time pattern strings, all unquoted ASCII letters [A-Za-z] are reserved - * as pattern letters representing calendar fields. SimpleDateFormat supports - * the date and time formatting algorithm and pattern letters defined by - * UTS#35 - * Unicode Locale Data Markup Language (LDML) and further documented for ICU in the - * ICU - * User Guide. The following pattern letters are currently available (note that the actual - * values depend on CLDR and may change from the examples shown here):

+ * as pattern letters representing calendar fields. Some of the most commonly used pattern letters are:

* * * - * * * * * * * - * - * + * * * - * * * - * - * - * - * - * - * - * - * - * * * * *
FieldSym.No.ExampleDescription
eraGG1..3ADEra - Replaced with the Era string for the current date. One to three letters for the + * Era - Replaced with the Era string for the current date. One to three letters for the * abbreviated form, four letters for the long (wide) form, five for the narrow form.
4Anno Domini
5A
yeary1..n1996Year. Normally the length specifies the padding, but for two letters it also specifies the maximum - * length. Example:
+ * length. Example:
*
* * @@ -172,49 +159,11 @@ class SimpleNumberFormatter; * * * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * * * * - * + * * * * @@ -225,28 +174,12 @@ class SimpleNumberFormatter; * * * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * * * * * + * if necessary (e.g. "08"). * * * @@ -261,41 +194,6 @@ class SimpleNumberFormatter; * * * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * * * * @@ -303,29 +201,6 @@ class SimpleNumberFormatter; * two digits (zero-padding if necessary, e.g. "08"). * * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * * * * @@ -345,61 +220,12 @@ class SimpleNumberFormatter; * * * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * * * * * * * - * * * * @@ -416,27 +242,13 @@ class SimpleNumberFormatter; * 12-hour-cycle format (h or K). Use HH for zero padding. * * - * - * - * - * - * - * - * - * - * - * - * - * - * * * * * + * (zero-padding if necessary, e.g. "08").. * * - * * * * @@ -444,28 +256,10 @@ class SimpleNumberFormatter; * (zero-padding if necessary, e.g. "08"). * * - * - * - * - * - * - * - * - * - * - * - * - * - * * * * - * * * @@ -475,43 +269,10 @@ class SimpleNumberFormatter; * Where that is unavailable, falls back to the long localized GMT format ("OOOO"). * * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * * * * - * * @@ -521,109 +282,6 @@ class SimpleNumberFormatter; * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * *
Y1..n1997Year (in "Week of Year" based calendars). Normally the length specifies the padding, - * but for two letters it also specifies the maximum length. This year designation is used in ISO - * year-week calendar as defined by ISO 8601, but can be used in non-Gregorian based calendar systems - * where week date processing is desired. May not always be the same value as calendar year.
u1..n4601Extended year. This is a single number designating the year of this calendar system, encompassing - * all supra-year fields. For example, for the Julian calendar system, year numbers are positive, with an - * era of BCE or CE. An extended year value for the Julian calendar system assigns positive values to CE - * years and negative values to BCE years, with 1 BCE being year 0.
U1..3甲子Cyclic year name. Calendars such as the Chinese lunar calendar (and related calendars) - * and the Hindu calendars use 60-year cycles of year names. Use one through three letters for the abbreviated - * name, four for the full (wide) name, or five for the narrow name (currently the data only provides abbreviated names, - * which will be used for all requested name widths). If the calendar does not provide cyclic year name data, - * or if the year value to be formatted is out of the range of years for which cyclic name data is provided, - * then numeric formatting is used (behaves like 'y').
4(currently also 甲子)
5(currently also 甲子)
quarterQ1..202Quarter - Use one or two for the numerical quarter, three for the abbreviation, or four for the - * full (wide) name (five for the narrow name is not yet supported).Quarter - Use one or two for the numerical quarter, three for the abbreviation, or four + * for the full (wide) name (five for the narrow name is not yet supported).
32nd quarter
q1..202Stand-Alone Quarter - Use one or two for the numerical quarter, three for the abbreviation, - * or four for the full name (five for the narrow name is not yet supported).
3Q2
42nd quarter
monthM1..209Month - Use one or two for the numerical month, three for the abbreviation, four for * the full (wide) name, or five for the narrow name. With two ("MM"), the month number is zero-padded - * if necessary (e.g. "08")
3S
L1..209Stand-Alone Month - Use one or two for the numerical month, three for the abbreviation, - * four for the full (wide) name, or 5 for the narrow name. With two ("LL"), the month number is zero-padded if - * necessary (e.g. "08")
3Sep
4September
5S
weekw1..227Week of Year. Use "w" to show the minimum number of digits, or "ww" to always show two digits - * (zero-padding if necessary, e.g. "08").
W13Week of Month
dayd1..21
D1..3345Day of year
F12Day of Week in Month. The example is for the 2nd Wed in July
g1..n2451334Modified Julian day. This is different from the conventional Julian day number in two regards. - * First, it demarcates days at local zone midnight, rather than noon GMT. Second, it is a local number; - * that is, it depends on the local time zone. It can be thought of as a single number that encompasses - * all the date-related fields.
week
- * day		E1..3TueTu
e1..22Local day of week. Same as E except adds a numeric value that will depend on the local - * starting day of the week, using one or two letters. For this example, Monday is the first day of the week.
3Tue
4Tuesday
5T
6Tu
c12Stand-Alone local day of week - Use one letter for the local numeric value (same - * as 'e'), three for the short day, four for the full (wide) name, five for the narrow name, or six for - * the short name.
3Tue
4Tuesday
5T
6Tu
perioda1AMAM or PM
hourh1..211
K1..20Hour [0-11]. When used in a skeleton, only matches K or h, see above. Use KK for zero padding.
k1..224Hour [1-24]. When used in a skeleton, only matches k or H, see above. Use kk for zero padding.
minutem1..259Minute. Use "m" to show the minimum number of digits, or "mm" to always show two digits - * (zero-padding if necessary, e.g. "08").
seconds1..212
S1..n3450Fractional Second - truncates (like other time fields) to the count of letters when formatting. - * Appends zeros if more than 3 letters specified. Truncates at three significant digits when parsing. - * (example shows display using pattern SSSS for seconds value 12.34567)
A1..n69540000Milliseconds in day. This field behaves exactly like a composite of all time-related fields, - * not including the zone fields. As such, it also reflects discontinuities of those fields on DST transition - * days. On a day of DST onset, it will jump forward. On a day of DST cessation, it will jump backward. This - * reflects the fact that is must be combined with the offset field to obtain a unique local time value.
zonez1..3PDTThe short specific non-location format. + * Time zone. The short specific non-location format. * Where that is unavailable, falls back to the short localized GMT format ("O").
Z1..3-0800The ISO8601 basic format with hours, minutes and optional seconds fields. - * The format is equivalent to RFC 822 zone format (when optional seconds field is absent). - * This is equivalent to the "xxxx" specifier.
4GMT-8:00The long localized GMT format. - * This is equivalent to the "OOOO" specifier.
5-08:00
- * -07:52:58		The ISO8601 extended format with hours, minutes and optional seconds fields. - * The ISO8601 UTC indicator "Z" is used when local time offset is 0. - * This is equivalent to the "XXXXX" specifier.
O1GMT-8The short localized GMT format.
4GMT-08:00The long localized GMT format.
v1PTThe short generic non-location format. + * Time zone. The short generic non-location format. * Where that is unavailable, falls back to the generic location format ("VVVV"), * then the short localized GMT format as the final fallback.
The long generic non-location format. * Where that is unavailable, falls back to generic location format ("VVVV"). *
V1uslaxThe short time zone ID. - * Where that is unavailable, the special short time zone ID unk (Unknown Zone) is used.
- * Note: This specifier was originally used for a variant of the short specific non-location format, - * but it was deprecated in the later version of the LDML specification. In CLDR 23/ICU 51, the definition of - * the specifier was changed to designate a short time zone ID.
2America/Los_AngelesThe long time zone ID.
3Los AngelesThe exemplar city (location) for the time zone. - * Where that is unavailable, the localized exemplar city name for the special zone Etc/Unknown is used - * as the fallback (for example, "Unknown City").
4Los Angeles TimeThe generic location format. - * Where that is unavailable, falls back to the long localized GMT format ("OOOO"; - * Note: Fallback is only necessary with a GMT-style Time Zone ID, like Etc/GMT-830.)
- * This is especially useful when presenting possible timezone choices for user selection, - * since the naming is more uniform than the "v" format.
X1-08
- * +0530
- * Z		The ISO8601 basic format with hours field and optional minutes field. - * The ISO8601 UTC indicator "Z" is used when local time offset is 0.
2-0800
- * Z		The ISO8601 basic format with hours and minutes fields. - * The ISO8601 UTC indicator "Z" is used when local time offset is 0.
3-08:00
- * Z		The ISO8601 extended format with hours and minutes fields. - * The ISO8601 UTC indicator "Z" is used when local time offset is 0.
4-0800
- * -075258
- * Z		The ISO8601 basic format with hours, minutes and optional seconds fields. - * (Note: The seconds field is not supported by the ISO8601 specification.) - * The ISO8601 UTC indicator "Z" is used when local time offset is 0.
5-08:00
- * -07:52:58
- * Z		The ISO8601 extended format with hours, minutes and optional seconds fields. - * (Note: The seconds field is not supported by the ISO8601 specification.) - * The ISO8601 UTC indicator "Z" is used when local time offset is 0.
x1-08
- * +0530		The ISO8601 basic format with hours field and optional minutes field.
2-0800The ISO8601 basic format with hours and minutes fields.
3-08:00The ISO8601 extended format with hours and minutes fields.
4-0800
- * -075258		The ISO8601 basic format with hours, minutes and optional seconds fields. - * (Note: The seconds field is not supported by the ISO8601 specification.)
5-08:00
- * -07:52:58		The ISO8601 extended format with hours, minutes and optional seconds fields. - * (Note: The seconds field is not supported by the ISO8601 specification.)
* *

diff --git a/icu4j/main/core/src/main/java/com/ibm/icu/text/SimpleDateFormat.java b/icu4j/main/core/src/main/java/com/ibm/icu/text/SimpleDateFormat.java index d2dadeb7418..49f6a231da8 100644 --- a/icu4j/main/core/src/main/java/com/ibm/icu/text/SimpleDateFormat.java +++ b/icu4j/main/core/src/main/java/com/ibm/icu/text/SimpleDateFormat.java @@ -57,53 +57,44 @@ import com.ibm.icu.util.UResourceBundle; * (date -> text), parsing (text -> date), and normalization. * *

- * SimpleDateFormat allows you to start by choosing - * any user-defined patterns for date-time formatting. However, you - * are encouraged to create a date-time formatter with either - * getTimeInstance, getDateInstance, or - * getDateTimeInstance in DateFormat. Each - * of these class methods can return a date/time formatter initialized - * with a default format pattern. You may modify the format pattern - * using the applyPattern methods as desired. + * Clients are encouraged to create a date-time formatter using + * DateFormat.getDateInstance(), DateFormat.getDateInstance(), + * or DateFormat.getDateTimeInstance() rather than + * explicitly constructing an instance of SimpleDateFormat. This way, the client + * is guaranteed to get an appropriate formatting pattern for whatever locale the + * program is running in. If the client needs more control, they should consider using + * DateFormat.getInstanceForSkeleton(). + * However, if the client needs something more unusual than + * the default patterns in the locales, he can construct a SimpleDateFormat directly + * and give it an appropriate pattern (or use one of the factory methods on DateFormat + * and modify the pattern after the fact with toPattern() and applyPattern(). * For more information on using these methods, see * {@link DateFormat}. * *

Date and Time Patterns:

* *

Date and time formats are specified by date and time pattern strings. - * Within date and time pattern strings, all unquoted ASCII letters [A-Za-z] are reserved - * as pattern letters representing calendar fields. SimpleDateFormat supports - * the date and time formatting algorithm and pattern letters defined by UTS#35 - * Unicode Locale Data Markup Language (LDML). The following pattern letters are - * currently available (note that the actual values depend on CLDR and may change from the - * examples shown here):

+ * The full syntax for date and time patterns can be found at + * https://unicode.org/reports/tr35/tr35-dates.html#Date_Format_Patterns.

+ * + *

Within date and time pattern strings, all unquoted ASCII letters [A-Za-z] are reserved + * as pattern letters representing calendar fields. Some of the most commonly used pattern letters are:

*
* * - * * * * * * * - * - * + * * * - * * * - * - * - * - * - * - * - * - * - * * * * @@ -164,44 +155,6 @@ import com.ibm.icu.util.UResourceBundle; * * * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * * * * @@ -217,22 +170,6 @@ import com.ibm.icu.util.UResourceBundle; * * * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * * * * @@ -253,41 +190,6 @@ import com.ibm.icu.util.UResourceBundle; * * * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * * * * @@ -295,29 +197,6 @@ import com.ibm.icu.util.UResourceBundle; * two digits (zero-padding if necessary, e.g. "08"). * * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * * * * @@ -337,61 +216,12 @@ import com.ibm.icu.util.UResourceBundle; * * * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * * * * * * * - * * * * @@ -408,19 +238,6 @@ import com.ibm.icu.util.UResourceBundle; * 12-hour-cycle format (h or K). Use HH for zero padding. * * - * - * - * - * - * - * - * - * - * - * - * - * - * * * * @@ -428,7 +245,6 @@ import com.ibm.icu.util.UResourceBundle; * (zero-padding if necessary, e.g. "08").. * * - * * * * @@ -436,27 +252,10 @@ import com.ibm.icu.util.UResourceBundle; * (zero-padding if necessary, e.g. "08"). * * - * - * - * - * - * - * - * - * - * - * - * - * - * * * * - * * * @@ -466,43 +265,10 @@ import com.ibm.icu.util.UResourceBundle; * Where that is unavailable, falls back to the long localized GMT format ("OOOO"). * * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * * * * - * * @@ -512,109 +278,6 @@ import com.ibm.icu.util.UResourceBundle; * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * - * *
FieldSym.No.ExampleDescription
eraGG1..3ADEra - Replaced with the Era string for the current date. One to three letters for the + * Era - Replaced with the Era string for the current date. One to three letters for the * abbreviated form, four letters for the long (wide) form, five for the narrow form.
4Anno Domini
5A
yeary1..n1996
Y1..n1997Year (in "Week of Year" based calendars). Normally the length specifies the padding, - * but for two letters it also specifies the maximum length. This year designation is used in ISO - * year-week calendar as defined by ISO 8601, but can be used in non-Gregorian based calendar systems - * where week date processing is desired. May not always be the same value as calendar year.
u1..n4601Extended year. This is a single number designating the year of this calendar system, encompassing - * all supra-year fields. For example, for the Julian calendar system, year numbers are positive, with an - * era of BCE or CE. An extended year value for the Julian calendar system assigns positive values to CE - * years and negative values to BCE years, with 1 BCE being year 0.
U1..3甲子Cyclic year name. Calendars such as the Chinese lunar calendar (and related calendars) - * and the Hindu calendars use 60-year cycles of year names. Use one through three letters for the abbreviated - * name, four for the full (wide) name, or five for the narrow name (currently the data only provides abbreviated names, - * which will be used for all requested name widths). If the calendar does not provide cyclic year name data, - * or if the year value to be formatted is out of the range of years for which cyclic name data is provided, - * then numeric formatting is used (behaves like 'y').
4(currently also 甲子)
5(currently also 甲子)
quarterQ1..2022nd quarter
q1..202Stand-Alone Quarter - Use one or two for the numerical quarter, three for the abbreviation, - * or four for the full name (five for the narrow name is not yet supported).
3Q2
42nd quarter
monthM1..209S
L1..209Stand-Alone Month - Use one or two for the numerical month, three for the abbreviation, - * four for the full (wide) name, or 5 for the narrow name. With two ("LL"), the month number is zero-padded if - * necessary (e.g. "08").
3Sep
4September
5S
weekw1..227Week of Year. Use "w" to show the minimum number of digits, or "ww" to always show two digits - * (zero-padding if necessary, e.g. "08").
W13Week of Month
dayd1..21
D1..3345Day of year
F12Day of Week in Month. The example is for the 2nd Wed in July
g1..n2451334Modified Julian day. This is different from the conventional Julian day number in two regards. - * First, it demarcates days at local zone midnight, rather than noon GMT. Second, it is a local number; - * that is, it depends on the local time zone. It can be thought of as a single number that encompasses - * all the date-related fields.
week
- * day		E1..3TueTu
e1..22Local day of week. Same as E except adds a numeric value that will depend on the local - * starting day of the week, using one or two letters. For this example, Monday is the first day of the week.
3Tue
4Tuesday
5T
6Tu
c12Stand-Alone local day of week - Use one letter for the local numeric value (same - * as 'e'), three for the short day, four for the full (wide) name, five for the narrow name, or six for - * the short name.
3Tue
4Tuesday
5T
6Tu
perioda1AMAM or PM
hourh1..211
K1..20Hour [0-11]. When used in a skeleton, only matches K or h, see above. Use KK for zero padding.
k1..224Hour [1-24]. When used in a skeleton, only matches k or H, see above. Use kk for zero padding.
minutem1..259
seconds1..212
S1..n3450Fractional Second - truncates (like other time fields) to the count of letters when formatting. Appends zeros if more than 3 letters specified. Truncates at three significant digits when parsing. - * (example shows display using pattern SSSS for seconds value 12.34567)
A1..n69540000Milliseconds in day. This field behaves exactly like a composite of all time-related fields, - * not including the zone fields. As such, it also reflects discontinuities of those fields on DST transition - * days. On a day of DST onset, it will jump forward. On a day of DST cessation, it will jump backward. This - * reflects the fact that is must be combined with the offset field to obtain a unique local time value.
zonez1..3PDTThe short specific non-location format. + * Time zone. The short specific non-location format. * Where that is unavailable, falls back to the short localized GMT format ("O").
Z1..3-0800The ISO8601 basic format with hours, minutes and optional seconds fields. - * The format is equivalent to RFC 822 zone format (when optional seconds field is absent). - * This is equivalent to the "xxxx" specifier.
4GMT-8:00The long localized GMT format. - * This is equivalent to the "OOOO" specifier.
5-08:00
- * -07:52:58		The ISO8601 extended format with hours, minutes and optional seconds fields. - * The ISO8601 UTC indicator "Z" is used when local time offset is 0. - * This is equivalent to the "XXXXX" specifier.
O1GMT-8The short localized GMT format.
4GMT-08:00The long localized GMT format.
v1PTThe short generic non-location format. + * Time zone. The short generic non-location format. * Where that is unavailable, falls back to the generic location format ("VVVV"), * then the short localized GMT format as the final fallback.
The long generic non-location format. * Where that is unavailable, falls back to generic location format ("VVVV"). *
V1uslaxThe short time zone ID. - * Where that is unavailable, the special short time zone ID unk (Unknown Zone) is used.
- * Note: This specifier was originally used for a variant of the short specific non-location format, - * but it was deprecated in the later version of the LDML specification. In CLDR 23/ICU 51, the definition of - * the specifier was changed to designate a short time zone ID.
2America/Los_AngelesThe long time zone ID.
3Los AngelesThe exemplar city (location) for the time zone. - * Where that is unavailable, the localized exemplar city name for the special zone Etc/Unknown is used - * as the fallback (for example, "Unknown City").
4Los Angeles TimeThe generic location format. - * Where that is unavailable, falls back to the long localized GMT format ("OOOO"; - * Note: Fallback is only necessary with a GMT-style Time Zone ID, like Etc/GMT-830.)
- * This is especially useful when presenting possible timezone choices for user selection, - * since the naming is more uniform than the "v" format.
X1-08
- * +0530
- * Z		The ISO8601 basic format with hours field and optional minutes field. - * The ISO8601 UTC indicator "Z" is used when local time offset is 0.
2-0800
- * Z		The ISO8601 basic format with hours and minutes fields. - * The ISO8601 UTC indicator "Z" is used when local time offset is 0.
3-08:00
- * Z		The ISO8601 extended format with hours and minutes fields. - * The ISO8601 UTC indicator "Z" is used when local time offset is 0.
4-0800
- * -075258
- * Z		The ISO8601 basic format with hours, minutes and optional seconds fields. - * (Note: The seconds field is not supported by the ISO8601 specification.) - * The ISO8601 UTC indicator "Z" is used when local time offset is 0.
5-08:00
- * -07:52:58
- * Z		The ISO8601 extended format with hours, minutes and optional seconds fields. - * (Note: The seconds field is not supported by the ISO8601 specification.) - * The ISO8601 UTC indicator "Z" is used when local time offset is 0.
x1-08
- * +0530		The ISO8601 basic format with hours field and optional minutes field.
2-0800The ISO8601 basic format with hours and minutes fields.
3-08:00The ISO8601 extended format with hours and minutes fields.
4-0800
- * -075258		The ISO8601 basic format with hours, minutes and optional seconds fields. - * (Note: The seconds field is not supported by the ISO8601 specification.)
5-08:00
- * -07:52:58		The ISO8601 extended format with hours, minutes and optional seconds fields. - * (Note: The seconds field is not supported by the ISO8601 specification.)
* *