That would be because the FAA has been trying and failing to upgrade their IT for darn near 50 years. MMDDYY was the standard way to code dates in the 1960s. Getting that fixed was what the Y2K apocalypse was about.
But while it's a nice standard that works a tread for the backends it's not something to impose on users. If you want to write dates as MM-DD-YY GnuCash should accept that. Regards, John Ralls > On Oct 12, 2023, at 17:02, Dean Gibson <gnucash.st...@mailpen.com> wrote: > > Actually,, ISO8601 describes the valid (& preferred) date representations. > Anything with dashes is presumed to be YYYY-MM-DD. Of course, just because > this is an international standard, doesn't mean that everyone (including > governments) follows it. This includes the US FAA. which presumes MM-DD-YY. > > So much for standards! I guess ISO8601 is pretty new (35 years ago) for some > organizations! > > On 2023-10-12 16:27, john wrote: >> ... >> >> Another more involved fix would be to make the date parser a bit more >> liberal about delimiters and formats; the only slightly minor difficulty is >> ordering ambiguous sequences: for example 21-10-23 could be 21 October 2023 >> or 23 October 2021 and 5/7/9 could be the 9 July 2005, 7 May 2009, or 5 July >> 2009. >> >> Regards, >> John Ralls >> > _______________________________________________ > gnucash-user mailing list > gnucash-user@gnucash.org > To update your subscription preferences or to unsubscribe: > https://lists.gnucash.org/mailman/listinfo/gnucash-user > ----- > Please remember to CC this list on all your replies. > You can do this by using Reply-To-List or Reply-All. _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
