Please note that the comments from myself and from Connie were aimed at those who value certain aspects of the SourceWriter option, most notably subsequent citations and bibliography. The Basic option had been proposed earlier in the thread.
Unfortunately, in either case (using Basic or fudging the fields of SW), the result is not really a 'template', per se. One would still need to remember how to consistently construct the particular type of citation each time, rather than being prompted helpfully by appropriate fields of a form. Ward ----- Original Message ----- From: Paula Ryburn To: [email protected] Sent: Monday, August 22, 2011 11:18 AM Subject: Re: [LegacyUG] Custom templates for SourceWriter? Or use the Basic format - it's pretty generic. Might be easier to "get creative" with it. And no bugs like with the SourceWriter over-rides. Just a thought. --Paula in Texas Researching: Adair Baker Beasley Benson Betz Bigley Blagrave Burton Chapman Clement Clough Coppernoll Costine Daulton Dinwiddie Doody Ellis Exline Field Floran Floyd Gates Goodale Gordon Gump Hale Harbaugh Hind Hopkins Hughes Hurdle Jones Klein Koyle Laswell McDonald Misner Passwaters Pelton Roberts Roche Ryburn Short Singer Sullivan Weller Williams From: Ward Walker <[email protected]> To: [email protected] Sent: Fri, August 19, 2011 11:55:30 AM Subject: Re: [LegacyUG] Custom templates for SourceWriter? We discussed SourceWriter source overrides in March/April 2009. One discovery was that a Master source override resulted in a citation with no info from the source Detail. But a Detail source override would completely replace the text from the Master source override. I would guess that this is still the behavior. As Connie says, the SourceWriter, when used carefully and without overrides, at least provides you with the 'subsequent citation' capability. By 'carefully', I mean that you have to be aware of which fields (Master and Detail) will disappear in the subsequent citation and which will always appear. Several bug reports were logged in this area in 2008/2009. Using the fields of an existing SourceWriter template creatively in order to effectively create a 'custom' template is probably still the reasonable option. Avoid templates that introduce hard-coded punctuation and connecting words between fields that you wish to ignore or to use for unexpected purposes. Ward 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
