Instead of starting from scratch, consider open source genealogy projects. The application may not come with the report you want, but allow you to create that report. There are literally hundreds of genealogy applications and utilities.Ĭonsider the reporting capabilities of existing applications alternatives existing applicationsīefore creating your own application, consider some alternative approaches to fulfilling your need. It has to deal in a sensible way with a wide variety of GEDCOM dialects that feature anything from vendor-specific extensions,Īnd vendor mistakes to complete and utter disregard for the GEDCOM specification,Īnd from those real-world consideration follows the need to create an import log to inform users of any issues found during import. The structure of GEDCOM files isn't particularly complex, but there are quite a few issues a GEDCOM reader must deal with.Ī good GEDCOM parser must support multiple character sets and encodings, and multiple calendars.Ī GEDCOM reader must support multiple ways of encoding the same citation, and multiple ways of dealing with FamilySearch GEDCOM limitations. Reading a random ostensible GEDCOM file created by another application considerably less so. You are more than likely wildly underestimating the feature set of a good genealogy application in general,Īnd the complexity of quality GEDCOM parser in particular,Īs well as the limitations and outright sloppiness of the FamilySearch GEDCOM specification.Ĭreating a GEDCOM file from your own application is fairly straightforward, You're perchance considering creating some genealogy application or utility, and that's probably a bad idea. If you're looking for information on GEDCOM parsers, Open Source GEDCOM Parsers Ready-made GEDCOM support Creating a GEDCOM file from your own application is fairly straightforward,
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |