Considering the length of time 5.5.1 has been available, if a program doesn't already support it the odds are, imho, it never will. -----Original Message----- From: Shmuel (Seymour J.) Metz <spamtrap@library.lspace.org.invalid> To: gencmp <gencmp@rootsweb.com> Sent: Wed, Feb 27, 2013 11:55 pm Subject: Re: Whither GEDCOM? In <512e34c5.4820774@news.eternal-september.org>, on 02/27/2013 at 04:37 PM, Eagle@bellsouth.net (J. Hugh Sullivan) said: >Seems to me the problem has recently been discussed here. Users >demand unique abilities in programs and developers try to satisfy. >Even for an accomplished programmer methinks it would be very >difficult to accomodate every variation even with options. The draft GEDCOM 5.5.1 already supports the features I mentioned, but a lot of software doesn't support it yet. -- Shmuel (Seymour J.) Metz, SysProg and JOAT <http://patriot.net/~shmuel> Unsolicited bulk E-mail subject to legal action. I reserve the right to publicly post or ridicule any abusive E-mail. Reply to domain Patriot dot net user shmuel+news to contact me. Do not reply to spamtrap@library.lspace.org ------------------------------- To unsubscribe from the list, please send an email to GENCMP-request@rootsweb.com with the word 'unsubscribe' without the quotes in the subject and the body of the message

On onsdag 2013-02-27 22:34, J. Hugh Sullivan wrote: > On Wed, 27 Feb 2013 13:48:18 -0600, Charlie Hoffpauir > <invalid@invalid.com> wrote: > >> On Wed, 27 Feb 2013 10:32:34 -0800 (GMT-08:00), Susan Goldsmith >> <jcwsmg@sprintmail.com> wrote: >> >>> Dear Members, >>> >>> What are the pros and cons of My Heritage v Family Tree Maker software? Which software do you prefer and why? >>> >>> Is there a way to synch the data I have in My Heritage software with the data I have in Family Tree Maker software? (Not having decided which software to settle on, I have made the mistake of updating some information in one software, some in the other). >>> >>> Thank you. >>> Best Regards, >>> S Goldsmith >>> >>> >> You really need to consider other choices. Look at Legacy, RootsMagic, >> and PAF. Most are either free or have free versions available for >> trial. You should explore all and then select the one you like best. >> As you can see from another thread in this group, changing your data >>from one program to another is a real pain. > > I agree with trying RM and Legacy at the minimum. IMO they are > unequalled except by TMG which has a steep learning curve (again IMO). > > FTM has a lot of supporters. I am happy not to be one of them. > > Hugh > I am a user of FTM since its DOS-time. But I stopped upgrading and I am happy using FTM 2006. I prefer to keep all information in my own system and not in any form of cloud. I am not storing any pictures in the FTM-database. I can´t see the advantage. I have looked at most of the other genealogy programs but stayed with a program where I can concentrate on the research instead of finding out HOW to do different tasks. I´m using GreatFamily to produce web-pages and The Complete Genealogy Reporter to produce reports to interested relatives. But, of course, I am used to edit the gedcom-file to overcome some of the strange habits of FTM. BTW, I am a Swede and have most of my relatives here, but I am sticking to English in my system. I am getting puzzled with all different translations to Swedish I have seen in different programs. FTM handles the Swedish "funny" letters without any problem. My largest complain is that it is impossible to get the dates according to ISO-standard, YYYY-MM-DD. The closest FTM offers is DD-MM-YYYY. Kurt F

In <512e34c5.4820774@news.eternal-september.org>, on 02/27/2013 at 04:37 PM, Eagle@bellsouth.net (J. Hugh Sullivan) said: >Seems to me the problem has recently been discussed here. Users >demand unique abilities in programs and developers try to satisfy. >Even for an accomplished programmer methinks it would be very >difficult to accomodate every variation even with options. The draft GEDCOM 5.5.1 already supports the features I mentioned, but a lot of software doesn't support it yet. -- Shmuel (Seymour J.) Metz, SysProg and JOAT <http://patriot.net/~shmuel> Unsolicited bulk E-mail subject to legal action. I reserve the right to publicly post or ridicule any abusive E-mail. Reply to domain Patriot dot net user shmuel+news to contact me. Do not reply to spamtrap@library.lspace.org

In <mpro.mivsln1d7akow0095.tim@powys.org>, on 02/27/2013 at 01:39 PM, Tim Powys-Lybbe <tim@powys.org> said: >My opinion is a zilch prognosis. The problem with GEDCOM is that it >makes it relatively easy to transfer a lot of the data between >genealogy programs. But for the programmer this is not Good News; >how much better to lock the user into their program by making >GEDCOM transfers more difficult? In my experience, deliberate lock-in is something that programmers do only when ordered to by management. >Yo might get more mileage by asking your current program owners >when _They_ are going to provide the above features. My current program has a scripting facility; it is easy to generate whatever format I want. The problem is that I want to be able to share my data, and until at least GEDCOM 5.5.1 is ubiquitous, there's no universal format that will handle my data. -- Shmuel (Seymour J.) Metz, SysProg and JOAT <http://patriot.net/~shmuel> Unsolicited bulk E-mail subject to legal action. I reserve the right to publicly post or ridicule any abusive E-mail. Reply to domain Patriot dot net user shmuel+news to contact me. Do not reply to spamtrap@library.lspace.org

On Wed, 27 Feb 2013 13:48:18 -0600, Charlie Hoffpauir <invalid@invalid.com> wrote: >On Wed, 27 Feb 2013 10:32:34 -0800 (GMT-08:00), Susan Goldsmith ><jcwsmg@sprintmail.com> wrote: > >>Dear Members, >> >> What are the pros and cons of My Heritage v Family Tree Maker software? Which software do you prefer and why? >> >> Is there a way to synch the data I have in My Heritage software with the data I have in Family Tree Maker software? (Not having decided which software to settle on, I have made the mistake of updating some information in one software, some in the other). >> >> Thank you. >> Best Regards, >> S Goldsmith >> >> >You really need to consider other choices. Look at Legacy, RootsMagic, >and PAF. Most are either free or have free versions available for >trial. You should explore all and then select the one you like best. >As you can see from another thread in this group, changing your data >from one program to another is a real pain. I agree with trying RM and Legacy at the minimum. IMO they are unequalled except by TMG which has a steep learning curve (again IMO). FTM has a lot of supporters. I am happy not to be one of them. Hugh

On Wed, 27 Feb 2013 15:20:44 -0500, singhals <singhals@erols.com> wrote: >>> Still -- Hugh -- If you haven't already, does Legacy let you >>> do case-sensitive? If so then pick that and do a Find: "H >>> Replace: (H and then a FIND: h" Replace: h) >>> >>> Cheryl >> >> >> I don't know enough about Legacy to test various types of GEDCOMS, I >> just went with the default, and as the responder on the Legacy user >> group advised, putting a name within quotes gave me the NICK in the >> export. Apparently this is what Hugh is getting also. >> >> As to the last comment, the point is that "Hugh" is just an example. >> In reality, the name to be altered from "Hugh" to (Hugh) is really >> "any" name. >> > >True enough, but what you want to find doesn't matter to the >technique? > >C Merci to Cheryl and Charles for babysitting me. Now I'll go slip into something comfortable like a Cuba Libre. Hugh

Charlie Hoffpauir wrote: > On Wed, 27 Feb 2013 15:20:44 -0500, singhals<singhals@erols.com> > wrote: > >> Charlie Hoffpauir wrote: >>> On Wed, 27 Feb 2013 13:33:10 -0500, singhals<singhals@erols.com> >>> wrote: >>> >>>> Charlie Hoffpauir wrote: >>>>> On Tue, 26 Feb 2013 20:07:06 -0500, singhals<singhals@erols.com> >>>>> wrote: >>>>> >>>>> <snip> >>>>>> I'm gonna take your word for it that when you export you get >>>>>> a "NICK" field. I can't make Legacy or RM put that field >>>>>> into the GED. I generated an RM GED (it didn't give me any >>>>>> options about my target), and 4 from Legacy. None of them >>>>>> had "NICK" when I looked. >>>>>> >>>>>>> If RM had the same Family Navigation Screen as Legacy I would switch >>>>>>> back. But I'm a creature of habit. Where is that Fountain of Youth? >>>>>> >>>>>> Just past the Free Lunch Counter. ;) >>>>>> >>>>>> Cheryl >>>>> >>>>> I tested this on the free version I downloaded, and if I put a given >>>>> name within quote marks, it is indeed put into a field labeled "NICK". >>>>> I found nothing in any Legacy documentation referring to this, but a >>>>> response posted in a Legacy user group indicated that this was the >>>>> practice. BTW, it also shows the name with quote marks in the NAME >>>>> field. Example below: >>>>> >>>>> 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 Legacy >>>>> 1 DATE 27 Feb 2013 >>>>> 1 SUBM @S0@ >>>>> 1 FILE G:\RootsMagic\GEDCOMS\Example.ged >>>>> 1 GEDC >>>>> 2 VERS 5.5.1 >>>>> 2 FORM LINEAGE-LINKED >>>>> 1 CHAR ANSEL >>>>> 0 @S0@ SUBM >>>>> 1 NAME Not Given >>>>> 0 @I31540@ INDI >>>>> 1 NAME Charles Richard "Dicky" /Hoffpauir/ >>>>> 2 GIVN Charles Richard "Dicky" >>>>> 2 SURN Hoffpauir >>>>> 2 NICK Dicky >>>>> 1 SEX M >>>>> 1 BIRT >>>>> 2 DATE 15 Oct 1939 >>>>> 1 _UID DC7C5732B78C4F388EBFC9274C420EE1650B >>>>> 1 CHAN >>>>> 2 DATE 27 Feb 2013 >>>>> 3 TIME 08:36 >>>>> 0 @I31541@ INDI >>>>> 1 NAME Jerry 'Lynn' /Hoffpauir/ >>>>> 2 GIVN Jerry 'Lynn' >>>>> 2 SURN Hoffpauir >>>>> 1 SEX M >>>>> 1 _UID F025847F04784538B6E815A6089FC80DE636 >>>>> 1 CHAN >>>>> 2 DATE 24 Feb 2013 >>>>> 3 TIME 09:13 >>>>> 0 @I31542@ INDI >>>>> 1 NAME Luther "Francis" /Hoffpauir/ >>>>> 2 GIVN Luther "Francis" >>>>> 2 SURN Hoffpauir >>>>> 2 NICK Francis >>>>> 1 SEX M >>>>> 1 _UID 1082D24D2C144E60A966605DCEB75FBB0A54 >>>>> 1 CHAN >>>>> 2 DATE 24 Feb 2013 >>>>> 3 TIME 09:13 >>>>> 0 TRLR >>>> >>>> >>>> Using a db I had handy at the FHC and Legacy7.5, I added >>>> "Tom" and (Tom) as an Alternate name to one Thomas >>>> Swearingen, and then created 4 GEDs: Legacy-to-Legacy; >>>> Legacy-to-GED5.5.1; Legacy-to-basic-GED; and Legacy-to-PAF5 >>>> Omitted from this is the Legacy to Basic GED one. >>>> >>> >>> Just wondering, why as an alternate name? What Hugh is looking at is >>> typically someone with the given names Luther Francis, who is called >>> Francis, and so usually signs L. Francis. Hugh wants to make it clear >>> that the program and anyone looking at it knows that person should be >>> known as Francis, rather than Luther, and so enters the name as Luther >>> "Francis". there's no need to use the alternate name field at all. >> >> Operating hypothesis was that if the GED was going to show >> NICK it would come from a field identified that way. >> Alt-Name was the nearest option. And, that's what it >> /sounded/ as if the HELP files were saying to do. OTOH, >> perhaps I was meant to understand that alt-name is where a >> woman's married name is to go. >> > Yeah, I had thoughts along the same line. I'm surprised there isn't a > field somewhere on the entry screen simply labeled Nickname, or at > least some comment on how to enter a nickname. I did a search on the > help file for "Nickname" and all I got was a list of nicknames and the > actual names that they might represent. I doubt that the programmer > intends the woman's married name there because there was a comment > that Legacy will accept an unlimited number of alternate names. Yeah, I saw that list too. Unhelpful was my thought, but I sort tossed in the Benefit of the Doubt, figuring maybe it was unhelpful because it wasn't what I needed? Alt-Name, OTOH, I'm always juberous when someone wants me to believe that John Hughes Smith and Jeremiah S. Oberoi are the same man, y'know? EVEN if I stipulate that John and Jeremiah both begin with an S ... [Note to non-US-Southerners: juberous = dubious with prejudice.] >> >>>> Out of Legacy TO Legacy: >>>> 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 Legacy >>>> 1 DATE 26 Feb 2013 >>>> 1 SUBM @S0@ >>>> 1 FILE E:\hhsbook\legacy.ged >>>> 1 GEDC >>>> 2 VERS 5.5.1 >>>> 2 FORM LINEAGE-LINKED >>>> 1 CHAR ANSEL >>>> 0 @S0@ SUBM >>>> 1 NAME Not Given >>>> 0 @I1@ INDI >>>> 1 NAME Thomas /Swearingen/ >>>> 2 GIVN Thomas >>>> 2 SURN Swearingen >>>> 1 NAME "Tom" // >>>> 2 GIVN "Tom" >>>> 2 SURN >>>> 1 NAME (Tom) // >>>> 2 GIVN (Tom) >>>> 2 SURN >>>> 1 NAME 'Tom' // >>>> 2 GIVN 'Tom' >>>> 2 SURN >>>> 1 SEX M >>>> 1 BIRT >>>> 2 DATE 1688 >>>> 2 PLAC Md >>>> 2 SOUR @S2@ >>>> 1 DEAT Y >>>> 1 _UID BBE139991522481FAFC4589C6E7BE324631E >>>> 1 CHAN >>>> 2 DATE 26 Feb 2013 >>>> 3 TIME 13:36 >>>> 1 FAMS @F1@ >>>> >>>> **** >>>> Out of Legacy to GED 5.5.1; >>>> >>>> 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 26 Feb 2013 >>>> 1 SUBM @S0@ >>>> 1 FILE E:\hhsbook\5.5ged.ged >>>> 1 GEDC >>>> 2 VERS 5.5.1 >>>> 2 FORM LINEAGE-LINKED >>>> 1 CHAR ANSEL >>>> 0 @S0@ SUBM >>>> 1 NAME Not Given >>>> 0 @I1@ INDI >>>> 1 NAME Thomas /Swearingen/ >>>> 2 GIVN Thomas >>>> 2 SURN Swearingen >>>> 1 NAME "Tom" // >>>> 2 GIVN "Tom" >>>> 2 SURN >>>> 1 NAME (Tom) // >>>> 2 GIVN (Tom) >>>> 2 SURN >>>> 1 NAME 'Tom' // >>>> 2 GIVN 'Tom' >>>> 2 SURN >>>> 1 SEX M >>>> 1 BIRT >>>> 2 DATE 1688 >>>> 2 PLAC Md >>>> 2 SOUR @S2@ >>>> 1 DEAT Y >>>> 1 _UID BBE139991522481FAFC4589C6E7BE324631E >>>> 1 CHAN >>>> 2 DATE 26 Feb 2013 >>>> 3 TIME 13:36 >>>> 1 FAMS @F1@ >>>> *** >>>> >>>> Out of Legacy to PAF 5.x: >>>> 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 PAF5 >>>> 1 DATE 26 Feb 2013 >>>> 1 SUBM @S0@ >>>> 1 FILE E:\hhsbook\paf5.ged >>>> 1 GEDC >>>> 2 VERS 5.5.1 >>>> 2 FORM LINEAGE-LINKED >>>> 1 CHAR UTF-8 >>>> 0 @S0@ SUBM >>>> 1 NAME Not Given >>>> 0 @I1@ INDI >>>> 1 NAME Thomas /Swearingen/ >>>> 2 GIVN Thomas >>>> 2 SURN Swearingen >>>> 2 _AKA "Tom" // or (Tom) // or 'Tom' // >>>> 1 SEX M >>>> 1 BIRT >>>> 2 DATE 1688 >>>> 2 PLAC Md >>>> 2 SOUR @S2@ >>>> 1 DEAT Y >>>> 1 _UID BBE139991522481FAFC4589C6E7BE324631E >>>> 1 CHAN >>>> 2 DATE 26 Feb 2013 >>>> 3 TIME 13:36 >>>> 1 FAMS @F1@ >>>> 0 @I2@ INDI >>>> 1 NAME Lydia /Riley/ >>>> 2 GIVN Lydia >>>> 2 SURN Riley >>>> 2 SOUR @S34@ >>>> 1 SEX F >>>> 1 BIRT >>>> 2 DATE 1691 >>>> 2 SOUR @S2@ >>>> 1 DEAT >>>> 2 DATE 1764 >>>> 1 _UID C6E486BFCC2A4B16A1481566C65678609EBB >>>> 1 CHAN >>>> 2 DATE 5 Feb 2013 >>>> 3 TIME 13:49 >>>> 1 FAMS @F1@ >>>> >>>> I then opened the same file with RM. So far as I could >>>> determine, the RM version available at the Family History >>>> Centers *has* no options, you either export a .ged or you >>>> don't -- I didn't even see a way to restrict how much of the >>>> file I wanted exported; probably a user-error there. >>>> >>> >>> Bruce has in the past said somthing to the effect that RM strickly >>> adhears to the GEDCOM spec.... so I guess that means that there ARE no >>> options. Like Legacy, after you decide to export a GEDOM you can (by >>> default) export the entire database, or in RM select from a list.... >>> where there are many options. >> >> It's hard to see how anything can actually adhere to the >> spec, because it several places it contradicts itself, but >> OK; still, I'd think it would let me SAY whether I wished to >> include ALL spouses or only direct-line ancestors. I did >> managed to pick a few to export, but for something larger >> than a 5-man sample, way too much manual effort. >> >> > Well, there is a bit of a learning cruve with using the selection > criteria, but it does work quite well and is really quite flexible. > Learning curbes are one thing, but I didn't see anything /to/ be learned ... >>>> However, RM to Ged: >>>> 0 HEAD >>>> 1 SOUR RootsMagic >>>> 2 NAME RootsMagic >>>> 2 VERS 6.0 >>>> 2 CORP RootsMagic, Inc. >>>> 3 ADDR PO Box 495 >>>> 4 CONT Springville, UT 84663 >>>> 4 CONT USA >>>> 3 PHON 1-800-ROOTSMAGIC >>>> 3 WWW www.RootsMagic.com >>>> 1 DEST RootsMagic >>>> 1 DATE 26 FEB 2013 >>>> 1 FILE RM_.ged >>>> 1 GEDC >>>> 2 VERS 5.5.1 >>>> 2 FORM LINEAGE-LINKED >>>> 1 CHAR UTF-8 >>>> 0 @I1@ INDI >>>> 1 NAME Thomas /Swearingen/ >>>> 2 GIVN Thomas >>>> 2 SURN Swearingen >>>> 1 NAME "Tom" // >>>> 2 GIVN "Tom" >>>> 1 NAME (Tom) // >>>> 2 GIVN (Tom) >>>> 1 NAME 'Tom' // >>>> 2 GIVN 'Tom' >>>> 1 SEX M >>>> 1 _UID CD0DA454E12248949954482C7D550E6A5CEE >>>> 1 CHAN >>>> 2 DATE 26 FEB 2013 >>>> 1 BIRT >>>> 2 _PRIM Y >>>> 2 DATE 1688 >>>> 2 PLAC Md >>>> 2 SOUR @S2@ >>>> 3 _TMPLT >>>> 4 FIELD >>>> 5 NAME Page >>>> 1 DEAT Y >>>> 1 FAMS @F1@ >>>> >>>> *** >>>> >>>> No NICK in sight. >>>> >>>> [shrug] As my mechanic often says, if I can't replicate it, >>>> I can't fix it. (g) >>>> >>>> Still -- Hugh -- If you haven't already, does Legacy let you >>>> do case-sensitive? If so then pick that and do a Find: "H >>>> Replace: (H and then a FIND: h" Replace: h) >>>> >>>> Cheryl >>> >>> >>> I don't know enough about Legacy to test various types of GEDCOMS, I >>> just went with the default, and as the responder on the Legacy user >>> group advised, putting a name within quotes gave me the NICK in the >>> export. Apparently this is what Hugh is getting also. >>> Yes, tried again, following instructions, ;^) and got the same. Cheryl >>> As to the last comment, the point is that "Hugh" is just an example. >>> In reality, the name to be altered from "Hugh" to (Hugh) is really >>> "any" name. >>> >> >> True enough, but what you want to find doesn't matter to the >> technique? >> >> C > > Correct, because what you want to "find" is anything between certain > characters. and what you want to do is replace that (whatever it is) > with the same thing between different characters. So programmatically, > you do the search first for lines containing the GEDCOM field NAME > then save the contents of each field to variables, then replace the > quote marks with something else, and write the variables back into the > correct places in the line. Or something like that. > > As I mentioned, I was rather surprised with how long it took (several > minutes) and the first few times I tried it, I was convinced that it > had crashed. This was on a GEDCOM of my data, that had only a few > instances of quote marks that I had added just to test the process. > Apparently what the procedure does is process every line, whether it > has quote marks or not, and that's why it runs rather slow. And quite > possibly it is writing the entire file out every time it makes a > correction..... I don't know enough about Powershell processing to > really know the nuts and bolts of what is going on.

On Wed, 27 Feb 2013 19:16:22 -0600, Charlie Hoffpauir <invalid@invalid.com> wrote: >On Wed, 27 Feb 2013 19:50:34 -0500, singhals <singhals@erols.com> >wrote: > ><Much snipped> >>>> It's hard to see how anything can actually adhere to the >>>> spec, because it several places it contradicts itself, but >>>> OK; still, I'd think it would let me SAY whether I wished to >>>> include ALL spouses or only direct-line ancestors. I did >>>> managed to pick a few to export, but for something larger >>>> than a 5-man sample, way too much manual effort. >>>> >>>> >>> Well, there is a bit of a learning cruve with using the selection >>> criteria, but it does work quite well and is really quite flexible. >>> >> >>Learning curbes are one thing, but I didn't see anything >>/to/ be learned ... >> > >File/Export >(People to export)Click then select and click on "Select from list" >In the window that opens, browse or type in the name of the person you >want to start the gedcom on, for me that's usually myself. >With that person highlighted , click on the tab that says "Mark Group" >Select one of the options, say descendants, then select whether you >want spouses, direct only, etc and for how many generations and click >OK > >Now, those people are all marked for export.... but don't stop there. >You can repeat those steps and continue marking additional people >again clicking the "Mark group" tab and selecting different options >until you get everyone you want included. >As I said, it's a bit complicated, but enables a very selective >export, and once familiar withthe process, it goes very fast. > >That's the basic process. There's also an "UNMARK GROUP" tab where I >think you could first select everyone, and then selectively "exclude" >people, but I've never used that. As an interesting aside, using Hugh's database, one could export ONLY those people for which he had put a given name in quote marks. After the select from a list choice, then mark Group, Select people by data fields, then in the search box put Given or Nickname contains ". (I'll bet you can't do that with PAF)

On Wed, 27 Feb 2013 13:39:23 +0000, Tim Powys-Lybbe <tim@powys.org> wrote: >On 27 Feb at 11:50, Shmuel (Seymour J.) Metz ><spamtrap@library.lspace.org.invalid> wrote: > >> I've seen a lot of references to really old versions of GEDCOM. GEDCOM >> 5.5.1 seems to satisfy my immediate needs[1], but has been in draft >> status for a very long time. GEDCOM 6 is still a work in progress and >> I'm not sure where GEDCOM-X is. What is the prognosis for the major >> players to support at least GEDCOM 5.5.1 in UTF-8? >> >> [1] E.g., storing both a secular and a religous name, storing a >> romanized transliteration of a name in a non-roman script, >> storing a date in two different calendars. > >My opinion is a zilch prognosis. The problem with GEDCOM is that it >makes it relatively easy to transfer a lot of the data between genealogy >programs. But for the programmer this is not Good News; how much better >to lock the user into their program by making GEDCOM transfers more >difficult? Which is not good news for users, because when the programmer dies, their data is as good as dead. And as soon as the news got around, nobody would touch their program with a bargepole. -- Steve Hayes from Tshwane, South Africa Blog: http://khanya.wordpress.com E-mail - see web page, or parse: shayes at dunelm full stop org full stop uk

J. Hugh Sullivan wrote: > On Wed, 27 Feb 2013 15:20:44 -0500, singhals<singhals@erols.com> > wrote: > >>>> Still -- Hugh -- If you haven't already, does Legacy let you >>>> do case-sensitive? If so then pick that and do a Find: "H >>>> Replace: (H and then a FIND: h" Replace: h) >>>> >>>> Cheryl >>> >>> >>> I don't know enough about Legacy to test various types of GEDCOMS, I >>> just went with the default, and as the responder on the Legacy user >>> group advised, putting a name within quotes gave me the NICK in the >>> export. Apparently this is what Hugh is getting also. >>> >>> As to the last comment, the point is that "Hugh" is just an example. >>> In reality, the name to be altered from "Hugh" to (Hugh) is really >>> "any" name. >>> >> >> True enough, but what you want to find doesn't matter to the >> technique? >> >> C > > Merci to Cheryl and Charles for babysitting me. > > Now I'll go slip into something comfortable like a Cuba Libre. > Du rien. The Collins boys say Hey. Cheryl

On Wed, 27 Feb 2013 18:19:28 GMT, Eagle@bellsouth.net (J. Hugh Sullivan) wrote: >If I want to continue to export seems like the best choice is to >remove NICK from the Legacy GEDCOM using "s - unless I can eliminate >/s from the surname. > >Hugh EUREKA, I think. If you look far enough down the custom list for export NICK can be excluded. It worked! You taught me to sit up and beg - what's the next trick? Hugh

On Wed, 27 Feb 2013 19:50:34 -0500, singhals <singhals@erols.com> wrote: <Much snipped> >>> It's hard to see how anything can actually adhere to the >>> spec, because it several places it contradicts itself, but >>> OK; still, I'd think it would let me SAY whether I wished to >>> include ALL spouses or only direct-line ancestors. I did >>> managed to pick a few to export, but for something larger >>> than a 5-man sample, way too much manual effort. >>> >>> >> Well, there is a bit of a learning cruve with using the selection >> criteria, but it does work quite well and is really quite flexible. >> > >Learning curbes are one thing, but I didn't see anything >/to/ be learned ... > File/Export (People to export)Click then select and click on "Select from list" In the window that opens, browse or type in the name of the person you want to start the gedcom on, for me that's usually myself. With that person highlighted , click on the tab that says "Mark Group" Select one of the options, say descendants, then select whether you want spouses, direct only, etc and for how many generations and click OK Now, those people are all marked for export.... but don't stop there. You can repeat those steps and continue marking additional people again clicking the "Mark group" tab and selecting different options until you get everyone you want included. As I said, it's a bit complicated, but enables a very selective export, and once familiar withthe process, it goes very fast. That's the basic process. There's also an "UNMARK GROUP" tab where I think you could first select everyone, and then selectively "exclude" people, but I've never used that.

On Wed, 27 Feb 2013 10:52:14 -0600, Charlie Hoffpauir <invalid@invalid.com> wrote: The wicket gets stickier! I converted the " to / and imported to RM. The result is James /Hugh/ /SULLIVAN/ /SULLIVAN/ because the Legacy GEDCOM shows both names with slashes - but no NICK. If I want to continue to export seems like the best choice is to remove NICK from the Legacy GEDCOM using "s - unless I can eliminate /s from the surname. Hugh

On Wed, 27 Feb 2013 10:52:14 -0600, Charlie Hoffpauir <invalid@invalid.com> wrote: Given Name: The following characters are not usually found in a name: !@#$%^&*_ +=|\/;:><~` []{} 0123456789. Above is the message I get when trying special characters. AHA! I don't see -, ., ,, or ?. But a glimmer of light. "usually" always gives me room to maneuver. :) In case you were worried about the old man :) I am NOT working with my regular GEDCOM and I doubt there is a limit on how many I can create. Hugh

On Wed, 27 Feb 2013 10:52:14 -0600, Charlie Hoffpauir <invalid@invalid.com> wrote: >I don't have an answer (not enough experience with Legacy, I can't >even find the search/replace function), but a question. What happens >if you decide to use a character that is not "handed", one that is the >same if it leads or follows the name? there are several, the obvious >ones are @, #, ^, *, and my favorites, |, and Š. I looked at that after an earlier post and the characters are not permitted. They may be permitted but problems might occur. The slash is permitted because the program uses the slash to distinguish the surname. That may have variations that I have not noticed. I'll look more closely. The S&R is the 5th menu item under search in the purchased copy. Hugh

On Wed, 27 Feb 2013 13:39:23 +0000, Tim Powys-Lybbe <tim@powys.org> wrote: >On 27 Feb at 11:50, Shmuel (Seymour J.) Metz ><spamtrap@library.lspace.org.invalid> wrote: > >> I've seen a lot of references to really old versions of GEDCOM. GEDCOM >> 5.5.1 seems to satisfy my immediate needs[1], but has been in draft >> status for a very long time. GEDCOM 6 is still a work in progress and >> I'm not sure where GEDCOM-X is. What is the prognosis for the major >> players to support at least GEDCOM 5.5.1 in UTF-8? >> >> [1] E.g., storing both a secular and a religous name, storing a >> romanized transliteration of a name in a non-roman script, >> storing a date in two different calendars. > >My opinion is a zilch prognosis. The problem with GEDCOM is that it >makes it relatively easy to transfer a lot of the data between genealogy >programs. But for the programmer this is not Good News; how much better >to lock the user into their program by making GEDCOM transfers more >difficult? > >Yo might get more mileage by asking your current program owners when >_They_ are going to provide the above features. > >-- >Tim Powys-Lybbe tim@powys.org > for a miscellany of bygones: http://powys.org/ Seems to me the problem has recently been discussed here. Users demand unique abilities in programs and developers try to satisfy. Even for an accomplished programmer methinks it would be very difficult to accomodate every variation even with options. Seems like a standardized version of GEDCOM with a program to adapt it to specific needs would be more of an answer. But I'm a user, not an enabler. Hugh

On Wed, 27 Feb 2013 08:41:25 -0600, Charlie Hoffpauir <invalid@invalid.com> wrote: With a tip of my fedora (beret?) to Cheryl (the freebie counter in this country is already WAY too crowded) I put my two peas in one pod... I started an S&R to replace the "s - almost 700. I knew in advance that the "Hugh" would become (Hugh(. I see no way to replace the first " only with a ( and repeat replacing the second " with a ). A / works. The problem? It's not what I want to do. So, I am reviewing individually because the S&R allows me to replace one and skip the other - then I can do it all over again. But as my dad used to say, "That's a lot of sugar for a dime!" Is there a command or other function that will allow me to replace "Hugh" with (Hugh) or even (Hugh" on the first try and (Hugh) on the second try without reviewing each of the instances individually? Thanks to everyone for bearing with me on this. Hugh

On Wed, 27 Feb 2013 15:20:44 -0500, singhals <singhals@erols.com> wrote: >Charlie Hoffpauir wrote: >> On Wed, 27 Feb 2013 13:33:10 -0500, singhals<singhals@erols.com> >> wrote: >> >>> Charlie Hoffpauir wrote: >>>> On Tue, 26 Feb 2013 20:07:06 -0500, singhals<singhals@erols.com> >>>> wrote: >>>> >>>> <snip> >>>>> I'm gonna take your word for it that when you export you get >>>>> a "NICK" field. I can't make Legacy or RM put that field >>>>> into the GED. I generated an RM GED (it didn't give me any >>>>> options about my target), and 4 from Legacy. None of them >>>>> had "NICK" when I looked. >>>>> >>>>>> If RM had the same Family Navigation Screen as Legacy I would switch >>>>>> back. But I'm a creature of habit. Where is that Fountain of Youth? >>>>> >>>>> Just past the Free Lunch Counter. ;) >>>>> >>>>> Cheryl >>>> >>>> I tested this on the free version I downloaded, and if I put a given >>>> name within quote marks, it is indeed put into a field labeled "NICK". >>>> I found nothing in any Legacy documentation referring to this, but a >>>> response posted in a Legacy user group indicated that this was the >>>> practice. BTW, it also shows the name with quote marks in the NAME >>>> field. Example below: >>>> >>>> 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 Legacy >>>> 1 DATE 27 Feb 2013 >>>> 1 SUBM @S0@ >>>> 1 FILE G:\RootsMagic\GEDCOMS\Example.ged >>>> 1 GEDC >>>> 2 VERS 5.5.1 >>>> 2 FORM LINEAGE-LINKED >>>> 1 CHAR ANSEL >>>> 0 @S0@ SUBM >>>> 1 NAME Not Given >>>> 0 @I31540@ INDI >>>> 1 NAME Charles Richard "Dicky" /Hoffpauir/ >>>> 2 GIVN Charles Richard "Dicky" >>>> 2 SURN Hoffpauir >>>> 2 NICK Dicky >>>> 1 SEX M >>>> 1 BIRT >>>> 2 DATE 15 Oct 1939 >>>> 1 _UID DC7C5732B78C4F388EBFC9274C420EE1650B >>>> 1 CHAN >>>> 2 DATE 27 Feb 2013 >>>> 3 TIME 08:36 >>>> 0 @I31541@ INDI >>>> 1 NAME Jerry 'Lynn' /Hoffpauir/ >>>> 2 GIVN Jerry 'Lynn' >>>> 2 SURN Hoffpauir >>>> 1 SEX M >>>> 1 _UID F025847F04784538B6E815A6089FC80DE636 >>>> 1 CHAN >>>> 2 DATE 24 Feb 2013 >>>> 3 TIME 09:13 >>>> 0 @I31542@ INDI >>>> 1 NAME Luther "Francis" /Hoffpauir/ >>>> 2 GIVN Luther "Francis" >>>> 2 SURN Hoffpauir >>>> 2 NICK Francis >>>> 1 SEX M >>>> 1 _UID 1082D24D2C144E60A966605DCEB75FBB0A54 >>>> 1 CHAN >>>> 2 DATE 24 Feb 2013 >>>> 3 TIME 09:13 >>>> 0 TRLR >>> >>> >>> Using a db I had handy at the FHC and Legacy7.5, I added >>> "Tom" and (Tom) as an Alternate name to one Thomas >>> Swearingen, and then created 4 GEDs: Legacy-to-Legacy; >>> Legacy-to-GED5.5.1; Legacy-to-basic-GED; and Legacy-to-PAF5 >>> Omitted from this is the Legacy to Basic GED one. >>> >> >> Just wondering, why as an alternate name? What Hugh is looking at is >> typically someone with the given names Luther Francis, who is called >> Francis, and so usually signs L. Francis. Hugh wants to make it clear >> that the program and anyone looking at it knows that person should be >> known as Francis, rather than Luther, and so enters the name as Luther >> "Francis". there's no need to use the alternate name field at all. > >Operating hypothesis was that if the GED was going to show >NICK it would come from a field identified that way. >Alt-Name was the nearest option. And, that's what it >/sounded/ as if the HELP files were saying to do. OTOH, >perhaps I was meant to understand that alt-name is where a >woman's married name is to go. > Yeah, I had thoughts along the same line. I'm surprised there isn't a field somewhere on the entry screen simply labeled Nickname, or at least some comment on how to enter a nickname. I did a search on the help file for "Nickname" and all I got was a list of nicknames and the actual names that they might represent. I doubt that the programmer intends the woman's married name there because there was a comment that Legacy will accept an unlimited number of alternate names. > >>> Out of Legacy TO Legacy: >>> 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 Legacy >>> 1 DATE 26 Feb 2013 >>> 1 SUBM @S0@ >>> 1 FILE E:\hhsbook\legacy.ged >>> 1 GEDC >>> 2 VERS 5.5.1 >>> 2 FORM LINEAGE-LINKED >>> 1 CHAR ANSEL >>> 0 @S0@ SUBM >>> 1 NAME Not Given >>> 0 @I1@ INDI >>> 1 NAME Thomas /Swearingen/ >>> 2 GIVN Thomas >>> 2 SURN Swearingen >>> 1 NAME "Tom" // >>> 2 GIVN "Tom" >>> 2 SURN >>> 1 NAME (Tom) // >>> 2 GIVN (Tom) >>> 2 SURN >>> 1 NAME 'Tom' // >>> 2 GIVN 'Tom' >>> 2 SURN >>> 1 SEX M >>> 1 BIRT >>> 2 DATE 1688 >>> 2 PLAC Md >>> 2 SOUR @S2@ >>> 1 DEAT Y >>> 1 _UID BBE139991522481FAFC4589C6E7BE324631E >>> 1 CHAN >>> 2 DATE 26 Feb 2013 >>> 3 TIME 13:36 >>> 1 FAMS @F1@ >>> >>> **** >>> Out of Legacy to GED 5.5.1; >>> >>> 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 26 Feb 2013 >>> 1 SUBM @S0@ >>> 1 FILE E:\hhsbook\5.5ged.ged >>> 1 GEDC >>> 2 VERS 5.5.1 >>> 2 FORM LINEAGE-LINKED >>> 1 CHAR ANSEL >>> 0 @S0@ SUBM >>> 1 NAME Not Given >>> 0 @I1@ INDI >>> 1 NAME Thomas /Swearingen/ >>> 2 GIVN Thomas >>> 2 SURN Swearingen >>> 1 NAME "Tom" // >>> 2 GIVN "Tom" >>> 2 SURN >>> 1 NAME (Tom) // >>> 2 GIVN (Tom) >>> 2 SURN >>> 1 NAME 'Tom' // >>> 2 GIVN 'Tom' >>> 2 SURN >>> 1 SEX M >>> 1 BIRT >>> 2 DATE 1688 >>> 2 PLAC Md >>> 2 SOUR @S2@ >>> 1 DEAT Y >>> 1 _UID BBE139991522481FAFC4589C6E7BE324631E >>> 1 CHAN >>> 2 DATE 26 Feb 2013 >>> 3 TIME 13:36 >>> 1 FAMS @F1@ >>> *** >>> >>> Out of Legacy to PAF 5.x: >>> 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 PAF5 >>> 1 DATE 26 Feb 2013 >>> 1 SUBM @S0@ >>> 1 FILE E:\hhsbook\paf5.ged >>> 1 GEDC >>> 2 VERS 5.5.1 >>> 2 FORM LINEAGE-LINKED >>> 1 CHAR UTF-8 >>> 0 @S0@ SUBM >>> 1 NAME Not Given >>> 0 @I1@ INDI >>> 1 NAME Thomas /Swearingen/ >>> 2 GIVN Thomas >>> 2 SURN Swearingen >>> 2 _AKA "Tom" // or (Tom) // or 'Tom' // >>> 1 SEX M >>> 1 BIRT >>> 2 DATE 1688 >>> 2 PLAC Md >>> 2 SOUR @S2@ >>> 1 DEAT Y >>> 1 _UID BBE139991522481FAFC4589C6E7BE324631E >>> 1 CHAN >>> 2 DATE 26 Feb 2013 >>> 3 TIME 13:36 >>> 1 FAMS @F1@ >>> 0 @I2@ INDI >>> 1 NAME Lydia /Riley/ >>> 2 GIVN Lydia >>> 2 SURN Riley >>> 2 SOUR @S34@ >>> 1 SEX F >>> 1 BIRT >>> 2 DATE 1691 >>> 2 SOUR @S2@ >>> 1 DEAT >>> 2 DATE 1764 >>> 1 _UID C6E486BFCC2A4B16A1481566C65678609EBB >>> 1 CHAN >>> 2 DATE 5 Feb 2013 >>> 3 TIME 13:49 >>> 1 FAMS @F1@ >>> >>> I then opened the same file with RM. So far as I could >>> determine, the RM version available at the Family History >>> Centers *has* no options, you either export a .ged or you >>> don't -- I didn't even see a way to restrict how much of the >>> file I wanted exported; probably a user-error there. >>> >> >> Bruce has in the past said somthing to the effect that RM strickly >> adhears to the GEDCOM spec.... so I guess that means that there ARE no >> options. Like Legacy, after you decide to export a GEDOM you can (by >> default) export the entire database, or in RM select from a list.... >> where there are many options. > >It's hard to see how anything can actually adhere to the >spec, because it several places it contradicts itself, but >OK; still, I'd think it would let me SAY whether I wished to >include ALL spouses or only direct-line ancestors. I did >managed to pick a few to export, but for something larger >than a 5-man sample, way too much manual effort. > > Well, there is a bit of a learning cruve with using the selection criteria, but it does work quite well and is really quite flexible. >>> However, RM to Ged: >>> 0 HEAD >>> 1 SOUR RootsMagic >>> 2 NAME RootsMagic >>> 2 VERS 6.0 >>> 2 CORP RootsMagic, Inc. >>> 3 ADDR PO Box 495 >>> 4 CONT Springville, UT 84663 >>> 4 CONT USA >>> 3 PHON 1-800-ROOTSMAGIC >>> 3 WWW www.RootsMagic.com >>> 1 DEST RootsMagic >>> 1 DATE 26 FEB 2013 >>> 1 FILE RM_.ged >>> 1 GEDC >>> 2 VERS 5.5.1 >>> 2 FORM LINEAGE-LINKED >>> 1 CHAR UTF-8 >>> 0 @I1@ INDI >>> 1 NAME Thomas /Swearingen/ >>> 2 GIVN Thomas >>> 2 SURN Swearingen >>> 1 NAME "Tom" // >>> 2 GIVN "Tom" >>> 1 NAME (Tom) // >>> 2 GIVN (Tom) >>> 1 NAME 'Tom' // >>> 2 GIVN 'Tom' >>> 1 SEX M >>> 1 _UID CD0DA454E12248949954482C7D550E6A5CEE >>> 1 CHAN >>> 2 DATE 26 FEB 2013 >>> 1 BIRT >>> 2 _PRIM Y >>> 2 DATE 1688 >>> 2 PLAC Md >>> 2 SOUR @S2@ >>> 3 _TMPLT >>> 4 FIELD >>> 5 NAME Page >>> 1 DEAT Y >>> 1 FAMS @F1@ >>> >>> *** >>> >>> No NICK in sight. >>> >>> [shrug] As my mechanic often says, if I can't replicate it, >>> I can't fix it. (g) >>> >>> Still -- Hugh -- If you haven't already, does Legacy let you >>> do case-sensitive? If so then pick that and do a Find: "H >>> Replace: (H and then a FIND: h" Replace: h) >>> >>> Cheryl >> >> >> I don't know enough about Legacy to test various types of GEDCOMS, I >> just went with the default, and as the responder on the Legacy user >> group advised, putting a name within quotes gave me the NICK in the >> export. Apparently this is what Hugh is getting also. >> >> As to the last comment, the point is that "Hugh" is just an example. >> In reality, the name to be altered from "Hugh" to (Hugh) is really >> "any" name. >> > >True enough, but what you want to find doesn't matter to the >technique? > >C Correct, because what you want to "find" is anything between certain characters. and what you want to do is replace that (whatever it is) with the same thing between different characters. So programmatically, you do the search first for lines containing the GEDCOM field NAME then save the contents of each field to variables, then replace the quote marks with something else, and write the variables back into the correct places in the line. Or something like that. As I mentioned, I was rather surprised with how long it took (several minutes) and the first few times I tried it, I was convinced that it had crashed. This was on a GEDCOM of my data, that had only a few instances of quote marks that I had added just to test the process. Apparently what the procedure does is process every line, whether it has quote marks or not, and that's why it runs rather slow. And quite possibly it is writing the entire file out every time it makes a correction..... I don't know enough about Powershell processing to really know the nuts and bolts of what is going on.

Charlie Hoffpauir wrote: > On Wed, 27 Feb 2013 13:33:10 -0500, singhals<singhals@erols.com> > wrote: > >> Charlie Hoffpauir wrote: >>> On Tue, 26 Feb 2013 20:07:06 -0500, singhals<singhals@erols.com> >>> wrote: >>> >>> <snip> >>>> I'm gonna take your word for it that when you export you get >>>> a "NICK" field. I can't make Legacy or RM put that field >>>> into the GED. I generated an RM GED (it didn't give me any >>>> options about my target), and 4 from Legacy. None of them >>>> had "NICK" when I looked. >>>> >>>>> If RM had the same Family Navigation Screen as Legacy I would switch >>>>> back. But I'm a creature of habit. Where is that Fountain of Youth? >>>> >>>> Just past the Free Lunch Counter. ;) >>>> >>>> Cheryl >>> >>> I tested this on the free version I downloaded, and if I put a given >>> name within quote marks, it is indeed put into a field labeled "NICK". >>> I found nothing in any Legacy documentation referring to this, but a >>> response posted in a Legacy user group indicated that this was the >>> practice. BTW, it also shows the name with quote marks in the NAME >>> field. Example below: >>> >>> 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 Legacy >>> 1 DATE 27 Feb 2013 >>> 1 SUBM @S0@ >>> 1 FILE G:\RootsMagic\GEDCOMS\Example.ged >>> 1 GEDC >>> 2 VERS 5.5.1 >>> 2 FORM LINEAGE-LINKED >>> 1 CHAR ANSEL >>> 0 @S0@ SUBM >>> 1 NAME Not Given >>> 0 @I31540@ INDI >>> 1 NAME Charles Richard "Dicky" /Hoffpauir/ >>> 2 GIVN Charles Richard "Dicky" >>> 2 SURN Hoffpauir >>> 2 NICK Dicky >>> 1 SEX M >>> 1 BIRT >>> 2 DATE 15 Oct 1939 >>> 1 _UID DC7C5732B78C4F388EBFC9274C420EE1650B >>> 1 CHAN >>> 2 DATE 27 Feb 2013 >>> 3 TIME 08:36 >>> 0 @I31541@ INDI >>> 1 NAME Jerry 'Lynn' /Hoffpauir/ >>> 2 GIVN Jerry 'Lynn' >>> 2 SURN Hoffpauir >>> 1 SEX M >>> 1 _UID F025847F04784538B6E815A6089FC80DE636 >>> 1 CHAN >>> 2 DATE 24 Feb 2013 >>> 3 TIME 09:13 >>> 0 @I31542@ INDI >>> 1 NAME Luther "Francis" /Hoffpauir/ >>> 2 GIVN Luther "Francis" >>> 2 SURN Hoffpauir >>> 2 NICK Francis >>> 1 SEX M >>> 1 _UID 1082D24D2C144E60A966605DCEB75FBB0A54 >>> 1 CHAN >>> 2 DATE 24 Feb 2013 >>> 3 TIME 09:13 >>> 0 TRLR >> >> >> Using a db I had handy at the FHC and Legacy7.5, I added >> "Tom" and (Tom) as an Alternate name to one Thomas >> Swearingen, and then created 4 GEDs: Legacy-to-Legacy; >> Legacy-to-GED5.5.1; Legacy-to-basic-GED; and Legacy-to-PAF5 >> Omitted from this is the Legacy to Basic GED one. >> > > Just wondering, why as an alternate name? What Hugh is looking at is > typically someone with the given names Luther Francis, who is called > Francis, and so usually signs L. Francis. Hugh wants to make it clear > that the program and anyone looking at it knows that person should be > known as Francis, rather than Luther, and so enters the name as Luther > "Francis". there's no need to use the alternate name field at all. Operating hypothesis was that if the GED was going to show NICK it would come from a field identified that way. Alt-Name was the nearest option. And, that's what it /sounded/ as if the HELP files were saying to do. OTOH, perhaps I was meant to understand that alt-name is where a woman's married name is to go. >> Out of Legacy TO Legacy: >> 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 Legacy >> 1 DATE 26 Feb 2013 >> 1 SUBM @S0@ >> 1 FILE E:\hhsbook\legacy.ged >> 1 GEDC >> 2 VERS 5.5.1 >> 2 FORM LINEAGE-LINKED >> 1 CHAR ANSEL >> 0 @S0@ SUBM >> 1 NAME Not Given >> 0 @I1@ INDI >> 1 NAME Thomas /Swearingen/ >> 2 GIVN Thomas >> 2 SURN Swearingen >> 1 NAME "Tom" // >> 2 GIVN "Tom" >> 2 SURN >> 1 NAME (Tom) // >> 2 GIVN (Tom) >> 2 SURN >> 1 NAME 'Tom' // >> 2 GIVN 'Tom' >> 2 SURN >> 1 SEX M >> 1 BIRT >> 2 DATE 1688 >> 2 PLAC Md >> 2 SOUR @S2@ >> 1 DEAT Y >> 1 _UID BBE139991522481FAFC4589C6E7BE324631E >> 1 CHAN >> 2 DATE 26 Feb 2013 >> 3 TIME 13:36 >> 1 FAMS @F1@ >> >> **** >> Out of Legacy to GED 5.5.1; >> >> 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 26 Feb 2013 >> 1 SUBM @S0@ >> 1 FILE E:\hhsbook\5.5ged.ged >> 1 GEDC >> 2 VERS 5.5.1 >> 2 FORM LINEAGE-LINKED >> 1 CHAR ANSEL >> 0 @S0@ SUBM >> 1 NAME Not Given >> 0 @I1@ INDI >> 1 NAME Thomas /Swearingen/ >> 2 GIVN Thomas >> 2 SURN Swearingen >> 1 NAME "Tom" // >> 2 GIVN "Tom" >> 2 SURN >> 1 NAME (Tom) // >> 2 GIVN (Tom) >> 2 SURN >> 1 NAME 'Tom' // >> 2 GIVN 'Tom' >> 2 SURN >> 1 SEX M >> 1 BIRT >> 2 DATE 1688 >> 2 PLAC Md >> 2 SOUR @S2@ >> 1 DEAT Y >> 1 _UID BBE139991522481FAFC4589C6E7BE324631E >> 1 CHAN >> 2 DATE 26 Feb 2013 >> 3 TIME 13:36 >> 1 FAMS @F1@ >> *** >> >> Out of Legacy to PAF 5.x: >> 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 PAF5 >> 1 DATE 26 Feb 2013 >> 1 SUBM @S0@ >> 1 FILE E:\hhsbook\paf5.ged >> 1 GEDC >> 2 VERS 5.5.1 >> 2 FORM LINEAGE-LINKED >> 1 CHAR UTF-8 >> 0 @S0@ SUBM >> 1 NAME Not Given >> 0 @I1@ INDI >> 1 NAME Thomas /Swearingen/ >> 2 GIVN Thomas >> 2 SURN Swearingen >> 2 _AKA "Tom" // or (Tom) // or 'Tom' // >> 1 SEX M >> 1 BIRT >> 2 DATE 1688 >> 2 PLAC Md >> 2 SOUR @S2@ >> 1 DEAT Y >> 1 _UID BBE139991522481FAFC4589C6E7BE324631E >> 1 CHAN >> 2 DATE 26 Feb 2013 >> 3 TIME 13:36 >> 1 FAMS @F1@ >> 0 @I2@ INDI >> 1 NAME Lydia /Riley/ >> 2 GIVN Lydia >> 2 SURN Riley >> 2 SOUR @S34@ >> 1 SEX F >> 1 BIRT >> 2 DATE 1691 >> 2 SOUR @S2@ >> 1 DEAT >> 2 DATE 1764 >> 1 _UID C6E486BFCC2A4B16A1481566C65678609EBB >> 1 CHAN >> 2 DATE 5 Feb 2013 >> 3 TIME 13:49 >> 1 FAMS @F1@ >> >> I then opened the same file with RM. So far as I could >> determine, the RM version available at the Family History >> Centers *has* no options, you either export a .ged or you >> don't -- I didn't even see a way to restrict how much of the >> file I wanted exported; probably a user-error there. >> > > Bruce has in the past said somthing to the effect that RM strickly > adhears to the GEDCOM spec.... so I guess that means that there ARE no > options. Like Legacy, after you decide to export a GEDOM you can (by > default) export the entire database, or in RM select from a list.... > where there are many options. It's hard to see how anything can actually adhere to the spec, because it several places it contradicts itself, but OK; still, I'd think it would let me SAY whether I wished to include ALL spouses or only direct-line ancestors. I did managed to pick a few to export, but for something larger than a 5-man sample, way too much manual effort. >> However, RM to Ged: >> 0 HEAD >> 1 SOUR RootsMagic >> 2 NAME RootsMagic >> 2 VERS 6.0 >> 2 CORP RootsMagic, Inc. >> 3 ADDR PO Box 495 >> 4 CONT Springville, UT 84663 >> 4 CONT USA >> 3 PHON 1-800-ROOTSMAGIC >> 3 WWW www.RootsMagic.com >> 1 DEST RootsMagic >> 1 DATE 26 FEB 2013 >> 1 FILE RM_.ged >> 1 GEDC >> 2 VERS 5.5.1 >> 2 FORM LINEAGE-LINKED >> 1 CHAR UTF-8 >> 0 @I1@ INDI >> 1 NAME Thomas /Swearingen/ >> 2 GIVN Thomas >> 2 SURN Swearingen >> 1 NAME "Tom" // >> 2 GIVN "Tom" >> 1 NAME (Tom) // >> 2 GIVN (Tom) >> 1 NAME 'Tom' // >> 2 GIVN 'Tom' >> 1 SEX M >> 1 _UID CD0DA454E12248949954482C7D550E6A5CEE >> 1 CHAN >> 2 DATE 26 FEB 2013 >> 1 BIRT >> 2 _PRIM Y >> 2 DATE 1688 >> 2 PLAC Md >> 2 SOUR @S2@ >> 3 _TMPLT >> 4 FIELD >> 5 NAME Page >> 1 DEAT Y >> 1 FAMS @F1@ >> >> *** >> >> No NICK in sight. >> >> [shrug] As my mechanic often says, if I can't replicate it, >> I can't fix it. (g) >> >> Still -- Hugh -- If you haven't already, does Legacy let you >> do case-sensitive? If so then pick that and do a Find: "H >> Replace: (H and then a FIND: h" Replace: h) >> >> Cheryl > > > I don't know enough about Legacy to test various types of GEDCOMS, I > just went with the default, and as the responder on the Legacy user > group advised, putting a name within quotes gave me the NICK in the > export. Apparently this is what Hugh is getting also. > > As to the last comment, the point is that "Hugh" is just an example. > In reality, the name to be altered from "Hugh" to (Hugh) is really > "any" name. > True enough, but what you want to find doesn't matter to the technique? C

On Wed, 27 Feb 2013 13:43:06 -0600, Charlie Hoffpauir <snip> >Note to Hugh: From your other post it looks like you are still trying >to make an alteration to a Legacy GEDCOM... to something that will >look right in RM. The best solution I've seen so far was what Dennis >Bieber wrote as a Powershell command set, to operate on a GEDCOM and >replace all instances of a name within quotes by that name within >tildes, so that "Hugh" becomes ~Hugh~ (only an example again, the >routine fixes "any" name) everywhere it appears in either a NAME field >or a GIVN field. I tested that on a large GEDCOM, and although it took >a long time to run, it did work perfectly. Once you import the >corrected GEDCOM into RM, it's trivial to do a search/replace to >change the tildes back to quotes. > >The good thing about Powershell is that you probably already have it >on your computer, or it's free to install. And you don't really have >to know anything else but how to copy the command once you open the >Powershell "shell". I now rescind all of the above, based on the fact that Hugh has determined that Legacy has the very neat feature of allowing one to eliminate one or more fields from the export to GEDCOM! That is by far the best solution!