J
John Doue
Hi,
Since in French, characters (;:?!) need an unbreakable space before
them, I frequnetly run a routine like this one for each of them:
Selection.Find.ClearFormatting
Selection.Find.Replacement.ClearFormatting
With Selection.Find
.Text = " ;"
.Replacement.Text = "^s;"
.Forward = True
.Wrap = wdFindContinue
.Format = False
.MatchCase = False
.Mat chWholeWord = False
.MatchWildcards = False
.MatchSoundsLike = False
.MatchAllWordForms = False
End With
Selection.Find.Execute Replace:=wdReplaceAll
which gets the job done.
However, I was recently remarked by a fellow translator that the revised
translations I was returning to him (with track changes on screen)
showed that all the properly hardspaced characters he had inserted had
been replaced by ... properly hardspaced characters.
Looking into the issue, I realized (I had forgotten about this) that
Word considers a "hard space" also as a "space" ... and therefore, my
macro needlessly replaces them. Which shows on screen when tracking
changes in on while running the macro.
Any ideas how to work around this?
Best regards
Since in French, characters (;:?!) need an unbreakable space before
them, I frequnetly run a routine like this one for each of them:
Selection.Find.ClearFormatting
Selection.Find.Replacement.ClearFormatting
With Selection.Find
.Text = " ;"
.Replacement.Text = "^s;"
.Forward = True
.Wrap = wdFindContinue
.Format = False
.MatchCase = False
.Mat chWholeWord = False
.MatchWildcards = False
.MatchSoundsLike = False
.MatchAllWordForms = False
End With
Selection.Find.Execute Replace:=wdReplaceAll
which gets the job done.
However, I was recently remarked by a fellow translator that the revised
translations I was returning to him (with track changes on screen)
showed that all the properly hardspaced characters he had inserted had
been replaced by ... properly hardspaced characters.
Looking into the issue, I realized (I had forgotten about this) that
Word considers a "hard space" also as a "space" ... and therefore, my
macro needlessly replaces them. Which shows on screen when tracking
changes in on while running the macro.
Any ideas how to work around this?
Best regards