Handling of CONC tags - Categorized in: Report a Problem

When I pull in a GEDCOM that contains CONC tags, they don't seem to be parsed correctly.

How I understand it is that when you have a long NOTE that needs to be broken down into multiple lines the additional lines start with either a CONT or a CONC tag. The CONT and CONC tags work exactly the same except where CONT puts in a space and then the text, CONC concatenates the text right onto the end of the last line. CONTinuation versus CONCatenation, I guess.

PAF seems to adhere to these standards pretty closely. Whenever there is a CONC tag the line starts with a word that is divided. FTM manages to screw it up. I think that they use CONC tags and don't split words, so you get a lot of run-together words with their GEDCOMS.

At any rate the CONC appears right in the Everything report. And now that I've type all of this, I'll go back and try changing the text to a null string in the Behold options to see what happens.

Close, but no cigar. When I change the text of the CONC tag to a null string, I still get one space that shouldn't be there. Maybe if you bring in CONT and CONC records with no space between the last record and the current record, but change the default text for CONT to a single space?

Seems like that would fix it.

This is a great program!