I just read the Sigil user guide. Awesome stuff thanks.

So now I have a better understanding of Sigil and how it works, I have a question.

Say I have a fully formatted html book in one html file (actually I do, this is not hypothetical). It includes a HTML TOC, and a decent sized appendix. Also all the CSS.

Is there a way of importing it and splitting it up in to sections without having to manually edit all the appendix links and TOC links etc?

I had a look through the plugins but I could not see anything.

Anyway I am just going to make a copy of a book to mess around with and see how I get on.

This question now is not on topic for the original thread I created. Should I create a new one or is it OK in here?

Yes.

It's inherent to Sigil itself. No need to use plugins.

If you use Add File to add your existing html to a blank epub, it will pull in the css file as well (as long as the link to it is valid). After that, it's a matter of using the built in Split feature and adding the ToC semantic. Add File(s)/Splitting/Merging and adding semantics are things that are documented in the user guide.

But yes: feel free to start a new thread if you want some assistance in using these various Sigil features.

Thank you! Fully appreciated. I will crack on and see what happens.

Well that was an easy process. I have completed my mission.

Thank you for all your help everyone.

:thumbsup:

@DiapDealer — now that the User Guide has been updated for 1.6.0+, would you consider putting a link to the User Guide in the Links section of the Sigil GitHub page, perhaps before or after the link to the MobileRead? Also maybe highlight the User Guide more prominently on the Sigil website Documentation page?

Sure. It's in the important links section of the Sigil github wiki, but I can add a link to the main readme if you think it will help.

But what would you suggest for making it more prominent on the documentation page? The link is already there. In my experience, it's not a problem of the link not standing out. The problem is they simply don't read the documentation page. Or any of the pages, really. For a large portion of the people who can't find the user guide, I've found that it's typically because the darn thing simply refuses to fall out of the sky and into their laps. ;)

Ha! I didn't even remember there was a Wiki! :)

Anyway, when I went searching for a link to the User Guide for jonesyb, it took a lot of clicking for me to find it, whereas links to MobileRead were prominently posted everywhere, which is why I think people come here first and don't even realize there is a User Guide. If a link to the User Guide were posted wherever there is a link to MobileRead, more people might try the User Guide first (if that's even your goal).

For the Documentation page, if you want people to check the User Guide before asking on MobileRead, I suggest making that the first paragraph rather than the last. As it is, the first paragraph says: "Please consider the Sigil User Forums at Mobileread to be the primary resource for getting help with your Sigil questions." If I read that, I'd stop reading right there and click the Mobileread link, never making it to the last paragraph.

Also, you might attach a link to "Sigil User Guide" so that it's highlighted and clickable and make it capitalized and bold. That would make it more noticeable.

<sarcasm>What? The installer does not install the user guide and automatically open it after the install? What kind of user hostile software are you creating?</sarcasm>

If you're consistent with your chapter titles, for example, I use h2 tags for chapter titles then you can use Sigil's insert split marker (ctl+shift+return) to have as a copy of what you're going to replace/change to. E.g., insert it just after the body line. Select the entire line with the split marker, ctl+x to cut it, then go down to the search and replace and put it in the Replace: box at the bottom. Above it in the Find: box put <h2, then in the Replace: box add that same <h2 at the end of the Replace: box. So then when you do replace all, all of the <h2s become split markers with an <h2 at the end of their line (or maybe on the next line). You can then use Mend and Prettify to add in line breaks after the split markers. Then do Split at Markers (f6). If you get it right you can have the .xhtml file names match the chapter numbers.

What? You mean the thing you're supposed to immediately click through as fast as possible and X right out of? :D

:thumbsup:

Insert > Split Marker (Ctrl+Shift+Enter) places this code within your EPUB:

then pressing Edit > Split At Markers (F6) splits the HTML files wherever that code is placed.

Or, like you mentioned, this can be done on a mass scale by using Search/Replace:

Search: <h2
Replace: <hr class="sigil_split_marker" /><h2

This looks for all "<h2" (or whatever else you use for chapter titles), then a simple F6 splits your entire book in one shot. :)

* * *

Example Code:

Original:

After S&R (or manually placing splits):

After F6:

maybe this is...erm... is directed at me here.

OK I admit, I can not remember how hard I looked for a user guide.

In fact, or at all. I am not very familiar with github at all. I am not sure it even crossed my mind. My idea was to just open sigil and use it. Or something like that.

But thank you. It has been fun learning this new software. I really like it.

I also use h2s for my chapters and this would work nicely. Thanks for the tip.

This is super useful, thank you!

I converted my first book yesterday using Sigil. It and it worked great. Now I am going to go back and do all the rest of them and see what else I can learn along the way.

Thanks again