Richard Damon commented on this topic: > My bigger complaint is that TMG doesn't really have a way > to indicate that a date is Julian (aka Old Style), only that > it should be double dated (only Old Style dates can be > double dated, but not all Old Style dates should be double dated). But Richard, as I noted in my reply to Barbara, TMG *does* have a way to indicate a single year date which falls within your "Old style date range" as being an Old Style date. I noted: > if you wish to output a date using an Old Style single year format, > enter "24 Feb 1691 OS" in the Date field, *BUT* put a non-breaking > space (Alt + 255 on the numeric keypad) between the year and 'OS'. > TMG will now treat that date as irregular and output it as entered. > Now be sure to enter a regular date using any of the recognized > input formats such as "24 Feb 1691/92" or "24 Feb 1692 OS" in > the Sort Date field so it will sort appropriately. As I noted to Barbara, any single-year date entered in TMG is assumed to be New Style. Even a date which "could" be double dated (such as a January or February date in a year within your "Old style date range" as specified in Preferences // Program Options // General), will be assumed to be New Style and will not be double dated. To cause a date within the "Old style date range" to be stored and later output in TMG as a double-year date, you must either enter the _New_Style_ date with the code 'OS' following it, or enter the date as a double-year date. I agree it is somewhat confusing in that the code 'OS' in a date entered in TMG (e.g. "24 Feb 1691 OS") does NOT mean that "24 Feb 1691" is an Old Style date. Instead it is telling TMG to store and later output this New Style date of "24 Feb 1691" as a double-year date. Because of this potential confusion, if I want a double-year date I always enter it as a double-year date. By the way, the only impact of the "Old style date range" in Preferences is that TMG will now recognize a date _within_ that range entered with one of the specified Old Style input formats as a request to store a double-year date. That allows "24 Feb 1691/92" or "24 Feb 1692 OS" to produce double-year dates when those years are within your range. But any date not in your range entered with one of those formats will NOT trigger the date to be stored as a double-year date. For example, the equivalent input of "24 Feb 1891/92" will produce "between 24 Feb 1891 and 1892", and a date input as "24 Feb 1892 OS" will be considered an irregular date. Even "24 May 1691/92" will not trigger a double-year date but will produce "between 24 May 1691 and 1692". Hope this helps explain this somewhat confusing topic, Michael