My goal in writing this book is to give fellow authors an easy and cheap way to self publish their books in the major ebook stores as well as in paperback.
These days there are tons of ways to do this. To keep the process easy, I’m not even going to attempt to teach them all to you. I’m not going to confuse you with option after option. I’m not going to bore you with histories and long-winded explanations. I’m going to teach you exactly one simple method. It’s my way, and I think it works pretty well. Maybe I should have called this “How I Self-Publish a Book.” Oh, well, too late now. I already have the domain name.
To keep it cheap, I’ll only use freely available (usually open source) software. The self-publishing sites I’ll show you also are free to use. Your only investment will be your time.
If you have any comments, questions, suggestions, or corrections please go to the announcement post.
I’m not finished with this book yet. In fact, I may never get all the way done. So don’t be worried if you see chapters on advanced topics that look suspiciously like an outline. However, there will be enough info here to get you published.
It’s no secret. I’m not the world’s greatest author. I’m not going to even try to teach you how to write. Not fiction nor non-fiction. There’s plenty of good information around the internet about that, anyway.
Also, this tutorial is not going to teach you how to make a killing on the kindle or sell a million copies. I have tried and failed at virtually every marketing strategy out there. Maybe someday I’ll have a foolproof plan for getting your work in front of more eyeballs. If that day comes, maybe I’ll write about it. The more I read and think about it, though, the more I am convinced that the best marketing strategy is simply writing more and better books.
Now you know what you’re getting in to.
Let’s move on and take a look at the software you’ll be using to self publish your book.
Before we get into formatting and preparing your book, let’s go ahead and install all the software that you’re going to need. My step by step instructions are going to mostly be for Windows users, but most of the tools have Mac and Linux versions as well.
Pandoc will be used to help you get your work into a usable format for publishing. It is extremely versatile.
The main website for pandoc is http://johnmacfarlane.net/pandoc
To be able to use pandoc, you’ll need to:
KindleGen is used to generate .mobi files that you upload to amazon to sell for the kindle. Kindle Previewer lets you test the formatting of your .mobi file. It can also do file conversions.
Gimp is an image editing software, similar in functionality to photoshop. We’ll be using it to make your cover.
Fotosketcher is another piece of image processing software. It takes photos and makes them looking like paintings or drawings. Sorry, this one is Windows only, but there are lots of filters for the Gimp and similar programs out there. This one isn’t neccessary. http://www.fotosketcher.com
To install Fotosketcher:
A word processor similar to Microsoft Word. We will be using its coversion and layout features in the final steps of publishing. We’ll be using version 4, but whatever version you have will probably work.
One of the skills that you’re going to learn as you go through this book is Markdown.
Markdown is a way to format text files, so that they are human readable and understandable. Markdown is also a bit of computer code that takes markdown-formatted text and converts it to something else that the computer can use. So you write something in Markdown text and the computer can spit out an html file.
Markdown and similar technologies are popping up all over the web. Many websites (especially nerdy ones like GitHub and Stack Overflow) now let you enter your comments using Markdown or a slightly modified Markdown.
There isn’t much to it. You just add in a couple of things as you type your words. To publish your book, your first step is going to be to get all of the text into Markdown.
Once you’re done, the text from your book is going to look something like this:
# Chapter 1 It is a **truth** universally acknowledged, that a single man in possession of a good fortune, must be in want of a wife. However little known the feelings or views of such a man may be on his first entering a neighbourhood, this truth is so well fixed in the minds of the surrounding families, that he is considered the *rightful property* of some one or other of their daughters. "My dear Mr. Bennet," said his lady to him one day, "have you heard that Netherfield Park is let at last?"
You see some strange symbols? That’s the Markdown of it. Those markings tell you that the line starting with # is a chapter header, and the parts surrounded by asterisks should have some kind of emphasis. We’ll get to specifics here in a minute, but I just wanted you to see how easy to read Markdown text is.
For most authors, there isn’t that much different formatting that you are going to need to make a professional-looking product. As I describe the Markdown way to format different things, I’m going to tell you exactly one way to do it, even if there are two ways. Also, I’m not going to cover everything in Markdown, only the stuff I consider most important to writers.
So with out further ado, here’s your most common formatting tasks.
I made a silly example that includes all of the above formatting marks.
If you were to put the example text through pandoc (the markdown processor we’ll be using later), with the simlest settings, you get the following:
Because markdown files are really just plain text, any old text editor will do. However, a few out there have built-in features that make writing Markdown text easier.
Next chapter we’ll cover what to do if you’ve already written your book in Word, LibreOffice, or something else.
Yes, you could write your book in a plain text editor using Markdown. And maybe for your next book you will. However, you are probably reading this book because you have already written your masterpiece and now you wish to publish it. If so, this chapter is for you.
Let’s assume that you have written your novel in a word processor. The first thing is to get it from its native format into html. Fortunately, all modern word processors have a way to export.
In LibreOffice and OpenOffice click on the file menu and select “Save As.”
Then in the “Save As type” box, select “HTML Document.”
If you use a different word processor, you should be be able to find a similar function.
Once you have your book in html, it’s time to get it into Markdown. For this we’ll be using Pandoc. Pandoc is available (for free) for Windows, Mac and Linux. You should have downloaded it when you read the chapter on software.
Pandoc is a command line tool, so you’ll need to open up an old school command window. In Windows, to go to your “my documents” file and navigate until you find the folder that is holding your newly-exported html file.
Hold down shift and right click on the folder.
Then select “Open command window here.” Something similar to the image below should pop up.
At the prompt in the command window, type the following instruction, replacing the obvious parts with your own filenames.
pandoc exportedfile.html -o your_markdown_file.txt -f html -t markdown –atx-headers
Here’s a breakdown of that command:
You will know when Pandoc is finished because a new prompt will appear in your command window.
Once your file has been exported, open it up in your favorite text editor. Just scroll through things and make sure that it looks right with the correct chapter headings and such. You may have to trim out a bunch of html tags. (Stuff surrounded by <s and >s)
Your book’s cover is probably going to be the most important piece of marketing it will ever have. And of course the quality of art is quite subjective. Lots of popular covers out there break the rules I’m about to set forth.
For our purposes, we’re going to make a very simple cover consisting of a single photo or illustration with the book title and your name overlaid on the top. Even with this simple formula, you can create something that professionally represents your work.
Because it is so important, you should consider hiring a pro for this. But, if you’re dedicated to do it all yourself…
The first hurdle to jump over is to find the art you want to use as your cover image. The art can be a photo or a drawing.
When choosing a cover image, you’ll want to be sure to match your book’s genre. This doesn’t mean be generic, it means to be genre -ic.
For example, if your book is about zombies but the cover looks like this…
…then people will pass on by without a second look. Trust me, this was the original cover for my first novel, and they did. Yes, it is about zombies, but most people who saw the cover probably thought it was a depressing drug addiction memoir.
Places to go for free photos:
And of course there are any number of pay sites like istockphoto.com and Shutterstock.com. If you want custom artwork, I’d suggest going to fiverr and post a request, make sure in your request that you mention you need a commercial license for the artwork. Expect to pay at least $50 (and going up from there) to get halfway decent custom artwork done. If you want to spend even more, but practically guarantee a great result, you can spend $300-$1200 do run a book cover contest at 99designs. Or Go to The Book Designer, find their most recent “eBook Cover Awards” post here’s an example, and look through the covers and notes, finding good cover designers you can hire.
If you want a different look for your cover image, you can achive a sketched or painted appearance with very little effort. The GIMP has lots of filters with dozens of options, but my favorite software for doing this kind of thing is called FotoSketcher. It’s free at fotosketcher.com and super easy to use. Once it’s installed just start it up and open the photo you want to use for your cover.
Then play with the options window that comes up.
My favorite settings are Oil Pastel Sketch, Pencil Sketch 4, Painting 5 (Watercolor), Painting 6 (Oil Painting)
You want your cover to have a single, interesting focus. Chose one element of your book. It can be the hero, a famous landmark, a gun, or whatever you want.
Also, there should be at least one large area of the image that is the same color, or at least has very similar colors. This is the area where you’ll be putting the book title, and that text needs to be readable.
Open up the gimp and click File >> New to make a new image. In the popup window, changes the little tap from px to inches, then enter in 6 and 9 in the width and height. Or 5.5 x 8.5 if that’s the size of paperback you’ll end up wanting. In fact, let’s go with 5.5 x 8.5, because that’s the size we will make when we format the paperback pdf. Click the arrow where it says “advanced options” and enter in 300 x resolution box. The y resolution box should update automatically.
Click File >> Open as Layer and then select your chosen cover image.
Depending on where you got your main image, once you select your image you may get a little popup that says something about “convert to RGB working space.” That’s fine, just click convert.
Here’s one that’s been imported. Photo courtesy african_fi
Now it’s time to get comfortable with the text tool. You’ll find it in the toolbox dock. It looks like the letter ‘A’.
Once you select the text tool, you can change the font style, color, or size. Then you can click on the image close to where you want it, then start typing. Don’t worry if it does not end up exactly where you want it. You can always move it around after.
If you want to change anything about a block of text, double click on the “T” in its layer in the layers dialog.
You can then play with the font size, color and spacing over in the toolbox dialog.
In the next picture, I’ve spaced out the letters in my name. It’s also hard to read the letters. Don’t worry, we’ll fix that in a minute.
Click the move tool in the toolbox.
Then click on the text. Make sure you click where the text has color, then drag the text where you want it. Be careful not to click in the empty space in-between. If you click and drag that, you’ll drag the background. Anyway, make sure the text’s layer is selected and the move icon appears before clicking and dragging.
Now we’re going to put a backlight behind the text. The same technique works to make a shadow. Now, gimp has an automatic drop shadow filter, but I want a sightly different effect.
Merge all the text layers. One by one, use the “merge down” option on the right click menu in the layyers window until all the text is one level.
Once the text is all in one layer, right click on that layer in the layers dialog and select “Alpha to Selection.”
Now click the “create a new layer” button, then click OK in the dialog that pops up. Now move that new layer down so that it is under the layer with the text. In the picture below I would need to click the little green arrow.
With the new layer still selected, right click in the main image window and choose Select->Grow. In the dialog that pops up, change the text input to .050 and click OK.
Select the bucket fill tool in the toolbox.
Click the foreground color picker.
Select white in the color picker, then click OK.
Now click in the selection area to fill it with white.
Hit Ctrl+Shift+A to clear the selection. Right click on your cover and select Filters->Blur->Gaussian Blur. Make the blur radius 75 and click OK.
Experiment with these settings to find the backlight or shadow your text needs to be readable. Here’s what the title looks like on my example cover.
Because your ebook is going to be seen primarily in thumbnail form until someone buys, it’s important to choose fonts that are going to be readable at small size. Especially the title of your book.
If you want to search for fonts that you can use for free in commercial products like your self published book, check out fontsquirrel.com.
You should zoom out in the main image window to make sure the thumnail is going to work well.
Make sure you click File > Save and choose a location and name. You don’t want to lose all your hard work.
Now you’ll need to get your cover in a format that you can upload to the self publishing companies. Click File > Export to.
Choose a file name, make it end in .jpg then click Export. In the quality dialog that pops up, move slider to 94 or so.
Finalize the process by clicking Export. The big version of your cover is now done.
You’ll also need a smaller version to embed in your ebook files. Click Image > Scale Image.
In the dialog that pops up, change the height to 900 and the width to 600, then click Scale.
Then use the File > Export To, this time selecting a new name. Something like cover_smaller.jpg. Remember where you saved these two cover files. You’ll need them later.
Here’s our final cover.
There are lots of good tutorials out there for doing professional-looking text effects. Here’s a site that compiles a bunch of them so that I don’t have to.
Here’s some things to double check before you call your cover “done.”
Now it’s almost time to generate the files you’ll be uploading to the various self publishing sites. There’s just a couple of things you need to do to your book’s text file first.
A couple of steps ago you built a markdown-flavored text file of your book. Open that file back up again in your favorite text editor (Which is hopefully not notepad, but even that’ll work.)
At the very top of the file, add a line that starts with a percentage sign and space followed by the book’s title. Then hit enter, put a percentage sign, space, and then your name. There should be no blank lines in-between lines of meta data. Separate this meta data block from your first chapter by one blank line. When you’re done, it should look like this:
% The Life and Adventures of Robinson Crusoe % Daniel Defoe
If you want to include a copyright date, follow that same pattern on the next line, so that now the top of your file looks something like this. The © part will insert the copyright symbol in your published files.
% The Life and Adventures of Robinson Crusoe % Daniel Defoe % © 1719
Now, go through any images you have in your book and put them in a sub directory called “images” and make sure you update the references to them in your text accordingly. This is not strictly necessary, but it really helps for organization.
If that’s not clear let’s say your book is called “Masterplan.” Here’s the directory structure you need for your project.
...\Masterplan\Masterplan.txt ...\Masterplan\images\ ...\Masterplan\images\image_001.jpg ...\Masterplan\images\image_002.jpg
Now move the cover file you made into your images directory and rename it “cover.jpg”. Make sure you use all lower case. Again, this is not strictly necessary, but will make your life easier later on.
Now you need to do a “find and replace” to get rid of smartquotes and other characters that can mess up some text-processing software. If you try to run pandoc on your file and it bonks, it is almost certain that you have strange characters that are messing it up.
Here’s a list of common things that need to be replaced.
To make your life a little easier, I’ve built a little online app that cleans most of these up for you. You can find it at: http://storyhack.com/how-to-self-publish-a-book/cleaner
And what if you happen to want smart quotes in your published files? Do not worry. Pandoc will automatically add them back in to the published files when the time comes.
Here is a project that you can unzip and use to test things out, or at least see what a project should look like.
Now it’s time to start making the files you’ll actually upload to the various self-publishing sites.
Now it’s time to generate the .epub file. The .epub file will be used if you decide to publish directly through Barnes and Noble, as well as a few of the other ebook publishers. Before you try this, make sure that you have pandoc http://johnmacfarlane.net/pandoc/ installed.
Open a command window by using the file explorer to find your book’s directory, hold the shift button and right click on it to get the expanded menu, then click on “Open command window here.”
You’ll get an old school command window that’s already in the directory you need.
Here’s a template for the pandoc command you need to type in.
pandoc -f markdown -t epub --epub-cover-image=images\cover.jpg -o final.epub --smart --toc --epub-stylesheet=epub.css inputfile.txt
Then hit enter.
Bam! Your epub is created.
Here’s what the different parts of this command do:
pandoc: the pandoc executable. -f markdown: tells pandoc that your input file is in markdown formatted text. Pandoc would probably figure this out on its own, but better safe than sorry. -t epub: tells pandoc to create an epub file. –epub-cover-image=images\cover.jpg: use the indicated image as the cover. -o final.epub: name the output file. -–smart: convert all the striaght quotation marks to smartquotes. Also fixes apostrophes and some other stuff. –toc: generate a table of contents. It uses all of your markdown headers (see markdown notes below) –epub-stylesheet=epub.css: This tells pandoc to use a custom css file to style the text in a way that looks professional. I'll link to the one I use this in a moment. In this case epub.css would be the name of the css file. inputfile.txt: replace this with the name of the your book text file.
I currently use the epub css starter kit file. It can be found at https://github.com/mattharrison/epub-css-starter-kit.
I’ve copied and renamed just the css file from the kit here: ./files/epub.css Note that if you just want to put ‘epub.css’ in the command above, you’ll need to copy the css file into the same directory as your book.
The css file is released under an MIT licence, so you’re good to use it in books you plan on selling.
That’s it. Like I said, your epub is done. I told you this was easy.
If you are planning on publishing more books in the future, you may want to put the epub.css file in a easy to remember directory, for example C:\SelfPub\. The section of the pandoc command for the css would then be
Once you have an epub file, building a mobi file is easy. You will use the .mobi file when you publish your book for the kindle store. To do this, we’ll use a program called Kindlegen. It’s written and distributed for free by Amazon.
You can download it from: http://www.amazon.com/gp/feature.html?docId=1000765211
Amazon provides Kindlegen as a zip file. Once your download completes, right click on the zip file and select “Extract All.” Then click the “extract” button in the popup window that appears. Windows will put all the files in to a directory called “kindlegen_win32_v2_9” or something similar.
Copy and paste the kindlegen.exe file from the place you just unzipped it to the directory where you have your epub file.
Like I described last chapter, ctrl + right click on your book’s directory and select “Open console window here”.
In the command window, type:
replacing “yourBook.epub” with your book’s actual file name.
Some text will whirr by for a bit and your mobi file will be created.
What to do if you get an error E23028
Sometimes kindlegen will fail. On the second to last line or so it will say Error: E23028 or something similar. There’s not much info online about it and I can’t really tell exactly what is causing it. However, it seems to only trigger when your .epub file is in too deep of a directory. For example C:\Users\Biff\Dropbox\Fiction\Short\The_Cradle\publish\cradle.epub. See how the file is 7 directories deep? I don’t know what the limit is that causes the error, but if you get this error, there is a workaround. Just move your epub to a directory that is less deep, for example C:\SelfPub and then run the kindlegen ccommand.
Now, moving that file is a pain in the butt, so let’s make it a bit easier…
That was pretty easy. However, copying around the kindlegen file every time you want to make a book sounds like unnecessary work. Let’s make it so you don’t have to do that.
Now when your are in in your book’s directory, you can type:
But we can make things even one step easier.
The “Path” in windows is a list of places windows looks for a file or program when you type it in to a command line.
By putting kindlegen’s directory on the path, you’ll be able to just type “kindlegen yourBook.epub” without copying around your kindlegen.exe file. I would suggest moving the kindlegen program to C:\SelfPub\ just like the custom css file, then adding the C:\SelfPub directory to the path.
There’s a lot that can be said about a book’s interior design, about fonts and gutters and ems and all that. If you are interested in all that, go get a copy of The Elements of Typographic Style. I’m going to assume that you don’t care about all the specifics, and what you really want is to produce a good looking layout for your book.
So in this chapter, we’re going to produce a pdf suitable for printing a 5.5” x 8.5” softcover book through CreateSpace (or others that accept that size).
This is a two step process. First, we’ll use pandoc to create a LibreOffice .odt file. Second, we’ll use LibreOffice to make the pdf.
To do this you’ll need 2 template files. Download them and put them in your c:\SelfPub\ directory, which by now I hope you’ve made. Here are the files:
Now, open up a command window in your book’s directory, using the steps I’ve described before in the beginning of the chapter called “Build an Epub.”
Here’s the command. Just replace the parts that say “your book” with your book’s actual filename.
pandoc yourBook.txt -f markdown -t odt -o yourbook.odt --reference-odt=c:\SelfPub\paperback.odt --smart --template=c:\SelfPub\paperback.template
Now start up LibreOffice, click “Open File” and select your newly created .odt file.
Once the file is open and ready, click File > Export… (Not Export as PDF…)
Select PDF - Portable Document Format as the file type, change the name of the file if you want, then click save.
In the PDF Options screen that comes up next, make sure you check the box next to PDF/A-1a. Even you choose to use the automated process later, you’ll need to make sure this option gets checked at least once. LibreOffice will remember this setting, and this is the only way to set it.
Click Export and LibreOffice will work diligently on creating your shiny new print-ready PDF file.
Does this seem like too much work to do? Don’t worry, there’s another way. I’ll cover it when we get to the chapter on automating the process.
This chapter still needs to be written, but here’s the gist of it.
Also, Createspace has a cover maker where you can import the front cover and easily add the spine/back text if you don’t want to try doing it in GIMP. In fact almost all self publishing places have a cover creator function these days.
Now we’re going to talk about creating a Microsoft Word document, specifically formatted so you can submit it to Smashwords.
This one is a two step process, very similar to producing the pdf. We’ll use pandoc to make a libreoffice .odt file, and then we’ll use LibreOffice to export a word .doc file. To do this you’ll need 2 more template files. Download them and put them in your c:\SelfPub\ directory, which by now I really hope you’ve made. Here are the files:
Open up a command window in your book’s directory (You shold be good at this by now), using the steps I’ve described before in the beginning of the chapter called “Build an Epub.”
Here’s the command. Just replace the parts that say “your book” with your book’s actual filename.
pandoc yourBook.txt -f markdown -t odt -o yourbook.odt --reference-odt=c:\SelfPub\smashwords.odt --smart --template=c:\SelfPub\smashwords.template
Now start up LibreOffice, click “Open File” and select your newly created .odt file.
Once the file is open and ready, click File > Save As. Then in the file chooser, where it says “Save as type:”, select “Word 1997/2000/XP/2003(.doc)(*.doc)“, then click the save button.
Now you have your .doc file ready to go.
This .rtf can be used at draft2digital. Pandoc can make it directly.
I do have a template to use that scrubs out the stuff pandoc will put in that you don’t need. Just put the template file in the c:\SelfPub directory like the others.
Then open up a command window (you should totally know how to do this by now) in your book’s directory and enter the following command:
pandoc -f markdown -t rtf --template=c:\SelfPub\draft2digital.template -o yourbook.rtf --smart yourbook.txt
You’ve done it all in parts, now it’s time to bundle it up and make it super easy every time you need new publishing files . All you’ll need to do is enter a single command.
First, you’ll need to make sure that you have all the templates and such that I have used up until now. Put them all into your c:\SelfPub directory
If you haven’t been downloading them as we go, you can grab them all as a zip file (including the batch file we’re about to discuss).
Download the kindlegen program and unzip it into your C:\SelfPub directory. Unless you downloaded it and put it on the path as described early on in the book. Then you don’t need to do it again.
And make sure that your c:\SelfPub directory is on the path. Here’s that tutorial for putting stuff on the path.
Finally, make sure that you have LibreOffice installed, and that you know where it is installed. (Usually something like “C:\Program Files (x86)\LibreOffice 5\program” Note that last “\program” its important. There will be a file called soffice.exe in the correct folder.)
A batch file is a text file that contains a list of commands that windows executes one at a time. Basically it is all the stuff that we’ve been typing into the console. When you get everything set up, you’ll be able to open a command window in your book’s directory, then type:
And then the batch file will do all the work for you! It will put all the exported files in a directory called “publish.” If you update anything, you just run it again and it updates all of those files.
Download the batch file. I’m going to go over all the commands in the batch file below, so you can know what it’s doing. If you don’t really care, or it get’s too nerdy for you, just skip down to “Now run the batch”
@echo on REM starting self publishing process.
The echo just means that the user will be shown everything that is going on and being run by this batch file. REM are basically comments. They don’t functionally do anything to your book, but they make the batch file easier to read.
REM create publish directory if it does not exist if not exist ".\publish" mkdir .\publish
Creates a publish directory next to your book file as a place to put all of the finished, publishable files.
REM create a temporary directory which we'll remove at the end if not exist "c:\SelfPub\temp" mkdir c:\SelfPub\temp
We have to make some intermediate files (remember the odts?) this is where we’ll put them.
REM create an epub REM epub with cover IF EXIST .\images\cover.jpg ( pandoc -f markdown -t epub --epub-cover-image=.\images\cover.jpg -o .\publish\%1.epub --smart --toc --epub-stylesheet=c:\SelfPub\epub.css %1 ) ELSE ( REM epub with no cover. pandoc -f markdown -t epub -o .\publish\%1.epub --smart --toc --epub-stylesheet=c:\SelfPub\epub.css %1 )
Lots going on here. First, the batch file checks to see if you have a cover file. If you do, the it makes sure to include it when it runs pandoc. The part that says %1 just means the first variable, or in other words the part where you typed “mybook.txt” The pandoc command is similar to what we discussed earlier in the book.
REM make a mobi SET wkdir=%CD% copy .\publish\%1.epub c:\SelfPub\temp cd c:\SelfPub\temp kindlegen %1.epub -o %1.mobi move %1.mobi "%wkdir%\publish" cd "%wkdir%"
Kindlegen sometimes barfs when you call it and you’re in a deep deep subdirectory. We solve this problem by copying your freshly made epub to your working directory and working on it there.
REM make the odt for the paperback pandoc -f markdown -t odt --template=c:\SelfPub\paperback.template -o C:\SelfPub\temp\%1-paperback.odt --smart --reference-odt=c:\SelfPub\paperback.odt %1
This makes the intermediate .odt file for the paperback.
REM make the pdf cd publish If EXIST "C:\Program Files (x86)\LibreOffice 5\program\soffice.exe" ( "C:\Program Files (x86)\LibreOffice 5\program\soffice" --headless -convert-to pdf:"writer_pdf_Export" C:\SelfPub\temp\%1-paperback.odt ) If EXIST "C:\Program Files (x86)\LibreOffice 4\program\soffice.exe" ( "C:\Program Files (x86)\LibreOffice 4\program\soffice" --headless -convert-to pdf:"writer_pdf_Export" C:\SelfPub\temp\%1-paperback.odt ) cd..
YOU MAY NEED TO CHANGE THE ABOVE A TINY BIT This looks for Libreoffice in the place it is by default installed. The “IF” statements check for the last 2 major versions (4 & 5) of Libreoffice. If you have a super old version, or you installed it somewhere crazy, you’ll need to change that.
REM make the odt for the smashwords doc pandoc -f markdown -t odt --template=c:\SelfPub\smashwords.template -o C:\SelfPub\temp\%1-smashwords.odt --smart --reference-odt=c:\SelfPub\smashwords.odt %1 REM make the doc cd publish
If EXIST “C:Files (x86)5.exe” ( “C:Files (x86)5” –headless -convert-to doc C:%1-smashwords.odt ) If EXIST “C:Files (x86)4.exe” ( “C:Files (x86)4” –headless -convert-to doc C:%1-smashwords.odt ) cd..
Same thing with this one, it check for a LibreOffice inastallation first, then make the doc file.
REM make draft2digital file pandoc -f markdown -t rtf --template=c:\SelfPub\draft2digital.template -o .\publish\%1-draft2digital.rtf --smart %1
Make the .rtf file.
REM Remove the temp files del /Q c:\SelfPub\temp
Clean up the mess.
Open a command window in your book’s directory, then type:
Where “Mybook.txt” is the actual name of your book’s markdown-formatted text file. You’ll see a bunch of text whir by. When it stops, you’re done! You have nicely-fomatted files suited for submission to any of the major self-publishing sites.
I’m not going to walk you through the whole process for every publisher. I’ll just point you in the right direction.
Take heart, however. All of these places are simple to use. Basically you sign up for an account, give it some info on how to pay you, and then fill out a form and upload your book and its cover. Also, I’m not including ANY vanity press-types here. You should be able to publish non-exclusively and for free to all of these.
Once again, if you have any comments, questions, suggestions, or corrections, please make them over at the the announcement post.
If you’d like to thank me, then buy one of my books, or leave an honest review for something I’ve written somewhere. Or invite me on your podcast or blog. Or give me a high five next time you see me.