CORRECTION Big, Big OOps, My last sentence should start “It will not”. *I* do believe that Legacy should support UTF-8, and should have done so for a long time.
Ron Ferguson http://www.fergys.co.uk/ From: Ron Ferguson Sent: Thursday, July 11, 2013 11:00 PM To: [email protected] Subject: Re: [LegacyUG] Helpfile indicates Gedcom 5.5 and UTF-8 are supported in Legacy7, but how do you make them work? Anna, Much to the regret of many of us Legacy does not and never has supported Unicode, no matter how one tries to enter data encoded in that way. I will not, therefore, support the use of the Cyrillic alphabet (or at least the Cyrillic characters. Ron Ferguson http://www.,fergys.co.uk/ From: Anna Kopij Sent: Thursday, July 11, 2013 10:23 PM To: [email protected] Subject: [LegacyUG] Helpfile indicates Gedcom 5.5 and UTF-8 are supported in Legacy7, but how do you make them work? The Legacy7 help file indicates that both of the following should be possible UNICODE if we support Gedcom 5.5 and import of UTF-8 Is there a switch in Legacy to turn Unicode on, the helpfile indicates we support Gedcom 5.5, which UNICODE is included. Is there a switch in Legacy to turn UTF-8 import ON, the helpfile indicates we support UTF-8 imports? I would like to add some Cyrillic names, and either method should allow me to do this? If this is a broke in Ver 7.5 could one of the Beta tests for Ver 8 make sure it's working Here the sections from the Help file followed by an 2 examples of trying to input the Surname "Судя" one via cut and paste and one via import. ****** UNICODE Index->Gedcom->Files $$$$$$ After two internal versions, the first public version of the GEDCOM spec was 3.0 and was released in 1987. In 1993 a new proposal was released and is known as version 5.2. In 1996, version 5.5 was presented as the new standard. Legacy is capable of importing and exporting the formats specified in these versions. $$$$$$ Although it would be great to support UTF-8 which is in the 1999 Gedcom 5.5.1 Draft and also in the December 18 2000 Gedcom 5.6 Draft, How does one get UNICODE to work in Legacy which is in the Gedcom 5.5 standard which the help file implies Gedcom 5.5 is supported? With 16 bit Unicode almost all Languages could be supported by Legacy even if UTF-8 in the 5.5.1 Gedcom draft is not supported. ****** Import of UTF-8 Index->Gedcom->Import Importing a Gedcom $$$$$$ Under "Character Set" In the help section under: *** Character Set Legacy automatically handles the import of various character sets including ANSI, ANSEL, and UTF-8 *** $$$$$$ Examples For example if I import a person with the surname Судя in English this would sound about 95% but not exactly C->S, y->u, д->d, and я-> ia Sudia Copy and paste "Судя" into the Surname appears as 4 question marks "????" Creating a Gedcom with FTM2012 saving as Gedcom 5.5 with UTF-8 with one surname "Судя" produces a Gedcom 0 HEAD 1 SOUR FTM 2 VERS Family Tree Maker (21.0.0.723) 2 NAME Family Tree Maker for Windows 2 CORP Ancestry.com 3 ADDR 360 W 4800 Ni 4 CONT Provo, UT 84604 3 PHON (801) 705-7000 1 DEST GED55 1 DATE 11 JUL 2013 1 CHAR UTF-8 1 FILE D:\ToLegacy_2013-07-11.ged 1 SUBM @SUBM@ 1 GEDC 2 VERS 5.5 2 FORM LINEAGE-LINKED 0 @SUBM@ SUBM 0 @I1@ INDI 1 NAME /Судя/ 1 SEX M 0 TRLR then importing the above gedcom into Legacy7. Before import Legacy detects that Char Set is UTF-8 and dest GEN55 now the Surname "Судя" appears as "СудÑ" in Legacy. Date: 07/11/13 Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
