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
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
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&data=02%7C01%7C%7C90dcda07d2c345f8a7cb08d6e0c9d81a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636943554848156647&sdata=pxGYrfp14ASlUbGW6bXPXi3uYGafXjQ5kbUWDyez0eU%3D&reserved=0 _______________________________________________ Email preferences: https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fbit.ly%2Frootswebpref&data=02%7C01%7C%7C90dcda07d2c345f8a7cb08d6e0c9d81a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636943554848156647&sdata=S%2Frp7po3NgXotZLMVGNj4IDB4O3wnUqtO25VPZesVJk%3D&reserved=0 Unsubscribe https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.rootsweb.com%2Fpostorius%2Flists%2Fbk%40rootsweb.com&data=02%7C01%7C%7C90dcda07d2c345f8a7cb08d6e0c9d81a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636943554848156647&sdata=kuIU%2FVEy1ofFIdhRgnwyV%2FiOv4w4D2QEfQ86q1ZbE%2Fw%3D&reserved=0 Privacy Statement: https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fancstry.me%2F2JWBOdY&data=02%7C01%7C%7C90dcda07d2c345f8a7cb08d6e0c9d81a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636943554848156647&sdata=D3ZHrTOsYKgSlnDQqfhnJH%2F1Q4nxwNNa6pvb%2Buiye2U%3D&reserved=0 Terms and Conditions: https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fancstry.me%2F2HDBym9&data=02%7C01%7C%7C90dcda07d2c345f8a7cb08d6e0c9d81a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636943554848166658&sdata=070dx3JGiSxmjZmnoSBNW%2FullXxgYwDVtEePjuNG0lY%3D&reserved=0 Rootsweb Blog: https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Frootsweb.blog&data=02%7C01%7C%7C90dcda07d2c345f8a7cb08d6e0c9d81a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636943554848166658&sdata=4TS4LVAAUYqQco409y6opXZGThzLWLNbl3DP9EE3nEc%3D&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&data=02%7C01%7C%7C90dcda07d2c345f8a7cb08d6e0c9d81a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636943554848166658&sdata=satEuIj1FY%2BAVoV1gssFLDVyC21cvELbU2loPuJKimM%3D&reserved=0 _______________________________________________ Email preferences: https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fbit.ly%2Frootswebpref&data=02%7C01%7C%7C90dcda07d2c345f8a7cb08d6e0c9d81a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636943554848166658&sdata=Khl9qQRdJOpgz956qAgBkn9jzj%2BiukpngBYa%2BwPq9bA%3D&reserved=0 Unsubscribe https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.rootsweb.com%2Fpostorius%2Flists%2Fbk%40rootsweb.com&data=02%7C01%7C%7C90dcda07d2c345f8a7cb08d6e0c9d81a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636943554848166658&sdata=gmXnuCxPgbBCk9VLy77efaxvOTYgu%2Fl54ksuNN7MeR4%3D&reserved=0 Privacy Statement: https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fancstry.me%2F2JWBOdY&data=02%7C01%7C%7C90dcda07d2c345f8a7cb08d6e0c9d81a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636943554848166658&sdata=NdUY%2F58J5XR7pIafEXxxUrMdLpvsfMQAytrKyV9%2F8Uo%3D&reserved=0 Terms and Conditions: https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fancstry.me%2F2HDBym9&data=02%7C01%7C%7C90dcda07d2c345f8a7cb08d6e0c9d81a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636943554848166658&sdata=070dx3JGiSxmjZmnoSBNW%2FullXxgYwDVtEePjuNG0lY%3D&reserved=0 Rootsweb Blog: https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Frootsweb.blog&data=02%7C01%7C%7C90dcda07d2c345f8a7cb08d6e0c9d81a%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636943554848166658&sdata=4TS4LVAAUYqQco409y6opXZGThzLWLNbl3DP9EE3nEc%3D&reserved=0 RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community
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 > > _______________________________________________ >
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