View Single Post
Old 04-23-2011, 04:13 PM   #98
st_albert
Guru
st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'st_albert gives new meaning to the word 'superlative.'
 
Posts: 698
Karma: 150000
Join Date: Feb 2010
Device: none
Quote:
Originally Posted by crutledge View Post
When I load an html file with <hr class="sigilChapterBreak" /> in all the desired places and split the file, the bookname.html (which contains the cover) comes out as the last entry in the text part of BB. I can then move this the the head of the text entries. Any other sections out of sequence are also moved.

When I initially press Alt F3 the toc shows up in the correct order with cover as the first item. I press Generrate TOC and the old type display appears and everything is fine except cover is always last. Sigil refuses any attempt I have made to correct this.

The only solution I have found is the copy toc.ncx to my external editor, move the cover record to the first position and then use GREP to re-number the display sequence, and copy this back into the sigil toc.ncx. This works but is very un-elegant.

Combine this with having to edit the OPF for missing entries almost makes me miss BD.

Have I missed something? I would very much like to have a experience.
I think this is related to Issue 863 and Issue 865. When the file is initially loaded into Sigil 0.4RC1, the toc.ncx is built from the unsplit file. Everything should be in order. If you look at the toc.ncx, all the file refs point to the single .xhtml file. After the split, the toc.ncx remains unchanged until you hit the "generate toc" button. Then the toc.ncx is rebuilt, with the garbled chapter order due to the garbled file split order as discussed above.

As an aside, the toc.ncx will have (at least in my experience) references to all of the chapter headers, even though some of the files will not be included in the content.opf <manifest> and/or <spine> sections.

Hence the FC errors like "file is reachable, but not in the manifest" because the toc.ncx does refer to it even though the content.opf doesn't have it.
st_albert is offline   Reply With Quote