View Single Post
Old 07-17-2012, 01:57 PM   #6
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 27,545
Karma: 193191846
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
EDIT: As I understand the way the above search works (and this seems to be confirmed by my subsequent testing), is that It first looks for all instances with a bullet preceded by the p tag and excludes them. Then it looks for all instances of the bullet followed by the p tag, and excludes them. Then it returns any results that weren't excluded by the preceding TWO searches. It is not a single search to exclude an enclosed bullet.
That's not the way I understand it... but then, I didn't really understand your goal. I still don't quite.

Do you want it to exclude any bullet that occurs anywhere in any string that is enclosed by those "p class='calibre1'" tags? That could prove pretty tough, if so. I know I can't get my head around the expression to accomplish that (not that THAT renders it impossible by any means ).

I'd say your best bet is to isolate/alter the scene-breaks first and then catch any possible OCR glitches in a subsequent search.

Last edited by DiapDealer; 07-17-2012 at 02:11 PM.
DiapDealer is offline   Reply With Quote