David, the problem revolves around the way FTM
handles the CONC
The <cr><lf> 0D 0A
are the standard line terminators that end every line in a plain text file such as GEDCOM
They are NOT
the real cause of the problem as the CONC
atenation algorithm discards them.
Previous versions of FTM
violated the CONC
rules and split lines on word boundaries.
It seems that FH
recognises FTM GEDCOM
files and automatically deals with the CONC
lines assuming the lines are split on word boundaries and inhibits the Check for word-wrapping errors
ensures a space character appears in the CONC
atenated text where the line is split, which is exactly as you describe.
However, the latest FTM 2017
as reported in Import Gedcom from a Mac? (15427)
today is now "Exporting concatenation tags correctly
". The lines are no longer split on word boundaries, but within words, which is compliant with the GEDCOM
rules. That is exactly as you have illustrated. BUT FH
does not know that yet and is still inserting a space at each line split.FOR THE THIRD TIME OF ASKING
Please simply edit the first few lines of the GEDCOM
file to remove reference to FTM
as illustrated previously.
That will force the Check for word-wrapping errors
dialogue and allow the correct CONC
atenation mode to be chosen.
I am in discussion with Calico Pie
about this issue, which has arisen due to FTM 2017
correcting its CONC
The workaround is to disguise the FTM
origin, and I will amend the Knowledge Base > Import from Family Tree Maker (FTM)