Thread: Search and replace sometimes doesn't work across all files
View Single Post
Old 11-09-2021, 11:36 PM   #13
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by Karellen View Post
Yes, I have found that you need to Beautify the book first to ensure all search results are captured.

I have also found that those that are missed are due to some instances using the No-Break space instead of a standard Space. So I also run a regex to remove those. Usually they are an additional space that is not needed, so I clear them out. It really had me pulling my hair out in my early editing days.

I have also found that "Wrap" works as expected on a single file in the Editor, but when using All Files, the Wrap is ignored and it wraps around to the start of the book and replaces unwanted instances and I end up with, as an example, <em><em>some word</em></em> which means an additional S&R to clear that out.
That sounds like wrapping is working to me. It hits the end of the current context, and goes to the beginning and continues from there. For "Current file" the file is the context. When it gets to the end of the file, it goes back to the beginning of the file and process up to the current position. For "All text files", when it hits the end of the current file, it goes to the next file, and then the next file. It eventually hits the end of all the files and starts at the first file and continues on from there until it hits the starting point. And that means it handles the start of the current file last.

If it is changing "unwanted" instances, then either you have the search wrong, or the search scope wrong. You do run the risk of wrapping and repeating change already made if the changed value matches the search. In your case, if your search was "(some word)" and the change was "<em>\1</em>", then if you didn't stop when you reached the first change, it would match again and you would get a result like you have.
davidfor is offline   Reply With Quote