Ward, They have announced publicly v8 to be released soon so they will not be working on new features until after they get that version released.
Anyone can make a suggestion/proposal from the Legacy Home page under Support. And contrary to some I have found them to be very responsive to users suggestions. Larry Lee [email protected] On Fri, Jun 21, 2013 at 3:22 PM, Ward Walker <[email protected]> wrote: > Larry, > > You say that as if your are an insider who knows what is already in V8. > Are you? > > This issue has come up on the list several times over the last few years. > I was hoping that the V8 developers had already given it some > consideration. But if you have some pull, please go for it. It is the type > of feature that can be added in a minor release, too. > > Ward > > *From:* Larry Lee <[email protected]> > *Sent:* Friday, June 21, 2013 4:40 PM > *To:* [email protected] > *Subject:* Re: [LegacyUG] Source Template Conversion Tool > > Ward etal, > > I will propose a new feature regarding SourceWriter and GEDCOM but due to > the current v8 schedule it will have to wait till later as it will require > too much programming at this time. > > > > Larry Lee > [email protected] > > > > On Fri, Jun 21, 2013 at 9:17 AM, Ward Walker <[email protected]> wrote: > >> GEDCOM is the source of the problem, but I have long advocated that an >> optional workaround could be provided in Legacy. In fact, this is near the >> top of my list of things I would like to see in a major new release. >> >> Since Legacy already knows how to format (for reports) the various master >> and detail fields of a SW source, it seems to me that the programming >> effort would not be overwhelming to similarly format those fields into a >> Basic-style source in the GEDCOM export. Yes, this would flatten out the >> sources such that there is no effective hierarchy of master and detail, but >> at least such sources would be readable in the system that imports the >> GEDCOM. Right now, they appear rather scrambled (depending on the template >> type). >> >> Ward >> >> *From:* Walt Quering <[email protected]> >> *Sent:* Thursday, June 20, 2013 9:43 PM >> *To:* [email protected] >> *Subject:* Re: [LegacyUG] Source Template Conversion Tool >> >> I may misunderstand the issue, but, from what I've seen, the problem is >> a GEDCOM problem, not a Legacy problem. The aging GEDCOM model has only so >> many fields for citations and dumps data from unrecognized fields in the >> software of origin into its note fields. Back when Legacy was the only >> software with detailed templates for sources, this impacted only Legacy, >> but other programs now also have detailed templates, so it impacts them as >> well. I've seen similar situations in other arenas, and, while the >> problems are not insurmountable, neither are they inexpensive. They also >> require that all parties involved cooperate. >> >> >> On Thu, Jun 20, 2013 at 6:04 PM, Larry Lee <[email protected]> wrote: >> >>> CE, >>> >>> I know very little about the use of GEDCOM, it either works for me or it >>> doesn't. Granted GEDCOM development is always behind the times. I >>> understand backward compatibility is always a challenge. >>> >>> Even so, since Millennia created Sourcewriter shouldn't they be >>> responsible to create a workaround algorithm to export the appropriate >>> fields into current GEDCOM fields? Even if most of the information might >>> wind up in a notes field at least the information would available on the >>> import end, although maybe not as useful as if it had proper GEDCOM fields. >>> >>> Larry Lee >>> [email protected] >>> >>> >>> >>> On Thu, Jun 20, 2013 at 5:45 PM, CE WOOD <[email protected]> wrote: >>> >>>> Unfortunately for Source Writer devotees, it is not a Legacy problem, >>>> it is that gedcom standards are out of date. Then again, perhaps a Legacy >>>> gedcom could be created that would accommodate Source Writer templates, but >>>> only for import back into Legacy. That might be useful for cleaning up a >>>> Legacy file, but still would not help if you were trying to send someone a >>>> gedcom to import into their genealogy program. >>>> >>>> >>>> CE >>>> >>>> ------------------------------ >>>> From: [email protected] >>>> To: [email protected] >>>> Subject: Re: [LegacyUG] Source Template Conversion Tool >>>> Date: Fri, 21 Jun 2013 09:35:26 +1000 >>>> >>>> I hope Legacy 8 will fix all these problems. >>>> >>>> John >>>> >>>> *From:* CE WOOD <[email protected]> >>>> *Sent:* Friday, June 21, 2013 5:09 AM >>>> *To:* [email protected] >>>> *Subject:* RE: [LegacyUG] Source Template Conversion Tool >>>> >>>> Before you convert, I advise you to read the archives here to learn >>>> about the many problems associated with using Source Writer templates. Many >>>> people have converted all their sources back to Basic because of the >>>> problems, not the least of which is the fact that gedcoms do not recognize >>>> Source Writer templates, and your sources will become Basic, but not also >>>> the way you would want them to read. >>>> >>>> >>>> CE >>>> >>>> ------------------------------ >>>> From: [email protected] >>>> To: [email protected] >>>> Subject: [LegacyUG] Source Template Conversion Tool >>>> Date: Thu, 20 Jun 2013 11:38:44 -0500 >>>> >>>> Hello: >>>> >>>> In an effort to clean up my sources, I would like to convert my >>>> existing basic source citations to the new Source Writer templates, but am >>>> unable to find the "Source Template Conversion Tool". My manual for 7.0 >>>> indicates that it is reached from the Master Source List by clicking the >>>> Options button but it is not available as a choice on my program. I have >>>> the latest build, 7.5.0.219. Can anyone advise me please? Thanks kindly. >>>> >>>> Christine >>>> >>> >> >> 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 > 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
