Fact-checked by Grok 2 weeks ago

Proleptic Gregorian calendar

The proleptic is an extension of the that applies its rules retroactively to all dates preceding the calendar's historical introduction in , creating a consistent system without accounting for prior discrepancies or day omissions during transitions. This proleptic approach treats the leap year algorithm as operative from the beginning of the , including for negative years and year 0 (corresponding to 1 BCE), which is designated as a . The itself was promulgated by in 1582 through the Inter gravissimas, aimed at realigning the calendar with the solar year to better approximate the vernal equinox for ecclesiastical purposes, correcting the Julian calendar's accumulated drift of 10 days since 325 AD. Its core rules define common years as 365 days and as 366 days, with an extra day inserted in ; a year is a if divisible by 4, except for century years, which must be divisible by 400 to qualify (e.g., 1600 and 2000 are , but 1700 and 1900 are not). This yields an average year length of 365.2425 days, reducing the drift to one day every approximately 3,300 years compared to the astronomical solar year. In modern applications, the proleptic Gregorian calendar is standardized in for representing dates and times in information interchange, which permits its use for dates expressed in the Gregorian format before 1582 by mutual agreement between information interchange partners, to ensure uniformity in , data exchange, and scientific contexts. It is widely implemented in programming libraries, such as Java's GregorianCalendar class, which supports proleptic computation by configuring the cutover date to extrapolate these rules indefinitely backward and forward, and in astronomical software for consistent historical dating. This extension facilitates precise chronological calculations across eras but differs from historical records, which followed the prior to local adoptions of the between 1582 and 1923.

Historical Background

Gregorian Calendar Origins

The Gregorian calendar was introduced through the papal bull Inter gravissimas, issued by on February 24, 1582, to reform the existing . This reform addressed the 's gradual misalignment with the solar year, which assumed a of 365.25 days, overestimating the actual of approximately 365.2425 days and causing a drift of about one day every 128 years. By the , this error had accumulated to a 10-day discrepancy, shifting the vernal from its traditional date of and complicating the computation of , the timing of which was central to the Christian liturgical . To implement the correction, the directed the omission of 10 days in 1582, so that , October 4, was immediately followed by , October 15, in adopting regions. Initial adoption occurred swiftly in several Catholic countries, including , , , the , and parts of , where the took effect on the specified date. The revised rules—skipping leap days in most century years—were also enacted to prevent future drifts, ensuring better long-term alignment with astronomical cycles. Adoption spread gradually across and beyond, often delayed by religious and political opposition to the papal decree. Protestant nations, wary of Catholic influence, implemented the change later; for instance, and its colonies switched in 1752, omitting 11 days ( followed by ) to account for the further elapsed drift. followed in 1918 by skipping 13 days in , while completed the transition in 1923 for civil purposes, though its retained the for religious observances until later. The original reform focused exclusively on prospective accuracy, aiming to restore the vernal equinox to March 21 and stabilize calculations for future centuries, without any retrospective application of the new rules.

Development of Proleptic Extension

The proleptic Gregorian calendar is defined as the extension of the calendar's rules indefinitely into the past, prior to its official adoption in 1582, thereby establishing a perpetual system that avoids the discontinuities arising from historical calendar transitions. This extrapolation applies the Gregorian leap year —skipping leap years in certain century years unless divisible by 400—retroactively to all preceding dates, resulting in a uniform chronological framework suitable for computational and astronomical purposes. The term "proleptic" derives from the Greek word prolepsis, meaning "anticipation" or "preconception," referring to the anticipatory application of rules to prior periods. In calendrical and astronomical contexts, it first appeared in the to describe such backward extensions, particularly as scholars sought consistent methods for dating ancient events without relying on evolving historical calendars. Astronomers in the late advocated for proleptic extensions to achieve uniform chronology in ephemerides and almanacs, enabling precise alignment of observations across millennia. The concept was further formalized in 20th-century standards, such as those governing astronomical data representation. The :2004 standard permits the use of the proleptic Gregorian calendar for dates before , but only with explicit agreement among parties to mitigate risks of misinterpretation in contexts where the was historically dominant. This provision ensures that the extended system supports global data interchange while acknowledging potential ambiguities in pre-reform records. In scholarly and archival work, best practices recommend always specifying the original historical calendar—such as the —alongside any proleptic Gregorian equivalents to avoid anachronistic interpretations and preserve contextual accuracy. This dual notation facilitates cross-referencing while highlighting the theoretical nature of retroactive applications.

Calendar Rules

Leap Year Criteria

The proleptic Gregorian calendar applies the same leap year rules as the modern to all years, extending them indefinitely into the past and future without interruption. A year is a if it is evenly divisible by 4. However, century years—those divisible by 100—are common years (not ) unless they are also divisible by 400. This can be expressed mathematically as: a year Y is a if Y \mod 4 = 0 and (Y \mod 100 \neq 0 or Y \mod 400 = 0). For example, the year 2000 is a because it is divisible by 400, while 1900 is not because it is divisible by 100 but not by 400; similarly, 1600 qualifies as a due to divisibility by 400. In , February has 29 days instead of 28, resulting in a total of 366 days for the year, compared to 365 days in common years; this adjustment helps align the calendar with the solar year.

Astronomical Year Numbering

In , the proleptic Gregorian calendar uses a continuous sequence of integers for years, designating year 0 as equivalent to and assigning negative values to preceding years—for instance, year −1 corresponds to and year −2 to 3 BC. This system aligns with the international standard , which extends Gregorian rules backward indefinitely without a gap at the AD/BC transition. Under this convention, year 0 qualifies as a because it is divisible by 400, thereby including and consisting of 366 days. The criteria—divisible by 4 but not by 100 unless also by 400—apply uniformly across all years, including zero and negatives, ensuring consistent day counting in the proleptic extension. The primary rationale for this numbering is to enable seamless integer arithmetic in astronomical computations, eliminating discontinuities that would arise from the absence of year 0 in traditional AD/BC systems and allowing straightforward calculations of intervals spanning the era boundary. This approach is particularly evident in formulas for the (), where the year parameter Y is set to 0 for (and negative for earlier years), with leap rules applied directly to determine day offsets. For example, in year 0 (), the presence of means that follows immediately after that date, maintaining the calendar's 366-day structure for the year.

Comparison to

Day Offset Accumulation

The overestimates the length of the compared to the proleptic calendar, with an average year of 365.25 days versus 365.2425 days, leading to a drift of approximately 0.0075 days per year or about 3 days every 400 years. This accumulation stems from the rule omitting leap days in most century years (divisible by 100 but not by 400), while the rule includes them as whenever divisible by 4. The cumulative day offset between the proleptic Gregorian and Julian calendars is the number of such omitted leap years up to a given year Y (using astronomical year numbering, where year 1 is 1 AD and year 0 is 1 BC). This , representing the number of days by which Julian dates lag behind proleptic Gregorian dates for the same physical day, is calculated as \left\lfloor \frac{Y}{100} \right\rfloor - \left\lfloor \frac{Y}{400} \right\rfloor where \left\lfloor \cdot \right\rfloor denotes the floor function. The offset remains zero before the first century difference, as both calendars align in their leap year placements until year 100 AD (when the century rule first omits a leap day in the Gregorian system); specifically, there is no offset for dates before . The offset changes only after February 29 in century years that are not divisible by 400. The offset accumulates progressively as follows, remaining constant within periods between differing leap days:
Period (AD)Offset (days, Gregorian ahead of Julian)
Before 1000
100–1991
200–2992
300–4993
500–5994
600–6995
700–7996
800–8996
900–9997
1000–11998–9
1200–12999
1300–139910
1400–149911
1500–159912
1900–209915
2100–219916
For instance, the offset reaches 12 days by and 15 days during –2100.

Century Rule Impacts

The century rule in the proleptic Gregorian calendar introduces exceptions for in century years, omitting leap days in years divisible by 100 but not by 400, unlike the , which treats all years divisible by 4 as . This results in the Gregorian calendar skipping three every 400-year cycle—specifically, in century years such as 1700, 1800, and , which are leap years in the Julian system but not in the Gregorian. These omissions prevent the overestimation of the solar year length inherent in the 's uniform quadrennial leaps. In the proleptic extension, these skips create stepwise divergences from the at specific historical points, with the difference increasing by one day immediately following each omitted in a century year. The first such divergence occurs after 100 AD, when the year is a in the but not in the proleptic Gregorian, shifting dates by one day; this accumulates to two days after 200 AD and three days after 300 AD. The pattern pauses during century years divisible by 400 (e.g., 400 AD, both calendars include the leap day), but resumes with additional skips at 500 AD, 600 AD, and 700 AD, building progressively. By 1582, the cumulative effect of these omissions reaches 12 days. Over the long term, the century rule refines the calendar's accuracy by establishing an average year length of 365.2425 days—achieved through 97 in every 400-year period—compared to the average of 365.25 days, which overestimates the by about 0.0075 days annually. This adjustment reduces the drift relative to the solar year to approximately one day every 3,300 years, a significant improvement over the calendar's drift of one day every 128 years. The impacts are evident in post-reform periods: the day offset remains 12 days from to 1699, increases to 13 days from 1700 to 1799 following the skip in 1700, reaches 14 days from 1800 to 1899, and stands at 15 days from 1900 to 2099. These step-wise increases highlight how the rule's exceptions create larger, punctuated divergences at century boundaries while maintaining overall alignment with astronomical cycles.

Modern Applications

Chronology and Scholarship

In historical, astronomical, and , the proleptic Gregorian calendar provides a uniform framework for dating events before 1582 by retroactively applying Gregorian rules, enabling consistent chronological analysis across disparate records. This approach facilitates the integration of ancient observations with modern computations, though it requires careful notation to distinguish from historical calendars like the Julian. In astronomy, employs the proleptic Gregorian calendar for eclipse predictions extending to ancient events, ensuring precise alignment with historical records such as from the 7th century BCE onward. For instance, this system correlates Babylonian timings—documented on clay tablets—with computed paths, treating year 0 (1 BCE) as a under proleptic rules to maintain uniformity in Number conversions. Such applications underscore its value in verifying predictive models like the Saros cycle against millennia-old data. Cultural studies, particularly , leverage proleptic conversions to bridge indigenous systems with Western dating. The Maya Long Count calendar's at 0.0.0.0.0 corresponds to August 11, 3114 BCE in the proleptic Gregorian calendar, marking the mythical date and allowing scholars to synchronize Long Count inscriptions with global timelines. This alignment, based on the Goodman-Martínez-Thompson correlation, supports analyses of Maya astronomical and historical texts without disrupting the 260-day Tzolk'in or 365-day Haab cycles. Scholars caution against uncritical use of the proleptic Gregorian in historical research to avoid anachronisms, especially for medieval periods reliant on dating. Discussions in W3C standards development highlight how mapping dates—such as July 15, 1099—to proleptic equivalents (e.g., July 7, 1099) can distort source comparisons and impede digital . This misuse risks conflating contemporary interpretations with period-specific records, as noted in specifications urging explicit calendar attributes for pre-Gregorian dates. As a scholarly standard, the proleptic Gregorian calendar is preferred in for representing dates before , provided all parties agree on its application. The notation uses a minus sign for negative years in astronomical numbering, such as -0456-07-14 for July 14, 457 BCE, ensuring unambiguous extended formats like YYYY-MM-DD across expanded year ranges from to . This convention treats year as a and avoids insertions or deletions, promoting in interdisciplinary . For example, advancements in date-time representations address challenges like backward for ancient artifacts, enhancing searchability while preserving contextual accuracy in software ecosystems. These efforts build on to support scalable, error-free uniform dating in scholarly databases.

Computing Implementations

The International Organization for Standardization's standard for representing dates and times extends the proleptically to dates before its 1582 adoption, allowing negative years in the format -YYYY for years before 1 and treating year 0000 as a . This proleptic extension ensures consistent date formatting across software systems, with January 1 of year 1 assigned ordinal 1. In programming languages, the standard library's datetime module defaults to the proleptic Gregorian calendar for date operations, including conversions from ordinal days where , year 1, is ordinal 1, and supports negative years without exceptions. Similarly, Java's GregorianCalendar class implements a hybrid system that applies proleptic Julian rules before the 1582 cutover date (October 15, 1582) and proleptic Gregorian rules afterward, enabling seamless extrapolation for dates far into the past or future. The .NET Framework's DateTime structure and 's Intl.DateTimeFormat also utilize proleptic Gregorian rules for handling and formatting historical dates. Database management systems commonly adopt proleptic Gregorian rules for pre-1582 dates to simplify computations. PostgreSQL's date type stores values as days since January 3, 2000, but interprets inputs using proleptic Gregorian leap year rules, supporting dates from 4713 BCE onward without a year 0. MySQL employs a proleptic Gregorian calendar in its date functions, enforcing a cutover discontinuity between October 4 and October 15, 1582, and warns against using functions like TO_DAYS for dates before 1582 due to potential inaccuracies. SQLite's built-in date and time functions, such as julianday(), compute based on the proleptic Gregorian calendar, referencing noon Greenwich on November 24, 4714 BCE, as Julian day 0. Astronomy-specific libraries leverage proleptic Gregorian for precise historical calculations. The library Skyfield uses proleptic Gregorian dates internally for computations, aligning with Python's datetime module and the Naval Observatory's conventions to facilitate back-projection to without calendar switches. Implementing proleptic Gregorian in software presents challenges, particularly around cutover dates and hybrid Julian transitions. For instance, PHP's DateTime functions default to proleptic Gregorian per but permit overrides for handling via custom parsing, which developers must specify to avoid discrepancies in historical data processing.

Conversion Examples

Historical Events

The birth of exemplifies the impact of calendar transitions in the British colonies. Recorded as February 11, 1731, under the Julian calendar (Old Style), this date shifted to February 22, 1732, in the proleptic Gregorian calendar following the 11-day adjustment implemented in 1752. The , a pivotal English victory during the , occurred on October 25, 1415, in the . In the proleptic , this date corresponds to November 4, 1415, reflecting a 10-day offset accumulated by the . The signing of the American Declaration of Independence on , 1776, was already aligned with the in the colonies, having adopted it in 1752 alongside . Thus, the proleptic equivalent is also , 1776, with no further shift required as prior adjustments had been absorbed. Britain's official adoption of the Gregorian calendar in 1752 involved skipping 11 days to synchronize with the proleptic Gregorian system. September 2, 1752 (Julian), was immediately followed by September 14, 1752 (Gregorian), effectively aligning the calendar without retroactive changes to earlier dates. Russia's transition to the Gregorian calendar in 1918, decreed by the Bolshevik government, required skipping 13 days to match the proleptic Gregorian alignment accumulated since the Julian system's divergence. February 1–13, 1918 (Julian), were omitted, so February 14 became the new starting point.

Ancient and Cultural Dates

The proleptic Gregorian calendar facilitates the alignment of ancient historical and cultural dates with modern chronology by applying rules retroactively to periods predating 1582. For instance, the traditional date of Julius Caesar's birth, recorded as , in the , experiences a minimal shift under proleptic rules, remaining , due to the negligible difference in adjustments during that era. In , the Long Count calendar's creation date, denoted as 0.0.0.0.0 (4 Ahau 8 Cumku), corresponds to August 11, 3114 BC in the proleptic Gregorian calendar, providing a fixed reference point for correlating inscriptions and astronomical observations with global timelines. This conversion highlights how proleptic extensions enable precise of indigenous systems with solar-based Western dating. The , a reportedly predicted by the Greek philosopher Thales and documented by as occurring on May 28, 585 BC in the , shifts to June 5, 585 BC under the proleptic Gregorian calendar, reflecting an 8-day adjustment from accumulated discrepancies. Proleptic Gregorian application also supports the harmonization of ancient East Asian lunisolar records, such as those from the Taichu initiated in 104 BC by of the , which standardized the calendar year to begin near the second new moon after the and aligned earlier events like observances with modern chronological frameworks. Similarly, in Jewish calendrical studies, the proleptic Gregorian calendar aids in correlating pre-1582 Hebrew dates by extending consistent solar adjustments, exemplified by the traditionally placed at 3761 BC, equivalent to September 7, 3761 BC proleptic Gregorian, which anchors biblical and rabbinic timelines to contemporary scholarship.

References

  1. [1]
    Calendars and their History - NASA Eclipse
    Oct 14, 2012 · These rules can be applied to times prior to the Gregorian reform to create a proleptic Gregorian calendar. In this case, year 0 (1 B.C.) is ...
  2. [2]
    Glossary - Astronomical Applications Department
    The Julian calendar was superseded by the Gregorian calendar. calendar, proleptic: the extrapolation of a calendar prior to its date of introduction. catalog ...<|control11|><|separator|>
  3. [3]
    [PDF] Information interchange - Representation of dates and times — Part 1
    NOTE. In the proleptic Gregorian calendar, the calendar year [0000] is a leap year. ... ISO/WD 8601-1. 26. © ISO 2016 – All rights reserved. In the ...
  4. [4]
    java.util.GregorianCalendar - People | MIT CSAIL
    GregorianCalendar implements proleptic Gregorian and Julian calendars. That is, dates are computed by extrapolating the current rules indefinitely far backward ...
  5. [5]
    Introduction to Calendars - Astronomical Applications Department
    The Gregorian Calendar resulted from a perceived need to reform the calculation method for the dates of Easter. Nonetheless, the Julian Calendar and variations ...Missing: exact | Show results with:exact
  6. [6]
    Gregorian Calendar - The Galileo Project | Chronology
    The English and their American colonies finally adopted the Gregorian Calendar in the middle of the eighteenth century. George Washington was born on 11 ...
  7. [7]
    Lecture 11: The Calendar
    Sep 29, 2007 · Japan adopted it in 1873 (Meiji period); Soviet Russia adopted it in 1918. Communist China adopted it in 1949. Eastern Orthodox Church still ...
  8. [8]
    POMS: GN 00307.180 - Gregorian/Julian Calendar - 08/26/2005 - SSA
    Aug 26, 2005 · *The Greek Government adopted the Gregorian calendar for civil records on 03/01/1923. The Church of Greece (the Greek Orthodox Church) adopted ...
  9. [9]
    The Julian and Gregorian Calendars - Hermetic Systems
    A calendar obtained by extension earlier in time than its invention or implementation is called the "proleptic" version of the calendar, and thus we obtain the ...
  10. [10]
    Prolepsis - Etymology, Origin & Meaning
    Originating from Greek prolēpsis meaning "a taking beforehand," prolepsis means anticipation or assigning something prematurely, used in philosophy and ...
  11. [11]
    proleptic, adj. meanings, etymology and more | Oxford English ...
    The earliest known use of the adjective proleptic is in the mid 1600s. OED's earliest evidence for proleptic is from 1658, in J. Ussher's Annals of World.
  12. [12]
    Time Scales - UC Observatories
    Newcomb used Greenwich as the prime meridian for determining noon on the calendar date. Therefore by 1901 there could no longer be any question that the ...
  13. [13]
    Representations of time coordinates in FITS
    This representation of time is tied to the Gregorian calendar (Pope Gregorius XIII 1582). In conformance with the present ISO-8601:2004(E) standard (ISO 2004) ...
  14. [14]
    Making <time> safe for historians - QuirksMode
    Apr 6, 2009 · Because medieval historians use Julian dates, mapping medieval dates to proleptic Gregorian is going to cause widespread confusion. The machine- ...Missing: practices | Show results with:practices
  15. [15]
    Original date of text and/or object - EpiDoc
    It is generally recommended to encode the dating information in numerical form, following the proleptic Julian calendar, using the att.datable.custom ...2025-02-18 · Relevant Element... · Date RangeMissing: best practices
  16. [16]
    Leap Years - Astronomical Applications Department
    The Rule: According to the Gregorian calendar, which is the civil calendar in use today, years evenly divisible by 4 are leap years, with the exception of ...
  17. [17]
    GregorianCalendar (Java SE 17 & JDK 17) - Oracle Help Center
    The Julian calendar specifies leap years every four years, whereas the Gregorian calendar omits century years which are not divisible by 400. GregorianCalendar ...
  18. [18]
    Julian Day - Orbital Mechanics & Astrodynamics
    Astronomical year numbering is the same as the Gregorian year for all after 1 AD. However, the Gregorian calendar does not include a Year 0, whereas the ...<|control11|><|separator|>
  19. [19]
    Converting Between Julian Dates and Gregorian Calendar Dates
    The Julian date (JD) is a continuous count of days from 1 January 4713 BC (= -4712 January 1), Greenwich mean noon (= 12h UT1). For example, AD 1978 January 1, ...Missing: 0 | Show results with:0
  20. [20]
    DAYDATE: Computing Days between Dates, the Day of the Week, etc.
    For the 16,000 year calendar, let f(y) := 365 y + floor(y/4) - floor(y/100) + floor(y/400) - floor(y/4000) g(j) := floor( (j + 0.402)/365.24225 ) . j = D + f(y) ...
  21. [21]
    Julian/Gregorian Calendars - The University of Nottingham
    This meant that three out of four centenary years would not be leap years, or, that in every 400 years there would not be 100 leap years but 97. Using this ...Missing: floor(
  22. [22]
    The Tangled History of Leap Years - Time Magazine
    Feb 29, 2016 · Skipping three leap days every 400 years would keep the calendar and solar years in alignment, or at least closer to that goal—sometime near ...
  23. [23]
    Retroactively using the Gregorian calendar for ancient dates
    Apr 21, 2025 · The calendar that pushes the Gregorian calendar back in time, before the adoption of the calendar, is known as the proleptic Gregorian calendar.
  24. [24]
    Julian to Gregorian Calendar: How We Lost 10 Days - Time and Date
    Conversion between Julian and Gregorian Calendars. Currently, the Julian calendar is 13 days behind the Gregorian calendar. So, to convert from the Julian ...
  25. [25]
    The Gregorian calendar - Claus Tøndering
    In the Gregorian calendar, the tropical year is approximated as 36597/400 days = 365.2425 days. Thus it takes approximately 3300 years for the tropical year ...<|separator|>
  26. [26]
    Maya Calendar Converter | Living Maya Time - Smithsonian Institution
    Use this interactive tool to convert Gregorian calendar dates into the Maya calendar system. Find the meaning of each day in the Tzolk'in calendar system.The Calendar System · Reading the Calendar Glyphs · 2012: Resetting the Count
  27. [27]
    HTML5 (Edition for Web Authors) - W3C
    Apr 5, 2011 · The week-year number of a particular day can be different than the number of the year that contains that day in the proleptic Gregorian calendar ...
  28. [28]
    Approaching Challenges in Representations of Date–Time ... - MDPI
    This issue originates from the introduction of the Gregorian calendar, which reformed the Julian calendar by skipping ten days to realign with the solstices ( ...2. Background · 5. Results · 5.14. Reading Period<|control11|><|separator|>
  29. [29]
    Calendars in Temporal - TC39
    Temporal uses calendars like Gregorian and ISO 8601, specifying them for calendar-sensitive operations. Many places use other calendars, and calendar-sensitive ...
  30. [30]
    datetime — Basic date and time types — Python 3.14.0 documentation
    Return the date corresponding to the proleptic Gregorian ordinal, where January 1 of year 1 has ordinal 1. ValueError is raised unless 1 <= ordinal <= date ...Datetime -- Basic Date And... · Timedelta Objects · Datetime Objects
  31. [31]
    GregorianCalendar (Java Platform SE 8 ) - Oracle Help Center
    GregorianCalendar is a hybrid calendar that supports both the Julian and Gregorian calendar systems with the support of a single discontinuity.
  32. [32]
    Documentation: 18: 8.5. Date/Time Types - PostgreSQL
    PostgreSQL supports the full set of SQL date and time types, shown in Table 8.9. The operations available on these data types are described in Section 9.9.Missing: proleptic | Show results with:proleptic
  33. [33]
  34. [34]
    Dates and Time — Skyfield documentation - Rhodes Mill
    This “proleptic” use of Gregorian dates makes date calculations simple, is compatible with Python's datetime , and is also the behavior of the United States ...Utc And Leap Seconds · Date Arrays · Ut1 And Downloading Iers...
  35. [35]
    Introduction - Manual - PHP
    The date/time features in PHP implements the ISO 8601 calendar, which is a proleptic Gregorian calendar which implements the current leap-day rules.
  36. [36]
    George Washington's Birthday | National Archives
    This shift of 376 days accounted for the new year being celebrated on January 1 instead of March 25 plus the 11 day difference between the Julian to Gregorian ...
  37. [37]
    8 Facts about George Washington and Religion
    He was born "about 10 in the Morning" on February 11, 1731/32, according to the Julian calendar then in use. When England adopted the Gregorian calendar in 1752 ...Missing: Old conversion
  38. [38]
    May | 2017 | RICARDIAN LOONS
    May 5, 2017 · ... proleptic Gregorian calendar”. For example, the Battle of Agincourt is recorded to have occurred on St Crispin's Day, the 25th of October ...
  39. [39]
    Calendar Converter
    Britain and her colonies (including what is now the United States), did not switch to the Gregorian calendar until 1752, when Wednesday 2nd September in the ...Missing: proleptic | Show results with:proleptic
  40. [40]
    13.2.7 What Calendar Is Used By MySQL?
    ... proleptic Gregorian calendar. This is what is used by MySQL, as is required ... Russia remained on the Julian calendar until 1918, losing 13 days in ...
  41. [41]
    [PDF] the englishman from lebedian'— - a life of evgeny zamiatin
    the Russian Julian calendar and the Gregorian calendar used in Western. Europe, which meant that he had jumped forward 13 days, well into. April, as soon as ...
  42. [42]
    Julian Day Calculations (Gregorian Calendar) - Bill Jefferys
    It is easy (with your calculator) to calculate the Julian Day Number of any date given on the Gregorian Calendar.
  43. [43]
    Ancient Maya documents concerning the movements of Mars - PMC
    The date of this day in a proleptic Gregorian ... This beginning day of the era fell on Julian Day Number 584,283, corresponding to 11 August 3114 B.C. in a back- ...
  44. [44]
    The Lunar New Year: Rituals and Legends - Asia for Educators
    In 104 BCE Emperor Wu of the Han dynasty (206 BCE to 220 CE) approved a calendar reform that fixed the beginning of the year on the day of the first new moon ...