|
|
|
|
|
|
|
The same papyrus gives an account of the later battle between Osiris and Typhon occurring the 26th day of the month of Thoth, a day marked in the calendars as triply deadly. |
|
|
|
|
|
|
|
|
Likewise, Budge (Introduction, p. lii, footnote) provides a translation of a hymn of praise to Osiris, stating that the Uak festival occurred on the 17th and 18th days of the month of Thoth. A similar footnote (Introduction, p. li) gives the date of the ceremony of "setting up the Tet in Tattu" as the last day of the month of Choiak. |
|
|
|
|
|
|
|
|
Similarly, Budge observes a footnote that the first, third, and fifth epagomenal days of the calendar were considered unlucky (Introduction, p. xlix). |
|
|
|
|
|
|
|
|
From these observations, two conclusions may be drawn regarding application code: |
|
|
|
|
|
|
|
|
A reading of the Egyptian calendars supplies a list of the various days of religious observance. This list may be used to produce functions of the fixed date type for the dates, which would allow computer generation of an Egyptian religious calendar for arbitrary years. |
|
|
|
|
|
|
|
|
Calendars tightly bound to religious practice often include an additional datum about a date whether it is propitious or not. This finding suggests the addition of one or more variables to the appropriate date structure, and perhaps its strength where it is important, to include these factors. In the case of the ancient Egyptian calendar, an application might therefore add the following structure: |
|
|
|
 |
|
|
|
|
struct DATE_INFO_EGYPT
{
int year;
int month;
int day;
int luck;
}; |
|
|
|
|
|
|
|
|
and use the variable luck as a signed indicator with values such as: |
|
|
|
|
| Value | Meaning | | triply unlucky | | doubly unlucky | | unlucky | | neutral | | lucky | | doubly lucky | | triply lucky |
|
|
|