Brian, Basically sources are not reproduced correctly in other software (ie not Legacy) because of incompatibility between the GEDCOM and the software, It mainly affects those of us who use other software for webpages. I use SW and put up with the problem.
Legacy is not on its own FTM, and my be other, software have the same problem. Ron Ferguson http://www.fergys.co.uk/ -----Original Message----- From: Brian L. Lightfoot Sent: Thursday, April 18, 2013 8:52 PM To: LegacyUserGroup@LegacyUsers.com Subject: RE: [LegacyUG] Source Writer I'd be curious to know exactly what problems you and others are experiencing in the creation of a GEDCOM from SW. Or am I misunderstanding what you are saying? My understanding of what Sherry is cautioning about is that if you then take that same GEDCOM and re-import it back into Legacy, the SW format is lost and everything is converted to the Basic format. That is understandable but I don't know why or when anyone would want to do that. As Sherry said, a GEDCOM is not your first choice for creating a Legacy backup but in a case of last resort, it would still have all the data there. I'm getting the impression that some people are staying away from the SW format because they think it somehow screws up a GEDCOM report. There is only one issue that I have noticed in the creation of my own GEDCOM using SW sources. For some reason, the REPO (Repository) element remains even though the GEDCOM template I'm using has excluded the REPO element. I'm not sure if this is the fault of GEDCOM or if the Legacy customization menu for GEDCOMs is slightly defective. Not really a big issue either way. Brian in California -----Original Message----- From: Ron Ferguson [mailto:ronfergy....@tiscali.co.uk] Sent: Thursday, April 18, 2013 12:01 PM To: LegacyUserGroup@LegacyUsers.com Subject: Re: [LegacyUG] Source Writer Sherry, Whilst what you say is accurate, many of us do export using a GEDCOM for publication of our websites. I appreciate that this is a GEDCOM problem rather than Legacy's. Ron Ferguson http://www.fergys.co.uk/ -----Original Message----- From: Sherry/Support Sent: Thursday, April 18, 2013 7:46 PM To: LegacyUserGroup@LegacyUsers.com Subject: Re: [LegacyUG] Source Writer Everything you enter should be included in the gedcom. It's just that when you import the gedcom into Legacy, the sources will show in the "Basic" format rather than SourceWriter format. But, unless you're going back to an earlier version of Legacy which doesn't support SourceWriter anyway, you wouldn't use a gedcom to move a file from Legacy to Legacy. You'd do a backup and restore (File > Backup Family File). The gedcom should only be used for moving data into a different program or uploading to a website. Sincerely, Sherry Technical Support Legacy Family Tree On Thu, Apr 18, 2013 at 11:12 AM, Barbara <brc...@yahoo.com> wrote: > Here is my dilemma: I would like to use Source Writer for my sourcing > in Legacy to be sure that I've sourced according to standards. But > now I've heard that the data produced using Source Writer doesn't > always translate correctly into Gedcom. What do other people do? > Barbara 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
