Showing posts with label Sigil. Show all posts
Showing posts with label Sigil. Show all posts

Friday, May 16, 2014

How to Build a Public Domain (Self) Publishing Assembly Line

Publishing public domain books means volume and repetitive tasks - an assembly line.

Publishing books on an assembly line basis is possible in self-publishing.
(art credit:Tobias Mikkelson)
A one-person publishing "empire" is possible these days. Regular passive income can be made from re-publishing public domain as long as you:
1) Add value.
2) Market effectively.
3) Stay focused.

The efficiencies of scale work here. As a single person (or small group) it's best to work in batches.

A project I'm currently involved in has passed the testing phase (28 books to 5 distributors) - sales are quite good, which means it's time to broaden the project.

Elsewhere, I've dealt in why this is possible, why it's profitable, specifics necessary to public domain publishing itself.

Today, let's organize for regular production.

0. Overview: we are building ebooks as the cornerstone, since in many cases these books have only poor-quality versions out there. While we also create the hardcopy version, the ebook version will have the links to send people to your website and also to the hardcopy version. You can do far more search engine marketing more easily to a digital product than a physical one.

We work in batches so that you can get some done and then do some more, and so on. If you give yourself a hundred books to publish in a certain niche, it can get tedious to do more than a few at once. A week doing each step could get monotonous. So set yourself a target for a handful of books published all the way through for that week. The next week, you can take the next set, and so on.

Note: You should do all the steps below to every distributor you are going to be using at least once. That way you can verify each step and adjust your templates as needed. You'll be tweaking as you go, but start off on the right foot with correct files - so you don't have to correct several dozen files which weren't created right originally. Each distributor is slightly different. Now that Lulu won't distribute public domain books, you are distributing to iTunes and Nook on your own. The other major ones are Amazon, Kobo, GooglePlay, and Leanpub. (See my other posts for specifics on each - as well as "Just Publish!")

00. Best is to set up a regular slot for uninterrupted work. Because it's work and you have to focus. Except for the cover, there is very little creative work here. It's more a point of digging a ditch, figuring out how many feet you can dig each day. Don't allow distractions, set daily goals and meet them, much as Stephen King and other writers simply crank out 2,000 words each day or else. Clock in, do your job, clock out. Move on.

1. Amass a selection of public domain books in a certain area. This is one of the points to adding value. You are going to be marketing these books newly, banking on either their content or their previous "well-known" status to gain your own sales.

You want the best-quality books you can find, as this will speed up your editing. Right off the bat, let's get one thing straight. While versions come and go, when a book is in the public domain, it belongs to everyone. In a later edition which has been edited, only the edits belong to that editor as copyright-able. The original text is still free to use. (See Wikipedia article on Derivative Works. This is not legal advice.)

I've found that quality ebooks are the easiest to edit. Sometimes the PDF's are created such that they have line breaks after every line, so you have to do a massive search/replace with a text editor to solve this. Time-consuming, and not often accurate, so requiring extra cross-check steps to ensure quality.

But, isn't this a rip-off? That's your value judgement. A lot of people put a lot of work into editing public domain books into shape. They are much appreciated. I link to my ebook sources all the time, and contribute to them as well. Even Gutenberg says that if you are going to use their books, ensure you take every mention of them out for trademark reasons. The point is adding value. There are literally hundreds of sites out there offering free ebooks of one type or another. Add value to make your versions stand out. Attract only paid readers, and become their go-to choice for these. You can always make derivative works which are even more helpful. Collected works by a single author in a sub-genre is one example. Study guides are another. Making it more possible for people to access and appreciate out-of-print public domain books is valuable in and of itself. People pay for quality. Creating a series of books in a certain area (like copywriting classics) is quite valuable, compared to the maze of misleading texts in this area these days. Always, always add value.

Many of the machine-produced ebooks have errors in them. So finding sites which offer versions which have already been edited are best - though sometimes you have no choice, particularly in long-tail niches.

1a. Select a logical batch to work on. Example: Out of a pile of fiction books, pick a genre, then subdivide that by author, etc. In a mass of fiction works some genre's (Romance) are more popular than others. Self-Help and Biography are more popular in non-fiction. Starting with a batch of these (selected Jane Austen's works, then the Bronte sisters, for example) would be a simple one. Or simply take the top 10 bestsellers, then the next 10, etc. so you can see an immediate boost in your income.

Long-tail niches are different. A site with old machine manuals might have books divided by brand or by type of equipment.  The books for a self-help author site could be divided into batches by author, school (New Thought), or technique (Affirmations).

2. Build a landing page for this set of books. We want to be able to send people to a site for "additional materials and related books," as well as being able to have a specific page where they can buy the books with all the links on it. If you are doing a handful of books only, then you can create a landing page for each one. A series could have a landing page for the set.

At the extreme front and back of each ebook, there is a link where you send people to that landing page. First and last thing they see - which will help them to act. You want to leverage any buyer of a single volume into a client for the rest.

At this stage, you merely set up the landing page. Later, we'll flesh it out with the cover, description and links. Building this at the beginning so you can easily link to it as you go, then come back when your book is published to update the landing page itself.

2a. Set up a template for the cover. Using GIMP, it's simple to create this in editable layers so that you can change out images and titles, etc. as you go. Create the master template at this point, then "save as" the specific book you are working on when you get to this.

3. Edit this batch into shape. Easiest production line is to use Calibre to convert epub versions to HTML files. Then open this in LibreOffice (or your own doc editor) and save in their native format. This has to be done on a one-on-one basis, obviously. But the steps are very similar and are actually less tiring to do several at once, as you can import the settings from one document to the next.

You do add the links at the front and back at this point to your landing page. If you have several books, you can link them with on-page anchors (Ex. "http://yourdomain.com/landing-page.html#anchor") so when they click they go to that specific part of the page to buy.

3a. Export the epub and test. This is by Sigil. You do an epubcheck to see if it will pass. I've only ever had a single book rejected (out of literally hundreds) which had earlier passed this check. That one turned out to have a very unique filename on it which was fine with Sigil, but not with Lulu.

Now days (and I haven't been able to do this on the MAC, and forget Windows...) I use another step of opening it with Calibre's editor, which will correct oddball filenames and often gets it into shape so that Sigil passes it right off. It's an extra step, but Calibre will correct mass errors that I've had to edit by hand in Sigil, which is painful.

3b. Create the hardcopy version. Save as a new file, then export as PDF. LibreOffice will automatically embed the fonts and produces a file which Lulu is happy with. We are using Lulu to publish as they have been doing it longer than anyone else, give free ISBN's, and are not subject to Amazon discrimination by independent bookstores who won't carry a CreateSpace edition, as it's owned by Amazon. CreateSpace has had to constantly play catch-up to Lulu.

You want to base your template off what is acceptable in Lulu. I usually format to trade-paperback, which is the same as hardback. Or rather that a 6x9 paperback can also be published as a hardback. Both versions get their own ISBN (required for hardcopy books) and will also add more authority (and sales) to your ebook when you do.

3c. Amazon has specific requirements to ensure they don't have duplicative files. These are linked on that step of their submission - but are essentially adding additional, relevant images (at least 10) or an annotation.

4. Create all the covers for this batch. This is a different form of editing, and will get faster as you repeat the actions as one set. Each one is different, so don't get into a scene of rubberstamping them.

If you want, out-source this, but ensure you aren't busting your own bank. Many public domain books will not sell well, just like they never did to begin with. Some bestsellers will sell regardless of who re-publishes them. Like the legacy publishers, the handful of books which sell really well will pay for the production of the others.

There are requirements for cover size, such as being a minimum of 1000 pixels on the shortest side for iTunes. Your template should take this into account, so that you don't have to go back and resize each one.

5. Fire up Calibre to record the meta-data as you publish these. You'll want to import all your books in all their versions into Calibre as well.  This will come in very handy for exporting a batch of books to GooglePlay, where you have to rename them by ISBN for submission.

6. Taking one distributor at a time (and starting with Lulu) publish the batch. We start with Lulu to test each book for inclusion into iTunes and Kobo. This is also where you can get a free ISBN. If it passes here, then you're set. Lulu will check for correct titles and files. At the end, you want to make sure you uncheck distribution to anywhere else. Saves you and them time.

The reason for the ISBN is to make searching for these easier. None of these distributors require ISBN's, actually. They all assign their own number to the book. You can (in all cases except Amazon) search by ISBN, so this is a template of links where you only have to change a single number in the code to have it work for each additional book.

6a. Submit your hardcopy version to extended distribution, so it will go through to Amazon and everywhere else. This means you will be buying a proof. Note: In doing this in batches, don't "check out" until you've published all your hardcopy books - this will save you shipping costs.)

Again, record this (required) ISBN in Calibre. (Note: Again, each distinct version of a book requires its own ISBN - ebook, paperback, hardback, audiobook, etc.) Most of the distributors (not Lulu or Amazon) actually encourage you to enter the print ISBN along with the ebook's. For GooglePlay, this is a simple way to promote both versions. (In Amazon, you need to send them an email to match up the two versions. Lulu isn't all that important in terms of actual online sales.)

You'll use the same cover as the ebook. This is efficient, it's also branding.

6b. For Googleplay, you'll upload all the ebooks as a batch with their titles changed to [ISBN].epub.

6c. Note: I haven't tested Leanpub extensively, so consider the below theory at this point -

In Leanpub, you are going to actually re-edit the book in their editor to get it into their system. Export the file (save as) to HTML, then open it up with Leanpub and (re)create your book again.

Other than already having several batches ready in LibreOffice, I would recommend setting up your ebook with Leanpub first. You are already starting out with an HTML file. Leanpub then gives you an epub version which is supposedly passing epubcheck. With this line, you'd then check it with Calibre's editor and Sigil just to be sure.

You will still need to open up the file in LibreOffice in order to create the hardcopy version. Leanpub creates a PDF file, and you can specify sizes of output. It is unknown at this writing if such a PDF will pass Lulu's requirements. (Tests forthcoming.)

The value of Leanpub is in creating binders and also to get maximal royalties. Buyers can actually reward you with higher royalties by increasing the price. Here you are also able to create packages with additonal data you weren't able to include in the book. Samples of other books, additional graphics, other related PDF's, etc.

6d. Publish to Kobo last as they pay the least in royalties (20%) - and have the worst policy of having to declare it as public domain if you include the entire book - even collections. Otherwise, they remove it. (Googleplay pays the most, as they simply don't care if it's public domain. So their 52% royalty is the highest except for Leanpub.)  If you get behind, you won't miss much. But do publish to Kobo, as you will get some income that you won't know you missed otherwise. Every penny counts.

7. Rinse, repeat - with your next batch.

- - - -

Notes:
Obviously, the devil is in the details. Producing high-volume, low-value shlock is exactly why distributors don't really like (read: royalty penalties) accepting public domain books. I usually publish as a beta edition, as there is no real cost-effective way to find every single error - 99.99 should be sufficient for most readers, since you make up the difference with price or other added-value.

If you have a truly original book (or one which is composed from excerpts of several public domain books) then you can distribute via Lulu to the Amazon, iTunes, Nook, and Kobo - all for 10% of your total royalties. That makes it much simpler and faster. Lulu decided not to publish public domain any longer, which now makes individual publishing required. Each distributor has their own requirements about public domain, which is apparently why Lulu changed their policy to squash this.

Since the bulk of my income comes from PD books as opposed to my original works, this will limit Lulu's sharing my future income. (They'll still get my hardcopy version income, though.)

Publishing PDF's directly to Lulu for hardcopy can be done. But you'll never be able to get an epub out of it without OCR and editing that OCR into shape. A big book can take me most of a work-week to create an epub that way. So it's not suggested compared with taking an existing epub, cross-checking it with that PDF to correct errors. But fastest is to work with high-quality epubs to begin with.

This also applies for PLR as an assembly line. I only really know that Amazon doesn't accept PLR. You don't get the royalty penalties for these books, but you also can't easily make them into hardcopy books. Again, you work with those where you get the .doc or .odt file along with .psd graphics.

I'll tweak this as I start publishing more directly to iTunes and Nook. This is based on nearly a couple of years now publishing directly and via Lulu.

- - - -

Had to get this out of my head, and to clarify it for myself.

Have fun with this.
Enhanced by Zemanta

Wednesday, May 14, 2014

How to Set Up a MAC for Self-Publishing to Itunes

Adventures in Apple-land: Using a MAC as a Self-Publishing Platform

When we last left our hero, he had made the decision - and leapt into the mist.

I ordered a MAC mini (hold the fries) and it arrived two days later. I celebrated by cleaning my desk and removing all the old hardware, cables and everything dusty.

We'll do this in steps. First, the unboxing:

Got my MAC mini shipped in two days from Best Buy - open-box discount.
Nice box from Best Buy online. Gas Duster for reference.
A MAC mini with all the stuff that comes with it. Key is that dongle which allows your monitor to hook up - and those nifty decals.
And look at all the stuff inside...
My MAC mini with leftover/spare USB keyboard, mouse and HDMI monitor. Ready to self-publish books...
All hooked up with leftover/spare everything.
Lulu on a MAC, proving the world doesn't end when public domain isn't distributed anymore.
Proof that the Internet works - from the people who made my MAC necessary.
MACs and Linux self-publishing workstations for home/small business owners.
My full set-up with the right two monitors going to my Linux box.
I connected it up to an existing monitor, plugged in an un-elegant leftover USB keyboard and mouse, and followed their instructions. It's been some years, but the clunky stuff we use in the non-Apple world looks shoddy compared to its elegant design. (Next quarter's royalty payments should give me a Bluetooth Apple keyboard, mouse, and maybe the extra RAM - this quarter's bought this MAC.)

I last used one of the old PowerMACs (15+ years ago) so the familiar startup sound took me back to younger days...

Back to business.

As I suspected, everything I've needed to publish on Windows or Linux are available for MAC. So far, anyway. I'm in the middle of downloading programs like LibreOffice, Firefox, Calibre, Sigil to see if this is all available. I've got nothing against Safari, it's just that I'm not used to it. But yes, MAC versions are available for all of these, and the Writer2Epub plug-in works as well.(See below for links and download sizes.)

The idea here is that a non-MAC user should be able to shift platforms (like how I ditched Windows for Linux.) I'd worked out a production flow which had creation in LibreOffice, and side-checking with Sigil, meta-data stored in Calibre. Firefox has always been my browser of choice (IE has always had security issues, and Chromium is fine, but not the same.)

So if a person has that production flow in Windows or Linux, they can do it on the MAC, too.

Next, in order to publish on iTunes, you have to have an Apple ID, which is fairly easy to set up, and then download iTunes Producer.

Since we are straining my "poor" overworked Internet provider, we'll let that run and get some sleep tonight.

- - - -

After coffee and breakfast: Well, the download didn't. Turns out Safari doesn't handle resuming downloads simply (takes a command line trick.) So I restarted that Firefox download and will install "downthemall" plug-in to make this happen. (With that download manager, you can restart paused/incomplete downloads.)

Again, just making it so I can use the tools I'm familiar with to get to work on this platform.

The blow-by-blow continues...

Since this is a 56mg download and my provider is currently penalizing me at their end of their month, I'm going out to do my chores now, and come back to finish this (hopefully.)

Update: The MAC has pre-configured SAMBA filesharing - nicer than out-of-the-box Linux, actually. OK. Funny enough, the common denominator is reverse-engineered Windows network sharing. Will need some more time on this to figure it out completely. Some work on this (while waiting for my downloads) showed that logging in as a remote user was easiest to get access - but is not work-safe for kids or "hacker wannabe's".

I've taken all my current files and sending them over via the network, so I can test the entire workflow. Calibre and GIMP need something to do.

(Oops - this download didn't go. Too much too fast for my poor Internet Provider, who says I've already downloaded too much, until next month's allotment, which starts in a few days.)

Meanwhile, I finally got the downloads down and, well - see below...

- - - -

What you'll need to simply get started creating your ebooks just like you did on Windows or Linux:

The iTunesProducer file is a 305mg download. Firefox is 59mg, Calibre is 84mg, Sigil 34mg, LibreOffice 190mg, and writer2epub is 1.4mg. So you may be at this awhile to get what you need. Oh - and don't forget GIMP (95mg) for doing your covers.

This means a person can easily shift to the MAC. What the MAC mini does is to make it relatively inexpensive. Anyone who has dealt with older machines usually has leftover mice and keyboards and monitors around. (USB and HDMI video - not the older plug-in versions - although I have a VGA adaptor coming...)

[Update: The Sigil initial download wasn't accepted by the MAC - until I Googled the phrase and found this solution. With that window open (security preferences) it will allow you to install the dmg package that just failed, one at a time. (No need to permanently set yourself wide open.)]

[Update 2: Hold down the control key when you click open, and you get the same "Are You Sure?" dialog.]

[Update 3: While this could be a separate post, all you really need to post your book to the MAC is to download and install their free iTunes Producer. You manage your books in iTunes Connect (http://itunesconnect.apple.com) via most any web browser. If you are already editing it on your Linux/Windows platform, you don't have to download a bunch of stuff to get going. I use Dropbox to sync my latest version to my MAC, and then simply upload those files in the next batch I have going. I then edit or improve the meta-data through my web browser. Again, the added value of a MAC is in the A/V you're now able to create for marketing your book.]


That means we have all the tools we need to create and edit.

However, until I solve file transfer, I will be using the workflow described below. By getting all the vital tools over to the MAC, it says that a first-time self-publisher could easily use a MAC to get their books up and going. And anyone dissatisfied with Windows could make the jump to a better platform. If you need elegance, that would be the only reason to move to a MAC from Linux, IMHO. But I'm a geek down deep and have always loved to get below the hood and tinker. My MAC mini will be a very capable back-up for my dual-monitor production machine.

As I said, when I solve the file transfer (SAMBA) scene, then this may change.

Whoring the MAC to get to iTunes.

The basic summary is that I'll be "whoring" this platform, using it mainly as a "go-to girl" for uploading to the various distributors - but chiefly, this MAC will be used for uploading to iTunes and handling audio recording. Reason being that file transfer is buggy at best - until that is solved, there is no real way to get files across except "sneaker-net" with flash-drives.

One additional feature is the native ability to simply create podcasts. Yes, you can do this with either Windows or Linux, but having a second machine should make this much easier - as I don't have to move/unplug the mic. Yes, I can get good old Audacity for MAC as well. Podcasts and videos are the necessary content production needed for marketing.

This MAC didn't come with any iMovie (it's a $15 app) so it also doesn't qualify (right out of the box, anyway) to handle making audio into video. My Linux version actually came with several of these programs - again, I have those 15 years which was more Linux than Windows during that time. So creating videos is still a learning scene.

[Update: I've found most of these Linux NLE's (movie editors) are also ported to MAC OSX, so that's an upcoming adventure.]

Plus, my Linux box has dual monitors, which is a simpler work flow.

I'll get there with the MAC, but essentially it's the learning curve which is throwing rain on this parade. (Coming up on Day 3 where I should have been editing and publishing.)

The bottom line is: Yes, you can do everything I do to self-publish a book on all the various distributors on a MAC. But just because you have to publish to one distributor, doesn't mean you're going to have to publish everything from there. It's possible, though.

All these downloads will make my learning curve on this platform simpler and shorter.

An alternative work-flow

Go the Leanpub route to build your book. This gives you a tested version at the end, which should pass muster. Means you

  1. Get a MAC (mini) and set it up with all these programs.
  2. Edit your book into shape with LibreOffice, but save it as an HTML file.
  3. Next, you open that in Leanpub and tweak it online.
  4. As part of that, create the cover in GIMP.
  5. Then, when you are happy with it, publish, then download their generated epub, mobi, and PDF files.
  6. Right after that, test it on Lulu to be sure (and to get your free ISBN.)
  7. If no go, sneaker-net it over to another box to tweak it on Sigil until it passes (or fire up a virtual machine and do it there.)
  8. Then upload to iTunes and everywhere else, saving your metadata to Calibre so it's a copy/paste production.

Now you can do it all on a MAC. See, that wasn't so hard, was it?

If I were just starting out, this is the route I'd take, since that single investment in a MAC mini would pay for itself in short order.

Additional marketing goodies

The MAC started out as a desktop publishing wonder, but then quickly got adopted by the A/V crowd and never looked back. As an addition to my other workflow, this new MAC will be able to do my podcasts and video production to be able to reach a wider audience with my book projects. With LibreOffice being able to export PDF's with embedded links (Leanpub's capability for your finished book) you then have all the major formats anyone could want to find about your book - and also, to create packages of goods anyone could want. (And also do something like Tim Ferris' bittorrent marketing)

For me, I'll have a standalone solution to audio and video in addition to my book publishing. So this investment - which pays for itself in the fees I don't have to pay to any aggregator to just reach iTunes - gives me auxiliary bonuses. Before this, the mic would have to be unplugged and moved away and back when I wanted to record, which left it less than useful - and less prone for me to actually do the recording. (Not to mention that the MAC mini has no machine noise, so if I ever build a sound booth, it will fit in perfectly.)

Not bad for a bunch of leftover peripherals and a $600 box.

Hardware wars - over?

I used to mess with building and re-building machines in the old days, accepting any amount of used equipment people would throw my way. What I found was that it was burning my time with little results. Re-cobbling parts together would as often as not result in no working machine, even when I put the original one back together "just like it was."

The real scene is that producers have moved to new formats of RAM and connectors which have made the other machines too expensive to upgrade. With few exceptions, such as installing the maximal RAM you can when you buy a machine - key on Linux (Windows often won't see or be able to use the extra) - there's little additional to do.

With the MAC mini, you can go to top of the line for about twice as much, which will give you 16gigs of RAM and a monster CPU - but the question for a struggling publisher is the cost benefit.

$600 is just above what I'd consider a decent price range for a new box. Sure, I can get a machine with the same specs as this MAC Mini from Overstock or similar for maybe $300, also with no monitor (but giving me yet another keyboard and mouse) - but it wouldn't get me into iTunes. Sure, I could spend the time getting torrents downloaded of a MAC disk image which would run on a virtual machine inside my Linux box - but that's for the uber-geek.

Time invested needs to leverage into income. For the average author, getting a MAC mini as a replacement computer is quite a leap, but can result in doing everything you need. The extra $200 also means a week or so that I don't have to spend getting a machine up and running on Linux - and just as stable.

Note: In my mind, there is no reason to use Windows, if you haven't guessed this by now. Part of the upgrade was giving away my last two Windows-only machines, which were on obsolete hardware. No way to go back. (I do have XP running on a virtual machine, for a minority few programs which were only ever released to Windows platform. It's still amazing that each Windows machine has to have it's own anti-virus and firewall program,when Linux and MAC natively don't.)

[Update: I was annoyed by the lack of keyboard shortcuts. So I got a bluetooth keyboard which 1) didn't have the same look and feel - it slowed me down with errors, and 2) quit working once the original batteries went on the blink. So I plugged back in my old USB keybord (with those satisfying pushing keys/clicks) and found I could remap the "alt" key to do the same as the "command" key in Windows. As there are very few shortcuts which actually use the alt key on a MAC, it really solves the problem. (Chief short-cut I use is alt-tab - from Windows days - to shift between applications.) Situation solved - other than it takes another USB outlet.]

[Update 2: I've found that a lot of hardware which would only work with Windows (not on my Linux box) has been ported to MAC, so drivers are available. One scanner I thought was only available on XP was able to get going under a MAC, courtesy of the companies updated drivers.]

Batch production 

My current plans are to do the development of batches of books, then copy sets of epubs with the final-final versions and their covers over to a jump-drive for transfer. This looks to be the simplest, most direct, and most efficient production line. This makes iTunes the last on the block, maybe excepting Leanpub. (Even Amazon and Smashwords accepts epubs, so this is again the lowest common denominator approach.)

Out of the dozens of books I've published to date (OK, it's over a dozen dozen at this point) the public domain and PLR books sell the best. So setting up batches of these (or saving up collections until I have a batch) is simpler than some indie author writing original fiction. For that person, the best approach is to fire them out when the editing and proofing is done - and then get busy writing the next one.

Writers get paid by selling books, not by worrying over whether they are selling. "Writing feeds the soul; Publishing feeds, clothes, and houses the body - plus pays for the occasional night out on the town." It's the backbench of books which proves that theory.

- - - -

While this last section really requires a new blog post, a short analysis today (while waiting for downloads, etc.) showed me that this is the core of my little one-man-band of a publishing company.  I have a few large batches worked up for the near future, and then I'll be ready to move over to a quasi-original derivative set of hand-illustrated classic stories.

Right now, I'm learning from classic copywriters. Once I'm content with a sufficiently deep back-bench, then I'll move over to marketing what I've been creating and meanwhile doing a segue over to these illustrated children's fables.

Lulu just compounded my work-flow by forcing me to get a MAC in order to do what used to be their job.

What this will eventually do is to improve my marketing backend, as I can do a lot more A/V work with this set-up.

Now you've had another glimpse into the world of an avid self-publisher.

Yes, there's a book in your future - part of which you're reading now. Someone has to tell the story of how anyone in the middle of nowhere can create a "publishing empire" from little more than consistent, focused production over a few years time.

Stay tuned...

Saturday, January 4, 2014

The only Constant is Change - ebook publishing continues to shift.

(photocredit: Nikki L.)
Of course, I owe you an update on "Just Publish: Ebook Creation for Indie Authors" - because there have been so many changes going and coming around.

If I haven't already let you know otherwise, I've got an entire work-up on how to publish on Google Play.

That means you can make even more income, particularly since between iTunes and Google Play, you are instantly available on any smartphone or tablet out there (except the 7% of Windows Tablets...)

All is not as it was...


On catching up on some backlogged stalled books on Lulu, I noticed that my old working line-up wasn't working - it seems iTunes and B&N have both "upgraded" their standards for ebooks, so my earlier scene of simply doing the epubcheck on Sigil didn't pass muster any more.

As I'm writing, this I have Lulu directly converting an ODT file for me - and they are taking forever to process it.

Meanwhile, I've downloaded the latest update to Sigil and installed it. I'll try with another bugged file and see how this goes...

- - - -

OK, that won't do it - see this forum post: http://www.mobileread.com/forums/showthread.php?t=186306 - apparently this has been going on for awhile (April 2013) with B&N/iTunes.

Testing this: funny, my file just passed: "Validated using EpubCheck version 3.0.1."

I tried an entirely different file - passed on that EpubCheck, flunked on Lulu's in-house scene.

So this complicates the flow. Only workaround I have is to hand-edit those files to make them work. The alternative is to have Lulu do it for you, which is interminably long. In fact, searching for this error via forums gave me a free ebook Epub on Lulu Simplified by Dave Lemay - where he simply tells you to set up a Word .doc exactly (much as Smashwords says to) and then submit that.

No thanks. Way too slow for the volume I have waiting for this.

The final solution perhaps isn't nice, but it works.

The why is being too complicated.

Things you need to know:

  • Epubcheck doesn't mean anything. Lulu has had to tweak whatever they had so it will generate content acceptible to iTunes and B&N. Just as Smashwords had to do. 
  • Your Sigil-proofed file will work just fine on other platforms with its internal epubcheck.
  • Complicated files make things worse. KISS.


Searching through the forums finds that Lulu doesn't like anything above H2 (Heading 2) - How I got replicable success was to

  1. Simply scrape the text out of the original document, saving it to a straigh-text editor to remove all formating. (Yes, I know, that hurts.)
  2. Only put in H1 and H2 headings for your chapters. H3 crashes their system every time.
  3. Make sure in Writer2Epub that you fill out the publisher and date spaces in the dialog.
  4. Replace any TOC with Sigil's and then save. (While you're at it, tweak your style sheets. Remove any you aren't using.)
Then you'll be fine. When in doubt, strip it out - and try again. The simpler you can make these books, the better.

Writer2Epub will eliminate a lot of extraneous stuff, but the points on not getting about H2 on your headings is key. Don't know when Lulu changed this, but that's now the way it is.

Yes, I've got another update to that "Just Publish!" book, as I mentioned.

Summary:

  • iTunes/B&N no longer accept anything below Heading 2. 
  • Remove any H3's, etc. 
  • Format everything else with bold and italic (ebook readers don't necessarily honor indents, sometimes not even bullets.
  • Replace your Writer2Epub table of contents with Sigil, then go ahead and do your epubcheck.
  • The file you wind up with will go anywhere else.
PS. You can't just use your earlier-approved epub files. Tried that. But one shortcut is to download your earlier file, open it up in Sigil, convert the H3's to p's (paragraphs) and then recreate the TOC. Finally, epubcheck (always) and re-upload.

Enhanced by Zemanta