Yes, those are the characters, � & � that are being switched. This has
nothing to do with the font or its set code, which is standard. The proper
characters appear in other programs. I have used alt 0167 (�) in about 800
event comment fields. There is nothing in the Search & Replace drop-down
that allows you to access the Event Comment field that I can see. I can find
all the instances using a straight search, but I really balk at doing 800+
manual changes, especially if they may all be changed again the next time I
open the file. Since the character code is correct and it is Legacy that is
mis-reading it, that seems highly probable. I could live with it, if it was
only a screen display problem, but the � character also prints in every
report.
Wm Voss
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Cheri
Casper
Sent: Saturday, 28 April, 2001 22:18
To: [EMAIL PROTECTED]
Subject: Re: [LegacyUG] unwanted character changes
I don't understand why you can't use a search and replace for this. What
type of events do you have this in? If they are the standard ones, you
should be able to run the S&R and using the alt + ASCI numbers put the S&R
strings into the search parameters.
To unsubscribe: http://www.legacyfamilytree.com/LegacyLists.asp
