A brief update on the reworking of the logic around handling tags from a GEDCOM file. The use of the stack worked well, although that understates the issues involved with the free compiler and an unusual stack result from my code. For reasons I was unable to determine, the use of an index with the stack for some lines in one of the GEDCOM files produced spaces being pushed instead of an ‘OBJE’ tag, even though debugging showed that ‘OBJE’ should of been on the top of the stack. A rather frustrating time but using another approach to the stack resulted in ‘cleaner’ code and a more desirable and less troublesome result.
At this stage, there are many loose ends still to be completed, namely;
- HEADER; Name of source data, publication date and copyright messaging, transmission time, submission system, language, place and note,
- INDIVIDUAL; Restrictions, attributes, sealing and submission system, associations, ancestry and descendants interests, record file number, ancestry file number, reference number, automated record id and change date,
- FAMILY; Age of husband and wife at event, count of children, sealing and submission system, reference numbers, automated record id and change date,
- MEDIA; complete,
- NOTE; Source citation, user reference number, automated record id and change date,
- REPOSITORY; User reference type, automated record id and change date,
- SOURCE; Data, concatenation on some source fields, abbreviation, text (transcription), user reference type, automated record id and change date,
- SUBMITTER; Media, language, registered number of a submitter of Ancestral file data, automated record id and change date,
- EVENT; Address, age, responsible agency and cause of event,
- CITATION; Role in event, event data (includes transcription) and quality assessment.
Although the above list is long, it appears in processing many of my GEDCOM files, only afew tags are not processed but I will commence work on transcriptions.