Louis Kessler’s Behold Blog     The Behold User Forum

You indeed sound excited today (or this morning your time). So does all this excitement, extend to your head nodding response at RootsTech2012 re implementing support for a 'new' GEDCOM standard within 30 days of release of said standard?

A few more results, all Opened the file, without any report. GRAMPS GENViewer GENMatcher

Your comment 'I wonder how bad a problem this is and if there are very many other programs out there that might choke on the “nothing” in the RootsMagic GEDCOM' made me think hard about the same. Thanks Louis (and Bart) for a copy of the GEDCOM file. Results for some software include: Ahnenblatt ...

You state: 'This code needs to be fast'. But what actual effect to Behold load time will this do for large GEDCOM files?

Again, thanks Louis. I had been doing it manually and then noticed this old post last night. It is not a problem as such, but would have made my corrections a little faster.

On Thu, 3 Dec 2009 you posted: However, Tamura's review has already led me to think I should reinstitute the logfile that was in versions of Behold up to 2 years ago. It integrates the log and the GEDCOM files together in a window which would allow clicking on an error message and taking you right to the line ...

Thanks for the clarification on dates.

Thanks Louis. To continue a little, do you consider BetterGEDCOM would be looking at incomplete dates as part of their charter? It seems to me that where some data is known, eg only day or month but no year, it needs to be kept in the GEDCOM, and within Behold, as you have stated above. However, if Behold will ...

Where sufficient data is not recorded eg only 13 APR, should the GEDCOM be produced containing or excluding the non valid data? Is it correct under GEDCOM standard to convert non valid dates to a date phrase? When 1.5 or 2.0 arrives, how do you think Behold will export date phrase to GEDCOM?

This is great news Louis, although I do not wish to be the cause of any delay in your quest to vs 1.5.