Skip to main content

Adobe's epub format and reader

The Adobe announcements last week were very interesting, but not for the reasons most people seem to think.

Here's the real story: The most important producer of print publishing tools is backing an XML-based format for electronic delivery, by making it a (relatively) painless option after preparing something for print. This means the new electronic format can come out the kind of editorial process publishers are already using. With all the limitations that this XML format has, it's much more in reach of publishers who can't afford to change all their editorial processes in a single go.

There's been a lot of concentration on the idea that a standard format will speed ebook reader adoption. This is something that vendors like Sony are realizing is important. Is this their first open format use in electronic media?. And indeed for the long-term future, I think that this is an important issue for vendors. For publishers and businesses right now, though, the focus on new reading platforms is insignificant outside of niche markets.

The Web is the platform that matters, especially for non-fiction content. At Tizra we've concentrated on PDF as the format that most publishers have in quantity, and on making it as close to a first-class web citizen as possible: that means we don't re-implement features (like bookmarks and emailing links) that web browsers already have, but instead we create a site where those features work as usual. That also means delivering pages as embedded content in HTML (with file download as an option, where it makes sense).

With our deep XML experience, we are going to be looking closely at how to take what is still designed as a monolithic file format for delivery and "Warehousing", and really get web marketing and product oomph out of it. Disaggregating .epub files will be as important as it is for PDF, but the results will be a little more precise and considerably more flexible.

And when we do it, PDF backfile or primary content will be delivered and managed the same way as .epub documents are managed.

Comments

Popular posts from this blog

Technical Podcasts

If there is something the web as surely changed, it was the way that software engineers need to work. It is now a crucial aspect of our work to be able draw from the huge internet knowledge base out there in an efficient way to get to the right answers. Part of that information extraction is related to the keeping-up-to-date effort that every developer is required to accomplish to continue to be productive. While previous a software engineer could rely mostly on print material, nowadays we need to rely as well on content available on the net. Podcasts are such a source that can bring an amazing amount of information to the mix of knowledge one needs these days. If you are a software engineer and have not jumped into the podcast wagon yet, I suggest you do so. Here is a list some technical podcasts that we hear at Tizra: The Java Posse : a fantastic podcast on Java development. Containing news info update, analysis of tools, overall software development discussions. Software as She Dev...

Using XML to Create a Better Online Reading Experience for the American Payroll Association

Congrats to the American Payroll Association on their recent launch of XML-based publications on Tizra!  Thanks to this collaboration, APA's authoritative books for payroll professionals are now available in crisp, reflowable HTML, creating a user experience that feels like a truly digital native product, rather than a conversion from print. XML-based publishing also creates a better mobile reading experience, supports more precise search and navigation, and opens the door to better accessibility for users with low vision and other disabilities. Our partners at  Scribe  did a great job supporting APA through the process of producing the XML for loading into Tizra, and we’d definitely recommend them to anyone interested in such a transition. It’s hard to overstate what a big step forward this is for Tizra as a platform and a company. XML has long been planned for in the product's architecture, but now for the first time, we have a working example that demonstrates t...

The importance of continuous integration

Leading a team of developers in the effort of building a robust, quality software product should involve the establishment of some process and tools to assist the team effort and serve as a safety net for the errors of getting people to work together. Continuous integration is, I believe, a crucial element of that process. Introduced by Martin Fowler and Matt Foemmel (see article Continuous Integration ), continuous integration establishes the practice of frequent integration of work developed by the several team members verified by automated build and testing of integrated code within a clean sandbox. This practice is valuable for several reasons: It promotes the development of a clear process of building/deployment independent of any specificity of developer's platforms. Code that exists on a single platform only is bound to become dependent on specific aspects of that platform without anyone really noticing the dependencies until trying to port to other platforms. The existence ...