Family Historian User Group

Hi,

I'm evaluation FH 3.1 and started by importing a gedcom file, but all non-English characters are transalated into garbage charaters.

Thanks
Erik

ID:3437

Currently FH does not support UniCode.

It is on the wish list, but is not a very popular request. see

http://www.fhug.org.uk/wishlist/wldispl ... lwlref=129

Hi Jane,

Thanks for your answer. The lack of Unicode support is rather disappointing and unexpected of a upcoming and awarded product like FH, and effectively blocks its use in most of the world, i.e. outside native English speaking countries. But that your choise ....

Regards
Erik

Its not only the non-English speaking countries. In these days of easy travelling its not uncommon to have quite a few immigrations and emmigrations in your tree so its quite likely for there to be relatives with names involving umlates (sp?) and so on. UK users will likely have european relatives, American users will have relatives from all over the world.

Considering that Windows XP and Vista are Unicode by default it means that FH is going out of it's way to stay ASCII only.

Even without unicode support, it still is possible to include a great many foreign characters using the ASCII Extended Character Set.

Your chart is useful as a stop gap till FH supports Unicode, but it still doesn't solve the problem with Ascii.

Using Ascii means it still depends on which code page you are using as to which character you actually get. So character 128 in your table is c-cedilla, but in code pages 862 (hebrew), 737 (Greek), and 775 (Estonia), it isn't. This is just one example. There are a few characters that are the same across all code pages in the extended section, but the point is that there is no guarantee that the user you are sending your Gedcom file to has the same ASCII code page installed on their PC. It all depends on what language setting they have.