On Thu, 23 Feb 2012 18:01:56 -0000, "Malcolm Webb" <mfwebb2005@btinternet.com> wrote: >I have just looked at the GedCom file for my Great Aunt, Kezia Webb. Her >death date is shown in the GedCom as "Q1 1955" and that is what has been >imported into the other programme. > >Whilst Q1 1955 may not be recognised in the GedCom as a proper date and >therefore not used in calculations, it certainly imports the information as >I want to see it. > >If a date such as "12 des 1955" is imported into the GedCom and not >converted to the proper date as 12 Dec 1955, then I am correct in my >assumption that the GedCom only imports dates as strings of text and what is >typed in the date for any event is exactly what is exported via GedCom. > The point is that if you use a tag characters-combination that are not according to the Gedcomspecification it is not proper converted to the language of Gedcom. The language of Gedcom is English and all other tags are converted to that according to the use of a programs that have the different tags translated. e.g. Death in Englis are added as død in Norwegian, but the tag in Gedcom is DEAT http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gctoc.htm All Gedcom tags are in capitall. So if you add a wrong name of moth as "mai" = mai tjhat is not transferred but copied to the gedcomfile and copied from the gedcomfile innto the datafolder for the New program It is only the correct tags that are according to the programming in the program (e.g. BK) that is coverted correctly. the other are copied That ius also why I stand for the fact that using Words or abbr. that are not correct according to the Gedcom tags are not coverted by only copied. eg. q1 or Q1 is only copied -- Otto Jørgensen http://www.bkwin.info/ All email is checked by NORTON

I appreciate that my way of dealing with imprecise dates may not be correct and may not convert accurately in a GedCom, and may cause problems in other languages. But for my own purposes, I have found a solution that gives me what I want in BK and which will transfer in a GedCom the way I want it to. I only use GedCom to upload my database into another programme to allow me easy access for reference when visiting archives. So, the use of Q1 1955, for example, tells me that the date was obtained from the UK register of Births Marriages and Deaths (BMD) and this shows up in BK as an invalid date because it is not in the format (or cannot be converted into the format) I specified i.e. DDMMYYYY. If anyone wants to see the "invalid date warning" in red go to File/Options and tick the box on the dates tab which says "check each date for validity". If you want to switch it off, simply untick the box. All the best. Malcolm Webb mfwebb2005@btinternet.com <mailto:mfwebb2005@btinternet.com> -----Original Message----- From: Otto Jørgensen [mailto:otjoerge@online.no] Sent: 23 February 2012 19:24 To: mfwebb2005@btinternet.com Cc: bk@rootsweb.com Subject: Re: [BK] Why "invalid date"? Also quarters. On Thu, 23 Feb 2012 18:01:56 -0000, "Malcolm Webb" <mfwebb2005@btinternet.com> wrote: >I have just looked at the GedCom file for my Great Aunt, Kezia Webb. Her >death date is shown in the GedCom as "Q1 1955" and that is what has been >imported into the other programme. > >Whilst Q1 1955 may not be recognised in the GedCom as a proper date and >therefore not used in calculations, it certainly imports the information as >I want to see it. > >If a date such as "12 des 1955" is imported into the GedCom and not >converted to the proper date as 12 Dec 1955, then I am correct in my >assumption that the GedCom only imports dates as strings of text and what is >typed in the date for any event is exactly what is exported via GedCom. > The point is that if you use a tag characters-combination that are not according to the Gedcomspecification it is not proper converted to the language of Gedcom. The language of Gedcom is English and all other tags are converted to that according to the use of a programs that have the different tags translated. e.g. Death in Englis are added as død in Norwegian, but the tag in Gedcom is DEAT http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gctoc.htm All Gedcom tags are in capitall. So if you add a wrong name of moth as "mai" = mai tjhat is not transferred but copied to the gedcomfile and copied from the gedcomfile innto the datafolder for the New program It is only the correct tags that are according to the programming in the program (e.g. BK) that is coverted correctly. the other are copied That ius also why I stand for the fact that using Words or abbr. that are not correct according to the Gedcom tags are not coverted by only copied. eg. q1 or Q1 is only copied -- Otto Jørgensen http://www.bkwin.info/ All email is checked by NORTON

Hi, Malcolm et al For dates obtained from the UK Registers of births, marriages and deaths I would suggest using the prefix BEF. So that for an event found in Q1 1955, I put BEF 31/3/1955. This makes clear when the event occurred and more importantly, it is a 'valid' date! Regards, Ivan Dickason Berkshire UK -----Original Message----- From: bk-bounces@rootsweb.com [mailto:bk-bounces@rootsweb.com] On Behalf Of Malcolm Webb Sent: 24 February 2012 07:03 To: Otto Jørgensen Cc: bk@rootsweb.com Subject: Re: [BK] Why "invalid date"? Also quarters. I appreciate that my way of dealing with imprecise dates may not be correct and may not convert accurately in a GedCom, and may cause problems in other languages. But for my own purposes, I have found a solution that gives me what I want in BK and which will transfer in a GedCom the way I want it to. I only use GedCom to upload my database into another programme to allow me easy access for reference when visiting archives. So, the use of Q1 1955, for example, tells me that the date was obtained from the UK register of Births Marriages and Deaths (BMD) and this shows up in BK as an invalid date because it is not in the format (or cannot be converted into the format) I specified i.e. DDMMYYYY. If anyone wants to see the "invalid date warning" in red go to File/Options and tick the box on the dates tab which says "check each date for validity". If you want to switch it off, simply untick the box. All the best. Malcolm Webb mfwebb2005@btinternet.com <mailto:mfwebb2005@btinternet.com> -----Original Message----- From: Otto Jørgensen [mailto:otjoerge@online.no] Sent: 23 February 2012 19:24 To: mfwebb2005@btinternet.com Cc: bk@rootsweb.com Subject: Re: [BK] Why "invalid date"? Also quarters. On Thu, 23 Feb 2012 18:01:56 -0000, "Malcolm Webb" <mfwebb2005@btinternet.com> wrote: >I have just looked at the GedCom file for my Great Aunt, Kezia Webb. Her >death date is shown in the GedCom as "Q1 1955" and that is what has been >imported into the other programme. > >Whilst Q1 1955 may not be recognised in the GedCom as a proper date and >therefore not used in calculations, it certainly imports the information as >I want to see it. > >If a date such as "12 des 1955" is imported into the GedCom and not >converted to the proper date as 12 Dec 1955, then I am correct in my >assumption that the GedCom only imports dates as strings of text and what is >typed in the date for any event is exactly what is exported via GedCom. > The point is that if you use a tag characters-combination that are not according to the Gedcomspecification it is not proper converted to the language of Gedcom. The language of Gedcom is English and all other tags are converted to that according to the use of a programs that have the different tags translated. e.g. Death in Englis are added as død in Norwegian, but the tag in Gedcom is DEAT http://homepages.rootsweb.ancestry.com/~pmcbride/gedcom/55gctoc.htm All Gedcom tags are in capitall. So if you add a wrong name of moth as "mai" = mai tjhat is not transferred but copied to the gedcomfile and copied from the gedcomfile innto the datafolder for the New program It is only the correct tags that are according to the programming in the program (e.g. BK) that is coverted correctly. the other are copied That ius also why I stand for the fact that using Words or abbr. that are not correct according to the Gedcom tags are not coverted by only copied. eg. q1 or Q1 is only copied -- Otto Jørgensen http://www.bkwin.info/ All email is checked by NORTON Remember - Use the Archives at http://archiver.rootsweb.ancestry.com/cgi-bin/search ------------------------------- To unsubscribe from the list, please send an email to BK-request@rootsweb.com with the word 'unsubscribe' without the quotes in the subject and the body of the message

In message <!&!AAAAAAAAAAAYAAAAAAAAAFcq+uxz7DBPmPsnBjh+/pLCgAAAEAAAAJT6T9r0t9FJuf2eF IVTUPkBAAAAAA==@dickason.co.uk>, Ivan Dickason <ivan@dickason.co.uk> writes: >Hi, Malcolm et al > >For dates obtained from the UK Registers of births, marriages and deaths I >would suggest using the prefix BEF. So that for an event found in Q1 1955, I >put BEF 31/3/1955. > >This makes clear when the event occurred and more importantly, it is a >'valid' date! [] Thanks, Ivan - worth considering! I suspect I'll continue, since I have so many already entered, using ____1955 (which BK reformats to __ ___ 1955), with "Q1" in the comment field, but since Malcolm has discovered that "Q1 1955" is to some extent parsed by BK, I might start using it. Though looking at your example again, Malcolm, you say 'I have an accurate birth date of a great aunt as 26 May 1872 and a death date as Q1 1955. Her age in the BK database is shown as "83+/-" and in the family group sheet it says "died at age 83".' I suspect BK is getting the 1955, but not the Q1 - have you other examples (with different quarters)? Because if she died in Q1 1955, that would be _before_ her 83rd birthday, which by usual convention (in England anyway, and 'I think'), would be described as 'died at age 82' (or of course 'in her 83rd year'). But at least it suggests that BK is correctly recognising the year, even if it isn't in DDMMYYYY or DD MMM YYYY format. [I, too, only use GEDCOM for uploading - the BK database is my reference source.] I do have an acknowledgement from Ancestry - about a year or more ago, now, I think - that their way of showing quarters in search results (i. e. "Mar 1956" when what they really mean is "Jan-Mar 1956") is misleading. (They did point out that you get the full Jan-Mar if you look at the record, but acknowledged that it was unclear in the search result.) -- J. P. Gilliver. UMRA: 1960/<1985 MB++G.5AL-IS-P--Ch++(p)Ar@T0H+Sh0!:`)DNAf <Squawk> Pieces of eight! <Squawk> Pieces of eight! <Squawk> Pieces of nine! <SYSTEM HALTED: parroty error!>

On Fri, 24 Feb 2012 07:02:33 -0000, "Malcolm Webb" <mfwebb2005@btinternet.com> wrote: >I appreciate that my way of dealing with imprecise dates may not be correct >and may not convert accurately in a GedCom, and may cause problems in other >languages. But for my own purposes, I have found a solution that gives me >what I want in BK and which will transfer in a GedCom the way I want it to. >I only use GedCom to upload my database into another programme to allow me >easy access for reference when visiting archives. > >So, the use of Q1 1955, for example, tells me that the date was obtained >from the UK register of Births Marriages and Deaths (BMD) and this shows up >in BK as an invalid date because it is not in the format (or cannot be >converted into the format) I specified i.e. DDMMYYYY. > >If anyone wants to see the "invalid date warning" in red go to File/Options >and tick the box on the dates tab which says "check each date for validity". >If you want to switch it off, simply untick the box. > we also use tags and words that are not legal or are not part of the programming. That is to make reports and data more friendly to the reader of reports, so Q1 or CHILD = age < 8 years INFANT = age < 1 year STILLBORN = died just prior, at, or near birth, 0 years in Norwegian, german danish are used, but they are presented in Red warning in the program, but gives the reader a nice way to understand and reading For the 4 tags mention in Norwegian it would be Kv 1 barn nyfødt døfødt This is as a result of the limits in Gedcom and BK -- Otto Jørgensen http://www.bkwin.info/ All email is checked by NORTON