Splitting a book

[HarryT]

I've recently bought a book which contains a single source file, 1.6MB in size. Is there any facility in the editor to automatically split it (eg by chapters) into more manageable pieces?

Thanks!

[theducks]

Originally Posted by HarryT

I've recently bought a book which contains a single source file, 1.6MB in size. Is there any facility in the editor to automatically split it (eg by chapters) into more manageable pieces?

Thanks!

Tweak (AKA the editor)
In the Preview pane (one of the few places it is used for other than viewing): click the folded paper icon, then drag the green line to the split spot: Click

There is a Bulk split, but I have not learned to use that (I am still stuck on Sigil-think where I just use the REGEX to insert a Sigil_Split marker. the execute the Split with a <F6>)

[jackie_w]

The Editor uses Xpath (right-click in code view) in the same way as on the convert Look&Feel page. If the existing code doesn't easily lend itself to the Xpath approach, I guess you could also use a kind-of-Sigil-split-marker-type approach by using regex to insert some <h2></h2> or <h3></h3> dummy headers (if they don't already exist), then remove them after the split.

[PatNY]

Assuming there is some sort of specific headline style at the beginning of each chapter which doesn't appear later on in the chapter -- and this is often the case -- then in the css stylesheet under that style you could add:

page-break-before: always;


Then do a Calibre conversion and make sure under "EPUB Output" that "Do not split on page breaks" is unchecked.

--Pat

[theducks]

Originally Posted by PatNY

Assuming there is some sort of specific headline style at the beginning of each chapter which doesn't appear later on in the chapter, then in the css stylesheet under that style you could add:

page-break-before: always;


Then do a Calibre conversion and make sure under "EPUB Output" that "Do not split on page breaks" is unchecked.

--Pat

That only appears to split the file: (start a new chapter at the top of a screen)
260K max is the MRSDK rule if you want a reliable book on older devices.

[PatNY]

Originally Posted by theducks

That only appears to split the file: (start a new chapter at the top of a screen)
260K max is the MRSDK rule if you want a reliable book on older devices.

ducks, Calibre will actually split the file whenever that line appears in the stylesheet, as long as you uncheck "Do not split on page breaks" in the "EPUB Output" tab.

This should work to produce a single file for each chapter, so long as the style element you give that line to doesn't appear multiple times within the chapter. Then you would have too many separate files.

--Pat

[theducks]

Originally Posted by PatNY

ducks, Calibre will actually split the file whenever that line appears in the stylesheet, as long as you uncheck "Do not split on page breaks" in the "EPUB Output" tab.

This should work to produce a single file for each chapter, so long as the style element you give that line to doesn't appear multiple times within the chapter. Then you would have too many separate files.

--Pat

Wow!
I thought that was just a CSS attribute

[phossler]

Originally Posted by jackie_w

The Editor uses Xpath (right-click in code view) in the same way as on the convert Look&Feel page. If the existing code doesn't easily lend itself to the Xpath approach, I guess you could also use a kind-of-Sigil-split-marker-type approach by using regex to insert some <h2></h2> or <h3></h3> dummy headers (if they don't already exist), then remove them after the split.

I recently had a mess of a book, multiple chapters in a single file, some chapters spread between 2 or 3 separate files.

Some one really had to work hard to mess it up that bad.

Merged all into single file, and then split on the <h1> into separate files. Multi-file rename to 'chap_001, etc.' and done.

VERY simple, mostly because at least most of the chapters were started with <h1> tags.

[kovidgoyal]

See last paragraph of http://manual.calibre-ebook.com/edit...ing-html-files

[HarryT]

Thanks for all the helpful advice. Much appreciated!