// © 2016 and later: Unicode, Inc. and others. // License & terms of use: http://www.unicode.org/copyright.html /* * Copyright (C) 1997-2016, International Business Machines Corporation and * others. All Rights Reserved. ******************************************************************************* * * File SMPDTFMT.H * * Modification History: * * Date Name Description * 02/19/97 aliu Converted from java. * 07/09/97 helena Make ParsePosition into a class. * 07/21/98 stephen Added GMT_PLUS, GMT_MINUS * Changed setTwoDigitStartDate to set2DigitYearStart * Changed getTwoDigitStartDate to get2DigitYearStart * Removed subParseLong * Removed getZoneIndex (added in DateFormatSymbols) * 06/14/99 stephen Removed fgTimeZoneDataSuffix * 10/14/99 aliu Updated class doc to describe 2-digit year parsing * {j28 4182066}. ******************************************************************************* */ #ifndef SMPDTFMT_H #define SMPDTFMT_H #include "unicode/utypes.h" #if U_SHOW_CPLUSPLUS_API /** * \file * \brief C++ API: Format and parse dates in a language-independent manner. */ #if !UCONFIG_NO_FORMATTING #include "unicode/datefmt.h" #include "unicode/udisplaycontext.h" #include "unicode/tzfmt.h" /* for UTimeZoneFormatTimeType */ #include "unicode/brkiter.h" U_NAMESPACE_BEGIN class DateFormatSymbols; class DateFormat; class MessageFormat; class FieldPositionHandler; class TimeZoneFormat; class SharedNumberFormat; class SimpleDateFormatMutableNFs; class DateIntervalFormat; namespace number { class LocalizedNumberFormatter; class SimpleNumberFormatter; } /** * * SimpleDateFormat is a concrete class for formatting and parsing dates in a * language-independent manner. It allows for formatting (millis -> text), * parsing (text -> millis), and normalization. Formats/Parses a date or time, * which is the standard milliseconds since 24:00 GMT, Jan 1, 1970. * <P> * Clients are encouraged to create a date-time formatter using DateFormat::getInstance(), * 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 * 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(). * * <p><strong>Date and Time Patterns:</strong></p> * * <p>Date and time formats are specified by <em>date and time pattern</em> strings. * Within date and time pattern strings, all unquoted ASCII letters [A-Za-z] are reserved * as pattern letters representing calendar fields. <code>SimpleDateFormat</code> supports * the date and time formatting algorithm and pattern letters defined by * <a href="http://www.unicode.org/reports/tr35/tr35-dates.html#Date_Field_Symbol_Table">UTS#35 * Unicode Locale Data Markup Language (LDML)</a> and further documented for ICU in the * <a href="https://unicode-org.github.io/icu/userguide/format_parse/datetime/#date-field-symbol-table">ICU * User Guide</a>. The following pattern letters are currently available (note that the actual * values depend on CLDR and may change from the examples shown here):</p> * * <table border="1"> * <tr> * <th>Field</th> * <th style="text-align: center">Sym.</th> * <th style="text-align: center">No.</th> * <th>Example</th> * <th>Description</th> * </tr> * <tr> * <th rowspan="3">era</th> * <td style="text-align: center" rowspan="3">G</td> * <td style="text-align: center">1..3</td> * <td>AD</td> * <td rowspan="3">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.</td> * </tr> * <tr> * <td style="text-align: center">4</td> * <td>Anno Domini</td> * </tr> * <tr> * <td style="text-align: center">5</td> * <td>A</td> * </tr> * <tr> * <th rowspan="6">year</th> * <td style="text-align: center">y</td> * <td style="text-align: center">1..n</td> * <td>1996</td> * <td>Year. Normally the length specifies the padding, but for two letters it also specifies the maximum * length. Example:<div align="center"> * <center> * <table border="1" cellpadding="2" cellspacing="0"> * <tr> * <th>Year</th> * <th style="text-align: right">y</th> * <th style="text-align: right">yy</th> * <th style="text-align: right">yyy</th> * <th style="text-align: right">yyyy</th> * <th style="text-align: right">yyyyy</th> * </tr> * <tr> * <td>AD 1</td> * <td style="text-align: right">1</td> * <td style="text-align: right">01</td> * <td style="text-align: right">001</td> * <td style="text-align: right">0001</td> * <td style="text-align: right">00001</td> * </tr> * <tr> * <td>AD 12</td> * <td style="text-align: right">12</td> * <td style="text-align: right">12</td> * <td style="text-align: right">012</td> * <td style="text-align: right">0012</td> * <td style="text-align: right">00012</td> * </tr> * <tr> * <td>AD 123</td> * <td style="text-align: right">123</td> * <td style="text-align: right">23</td> * <td style="text-align: right">123</td> * <td style="text-align: right">0123</td> * <td style="text-align: right">00123</td> * </tr> * <tr> * <td>AD 1234</td> * <td style="text-align: right">1234</td> * <td style="text-align: right">34</td> * <td style="text-align: right">1234</td> * <td style="text-align: right">1234</td> * <td style="text-align: right">01234</td> * </tr> * <tr> * <td>AD 12345</td> * <td style="text-align: right">12345</td> * <td style="text-align: right">45</td> * <td style="text-align: right">12345</td> * <td style="text-align: right">12345</td> * <td style="text-align: right">12345</td> * </tr> * </table> * </center></div> * </td> * </tr> * <tr> * <td style="text-align: center">Y</td> * <td style="text-align: center">1..n</td> * <td>1997</td> * <td>Year (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.</td> * </tr> * <tr> * <td style="text-align: center">u</td> * <td style="text-align: center">1..n</td> * <td>4601</td> * <td>Extended 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.</td> * </tr> * <tr> * <td style="text-align: center" rowspan="3">U</td> * <td style="text-align: center">1..3</td> * <td>甲子</td> * <td rowspan="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').</td> * </tr> * <tr> * <td style="text-align: center">4</td> * <td>(currently also 甲子)</td> * </tr> * <tr> * <td style="text-align: center">5</td> * <td>(currently also 甲子)</td> * </tr> * <tr> * <th rowspan="6">quarter</th> * <td rowspan="3" style="text-align: center">Q</td> * <td style="text-align: center">1..2</td> * <td>02</td> * <td rowspan="3">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).</td> * </tr> * <tr> * <td style="text-align: center">3</td> * <td>Q2</td> * </tr> * <tr> * <td style="text-align: center">4</td> * <td>2nd quarter</td> * </tr> * <tr> * <td rowspan="3" style="text-align: center">q</td> * <td style="text-align: center">1..2</td> * <td>02</td> * <td rowspan="3"><b>Stand-Alone</b> 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).</td> * </tr> * <tr> * <td style="text-align: center">3</td> * <td>Q2</td> * </tr> * <tr> * <td style="text-align: center">4</td> * <td>2nd quarter</td> * </tr> * <tr> * <th rowspan="8">month</th> * <td rowspan="4" style="text-align: center">M</td> * <td style="text-align: center">1..2</td> * <td>09</td> * <td rowspan="4">Month - 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")</td> * </tr> * <tr> * <td style="text-align: center">3</td> * <td>Sep</td> * </tr> * <tr> * <td style="text-align: center">4</td> * <td>September</td> * </tr> * <tr> * <td style="text-align: center">5</td> * <td>S</td> * </tr> * <tr> * <td rowspan="4" style="text-align: center">L</td> * <td style="text-align: center">1..2</td> * <td>09</td> * <td rowspan="4"><b>Stand-Alone</b> 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")</td> * </tr> * <tr> * <td style="text-align: center">3</td> * <td>Sep</td> * </tr> * <tr> * <td style="text-align: center">4</td> * <td>September</td> * </tr> * <tr> * <td style="text-align: center">5</td> * <td>S</td> * </tr> * <tr> * <th rowspan="2">week</th> * <td style="text-align: center">w</td> * <td style="text-align: center">1..2</td> * <td>27</td> * <td>Week 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").</td> * </tr> * <tr> * <td style="text-align: center">W</td> * <td style="text-align: center">1</td> * <td>3</td> * <td>Week of Month</td> * </tr> * <tr> * <th rowspan="4">day</th> * <td style="text-align: center">d</td> * <td style="text-align: center">1..2</td> * <td>1</td> * <td>Date - Day of the month. Use "d" to show the minimum number of digits, or "dd" to always show * two digits (zero-padding if necessary, e.g. "08").</td> * </tr> * <tr> * <td style="text-align: center">D</td> * <td style="text-align: center">1..3</td> * <td>345</td> * <td>Day of year</td> * </tr> * <tr> * <td style="text-align: center">F</td> * <td style="text-align: center">1</td> * <td>2</td> * <td>Day of Week in Month. The example is for the 2nd Wed in July</td> * </tr> * <tr> * <td style="text-align: center">g</td> * <td style="text-align: center">1..n</td> * <td>2451334</td> * <td>Modified 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.</td> * </tr> * <tr> * <th rowspan="14">week<br> * day</th> * <td rowspan="4" style="text-align: center">E</td> * <td style="text-align: center">1..3</td> * <td>Tue</td> * <td rowspan="4">Day of week - Use one through three letters for the short day, four for the full (wide) name, * five for the narrow name, or six for the short name.</td> * </tr> * <tr> * <td style="text-align: center">4</td> * <td>Tuesday</td> * </tr> * <tr> * <td style="text-align: center">5</td> * <td>T</td> * </tr> * <tr> * <td style="text-align: center">6</td> * <td>Tu</td> * </tr> * <tr> * <td rowspan="5" style="text-align: center">e</td> * <td style="text-align: center">1..2</td> * <td>2</td> * <td rowspan="5">Local 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.</td> * </tr> * <tr> * <td style="text-align: center">3</td> * <td>Tue</td> * </tr> * <tr> * <td style="text-align: center">4</td> * <td>Tuesday</td> * </tr> * <tr> * <td style="text-align: center">5</td> * <td>T</td> * </tr> * <tr> * <td style="text-align: center">6</td> * <td>Tu</td> * </tr> * <tr> * <td rowspan="5" style="text-align: center">c</td> * <td style="text-align: center">1</td> * <td>2</td> * <td rowspan="5"><b>Stand-Alone</b> 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.</td> * </tr> * <tr> * <td style="text-align: center">3</td> * <td>Tue</td> * </tr> * <tr> * <td style="text-align: center">4</td> * <td>Tuesday</td> * </tr> * <tr> * <td style="text-align: center">5</td> * <td>T</td> * </tr> * <tr> * <td style="text-align: center">6</td> * <td>Tu</td> * </tr> * <tr> * <th>period</th> * <td style="text-align: center">a</td> * <td style="text-align: center">1</td> * <td>AM</td> * <td>AM or PM</td> * </tr> * <tr> * <th rowspan="4">hour</th> * <td style="text-align: center">h</td> * <td style="text-align: center">1..2</td> * <td>11</td> * <td>Hour [1-12]. When used in skeleton data or in a skeleton passed in an API for flexible data pattern * generation, it should match the 12-hour-cycle format preferred by the locale (h or K); it should not match * a 24-hour-cycle format (H or k). Use hh for zero padding.</td> * </tr> * <tr> * <td style="text-align: center">H</td> * <td style="text-align: center">1..2</td> * <td>13</td> * <td>Hour [0-23]. When used in skeleton data or in a skeleton passed in an API for flexible data pattern * generation, it should match the 24-hour-cycle format preferred by the locale (H or k); it should not match a * 12-hour-cycle format (h or K). Use HH for zero padding.</td> * </tr> * <tr> * <td style="text-align: center">K</td> * <td style="text-align: center">1..2</td> * <td>0</td> * <td>Hour [0-11]. When used in a skeleton, only matches K or h, see above. Use KK for zero padding.</td> * </tr> * <tr> * <td style="text-align: center">k</td> * <td style="text-align: center">1..2</td> * <td>24</td> * <td>Hour [1-24]. When used in a skeleton, only matches k or H, see above. Use kk for zero padding.</td> * </tr> * <tr> * <th>minute</th> * <td style="text-align: center">m</td> * <td style="text-align: center">1..2</td> * <td>59</td> * <td>Minute. Use "m" to show the minimum number of digits, or "mm" to always show two digits * (zero-padding if necessary, e.g. "08").</td> * </tr> * <tr> * <th rowspan="3">second</th> * <td style="text-align: center">s</td> * <td style="text-align: center">1..2</td> * <td>12</td> * <td>Second. Use "s" to show the minimum number of digits, or "ss" to always show two digits * (zero-padding if necessary, e.g. "08").</td> * </tr> * <tr> * <td style="text-align: center">S</td> * <td style="text-align: center">1..n</td> * <td>3450</td> * <td>Fractional 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)</td> * </tr> * <tr> * <td style="text-align: center">A</td> * <td style="text-align: center">1..n</td> * <td>69540000</td> * <td>Milliseconds in day. This field behaves <i>exactly</i> 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.</td> * </tr> * <tr> * <th rowspan="23">zone</th> * <td rowspan="2" style="text-align: center">z</td> * <td style="text-align: center">1..3</td> * <td>PDT</td> * <td>The <i>short specific non-location format</i>. * Where that is unavailable, falls back to the <i>short localized GMT format</i> ("O").</td> * </tr> * <tr> * <td style="text-align: center">4</td> * <td>Pacific Daylight Time</td> * <td>The <i>long specific non-location format</i>. * Where that is unavailable, falls back to the <i>long localized GMT format</i> ("OOOO").</td> * </tr> * <tr> * <td rowspan="3" style="text-align: center">Z</td> * <td style="text-align: center">1..3</td> * <td>-0800</td> * <td>The <i>ISO8601 basic format</i> 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.</td> * </tr> * <tr> * <td style="text-align: center">4</td> * <td>GMT-8:00</td> * <td>The <i>long localized GMT format</i>. * This is equivalent to the "OOOO" specifier.</td> * </tr> * <tr> * <td style="text-align: center">5</td> * <td>-08:00<br> * -07:52:58</td> * <td>The <i>ISO8601 extended format</i> 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.</td> * </tr> * <tr> * <td rowspan="2" style="text-align: center">O</td> * <td style="text-align: center">1</td> * <td>GMT-8</td> * <td>The <i>short localized GMT format</i>.</td> * </tr> * <tr> * <td style="text-align: center">4</td> * <td>GMT-08:00</td> * <td>The <i>long localized GMT format</i>.</td> * </tr> * <tr> * <td rowspan="2" style="text-align: center">v</td> * <td style="text-align: center">1</td> * <td>PT</td> * <td>The <i>short generic non-location format</i>. * Where that is unavailable, falls back to the <i>generic location format</i> ("VVVV"), * then the <i>short localized GMT format</i> as the final fallback.</td> * </tr> * <tr> * <td style="text-align: center">4</td> * <td>Pacific Time</td> * <td>The <i>long generic non-location format</i>. * Where that is unavailable, falls back to <i>generic location format</i> ("VVVV"). * </tr> * <tr> * <td rowspan="4" style="text-align: center">V</td> * <td style="text-align: center">1</td> * <td>uslax</td> * <td>The short time zone ID. * Where that is unavailable, the special short time zone ID <i>unk</i> (Unknown Zone) is used.<br> * <i><b>Note</b>: 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.</i></td> * </tr> * <tr> * <td style="text-align: center">2</td> * <td>America/Los_Angeles</td> * <td>The long time zone ID.</td> * </tr> * <tr> * <td style="text-align: center">3</td> * <td>Los Angeles</td> * <td>The exemplar city (location) for the time zone. * Where that is unavailable, the localized exemplar city name for the special zone <i>Etc/Unknown</i> is used * as the fallback (for example, "Unknown City"). </td> * </tr> * <tr> * <td style="text-align: center">4</td> * <td>Los Angeles Time</td> * <td>The <i>generic location format</i>. * Where that is unavailable, falls back to the <i>long localized GMT format</i> ("OOOO"; * Note: Fallback is only necessary with a GMT-style Time Zone ID, like Etc/GMT-830.)<br> * This is especially useful when presenting possible timezone choices for user selection, * since the naming is more uniform than the "v" format.</td> * </tr> * <tr> * <td rowspan="5" style="text-align: center">X</td> * <td style="text-align: center">1</td> * <td>-08<br> * +0530<br> * Z</td> * <td>The <i>ISO8601 basic format</i> with hours field and optional minutes field. * The ISO8601 UTC indicator "Z" is used when local time offset is 0.</td> * </tr> * <tr> * <td style="text-align: center">2</td> * <td>-0800<br> * Z</td> * <td>The <i>ISO8601 basic format</i> with hours and minutes fields. * The ISO8601 UTC indicator "Z" is used when local time offset is 0.</td> * </tr> * <tr> * <td style="text-align: center">3</td> * <td>-08:00<br> * Z</td> * <td>The <i>ISO8601 extended format</i> with hours and minutes fields. * The ISO8601 UTC indicator "Z" is used when local time offset is 0.</td> * </tr> * <tr> * <td style="text-align: center">4</td> * <td>-0800<br> * -075258<br> * Z</td> * <td>The <i>ISO8601 basic format</i> 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.</td> * </tr> * <tr> * <td style="text-align: center">5</td> * <td>-08:00<br> * -07:52:58<br> * Z</td> * <td>The <i>ISO8601 extended format</i> 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.</td> * </tr> * <tr> * <td rowspan="5" style="text-align: center">x</td> * <td style="text-align: center">1</td> * <td>-08<br> * +0530</td> * <td>The <i>ISO8601 basic format</i> with hours field and optional minutes field.</td> * </tr> * <tr> * <td style="text-align: center">2</td> * <td>-0800</td> * <td>The <i>ISO8601 basic format</i> with hours and minutes fields.</td> * </tr> * <tr> * <td style="text-align: center">3</td> * <td>-08:00</td> * <td>The <i>ISO8601 extended format</i> with hours and minutes fields.</td> * </tr> * <tr> * <td style="text-align: center">4</td> * <td>-0800<br> * -075258</td> * <td>The <i>ISO8601 basic format</i> with hours, minutes and optional seconds fields. * (Note: The seconds field is not supported by the ISO8601 specification.)</td> * </tr> * <tr> * <td style="text-align: center">5</td> * <td>-08:00<br> * -07:52:58</td> * <td>The <i>ISO8601 extended format</i> with hours, minutes and optional seconds fields. * (Note: The seconds field is not supported by the ISO8601 specification.)</td> * </tr> * </table> * * <P> * Any characters in the pattern that are not in the ranges of ['a'..'z'] and * ['A'..'Z'] will be treated as quoted text. For instance, characters * like ':', '.', ' ', '#' and '@' will appear in the resulting time text * even they are not embraced within single quotes. * <P> * A pattern containing any invalid pattern letter will result in a failing * UErrorCode result during formatting or parsing. * <P> * Examples using the US locale: * <pre> * \code * Format Pattern Result * -------------- ------- * "yyyy.MM.dd G 'at' HH:mm:ss vvvv" ->> 1996.07.10 AD at 15:08:56 Pacific Time * "EEE, MMM d, ''yy" ->> Wed, July 10, '96 * "h:mm a" ->> 12:08 PM * "hh 'o''clock' a, zzzz" ->> 12 o'clock PM, Pacific Daylight Time * "K:mm a, vvv" ->> 0:00 PM, PT * "yyyyy.MMMMM.dd GGG hh:mm aaa" ->> 1996.July.10 AD 12:08 PM * \endcode * </pre> * Code Sample: * <pre> * \code * UErrorCode success = U_ZERO_ERROR; * SimpleTimeZone* pdt = new SimpleTimeZone(-8 * 60 * 60 * 1000, "PST"); * pdt->setStartRule( Calendar::APRIL, 1, Calendar::SUNDAY, 2*60*60*1000); * pdt->setEndRule( Calendar::OCTOBER, -1, Calendar::SUNDAY, 2*60*60*1000); * * // Format the current time. * SimpleDateFormat* formatter * = new SimpleDateFormat ("yyyy.MM.dd G 'at' hh:mm:ss a zzz", success ); * GregorianCalendar cal(success); * UDate currentTime_1 = cal.getTime(success); * FieldPosition fp(FieldPosition::DONT_CARE); * UnicodeString dateString; * formatter->format( currentTime_1, dateString, fp ); * cout << "result: " << dateString << endl; * * // Parse the previous string back into a Date. * ParsePosition pp(0); * UDate currentTime_2 = formatter->parse(dateString, pp ); * \endcode * </pre> * In the above example, the time value "currentTime_2" obtained from parsing * will be equal to currentTime_1. However, they may not be equal if the am/pm * marker 'a' is left out from the format pattern while the "hour in am/pm" * pattern symbol is used. This information loss can happen when formatting the * time in PM. * * <p> * When parsing a date string using the abbreviated year pattern ("y" or "yy"), * SimpleDateFormat must interpret the abbreviated year * relative to some century. It does this by adjusting dates to be * within 80 years before and 20 years after the time the SimpleDateFormat * instance is created. For example, using a pattern of "MM/dd/yy" and a * SimpleDateFormat instance created on Jan 1, 1997, the string * "01/11/12" would be interpreted as Jan 11, 2012 while the string "05/04/64" * would be interpreted as May 4, 1964. * During parsing, only strings consisting of exactly two digits, as defined by * <code>Unicode::isDigit()</code>, will be parsed into the default century. * Any other numeric string, such as a one digit string, a three or more digit * string, or a two digit string that isn't all digits (for example, "-1"), is * interpreted literally. So "01/02/3" or "01/02/003" are parsed (for the * Gregorian calendar), using the same pattern, as Jan 2, 3 AD. Likewise (but * only in lenient parse mode, the default) "01/02/-3" is parsed as Jan 2, 4 BC. * * <p> * If the year pattern has more than two 'y' characters, the year is * interpreted literally, regardless of the number of digits. So using the * pattern "MM/dd/yyyy", "01/11/12" parses to Jan 11, 12 A.D. * * <p> * When numeric fields abut one another directly, with no intervening delimiter * characters, they constitute a run of abutting numeric fields. Such runs are * parsed specially. For example, the format "HHmmss" parses the input text * "123456" to 12:34:56, parses the input text "12345" to 1:23:45, and fails to * parse "1234". In other words, the leftmost field of the run is flexible, * while the others keep a fixed width. If the parse fails anywhere in the run, * then the leftmost field is shortened by one character, and the entire run is * parsed again. This is repeated until either the parse succeeds or the * leftmost field is one character in length. If the parse still fails at that * point, the parse of the run fails. * * <P> * For time zones that have no names, SimpleDateFormat uses strings GMT+hours:minutes or * GMT-hours:minutes. * <P> * The calendar defines what is the first day of the week, the first week of the * year, whether hours are zero based or not (0 vs 12 or 24), and the timezone. * There is one common number format to handle all the numbers; the digit count * is handled programmatically according to the pattern. * * <p><em>User subclasses are not supported.</em> While clients may write * subclasses, such code will not necessarily work and will not be * guaranteed to work stably from release to release. */ class U_I18N_API SimpleDateFormat: public DateFormat { … }; inline UDate SimpleDateFormat::get2DigitYearStart(UErrorCode& /*status*/) const { … } U_NAMESPACE_END #endif /* #if !UCONFIG_NO_FORMATTING */ #endif /* U_SHOW_CPLUSPLUS_API */ #endif // _SMPDTFMT //eof
Codebase Browser
chromium