How Amazon and Apple stabbed me in the eye

Posted in think

Fred Hicks and Rob Donoghue have already weighed in. I don’t have anything new to add except possibly my opinion which I think is completely uninteresting. Facts will carry the day and this is clearly a skirmish in the war that will occupy the next several years in the publishing business. The expected (and apropos) analogy with dinosaurs and mammals has been made repeatedly. I believe I alluded to it myself last year sometime.

The only thing I really care about is the fact that I enjoy layout as an art form and the electronic book market, given the direction it’s heading, is poised to change what that is a very great deal. And that’s scary. It means that just as the tools we use for layout are becoming mature, the game is changing under them and again layout is complicated. Complicated is interesting. I’m cool with that. Just scared.

Anyway, is making me re-think Deluge as a product and that’s also a good thing because it lets me address my release fear by not releasing. It’s currently designed as a hybrid product — a PDF that’s built on a US Letter page scaffold with the recognition that some significant body of readers will want to print it. It looks pretty printed — even clever — right now. It also works as a PDF. But as it is an experiment in current electronic publishing, it seems Steve Jobs has insisted that I make it work on a third axis. Okay fine.

So, it has to work in print. It has to work as a functional PDF (that is, printed and on screen). It has to work as a re-flowable form like MOBI or ePub. ePub is a supposedly heavily supported (partially designed) by Adobe. Yet the ePub output from InDesign looks like crap by default, assuming you concentrated on making a cool looking page. Pages are primary to InDesign’s operation and yet the ePub output has no page. You have to think in terms of the “story” and ignore the page for this to work (and yes that means making images inline, which almost always sucks and a half). Okay, I can do this.

Paper and PDF are paginated. ePub (and whatever I convert to from there) is not. I want to have products cross-correlate, so I think Toph’s page insertion scheme is ideal here — at the beginning of each page, the text will contain a reference to the page number, so a reflowed version will identify each page as it would have started in the paged version. I will try to automate this with InDesign and have some ideas. This is fairly inobtrusive (compared with treating the reflowed text as canonical and numbering some fundamental unit of the text, like paragraphs, which is slicker but uglier) but not without controversy. In particular, the implicit declaration that the paged version is canonical strikes me as wrong.

Images have to go inline. That means my lovely margin usage will vanish and images will simply interrupt the text. I can cope.

Sidebars have to go inline. Lots of electronic formats support sidebars but they all suck. The problem is that there’s just not enough real-estate on screen to give sidebars the function that they have on a page — they are either completely intrusive or they are a push-button away and switch between dominant and non-existent. These choices suck. Instead I think I will re-write so that they are not sidebars. This has worked for technical books for ages. Sidebars may be mostly a gimmick anyway–I’m not convinced of their utility beyond breaking up the page and providing visual landmarks.

Cross-references have to be logical rather than literal because they need to become actual links. This is all good.

The deepest issue is one of legibility — it’s not clear to me that a single set of choices will create a legible document when printed on US Letter as when viewed on the screen in print-preview (PDF) form as when viewed in a reflowable form. I can actually ignore the reflowable version — it’s pretty much guaranteed to be legible because its presentation is reader and user dependent.  But for the two presentations that are most deeply at odds, there are serious issues. I’m pretty sure, for example, that it will pay off to use a larger typeface than I would for print-only target because the sorts of devices used to view PDFs are myriad. But this is likely to make print ghastly and paper-intensive unless the intended print form is two-up or four-up. Can I make that assumption? I suppose I can declare it in the product.

The bottom line, though, is that doing layout just became a very different kind of job for RPGs. Novelists have it easy — one typeface and every page the same shape. No diagrams, no tables (ugh tables — that’s going to suck too), and one typeface. But with all these things there are so many opportunities for the RPG layouterizer to make elegant and beautiful choices. Most of which are undermined by the new technology. I think, though, that honestly Apple and Amazon have together changed the landscape.

It will be years before things shake out, but it’s clear that the shaking has started. And I am in a better position to be a mammal than a dinosaur. But fans of that analogy should keep clear in their heads that we still also have a lot of birds in this modern world. Recall that when mammals started eating their eggs, dinosaurs took to the air.

Predicting the future is a mug’s game. The best you can do is react, especially if you’re well positioned to do so cheaply.

–BMurray

Posted by halfjack   @   1 February 2010

Related Posts

Like this post? Share it!

RSS Digg Twitter StumbleUpon Delicious Technorati Facebook

4 Comments

Comments
Feb 1, 2010
13:57

Well, you don’t HAVE to sell it via Amazon or Apple. I’d think for a specialty print product (and I’ve got some experience in the field), PDF distribution is a good choice (for electronic distribution). You can sell through IPR, RPGnow, Lulu — and, most importantly — through your own site (it’s dead easy, and maximizes your profit). You don’t have to get into the Amazon or Apple eco-systems to sell RPG content.

As far as reading that PDF book goes (printing aside), you can view it on any computer (desktop or laptop) and you’ll be able to view it on the iPad and the Amazon Kindle DX.

Hell, I’m getting an iPad mainly so I can read PDFs in a larger form factor, especially RPG books. In color, too. The Amazon Kindle DX can display PDFs at something like full size, too (though in black and white).

Reading nearly any sort of formatted reading content (esp. with graphics and tables and whatnot)on the iPhone (or other smartphone) is an exercise in frustration, even though you CAN do it.

Epub will evolve, and perhaps other, similar sorts of “flowed” text content will emerge, but PDF is still a viable and useful format, even in the New World computing age of the iPad.

Don’t give up on it yet.
I’m looking forward to having Diaspora on my iPad one day soon (in addition to the print version I already own). Deluge, too!

Feb 1, 2010
14:06
#2 halfjack :

Well, first, Deluge is an experiment in technologies so it’s not an indication that I intend to sell through Amazon or Apple. It’s just that all the kafuffles surrounding these companies are signposts on the personal publishing highway, so it makes sense to pay attention.

PDF is the primary form for Deluge for exactly the reasons you describe, but I don’t want to box myself in — there are layout choices I can make that will make other forms (reflowable ones, notably) more or less complicated going forward. So part of the experiment is to find a PDF layout that will turn into a reflowable form handily and also print handily. And, ideally, also cross-correlate.

I think we’re stuck with PDF for a while, but even there I can build PDF-for-screen that is radically different than PDF-for-print. The screen target PDF is also intrinsically closer to the reflowable form. The print target PDF is the prettiest by far.

Feb 1, 2010
22:22
#3 Ian Borchardt :

The PDF format was never really designed for e-publishing, especially dedicated design in e-publishing. It’s designed to package a printable document in a portable format. And incidentally, allow it to be viewed on screen. And, after all it’s over 15 years old, even with refinements and upgrades there is only so far you can go with the base architecture.

I do think that the next step is going to be a CSS type system which separates content from styling. Your device will load the correct style file to display the work appropriately for the device format. A collision between web-design and physical layout philosophies.

But I also think that that is only a midway step, and eventually text-books (in which category I include RPGs), will have more in common with an interactive app driving a content database than a text document. Something that follows an information architecture more compatible with how people actually use these books, which can be decidedly non-linear (at least, after the initial read-through). [Then again, this last could just be my wishful thinking, and it probably won't be something developed by the RPG industry. <grin>]

Feb 2, 2010
00:36
#4 halfjack :

Yeah, Ian, if you head back a couple dozen posts you’ll see I’m the choir on that front. :D PDF is basically an encapsulated print preview and so seems like a dead end to me. Still it’s the dead end of choice.

Leave a Comment

Name

Email

Website

Previous Post
«
Next Post
»
Powered by Wordpress   |   Lunated designed by ZenVerse

Bad Behavior has blocked 58 access attempts in the last 7 days.