Mapiah recently highlighted a typo I made in some of my th2 files a year or so ago - detail here, but perhaps it is not important - [BUG] Parsing errors on opening some th2 files <https://github.com/rsevero/mapiah/issues/42> . Issue #42 . rsevero/mapiah I'm curious as to what Therion users understand is the intention with, or desirable for, the date range specification. The Therion Book says. Nothing there about the order of the dates, and it seems Therion is agnostic as to whether the earliest date in the range is specified first or last. I had always assumed incorrectly that the earliest date should be first. Survex date specification seems to be more flexible, allowing multiple distinct dates as well as ranges. I tried some variations of this with a single statement line with Therion, but it seems Therion cannot handle multiple distinct dates, unless multiple statements would do it - did not check. Survex 1.4.22 documentation - date <https://survex.com/docs/manual/datafile.htm#date> If Therion put up a warning when it detected a date range specified in the wrong order, then my typo might have been detected at the time. May I suggest that some date related warnings be added to Therion: * [author] [explorer] [topo] [copyright] date range in reverse order in [object name] * date earlier than 1900 AD in [object name] * future date specified in [object name] Bruce
