|
Forum Members
Last Login: Wednesday, February 19, 2020
Posts: 4,
Visits: 18
|
I am the author of several programs that process GEDCOM files. Some users have sent me GEDCOM files exported from GenoPro. The HEAD record from one of the files looks like this:
0 HEAD
1 SOUR GenoPro
2 NAME GenoPro® - Picture Your Family Tree!(TM)
2 VERS 3.0.1.1
2 CORP GenoPro
2 ADDR http://www.genopro.com
1 DATE 1 DEC 2018
1 CHAR UTF-8
1 GEDC
2 VERS 5.5
2 FORM LINAGE-LINKED
0 GLOBAL
... |
That file includes several non-standard GEDCOM records, as do other similar files where the SOUR value is "GenoPro". While doing some research on this, I discovered that there is a plug-in (or skin?) for the GenoPro report writer that also creates GEDCOM files. I found a GEDCOM file online that may be written by that plug-in/skin, I am not sure. It's HEAD record looks like this: 0 HEAD
1 SOUR GenoPro®
2 VERS 2.0.1.3/2007.02.28
2 CORP GenoPro Inc.
3 ADDR http://www.genopro.com
1 DATE 3 DEC 2007
1 SUBM @subm1@
1 GEDC
2 VERS 5.5
2 FORM LINEAGE_LINKED
1 CHAR UTF-8
0 @ind01542@ INDI
... |
The example above is from 2007 so it may not be of any use. The HEAD record has some obvious differences, such as the SOUR value: "GenoPro" (ex 1) versus "GenoPro®" (ex 2). I assume the "Â" character is the result of some character encoding issue, perhaps caused by the way the files were handled before they got to me. The HEAD record for example 2 is valid except for the "_" in "LINEAGE_LINKED", which should be "-", i.e., "LINEAGE-LINKED". So, my questions: 1 - Do GenoPro users use the plug-in/skin to export GEDCOM files from GenoPro? 2 - What is the SOUR value written by the plug-in? I'd like to use the SOUR value to distinguish between the two GenoPro GEDCOM types, but I am not confident I have a valid example file from the plug-in. Thanks for any help you can offer! John
|