eProduction Jumpstart

EasyPress and Adobe highlight their best features, Joshua Tallent convinces me to buy his book, and I’m guessing no one knows which workflow is most efficient without trying them all.

The morning tech session focused on case studies of eBook conversion. First up was James MacFarlane of the cloud-based auto conversion service EasyPub from EasyPress. This web-based platform looked like it did a pretty fair job of converting files, although in a one-on-one demo the day before, there had been a glitch. McFarlane suggested starting with an Indesign file with style sheets universally applied (all of your backlist documents are totally style-sheeted right?), both character and paragraph sheets are acceptable to the system. The file is uploaded to your client portal, and you map document styles to CSS styles using a point and click interface. Then the file is automatically converted for all eReaders, except Nook, which requires an extra process.

Kiyo Toma from Adobe showed off InDesign 5.5s snazzy new EPUB export features. Lots less code junk, human readable-line breaks, no more anchoring images (woot!!!), image optimization improvements, image spacing you can set in InDesign. Lots of the #eprdctn folks on Twitter have bought the InDesign update, and love it. Is it faster than starting from scratch and hand coding your document? I’m not sure. It’s certainly an advantage to have one document for both print and web, it would make corrections and iterations easier to implement and track. Many current eBook production workflows are blends of automatic conversion and hand coding-fix ups. I’ll be curious to see how the InDesign 5.5 workflow stacks up to that in terms of cost and efficiency.

Joshua Tallent of eBook Architects suggests this Kindle workflow: ePub>remove fonts>add guide to OPF>minimize CSS>remove borders>add page breaks. Joshua was also passionate about the need for good document structure and human-readable code as the best ways to a) provide accessibility and b) future proof your documents. My last note from this session is “Buy Joshua’s damn book.” So I plan to.

One participant raised the question, “Can you just write the html from scratch like a website?” Which kind of brought the panel discussion to a halt. Of course you can. I find it much easier than cleaning up the code from Adobe 4.o, especially for a fixed-width title. Figuring out which CSS tags work well in browsers but are not supported in reading system x or y or z, that’s kind of another story. Would it be more efficient and cost-effective to use the EasyPub service or upgrade to InDesign 5.5? Hard to say. Start small and fail fast? Begin with what you know and build from there?

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: