qpp_TempSaints.txt contains the regular saints and namedays temporary table prepared for diary generation.
Its records use a month and day, rather than a complete calendar date, so the same entry can be used in different years.
Column |
Interpretation |
CountryID |
Internal holidays-set ID holding the saints/namedays list. Resolve it from the script’s saints/namedays selections. |
Month, Day |
Month/day key of the recurring entry. There is no year column. |
Sex |
Stored gender code used by saints/namedays processing. Do not infer a numeric mapping from the sample alone. |
Value |
Stored name or list of names. Keep accents, spaces, separators, and text markers intact. |
GraphicsPath |
Stored graphics path, if present. NULL means no path is supplied in this field. |
NoSite |
Site identifier; preserve it as text. |
The exact names matter: this table uses CountryID, while the holiday export uses Country_ID. Match by field name and meaning when comparing the files.
CountryID Month Day Sex Value GraphicsPath NoSite
10041 1 1 0 "Ste Marie" NULL "001"
This row supplies the stored text “Ste Marie” for 1 January in set 10041 at site 001. The simple-run file contains 366 entries for that set, including a 29 February entry. A leap-day record does not mean that every year being generated is a leap year.
The complex-run file has no data rows and a footer confirming zero records. That is a complete empty export for that run. Check whether the script requires a saints/namedays list before interpreting an empty table as a problem.
The sample stores prefixes such as “Ste” and “St” within Value. Do not add, remove, or expand them merely from the column name. The actual output also depends on the selected token variant, language, and saints/namedays options.
Diagnosing a Missing or Unexpected Name
1. Resolve the effective set from Saints/Namedays and any DiaryGridLine override in Saints/Namedays Options. The holidays aeiou mapping is not automatically the saints mapping.
2. Find the matching NoSite, CountryID, Month, and Day. If the row is missing, state which key was absent. If it is present, retain the exact Value and Sex for comparison.
3. Check the saints/namedays token and the options that affect prefixes, capitalization, separators, ordering, or the number of names displayed. The stored Value is the input to that processing, not necessarily the final printed text.
4. If the day’s saint is being replaced, inspect legacy saints exceptions and the “Combine with Holidays Set below” options. Holiday-based replacements require the relevant rows in qpp_TempHolidays.txt.
Report the exact month/day and set key, the stored text, and the script settings needed to explain any difference from the output. Do not treat a missing year column as missing data, assume the numeric gender mapping, or split a multiword name without considering the saints/namedays options.
See the diagnostic-files overview for quoting, escaping, NULL values, and completeness checks.
Topic 189925, last updated on 22-Oct-2026
