Home | History | Annotate | Download | only in i18n

Lines Matching full:year

21 *   10/14/99    aliu        Updated 2-digit year parsing so that only "00" thru
23 * 11/15/99 weiv Added support for week of year/day of week format
1238 // the Calendar YEAR field runs 1 through 60 for cyclic years
1242 // else fall through to numeric year handling, do not break here
1244 // OLD: for "yyyy", write out the whole year; for "yy", write out the last 2 digits
1246 //Year y yy yyy yyyy yyyyy
1792 // Take the date April 3 2004 at 2:30 am. When this is first set up, the year
1793 // will be wrong if we're parsing a 2-digit year pattern. It will be 1904.
1802 calendar.add(Calendar.YEAR, 100);
1810 // when the two-digit year is equal to the start year, and thus might fall at the
1812 // the year correctly to start with in other cases -- see subParse().
1813 if (ambiguousYear[0] || tztype != UTZFMT_TIME_TYPE_UNKNOWN) // If this is true then the two-digit year == the default start year
2259 bestMatch++; // only get here for cyclic year names, which match 1-based years 1-60
2525 // verify no year information also
2532 // If there are 3 or more YEAR pattern characters, this indicates
2533 // that the year value is to be treated literally, without any
2534 // two-digit year adjustments (e.g., from "01" to 2001). Otherwise
2535 // we made adjustments to place the 2-digit year in the proper
2548 // to 1904, 1905, etc. If the year is 03, then it is 2003 if the
2550 // date afterwards. As a result, 03 is an ambiguous year. All other
2552 if(fHaveDefaultCentury) { // check if this formatter even has a pivot year
2608 // or not it was a leap year. We may or may not yet know what year it is, so might have to delay checking until
2609 // the year is parsed.