Building on Dates are bold on importing for a few dates:
When I set Gramps to use Dutch dates in the dd month year format, it will recognize Dutch month names like Mei, Juni, and Oktober, or their 3 character abbreviations, which is nice when I use Dutch sites that write mont names in full. It will not recognize a format like 30-09-2020 however, which is how today is spelled on most Dutch archive sites.
I also often use English speaking genealogy sites, which use May, Jun(e), or Oct(ober), and these dates give errors here, because when configured as above, Gramps can only read Dutch names.
This means that in both situations, I have to retype the month name, from May to Mei, or 09 to Sep, which I find quite annoying. And I think that I have some code in my gramps34 branch that cures this, by trying English as a fallback, and by running the ISO date processor, and let it reverse the date interpretation when the day number is larger than 2 digits.
Reading (long) English dates in dd month year format will also cure the problem listed in the cited message, which refers to Ancestry always exporting long names, even though that is against the GEDCOM rules. And I know that these long names also appear in the GEDCOM files created by the GetMyAncestors tool, also known as FSTOGEDCOM.
Would it be an idea to integrate my hack in 5.1?