View Single Post
Old 01-03-2011, 05:37 AM   #5
cybmole
Wizard
cybmole ought to be getting tired of karma fortunes by now.cybmole ought to be getting tired of karma fortunes by now.cybmole ought to be getting tired of karma fortunes by now.cybmole ought to be getting tired of karma fortunes by now.cybmole ought to be getting tired of karma fortunes by now.cybmole ought to be getting tired of karma fortunes by now.cybmole ought to be getting tired of karma fortunes by now.cybmole ought to be getting tired of karma fortunes by now.cybmole ought to be getting tired of karma fortunes by now.cybmole ought to be getting tired of karma fortunes by now.cybmole ought to be getting tired of karma fortunes by now.
 
Posts: 3,720
Karma: 1759970
Join Date: Sep 2010
Device: none
[QUOTE=Manichean; Also, I believe the chapter detection is done by XPath instead of regexes, so if you do use regexes, results may vary.

.[/QUOTE]

in the calibre path wizard screen there are 3 boxes to complete, it tells you to use a regex in the value box.
the line of code I want to detect is eg
Code:
<p class="MsoPlainText"><span>CHAPTER 2</span></p>
that class is used throughout the book, so focussing on the word CHAPTER seems to be the way to go
so I used tag=*(default), attribute BLANK (default), value CHAPTER \D

trying again with tag = span...... no difference...

PS the "night" entry in toc reads
Code:
night /*/@page{margin-bottom  etc
now NIGHT is in the title html tags as per extract posted earlier, but how is that also getting into the TOC , once per chapter ? I can supress it by putting the word NIGHT into TOC FILTER box, but don't understand the need for that.

Last edited by cybmole; 01-03-2011 at 05:47 AM.
cybmole is offline   Reply With Quote