Jim, My 'general' notes are filled with these 'spacation' errors as you call them.
Do you have any idea on a good way to resolve them? I know spell check will catch them, but man, with as large of a file as I have, that would literally take me months if I worked 8 hours a day. Maybe a spell checker that automatically tried to repair by removing the space before or after to see if that fixed it. I know that might add a few problems, but for the few dozen it may add, it would have fixed a thousand. Just reaching out as this is the first mention I have seen of the 'spacation' problem in many years. Thanks in advance for any help. Jay On Thu, Dec 12, 2013 at 12:00 AM, <legacy-requ...@rootsweb.com> wrote: > > > Today's Topics: > > 1. Re: Legacy vs. FTM (Jim Winfrey) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 11 Dec 2013 07:34:24 -0500 > From: Jim Winfrey <jimwinf...@gmail.com> > Subject: Re: [LEGACY] Legacy vs. FTM > To: leg...@rootsweb.com > Message-ID: > <CAP-= > f_1mpyaf6xoica-tunpp+nsh5lzbpkbanjmn+h7mrfz...@mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > Starting with FTM2011, the integration with Legacy improved greatly. If I > export an FTM20xx file as a FTM16, Legacy imports the file with fairly > little word needed. FTM now reads imports Legacy from the .db file with no > gedcom involved. > > All that positive stuff aside, multiple transfers of data between any two > programs results in what I call spacation errors - spaces randomly inserted > in citations and notes (never in primary facts or places). The cause for > this is the different line length each program writes into their gedcom > export and our inability to set this parameter. > > I now use FTM2014 as a browser and enter all the data into Legacy. This > works best for me. > > Jim > > > On Tue, Dec 10, 2013 at 9:44 PM, DanBCooley <dang...@gmail.com> wrote: > > > Debbie and Ward, > > I'll quickly relate to you my experience with cross-program GEDCOMs. > > Prior to switching to /Legacy/ I had /Generations/, a program that had > > numerous problems, the worst of which was its implementation of GEDCOM. > > Things got so bad with Generations they tossed in the towel and > > disappeared. What a dilemma. I switched to Legacy but I had so much > > entered into Generations that was lost in the GEDCOM transfer that > > re-typing was out of the question. So! I learned GEDCOM and laboriously > > edited the Generations GEDCOM almost line by line to fit Legacy. It took > > me almost five months. After changing a short block of code I would test > > it in Legacy, note error messages and go back to try again. What a > > nightmare, and, I'm still not sure I got everything from Generations. > > > > The original intent of GEDCOM (started with PAF I think) was lost many > > years ago. Each new genealogy program company thinks IT has the correct > > way to implement it. Well, fine for them but not so good for the user. > > So, my point is: Do not trust a GEDCOM generated by FTM or any other > > genealogy program to transfer everything intact to Legacy. Stick with > > one original data-entry program and never change (easy to say). From > > what you've said below that would apply to Legacy 6, 7, and 8 too. > > > > Dan Cooley > > Las Vegas, Nevada > > > > > > > Debbie, > > > > > > I have had problems with the import of GEDCOMs created by FTM. You > might > > not > > > have problems if you are the user of both systems and adjust your usage > > > accordingly. Last March I logged an enhancement request for Legacy to > > handle > > > certain import issues in a more helpful way. I don't know if any of my > > > requests have since been implemented. I haven't tried Legacy 8 yet. The > > area > > > to watch, in this case, is notes attached to vital events (birth, > death, > > > marriage, etc.). FTM used GEDCOM in a way that Legacy did not, so the > > import > > > was not good. > > > > > > Marriage notes (specifically, text on the MARR tag line in the GEDCOM) > > were > > > discarded, if short. If long, the first parts were discarded but the > > > continuation portions were imported into Legacy marriage notes. > > > > > > Note text on the BIRT/DEAT/BURI tag lines were imported to the > > appropriate > > > Legacy notes. No problem for short notes. However, any continuation > lines > > > (CONC tag) for longer notes were considered as invalid GEDCOM. > Depending > > on > > > the import option you select, these were either discarded or dumped > into > > > General Notes as unrecognized entries. > > > > > > So, I guess the point is to experiment with FTM-to-Legacy via GEDCOM > and > > > carefully examine the data. > > > > > > Regarding Legacy-to-FTM, you probably already know about the issue with > > > source citations. If you had used the SourceWriter feature in Legacy, > > then > > > these source citations are transformed during the export to look like > > > (GEDCOM-compatible) 'Basic' style sources. Information is not exactly > > lost, > > > but the wording can appear rather scrambled at the other end (FTM), > > > depending on which SourceWriter templates were used. Stick to Basic > style > > > sources if you need to go back and forth (or to Ancestry, for that > > matter). > > > > > > Ward > > > > > > -----Original Message----- > > > From: Growing A Tree > > > Sent: Monday, December 09, 2013 12:53 PM > > > To: Legacy Rootsweb > > > Subject: [LEGACY] Legacy vs. FTM > > > > > > I love Legacy and have also used FTM. I do like that FTM let's me > easily > > > upload the tree back-and-forth from Ancestry.com. I find that it's > > easier > > > to do some things online, and other things on my desktop app -- so I > flip > > > back and forth at times. In my experience, Legacy is more robust in a > > > variety of ways. > > > > > > I suppose I am wondering a few things.... > > > > > > 1. When trees are exported from Legacy to FTM (or vice-versa) is there > > any > > > data loss?? If so, what? > > > > > > 2. Can Legacy upload/download from Ancestry.com? > > > > > > 3. And (LOL) are there any other questions I should be asking as I > > compare > > > the two systems? > > > > > > > > > many thanks! > > > Debbie > > > > > > ------------------------------- > > > To unsubscribe from the list, please send an email to > > > legacy-requ...@rootsweb.com with the word 'unsubscribe' without the > > quotes > > > in the subject and the body of the message > > > > > > > > > ------------------------------- > > > To unsubscribe from the list, please send an email to > > legacy-requ...@rootsweb.com with the word 'unsubscribe' without the > > quotes in the subject and the body of the message > > > > > > > > > > ------------------------------- > > To unsubscribe from the list, please send an email to > > legacy-requ...@rootsweb.com with the word 'unsubscribe' without the > > quotes in the subject and the body of the message > > > > > ------------------------------ > > To contact the LEGACY list administrator, send an email to > legacy-ad...@rootsweb.com. > > To post a message to the LEGACY mailing list, send an email to > leg...@rootsweb.com. > > __________________________________________________________ > To unsubscribe from the list, please send an email to > legacy-requ...@rootsweb.com > with the word "unsubscribe" without the quotes in the subject and the body > of the > email with no additional text. > > > End of LEGACY Digest, Vol 8, Issue 65 > ************************************* > Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
