View Single Post
Old 01-03-2011, 05:19 AM   #4
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
update:

I tried again using simple CHAPTER, not CHAPTER \d

similar results. TOC also contains a per chapter entry for NIGHT, which seems to match this piece of code ?
Code:
  <title>NIGHT</title>
  <link href="../Styles/stylesheet.css" rel="stylesheet" type="text/css" />
  <style type="text/css">
/*<![CDATA[*/
                @page { margin-bottom: 5.000000pt; margin-top: 5.000000pt; }
  /*]]>*/
that stuff about margin bottom also appears in the toc ???

PS is there a tutorial on xpath that I should study, rather than just wing it.

PPS I know I can fix this manually by editing all CHAPTER occurence tags in sigil - from normal - to H1 or H2 - but that is tedious, & devising a regex for that is a bit beyond me. manually is open book in sigil- find CHAPTER, use drop down menu to change normal to H2, rinse & repeat... calibre will create a TOC once H2 tags are in place.

So at present I'm trying to find an alternative way to derive a TOC, based on recognition of books' chapter labelling, which is usually CHAPTER ONE, CHAPTER TWO,etc or CHAPTER 1, CHAPTER 2 etc

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