Jump to content


BillieS

Member Since 03 Sep 2019
Offline Last Active Sep 04 2019 08:05 AM
-----

Posts I've Made

In Topic: Changing fields on import

04 September 2019 - 07:52 AM

Thanks Tom and Jerry.  I think that I'll keep my custom field rather than try to move the several thousand Hebrew names to "alternate name" - at least until I learn how to use SQLite.  That's definitely on my to do list.


In Topic: Changing fields on import

04 September 2019 - 03:06 AM

It looks like I'll have to keep the custom fact as is.


In Topic: Creating gedcom files from text

03 September 2019 - 08:11 AM

I changed the CHAR line to UTF-8  It worked!  THANK YOU! :)

 

The original software is Family Tree Maker 2005. I have a 2nd question, but it's a different topic so I'll send that separately.


In Topic: Creating gedcom files from text

03 September 2019 - 07:27 AM

My gedcom file was produced by a program that does not support Unicode. Despite this, I was able to enter Hebrew letters in one of the fact fields. When I exported the file to gedcom, the Hebrew letters came out in a different (Corsican) alphabet. The change that I had to make was to convert the letters one by one to the correct alphabet. 

I followed Jerry's suggestion using Windows File Explorer. In the original file, I changed the char at the beginning of the gedcom file from ANSI to UNICODE, and then letter by letter, using "replace" changed the Corsican letters into Hebrew, and saved the file. I was able to change the extension from .txt to .ged and import the new file. Sounds good, doesn't it?
When I opened the new file in RootsMagic, what should have been Hebrew text came up in a new form of gibberish! and it added letters. What in Hebrew should be מאיר came out as ×ž×�יר ×–×�ב. Even if you are not familiar with the Hebrew alphabet, you can see that there is a difference. 
What now?
I followed your instructions, and everything worked exactly as you said it would. In the original file, I changed the char at the beginning of the file from ANSI to UNICODE, and then letter by letter changed the Corsican letters into Hebrew, and saved the file. I was able to change the extension from .txt to .ged and import the new file. Sounds good, doesn't it?
When I opened the new file in RootsMagic, what should have been Hebrew text came up in a new form of gibberish! and it added letters. What in Hebrew should be מאיר came out as ×ž×�יר ×–×�ב. Even if you don't know the Hebrew alphabet, you can see that there is a difference.