lightbulb_outline Help shape the future of the Google Play Console, Android Studio, and Firebase. Start survey

ThaiBuddhistChronology

public final class ThaiBuddhistChronology
extends AbstractChronology implements Serializable

java.lang.Object
   ↳ java.time.chrono.AbstractChronology
     ↳ java.time.chrono.ThaiBuddhistChronology


The Thai Buddhist calendar system.

This chronology defines the rules of the Thai Buddhist calendar system. This calendar system is primarily used in Thailand. Dates are aligned such that 2484-01-01 (Buddhist) is 1941-01-01 (ISO).

The fields are defined as follows:

  • era - There are two eras, the current 'Buddhist' (ERA_BE) and the previous era (ERA_BEFORE_BE).
  • year-of-era - The year-of-era for the current era increases uniformly from the epoch at year one. For the previous era the year increases from one as time goes backwards. The value for the current era is equal to the ISO proleptic-year plus 543.
  • proleptic-year - The proleptic year is the same as the year-of-era for the current era. For the previous era, years have zero, then negative values. The value is equal to the ISO proleptic-year plus 543.
  • month-of-year - The ThaiBuddhist month-of-year exactly matches ISO.
  • day-of-month - The ThaiBuddhist day-of-month exactly matches ISO.
  • day-of-year - The ThaiBuddhist day-of-year exactly matches ISO.
  • leap-year - The ThaiBuddhist leap-year pattern exactly matches ISO, such that the two calendars are never out of step.

Summary

Fields

public static final ThaiBuddhistChronology INSTANCE

Singleton instance of the Buddhist chronology.

Public methods

ThaiBuddhistDate date(int prolepticYear, int month, int dayOfMonth)

Obtains a local date in Thai Buddhist calendar system from the proleptic-year, month-of-year and day-of-month fields.

ThaiBuddhistDate date(Era era, int yearOfEra, int month, int dayOfMonth)

Obtains a local date in Thai Buddhist calendar system from the era, year-of-era, month-of-year and day-of-month fields.

ThaiBuddhistDate date(TemporalAccessor temporal)
ThaiBuddhistDate dateEpochDay(long epochDay)

Obtains a local date in the Thai Buddhist calendar system from the epoch-day.

ThaiBuddhistDate dateNow(ZoneId zone)
ThaiBuddhistDate dateNow()
ThaiBuddhistDate dateNow(Clock clock)
ThaiBuddhistDate dateYearDay(Era era, int yearOfEra, int dayOfYear)

Obtains a local date in Thai Buddhist calendar system from the era, year-of-era and day-of-year fields.

ThaiBuddhistDate dateYearDay(int prolepticYear, int dayOfYear)

Obtains a local date in Thai Buddhist calendar system from the proleptic-year and day-of-year fields.

ThaiBuddhistEra eraOf(int eraValue)
List<Era> eras()
String getCalendarType()

Gets the calendar type of the underlying calendar system - 'buddhist'.

String getId()

Gets the ID of the chronology - 'ThaiBuddhist'.

boolean isLeapYear(long prolepticYear)

Checks if the specified year is a leap year.

ChronoLocalDateTime<ThaiBuddhistDate> localDateTime(TemporalAccessor temporal)
int prolepticYear(Era era, int yearOfEra)
ValueRange range(ChronoField field)
ThaiBuddhistDate resolveDate(Map<TemporalFieldLong> fieldValues, ResolverStyle resolverStyle)

Resolves parsed ChronoField values into a date during parsing.

ChronoZonedDateTime<ThaiBuddhistDate> zonedDateTime(TemporalAccessor temporal)
ChronoZonedDateTime<ThaiBuddhistDate> zonedDateTime(Instant instant, ZoneId zone)

Inherited methods

Fields

INSTANCE

added in API level 26
public static final ThaiBuddhistChronology INSTANCE

Singleton instance of the Buddhist chronology.

Public methods

date

added in API level 26
public ThaiBuddhistDate date (int prolepticYear, 
                int month, 
                int dayOfMonth)

Obtains a local date in Thai Buddhist calendar system from the proleptic-year, month-of-year and day-of-month fields.

Parameters
prolepticYear int: the proleptic-year

month int: the month-of-year

dayOfMonth int: the day-of-month

Returns
ThaiBuddhistDate the Thai Buddhist local date, not null

Throws
DateTimeException if unable to create the date

date

added in API level 26
public ThaiBuddhistDate date (Era era, 
                int yearOfEra, 
                int month, 
                int dayOfMonth)

Obtains a local date in Thai Buddhist calendar system from the era, year-of-era, month-of-year and day-of-month fields.

Parameters
era Era: the Thai Buddhist era, not null

yearOfEra int: the year-of-era

month int: the month-of-year

dayOfMonth int: the day-of-month

Returns
ThaiBuddhistDate the Thai Buddhist local date, not null

Throws
DateTimeException if unable to create the date
ClassCastException if the era is not a ThaiBuddhistEra

date

added in API level 26
public ThaiBuddhistDate date (TemporalAccessor temporal)

Parameters
temporal TemporalAccessor

Returns
ThaiBuddhistDate

dateEpochDay

added in API level 26
public ThaiBuddhistDate dateEpochDay (long epochDay)

Obtains a local date in the Thai Buddhist calendar system from the epoch-day.

Parameters
epochDay long: the epoch day

Returns
ThaiBuddhistDate the Thai Buddhist local date, not null

Throws
DateTimeException if unable to create the date

dateNow

added in API level 26
public ThaiBuddhistDate dateNow (ZoneId zone)

Parameters
zone ZoneId

Returns
ThaiBuddhistDate

dateNow

added in API level 26
public ThaiBuddhistDate dateNow ()

Returns
ThaiBuddhistDate

dateNow

added in API level 26
public ThaiBuddhistDate dateNow (Clock clock)

Parameters
clock Clock

Returns
ThaiBuddhistDate

dateYearDay

added in API level 26
public ThaiBuddhistDate dateYearDay (Era era, 
                int yearOfEra, 
                int dayOfYear)

Obtains a local date in Thai Buddhist calendar system from the era, year-of-era and day-of-year fields.

Parameters
era Era: the Thai Buddhist era, not null

yearOfEra int: the year-of-era

dayOfYear int: the day-of-year

Returns
ThaiBuddhistDate the Thai Buddhist local date, not null

Throws
DateTimeException if unable to create the date
ClassCastException if the era is not a ThaiBuddhistEra

dateYearDay

added in API level 26
public ThaiBuddhistDate dateYearDay (int prolepticYear, 
                int dayOfYear)

Obtains a local date in Thai Buddhist calendar system from the proleptic-year and day-of-year fields.

Parameters
prolepticYear int: the proleptic-year

dayOfYear int: the day-of-year

Returns
ThaiBuddhistDate the Thai Buddhist local date, not null

Throws
DateTimeException if unable to create the date

eraOf

added in API level 26
public ThaiBuddhistEra eraOf (int eraValue)

Parameters
eraValue int

Returns
ThaiBuddhistEra

eras

added in API level 26
public List<Era> eras ()

Returns
List<Era>

getCalendarType

added in API level 26
public String getCalendarType ()

Gets the calendar type of the underlying calendar system - 'buddhist'.

The calendar type is an identifier defined by the Unicode Locale Data Markup Language (LDML) specification. It can be used to lookup the Chronology using Chronology.of(String). It can also be used as part of a locale, accessible via Locale.getUnicodeLocaleType(String) with the key 'ca'.

Returns
String the calendar system type - 'buddhist'

See also:

getId

added in API level 26
public String getId ()

Gets the ID of the chronology - 'ThaiBuddhist'.

The ID uniquely identifies the Chronology. It can be used to lookup the Chronology using Chronology.of(String).

Returns
String the chronology ID - 'ThaiBuddhist'

See also:

isLeapYear

added in API level 26
public boolean isLeapYear (long prolepticYear)

Checks if the specified year is a leap year.

Thai Buddhist leap years occur exactly in line with ISO leap years. This method does not validate the year passed in, and only has a well-defined result for years in the supported range.

Parameters
prolepticYear long: the proleptic-year to check, not validated for range

Returns
boolean true if the year is a leap year

localDateTime

added in API level 26
public ChronoLocalDateTime<ThaiBuddhistDate> localDateTime (TemporalAccessor temporal)

Parameters
temporal TemporalAccessor

Returns
ChronoLocalDateTime<ThaiBuddhistDate>

prolepticYear

added in API level 26
public int prolepticYear (Era era, 
                int yearOfEra)

Parameters
era Era

yearOfEra int

Returns
int

range

added in API level 26
public ValueRange range (ChronoField field)

Parameters
field ChronoField

Returns
ValueRange

resolveDate

added in API level 26
public ThaiBuddhistDate resolveDate (Map<TemporalFieldLong> fieldValues, 
                ResolverStyle resolverStyle)

Resolves parsed ChronoField values into a date during parsing.

Most TemporalField implementations are resolved using the resolve method on the field. By contrast, the ChronoField class defines fields that only have meaning relative to the chronology. As such, ChronoField date fields are resolved here in the context of a specific chronology.

ChronoField instances are resolved by this method, which may be overridden in subclasses.

  • EPOCH_DAY - If present, this is converted to a date and all other date fields are then cross-checked against the date.
  • PROLEPTIC_MONTH - If present, then it is split into the YEAR and MONTH_OF_YEAR. If the mode is strict or smart then the field is validated.
  • YEAR_OF_ERA and ERA - If both are present, then they are combined to form a YEAR. In lenient mode, the YEAR_OF_ERA range is not validated, in smart and strict mode it is. The ERA is validated for range in all three modes. If only the YEAR_OF_ERA is present, and the mode is smart or lenient, then the last available era is assumed. In strict mode, no era is assumed and the YEAR_OF_ERA is left untouched. If only the ERA is present, then it is left untouched.
  • YEAR, MONTH_OF_YEAR and DAY_OF_MONTH - If all three are present, then they are combined to form a date. In all three modes, the YEAR is validated. If the mode is smart or strict, then the month and day are validated. If the mode is lenient, then the date is combined in a manner equivalent to creating a date on the first day of the first month in the requested year, then adding the difference in months, then the difference in days. If the mode is smart, and the day-of-month is greater than the maximum for the year-month, then the day-of-month is adjusted to the last day-of-month. If the mode is strict, then the three fields must form a valid date.
  • YEAR and DAY_OF_YEAR - If both are present, then they are combined to form a date. In all three modes, the YEAR is validated. If the mode is lenient, then the date is combined in a manner equivalent to creating a date on the first day of the requested year, then adding the difference in days. If the mode is smart or strict, then the two fields must form a valid date.
  • YEAR, MONTH_OF_YEAR, ALIGNED_WEEK_OF_MONTH and ALIGNED_DAY_OF_WEEK_IN_MONTH - If all four are present, then they are combined to form a date. In all three modes, the YEAR is validated. If the mode is lenient, then the date is combined in a manner equivalent to creating a date on the first day of the first month in the requested year, then adding the difference in months, then the difference in weeks, then in days. If the mode is smart or strict, then the all four fields are validated to their outer ranges. The date is then combined in a manner equivalent to creating a date on the first day of the requested year and month, then adding the amount in weeks and days to reach their values. If the mode is strict, the date is additionally validated to check that the day and week adjustment did not change the month.
  • YEAR, MONTH_OF_YEAR, ALIGNED_WEEK_OF_MONTH and DAY_OF_WEEK - If all four are present, then they are combined to form a date. The approach is the same as described above for years, months and weeks in ALIGNED_DAY_OF_WEEK_IN_MONTH. The day-of-week is adjusted as the next or same matching day-of-week once the years, months and weeks have been handled.
  • YEAR, ALIGNED_WEEK_OF_YEAR and ALIGNED_DAY_OF_WEEK_IN_YEAR - If all three are present, then they are combined to form a date. In all three modes, the YEAR is validated. If the mode is lenient, then the date is combined in a manner equivalent to creating a date on the first day of the requested year, then adding the difference in weeks, then in days. If the mode is smart or strict, then the all three fields are validated to their outer ranges. The date is then combined in a manner equivalent to creating a date on the first day of the requested year, then adding the amount in weeks and days to reach their values. If the mode is strict, the date is additionally validated to check that the day and week adjustment did not change the year.
  • YEAR, ALIGNED_WEEK_OF_YEAR and DAY_OF_WEEK - If all three are present, then they are combined to form a date. The approach is the same as described above for years and weeks in ALIGNED_DAY_OF_WEEK_IN_YEAR. The day-of-week is adjusted as the next or same matching day-of-week once the years and weeks have been handled.

The default implementation is suitable for most calendar systems. If ChronoField.YEAR_OF_ERA is found without an ChronoField.ERA then the last era in Chronology.eras() is used. The implementation assumes a 7 day week, that the first day-of-month has the value 1, that first day-of-year has the value 1, and that the first of the month and year always exists.

Parameters
fieldValues Map: the map of fields to values, which can be updated, not null

resolverStyle ResolverStyle: the requested type of resolve, not null

Returns
ThaiBuddhistDate the resolved date, null if insufficient information to create a date

zonedDateTime

added in API level 26
public ChronoZonedDateTime<ThaiBuddhistDate> zonedDateTime (TemporalAccessor temporal)

Parameters
temporal TemporalAccessor

Returns
ChronoZonedDateTime<ThaiBuddhistDate>

zonedDateTime

added in API level 26
public ChronoZonedDateTime<ThaiBuddhistDate> zonedDateTime (Instant instant, 
                ZoneId zone)

Parameters
instant Instant

zone ZoneId

Returns
ChronoZonedDateTime<ThaiBuddhistDate>