Dear all, let me take the note from Max van Dam and the GEDCOM question someone noted. In addition to the 3 described abbreviations GEDCOM allows: 2 DATE FROM Date 2 DATE TO Date 2 DATE FROM Date1 TO Date2 2 DATE BET Date1 AND Date2 2 DATE CAL Date 2 DATE EST Date and DATE may be: YYYY for the year MMM YYYY for month (3 letters) and year DD MMM YYYY for day month year This is for the ged-file, not necessarily for the BK input. BK may convert some input strings to correct GEDCOM syntax during GEDCOM export. CA, CIR, BET 1820-1825 or others are not allowed in ged-files and may be lost during transfer to another PC with a different genealogy program. Only in case the importing program has sufficient features build in, the dates will be taken correctly. best regards Diedrich (Hesmer) http://ofb.hesmer.name/gedcom Am 27.03.15 um 10:03 schrieb Max van Dam via: > Dear John Gilliver, > > I have a standard approach for using ABT, BEF, AFT. > > BEF > > I use BEF very often when I know the parents from somebody without any dates > for this person. > If somebody married in 1840 and the person is 20 years old at the marriage > date, than I mention that the parents are born BEF 1800 to have any idea in > my database. > > AFT > > I use AFT mostly if I do not know the date of death. In the case before > marriage 1840, if a parent is present to a marriage of one of their > children than I mention died AFT. 1840 if known that one of the parents > died before 1840 than I mention died BEF 1840. > > ABT > > I know sometimes the exact marriage date and the ages of groom and bride. In > that case I use ABT. > In my case of marriage 1840, if the groom is 22 and the bride 20 than I use > born ABT 1818 and born ABT 1820. > > In the cases of ABT it is closer to the exact date than at BEF and AFT. > > > Met vriendelijke groet, > > Max van Dam > Rechovoth > Israel > > http://www.maxvandam.info/ > > > > > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of > J. P. Gilliver (John) via > Sent: 27 March 2015 01:47 > To: [email protected] > Subject: [BK] How do you (discussion, not enquiry) express dates with the > BEF(ore) tag? > > There are times when I know something happened before a date: I sometimes > wonder how precise I should be with the date. For example, say someone is > known, on a specific date, to be a widow(er): obviously, the DOD of the > spouse is BEF(ore) that date. But do I say BEF ddmmyyyy? > That's strictly _correct_, and on the whole is what I do, but some people > seeing it might think it means they died quite close to it. > > I was just wondering how others express the date when they use BEEF. > > (Side idle thought: when the husband dies first, the wife is widowed, > becoming a widow. When the wife dies first, the husband becomes a widower - > so is he widowed, or widowered?) > -- > J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)[email protected]+H+Sh0!:`)DNAf > > "If you have ten thousand regulations you destroy all respect for the law." > - Winston Churchill. > Remember - Use the Archives at > http://archiver.rootsweb.ancestry.com/cgi-bin/search > ------------------------------- > To unsubscribe from the list, please send an email to > [email protected] with the word 'unsubscribe' without the quotes in > the subject and the body of the message > > > Remember - Use the Archives at http://archiver.rootsweb.ancestry.com/cgi-bin/search > ------------------------------- > To unsubscribe from the list, please send an email to [email protected] with the word 'unsubscribe' without the quotes in the subject and the body of the message >

Dear Diedrich Hesmer, I do not understand your remarks. I have only reacted how I use BEF, AFT and ABT. I do not use other abbreviations. In my website BEF, AFT and ABT comes these abbreviations correctly over in the other languages too. See for example Raphael Salomon Hofsteede. So my gedcom gives what I wish in this case. I have no experiences with other programs than BK and HUMO-gen. With my best regards, Max van Dam Rechovoth Israel http://www.maxvandam.info/ -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Diedrich Hesmer via Sent: 27 March 2015 13:01 To: [email protected] Subject: Re: [BK] DATE and GEDCOM - was [How do you (discussion, not enquiry) express dates with the BEF(ore) tag?] Dear all, let me take the note from Max van Dam and the GEDCOM question someone noted. In addition to the 3 described abbreviations GEDCOM allows: 2 DATE FROM Date 2 DATE TO Date 2 DATE FROM Date1 TO Date2 2 DATE BET Date1 AND Date2 2 DATE CAL Date 2 DATE EST Date and DATE may be: YYYY for the year MMM YYYY for month (3 letters) and year DD MMM YYYY for day month year This is for the ged-file, not necessarily for the BK input. BK may convert some input strings to correct GEDCOM syntax during GEDCOM export. CA, CIR, BET 1820-1825 or others are not allowed in ged-files and may be lost during transfer to another PC with a different genealogy program. Only in case the importing program has sufficient features build in, the dates will be taken correctly. best regards Diedrich (Hesmer) http://ofb.hesmer.name/gedcom Am 27.03.15 um 10:03 schrieb Max van Dam via: > Dear John Gilliver, > > I have a standard approach for using ABT, BEF, AFT. > > BEF > > I use BEF very often when I know the parents from somebody without any > dates for this person. > If somebody married in 1840 and the person is 20 years old at the > marriage date, than I mention that the parents are born BEF 1800 to > have any idea in my database. > > AFT > > I use AFT mostly if I do not know the date of death. In the case > before marriage 1840, if a parent is present to a marriage of one of > their children than I mention died AFT. 1840 if known that one of the > parents died before 1840 than I mention died BEF 1840. > > ABT > > I know sometimes the exact marriage date and the ages of groom and > bride. In that case I use ABT. > In my case of marriage 1840, if the groom is 22 and the bride 20 than > I use born ABT 1818 and born ABT 1820. > > In the cases of ABT it is closer to the exact date than at BEF and AFT. > > > Met vriendelijke groet, > > Max van Dam > Rechovoth > Israel > > http://www.maxvandam.info/ > > > > > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of J. P. Gilliver (John) via > Sent: 27 March 2015 01:47 > To: [email protected] > Subject: [BK] How do you (discussion, not enquiry) express dates with > the > BEF(ore) tag? > > There are times when I know something happened before a date: I > sometimes wonder how precise I should be with the date. For example, > say someone is known, on a specific date, to be a widow(er): > obviously, the DOD of the spouse is BEF(ore) that date. But do I say BEF ddmmyyyy? > That's strictly _correct_, and on the whole is what I do, but some > people seeing it might think it means they died quite close to it. > > I was just wondering how others express the date when they use BEEF. > > (Side idle thought: when the husband dies first, the wife is widowed, > becoming a widow. When the wife dies first, the husband becomes a > widower - so is he widowed, or widowered?) > -- > J. P. Gilliver. UMRA: 1960/<1985 > MB++G()AL-IS-Ch++(p)[email protected]+H+Sh0!:`)DNAf > > "If you have ten thousand regulations you destroy all respect for the law." > - Winston Churchill. > Remember - Use the Archives at > http://archiver.rootsweb.ancestry.com/cgi-bin/search > ------------------------------- > To unsubscribe from the list, please send an email to > [email protected] with the word 'unsubscribe' without the quotes > in the subject and the body of the message > > > Remember - Use the Archives at > http://archiver.rootsweb.ancestry.com/cgi-bin/search > ------------------------------- > To unsubscribe from the list, please send an email to > [email protected] with the word 'unsubscribe' without the quotes > in the subject and the body of the message > Remember - Use the Archives at http://archiver.rootsweb.ancestry.com/cgi-bin/search ------------------------------- To unsubscribe from the list, please send an email to [email protected] with the word 'unsubscribe' without the quotes in the subject and the body of the message