Was there a time in which anyone inventing new technologies was stoned to death for violating tradition? I imagine there was. And every time I have to deal with a new battle of proprietary products I start looking for something to throw.
Don’t get me wrong, I do not idolize old technologies (with the exceptions of the bound book and a manual transmission in my car). I’ve lived with oil lamps and wood burning stoves and outhouses and having to haul in water. I’ve written with a manual typewriter (it’s sort of a printer/keyboard combo without a monitor and very limited editing capabilities, primarily involving the crumpling of paper). I’m not someone who misses the sounds of clicks and crackles on vinyl or the hiss of tape. My desk no longer sags under the weight of a CRT monitor. Et cetera.
I do, though, tend to embrace technology when it has stabilized a little, when one developer’s offering has won the battle in the market place and we can all settle down to enjoy the content rather than fussing over the medium.
This has not yet happened in the world of electronic publishing. The primary forms are: EPUB and its variants; interactive PDF; interactive magazines; and HTML. I think the only format that works on all computer platforms and on almost all mobile devices is HTML. At a glance PDF also seems almost universal.
My first foray into both reading and production was overly optimistic. ePublishing with InDesign CS6 by Pariah Burke is an excellent work, digging rather deeply into things not exactly specific to the book’s title, with an abundance of information and tips. At the time I was looking into buying his book I was also looking at Digital Publishing with Adobe InDesign CS6 by Sandee Cohen and Diane Burns. Cohen and Burns’ book looked as though it did little more than walk you through the InDesign menus. This is more or less true, though there are a couple pages in their book that I wish I’d read (pages 224-225). Burke has charts with the pros and cons of each format and spells out their limitations. Unfortunately he’s not really looking at the market and what is typically being supported.
For instance, the EPUB: version 3.0 supports more layout options as well as audio and video. Very encouraging. Cohen and Burns point out that very few e-readers or mobile devices recognize EPUB 3.0 and, to date, that most of the electronic book sellers do not market it. (I think my next project will be a new collection, a dream log, created in both versions of EPUB and probably PDF. I’ll post them here, but until I get a website of my own this will be the extent of availability. And that’s another problem for independent publishers and do-it-yourselfers: where to publish and how to make your work available to as many devices and operating systems as possible.)
On the surface PDF would seem to be the ultimate format for an electronic book. You can do almost anything with it, it’s been around forever, and almost all devices and operating systems can open it. But there’s the catch: often they can only open it. Cohen and Burns have a long list of things that don’t work, for instance in Macs and mobile devices. Hyperlinks usually still work but multimedia and buttons only work on your PC (I found this to be true on my NOOK HD as well as on my partner’s iPad3, and I’ve gotten reports from friends that my first foray was a bust on their Mac laptops). Except on a PC an interactive PDF is likely to be opened as a flat, printable PDF (your basic, boring user’s manual-type PDF). If you’d gone ahead and created a printable PDF your images would at least be higher quality.
Interactive magazine is very interesting and very versatile, with all kinds of interactivity, linking, multimedia, and viewing options. Two catches: one is that, at present, they are not viewable on computers, just on tablets (both reference books were saying the same thing); the other is that you have more hoops in terms of processing and integration to create an app for your publication and potentially much more work and expense. For instance, to create an app for an Apple readable publication you have to have an Apple computer. I don’t think I’ll be creating any kind of interactive magazine for years to come.
What about HTML? It’s capable of doing just about everything the other formats are promising, and maybe more. It’s viewable and functional on everything but some of the older e-readers.…I think the problems are threefold: packaging, distribution, and know-how. I think for me packaging and distribution are the more difficult to overcome. Unlike the general subject of digital publishing creating a downloadable packet of HTML is a deeply buried sub-genre that is not featured in how-to books or videos. It’s something that’s always “outside the scope of this book”. It’s probably not much more than creating a folder, as you would for a website, and maybe ZIP-ing it. (Once again I’ll mention that I subscribe to Adobe’s Creative Cloud and its incredible assortment of software. Muse is still under development—at least as far as I’m concerned—but it’s already an extraordinarily easy tool for creating HTML. It’s a lot like using InDesign for creating print and electronic books.…I still find it doesn’t work well for adding audio files (and also video?) and that I need to do that in Dreamweaver.)…I have no idea how to tackle distribution. None of the online bookstores market HTML books. If they did we’d probably end up with another proprietary nightmare (for instance, even though EPUB is a common format Amazon’s Kindle will not read it, you have to convert your EPUB to their file system).
So, yes, I will keep working through these issues. And, yes, I will keep you posted as to the results.
In the meantime, I’m having vicious fantasies of throwing things at the developers of proprietary systems. I’m more of a mind to pelt them with our ever-dwindling supply of Twinkies than with stones.