Most of these are (by design) internal and not user-facing, but at least two are notable and possibly quite fun.

Feedbooks integration

At the bottom of the user library page (your home page when you log in), there’s now an option to download any books from the Feedbooks most-popular feed. This is language-aware; Bookworm will request books in your current language preference, and Feedbooks will return the most popular books in that language:

One-click adding

Clicking on a Feedbooks title will immediately add that book to your library, without having to download it to your computer first.

Any other site can create an “add to Bookworm” button using this simple URL scheme:

http://bookworm.oreilly.com/add/?epub=http://www.example.com/book.epub

For example:

http://bookworm.oreilly.com/add/?epub=http://www.feedbooks.com/book/187.epub

At this point, you will already need to be logged in to Bookworm for this to work. In the near future we’ll provide even more methods to get content in and out of Bookworm.

Many thanks to the O’Reilly TOC folks who sponsored this work.

Thank you Mahalo Ito!

Thanks to Marco Croella of Simplicissimus for generously donating the translation to the open source project!

I helped out with the installation but the very competent folks at Simplicissimus will be managing it from here on. Best of luck!

Neither one is publishing-specific, but Django (like Rails and Drupal) is a great way to deploy a web application quickly and easily. (Bookworm runs on Django, as do many of my smaller projects.)

You can also download the slides as a PDF. Licensed Creative-Commons-Attribution.

It was a pretty good event overall although I felt that the main program was much stronger than the workshops (my talk was part of the latter), and I was disappointed that there were no major product announcements — in particular from Sony.

I’m also looking forward to meeting people at Book Expo America later this month (and most especially the BEA Tweetup).

Lastly, I’m very excited about BookCamp Toronto. I’ve been to a number of technical unconferences and they are universally great. It will also be my first visit to that city.

If you’ll be at any of these events and would like to chat, send me an email at liza@threepress.org.

For more information on translating Bookworm, see the post on O’Reilly labs or join the Bookworm translators’ list.

Bookworm will switch to your preferred language automatically if it is available, or you can manually set your language by updating your user profile.

Thank you to Jens Quade for his initial work in internationalizing Bookworm and especially to Michael Wiedmann for heroically translating the remainder of the site.

Danish, Spanish and Finnish are all coming soon.

For more information on translating Bookworm, see the post on O’Reilly labs or join the Bookworm translators’ list.

There’s a lot of finger-pointing going on, but my feeling is that it reduces down to two statements:

1. Reading systems need to fully support HTML/CSS. Realistically this means they must be based on WebKit or a similar mature HTML rendering engine. A home-grown engine like Adobe Digital Editions is often a source of frustration for ePub producers and readers.
2. ePub producers need to take responsibility to understand how to correctly mark up their books. The best thing you can do when getting started is minimize your use of styles and custom formatting. Later, bring on an HTML/CSS expert to help fine-tune the layout.

Where I disagree with Mike is the idea that a beautiful ebook needs to precisely mimic its print equivalent. For born-digital works this obviously doesn’t apply at all, and the ability to read an ebook on devices of varying screen sizes and capabilities means that pixel-perfect rendering isn’t even desirable. Anybody with an ereader who’s tried to read PDFs on them is familiar with this problem.

What does need to improve are the defaults. This is where Apple tends to excel, by providing beautiful interfaces out-of-the-box.

But I also recently worked on a project to replace an unmaintainable website that was generated by Apple’s web-building software. It looked great in Safari but was totally unusable for the visually-impaired community, a substantial fraction of the target audience. I’m afraid an Apple ereading solution would be just as much of a beautiful cage.

Luckily, mature web browsers + high-quality HTML + reasonable CSS can produce some lovely results already. Here’s Mike’s test document in Bookworm’s new Reading Mode. I happen to think this looks nice.

But it’s much more important for ebook creators to proof the content rather than the layout. Check that the line breaks are right, that words aren’t run together, and that special characters are displayed properly. (The last Kindle book I purchased had numerous spacing errors — not bad enough to return it, but annoying for something that cost $6.00).