Mike, I see your point. Although, I'll have to take your word for it that the standardization process is truly dead for this standard. I seem to recall someone questioning that when we last discussed this problem.
I wonder if there could be a workaround, perhaps as an option, that would be akin to extreme splitting. Legacy could craft a well-formatted citation as a single block of text consisting of all of the master and detail data. Essentially, once exported, there would be no 1-to-many relationship between master and detail records -- just many enhanced 'master' sources with no 'detail' field to point to. The file size would go up. This option wouldn't work for back and forth exchanges, but at least the target system would see the proper citations in one-way exchanges. Ward ----- Original Message ----- From: "Mike Fry" <[email protected]> To: <[email protected]> Sent: Friday, May 28, 2010 12:59 PM Subject: Re: [LegacyUG] Incomplete Export of Source Details On 2010/05/28 18:51, Ward Walker wrote: > I just updated my (Deluxe) build from 7.4.0.30 to 7.4.0.39 and got a > different result. (Somehow I missed or overlooked the notice of a newer > build.) The detail information is once again present in the GEDCOM file > and likewise in the Source Detail fields in the re-imported family file. > This is good! However, in the Legacy family file, the checkbox to "Add > this detail to the source citation on reports" is not checked. I can't > recall whether this was the behavior during last year's tests. It looks > like a Legacy import bug. Other systems might behave differently on > import, as I don't think there is anything in the GEDCOM that could > influence this import decision. > If one manually checks the above box, then, as before, all the > information is present in the citation, but it is badly formatted. > Non-Legacy products would surely do the same, given the same GEDCOM file. > An example of the formatting problem: The export of a master source > includes the string "... e-mail<; ...", while the detail source field > contains the string "... 27 Dec 2009> ...". The resulting output > citation places these two strings in different locations! You are aware, of course, that this exporting of SourceWriter stuff will only work:- a) Once there is a new GEDCOM standard b) EVERY Genealogy program has equal support for the ESM 'standard' The answers to these questions are :- a) Never because GEDCOM as a standard is dead. It will not evolve. b) Highly unlikely. -- Regards, Mike Fry Johannesburg 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
