-
Since I started reading GEDCOM, I have always wondered why on some places in the GEDCOM, ADDR had to be used, and on other places PLAC.
Inside ADDR we have tags for CITY, STAE, POST and CTRY.
But in…
-
For some reasons I checked on GedCom 7 compability. The error check is based on GedCom 5.5.1. This gives a lot of error messages.
Request: Is it possible to do the error check based on GedCom 7 wh…
-
I've tried to import a gedcom into the Churchill demo without saving. Just as an experiment. Every gedcom I've tried so far, the import process skips every individual, but it seems that everyone and t…
-
The current [compatibility guide](https://gedcom.io/compatibility/) suggests compatibility with the specification is tied to supporting a wide set of features. I'd rather define it in terms of the ali…
-
As a sanity check it is worth checking that GEDCOMX fulfills the needs for the research process. In an attempt to prevent too much debate on the definition of the research process I am citing the mode…
-
I had forwarded to me a longer email that contained the following ideas, which I've re-expressed to remove the ideas from the context of that email.
----
We use 5.5.1 FAM records to express biol…
-
I used a Windows software to create my family tree, and this one supports call names, i.e. mark the typically used first name when the person has more than one first name. It would be great to at leas…
-
in [https://github.com/FamilySearch/GEDCOM/blob/main/extracted-files/grammar.gedstruct](url)
we have types, that reference types going round in a loop
, for example, look at the p…
-
What are your plans with respect to supporting version 7.0 of the Gedcom specification?
-
Erreur lors de l'export sous windows 7 avec Gramps 5.1.1
J'ai l'impression que c'est lié au chemin relatif des media
```
FileNotFoundError: [WinError 3] Le chemin d’accès spécifié est introuvable…