Quote:
Originally Posted by phossler
@Tex2002ans -- thanks, I tried something similar, but the document had a lot of all caps acronyms that were being found. I tried the 'Replace/Find Next' but that was taking a lot of time
|
Ahhh... what I do is run this regex as one of my "final" cleanup passes.
I have a toc.ncx already generated, and/or I have preview open up on the left-half of my screen. I quickly jump to where I need to be using TOC/Preview, and then Find/Replace what I need in Code View.
I don't use this Find/Replace throughout the entire book (unless this particular book has some odd ALL CAPS floating around it that need to be checked/fixed).
It isn't the quickest/most automated way to do it, but while I am fixing this I am also quickly just scanning around/taking a look to see if I can catch any other typos/errors.
Quote:
Originally Posted by DiapDealer
@Tex2002ans:
The \b word boundary is handy, but it can also result in some confusing behavior if you run into any typographic quotes, apostrophes, or other unicode characters contained in the text.
|
Thanks for the info. Which is why I mentioned where my Regex breaks in my first post. Some of these Regex can get downright hairy, and I prefer something that is still understandable by a normal human!
