Quote:
Originally Posted by edeniz
Question, because something confuses me:
What could be the reason if the plugin doesn't find the searched-for term in the epub?
For example, it's happened some time ago, that a searched-for text inside the epub body was not found, so I thought it maybe wasn't in any of the books in my library, but I found what I was looking for at a later date by sheer coincidence. It wasn't even like there were some special irregular, non-ASCII characters or some such in the text I was looking for.
Similarly, today I thought to do a search to find this in my epub:
and while there should have been at least one epub with it, the search returned empty. So, yeah, I'm confused. Something obvious I'm missing? 
I realize this description may be far too vague. If so, sorry. But the point is, I have no idea what the criteria are that could cause the plugin to not recognize a search, and I have not found anything about it in the help file, so maybe someone could point me in the right direction? |
I don't believe the PI does REGEX
because that might be what you need)
the \s* allows for 'pretty' (indented/multiline) coding
But ???
why not search for JUST </table> and avoid the multi-line issue?
I assume
that you want to edit books that HAVE tables
Code:
</td>\s*</tr>\s*</tbody>\s*</p>