I believe that in short time we will have the New update ready fir downloading. So still untill that day we have to waite --- hilsen/regards Otto -#- Den 29.05.2019 07:36, skrev Bert Maier via BK: > Hello John, and BK community, > is there any news regarding the future update policy of BK? > As I stated in a previous post, the website bkwin.org lists the last available version as 7.3.4, dated Dec. 2018. > In the shop, however, there seems to be a version 7.4 for sale. > Can you please explain what will be the future procedure to be informed about updates and how to obtain them? > Thanks a lot! > Bert from Germany > > Am Freitag, 10. Mai 2019, 17:02:42 MESZ hat Bert Maier via BK <bk@rootsweb.com> Folgendes geschrieben: > > Dear BK users, dear John, > as a registered user I always try to keep my copy of BK up to date.The web site bkwin.org (and also bwin.com) says the latest version is 7.3.4, published in Dec. 2018.However, the online store now offers a version 7.4, but it is for sale, even for registered users. > > Can anyone please explain what will be the future update policy of BK?What is the difference between 7.3 and 7.4? > If I buy the update to 7.4 now, will I be able to participate in future updates (7.5 etc.) for free again? Or will all future updates be chargeable from now on? > Any clarification is welcome. > Bert from Germany > > our loyal RootsWeb community

Hello John, and BK community, is there any news regarding the future update policy of BK? As I stated in a previous post, the website bkwin.org lists the last available version as 7.3.4, dated Dec. 2018. In the shop, however, there seems to be a version 7.4 for sale. Can you please explain what will be the future procedure to be informed about updates and how to obtain them? Thanks a lot! Bert from Germany Am Freitag, 10. Mai 2019, 17:02:42 MESZ hat Bert Maier via BK <bk@rootsweb.com> Folgendes geschrieben: Dear BK users, dear John, as a registered user I always try to keep my copy of BK up to date.The web site bkwin.org (and also bwin.com) says the latest version is 7.3.4, published in Dec. 2018.However, the online store now offers a version 7.4, but it is for sale, even for registered users. Can anyone please explain what will be the future update policy of BK?What is the difference between 7.3 and 7.4? If I buy the update to 7.4 now, will I be able to participate in future updates (7.5  etc.) for free again? Or will all future updates be chargeable from now on? Any clarification is welcome. Bert from Germany .

This just so brilliant, Diedrich Thank you for the link. The information therein is clean, clear & concise. What is needed now is for users to comply! The computers will handle a wide range of people variables, but not 'free-thought' data entry. I will create a STANDARDS note for myself. Obviously that will be the simplest of singular choices. That means my compliance will be assured. Regards Barry P. ---------===========------ -----Original Message----- From: Diedrich Hesmer [mailto:dhesmer@gmx.de] Sent: Sunday, 26 May 2019 11:36 PM To: bk@rootsweb.com Subject: [BK] Re: What data to enter for DATE Hi Barry, Jim et. al. you might have a look to the link https://wiki-en.genealogy.net/Category:GEDCOM-Tag and on that page go to DATE. This is the english version of the results of a working group of 24 german genealogy programmers containing the definitions of GEDCOM standard 5.5.1 and the agreements reached in case of questionable items of the 5.5.1 for most of the GEDCOM tags. Our goal was to # Improve communication between Genealogy programs using GEDCOM files # Reduce loss of data during export/import of GEDCOM files # Common understanding and interpretation of the GEDCOM standard # Agree to a common solution to improve the user satisfaction # By obtaining the uniqueness of every program # Use the GEDCOM standard draft 5.5.1 as base This might help, even in your case. Have a look at the DATE page to item 3.6 Date Phrase: The text must be enclosed in round brackets, e.g. using Jims example: 2 DATE (?/??/19??) would be according to the specification. Usually the exporting program should add these 2 brackets. The only question would be, does a reading program understand the standard correctly. best regards Diedrich (Hesmer) Am 26.05.19 um 12:55 schrieb Barry PYCROFT: > That is good, Jim. > It certainly satisfies local & personal application. The Century idea is good,. For that, your reasoning is good. > Somehow though, age and Reasonableness calculations get lost. But they do also if blank!! Hi hi. > > However, I wonder how a remote reader would enjoy the concept? Such as WCBeta? > > Barry P. > > -----Original Message----- > From: Jim Dell via BK [mailto:bk@rootsweb.com] > Sent: Sunday, 26 May 2019 8:55 PM > To: barry@pycroft.co.nz; bk@rootsweb.com > Cc: Jim Dell <dellji@yahoo.com> > Subject: [BK] Re: What data to enter for DATE > > BarryI use three (3) question marks for unknown places.For unknown > birth or death I use ?/??/19??Guessing at the centuryThat way when I > print out a register report and give it to a relative, who is not a > genealogist, they know something is missing and might give me some > clues where to find the missing information Jim > > > Sent from Yahoo Mail for iPad > > > On Saturday, May 25, 2019, 11:06 PM, Barry PYCROFT <barry@pycroft.co.nz> wrote: > > Still on Gedcom and VALIDATOR. > > I have a Gedcom where the [DATE ] has a value of <UNKNOWN>. > There is also no [PLAC ] entered for this event. > > **> What is the proper thing to do? > > Personally I leave the whole event as unwritten, blank. > Others Might write DEAD or UNKNOWN > Some might have a Place with no Date. > > Some receiving programs do not care. If the last four characters of a DATE are not numbers that represent a YEAR, then omission is the result. > > Aft, Bef, and Abt are recognised "approximations or guesses". > Cir apparently is not a recognised value part for DATE. > > **> Your thoughts leading to what data to enter will be helpful. > > Barry P. > > Barry PYCROFT > Christchurch. 8013 > New Zealand > - - - - - - - - - - - - . > > > > _______________________________________________ > Remember - Use the Archives at > http://archiver.rootsweb.com/cgi-bin/search > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref Unsubscribe > https://lists.rootsweb.com/postorius/lists/bk@rootsweb.com > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: > https://ancstry.me/2HDBym9 Rootsweb Blog: http://rootsweb.blog > RootsWeb is funded and supported by Ancestry.com and our loyal > RootsWeb community > > > > > _______________________________________________ > Remember - Use the Archives at > http://archiver.rootsweb.com/cgi-bin/search > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref Unsubscribe > https://lists.rootsweb.com/postorius/lists/bk@rootsweb.com > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: > https://ancstry.me/2HDBym9 Rootsweb Blog: http://rootsweb.blog > RootsWeb is funded and supported by Ancestry.com and our loyal > RootsWeb community > > _______________________________________________ > Remember - Use the Archives at > http://archiver.rootsweb.com/cgi-bin/search > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref Unsubscribe > https://lists.rootsweb.com/postorius/lists/bk@rootsweb.com > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: > https://ancstry.me/2HDBym9 Rootsweb Blog: http://rootsweb.blog > RootsWeb is funded and supported by Ancestry.com and our loyal > RootsWeb community > _______________________________________________ Remember - Use the Archives at http://archiver.rootsweb.com/cgi-bin/search _______________________________________________ Email preferences: http://bit.ly/rootswebpref Unsubscribe https://lists.rootsweb.com/postorius/lists/bk@rootsweb.com Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: https://ancstry.me/2HDBym9 Rootsweb Blog: http://rootsweb.blog RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community

See here a piece of Gedcom I received by email a file downloaded from Ancestry.com First up is the UTF-8 is not a character set to be used with GEDC 5.5. (It was not invented at that time!). Apparently a ""SUBmitter"" is a requirement. Perhaps for the original intent. 0 HEAD 1 CHAR UTF-8 1 SOUR Ancestry.com Family Trees 2 VERS (2010.3) 2 NAME Ancestry.com Family Trees 2 CORP Ancestry.com 1 GEDC 2 VERS 5.5 2 FORM LINEAGE-LINKED There are only 5100 individuals, but over 9000 Compatibility issues. Note the warnings are because the VALIDATOR is applying very strict, very simple 'original' rules of the 1980's. And the garbage that Family Tree analyser makes of this, its own tree is horrendous. So I would say that BK is pretty good with its Gedcom overall. The secret is in the quality and style of the data that is written in the database. Barry P. Barry PYCROFT www.pycroft.co.nz 8 Orcades Street Shirley Christchurch. 8013 New Zealand Ph: +64-3-942.8417 Mob:- +64 223 140 100 - - - - - - - - - - - - - . -

Hi Barry, Jim et. al. you might have a look to the link https://wiki-en.genealogy.net/Category:GEDCOM-Tag and on that page go to DATE. This is the english version of the results of a working group of 24 german genealogy programmers containing the definitions of GEDCOM standard 5.5.1 and the agreements reached in case of questionable items of the 5.5.1 for most of the GEDCOM tags. Our goal was to # Improve communication between Genealogy programs using GEDCOM files # Reduce loss of data during export/import of GEDCOM files # Common understanding and interpretation of the GEDCOM standard # Agree to a common solution to improve the user satisfaction # By obtaining the uniqueness of every program # Use the GEDCOM standard draft 5.5.1 as base This might help, even in your case. Have a look at the DATE page to item 3.6 Date Phrase: The text must be enclosed in round brackets, e.g. using Jims example: 2 DATE (?/??/19??) would be according to the specification. Usually the exporting program should add these 2 brackets. The only question would be, does a reading program understand the standard correctly. best regards Diedrich (Hesmer) Am 26.05.19 um 12:55 schrieb Barry PYCROFT: > That is good, Jim. > It certainly satisfies local & personal application. The Century idea is good,. For that, your reasoning is good. > Somehow though, age and Reasonableness calculations get lost. But they do also if blank!! Hi hi. > > However, I wonder how a remote reader would enjoy the concept? Such as WCBeta? > > Barry P. > > -----Original Message----- > From: Jim Dell via BK [mailto:bk@rootsweb.com] > Sent: Sunday, 26 May 2019 8:55 PM > To: barry@pycroft.co.nz; bk@rootsweb.com > Cc: Jim Dell <dellji@yahoo.com> > Subject: [BK] Re: What data to enter for DATE > > BarryI use three (3) question marks for unknown places.For unknown birth or death I use ?/??/19??Guessing at the centuryThat way when I print out a register report and give it to a relative, who is not a genealogist, they know something is missing and might give me some clues where to find the missing information Jim > > > Sent from Yahoo Mail for iPad > > > On Saturday, May 25, 2019, 11:06 PM, Barry PYCROFT <barry@pycroft.co.nz> wrote: > > Still on Gedcom and VALIDATOR. > > I have a Gedcom where the [DATE ] has a value of <UNKNOWN>. > There is also no [PLAC ] entered for this event. > > **> What is the proper thing to do? > > Personally I leave the whole event as unwritten, blank. > Others Might write DEAD or UNKNOWN > Some might have a Place with no Date. > > Some receiving programs do not care. If the last four characters of a DATE are not numbers that represent a YEAR, then omission is the result. > > Aft, Bef, and Abt are recognised "approximations or guesses". > Cir apparently is not a recognised value part for DATE. > > **> Your thoughts leading to what data to enter will be helpful. > > Barry P. > > Barry PYCROFT > Christchurch. 8013 > New Zealand > - - - - - - - - - - - - . > > > > _______________________________________________ > Remember - Use the Archives at http://archiver.rootsweb.com/cgi-bin/search > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref Unsubscribe https://lists.rootsweb.com/postorius/lists/bk@rootsweb.com > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: https://ancstry.me/2HDBym9 Rootsweb Blog: http://rootsweb.blog RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community > > > > > _______________________________________________ > Remember - Use the Archives at http://archiver.rootsweb.com/cgi-bin/search > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref Unsubscribe https://lists.rootsweb.com/postorius/lists/bk@rootsweb.com > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: https://ancstry.me/2HDBym9 Rootsweb Blog: http://rootsweb.blog RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community > > _______________________________________________ > Remember - Use the Archives at http://archiver.rootsweb.com/cgi-bin/search > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref > Unsubscribe https://lists.rootsweb.com/postorius/lists/bk@rootsweb.com > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: https://ancstry.me/2HDBym9 > Rootsweb Blog: http://rootsweb.blog > RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community >

Barry Right now WCBeta is down for maintence;-) Jim -----Original Message----- From: Barry PYCROFT <barry@pycroft.co.nz> Sent: Sunday, May 26, 2019 6:55 AM To: bk@rootsweb.com Subject: [BK] Re: What data to enter for DATE That is good, Jim. It certainly satisfies local & personal application. The Century idea is good,. For that, your reasoning is good. Somehow though, age and Reasonableness calculations get lost. But they do also if blank!! Hi hi. However, I wonder how a remote reader would enjoy the concept? Such as WCBeta? Barry P. -----Original Message----- From: Jim Dell via BK [mailto:bk@rootsweb.com] Sent: Sunday, 26 May 2019 8:55 PM To: barry@pycroft.co.nz; bk@rootsweb.com Cc: Jim Dell <dellji@yahoo.com> Subject: [BK] Re: What data to enter for DATE BarryI use three (3) question marks for unknown places.For unknown birth or death I use ?/??/19??Guessing at the centuryThat way when I print out a register report and give it to a relative, who is not a genealogist, they know something is missing and might give me some clues where to find the missing information Jim Sent from Yahoo Mail for iPad On Saturday, May 25, 2019, 11:06 PM, Barry PYCROFT <barry@pycroft.co.nz> wrote: Still on Gedcom and VALIDATOR. I have a Gedcom where the [DATE ] has a value of <UNKNOWN>. There is also no [PLAC ] entered for this event. **> What is the proper thing to do? Personally I leave the whole event as unwritten, blank. Others Might write DEAD or UNKNOWN Some might have a Place with no Date. Some receiving programs do not care. If the last four characters of a DATE are not numbers that represent a YEAR, then omission is the result. Aft, Bef, and Abt are recognised "approximations or guesses". Cir apparently is not a recognised value part for DATE. **> Your thoughts leading to what data to enter will be helpful. Barry P. Barry PYCROFT Christchurch. 8013 New Zealand - - - - - - - - - - - - . _______________________________________________ Remember - Use the Archives at http://archiver.rootsweb.com/cgi-bin/search _______________________________________________ Email preferences: http://bit.ly/rootswebpref Unsubscribe https://lists.rootsweb.com/postorius/lists/bk@rootsweb.com Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: https://ancstry.me/2HDBym9 Rootsweb Blog: http://rootsweb.blog RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community _______________________________________________ Remember - Use the Archives at http://archiver.rootsweb.com/cgi-bin/search _______________________________________________ Email preferences: http://bit.ly/rootswebpref Unsubscribe https://lists.rootsweb.com/postorius/lists/bk@rootsweb.com Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: https://ancstry.me/2HDBym9 Rootsweb Blog: http://rootsweb.blog RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community _______________________________________________ Remember - Use the Archives at http://archiver.rootsweb.com/cgi-bin/search _______________________________________________ Email preferences: http://bit.ly/rootswebpref Unsubscribe https://lists.rootsweb.com/postorius/lists/bk@rootsweb.com Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: https://ancstry.me/2HDBym9 Rootsweb Blog: http://rootsweb.blog RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community

That is good, Jim. It certainly satisfies local & personal application. The Century idea is good,. For that, your reasoning is good. Somehow though, age and Reasonableness calculations get lost. But they do also if blank!! Hi hi. However, I wonder how a remote reader would enjoy the concept? Such as WCBeta? Barry P. -----Original Message----- From: Jim Dell via BK [mailto:bk@rootsweb.com] Sent: Sunday, 26 May 2019 8:55 PM To: barry@pycroft.co.nz; bk@rootsweb.com Cc: Jim Dell <dellji@yahoo.com> Subject: [BK] Re: What data to enter for DATE BarryI use three (3) question marks for unknown places.For unknown birth or death I use ?/??/19??Guessing at the centuryThat way when I print out a register report and give it to a relative, who is not a genealogist, they know something is missing and might give me some clues where to find the missing information Jim Sent from Yahoo Mail for iPad On Saturday, May 25, 2019, 11:06 PM, Barry PYCROFT <barry@pycroft.co.nz> wrote: Still on Gedcom and VALIDATOR. I have a Gedcom where the [DATE ] has a value of <UNKNOWN>. There is also no [PLAC ] entered for this event. **> What is the proper thing to do? Personally I leave the whole event as unwritten, blank. Others Might write DEAD or UNKNOWN Some might have a Place with no Date. Some receiving programs do not care. If the last four characters of a DATE are not numbers that represent a YEAR, then omission is the result. Aft, Bef, and Abt are recognised "approximations or guesses". Cir apparently is not a recognised value part for DATE. **> Your thoughts leading to what data to enter will be helpful. Barry P. Barry PYCROFT Christchurch. 8013 New Zealand - - - - - - - - - - - - . _______________________________________________ Remember - Use the Archives at http://archiver.rootsweb.com/cgi-bin/search _______________________________________________ Email preferences: http://bit.ly/rootswebpref Unsubscribe https://lists.rootsweb.com/postorius/lists/bk@rootsweb.com Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: https://ancstry.me/2HDBym9 Rootsweb Blog: http://rootsweb.blog RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community _______________________________________________ Remember - Use the Archives at http://archiver.rootsweb.com/cgi-bin/search _______________________________________________ Email preferences: http://bit.ly/rootswebpref Unsubscribe https://lists.rootsweb.com/postorius/lists/bk@rootsweb.com Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: https://ancstry.me/2HDBym9 Rootsweb Blog: http://rootsweb.blog RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community

BarryI use three (3) question marks for unknown places.For unknown birth or death I use ?/??/19??Guessing at the centuryThat way when I print out a register report and give it to a relative, who is not a genealogist, they know something is missing and might give me some clues where to find the missing information Jim Sent from Yahoo Mail for iPad On Saturday, May 25, 2019, 11:06 PM, Barry PYCROFT <barry@pycroft.co.nz> wrote: Still on Gedcom and VALIDATOR. I have a Gedcom where the [DATE ] has a value of <UNKNOWN>. There is also no [PLAC ] entered for this event. **> What is the proper thing to do? Personally I leave the whole event  as unwritten, blank. Others Might write DEAD or UNKNOWN Some might have a Place with no Date. Some receiving programs do not care.  If the last four characters of a DATE are not numbers that represent a YEAR, then omission is the result. Aft, Bef, and Abt are recognised  "approximations or guesses". Cir apparently is not a recognised value part for DATE. **> Your thoughts leading to what data to enter will be helpful.     Barry P. Barry PYCROFT    Christchurch.  8013    New Zealand - - - - - - - - - - - - . _______________________________________________ Remember - Use the Archives at http://archiver.rootsweb.com/cgi-bin/search _______________________________________________ Email preferences: http://bit.ly/rootswebpref Unsubscribe https://lists.rootsweb.com/postorius/lists/bk@rootsweb.com Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: https://ancstry.me/2HDBym9 Rootsweb Blog: http://rootsweb.blog RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community

Still on Gedcom and VALIDATOR. I have a Gedcom where the [DATE ] has a value of <UNKNOWN>. There is also no [PLAC ] entered for this event. **> What is the proper thing to do? Personally I leave the whole event as unwritten, blank. Others Might write DEAD or UNKNOWN Some might have a Place with no Date. Some receiving programs do not care. If the last four characters of a DATE are not numbers that represent a YEAR, then omission is the result. Aft, Bef, and Abt are recognised "approximations or guesses". Cir apparently is not a recognised value part for DATE. **> Your thoughts leading to what data to enter will be helpful. Barry P. Barry PYCROFT Christchurch. 8013 New Zealand - - - - - - - - - - - - .

the gedcom files should always in the heading give information about the correct characterset that is used for the file, and the receiverprogram should use that --- hilsen/regards Otto -#- Den 25.05.2019 23:30, skrev Joe: > I did not select a character set, looks like default was ANSEL, will try again with UTF-8. > > Thanks , John

I did not select a character set, looks like default was ANSEL, will try again with UTF-8. Thanks , John On 5/25/2019 1:31 PM, John Steed wrote: > To Joe Weiss > > As a test, I entered a name in BK as > > Joe Dörrenbach > > Then I made a GEDCOM file using the option for UTF-8 characters and opened the GEDCOM file with NotePad. > > It showed correctly > > 1 CHAR UTF-8 > 0 @I1086@ INDI > 1 NAME Joe /Dörrenbach/ > 1 SEX M > > So are you picking UTF-8 character set? > > Do you have the options in BK set to anything unusual for the character set? > > John Steed > > > ________________________________ > From: Barry PYCROFT <barry@pycroft.co.nz> > Sent: Saturday, May 25, 2019 4:30 AM > To: bk@rootsweb.com > Subject: [BK] Re: more GEDCOM errors > > I think it is about time we had UTF-16 as an option in addition to the UTF-8 > Barry P. > > -----Original Message----- > From: Joe [mailto:joe968@comcast.net] > Sent: Saturday, 25 May 2019 9:25 AM > To: bk@rootsweb.com > Subject: [BK] more GEDCOM errors > > Another GEDCOM error I am getting is unmapable characters. What is in my files as Dörrenbach ends up D”rrenbach in the gedcom. Does GEDCOM not support the full 256 characters set? Some of my data is cut and paste so may have illegal characters. How can I view the ascii number of the character. > > Also , how do I find hidden white spaces in the GEDCOM. > > Thanks for any help. > Joe Weiss > > _______________________________________________ >

To Joe Weiss As a test, I entered a name in BK as Joe Dörrenbach Then I made a GEDCOM file using the option for UTF-8 characters and opened the GEDCOM file with NotePad. It showed correctly 1 CHAR UTF-8 0 @I1086@ INDI 1 NAME Joe /Dörrenbach/ 1 SEX M So are you picking UTF-8 character set? Do you have the options in BK set to anything unusual for the character set? John Steed ________________________________ From: Barry PYCROFT <barry@pycroft.co.nz> Sent: Saturday, May 25, 2019 4:30 AM To: bk@rootsweb.com Subject: [BK] Re: more GEDCOM errors I think it is about time we had UTF-16 as an option in addition to the UTF-8 Barry P. -----Original Message----- From: Joe [mailto:joe968@comcast.net] Sent: Saturday, 25 May 2019 9:25 AM To: bk@rootsweb.com Subject: [BK] more GEDCOM errors Another GEDCOM error I am getting is unmapable characters. What is in my files as Dörrenbach ends up D”rrenbach in the gedcom. Does GEDCOM not support the full 256 characters set? Some of my data is cut and paste so may have illegal characters. How can I view the ascii number of the character. Also , how do I find hidden white spaces in the GEDCOM. Thanks for any help. Joe Weiss _______________________________________________ Remember - Use the Archives at https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Farchiver.rootsweb.com%2Fcgi-bin%2Fsearch&amp;data=02%7C01%7C%7C90dcda07d2c345f8a7cb08d6e0c9d81a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636943554848156647&amp;sdata=pxGYrfp14ASlUbGW6bXPXi3uYGafXjQ5kbUWDyez0eU%3D&amp;reserved=0 _______________________________________________ Email preferences: https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fbit.ly%2Frootswebpref&amp;data=02%7C01%7C%7C90dcda07d2c345f8a7cb08d6e0c9d81a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636943554848156647&amp;sdata=S%2Frp7po3NgXotZLMVGNj4IDB4O3wnUqtO25VPZesVJk%3D&amp;reserved=0 Unsubscribe https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.rootsweb.com%2Fpostorius%2Flists%2Fbk%40rootsweb.com&amp;data=02%7C01%7C%7C90dcda07d2c345f8a7cb08d6e0c9d81a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636943554848156647&amp;sdata=kuIU%2FVEy1ofFIdhRgnwyV%2FiOv4w4D2QEfQ86q1ZbE%2Fw%3D&amp;reserved=0 Privacy Statement: https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fancstry.me%2F2JWBOdY&amp;data=02%7C01%7C%7C90dcda07d2c345f8a7cb08d6e0c9d81a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636943554848156647&amp;sdata=D3ZHrTOsYKgSlnDQqfhnJH%2F1Q4nxwNNa6pvb%2Buiye2U%3D&amp;reserved=0 Terms and Conditions: https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fancstry.me%2F2HDBym9&amp;data=02%7C01%7C%7C90dcda07d2c345f8a7cb08d6e0c9d81a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636943554848166658&amp;sdata=070dx3JGiSxmjZmnoSBNW%2FullXxgYwDVtEePjuNG0lY%3D&amp;reserved=0 Rootsweb Blog: https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Frootsweb.blog&amp;data=02%7C01%7C%7C90dcda07d2c345f8a7cb08d6e0c9d81a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636943554848166658&amp;sdata=4TS4LVAAUYqQco409y6opXZGThzLWLNbl3DP9EE3nEc%3D&amp;reserved=0 RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community _______________________________________________ Remember - Use the Archives at https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Farchiver.rootsweb.com%2Fcgi-bin%2Fsearch&amp;data=02%7C01%7C%7C90dcda07d2c345f8a7cb08d6e0c9d81a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636943554848166658&amp;sdata=satEuIj1FY%2BAVoV1gssFLDVyC21cvELbU2loPuJKimM%3D&amp;reserved=0 _______________________________________________ Email preferences: https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fbit.ly%2Frootswebpref&amp;data=02%7C01%7C%7C90dcda07d2c345f8a7cb08d6e0c9d81a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636943554848166658&amp;sdata=Khl9qQRdJOpgz956qAgBkn9jzj%2BiukpngBYa%2BwPq9bA%3D&amp;reserved=0 Unsubscribe https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.rootsweb.com%2Fpostorius%2Flists%2Fbk%40rootsweb.com&amp;data=02%7C01%7C%7C90dcda07d2c345f8a7cb08d6e0c9d81a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636943554848166658&amp;sdata=gmXnuCxPgbBCk9VLy77efaxvOTYgu%2Fl54ksuNN7MeR4%3D&amp;reserved=0 Privacy Statement: https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fancstry.me%2F2JWBOdY&amp;data=02%7C01%7C%7C90dcda07d2c345f8a7cb08d6e0c9d81a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636943554848166658&amp;sdata=NdUY%2F58J5XR7pIafEXxxUrMdLpvsfMQAytrKyV9%2F8Uo%3D&amp;reserved=0 Terms and Conditions: https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fancstry.me%2F2HDBym9&amp;data=02%7C01%7C%7C90dcda07d2c345f8a7cb08d6e0c9d81a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636943554848166658&amp;sdata=070dx3JGiSxmjZmnoSBNW%2FullXxgYwDVtEePjuNG0lY%3D&amp;reserved=0 Rootsweb Blog: https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Frootsweb.blog&amp;data=02%7C01%7C%7C90dcda07d2c345f8a7cb08d6e0c9d81a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636943554848166658&amp;sdata=4TS4LVAAUYqQco409y6opXZGThzLWLNbl3DP9EE3nEc%3D&amp;reserved=0 RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community

Thanks Jim, something else not thought about.  We'll see if such pops up in Reasonableness check.   I have loads of work ahead of me as I have 27 pages of inconsistencies.  Not sure how I got so far behind checking my database. Fran On 25/05/2019 7:47 a.m., Jim Dell via BK wrote: > Fran > Another error that pops up for me is second marriages, where say a man > marries a very young lady and you have her marked as step mother for his > children that might be older than her. > Also if you have the century wrong on one of the parents it will be a chain > reaction for all the children. So one date in the birth date of a parent > might create multiple errors. > > Jim > > -----Original Message----- > From: Barry PYCROFT <barry@pycroft.co.nz> > Sent: Saturday, May 25, 2019 12:27 AM > To: bk@rootsweb.com > Subject: [BK] Re: Reasonable Check > > Fran > I have just tested in the data you sent me. > The test is for those event OUTSIDE the reasonable. > If you set 30 as a minimum, then zero to thirty is outside that range. And > over 50 is the high end. > What you might want is those that3 do not appear with a marriage range of > 0 to 20, then 0 to 30, then zero to 50 etc. > It took me a while to see what was happening since all other tests are > reported in the list. > It would be helpful if the report could have option for each test. > > Barry P. > > > > -----Original Message----- > From: Frances LaChance [mailto:singer.35@hotmail.com] > Sent: Saturday, 25 May 2019 11:25 AM > To: bk@rootsweb.com > Subject: [BK] Reasonable Check > > Bk 7.3.4 > > Doing a reasonable check and have set parameters for "Ages difference of > spouses" as 15 - 30.   However, I am getting hits for age difference of > 2-3 years, which is practically everyone in my database of over 80,000. Am I > doing something wrong? > > Fran > > > _______________________________________________ > Remember - Use the Archives at http://archiver.rootsweb.com/cgi-bin/search > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref Unsubscribe > https://lists.rootsweb.com/postorius/lists/bk@rootsweb.com > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: > https://ancstry.me/2HDBym9 Rootsweb Blog: http://rootsweb.blog RootsWeb is > funded and supported by Ancestry.com and our loyal RootsWeb community > > _______________________________________________ > Remember - Use the Archives at http://archiver.rootsweb.com/cgi-bin/search > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref Unsubscribe > https://lists.rootsweb.com/postorius/lists/bk@rootsweb.com > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: > https://ancstry.me/2HDBym9 Rootsweb Blog: http://rootsweb.blog RootsWeb is > funded and supported by Ancestry.com and our loyal RootsWeb community > > _______________________________________________ > Remember - Use the Archives at http://archiver.rootsweb.com/cgi-bin/search > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref > Unsubscribe https://lists.rootsweb.com/postorius/lists/bk@rootsweb.com > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: https://ancstry.me/2HDBym9 > Rootsweb Blog: http://rootsweb.blog > RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community

To Joe Weiss It looks like there is some invalid (and invisible) character in the regular Name field after the last name. Go to the Edit screen and bring up person 72346 Click on the Name field. Press the END key and press the Back-Space key to delete everything after the last name. You may need to type spaces after the last name to overwrite the invalid characters. Then move to another person and if it asks "do you want to change the name of the person" answer Yes. You can then also delete what you have in the Last Name field on the Names tab. John Steed ________________________________ From: Joe <joe968@comcast.net> Sent: Friday, May 24, 2019 4:57 PM To: bk@rootsweb.com Subject: [BK] GEDCOM problem I am also getting my upload GEDCOM file rejected by WorldConnectBeta. I tried the GEDCOM validator and among the many errors were several "invalid line structures", This is a snip-it of one, the third line is the error. 0 @I72346@ INDI 1 NAME Barbara Ehrmanntraut / / 2 _AKAN B Ehrmanbrant 1 SEX F 1 BIRT 2 DATE 21 OCT 1815 2 PLAC Schèonau (BA. Primasens), Bayern, Germany 1 DEAT Searching for this person with F3 it does not find her, when I find her and go to Names, Show Defaults. it has only First Name , no Last Name or Sort Name. I entered the last name to the last name and sort name boxes and after a re-index F3 still does not find her. How do I fix this and find the rest of them? My data file has 112,000 names, using BK 7.4.1. Joe Weiss _______________________________________________ Remember - Use the Archives at https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Farchiver.rootsweb.com%2Fcgi-bin%2Fsearch&amp;data=02%7C01%7C%7C17e7440f1c274fee324208d6e0690e05%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636943139136872424&amp;sdata=%2BEbnnUEZlKmopUN3bi7ny5QZrlpdbfUrClWVBiP0OTE%3D&amp;reserved=0 _______________________________________________ Email preferences: https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fbit.ly%2Frootswebpref&amp;data=02%7C01%7C%7C17e7440f1c274fee324208d6e0690e05%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636943139136882429&amp;sdata=W6p3ItP4f6ZNLYDcybM%2BwYpXXZGkJTg5Rskh%2B0k%2Fsjk%3D&amp;reserved=0 Unsubscribe https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.rootsweb.com%2Fpostorius%2Flists%2Fbk%40rootsweb.com&amp;data=02%7C01%7C%7C17e7440f1c274fee324208d6e0690e05%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636943139136882429&amp;sdata=WcBXZ5Nd9Vd%2BaLVzlTFeCdzyEw58Cb2IdGLJaAs4f4E%3D&amp;reserved=0 Privacy Statement: https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fancstry.me%2F2JWBOdY&amp;data=02%7C01%7C%7C17e7440f1c274fee324208d6e0690e05%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636943139136882429&amp;sdata=gW%2FBRfO6WEWTsOn77qXon0OdBjATOEfJIj1Sc150TYM%3D&amp;reserved=0 Terms and Conditions: https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fancstry.me%2F2HDBym9&amp;data=02%7C01%7C%7C17e7440f1c274fee324208d6e0690e05%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636943139136882429&amp;sdata=ewyEA0UNEAq%2BPbdEB9RATS04XEUP3%2Bs5txWhg8YxWsQ%3D&amp;reserved=0 Rootsweb Blog: https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Frootsweb.blog&amp;data=02%7C01%7C%7C17e7440f1c274fee324208d6e0690e05%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636943139136882429&amp;sdata=RlFPWEzJ4HEB2zr4x9dQ0FshMYiEhwX5dL5Hw3vYsP0%3D&amp;reserved=0 RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community

This is Jeff not Joe. Joe is also having Gedcom problems. I may try the suggestion. > Joe > Do you have an Ancestry account? > If so try uploading it to Ancestry and then downloading a GEDCOM of the > Ancestry file. > Jim > > -----Original Message----- > From: Jeff Stewart <jeff1950(a)gmail.com&gt; > Sent: Friday, May 24, 2019 6:03 PM > To: bk(a)rootsweb.com > Subject: [BK] GEDCOM Validator > > I downloaded and installed Gedcom Valdator from the Microsoft store, I > cleaned the gedcom file and no errors. Gedcom not valid when I upload to > WorldConnectBeta. I got the reply from Rootsweb to keep trying to upload the > file from Kristy. I have used BK to generate the gedcom and never had any > problems uploading to the old Worldconnect. > > _______________________________________________ > Remember - Use the Archives at http://archiver.rootsweb.com/cgi-bin/search > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref Unsubscribe > https://lists.rootsweb.com/postorius/lists/bk@rootsweb.com > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: > https://ancstry.me/2HDBym9 Rootsweb Blog: http://rootsweb.blog RootsWeb is > funded and supported by Ancestry.com and our loyal RootsWeb community

Fran Another error that pops up for me is second marriages, where say a man marries a very young lady and you have her marked as step mother for his children that might be older than her. Also if you have the century wrong on one of the parents it will be a chain reaction for all the children. So one date in the birth date of a parent might create multiple errors. Jim -----Original Message----- From: Barry PYCROFT <barry@pycroft.co.nz> Sent: Saturday, May 25, 2019 12:27 AM To: bk@rootsweb.com Subject: [BK] Re: Reasonable Check Fran I have just tested in the data you sent me. The test is for those event OUTSIDE the reasonable. If you set 30 as a minimum, then zero to thirty is outside that range. And over 50 is the high end. What you might want is those that3 do not appear with a marriage range of 0 to 20, then 0 to 30, then zero to 50 etc. It took me a while to see what was happening since all other tests are reported in the list. It would be helpful if the report could have option for each test. Barry P. -----Original Message----- From: Frances LaChance [mailto:singer.35@hotmail.com] Sent: Saturday, 25 May 2019 11:25 AM To: bk@rootsweb.com Subject: [BK] Reasonable Check Bk 7.3.4 Doing a reasonable check and have set parameters for "Ages difference of spouses" as 15 - 30.   However, I am getting hits for age difference of 2-3 years, which is practically everyone in my database of over 80,000. Am I doing something wrong? Fran _______________________________________________ Remember - Use the Archives at http://archiver.rootsweb.com/cgi-bin/search _______________________________________________ Email preferences: http://bit.ly/rootswebpref Unsubscribe https://lists.rootsweb.com/postorius/lists/bk@rootsweb.com Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: https://ancstry.me/2HDBym9 Rootsweb Blog: http://rootsweb.blog RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community _______________________________________________ Remember - Use the Archives at http://archiver.rootsweb.com/cgi-bin/search _______________________________________________ Email preferences: http://bit.ly/rootswebpref Unsubscribe https://lists.rootsweb.com/postorius/lists/bk@rootsweb.com Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: https://ancstry.me/2HDBym9 Rootsweb Blog: http://rootsweb.blog RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community

I think it is about time we had UTF-16 as an option in addition to the UTF-8 Barry P. -----Original Message----- From: Joe [mailto:joe968@comcast.net] Sent: Saturday, 25 May 2019 9:25 AM To: bk@rootsweb.com Subject: [BK] more GEDCOM errors Another GEDCOM error I am getting is unmapable characters. What is in my files as Dörrenbach ends up D”rrenbach in the gedcom. Does GEDCOM not support the full 256 characters set? Some of my data is cut and paste so may have illegal characters. How can I view the ascii number of the character. Also , how do I find hidden white spaces in the GEDCOM. Thanks for any help. Joe Weiss _______________________________________________ Remember - Use the Archives at http://archiver.rootsweb.com/cgi-bin/search _______________________________________________ Email preferences: http://bit.ly/rootswebpref Unsubscribe https://lists.rootsweb.com/postorius/lists/bk@rootsweb.com Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: https://ancstry.me/2HDBym9 Rootsweb Blog: http://rootsweb.blog RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community

Fran I have just tested in the data you sent me. The test is for those event OUTSIDE the reasonable. If you set 30 as a minimum, then zero to thirty is outside that range. And over 50 is the high end. What you might want is those that3 do not appear with a marriage range of 0 to 20, then 0 to 30, then zero to 50 etc. It took me a while to see what was happening since all other tests are reported in the list. It would be helpful if the report could have option for each test. Barry P. -----Original Message----- From: Frances LaChance [mailto:singer.35@hotmail.com] Sent: Saturday, 25 May 2019 11:25 AM To: bk@rootsweb.com Subject: [BK] Reasonable Check Bk 7.3.4 Doing a reasonable check and have set parameters for "Ages difference of spouses" as 15 - 30.   However, I am getting hits for age difference of 2-3 years, which is practically everyone in my database of over 80,000. Am I doing something wrong? Fran _______________________________________________ Remember - Use the Archives at http://archiver.rootsweb.com/cgi-bin/search _______________________________________________ Email preferences: http://bit.ly/rootswebpref Unsubscribe https://lists.rootsweb.com/postorius/lists/bk@rootsweb.com Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: https://ancstry.me/2HDBym9 Rootsweb Blog: http://rootsweb.blog RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community

I'd be interested to know if WC will accept it.  So if you do try it please let us all know. :-) Fran L On 24/05/2019 7:22 p.m., Jim Dell via BK wrote: > Joe > Do you have an Ancestry account? > If so try uploading it to Ancestry and then downloading a GEDCOM of the > Ancestry file. > Jim > > -----Original Message----- > From: Jeff Stewart <jeff1950@gmail.com> > Sent: Friday, May 24, 2019 6:03 PM > To: bk@rootsweb.com > Subject: [BK] GEDCOM Validator > > I downloaded and installed Gedcom Valdator from the Microsoft store, I > cleaned the gedcom file and no errors. Gedcom not valid when I upload to > WorldConnectBeta. I got the reply from Rootsweb to keep trying to upload the > file from Kristy. I have used BK to generate the gedcom and never had any > problems uploading to the old Worldconnect. > > _______________________________________________ > Remember - Use the Archives at http://archiver.rootsweb.com/cgi-bin/search > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref Unsubscribe > https://lists.rootsweb.com/postorius/lists/bk@rootsweb.com > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: > https://ancstry.me/2HDBym9 Rootsweb Blog: http://rootsweb.blog RootsWeb is > funded and supported by Ancestry.com and our loyal RootsWeb community > > _______________________________________________ > Remember - Use the Archives at http://archiver.rootsweb.com/cgi-bin/search > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref > Unsubscribe https://lists.rootsweb.com/postorius/lists/bk@rootsweb.com > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: https://ancstry.me/2HDBym9 > Rootsweb Blog: http://rootsweb.blog > RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community

Bk 7.3.4 Doing a reasonable check and have set parameters for "Ages difference of spouses" as 15 - 30.   However, I am getting hits for age difference of 2-3 years, which is practically everyone in my database of over 80,000.  Am I doing something wrong? Fran