Hmmm....I'm supposing that such shared events also will fail to import into Ancestry.com, both the paid subscriber pages and the free pages at RootsWeb. Not good.
Brian in CA -----Original Message----- From: Ward Walker [mailto:[email protected]] Sent: Thursday, August 01, 2013 5:09 PM To: [email protected] Subject: Re: [LegacyUG] ? about the new shared even feature It is a common problem, but I think that it is one that Millennia should seriously consider providing an optional workaround. Information will be lost. Legacy should include an option on export to unlink the shared events into separate, standard events in the GEDCOM. By not doing so, it forces Legacy users to consider avoiding this new feature if we ever expect to share data with relatives who do not use Legacy. I see this as similar to the problem with SourceWriter sources. Legacy should have an option to reformat the source citation so that it makes sense when converted into a Basic source in the GEDCOM. In general, proprietary features are great, as long as there is always an optional way to mash them into the current, inadequate GEDCOM standard. Ward -----Original Message----- From: Brian/Support Sent: Thursday, August 01, 2013 5:56 PM To: [email protected] Subject: Re: [LegacyUG] ? about the new shared even feature Legacy will export the information to share the event but, as with any non-standard GEDCOM feature, we use custom GEDCOM tags for that data. Legacy 8 will re-import the shared events correctly but programs that do not support shared events and possibly even those that do but which do not correctly interpret the custom tags from Legacy will not know how to import that shared event data. This is a common problem when programs have features which are not supported by the GEDCOM standards. Brian Customer Support Millennia Corporation [email protected] http://www.LegacyFamilyTree.com -- On 01/08/2013 1:56 PM, Virginia Blakelock wrote: > On Thu, Aug 1, 2013 at 12:29 PM, Brian/Support > <[email protected]> wrote: >> Then there are all the census events as well to convert family > group census entries to shared events.< > > And - as with shared events in other programs - the shared events are > not included (will not transfer) via GEDCOM? > > Virginia 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 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
