Louis Kessler’s Behold Blog     The Behold User Forum

Very interesting observations, Enno. I don't share your negativism though. I think it is still early in the life of these APIs and they will evolve, maybe even into something quite different that we might not be able to foresee until it happens. Louis

Enno, I don't have much experience with the APIs out there yet. But I am seeing that more and more of the online genealogy repositories and online family tree collections are making evidence through sources and documents more important parts of their systems. That has to mean that they will at some time in ...

Arb: Now I know you. You're Amos Bannister. I've been following your Geneatools blog as well as your Tracing the Footsteps of Amos blog for some time now. I may even have added a comment on your blog at some time to encourage you. You have interesting ideas. Don't get discouraged. Keep forging ...

Thanks, James. Arb: I am VERY curious about "the genealogical tools" you mention that you are writing. Can you shed more light on them? Regarding FHISO, you make very valid points. Telling me won't help them, though. Louis

Arb, Unfortunately, the initial APIs must be created first by each developer to put in context the range of what's required. Only then can the different APIs be analyzed and some standardization can be agreed on. And it usually takes a bit of chaos before there becomes a widespread realization that a ...

Thanks, Deckie. I appreciate those nice words. And as far as informing goes, I do hope to restart my newsletter to those who've opted in once this current version comes out. The last Behold News newsletter I sent out was in January 2012. Louis

Thanks, Arnold for sending this. The problem is fixed and will be included in the upcoming version 1.1. Also, in Version 1.1, I've made the missing BOM a warning, since although Behold handles this, some programs won't correctly process a UTF-8 file without the BOM. Despite the incorrect messages, the current ...

Arnold, This seems like it might be that the file has a BOM (Byte Order Mark) that is inconsistent with the 1 CHAR set specified in the file, or the GEDCOM file might not match the 1 CHAR set. Would you mind sending me at least the log file, and (if you don't mind) the GEDCOM file as well, and I can see what's ...

GEDCOM's error checking is only "good" right now. It will get much better when I implement export to GEDCOM 5.5.1 because I'll have to ensure the export is completely valid. I also will be trying to do simple corrections to input when the GEDCOM is wrong, if it is obvious and non-ambiguous what the data was ...