I imagine, like most modern genealogy programs, TMG included special tags to output data for items that were not supported by the GEDCOM specification. The spec allowed for these special outputs by letting programs invent custom output tags preceded by an underscore "_" that were unique to their program features. I do not know what custom tags a TMG GEDCOM contained nor whether Legacy tries to interpret those custom tags when importing where we support the same feature. The GEDCOM spec allows importing programs to ignore any custom tags encountered but Legacy does try to accept custom tags from competitor's GEDCOMs if we can figure out a compatible feature in Legacy where it would apply.
Hopefully the direct import will include all the mutually supported items and will transfer a more complete set of data. Items like modified dates (date last edited), date added to file etc (if TMG has that info in the file) may transfer without change. When using a GEDCOM all the people's added dates are the date of the import and last edited dates are also set to the import date. I do not know the structure of a TMG file since I never used the program nor am I aware of what the programmer working on the import is trying to include. On 16/12/2014 5:41 PM, Nancy wrote: > I already imported using a Gedcom file. Will this new import import things > that the gedcom did not from TMG? > > Sent from my iPad > >> On Dec 16, 2014, at 4:38 PM, Brian/Support <[email protected]> >> wrote: >> >> We are working on a direct import from TMG but we never promised that we >> would import "everything". We cannot import things for which Legacy has >> no equivalent. The direct import will import from a TMG file without the >> use of a GEDCOM but it can only import things that Legacy can support. >> >> Brian >> Customer Support >> Millennia Corporation >> [email protected] >> http://www.LegacyFamilyTree.com >> >> >>> On 16/12/2014 4:18 PM, [email protected] wrote: >>> snip> >>> Several months ago the rumors were that Legacy was being retooled to >>> directly import everything directly from the TMG structure, but I am >>> wondering >>> how many years that will take. TMG has taken 25 years to become the >>> program >>> that it is closing down as. Is that how long it will take Legacy to get >>> caught up??? >>> >>> PJ >> >> >> >> 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 >> >> > > > > 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 > > > . > 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
