|
|
|
Junior Member
 
Group: Customers
Last Login: 3/1/2008 9:36:44 PM
GenoPro Version: 2.0.1.4
Posts: 18,
Visits: 41
|
|
| Using 2.b15d and exporting a Gedcom file with hyperlinked individuals on different genomaps seems to create two individual records for each individual. It looks like this works with most applications that read Gedcom files, and I am just curious as to how the link between the two individuals in Gedcom format works. I am asking mainly because I would like to export Gedcom files from GenoPro for use in Genelines and currently everything works great except I can't see ancestors of an individual on a certain genomap. I can provide my .gno file if need be. As a workaround I moved everyone to one genomap, deleted the duplicate individuals that had tied the genomap together (thus making one gigantic tree), and exported everyone as a Gedcom file. This worked perfectly but it's a tedious process to go through each time I make changes to the original genomapped .gno file. Thanks for your time & hard work, Beau.
|
|
|
|
|
Legendary Master
Group: Administrators
Last Login: Today @ 12:17:52 PM
GenoPro Version: 2.b17i
Posts: 3,485,
Visits: 14,580
|
|
At the moment, all individuals are exported in Gedcom with the INDI tag. As a result, an hyperlinked individual is stored twice in the Gedcom file. GenoPro has a mechanism to determine if an individual is an hyperlink of another individual, however other Gedcom-compatible applications cannot, thus producing duplicate entries for every hyperlinked individual. A similar question was posted regarding hyperlinked families.I have thinking of using the _INDI tag for hyperlinked individuals. Using the _INDI tag requires a fair amount of work, including the replacement of the current XML parser. At the moment, it is not the time to do it because GenoPro relies too heavily on the XML import to risk new bugs. Once GenoPro 2.0 is out, it will be safe to upgrade the import module.
|
|
|
|
|
Junior Member
Group: Customers
Last Login: 3/1/2008 9:36:44 PM
GenoPro Version: 2.0.1.4
Posts: 18,
Visits: 41
|
|
| Makes sense--are there plans to modify the Gedcom exporter to spit out files that won't be readable back into GenoPro with genomaps or with the other GenoPro-specific options? I.e., solely for import into other programs that don't know what to do with genomaps? (Or is that basically what _INDI support will accomplish while still allowing GenoPro-specific features?) I will make due with my workaround in the meantime and eagerly await 2.0 final and beyond. Just bought 1 user license, by the way--had been making do with the beta but figured I should finally buy it once the registration dialog popped up in beta 15. Thanks again and keep up the excellent work!
|
|
|
|
|
Legendary Master
Group: Administrators
Last Login: Today @ 12:17:52 PM
GenoPro Version: 2.b17i
Posts: 3,485,
Visits: 14,580
|
|
We will fix this issue for sure, however the fix will be after version 2.0. GenoPro will also have the option to create a clean Gedcom file - without the GenoPro specific tags.
|
|
|
|
|
Junior Member
Group: Customers
Last Login: 3/1/2008 9:36:44 PM
GenoPro Version: 2.0.1.4
Posts: 18,
Visits: 41
|
|
I tried out the Tools -> Generate Report... -> Skin Name: "Export to Gedcom {EN}" option today with 2.b19g and the resulting Gedcom file was readable by Progeny Genelines without major issues. 
|
|
|
|