New calendar and old calendar: how parish software should keep either faithfully

Ask two Orthodox parishes what day it is, and you may get two different answers. One keeps the new calendar; the other keeps the old. Both are Orthodox, and both are right. The difference between the new calendar and old calendar is not a preference or a rounding error — it is a settled part of how a parish receives its saints, its tone, its appointed readings, and its fast. Good parish software should never flatten that difference into a single civil grid. It should hold whichever calendar your parish keeps, and let everything else follow faithfully from that one choice.

What the new calendar and old calendar actually are

The two calendars part company over the fixed feasts — the ones tied to a date rather than to Pascha.

The old (Julian) calendar now runs thirteen days behind the civil calendar most of the world uses. So the Nativity of Christ, kept on December 25 by the reckoning of the Church, falls on January 7 in civil terms for a parish on the old calendar. The new (Revised Julian) calendar was aligned so that these fixed feasts land on the same civil dates as the Gregorian calendar — December 25 is December 25.

What the two share is the movable cycle. Nearly all of the Orthodox world still computes Pascha by the older Paschalion, so a new-calendar parish and an old-calendar parish usually keep Pascha on the same Sunday — and with it the same tone of the week, the same Sunday gospels, the same unfolding of the Triodion and Pentecostarion. The disagreement is real but bounded: the fixed feasts of the menaion diverge; the paschal cycle mostly does not.

Which calendar a parish keeps tends to follow its jurisdiction and its history:

• New (Revised Julian): commonly the Greek Orthodox Archdiocese, the Antiochian Archdiocese, the OCA, and many Romanian and Bulgarian parishes.
• Old (Julian): commonly ROCOR, the Serbian Orthodox Church, the Church of Russia, the Church of Jerusalem, and the monasteries of Mount Athos.

There are exceptions and local variations in every direction, which is precisely why software should read the parish's setting rather than assume one.

Why the difference is pastoral, not just technical

For the person in the pew, the calendar is not an abstraction. It is when the Nativity Fast begins, when the parish keeps its patronal feast, when a child's nameday arrives, when a family expects the Nativity liturgy.

Move the calendar and all of it moves together. The fast that starts on November 15 by the Church's count starts on a different civil evening for an old-calendar parish. The feast, the fasting rule that lifts for it, the commemoration read that morning, the tone sung that week — these are not separate settings to be toggled one by one. They are one fabric, and the calendar is the loom.

This is why a generic tool struggles. It can put "Nativity" on a date because someone typed it in. It cannot tell you that the fast is in its second week, that today permits wine and oil, that the reader needs a particular epistle — because it does not derive the day from the calendar the parish actually keeps.

What "keeping either faithfully" asks of software

Faithful means that a single, honest setting — the calendar your parish keeps — drives everything downstream:

• The saint or saints commemorated on that day, by your calendar
• The tone of the week, drawn from the shared paschal cycle
• The appointed readings, fixed and movable together
• The fasting rule for the day, including the relaxations a feast brings
• Fixed feasts placed on the correct civil date, so the bulletin and the sign-up sheet agree

When the calendar is set once and the rest is computed, the parish stops maintaining a hand-typed events list that drifts out of true by mid-Lent. This is the work behind our living typikon, and it is why the parish calendar shows the shape of the day rather than a blank square.

Mixed practice, transitions, and honest limits

Not every parish is tidy. Some keep the fixed feasts on one calendar while a particular commemoration, a founder's memory, or a local custom follows another. A parish may be mid-transition, or serve a community that spans both practices.

Software should meet that honestly. It can compute the day cleanly for the calendar a parish keeps, and it can make the edge cases easy to see and adjust — but the rector confirms them. A well-prepared calendar is a strong starting point, not the last word. The last word is pastoral, and it belongs to the priest.

The point

The choice between the new calendar and old calendar is one a parish has usually already made, quietly, long before it opens any software. The software's job is not to have an opinion about it. Its job is to keep that choice faithfully — to let the saints, the tone, the readings, and the fast all follow from it — so that the day the parish is actually living is the day on the screen.