The real problem seems to be database incompatibility.
The reason GDBI and PGV work so well together is that they
both use GEDCOM as their database. Other programs do as
well. But most full-featured programs, like Gramps, use
their own database which may be better than GEDCOM, but is
incompatible. Most programs provide GEDCOM import/export,
but you may lose info on the export, since they store info
that GEDCOM can’t handle. As they said in the Gramps
forum, they can only import a GEDCOM file as a whole.
The only hope would be converting this to a record-by-
record import/export. This conversion could be done by
either GDBI or Gramps, but it would take some work, and as
I mentioned above, you might lose data on the conversion.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=325184
GDBI is Java, and Gramps is Python, so it would be a major
conversion effort.
Logged In: YES
user_id=910179
see new comment at
https://sourceforge.net/tracker/index.php?func=detail&aid=1183817&group_id=25770&atid=385140
Logged In: YES
user_id=325184
The real problem seems to be database incompatibility.
The reason GDBI and PGV work so well together is that they
both use GEDCOM as their database. Other programs do as
well. But most full-featured programs, like Gramps, use
their own database which may be better than GEDCOM, but is
incompatible. Most programs provide GEDCOM import/export,
but you may lose info on the export, since they store info
that GEDCOM can’t handle. As they said in the Gramps
forum, they can only import a GEDCOM file as a whole.
The only hope would be converting this to a record-by-
record import/export. This conversion could be done by
either GDBI or Gramps, but it would take some work, and as
I mentioned above, you might lose data on the conversion.