I’m a bit late to this thread so it’s possible I’ve completely misunderstood 
the problem. If I’ve understood correctly, would this help? Import the gedcom 
again, but use a different name for the file, and use the setting that will 
result in clean notes. Then you could tag everyone who has a note, then open 
the two files side by side and copy and paste the properly formatted note to 
replace the goofed up note. As you finish a copy and paste, untag the person 
and go to the next tagged person and repeat. Use the individual tag box in the 
lower right hand part of the screen; this will move you from tagged person to 
tagged person  quickly.



This might at least speed up the process by allowing you to copy and paste 
quickly. It would certainly be quicker than correcting each note individually.



If I’m out in left field, please take into account my advanced age! J



Mary







From: Jay 1FamilyTree [mailto:[email protected]]
Sent: Wednesday, July 30, 2014 2:27 PM
To: [email protected]
Subject: Re: [LegacyUG] Switch From FTM 2014



This is so TRUE.



And it would work.



If you could just get the spell checker to review each "note" for errors and 
prompt you to review those for corrections.

Even better is to have a 'switch' that knows you are repairing broken words and 
when it finds a mis-spelled word it automatically checks to see if removing the 
space before or after solves the issue.

With that type of tool, I could fix all my issues in an hour!







On Wed, Jul 30, 2014 at 12:28 AM, Mike Fry <[email protected]> wrote:

On 30 Jul 2014 02:46, Jay 1FamilyTree wrote:

> I have over 50,000 with notes that have broken words.
> I have been waiting in hopes some day some eager programmer would create an 
> easy
> to use tool to fix everything..

:-)

What Legacy needs is a simple (?) addition to the search/replace mechanism.

a) Search any Notes field
b) For a spelling mistake
c) When found, pop up the standard spellcheck screen

--
Regards, Mike Fry
Johannesburg



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