Louis Kessler’s Behold Blog The Behold User Forum
Forum Posts
182.
NAME identifier and date orplace - Forum post by lkessler in General Discussion - 17 Mar 2012
Brett:
Comparing the logs you sent me from VGedX and GED-inline tells me that GED-inline gives better messages.
VGedX said: "Unknown record found" which doesn't tell you much, but GED-inline tells you "Tag DATE is not allowed under NAME" and "Tag PLAC is not allowed under name".
GED-inline is correct. DATEs ...
183.
NAME identifier and date orplace - Forum post by brett in General Discussion - 16 Mar 2012
Am I able to input an AKA under Name, to include a date and place known as that individual, and retain GEDCOM standard?
My GEDCOM is exported as:
1 NAME Caroline Juliette Edmonds
2 DATE 12 MAR 1891
2 PLAC Sydney, New South Wales, Australia
however this flags as an error, Unknown record found, in vGed 3.04.
It ...
184.
5.5.1 compliant GEDCOM file - Forum post by lkessler in General Discussion - 11 Mar 2012
What I'll probably do is:
0 HEAD
1 SOUR Behold
2 VERS 1.0.4
2 NAME Behold version 1.0.4, 23 Jan 2012
185.
5.5.1 compliant GEDCOM file - Forum post by brett in General Discussion - 11 Mar 2012
Louis
Does the GEDCOM character limit include the TAG?
If no, would this be suitable for vs and date?
VERS xx.x.x mm-dd-yy
Brett
186.
5.5.1 compliant GEDCOM file - Forum post by lkessler in General Discussion - 11 Mar 2012
Brett:
Good catch. Behold was not reporting extra spaces between date parts. Next version will.
Comparing the GED-inline and VGedX reports you sent me, I see that GED-inline reports all 7 problems that VGedX does but with better messages, and then finds 17 more problems, most of which are CONT tags where they ...
187.
5.5.1 compliant GEDCOM file - Forum post by brett in General Discussion - 10 Mar 2012
OK, so I did jump too early.
I have validated through the above and also Genealogica Grafica and GenMatcher.
I will report all errors in an email.
In the meantime, the one error of most interest is:
Invalid content for DATE tag: '28 APR 1997' is not a valid <DATE_VALUE>
This does not error in Behold. ...
188.
5.5.1 compliant GEDCOM file - Forum post by lkessler in General Discussion - 10 Mar 2012
Brett:
Don't jump for joy just yet. Behold won't do complete GEDCOM checking until Version 1.5 and right now it lets a few things go.
You should also try a couple of other validators: VGedX at http://ancestorsnow.com/tools/vgedx.php and GED-inline at http://ged-inline.elasticbeanstalk.com/validate
I wouldn't ...
189.
5.5.1 compliant GEDCOM file - Forum post by brett in General Discussion - 10 Mar 2012
After several years, much assistance from Behold's great GEDCOM validation, advice from Louis and support from Darrin and the User Group of The Next Generation of Genealogy Sitebuilding (TNG), I now have a GEDCOM exported file which meets 5.5.1.
What a pleasure it was to see
'No problems to report.'
in the File ...
190.
Invalid date format - Forum post by lkessler in General Discussion - 10 Mar 2012
Brett:
It depends on the program and what it lets you do. If programs allow date phrases, which are dates in any format whatsoever, then that would be fine. A date phrase in GEDCOM is any expression enclosed in parenthesis, e.g.:
2 DATE (April 13)
If that is not allowed in your program, I'd just add it as a ...
Prev 171-180
NAME identifier and date orplace - Forum post by brett in General Discussion - 17 Mar 2012