Horse eBooks

For the last week I’ve had no phone line, no internet except that which comes over the ‘smart phone’. Holy Shit how do people ‘consume’ through that tenuous porthole? Here’s me holding the phone up in the air trying to catch a reasonable WiFi signal, just so I can maybe see 5 words at a time from a ‘mobile’ news site – which is bowdlerised to the hell to show only ‘popular’ news items. No wonder so many dumb-ass millennials if that’s their online experience.

Anyway – it’s relevant to the topic at hand – what is ‘a book’ in this year 2015? What will ‘a book’ be in 2025? This really should be of interest to budding media designers, who spend too much time creating content and not enough worrying about publishing it. I’m starting a course on this topic because it makes no sense to keep teaching people how to animate for film and TV. That’s like teaching how to hoist sails on a long ship. Good luck on the high seas matey. I am no expert in electronic publishing, but then again I got the gig teaching ‘film studies’ 7 years ago from being a musician, and no complaints.

There will be paper books, they will be expensive collectables, like vinyl. Never mind that foppery. There will tablets, watches and perhaps eReaders, although the most recent Kindles seem to announce death of the purpose designed reader. You would hope that the book would not just be a flow of endless text pulled from a word processor, and would in some way respond to the potential of the device with sound and animation.

In 2011 the ePub3 format finally took on fixed text and multimedia. But in 2015 most eReaders still do not properly reproduce this format.

Obviously Apple got sick of that shit and Embraced, Expanded and Extinguished it into iBooks. You can’t blame them for getting tired of waiting, in fact you have to admire their snappy Hugo Boss uniforms. But at some point the iPad will no longer be the Fuhrer, and iBooks will be a dead end. ePub, like HTML5, is a mongrel, but it’s the mongrel we have to adopt.

Most of Apple’s shenanigans have to do with punching Adobe in the face enough times to try kill it, but you can’t kill that which does not live. Example – having been punched for Flash, Adobe built a tool called Edge Animate that creates Javascript animations. People build these into iBooks. Apple updates iBooks with a kill switch for Edge. Adobe updates Edge with a cloaking device. I am mainly on Adobe’s side because at least they are building a tool, whereas Apple is breaking it. Flash may have been too hard on the first iPads, but that’s turned into an ancestral dispute.

My students need to publish visually dense books that represent artistic folios, and that means InDesign. It will make ePub3 as well as PDF, which is a strong format for print publication and archives, but a little too heavy for portable devices. You can also get a HTML5 website out of it, which might equally be a book in 2025.

Under the hood the ePub is an XHTML file, the format that lead to the great HTML rebellion (in which the W3c tried to move the community over to clean and tidy XHTML only to have outsiders instead propose the messy and forgiving HTML5 spec.). Sadly that means they preserve a religious schism that has since healed, and makes hand scripting difficult. An eBook also uses Scalable Vector Graphics, while HTML5 avoids this heavy computation. All up it’s the kind of file zoo that existed all over digital media back in the good old days.
Of course there are many more things that you can do on a pad that have artistic merit. If they want to dip into objective C then it’s their private hell. Some students might want to make ‘apps’, which run on watches. Bless them, I do not know how you can convey important things on a watch.

Will we make 2025 books? Will they be good books? Can we start a dialogue between engineer and artist?

Comments

No comments yet. Why don’t you start the discussion?

Leave a Reply

Your email address will not be published. Required fields are marked *