I use wildcards so rarely (and so ineptly) that I wasn't aware that spaces
are treated differently. Thanks for enlightening me.
As for the replacement, Bob Buckland performed a number of diagnostic tests
with results too complex to even read about, much less report, but I think
we can all agree that Word's behavior is not illogical even though it is
(initially) puzzling.
--
Suzanne S. Barnhill
Microsoft MVP (Word)
Words into Type
Fairhope, Alabama USA
"PamC via OfficeKB.com" u43222@uwe wrote in message
news:86164fb039204@uwe...
Suzanne, I agree with you completely about your point 2. I was so caught
up
in his saying the replace couldn't "find" the spaces that I didn't
interpret it as meaning that it didn't replace the two spaces--which, as
you
say, is perfectly understandable when there are deletions between the
spaces.
And you are right about point 1 too, except if you are searching using
wild
cards, which is what I most often do. In fact I rely on Word not finding
my
combinations of NB space and regular space when I run my multiple space
removing macro. Word is such a tricky program.
Thanks for setting me straight.
PamC
Suzanne S. Barnhill wrote:
Just a couple of points he
1. Searching for a space will actually find nonbreaking spaces as well as
ordinary ones.
2. Eric *is* searching in Final view; that's the issue. The spaces he's
looking for are separated by deleted text. This doesn't seem to prevent
Word
from finding the two spaces as long as he's only looking, but it does
prevent replacement.
The more I think about this, the more logical it is, really. In order to
replace the two spaces with one, Word would have to make some decision
about
the deleted text that separates them, and the logical result would be to
delete it, but until that change is accepted, it can't actually be finally
deleted. I think that's the issue here.
OK. In the Find and Replace dialog, Click the more button. Make sure
all
[quoted text clipped - 49 lines]
And what are you replacing it with?
--
Message posted via http://www.officekb.com