RootsWeb.com Mailing Lists
Total: 1/1
    1. Re: [TMG] error in TMG's handling of Old Style dates
    2. Richard Damon via
    3. On 11/3/15 4:30 PM, Michael J. Hannah via wrote: > 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. I wouldn't consider this 'support' for Julian dates, anymore than the fact we can enter irregular date support for the Quaker Dating system or the Jewish Calendar. (One big factor is that making a date irregular affects so many things). I am not sure if I have ever seen a program that REALLY handles Julian dates properly (i.e. knows the difference between the types of dates and fully handles the differences). I suspect the problem is that to someone not really aware of the issues, treating Julian dates as if they were Gregorian (which is what most programs do) just seems to work. You will find that many will support the double year notation, as this is a common notational issue, but many assume that it is related to the Julian/Gregorian switchover (which it really isn't, it is caused by the change of the start of year which was forced by the Gregorian calendar, but also occurred prior for some usages, and actually should be used for ANY Julian date in the Jan-Mar time frame where the Julian date uses the March year change, not just those after 1582 unless the program REALLY supports that form of the Julian calendar and treats Jan xxxx as after Dec xxxx). -- Richard Damon

    11/06/2015 01:49:28