[converted to Plain Text format] Dave,
Sorry my first test was on the next-to-latest build. I hope you saw my 'Update' e-mail, which explains that the latest build does export the detail. The target system might 'hide' such detail, as Legacy does by not automatically turning on the appropriate checkbox during re-import. (So I was wrong in stating that "the test need go no further than the GEDCOM file".) I introduced Problem 2 because I assumed that it was just as much a deal-breaker as Problem 1, in your decision whether to avoid SourceWriter sources. Ward ----- Original Message ----- From: Dave Keeney To: [email protected] Sent: Friday, May 28, 2010 4:46 PM Subject: Re: [LegacyUG] Incomplete Export of Source Details Sorry if I was overly confusing. The issue I was talking about was Problem 1 below. If that's a Legacy Bug (I sure thought it was/is) has it been noted by Legacy? In the past I've submitted bugs and they've been noted but I never know if or when they'll be addressed. That's the only thing I was trying to get at when I originally asked if there was any progress/update on the issue. On Fri, May 28, 2010 at 8:42 AM, Ward Walker <[email protected]> wrote: Ron, For both problems (source details missing, and source fields scrambled), the test need go no further than the GEDCOM file produced by Legacy. The first problem is entirely a Legacy bug. The root cause of the second problem is the GEDCOM standard, although Legacy might be able to mitigate the effect somewhat during the export. ... Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
