Ron, whether an issue has been "beaten to death" depends on the individual. As long as viewpoints are being exchanged on an issue that is list-appropriate, someone may be lurking in the wings who is benefitting from the discussion. Only the moderator can shut down a discussion, and usually only if the tone has become uncivil or is not list-appropriate. Just my two cents. Barton On Thu, Apr 02, 2015 at 04:24 AM, Ron Bernier wrote:
With all due respect, this horse has been beaten to death, buried, and totally decomposed. Can we please move on. I for one would really appreciate it if you and Jay could continue this discussion off list. The two of you are just arguing (discussing) the same point over and over again. If you feel in your mind that Legacy isn’t handling the issue the way that you want then to handle it, you have the ability to submit a suggestion. Respectfully, Ron Bernier Woonsocket, RI From: John Lisle [mailto:[email protected]] Sent: Thursday, April 02, 2015 12:15 AM To: [email protected] Subject: Re: [LegacyUG] Source Comments in GEDCOM [WAS: Details text showing up in Footnote citation] Jay, Please think again about what the attributes are in a default Child Status list: Twin and Stillborn. These are attributes that are true of an individual no matter what family they are part of. Even Adopted which has been in earlier lists is an attribute of a person. A person is either adopted or not adopted, whether or not they know it. :-) In a family, the adoption or non-adoption status of a child can be determined for each parent. This concept is supported by most large genealogy programs and all by use of level 2 _MREL and _FREL tags. These tags are not mentioned in Ged standard, but are valid extensions. FTM and Family Historian, as far as I could determine, do not have a standard personal attribute to express Twin status. Their users add an individual custom event or fact if they wish to add this attribute. By using valid extensions of the Gedcom standard, all other products that I have reviewed link the attributes that Legacy associates with Child Status as attributes of the individual, not the family. Legacy needs to do likewise. john. 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://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 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://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
