On Sun, 24 Feb 2013 00:17:51 -0500, "T.M. Sommers" <tmsommers2@gmail.com> wrote: >On 2/18/2013 11:20 AM, J. Hugh Sullivan wrote: >> >> I use " marks to identify middle names of people who go by the middle >> name. My problem is switching from one genie program to another. The >> second reads the name in quotes as a nickname and shows it twice... >> James "Hugh" "Hugh" Sullivan. > >Why not use 'James Hugh "Hugh" Sullivan'? It clearly indicates that >Hugh is not only your real name (there is a 'Claude "Pete" Davis' in my >database, who was called 'Pete' although that was no part of his "real" >name), but it is the name you used. The duplication may look a little >odd, but it is unambiguous, and, I think, clear to anyone. That's an interesting suggestion, but I don't think it addresses the problem that the OP was seeing. If I understand his problem correctly, entering the name(s) as 'James Hugh "Hugh" Sullivan' would simply cause the name to appear as 'James Hugh "Hugh" "Hugh" Sullivan' when it transferred into the other program. I downloaded a copy of the free version of Legacy, and imported my data into it to play around with this. Legacy does indeed put the name in quote marks into the GEDCOM in a field labeled as "NICK". The interesting thing is, I can't find anywhere in Legacy where you can actually enter a Nickname. It's easy to add another name, but it shows up as an alternate name. (But I'm not a Legacy user, so I'm not familiar with the program.) My guess is that Legacy (somewhere) advocates the user entering a nickname in quotes.... if that's the case, then the OP is actually creating the problem by the technique he uses. Now if Hugh doesn't use the quote marks as defining a nickname for any other entries, the editing the GEDCOM to correct the problem becomes much easier.... ie, simply remove any instance of the NICK field.

On 2/24/2013 8:09 AM, Charlie Hoffpauir wrote: > On Sun, 24 Feb 2013 00:17:51 -0500, "T.M. Sommers" > <tmsommers2@gmail.com> wrote: > >> On 2/18/2013 11:20 AM, J. Hugh Sullivan wrote: >>> >>> I use " marks to identify middle names of people who go by the middle >>> name. My problem is switching from one genie program to another. The >>> second reads the name in quotes as a nickname and shows it twice... >>> James "Hugh" "Hugh" Sullivan. >> >> Why not use 'James Hugh "Hugh" Sullivan'? It clearly indicates that >> Hugh is not only your real name (there is a 'Claude "Pete" Davis' in my >> database, who was called 'Pete' although that was no part of his "real" >> name), but it is the name you used. The duplication may look a little >> odd, but it is unambiguous, and, I think, clear to anyone. > > That's an interesting suggestion, but I don't think it addresses the > problem that the OP was seeing. If I understand his problem correctly, > entering the name(s) as 'James Hugh "Hugh" Sullivan' would simply > cause the name to appear as 'James Hugh "Hugh" "Hugh" Sullivan' when > it transferred into the other program. Then I misunderstood the problem. It looks like a bug to me, in that case. -- T.M. Sommers -- ab2sb

On Sun, 24 Feb 2013 07:09:01 -0600, Charlie Hoffpauir <invalid@invalid.com> wrote: >Now if Hugh doesn't use the quote marks as defining a nickname for any >other entries, the editing the GEDCOM to correct the problem becomes >much easier.... ie, simply remove any instance of the NICK field. I entered my name five times with the middle name in (1) parens (2) slashes (3) apostrophes (4) quotes (5) single apostrophe. The results are 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 24 Feb 2013 1 SUBM @S0@ 1 FILE C:\My Documents\GED\GECOM Trial.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 James (Hugh) /SULLIVAN/ 2 GIVN James (Hugh) 2 SURN SULLIVAN 1 SEX M 1 _UID E4099F3324514CD88BFB63DBCC224CFB51C2 1 CHAN 2 DATE 24 Feb 2013 3 TIME 09:39 0 @I2@ INDI 1 NAME James /Hugh/ /SULLIVAN/ 2 GIVN James /Hugh/ 2 SURN SULLIVAN 1 SEX M 1 _UID E1898F2341DF42EEB2A50ECDA7C69C05ACD6 1 CHAN 2 DATE 24 Feb 2013 3 TIME 09:41 0 @I3@ INDI 1 NAME James 'Hugh' /SULLIVAN/ 2 GIVN James 'Hugh' 2 SURN SULLIVAN 1 SEX M 1 _UID 8BAD81023233425293E5437D496B205212CF 1 CHAN 2 DATE 24 Feb 2013 3 TIME 10:07 0 @I4@ INDI 1 NAME James "Hugh" /SULLIVAN/ 2 GIVN James "Hugh" 2 SURN SULLIVAN 2 NICK Hugh 1 SEX M 1 _UID B33B642F082E42A6BD0B4CDAF4A0A506CC83 1 CHAN 2 DATE 24 Feb 2013 3 TIME 10:01 0 @I5@ INDI 1 NAME James 'Hugh /SULLIVAN/ 2 GIVN James 'Hugh 2 SURN SULLIVAN 1 SEX M 1 _UID AA32319050E5438982722A012BAC0BA14028 1 CHAN 2 DATE 24 Feb 2013 3 TIME 10:10 0 TRLR Using the slash and two apostrophes the program gave a warning and a list of special characters that should not be used (all except parens and slashes). It also gave the option to ignore the problem for the current individual. Interestingly it objected to TWO apostrophes but not one. When I looked at the help file for Legacy on nicknames it gave a long list of nicknames but no indication that quote marks would be treated as nicknames. The S & R in the program does not appear to work. Even if it did how would it know to replace the first " with an open ( and the second " with a closed )? I would apologize again for my naivete in using the program BUT, it seems to have accomplished one thing. Because of the variety in programs no standardized GEDCOM will ever serve a universal purpose. Thus the discussion on the best program to manipulate a GEDCOM may be of use. Hugh

On Sun, 24 Feb 2013 16:25:51 GMT, Eagle@bellsouth.net (J. Hugh Sullivan) wrote: >On Sun, 24 Feb 2013 07:09:01 -0600, Charlie Hoffpauir ><invalid@invalid.com> wrote: > >>Now if Hugh doesn't use the quote marks as defining a nickname for any >>other entries, the editing the GEDCOM to correct the problem becomes >>much easier.... ie, simply remove any instance of the NICK field. > >I entered my name five times with the middle name in (1) parens (2) >slashes (3) apostrophes (4) quotes (5) single apostrophe. The results >are 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 24 Feb 2013 >1 SUBM @S0@ >1 FILE C:\My Documents\GED\GECOM Trial.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 James (Hugh) /SULLIVAN/ >2 GIVN James (Hugh) >2 SURN SULLIVAN >1 SEX M >1 _UID E4099F3324514CD88BFB63DBCC224CFB51C2 >1 CHAN >2 DATE 24 Feb 2013 >3 TIME 09:39 >0 @I2@ INDI >1 NAME James /Hugh/ /SULLIVAN/ >2 GIVN James /Hugh/ >2 SURN SULLIVAN >1 SEX M >1 _UID E1898F2341DF42EEB2A50ECDA7C69C05ACD6 >1 CHAN >2 DATE 24 Feb 2013 >3 TIME 09:41 >0 @I3@ INDI >1 NAME James 'Hugh' /SULLIVAN/ >2 GIVN James 'Hugh' >2 SURN SULLIVAN >1 SEX M >1 _UID 8BAD81023233425293E5437D496B205212CF >1 CHAN >2 DATE 24 Feb 2013 >3 TIME 10:07 >0 @I4@ INDI >1 NAME James "Hugh" /SULLIVAN/ >2 GIVN James "Hugh" >2 SURN SULLIVAN >2 NICK Hugh >1 SEX M >1 _UID B33B642F082E42A6BD0B4CDAF4A0A506CC83 >1 CHAN >2 DATE 24 Feb 2013 >3 TIME 10:01 >0 @I5@ INDI >1 NAME James 'Hugh /SULLIVAN/ >2 GIVN James 'Hugh >2 SURN SULLIVAN >1 SEX M >1 _UID AA32319050E5438982722A012BAC0BA14028 >1 CHAN >2 DATE 24 Feb 2013 >3 TIME 10:10 >0 TRLR > >Using the slash and two apostrophes the program gave a warning and a >list of special characters that should not be used (all except parens >and slashes). It also gave the option to ignore the problem for the >current individual. Interestingly it objected to TWO apostrophes but >not one. > >When I looked at the help file for Legacy on nicknames it gave a long >list of nicknames but no indication that quote marks would be treated >as nicknames. > >The S & R in the program does not appear to work. Even if it did how >would it know to replace the first " with an open ( and the second " >with a closed )? > >I would apologize again for my naivete in using the program BUT, it >seems to have accomplished one thing. Because of the variety in >programs no standardized GEDCOM will ever serve a universal purpose. >Thus the discussion on the best program to manipulate a GEDCOM may be >of use. > >Hugh My limited tests on the free version confirm everything you've said. Hindsight tells me you should have started putting the called name in single quotes, or parens, or quite possibly anything but quotes. Given the present situation, possibly you could modify the routine that Dennis Bieber wrote in Powershell to replace the double quotes with singles, and eliminate the nickname field, then re-import the corrected GEDCOM back into Legacy.(you may not want to do this if you have entered "real" nicknames in your file). However, if you have "real" nicknames, how did you get them entered? I searched everywhere I know to look and I can't see any way to intentionally enter a nickname, other than the (undocumented) way of using double quotes. This all makes me glad I now only use one genealogy program.