We not live so long.  They have told us they would have to totally rewrite the 
whole program, which isn't going to happen in my lifetime, at least.
CE
From: [email protected]
To: [email protected]
Subject: RE: [LegacyUG] UTF-8 Polish, Slovak, Ukranian, non-English characters
Date: Mon, 12 Mar 2012 11:19:31 -0500



A better question is when/if Legacy will add these sets.  Marianne

-----Original Message-----

From: Michele Lewis

Sent: Mar 12, 2012 8:13 AM

To: [email protected]

Subject: RE: [LegacyUG] UTF-8 Polish, Slovak, Ukranian, non-English characters



Good grief!  I am nowhere near computer savvy enough to do all of that!  I 
think I will just wait until Legacy adds the alphabet set! michele From: John 
Magyari [mailto:[email protected]]
Sent: Monday, March 12, 2012 8:55 AM
To: [email protected]
Subject: Re: [LegacyUG] UTF-8 Polish, Slovak, Ukranian, non-English characters 
After reading Michele's comment about Polish Characters I tried the following:

In Legacy I tried to use Ukrainian, Polish and Slovak letters and I could 
figure out how to enter them.

I exported a UTF-8 Gedcom 5.5.1 file with 4 people in Legacy an English person 
whose father was Ukrainian whose father was Polish whose father was Slovak used 
all english characters for names..

I then edited created Gedcom file with notepad and added Cyrillic, Polish and 
Slovak characters to the appropriate person's name.

I then imported into Genbox, FTM2012 both imported gedcom no errors and were 
able to create charts with all characters.

I then imported into Legacy did not see any error messages,  non-English 
characters were not displayed correctly.

Names stored in fdb tables IR, MR, NR and NX appeared as they do in Legacy but 
not like they do in the Gedcom,

Legacy export mentions UTF-8 and Ansel which both should support Polish, Slovak 
and Ukrainian (Cyrillic) characters.

Here's the gedcom

0 HEAD
1 SOUR Legacy
2 VERS 7.5
2 NAME Legacy (R)
2 CORP Millennia Corp.
3 ADDR PO Box 9410
4 CONT Surprise, AZ 85374
1 DEST Gedcom5.5.1
1 DATE 12 Mar 2012
1 SUBM @S0@
1 FILE R:\Program Files\Legacy\Data\UTF8.ged
1 GEDC
2 VERS 5.5.1
2 FORM LINEAGE-LINKED
1 CHAR UTF-8
0 @S0@ SUBM
1 NAME John Magyari
0 @I1@ INDI
1 NAME English /E2/
2 GIVN English
2 SURN E2
1 SEX M
1 _UID D2E6041F943745EFA4B75A476B01DDE302B7
1 CHAN
2 DATE 12 Mar 2012
3 TIME 05:03
1 FAMC @F3@
0 @I2@ INDI
1 NAME Ukrainian /U2лджє/
2 GIVN Ukrainian
2 SURN U2лджє
1 SEX M
1 _UID E4BF8AAB39B34493BAC6D52004B69B056A21
1 CHAN
2 DATE 12 Mar 2012
3 TIME 05:03
1 FAMS @F3@
1 FAMC @F1@
0 @I3@ INDI
1 NAME Polish /P2żśłą/
2 GIVN Polish
2 SURN P2żśłą
1 SEX M
1 _UID 69BD6EF9F49C4624BCE63281EAA9DF4896F4
1 CHAN
2 DATE 12 Mar 2012
3 TIME 05:03
1 FAMS @F1@
1 FAMC @F2@
0 @I4@ INDI
1 NAME Slovak /S2ôúäň/
2 GIVN Slovak
2 SURN S2ôúäň
1 SEX M
1 _UID CF781FD94CA144F6B6496BDE23C5458C67F0
1 CHAN
2 DATE 12 Mar 2012
3 TIME 05:03
1 FAMS @F2@
0 @F1@ FAM
1 HUSB @I3@
1 MARR
1 CHIL @I2@
1 CHAN
2 DATE 12 Mar 2012
3 TIME 05:03
0 @F2@ FAM
1 HUSB @I4@
1 MARR
1 CHIL @I3@
1 CHAN
2 DATE 12 Mar 2012
3 TIME 05:03
0 @F3@ FAM
1 HUSB @I2@
1 MARR
1 CHIL @I1@
1 CHAN
2 DATE 12 Mar 2012
3 TIME 05:03
0 TRLR





On 3/11/2012 5:19 AM, Michele Lewis wrote: Speaking of Polish locations…  Be 
aware that Legacy does not include the needed alphabet set to be able to write 
the Polish characters. Michele From: John Magyari [mailto:[email protected]]
Sent: Sunday, March 11, 2012 8:08 AM
To: [email protected]
Subject: Re: [LegacyUG] How to document Locations in Europe 5 Fields vs 4 
Fields Thanks for everyone's ideas.
Some of my Polish time periods use 4 some 5 positions

I decided to force all 5 location positions into 4.  Having same number of 
fields helps with sorting.

Ideally if would be nice to specify Number of locations field MAX.  Then if 
entered with less fields specify which fields to become null.
ie. MaxPositions = 5,  LessPositionOrder if less 2,3if less than MAX
ie For Me for Poland
city, administration, county, state, country (1,2,3,4,5)
If less fields entered enter Nulls
city, county, state, country (Null 1 field - admin)
city, state, country (Null other 2 fields -admin, county)
city, state (Null other 3 fields)
state (Null other 4 fields)


I will use 4 fields, and in the process converted all locations with fewer 
positions to 4 position system.

john







On 3/11/2012 4:04 AM, Ron Ferguson wrote: John, By all means use the 
American four field standard for American locations, but for other countries 
use their own formats, normally the way in which they are written. Ron 
Fergusonhttp://www.fergys.co.uk/  From: John Magyari Sent: Thursday, 
March 08, 2012 7:35 PMTo: [email protected] Subject: [LegacyUG] 
How to document Locations in Europe 5 Fields vs 4 Fields Typically for US 
locations i have ****4 FIELDS
City, County, State, Country

How do others handle European Countries?

For example I have a village in Poland Area

1900's part of Austria Hungary

Village, District, Province, Country ****4 FIELDS
Lipowiec, Sanok District, Galicia Province, Austria-Hungary

Same place in 1940's ****4 FIELDS
Lipowiec, Sanok District, Krosno Voivodeship, Poland

Almost all places in Current Day Poland 1950's through today *****5 FIELDS
City, Gmina, County, Voivodeship, COUNTRY
Lipowiec, Dukla Gmina, Krosno County, Subcarpathian Voivodeship, Poland

and since 2012 *****5 Fields
Lipowiec, Jasliska Gmina, Krosno County, Subcarpathian Voivodeship, Poland

When some locations ideally be 5 FIELDS, do you go back and update those with 4 
Fields?

With some having 4 some having 5 it's also harder sorting and then viewing 
similar towns over time periods.

thanks,
john magyari

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

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

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

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


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





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



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

Reply via email to