Gedcom 7 Library [ Future basis of a new Gedcom 7 import addon ]

Development
,
23

Are you sure?

I didn’t actually try, but looking at the code it rather looks like Gramps XML itself is versioned independently of Gramps version:

It would be silly having to use an older version with less bug fixes.

24

The Gramps application version and the XML schema IS versioned separately.

It is the importer that complains (when it should not) about the file being created by a newer version of the Gramps App.

And that is misleading in any case. It is an external converter application generating the file and it should identify itself as that.

Since it generates XML different than the Gramps application would from the same GEDCOM, it should identify as the version of the Web Convertor App

25

What I am claiming is that this dialog will only appear if the XML schema has a mismatch, not if the Gramps version has a mismatch, even if the error message seems to imply otherwise. See here for the code:

Consequently, a user running 6.0.0 will not see an error message for files created under 6.0.5.

1 Like
26

Ok. I extrapolated from what was necessary to make 5.2.2 load a .gramps file from the converter.

I thought that only editing the XML schema down to 1.7.0 would be sufficient. But Gramps argued until I lowered the Gramps version too.

27

Maybe just ignore citation references from event for individuals? By looking at changes/improvements, I saw this one:

+/database/people/person[0]/eventref[0]/citationref[0]
+/database/people/person[0]/eventref[0]/citationref[0]/@hlink
1 Like
28

New and drastically improved release:

Since Gedcom 7 import addon by DavidMStraub · Pull Request #744 · gramps-project/addons-source · GitHub is blocked, I’ll soon proceed to add dedicated import logic (using version 5/7 detection) to Gramps Web API.

3 Likes