Louis Kessler’s Behold Blog     The Behold User Forum

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

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 ...

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 ...

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 ...

Brett: The way you did it (with a second NAME tag and no TYPE tag) is also an accepted way of entering two alternative names. The TYPE tag with "aka" is preferred but not required. When more than one NAME tag is given, GEDCOM instructs programs to use the first one as the "preferred" name. Louis

Brett, The short answer is to replace: 1 ALIA Letitia Holland with 1 NAME Letitia /Holland/ 2 TYPE aka The long answer is a blog post your question prompted me to post: The ALIA Tag of GEDCOM Louis

Brett: I've been working hard to see if I could squeeze what I would call "life events" into the individual profiles. I wrote about it in my Endless Possibilities blog post, where I said: I might want to also expand the parent links, child links, and spouse links within the individuals and families and turn ...

Brett: I included support for GEDCOM 5.5EL in Version 1.0.1. The info in the _LOC records is merged into Behold's Place details. Behold already had support for the _WITN tag and Behold's method of handling the ASSO and TYPE tags will handle them. The Find Files window will also identify GEDCOM 5.5EL files. I ...

BetterGEDCOM is probably stalled, not by FHISO and the necessity to make the new organization legal and give it structure, but probably by the effects of GEDCOMX and RootsTech interrupting matters. Once FHISO is legally underway, I'm sure they'll take a coordinating role, and use the BetterGEDCOM moniker to ...

At the time, the way I hoped to implement this was to integrate both the log file and the GEDCOM file into Behold. It was a nice idea at the time, but I later decided that this was not important functionality needed by Behold. The log file need only be there for the people who were interested and needed to ...