set pagebreaks at TOC entires

[ldolse]

Sounds like you're getting it.

The epub special case will be going away in the near future, along with some other enhancements to preprocess.

[cybmole]

Originally Posted by ldolse

Sounds like you're getting it.

The epub special case will be going away in the near future, along with some other enhancements to preprocess.

sounds good.

there's a warning taken onto structure detect - something like

"use with care- this may make things worse "

under what circumstances does that happen ?

[cybmole]

I have sound some books in a series where the above structure detection appraoch is not working. chapters are not being detected. ...
I am going from mobi to epub and in the epub I see

    <p class="calibre9"><span class="calibre3"><span class="bold">Chapter 1</span></span></p><br class="calibre1" />  

...  

 <p class="calibre9"><span class="calibre3"><span class="bold">Chapter 2</span></span></p><br class="calibre1" />

I will now try to put them into the bug tracker system for you, please confirm that I've have done that correctly.

UPDATE - seems to be a case of preprocess not running on mobi source, despite having reset convert options to default.I did the extra step of copy the epub created by the failed attempt, renamed it as zip, add back to library, reconverted - then I do get chapters found, files split etc..

that's still pretty slick when I think of how long I spent fixing vol 1 & 2 of this series by hand ! but check it out please - should the preprocess have worked on the .mobi source ?

[ldolse]

See the bug, will make sure these scenarios are covered.

[ldolse]

Originally Posted by cybmole

I have sound some books in a series where the above structure detection appraoch is not working. chapters are not being detected. ...
I am going from mobi to epub and in the epub I see

    <p class="calibre9"><span class="calibre3"><span class="bold">Chapter 1</span></span></p><br class="calibre1" />  

...  

 <p class="calibre9"><span class="calibre3"><span class="bold">Chapter 2</span></span></p><br class="calibre1" />

I will now try to put them into the bug tracker system for you, please confirm that I've have done that correctly.

UPDATE - seems to be a case of preprocess not running on mobi source, despite having reset convert options to default.I did the extra step of copy the epub created by the failed attempt, renamed it as zip, add back to library, reconverted - then I do get chapters found, files split etc..

that's still pretty slick when I think of how long I spent fixing vol 1 & 2 of this series by hand ! but check it out please - should the preprocess have worked on the .mobi source ?

Mobi wasn't fully integrated into preprocess, as I didn't really have any mobi sources that required this sort of processing when I implemented the feature. The work that's underway now will have all file formats going through preprocess if it's enabled.

Regarding 'making things worse', the feature just uses common patterns. False positives are possible, though a lot of logic exists to prevent this, they can't be completely eliminated. It also removes all non-breaking spaces from the document to facilitate processing - if there were some in place for formatting reasons they'll be eliminated.

[cybmole]

thanks - I'll be happy to test on mobi sources for you, and/or to search my unchecked books for other types of chapter headers in mobi. meantime the mobi to epub; copy & rename to to zip, zip to epub to mobi route will do me.

the copy, rename, add back to calibre steps could probably done with a little dos script

[cybmole]

PS actually we never totally nailed the original thread question -

aside from going via structure detection, is it possible to tell calibre to add a page break and/or file split at each toc entry point, working directly from the existing toc ?

the reason for asking is that a book can have an obscure, hard to detect way of starting chapters but can also have a good-to-go TOC already. in that case, after convert to mobi - K3 will skip to next/prev toc entry OK, but will not start each chapter with a page break

[cybmole]

Originally Posted by ldolse

T


With the default ( preprocess) settings your file WILL be split into a single file per chapter - .

I thought I'd understood this , & bought into the above, but after filing a bug report re one obstinate book I get 2 contradictory responses:

1 - you saying - resolved - will be fixed in next release
"resolution: => fixed"

then

2, Kovid saying invalid bug report
resolution: => invalid
"Comment:
calibre does not recombine split files."

well does it or doesn't it ???


I thought that was a preprocess feature & it has worked OK on many books, once I got my preferences sorted , and grasped that currently, the file has to be re-imported as a zip for that preprocess to work OK???

[ldolse]

You're talking about two entirely different things. If a file is already split into multiple flows, Calibre won't re-merge it into a single flow, it will convert it as is, possibly adding new split points if configured to.

If a file IS a single flow, there are a variety of ways you can get Calibre to split it during conversion, one of which is the preprocess option combined with page break settings. The bug I fixed was to split files, not put them back together.

[cybmole]

ok - got it - so to combine files I would need to do somteing like epub to rtf to filtered html - reimport....

unfortunately, because the source is crap, calibre creates an invalid .rtf!

( as you have the buggy book already - any chance you call tell me why the rtf fails & whether I should register that as a different bug, please )

I could go via .txt but then I'd have to start over with tagging the chapter points !

[ldolse]

I don't support the rtf output plugin. Try txt instead, you can try to export the text using markdown to preserve some of the original formatting if there is any. Markdown will preserve any chapters already in the doc.

[theducks]

Originally Posted by cybmole

ok - got it - so to combine files I would need to do somteing like epub to rtf to filtered html - reimport....

unfortunately, because the source is crap, calibre creates an invalid .rtf!

( as you have the buggy book already - any chance you call tell me why the rtf fails & whether I should register that as a different bug, please )

I could go via .txt but then I'd have to start over with tagging the chapter points !

Sigil will combine (xHTML)files

[JSWolf]

Does anyone know who is in charge of the Mobipocket output or the ePub input?

I've found a bug converting an ePub to Mobi that a page was converted to three mobi pages.

[ldolse]

Originally Posted by JSWolf

Does anyone know who is in charge of the Mobipocket output or the ePub input?

I've found a bug converting an ePub to Mobi that a page was converted to three mobi pages.

Just open a bug with the file attached, someone will look at it.

[cybmole]

Originally Posted by ldolse

I don't support the rtf output plugin. Try txt instead, you can try to export the text using markdown to preserve some of the original formatting if there is any. Markdown will preserve any chapters already in the doc.

ok - i went that route and got the book into as good a shape as is practical.

I will not file a bug on rtf right now, I do not use rtf much, and the times is has given invalid results are with poor quality sources