One EPUB formatting question which I recently got interested in was: how to create a bilingual poetry book? That is, if you want to have a book of poetry in one language with line-by-line translation to another language (to aid a reader who knows the language of the original not too well), how do you do that? In a paper book, a good and well-tried solution is to have the texts in two languages placed on the left and the right page, facing each other. For an e-book, unfortunately, that approach cannot be reused; in particular because with an e-book you usually have only one page visible at a time. Splitting the page into two columns may be acceptable for short citations, but to format a whole poetic collection in this way would be inconvenient, for the columns are somewhat too narrow in this case even on bigger devices.

Here I describe a solution which I find acceptable. Though the problem in question is a rather narrow one, some details of the approach may be useful for other goals as well. In the examples I use the first lines of Catullus 1, with both the original text and the translation taken from the corresponding wikisource page.

There is, in fact, one special reason why I like to use passages from the Roman classics in EPUB examples. An e-book, which is scrolled page-by-page and remains open on the page where you stopped reading it last time, is in these respects amazingly similar to a papyrus scroll, which was what Catullus and Horace and Virgil used. Just think of that: when you are reading The Aeneid on your smartphone, your experience is in a way much closer to that of the original readers than what the generations before us had with codex-format books. Anyway, back to the topic…

The formatting of the poetic lines is done here in the same way as in my earier essay,
with a few small alterations: using dev rather than p as the tag for a poetry line (as proposed by Lee Passey in the comments) and adding page-break-inside attribute to avoid a page break in the middle of a split line (in the readers which support this attribute, certainly). I will not use line chunking here, in order to keep the examples simple and focused on the present topic. The entry in the style sheet goes as follows:

.poemLine {
  font-size: 1em;
  margin: 0;
  border: 0;
  padding: 0;
  page-break-inside: avoid;
  margin-left: 2.5em;
  text-indent: -2.5em;
}

The obvious good thing about poetry in our case is that it is split into fixed lines. What if we just place the translation below each line of text, formatting both language versions using the same poetryLine style?

The result is rather unreadable, though the direction is probably not bad. Is there something small to be improved? Sure. Let’s just make a separate poemLine2 style for the translation: almost the same, but with one addition:

color: #808080;

Now the result looks this way:

Suddenly, I almost like it. My only objection is that if the user needs to consult the translation only occasionally, its constant screenspace-consuming presence can be annoying. Stating the problem in a more abstract and general way, it would be nice to have a possibility to create several layers of text in the book (e.g. original and translation in our case) switchable on and off at the user’s will at any time.

Such a concept of an e-book may be useful in more than one case. Imagine reading an abridged verion of a history book, switching to the full version on the passages which you are more interested in, and back when such a passage is over.

Let’s try to get some reasonable approximation of such functionality for our particular case, keeping in mind that the support of scripting in EPUB is optional and so solutions based on scripting are undesirable at the moment.

Luckily, with e-books we are not afraid to make the volume a bit bigger; it weights nothing in any case. So, let’s make two editions, a monolingual and a bilingual one, united in one e-volume and tightly interconnected with hyperlinks all over. That is, the lines in the monolingual part (catullus1.html) are to be formatted as follows:

<div class="poemLine"><a href="catullus2.html#l1_1b" id="l1_1">&nbsp;+&nbsp;</a>Cuī dōnō lepidum novum libellum</div>
<div class="poemLine"><a href="catullus2.html#l1_2b" id="l1_2">&nbsp;+&nbsp;</a>āridā modo pūmice expolītum?</div>

And the lines in the bilingual part (catullus2.html) are to be formatted as follows (note the invisible elements: they are needed for the black and the grey lines to be aligned correctly together):

<div class="poemLine"><a href="catullus1.html#l1_1" id="l1_1b">&nbsp;–&nbsp;</a>Cuī dōnō lepidum novum libellum</div>
<div class="poemLine2"><span style="visibility: hidden">&nbsp;–&nbsp;</span>To whom do I give this delightful new booklet,</div>
<div class="poemLine"><a href="catullus1.html#l1_2" id="l1_2b">&nbsp;–&nbsp;</a>āridā modo pūmice expolītum?</div>
<div class="poemLine2"><span style="visibility: hidden">&nbsp;–&nbsp;</span>recently polished with pumice?</div>

If you want to keep every line on the same page with its translation, you may wrap each such pair into an additional div element with page-break-inside style property set to avoid.

Now we have two versions of the page appearance, between which we can switch by clicking on the pluses and minuses (no actual links in the examples below, just the general appearance of the pages is imitated; the a tags are assumed to have text-decoration: none set to switch off underlining, otherwise the little links look worse). The link near every line ensures that you are always directed to the right page of the other version (because, obviously, one monolingual page corresponds to several bilingual pages).

A bit strange, but, hopefully, convenient enough (I have tried it in Aldiko on an Android phone). There is much space for task-specific alterations, certainly. You may create an option to leave only the translation on the screen; or make three layers for each line instead of two (e.g. original + translation + commentary), or design a nicer and more convenient appearance for the links (the simple ones are sometimes easy to miss with the finger), and so on. So, good luck to anyone who is going to experiment with that.

Written by Anton Bryl.

Even though the specification for EPUB v3.0 was finalised last October, we’ve yet to see any production ready EPUB3 books out in the wild. The likely reason for this is that EPUB3 compatible eReaders have only come on the scene recently and without an eReader, there’s no way to test how the ebooks look – a bit of a catch-22.

Version 3.0 ebooks may seem non-existent at the moment but this will no doubt change before the end of the year, so now is a really good time to look at how we’re going to transform our Masters to EPUB3 – you do have your books in a master format right?

This last week I decided to convert one of the titles from epubBooks.com to EPUB3 and set to work on Gulliver’s Travels (download link below). I’ve only found two ways to view my newly generated EPUB3 ebook; Azardi and iBooks.

(Note: this test ebook is a very simple conversion from EPUB2 and doesn’t use any HTML5 or CSS3 specific features – consider this article as just a cursory overview.)

Azardi eReader

A short while back Infogrid Pacific updated their desktop eReader app to support EPUB3. At the time it didn’t mean too much because there weren’t any ebooks around. Now that I’ve got something to try I uploaded it and have to say, everything looks good. The Table of Contents works as required and all the content displays well.
Azardi is available on the main OS platforms; Windows, Linux and Mac. Try it.

iBooks

It seems Apple’s newest version if iBooks has some support for EPUB3. Like with Azardi, the TOC displays as expected along with all the content in the same way as the EPUB2 version. One nice feature in iBooks is how it handles footnotes; these are pulled from their place at the end of the chapter and displayed as a pop-up – perhaps the most useful way to view footnotes in an ebook.
iBooks is available on all iOS platforms. Try it.

Adobe Digital Editions (ADE) – Preview 1.8

Although ADE 1.8 Preview opens my EPUB3 ebook, it doesn’t work so well. The TOC is not available at all and footnote links don’t work. They do at least show at the end of the chapter.
The ADE engine is used in all the popular E-Ink eReaders, so let’s hope Adobe introduce full EPUB3 support before the final 1.8 version is released.

Gulliver’s Travels: EPUB3 eBook Experiment

As I’m expecting compatible eReaders to become more abundant over the next months I wanted to look at what’s needed to create a good solid looking EPUB3 book as I’d like to release all the free ebooks on epubBooks.com in the EPUB3 format. The book I chose for this experiment is Gulliver’s Travels by Jonathan Swift (EPUB2 version here).
This is only a first-try and most of what I’ve worked on is the mark-up to make it a valid EPUB3 document. This means that all the CSS remains unchanged and mostly only the head section of the HTML has been updated. This first test is not EPUB2 Reader compatible, so there is certainly more I can do to make it work better on ADE and other v2 eReaders.

EPUB3 Experiment: Gulliver's Travels

Anyway, I hope you find it useful and please do post your feedback in the comments.

What we are going to discuss here is how to format poetry in XHTML format (which underlies EPUB) so that it looks nice on smartphone screens – that is, when many or even all of the lines do not fit the screen width. In other words, our concern is how to break poetry lines nicely.

We do not discuss the poems which use non-standard formatting (Lewis Carrol’s Fury said to a mouse, shaped like a twisting tail, is a good example of what we are not talking about here); each poem of this sort is a separate formatting problem of artistic rather then technical nature. What we are going to consider are poetry pieces which use some sort of conventional formatting. The examples used further in this tutorial are from Shakespeare, from Horace, and, for a more specific formatting convention, from Beowulf.

Note: This is a guest post by Anton Bryl

It is clearly unacceptable to use plain left-align text with no style modification: the result of line breaking will be rather ugly, as shown below (a few lines from Shakespeare’s Henry V are used):

Centering everything (a solution frequently met in actual e-books) is better, but still far enough from perfection:

Let us now proceed to another variant, which is also used widely enough and which I think to be a reasonable basic approach to the problem, and then see what we can add to it.

1. The Basic Way

The idea in this basic approach is simply to use different indentation for the first and the subsequent portions of every poetic line. It has already been proposed several times by different people online; I suppose, it is usually the first thing better then just-center-it-all that comes to one’s mind (after one figures out that, alas, text-align CSS property cannot be defined separately for the first-line selector).

In terms of CSS properties, it means that the text should have a non-zero left margin, and the first line of each paragraph should be negatively indented with respect to the rest of the text (each paragraph being a poetic line rendered, depending on the screen width, as one or more lines of text on the screen):

If different lines of the poem have different indentation, it is possible either to define several style classes, or just to add some non-breaking spaces ( ) in the beginning of the indented lines.

Now let’s format the same few lines from Henry V using this style.

Below you see how it will be rendered…

…on a wider page:

…on a narrower page:

…on an even narrower page:

The result looks better then the previous ones. However, to my taste it is still not as readable as desired. This solution is nearly perfect for the cases when only a small percentage of lines do not fit the screen width (see the second of the three screen widths in the example above). However, when smartphones are in question, splitting of a line into two is no longer a rare emergency which is to be handled just ‘nicely enough’, but rather something that happens to nearly every line (see the last of the three screen widths in the example above). For such cases this formatting is, to my taste at least, good enough to consult the text but not really good enough to enjoy it with convenience. So what can be done to that?

2. Structuring the Text

The way to overcome the lack of structure is, certainly, to add some. In our case apparently a reasonable thing to do in this direction is to allow line breaks only at pre-selected positions which correspond to pauses, or to boundaries between phrases, or to something else of the same sort. An easy way to do it is to replace the white-spaces which should not become line breaks with non-breaking spaces ( ).

An alternative way could be to use white-space property in CSS, but the support of this property by EPUB reading software is, in my experience, not guaranteed in practice; yet another relevant markup element, nobr tag, is by now deprecated and should be avoided.

So, let us format the same piece of poetry once more, now with non-breaking spaces enforcing some logic in line-breaking:

The difference created by structuring the text with non-breaking spaces is seen on narrow pages:

…and:

The choice of ‘permitted line-breaking places’ is surely rather subjective, and may be made differently. In any case, to my eye, the text is both easier to read and more pleasant to see when formatted this way.

A drawback of the approach is the amount of manual markup needed to format a long piece of poetry this way. However, such or similar «chunking» of poetry lines into non-breakable fragments can be done automatically, or semi-automatically. Here is a sample set of rules for English (and a Perl script – poemnobr.pl – based on these rules) which would produce tolerable result in many cases:

1. If application of any of the following rules results in a non-breakable block longer then 25 characters, this rule is skipped. The choice of the number ’25′ reflects my understanding of what should fit on any screen and is rather subjective; you may use whatever number seems reasonable to you in its place.
2. With the above restriction in place, the following rules are attempted, in the given order:
   1. If there is a space before a dash, it is made non-breaking.
   2. If there are punctuation marks in the line before the end of line, everything after the last such punctuation mark is transformed into a single non-breakable block.
   3. If an article (‘a’, ‘an’, ‘the’) or a demonstrative (‘this’, ‘that’, etc.) is not followed by a punctuation mark, the following white space is replaced by a non-breaking space.
   4. Next, the same is applied to the word ‘no’ (the word ‘not’ cannot be processed that easily, for it may be connected, in different cases, both with the previous word and with the next one, e.g. ‘not knowing of something’ vs. ‘Somebody knows not of something’).
   5. Next, the same is applied to interrogative words (‘who’, ‘when’, etc.).
   6. Next, the same is applied to conjunctions (‘and’, ‘but’, etc.).
   7. Next, the same is applied to prepositions (‘of’, ‘from’, etc.).

After such automatic processing, some manual post-correction may be applied, which, in turn, may eventually lead the editor to formulating additional automatic rules to her/his own liking. It may be potentially interesting also to consider more advanced text analysis for automatic chunking of poetry lines; e.g. syntactic parsing may be helpful in deciding which portions of text should be ‘kept together’.

3. Some special cases

This section is dedicated to special sorts of poems, and if you are not interested in them, you may just skip it.

3.1. Greek and Roman Classics: Handling Formal Cæsuræ

For the metrical forms with clear cæsuræ it may be good for readability to enforce those as the only allowed line-breaking positions. Like this:

(The example is taken from the Ode 1.11 by Horace, as translated by Arthur Hugh Clough)

Below you see how it will be rendered…

…on a wider page:

…on a narrower page:

…on an even narrower page:

3.2. Old English Poems

One more special case: Old English poems. Here, obviously, the most appropriate line-breaking position is right before the long space which separates the half-lines. Note, that in this case the long space itself will provide the necessary indentation for the second half-line, so no special provisions for indentation are needed, and the CSS style should look as follows:

Then the text is formatted as follows:

(The example is taken from Beowulf)

Below you see how it will be rendered…

…on a wider page:

…on a narrower page:

…on an even narrower page:

That said and shown, it remains only to wish the readers good luck with formatting whatever they want.

A couple of weeks back Ectaco announced their new 9.7 inch E-Ink eReader (WiFi and Touch Screen), nothing special in that, but the big news about this is that it will be the first colour E-Ink device to be available for purchase!

The jetBook Color EDU.12 has been in development since earlier this year in Russia and will be made available in the States during Q4 2011. The new eReader is actually being pushed as a K-12 device, or as Ectaco put it, “Educational eTextbook tablet with Test System, Home Assignments, Remote Tutoring and eBook studies”.

Anyone outside of the education system us unlikely to get their hands on one, or want to for that matter, as the it seems to be tied heavily to the “Teacher’s Console” and purchasing looks to be only possible via the Ectaco website; so you’ll probably need appropriate credentials.

There’s plenty more details on the jetBook K-12 website but I’ll list some of the main features here;

• Color e-Ink 9.68″ PVI EPD touch screen (1600×1200) using Electromagnetic Resonance Technology.
• 32GB of memory.
• Rechargeable 2350mAh Lithium-Polymer battery lasting for 10,000 page turns.
• Plug-in GPS module that allows parents to locate their child or the unit itself with a few clicks.
• Text-to-speech module for pronunciation of books
• Script character recognition in combination with an EMT panel allows students to write on the screen.
• Teachers can restrict the download of any programs or content that is not related to the class.
• Screen serves as an ID card for the student displaying a schedule of classes (updated daily via Wi-Fi or 3G).
• Send students grades, exams, homework, and messages.
• Fully interactive SAT course that will train, test, and raise students’ SAT scores.
• Features the content of a 50-state reading list
• A Speed Reading course
• Talking Oxford Dictionaries narrated by professional linguists
• Foreign language courses that teach any of the 52 available languages and provide great support to ESL students.

Pictures of the EDU.12 are hard to come by at the moment but from what we can see the device will suffer from one known limitation of E-Ink, which is that the colours aren’t generally very vibrant (suffering from low contrast and “pastel” colours) compared to the screens found on the current crop of tablets.

Still, every new advancement in screen technology brings us closer to the perfect screen – great clarity, very low powered, full colour, fast refresh, usable in bright sunlight, etc. – so hopefully this will be a success and provide the R&D teams with more funding to continue development.

I could only find a couple of visuals for this new eReader; an image from Liliputing and a video (in Russian) on YouTube, which shows the device for a total of about 5 seconds (jump to 2:05 and then again just after the 3 minute mark).

Rumours are abound right now that Amazon is on the verge of providing support for EPUB ebooks on their Kindle eReader. What’s getting peoples tongues wagging is a post from an eReader blog* stating that Amazon is telling publishers to start providing them with titles in the EPUB format.

As vague as the details are from that post, there is some substance in the concept that Amazon are preparing to add EPUB support.

Back in April Amazon announced the introduction of their new Library Lending Program in co-operation with OverDrive, who [currently at least] deliver their ebook titles as EPUB files. The OverDrive blog also states, “[y]our existing collection of downloadable eBooks will be available to Kindle customers”. We also know that the Kindle Previewer software (for ebook developers) will import EPUB files, which internally converts them to MOBI.

Liz Castro, well-known ebook developer and author of EPUB: Straight to the Point, has her own thoughts on how the Kindle will support EPUB, believing that Amazon will just convert titles to their proprietary MOBI format for use on the older Kindles.

In my opinion, Amazon can do better than just convert the EPUB’s.

I’ll confess here that I don’t know much about the Kindle software system, but I would be surprised if they couldn’t run two different reading apps side-by-side. As for the hardware on the older Kindles; if they are capable of reading MOBI ebooks, there’s no real reason they can’t also read EPUB 2, perhaps even support the full EPUB3 spec.

Most, if not all, ebook developers will tell you that MOBI is an inferior ebook format to EPUB (not that this format doesn’t have its faults), add to that the features being developed for the upcoming EPUB3 and you have a strong case for why Amazon may decide to phase out their own ebook format.

If publishers and ebook developers are allowed to focus all their efforts on just one standard ebook format, then ebook production will take a great leap forward, which in turn will give the people on the streets better ebooks — at least in regard to features — and ultimately a better user experience.

* It’s unclear if this is a reputable source for such gossip, so I’ve made the decision not to link to this site. The article doesn’t really say alot but if you’re interested, a quick look on your fave search engine should bring them up.

After many months of hard work, the EPUB Working Group has released the first Public Draft of the new EPUB® 3 specifications for review. This is a substantial update on the current spec and has core changes that include;

• HTML5 support
• Rich Media and Interactivity
• Layout Improvements
• Global Languages
• Accessibility Improvements

EPUB is a XML and Web Standards based delivery format for digital books and publications allowing content to be used on many Reading Systems, which include Apple iOS, Android, Desktop computers and dedicated eReaders.

The new EPUB3 is a major revision to the current standard and with a move to HTML5 based content, now provides support for key emerging technologies including video, audio, scripting, interactivity, styling and layout enhancements, vertical writing, improved accessibility and MathML support.

The WG has also made big improvements on how the EPUB 3 spec is structured, now providing 5 documents; EPUB 3 Overview, Publications 3.0, Content Documents 3.0, Open Container Format 3.0 and Media Overlays 3.0. You will also find an, EPUB 3 Changes from EPUB 2.0.1 document, which should help everyone better understand the changes made from the old spec.

It must be noted that this is just the first public draft and the EPUB WG are now open for both IDPF members and general public to comment on.

The current draft can be found here on the IDPF website: http://idpf.org/epub/30

All comments on the EPUB3 specification should be submitted to the Issue Tracker.

EPUB3 Final Recommendation is expected to be reached in mid-2011.

Booki.sh have just announced they’ll be launching an ebook store in Australia, where the books are not downloaded but streamed from the cloud.

With the implication that we’re only renting/licensing our purchases, this news has caused quite a bit of a stir with some people denouncing it as, the worst thing to happen to publishing. Of course, some people would say that DRM has already killed off any possibility of actually owning our ebooks, including Booki.sh themselves.

This “ebooks-in-the-cloud” scenario isn’t new. I’ve been mulling it over for a while and my conclusion is that it’s not such a bad idea – but only if the book industry change the way we pay for them.

If all our books are stored in the cloud – meaning that we can’t download them to external storage – then we really are only renting them. I don’t find this such a big deal because if I actually wanted to own a book, I’d probably go out and buy a paper version anyway (wow, did I just say that).

(Ok, so that’s no completely true, but most of the ebooks I do buy are DRM-free professional books, from O’Reilly, A Book Apart, etc., so I do actually own them.)

It’s only recently that I’ve come to realise (or is that admitted to myself) that I mostly only read books (novels) once and if I ever read them again, it’s likely years after the first time, so I don’t mind having one-off/temporary access to them. But, if these cloud books imply that we’re only renting them, then I’d expect the price to be reflected in that.

The business model for ‘ebook Rental’ could be something similar to what we have with DVD rentals, where you can get pay-per-view movies streamed over the internet for anything from 25% – 50% of the purchase price. If I take a monthly subscription package then I could get them even cheaper.

So publishers, are you going to let me rent my ebooks – will you let me read Stieg Larsson for $2.00?

…no, I didn’t think so.

During some research on using Adobe’s InDesign to create EPUB documents I came across this UK training course entitled, “Creating ePubs with InDesign”, which is being run by Highlander, one of the UK’s oldest and most successful training providers for the creative, web and marketing sectors.

They have two 1 Day sessions available in March and April (London, UK) and the course will cover everything from an introduction to EPUB documents, to setting up paragraph and character styles, to setting up metadata, to covering the processes involved in converting the exported EPUB files to other ebook formats – I presume the Amazon Kindle will be covered, but there is no mention of it on their website.

You’ll need to have previous experience with Adobe’s InDesign CS5 software and it’ll also be useful if you have some previous knowledge of HTML and CSS, although it’s not a requirement.

Here’s a (shortened) outline of the course details;

• Overview
  • EPUB vs. PDF
  • Supported devices
  • What is kept and what is lost in EPUB?
• Overview of InDesign long documents
• Adobe Digital Editions reader
  • Evaluating an EPUB in Digital Editions
• Modifying documents for EPUB export
• Video and your eBook
• Managing images for EPUB export
• The Export Process
  • Embed metadata
  • Embed fonts
• What is the EPUB format
  • Converting EPUB to other eBook formats
  • Applications used to create eBooks
  • Applications used to read eBooks
  • Applications used to convert eBooks to other eBook formats
  • Other eBook formats

If you’re a UK resident then this could be a really useful course for anybody who needs to use InDesign CS5 for exporting to EPUB, but please note that this is not an official endorsement as I have no previous knowledge of Highlander. However, according to their website, they’ve been running all kinds of training sessions since 1995 and are an authorised Adobe Training Centre, so I would expect the quality of their courses to be of a good standard.

The 1 Day course price is £350 and there are currently two sessions available; 3^rd March and 28^th April 2011. You can book your place at Highlander.co.uk.

Now firmly placed as a mainstream item, ebooks have grown in popularity enough for many libraries to have started making digital versions from their catalogue available for lending.

The only thing you’ll need, except your eReader and an appropriate library card, is an Adobe ID (see below).

Most libraries that do provide ebooks are using the Adobe DRM protection system, which also means that most dedicated eReaders (Sony, Kobo, etc) and several eReader apps (Bluefire, OverDrive) can be used to read these DRM protected library ebooks.

I’m going to write three very short tutorials on how to get your library ebook onto your eReader/App. One of these three options should give you enough information even if yours is not actually covered here.

Adobe ID / Activation

As libraries are using the Adobe DRM protection you will first need to create an Adobe ID before you’ll be able to read those borrowed books. If you don’t already have one, then please visit the Adobe website and complete this form.

Adobe Digital Editions (ebook reader)

Unless you are using the OverDrive iPhone/Android app (see below) you must install Adobe’s Digital Editions Reader so that your library books can be activated before they are transferred to your ebook reader.

Download Adobe Digital Editions here.

The first time you run DE, you will be asked to activate it with the Adobe ID and password you created previously.

With DE installed, you don’t even need a digital reader as you can read EPUB books on your computer directly from within Digital Editions. If you do have a digital reader, then read on.

Bluefire eReader App for the iPad and iPhone

Bluefire has become a very popular app as it was the first eReader to allow Adobe DRM EPUB files to be added no matter where you bought your books from, which also makes it perfect for users wanting to read library books on the iPad.

First, download the Bluefire Reader app from iTunes (available for the iPad, iPhone and iPod Touch).

Before continuing please activate Bluefire with your Adobe ID; start the app and on the “Library” page click the “Info” icon, located at the bottom. Here you will see the button for activating your Bluefire reader.

Next, visit your library’s website, checkout an eBook, and click the download link – when asked to save or open, select “Open with Digital Editions”.

Using iTunes we will now transfer the book to the Bluefire app;

• Connect your iPad to a computer and start iTunes.
• Select your device (iPad/iPhone) and click on the “Apps” tab.
• Scroll down to the “File Sharing” section and click the “Bluefire Reader” icon in the Apps section.
• Click the “Add…” button.

At this point you’ll need to browse to where Adobe Digital Editions has stored your eBook. By default they will be saved to one of these locations;

On Windows: your-home-directory/Documents/My Digital Editions
On OSX: your-home-directory/Documents/Digital Editions

The EPUB book will then transfer to Bluefire where you can then start reading.

Library Books on a Dedicated eReader (Sony, Kobo, etc.)

Dedicated ebook readers often have their own software for adding books, but we will stick with using Adobe Digital Editions to get your library ebooks on to your eReader.

I’ll be using the Sony Touch Edition for this example, but it should be the same for all devices that support EPUB with Adobe DRM protection. This procedure will be very similar to the way you do it when you purchase ebooks from a store, so please refer to your documentation for more detailed help. Otherwise here is the brief outline.

• Connect the eReader to your computer and start Digital Editions.
• Unless you have already done so, you will be shown the “Device Setup Assistant” – you will need to authorise your reader.
• Visit your library’s website, checkout an ebook and download to DE.
• From within DE drag the book(s) to your reader – In my case I dragged them to PRS-600.

And that’s it.

Overdrive eReader App for iPhone and Android

OverDrive are a digital distribution company who provide ebooks to all libraries. They also have their own app which is available for both Apple and Android devices.

As I don’t have an Android device I’ll be doing this tutorial with my iPod Touch, but the procedures should be the same on Android systems.

Download the “OverDrive Media Console” app from iTunes (or Android Market Place).

Once downloaded;

• Launch the app and click on the “Get Books +” button (top right).
• On the next screen click the “Add a Website +” button.

You’ll then be taken to the OverDrive website where you can search for your library. In my case, I searched for “Manchester Public Library” – searching for “Manchester UK” or “Manchester Great Britain” generated no results, so if you don’t find your library on the first go, try a different search.

• Select your library from the list.
• Clicking the link under the “Library Systems” heading – you’ll be taken to that library’s website.
• Sign in to your library account, find a book to checkout.
• When you click the download button you will be taken back to the OverDrive app.

As this will be the first time you’ve used OverDrive, you will be asked to sign in with your Adobe ID. Once done, you can proceed with the download and start reading your new book.

The OverDrive app is perhaps not the best eReader out there, but the fact that it makes getting books from a library to your device very easy, it can be a better option for many people.

I hope this tutorial helps and if you come across any issues that need sharing, please leave a comment and I’ll update the article.

In a recent ZDNET article, Jason Perlow described his hesitations for buying one of the new Amazon Kindle’s, which was due to its lack of EPUB support. Many responses to the article noted that the “average user” doesn’t care about the format of an eBook, only for the buying experience. I’m not going to argue on that point because in essence, they are right; the average user doesn’t care. Yet there are two real reasons why having one eBook standard is important, and these reasons will certainly impact the end user.

Publishing Infrastructure and Costs

Although most publishers will use a XML Master Format for storing the original book content, they still have to spend a lot of time, effort and costs in producing and maintaining all the different output formats they need to get their books in to the buyer’s hands. There are also no guarantees that all these different output formats will support the same kinds of features, which will mean even more resources (costs) will be needed to support these alternate formats.

Now, if the publishers only had work one eBook standard then they could spend more resources on improving their own tools to produce better output, which will ultimately give the user an even more enjoyable reading experience. Publisher will also have more resources available to give input back to the IDPF on improving the EPUB standard; bringing more and better features to the eBook world. Certainly a win-win situation for consumers and publishers. Without universal support for EPUB though, everyone will be forced to maintain multiple tool sets, which do nothing but increase costs.

I won’t bring DRM in to this conversation as it is actually independent to the eBook format itself and should not be used as an argument against embracing EPUB.

Independent Authors

One important issue Jason brought up in his ZDNet article was that of self publishing authors. By giving independent authors just one eBook format to think about they are able to spend less time producing eBooks files and more time writing content. They’ll have fewer headaches in getting their books out to the public because all vendors will accept EPUB. With just one eBook standard, more and more EPUB-ready word processors and tools will be developed. The more authors that get content on to Amazon’s self publishing system, the more money Amazon will make. Isn’t this what Amazon wants?

Until just a couple of years ago the publishing world was in turmoil with a multitude of eBook formats it had to support, yet the arrival of EPUB had a hugely positive impact which continues to be seen today.

Sure, EPUB itself is not perfect, but it is being continually improved and with the formation of the EPUB Working Group, there are huge improvements being made right now.

I still can’t make up my mind if Amazon will ever support EPUB but I do believe that it will be more and more difficult for them to refuse to do so. Let’s hope it’s sooner rather than later.

Whether you call them categories, subjects or genres, how you label your book is vitally important, perhaps especially so in these times of the digital marketplace. Being placed correctly in ebook stores and libraries can help in both regular searches and with discovery techniques such as “Similar Titles”.

The EPUB format has been developed to allow your work to be properly tagged with as many subjects as is necessary to describe the title correctly, allowing any ebook reading system to categorise your books appropriately.

If you’re creating your EPUB files manually then you’ll need to open the .OPF in your favourite text editor. Then inside the metadata tags you can add your subject tags.

Here are some example entries;

<dc:subject>Fiction</dc:subject>
<dc:subject>Comedy</dc:subject>
<dc:subject>Satire</dc:subject>

You can add as many subjects as you like, though it’s probably best to keep things focused–adding 50 tags will be just as bad as adding none.

The arbitrary keyword or phrase used inside the subject tag hasn’t been standardised by the IDPF, but I’d recommend using the BISAC, LoC (Library of Congress) or other standardised system.

At this point you probably think there’s nothing more to be said on the topic, however…

eReaders Don’t Use All Provided Genres

When you send your EPUB out into the wild you’ll be somewhat disappointed to find that many eReaders don’t display every subject you placed in the OPF file, if any at all.

There are no IDPF requirements stating that a reading system must use any or all of the subject tags for categorisation and if it does use them, then you’ll find that it’s usually just the first entry. In the example above this would be Fiction. Still, we should take the time to add appropriate genres now as you can fully expect that future eReaders will utilise them more fully.

So, along with choosing the correct genres to describe your work I’d also recommend you list them in an appropriate order, and with the understanding that at this time, only the first entry will likely be used to categorise your book.

Since EPUB became the industry standard eBook format there has been a lot of talk regarding the lack of an official logo, and this was actually an important point to make.

For almost any standard media in existence there is also an official logo, think DVD, CD, etc. This allows distributors and device manufacturers to display the logo and show that they are supporting that standard.

So in April this year the IDPF (those who created the standard) launched a logo competition, asking both members and non-members to submit their own design. In total 203 entries from 18 different countries were submitted and today the winner was finally announced.

Graphic designer and author, Ralph Burkhardt submitted the winning entry, summarising his entry with;

I wanted to create a sign and that is also recognizable as a possible file format graphic (e.g. icons). It should be easy understandable and recognizable.

You can read the full IDPF competition announcement on their website, where you can also find a link to the ZIP file which contains various different file formats, including an Illustrator EPS file.

My initial thoughts on the logo are that I like it. I guess the only complaint I would have is that the “ePUB” text might be better as bold face, as when the image is resized smaller, that text starts to fade away a little and becomes not so recognisable.

I truly hope all the eReader manufactures that fully support the EPUB format will now start to make use of the new logo. I’ll be implementing this into all the EPUB eBooks found here on epubBooks.com, which I hope to have live soon.

Apple have just released an updated iTunes 9.1 to make ready for iPad syncing and EPUB support for when the users receive their iPad and can access the iBooks store.

We here in Europe can’t even pre-order an iPad yet so I won’t be able to do a full test for some time yet but I thought I’d see what happens when a DRM-Free EPUB file is added to iTunes….which turns out to be not a lot.

As you can see from the screenshot below, the EPUB book does get recognised as a Book with the title and author details being taken from the file’s meta data. One thing that concerns me is with the book Info dialogue and how the book’s meta details are presented as though it is a song; Artist, Composer, Track Number, etc. Let’s hope this gets fixed soon to show an appropriate information page.

I’m using the Swiss Family Robinson here as an example, which doesn’t include a book cover in the file, so this is the default icon you will have for any titles that don’t include covers–this will be most free public domain works you will find from around the internet.

Right-click on the book and a pop-up menu shows a “Play” item, though at present this does nothing; one has to presume that once iBooks is released we will be presented with an option to download from the App Store. Whether the iBooks app will be made available to iPhone and iPod Touch users is still speculation but my own guess is that it won’t happen until the iPad has seen its worldwide release–even then I’m sure it won’t be until sometime later.

Update: I’ve now posted a review of the Apple iPad in the eReaders section of the site.

It’s been a few weeks now since the Apple iPad announcement; a 9.7-inch multi-purpose tablet with native Book, Magazine and Newspaper options. Although Apple hasn’t released this as a dedicated eBook reader or as a direct competitor to popular eReaders such as the Amazon Kindle and Sony Reader, in essence, it is an eReader nonetheless.

So, the iPad is an eReader, and one that reads not only books and newspapers but web pages, emails and numerous other electronic documents. It can also do the stuff that an iPhone and iPod Touch can do – running thousands of third party applications from the iTunes App store. For this article though I’d like to focus on the book aspects, especially in relation to the EPUB eBook format.

There were rumours abound weeks before Apple’s announcement that they’d been discussing with publishers and newspapers to get their content for a new Apple device. Most of this content will be accessible from the upcoming Apple iBooks Store and there should be plenty to choose from as Apple have brought onboard big names such as Penguin, HarperCollins and Macmillan.

The new iBooks store will be integrated in true iTunes style and with a 3G iPad option; you won’t even have to worry about logging into Wi-Fi hotspots.

From what’s shown in the videos circulating the internet, the iBooks application seems to have typical viewing options (font sizes) and also that life-like page turn feature, though to be honest I still can’t figure out why this kind of gimmick is considered so cool. That whole drag a page, swipe your finger (Sony Touch) feature is fun for the first 10 minutes but quite frankly, I don’t sit there when reading a paper book being thrilled at the ingenuity of how a paper page turns, so why should it be any different with an eBook. Just let me tap the screen/press a button and give me the next page by the time I get my eyes to the top of the screen, thankyouverymuch.

People have talked about the iPad as being a game changer or an E-Ink Killer (Kindle/Sony). Well, I’m not sure any of the current E-Ink developers believed they’d reached the pinnacle of electronic mobile reading – E-Ink eReaders were always going to evolve and become more multi-purpose – but there are still advantages of these over the iPad with power consumption and reading longevity being two.

E-Ink is extremely low power and thus allows usage of up to two weeks before a recharge is needed. Also, sitting for hours on end with no interruptions from IM’s and incoming email, plus a very paper like screen, are very pleasant experiences I can assure you.

We’ll have to wait until its released before we know the exact power consumption, but the iPad will probably give around ten hours of play, and that’s highly likely with anything and everything turned off and maybe even a low backlit screen.

Okay, so this isn’t an iPad review and much of what I’ve said here is all personal preference anyway. I guess the real question you want form me is;

Does the iPad Support EPUB eBooks?

The quick answer is, yes.

The longer answer would also be yes, but there might well be some caveats here.

The Apple iPad native eBook format is EPUB; Steve Jobs said this himself at the announcement in San Francisco. This of course makes sense as many, if not most publishers have been working toward creating their content in this format, thankfully Apple haven’t forced the providers to come up with yet another format.

EPUB is lucky in some respects; it came about at a time when eBooks was just starting to become more main stream and this gave publishers the ability to focus [mostly] on just one eBook format. Beneficial for them and the end user.

It seems that there are really two questions regarding the iPad and the EPUB format.

One. What kind of DRM will it have?

The iPad EPUB eBooks will have DRM and it certainly won’t be the Adobe flavour. A recent announcement says that Apple is dusting off their old Fair Play DRM that was used for music in their iTunes stores up until just a year or so ago. This means you’ll not be able to use these books on other eReaders – you buy from Apple, you use on Apple – at least that’s the way it seems at the moment. Once the iPad is out there, perhaps we’ll see some solutions to get around that.

I should note that I don’t know enough on Apple’s Fair Play DRM to know if other vendors can implement it or whether this will affect their ability to use the Adobe DRM side-by-side with Apple’s.

Perhaps in the long term Apple will turn out to be instrumental in getting DRM off eBooks completely and a couple of years or three down the line this issue won’t matter any more. We can but hope.

Two. Can you Download or Buy from Sources other than the iBooks Store?

Will I be able to browse the epubBooks.com website, click the download button and have my books open in the iBooks reading application?

This is a really big question and one which is still open. My gut feeling is that the answer will be no.

I’ve yet to hear if Apple will allow competing eBook apps to be ported to the iPad. Perhaps the eReader developers themselves know that answer, but the Apple TC’s will forbid them to talk, so everything is hush hush for the moment.

If apps such as Stanza are allowed onto the iPad then I think all the above questions will be answered in a positive light.

The iPad will be out there in a couple of months so then we’ll know for certain the future of reading with the Apple iPad.

[UPDATE: EPUBs from epubBooks.com can now be added to iBooks and there are now plenty of other Reading apps for you to use. You can read more about this over on my Apple iPad review page.]

Apple iPad: Quick Facts

• Released Date: Late March 2010 and April 2010 for 3G option
• Price: Currently $499 for the 16GB model
• Memory: 16/32/64GB
• Multi-Touch 9.7 inch screen (1024×768)
• iBooks Store for books, magazines and newspapers
  • EPUB book format
  • Apple Fair Play DRM
• Various other electronic content
  • Video, Music, Games
  • Untold apps providing eMail, Calendars, Maps, Photos, etc.
• Wi-Fi & Bluetooth
• Pre-paid, no-contract, unlocked 3G connectivity (optional upgrade)
• External Keyboard Dock
  • Apple or other standard Bluetooth keyboards

Today, Nicolas Gary from the French website www.actualitte.com contacted me about their exclusive first look at the next generation Bookeen eReader, the ORIZON. As the article is in French, Nicolas has kindly written a short overview in English.

Bookeen is introducing a new eBook Reader called ORIZON, supporting ePub files (with or without DRM) of course. It comes with a 6 inch touchscreen display, WiFi and Bluetooth (Have fun! This is the first Reader in France with a wireless connection!) What else? An accelerometer, so you can read in landscape or portrait mode.

Weight : 226g for 12.25 x 18.5 x 0.75 cm and we know a few specifications like the resolution, 167 dpi and 16 levels of grey.

Bookeen says there will also be a new version of the Boo Reader software.

And about the Opus…just few new colours…

If your French is up to scratch you can read the full exclusive over at actualitte.com.

When I was at the 2009 Frankfurt Book Fair, Michaël Dahan from Bookeen did mention there would be a new 6 inch reader this year. I was very impressed with the Bookeen Opus when I reviewed it in November and said to myself at the time that if they had a 6 inch version this would be my choice of eReader.

For the last few months I’ve been using the Sony Reader Touch Edition and although I think there are many amazing features, that dark shiny touch screen really does bug me. The shininess I could live with, but I really do hope the Orizon’s screen brightness doesn’t suffer from the addition of the touch screen like the Sony does.

At the moment there are a multitude of eReaders coming onto the market (all supporting EPUB it seems :- ) but I get the feeling the Bookeen might be one step ahead of most of them.