Quote:
Originally Posted by theducks
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>
|
Yeah, no, I don't think it does regex either, which is half the problem. But the thing is, that line? is not a multiline. It's a single line, that is present in the ebook in exactly the form I've written it down. I can't just look for </table>, because I have a lot of books that have multiple tables in them, and I am looking for a specific few ones. Actually, the line I was looking for is far longer, but as regex won't work, the bit I mentioned is basically the only thing I can search without getting too many false positives, so to say. But having nevertheless tried that too, as well as <table>, I can honestly say even that search turns up negative.
Also, that doesn't explain why utterly normal text (well, normal aside from the fact that it is inside a table, come to think of it) will not be found by the plugin either.
There has to be a reason, so if there are reasons, like say, tables are inherently unsearchable or something, I'd like to know for future reference.