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…

Maybe a Tool would add less overhead? There is a “HasInValidDate” Events rule too. (It is a Manually Installable Isotammi add-on .) There might be a way to leverage that? Perhaps an export, exit Gramps, switch to the other language, restart Gramps and import? Unfortunately, that might overwrite or i…

To make it easy, I looked at my old hack on GitHub, and changed the ISO parser a bit, so that it swaps day and year when the day is larger than 99. And that works.

[image] emyoulation: A script could leverage @kku ’s HasInValidDate query rule’s code and just try to recommit all the invalid date events while Gramps is active in the appropriate language. I recently imported a 1996 Brother’s Keeper GEDCOM to a blank tree to make an example Gramps tree that …

Dates present even more complexity. The Events Filter Gramplet’s filtering: is on the date value unless it is an Invalid date does not search the formatted date string as displayed has a doubled factoring of date range adjustments does not apply RegEx in the compares That means to effectively us…

Hi, I’m new to gramps and just met a similar issue. I exported a GEDCOM from familysearch. In Familysearch I have some dates that are in english and some other dates that are in Italian (they are both valid dates for familysearch). My Gramps is set to use english language and YYY-MM-DD ISO format…

Hi Rocco, Nice to see you here. Like I wrote on Facebook, the real problem is in RootsMagic, and maybe it’s better if we address the problem there. All dates are OK if you download Adele and relatives with Ancestral Quest or Legacy Family Tree. The problem that we encountered is that RootsMagic do…

I asked Rocco to cross post. The thought was that maybe some discussion can help evolve his SuperTool script and make it more easily adapted by the next user. The particular problem he describes is usually short-lived. So the first person makes a broad hack at a resolution, manually tweaks the resu…

OK, thanks! Cross posting is a good idea, because Discourse gives us way more flexibility with messages, and also way more screen estate, to keep things clear. I’m still in doubt about the right approach though. We have GEDCOM files with weird dates, caused by anomalities in other software, like An…

The problem is that the dates were not saved (in FamilySearch or RootsMagic, etc) as a valid date and are imported as purely Text. When we enter the date in an Event record, as part of saving the event Gramps takes the date, which we entered as text, and converts it to a valid date. You probably no…

[image] DaveSch: I do not know of any bulk process that will take care of these dates. Others may have had found a process to make the conversion from Text to Date. With SuperTool, it is simple to find all the invalid dates events, poll the text string, pass it back through the parser & commi…

Making date input more flexible

Ideas

Topic		Replies	Views
Importe von Ancestry zeigen Datumsangaben auf tausend verschiedene Arten an Deutsch (German) data-import	9	107	January 27, 2026
Invalid dates on import because language not installed Ideas	1	296	October 19, 2022
US and DE date formats mixed up in Ancestry GEDCOM import Help	35	1189	May 6, 2023
Format dates from day-month-year Help dates	17	1643	August 6, 2024
Data verification & Dates [ Identify invalid dates ] Help	5	187	August 11, 2025

Making date input more flexible

Related topics