How to Convert Your Book to Get Accepted by Shops – Sigil for Dummies
Following the success of our last article on ebook editors, we decided to create an Ebook formatting 101 with the three most popular converters: Sigil, Calibre and Vellum. The series starts with Sigil, that being the one true professionals use and the one our team recommends for instant success – and the one we receive the most questions about. If you always wanted to try it but never dared, stay with me: I’m just as a beginner as you are.
(If you need your manuscript converted to an epub format before distribution, PublishDrive can do it for you: simply save it as a .docx file, and drag & drop it to the “Content file” field.)
Sigil: The first steps
While I consider myself highly computer literate, I was always reluctant to use it: why should I switch to a code based editor to create ebooks when Calibre can do it for me with one click?
But then our in-house ebook editing superstar, Csilla convinced me to give it a go. She argued that I won’t only get clean code (about which I as a reader and writer couldn’t care less) but my books will display more consistently across devices and apps. I documented my journey, so you can follow it step by step. You can download the file I made by clicking here and use it as a template. Sigil can obviously do much more than this: I just wanted to help you get started on your journey and give a guide for using it. I’ll try to use the html editor as little as possible – it really gives me the heebie-jeebies anyway.
Firstly, it took me almost 5 minutes to find the file I need to download. Apparently, you get the Sigil support for free. An open-source code app and the latest version works with Sigil too, always available on GitHub: I tried 0.9.8., the download links are at the bottom of the page. Thankfully, it's pretty straightforward to install Sigil. (Csilla’s advice is never to use the latest version, as it is usually not too stable. I learned this the hard way: it kept freezing.)
Importing the document
For presentation purposes, I decided to download a html version of The Time Machine from the Project Gutenberg. I copied and pasted the text into the big white area in the middle. It automatically asked me whether I want to keep file formatting, and I said no: I went for the plain text option. This means that all manual formatting, including italics or bold will be lost and has to be replaced manually.
If you have written a novel, it is probably in a word document. If you copy straight from the word document and keep the formatting, your code will be full of rubbish – unnecessary pieces of information. Our pro, Csilla recommends to save from word as a html file and copy that in html mode. (You can change to html view by double clicking the tab.) You have to copy your text between the two <body> tags.
Now that I have enough empty windows, I separated the file into chapters and parts of book. While I was doing this, I also renamed the files meaningfully and added semantics (both in the same menu). With the file names, make sure to use _ instead of a space, e.g. Chapter_1.xhtml. These names will function as links.
Semantics in this context only means that I allocated each file with a function as part of the book: every book has to have a cover, a title page, a copyright page, chapters (or a main text). Luckily, a description is included to all semantics items.
This was the point where I realized that the evil Sigil randomly added extra lines to my text.
Cleaning up the code
Instead of jumping off the fourth floor, I opened the html editor and pressed ctrl+f for searching. With one click, you can replace all<p><br/></p>with nothing. You can use this find and replace method to clean up your code as well and remove any unnecessary lines of code, such as font type or size.
As my next move, I marked my chapter titles as H1 in the visual editor: this won’t only make them stand out but is necessary for the TOC generator to work properly. Then I decided my book looks fancy enough already and went to edit the metadata.
Metadata and TOC
As it is always the case with Sigil, your metadata options are endless, but thankfully it explains you what to put where. The language was automatically filled in, I just have to add the title and the name of the author. You also have to specify the role of the creator: is this book associated with authors or editors? For author write: ‘aut’. The date can be the year of publication, and you should also add a publisher. If you leave the publisher empty, your distributor will automatically fill it in. (Books distributed by us will appear under PublishDrive.) You can check your metadata and manually edit it in the content.opf file:
<dc:language>en-US</dc:language><dc:title>The Time Machine</dc:title><dc:date opf:event="modification">2017-09-06</dc:date><dc:publisher>Project Gutenberg</dc:publisher><dc:creator opf:role="aut">H. G. Wells</dc:creator>
I believe there is not much left. Generating the table of contents is fairly easy and straightforward. You can even decide what you want to include in it and what not.
OK, I think I only have to add a cover image, and it is ready. For this, I have to click the big blue + and select the image from my computer. It will automatically go in the ‘Images’ folder on the left. I right click the file and set is as cover image.
I open it in Calibre to give it a last check and upload it to PublishDrive: it is valid! My first Sigil epub passed the tests.