Yes the Privacy brackets stop the Master Source Comments appearing in the Gedcom UNLESS you override the Privacy settings.
You can continue negative towards Legacy 8 but if you're not encountering the bugs in Legacy 7.5 you probably won't encounter them in Legacy 8. The reality that fixing some bugs sometimes creates others has been happening since Legacy 2. It's what happens with computer programs - not just Legacy. The reality is that the bugs in Legacy 7.5 are not being addressed whereas the ones in Legacy 8 are. But of course you need to report the ones you find. We all use Legacy on different computers and in different ways so will sometimes encounter bugs that others haven't. I don't know how many times I've reported bugs that the programmers haven't been able to reproduce until further work has been done by Beta testers to identify the conditions that produce it. Cathy CE WOOD wrote: > > Agreed! They even asked me what bugs I have encountered. It is > unbelievable how many there are, and that they need me to let them > know what they are! > > Every time they fix one, it seems they create another. We don't know > what will get fixed and what will then not work as a result. So sad. > > > CE > > > From: [email protected] > > To: [email protected] > > Subject: RE: [LegacyUG] Source Comments in GEDCOM [WAS: Details text > showing up in Footnote citation] > > Date: Tue, 31 Mar 2015 11:59:39 +1100 > > > > Sorry, I am still on V7.5 > > This is just another reason I won’t upgrade to V8. > > > > Regards, > > > > Jennifer > > http://colston-wenck.com > > > > From: CE WOOD [mailto:[email protected]] > > Sent: Tuesday, 31 March 2015 11:28 AM > > To: [email protected] > > Subject: RE: [LegacyUG] Source Comments in GEDCOM [WAS: Details text > showing up in Footnote citation] > > > > So, do privacy brackets prevent the comments or text from appearing > in the GEDCOM? That seems to be the problem; the privacy brackets > don't work. > > > > The bug is that the parameters one sets are not recognized by the > Legacy program when it creates the GEDCOM. > > > > > > CE > > > > > > > From: [email protected] > > > To: [email protected] > > > Subject: RE: [LegacyUG] Source Comments in GEDCOM [WAS: Details > text showing up in Footnote citation] > > > Date: Tue, 31 Mar 2015 11:13:00 +1100 > > > > > > I always put privacy brackets [[ at the beginning of any text in > the Master Source text or comments field. > > > I sometimes use the whole of an email in text form for a source > and don't want the senders details or the whole of the text to appear > anywhere. > > > > > > Regards, > > > > > > Jennifer > > > http://colston-wenck.com > > > > > > From: Ward Walker [mailto:[email protected]] > > > Sent: Tuesday, 31 March 2015 6:43 AM > > > To: [email protected] > > > Subject: [LegacyUG] Source Comments in GEDCOM [WAS: Details text > showing up in Footnote citation] > > > > > > See below... > > > > > > From: Brian L. Lightfoot > > > Sent: Sunday, March 29, 2015 2:15 PM > > > To: [email protected] > > > Subject: RE: [LegacyUG] Details text showing up in Footnote citation. > > > > > > ... > > > Now for the really bad news that nobody has yet caught. I seems > this info on the Comment tab of a Master Source is always included on > a GEDCOM submission which kind of negates my idea of keeping it private. > > > > > > Brian in CA > > > ---------------------- > > > > > > Brian, I agree that there is bad news here, especially when the > target system for the GEDCOM is not well-behaved. I ran into this with > my TNG experimentation. I have just run some additional tests in order > to sort out what is happening. Results are below. In summary, I always > uncheck the export box that says ‘override source options’. Otherwise, > TNG bloats the source citations with unwanted text/comments from the > source Detail, and also displays citations that were unwanted. But > this is a compromise, because now Sourcewriter detail fields are > missing (at least for the templates that I tested) – a Legacy issue. > There are other TNG source-handling issues no matter which override > option you choose. > > > > > > Ward > > > > > > ******* Legacy Sources On Export to GEDCOM **************** > > > > > > (Export to 'Legacy' GEDCOM was selected for most of these tests.) > > > > > > If choose to override source options: > > > > > > - Sourcewriter Sources: > > > - Master source Text/Comments: Included in GEDCOM > > > - Detail Fields: Included > > > - Detail source Text/Comments: Included > > > > > > - Basic Sources: > > > - Master source Text/Comments: Included > > > - Detail Fields: Included > > > - Detail source Text/Comments: Included > > > > > > - The source is included in the GEDCOM even if the box 'Include > this citation on reports' was unchecked on the source detail panel. > (There is a _CIT No tag that Legacy probably uses on re-import, but a > non-Legacy target system would not.) > > > > > > > > > If choose not to override source options: > > > > > > - The Entire citation is missing if you do not check 'Include this > citation on reports' on the edit Detail panel. Otherwise... > > > > > > - Sourcewriter Sources: > > > - Master source Text/Comments: Included > > > - Detail Fields: NOT Included!! > > > - Detail source Text/Comments: Included only if had checked 'Add > this text/comments to the Source Citation on Reports. > > > > > > - Basic Sources: > > > - Master source Text/Comments: Included > > > - Detail Fields: Included only if had checked 'Add this Detail to > the Source Citation on Reports' > > > - Detail source Text/Comments: Included only if had checked 'Add > this text/comments to the Source Citation on Reports. > > > > > > > > > TNG Import: > > > > > > - Displays the source list name first, in the citation (i.e., the > name that is supposed to be for internal use, only!!) > > > - Displays no master text/comment text in the citation, or if > click on the source number. > > > - But DOES expands all the master source text/comments under the > citation in the PDF report!! > > > - Displays master source media, when click to drill down on the > source number. > > > - Displays available source detail fields in the citation, > although not when drill down on the source number. (Master info only.) > > > - Displays source detail text/comment data, if present, right in > the citation!! > > > - Displays no source detail media. (No media link.) > > > - Displays the Description field of the Detail Media file, in the > citation!! > > > > > > > > > > > > > > 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 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
