The reason I asked is because Darrin advised me against using GEDCOM 5.5.1.
Perhaps the problem some experience comes from not using the Legacy GEDCOM, thinking it is for use with Legacy only. CE Date: Thu, 26 Mar 2015 00:16:18 -0400 To: legacyusergroup@LegacyUsers.com From: leg...@johnlisle.com Subject: RE: [LegacyUG] Issue with Gedcom Export of Child Status CE, The issue is not which version of Gedcom you use. However, when I export a Gedcom for import to TNG, I always use the Legacy style export as this exports all of the information and so I have only a small information lossage. This Child Status feature is one of the most important pieces that is lost. john. At 09:56 PM 3/25/2015, CE WOOD wrote: What GEDCOM version do you use? CE From: dwquig...@cox.net To: legacyusergroup@LegacyUsers.com Subject: RE: [LegacyUG] Issue with Gedcom Export of Child Status Date: Wed, 25 Mar 2015 18:05:02 -0700 Hmmm. On my TNG website, the "child relationship" seems to show properly as the "Relationship" under a parent on a child's Personal Information page Donald Quigley Escondido, CA Quigley Doyle Family Tree http://www.donquigley.net -----Original Message----- From: John B. Lisle [ mailto:leg...@johnlisle.com] Sent: Wednesday, March 25, 2015 1:49 PM To: legacyusergroup@LegacyUsers.com Subject: [LegacyUG] Issue with Gedcom Export of Child Status Hi, A user recently reported to me that Child Status attributes, such as Stillborn, Twin, Adopted, etc., were not being imported into his TNG web site from a Legacy Gedcom file. Analysis shows that Legacy is exporting the Child Status in Gedcom, and can import those Legacy Gedcoms properly back into in Legacy. But the TNG web publishing application that many Legacy users use does not import the tag that Legacy uses to report Child Status. (Legacy currently exports it as an attribute of the child in the family structure.) --> IE, none of your Child Status attributes have EVER been imported into TNG. Maybe this OK with you? Maybe you have never noticed? Further analysis shows that Legacy's approach to Child Status seems to be unique among the major genealogy products and, although the best (as far as I am concerned) actually, may not be optimal. In reality, there is no consistency in how various products implement Child Status attributes, if they handle them at all. Consequently, the TNG developer has less incentive to provide the fix for this mis-match with Legacy. As this has been a problem for 10+ years with, supposedly, only myself and one other user expressing concern over this to Legacy, I would like to know if other users have seen this and would like to see this resolved. Getting something resolved - and quickly - will require having many folks second that this is an issue for them. --> Let me emphasize that this is not a Legacy bug. Legacy itself works fine. This is a mis-match in the interface between two products. Also, do you know of any other programs where the current Child Status implementation is causing a problem from Legacy Gedcoms? Thanks for listening, john. nashua, new hampshire 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://support.legacyfamilytree.com 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
