Ward, This is an excellent idea which I hope would be relatively easy to implement. I have no desire to abandon Legacy, but there is a competitor I'd like to use for some purposes. I'm essentially "trapped" in Legacy because I have many sources written in SourceWriter and they are completely garbled when exported to GEDCOM. For that matter, they are garbled if reimported from GEDCOM into Legacy.
Now that this issue is getting publicity on a rather widely read blog, I hope it will be higher on the "to fix" list. Connie --- On Thu, 2/3/11, Ward Walker <wnkwal...@rogers.com> wrote: > The underlying problem is the GEDCOM > format. However, I think that the > Legacy programmers could devise a workaround, if > sufficiently motivated by > customer demand. Here is one idea, which should work as a > user option for > 1-way transfers, at least. It wouldn't be very suitable for > back and forth > transfers. Instead of simply throwing all the master source > fields together > in one GEDCOM field, and all the detail source fields > together in another > GEDCOM field, flatten out the hierarchy. Each citation > would essentially be > one big detail field in the GEDCOM containing the full > citation exactly as > if formatted for an internal Legacy report. > > There are probably other ideas. I wonder what Legacy's > competitors are doing > with the same issue? > > Ward > 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 To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
