I never realized that the sample data was pulled from an editable text file. But I have chosen to locate my entire data folders in a non-default location that is different than the C:\ drive which means I never have the necessity to look back at the Legacy created "_AppData" folder. Besides, for what reason would anyone ever want to edit the sample data file?
I know how the sample sentence option works with Male/Female/Marriage options but you have to admit, some of those choices for sample data sentences are strange and certainly worth a chuckle. Most are along lines of what could be a reasonable, similar to real life type example such as "[Desc] Employment / as a laborer", but then there are the others that make me think that the programmers had a fun time with some of these such as "[Desc] Emigration / in the middle of the night" or even "[Desc] Marriage Settlement / in the afternoon". Oh well, it was good for a few minutes of laughs. Brian in California -----Original Message----- From: Brian/Support [mailto:[email protected]] Sent: Friday, December 04, 2015 2:32 PM To: [email protected] Subject: Re: [LegacyUG] Sample Data in Event Definition Sentences Those sample sentence displays have been in Legacy 8 since it was issued. Observant aren't you. There are three options for the "sample sentence". Male Individual, Female Individual and Marriage Event. Your John and John example of a marriage license will happen if you have any marriage event linked to an individual (spouse data like spouse name will simply repeat the name of the individual since an individual event does not know what spouse name to use). The event sentence for a marriage license is written for a couple and includes the [WifeFirstname] field. "[HusbFirstName] and [WifeFirstName] obtained a marriage licence [Desc] [onDate] [inPlace]." If you do not like the sample sentences they are in files which you can edit or edit the event sentence itself. The sample sentence display use data from the event by translating those fields in square brackets at the beginning of the sample sentence files. Look for the _AppData\Misc\SampleSentenceData folder for the samples in each language. There are some instructions included in the files for how to edit the event lines. Brian Customer Support Millennia Corporation [email protected] http://www.LegacyFamilyTree.com On 04/12/2015 2:12 PM, Brian L. Lightfoot wrote: > Here is something that I’ve never noticed before nor have I seen it > mentioned in this forum. It appears to be what I’d call some small “Easter > Eggs” put in the program code by programmers usually as hidden things that > can happen or some humor that is usually seen or known only by them. It > involves the “sample data” for event definition sentences You will see such > sample data when viewing the Edit Event Definition window and the sample > data is used to create what a possible sentence would look like. > > The easiest way to see all of these in one place is to click View / Master > Lists / Event Definition. Within that long list of Events that will appear > scroll down to any of the following events and just double click that event. > That will open up the Add / Edit Event Definition window. Down at the bottom > is a sentence that will be created based upon sample data that apparently is > hard coded into the program. Not all events have sample data and any custom > events added by the user will not have sample data. You will also note that > the sample.fdb supplied by Millenia contains different sample data than a > normal user created database. > > Here are a few that I found that contain some weird / humorous data. There > probably are more but this is just a quick look with my comments in > parentheses: > > > Alt.Birth = He has conflicting birth information of a suspicious nature, 28 > May 1904 and Seattle, King, Washington, United States.¹ These are the event > notes. (This sentence was taken from the sample.fdb. The real database > created for the user does not contain "of a suspicious nature".) > > Alt.Burial = He has conflicting burial information of that is interesting, > 28 May 1904 and Seattle, King, Washington, United States.¹ These are the > event notes. (this is interesting...???) > > Alt.Christening = He has conflicting christening information of that is > different, 28 May 1904 and Seattle, King, Washington, United States.¹ These > are the event notes. (this is interesting...???) > > Alt.Death = He has conflicting death information of that is wrong, 28 May > 1904 and Seattle, King, Washington, United States.¹ These are the event > notes. (This sentence was taken from the sample.fdb. The real database > created for the user does not contain "of that is wrong".) > > Alt.Marriage = He has conflicting marriage information of that is > surprising, 28 May 1904 and Seattle, King, Washington, United States.¹ These > are the event notes. (This sentence was taken from the sample.fdb. The real > database created for the user does not contain "of that is surprising".) > > Engagement = He was engaged in the parking lot on 28 May 1904 in Seattle, > King, Washington, United States.¹ These are the event notes. > (Really...engaged in the parking lot ???) > > Marriage Contract = He signed a marriage contract unwillingly on 28 May 1904 > in Seattle, King, Washington, United States.¹ These are the event notes. > (Really...unwillingly ???) > > > And for the most surprising one of all which comes only from the sample.fdb. > Remember, this is a genealogical program that does not support same sex > marriages...... > > Marriage License = John and John obtained a marriage license together on 28 > May 1904 in Seattle, King, Washington, United States.¹ These are the event > notes. (Wow, John and John !!!) > > > > Brian in California > 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
