Jump to content


Witterly

Member Since 15 Oct 2017
Offline Last Active Dec 29 2020 01:23 AM
-----

Posts I've Made

In Topic: After importing a GEDCOM into RM7 there are erroneous spaces added in the mid...

15 December 2020 - 05:22 PM

You have gotten caught in this little misunderstanding. I doubt that the problem will ever be completely resolved. To tell you the truth, the problem presently seems to me to be less severe than it did many years ago.
Jerry


If that’s true, that’s really unfortunate. I’ve long given up on the idea of templates sources transferring from one program to another. The fact that free text non formatted citations can’t even be imported correctly without manually editing the GEDCOM file is annoying.

While I appreciate that the problem may not be as severe as it used to be, the citations are still unacceptable in any professional setting.

Besides fixing this bug for FTM, I think either RM needs to treat all GEDCOM imports the same or alternatively post a guide explaining how they are compensating for each program. I mean, it’s great that RM7 offers the ability for a direct import from several programs (including FTM 2014), but then having a GEDCOM import that is inconsistent is really confusing.

In Topic: After importing a GEDCOM into RM7 there are erroneous spaces added in the mid...

15 December 2020 - 02:53 PM

Update:

 

Ok I think I figured out what is going on.

 

At one point FTM appears to have been using the CONC tag incorrectly on GEDCOM export. Now they seem to have fixed that problem. However RM7 is compensating by putting in an extra space since my GEDCOM export was from FTM.

 

After removing references to Family Tree Maker from the header of my GEDCOM (below) the problem seems to have been solved.

 

If RM is treating GEDCOM files differently based on the program of export, this is a bit frustrating. Is there a list or resource that compares how RM handles GEDCOMs from the major software programs?

0 HEAD
1 SOUR 0
1 DATE 15 DEC 2020
1 CHAR UTF-8
1 SUBM @SUBM@
1 GEDC
2 VERS 5.5.1
2 FORM LINEAGE-LINKED
0 @SUBM@ SUBM
1 NAME Not Given
0 @I1@ INDI
1 NAME William /Smith/
1 SEX M
1 BIRT
2 DATE 1864
2 PLAC Syracuse, Onondaga, New York, USA
3 MAP
4 LATI N43.048119
4 LONG W76.147408
1 DEAT
2 DATE 1930
2 PLAC Syracuse, Onondaga, New York, USA
3 MAP
4 LATI N43.048119
4 LONG W76.147408
2 SOUR @S1@
3 PAGE PDF pg. 1–3; Last Will and Testament (1930)
3 NOTE @N1@
1 FAMC @F1@
0 @I3@ INDI
1 NAME Rebecca /Adams/
1 SEX F
1 FAMS @F1@
0 @I2@ INDI
1 NAME Grant /Smith/
1 SEX M
1 FAMS @F1@
0 @F1@ FAM
1 HUSB @I2@
1 WIFE @I3@
1 CHIL @I1@
2 _FREL Natural
2 _MREL Natural
0 @S1@ SOUR
1 TITL Onondaga County, New York, probate case files, no. 283, William Smit
2 CONC h (1930); Onondaga County Surrogate's Court, Syracuse
0 @N1@ NOTE
1 CONC # Abstract
1 CONT
1 CONT 1937 - 473
1 CONT
1 CONT I, William Smith of the City of Syracuse, N.Y., do make, publish and d
1 CONC eclare this to be my last Will and Testament as follows:
1 CONT
1 CONT 1: ...my debts and funeral expenses be paid...
0 TRLR


In Topic: After importing a GEDCOM into RM7 there are erroneous spaces added in the mid...

15 December 2020 - 11:43 AM

Below is relevant:

Windows - Lines end with both a <CR> followed by a <LF> character e.g. \r\n
Macintosh (Mac OSX) - Lines end with only a <LF> character

 

Load the FTM ged in a text editor and save for Windows rather than MacOS. An Editor such as EditPad Lite will do the job - Convert > Line Break Style > To Windows (CR LF). There are several text editors that have this functionality (BBEdit on your Mac comes to mind).

 

Thanks for the suggestion. I downloaded a trial of BBEdit (looks like a great program by the way), converted all line breaks to CR LF, and re-attempted. It does not seem to have fixed the problem.