Lines Matching refs:calendar
25 ICU has two main calendar classes used for parsing and formatting Calendar
30 An abstract base class that defines the calendar API. This API supports
35 A concrete subclass of `Calendar` that implements the standard calendar used
61 The `Calendar` class is designed to support additional calendar systems in the future.
68 When a calendar object is created, via either `Calendar::create()`, or
70 calendar type for that locale. At present, all locales default to a Gregorian
71 calendar, except for the compatibility locales th_TH_TRADITIONAL and
72 ja_JP_TRADITIONAL. If the "calendar" keyword is supplied, this value will
75 For instance, `Calendar::createInstance("fr_FR", status)` will create a Gregorian calendar,
76 but `Calendar::createInstance("fr_FR@calendar=buddhist")` will create a Buddhist calendar.
78 It is an error to use an invalid calendar type. It will produce a missing resource error.
91 class, define specific operations that correspond to a real-world calendar
119 which means it is calendar and time zone independent. `UDate` is the most compact
121 the other hand, depend on the calendar system (that is, the concrete subclass of
122 `Calendar`) and the calendar object's context state.
127 At any given time, a calendar object uses (when `DateFormat` is not sufficient)
148 March 15, 1999 sets the calendar to May 15, 1999. The `roll()` method is similar,
150 `roll(Calendar::HOUR, n)` changes the hour that a calendar is set to without
155 difference between a calendar's currently set time and a specified `UDate` in
159 with the results of `fieldDifference(when, n)`, then the calendar is moved toward
190 The context of a `Calendar` object can be queried after the calendar is created
197 Like other format classes, the best way to create a calendar object is by using
200 used to enable the code to obtain the correct calendar for a locale without
232 The `GregorianCalendar` class implements two calendar systems, the Gregorian
233 calendar and the Julian calendar. These calendar systems are closely related,
234 differing mainly in their definition of the leap year. The Julian calendar has
235 leap years every four years; the Gregorian calendar refines this by excluding
239 Historically, most western countries used the Julian calendar until the 16th to
241 calendar. The `GregorianCalendar` class mirrors this behavior by defining a
242 cut-over date. Before this date, the Julian calendar algorithms are used. After
243 it, the Gregorian calendar algorithms are used. By default, the cut-over date is
245 adopting the Gregorian calendar. The `GregorianCalendar` class does not attempt
250 Code that is written correctly instantiates calendar objects using the Calendar
282 If fields conflict, the calendar gives preference to fields set more
283 recently. For example, when determining the day, the calendar looks for one
290 For the time of day, the calendar looks for one of the following
325 Programming for calendar [examples in C++, C, and Java](examples.md) .