Moderator’s note: Marc is clearly listening to your feedback. I myself am a big Stanza fan. Question: Should we run a separate post on, say, eReader or BookShelf—and then likewise invite the devs to reply to your comments on the pros and cons? – D.R.

We at Lexcycle have been overwhelmed by the support and encouragement from the e-book community (especially TeleRead) regarding Stanza.

The praise has given us the confidence to forge ahead, and the constructive criticism has tempered our hubris and made us wiser.

And overall, the community’s many years of musings over what would make a perfect e-book reader has provided us with invaluable insight into the needs and wants of those who see the future of books unchained from their bindings.

85,000 Stanza users in a dozen countries

Stanza has gotten off to a tremendous start, with 85,000 users spread out over a dozen countries. This is thanks in no small part to Hadrien Gardeur of Feedbooks.com, whose content is central to the success of Stanza.

His vision and tireless work in creating the Feedbooks API cannot be underestimated, and his many efforts over sleepless nights half a world away in working out nuances with the glue between Stanza and Feedbooks have been truly heroic. Nearly half a million books have been downloaded from Feedbooks via Stanza thus far!

The text styling issue

That being said, we are still at the start. One of the major complaints our users have is the loss of text styling when importing from other e-book formats. For example, if you open a .lit file in Stanza Desktop and then share it with Stanza iPhone, nearly all the text styling is lost in the process.

Note that this is not a limitation of Stanza iPhone itself (which fully supports advanced book formatting, as can be seen in its support for the formatting of the Feedbooks books), but rather it is a conversion issue when loading other formats into Stanza Desktop. Improving our support for book styling is one of our highest priorities at this point. As any frequent reader of the MobileRead forums knows, scaling the Tower of e-Babel is a laborious process, and while we are off to a good start, we are still on the first few steps.

On the issues of Windows, metadata and configurability

Some of the other criticisms that are mentioned in these threads are things that we have already addressed. For example, one of the major shortcomings of Stanza until recently was that Stanza Desktop was only available for Macintosh computers. We released Stanza Desktop for Windows last week, which has resulted in an enormous surge in Stanza’s usage.

Stanza iPhone (which was released a couple of weeks ago) now also provides the ability to edit a book’s title, author, and subjects. We expect similar metadata editing to come to Stanza Desktop in the near future. In the vein of features that we’ve added in response to user feedback is user-definable bookmarks, which will appear in Stanza iPhone 1.2 very soon.

Another persistent user complaint is that Stanza iPhone doesn’t provide enough configurability, but this is due to the non-obvious fact that Stanza’s preferences are actually located inside the central iPhone Settings application, and not inside Stanza itself.

While this is in accordance with Apple’s own iPhone user interface guidelines, the confusion that this has caused is significant. So for Stanza iPhone 1.3, we are moving some of the often-used preferences inside Stanza itself, which has the additional benefit of enabling us to provide a live preview of changes to fonts, colors, and other display preferences like line spacing and text alignment.

Already supports ePub table of contents

Other reported issues mention are things whose accuracy we question. For example, the review at http://jedisaber.com/ebooks/Readers.asp mentions that we do not support ePub table of contents, which is not accurate.

In both Stanza Desktop and Stanza iPhone we have full support for the table of contents defined in the ePub book. That same review also claims that Stanza does not return to their last position when re-opening a book, but Stanza has had that feature since it was first released, and we haven’t heard any other reports of it not working.

Sharing glitches are on the fix list

And finally, there are those straight-up bugs that we are working to fix. For example, some people have problems sharing between Stanza Desktop and Stanza iPhone. These are usually configuration issues with their firewall, network, or Bonjour support which we are often able to guide them through, but there are other problems that are legitimate bugs that we are in the process of researching and correcting.

The laundry list of issues could continue ad nauseam, but we think we have expressed our central point: we are listening to our users, we have corrected many problems already, and we are working hard on correcting others. The Stanza forums at http://www.lexcyle.com are a good place to discuss individual problems and share experiences with other users.

Other improvements on the plate

As for the future, that is where the excitement lies. We are working on our list of short-term improvements, such as the ability to edit a book’s metadata from within Stanza, implementing text styling for more e-book formats, a smoother set up experience for sharing books between the desktop and the mobile device, the ability to search in the entire book (rather than just the current chapter), and configurable device-side hyphenation. And for the longer term, our priorities are the same as that of the community. The big one, of course, is integrated library management, iTunes-style. This will enable a user to catalog their entire library, assign cover artwork, and share en masse with their mobile device without having to open each book individually.

Other projects include integration into commercial bookstores, adding search support to the Lexcycle Online Catalog, implementing ability to take notes and highlight text, enabling the user to send excerpts of books to friends via e-mail. The list goes on; we clearly have our work cut out for us.

Further feedback appreciated

We hope that the TeleRead community will continue to provide us with the valuable feedback they have given thus far. It is only with the insight of enthusiasts like you that we will be able to help bring about the revolution in electronic reading. And while no software application can be everything to everyone, that doesn’t mean that we aren’t going to try 🙂

///////////

Marc Prud’hommeaux joined Lexcycle in early 2008, coming from BEA Systems.

He has been in the software industry in various capacities for over ten years, and holds a BA in Philosophy from Cornell University.

Screen image: It originally appeared in a gung-ho Wired review of Stanza.

Note: I invited Marc to respond. The actual title of the post was “Lexcycle responds to TeleRead on Stanza’s usability, issues, and future.” I couldn’t resist tweaking it, however to get in the number of users Stanza has attracted in just a month or so. Meanwhile here’s my latest suggestion. At some point maybe Marc can see if Stanza can work with nonDRMed Mobipocket files that originally were PDF books and were translated via Mobipocket Desktop. – D.R.

Technorati Tags: ,

11 COMMENTS

  1. I need to update my review (sheepish grin).

    After I wrote it, I did discover that it will open a book to the latest read page, and since then an update has come out that auto-opens the latest book.

    I still have an issue with Stanza’s support for the epub table of contents.

    It does indeed have a table of contents, but it seems to pull the TOC from the .opf file, instead of the TOC.ncx like it should. Still, this is a minor problem.

    Overall I love Stanza, and thanks for the new features that are coming soon!

    (I’ll update my review sometime today.)

  2. The ePub .ncx table of contents will be used whenever there is an entry for an item. However, if an item does not have a corresponding section in the .ncx file, the items name will be used (which is often not very human-friendly). We’re considering way of improving this.

    As for the page turning problem, we have had other reports as well. I find it very annoying, and we are trying our best to track it down and correct it. Note, though, that this only affects swiping to turn the pages; tapping the sides to switch pages always works, at least for us.

  3. Hi Marc

    I have great hopes for Stanza, reading ebooks was a major consideration in my iPhone purchase. I have posted elsewhere on TeleRead that I prefer no hyphenation on a small screen (perhaps an option to turn it off), and that italic/bold support is essential for many of the books I would like to convert to read with Stanza. Those are my personal priorities to watch out for. I believe these are in the queue, but it is early days for everyone on the iPhone and I am patient!

    It would be nice on the settings page to have a preview of the font size when adjusting the slider so that you don’t have to pop back and forth to the book to get it just so!

  4. Hi Marc,

    ePub is HTML based. HTML is quite complicated. That means that successful rendering of ePub can be achieved only in case reader is based on some quality browser engine.

    Stanza is Java based. As I know embedding quality browser into Java program is a serious problem and the only browser control available for Java that can be evaluated as being of high quality is WebRender. But producers of that control even have not published licensing terms.

    What engine for rendering HTML is used in Stanza? Is there any hope for rendering HTML using some quality browser engine, being it Firefox or Webkit or yet some other?

  5. Hi Mark,

    Stanza is actually using Webkit on Mac and IE on Windows to do the rendering using platform-specific native components.

    If it is then Stanza’s rendering of HTML and CSS should be much better. Currently Stanza does not succeed even in rendering such simple HTML + CSS as

    div.header {
    color: green;
    margin-top: 2em;
    margin-bottom: 1em;
    border-bottom: 1px solid red;
    text-align: center;
    }

    <div class=’header’>
    <h3>1. Lassiter</h3>
    </div>

    Instead of rendering all HTML and CSS Stanza renders only text.

    With such poor performance in rendering HTML and CSS I do not see any perspectives for Stanza making revolution in reading.

    The choice of Java as a platform for ebook reader seemsIt seems strange for me. Why not Mozilla’s XulRunner? Why not Adobe’s AIR?

  6. Laisvunas writes:

    > > Stanza is actually using Webkit on Mac
    > > and IE on Windows to do the rendering
    >
    > If it is then Stanza’s rendering of HTML
    > and CSS should be much better.

    The reason your example doesn’t render as you expect isn’t due to a problem with the rendering engine, but rather as a result of how Stanza handles HTML files.

    As far as I can tell, Stanza doesn’t actually render the HTML in a source file, but rather uses it as input to a pre-processor that attempts to extract content from it in an “intelligent” manner. For example, it appears to assume that the content of the first header element it encounters contains the title, which may or may not be the case. I have a number of my own editions of plays in which the title appears in a “div” element that is styled using CSS and the text “Dramatis Personae” appears in the first header element. When viewed in Stanza, all of my plays are entitled “Dramatis Personae.”

    As for CSS styling, Stanza appears to ignore it completely. The reason that I bother to generate my own editions, which are all adapted from Project Gutenberg texts that are already available in HTML editions, is so that I have complete control over the appearance of these editions using CSS. This makes Stanza essentially useless for viewing these editions since all of the formatting that I have added with tender loving care is discarded.

    If my assumptions are correct, I consider it rather misleading to say that Stanza “supports” HTML e-books. It seems to me it would be more accurate to say that Stanza can extract content from HTML files and render it, possibly inaccurately.

    I’d be very interested to hear from Marc on this matter.

    (Aside for those keeping score: My third attempt to share files between my Mac and my iPod using three different releases of Stanza was no more successful than the first two. Although the iPod client now succeeds in finding the Mac server, establishing a connection, and determining what books are available for sharing, it times out while attempting to transfer a book.)

  7. As for CSS styling, Stanza appears to ignore it completely.

    If my assumptions are correct, I consider it rather misleading to say that Stanza “supports” HTML e-books.

    By extension it is misleading to say that Stanza supports ePub.

    It seems strange that

    using Webkit on Mac and IE on Windows to do the rendering

    the result is inability to render even simple css. I agree with Todd Jonz that it seems that HTML is not rendered in Stanza, but rather “processed” to extract content from it.

    If using IE or Webkit were the case then there were no need for such extraction of content.

    So, it is completely unclear how Stanza uses IE and Webkit and what are Stanza’s real possibilities for handling HTML.

The TeleRead community values your civil and thoughtful comments. We use a cache, so expect a delay. Problems? E-mail newteleread@gmail.com.