Louis Kessler’s Behold Blog     The Behold User Forum

Over at BetterGEDCOM, they're crossing the entire spectrum of dates, from simple to complex to international, so everything is being looked at. Personally, I don't think that GEDCOM did that bad a job at defining dates. I like the concept of date phrases for anything that isn't a standard date. A partial date ...

It is not correct to put 13 APR into GEDCOM. That is definitely illegal syntax. There is no "correct" or "not correct" regarding converting non-valid dates to a date phrase. It is my personal opinion that it is best to do so, so that the information entered is still associated with the date and is not lost. ...

The first four are invalid. You need the year to have a month and you need the year and the month to have the day. Behold will put the first 4 into parentheses, e.g. (13 APR) to make them a date phrase which is valid. The last two are both valid.

Well, my idea for Virtual Merging is extremely necessary. Too often, people are merging other people's GEDCOMs into their own, trusting that other people did theirs correctly and proliferating what are called "junk genealogies". Not only that, you WANT to keep your work separate. If relatives send something ...

Seecan: Currently, Behold will import two (or more) GEDCOMs and display them together. The current weakness is that it currently has no way for you to indicate the people who you know are the same in the two families, so every duplicated person will be shown twice. In the case of your paternal grandfather and ...

Brett: Thanks for this. Yes that is a bug. It should not include the day of the week in the error message. It should simply say: ** Date NonStd (#43): Should be "26 MAY 1935" to conform to GEDCOM standards. I'll make that fix and squeeze it into a Version 1.0.2 tonight. Actually, I have to sheepishly say, I ...

Yes, Legacy corrects your data for you. I don't understand how it might do it. It's not just a matter of adding a comma at the end. It has to know one is missing. That means it has to know that is a State abbreviation at the end. What if it's a State name instead, e.g. Texas instead of TX. Will it add the ...

I'm reading back my last post. I hope I didn't sound terse. I didn't mean to. I just wanted to say that I'm trying to present your data in Behold in the most useful way possible. If Behold isn't reading your data as you thought you had entered it, then no other program will either. That's why it's important ...

So let me understand. You want an option to sort places either "the correct way" or "the wrong way". Behold sorts the correct way so that you can correct your mistakes. Is there a reason under the Place details as to why you would want events sorted by date first? I cannot see a reason because there are no ...

esd: The simple test I did exporting from Legacy with default export options resulted in the same situation as you had, where Behold did not seem to report every place. But when I looked in the GEDCOM file Legacy produced, I saw there were a number of people marked PRIVATE with no events or places attached to ...