MobileRead Forums - View Single Post - Why supported formats don't matter to me (very much)

Bob Russell · 11-27-2008, 01:15 PM

When we think about comparing e-book devices, we care mostly about some basics:
* Screen quality
* Battery life
* Size and ease of use
* Supported e-book formats

Sure, there are many other features like screen lights that people care about. And the price certainly matters when deciding whether or not to purchase. But I think this pretty much covers the basics. (I'm sure that if I left out something obvious, we'll see it pop up immediately in the comments!)

Okay. Now let's focus for a moment on the issue of supported formats. First of all, I am going to surprise you by saying that I don't care what format the reader supports natively. As long as there is a way to easily and accurately create that native format (on Linux and Windows), it's okay.

So you might think that lots of formats are very important, but I only care about the following two things:
1) The ability to convert HTML and PDF files for use on the device.
2) Support for my favorite DRM'd format

The only reason I include #2 is obvious - there are always books out there that are only available in DRM'd formats, and I want to be able to purchase and read them. Conversion programs aren't going to do the job unless they strip out the DRM, which is a whole other discussion.

So why don't I care about native text support, for example? Or any of the many other formats? It's simple. Because e-books represent a significant amount of time investment as I read them, I don't mind spending a little bit of time doing a format conversion beforehand. I rarely need to read something particular "by surprise" so I can plan ahead. As long as it's a popular non-DRM'd format, I feel confident that there will be simple ways to convert most files into a simple universal format like HTML, and then from there is can be converted to use on the device.

The only reason I include PDF conversion in the picture is because there are documents that are not-text based, or require special layout. HTML isn't very good for that. Plus, one can grab a free PDF print driver and create a PDF file out of anything that is printable.

There is one huge caveat, however. The software that puts HTML or PDF files on the device must actually work. All the time on every "reasonable" file without problems. It must come out looking good. And the software must be available and continue to be updated for a period of time, and support all popular platforms. Already, that is reason enough for some people to say "I must have native PDF/HTML format support, or the equivalent".

Some people will also object because they don't want to have to do a conversion step at all. They want to pop in an SD card with an RTF file and just start reading. I agree. That is also a nice feature. For me, though, it's not essential. Just nice.

And, finally, I should add one more comment with respect to the e-book format wars. You might think I don't care. Not true. Even though I don't care too much personally about formatting beyond what HTML gives us, there are two huge reasons I care a lot about a universal reflowable e-book format. Number one, I want to eliminate every concern about conversions entirely. If, for example, everyone creates and supports all e-books in ePub, then we all win in terms of reduced complexity and improved compatibility. Ideally, it would be like .txt or .html files, but with more features. Just the way HTML improves on text files, but retains the universality, so might a standard format like ePub if everyone uses it.

And number two, formats matter because there is a feint hope for the holy grail of a common DRM scheme. Imagine every protected e-book using the same interchangeable protection scheme and the same interchangeable key mechanisms. Any e-book reader could read any DRM'd book if you have the right to read it. If you buy a new device, you can still read the same books that you bought. If a company goes out of business, it doesn't stop you from keeping usage of the books. I don't have a lot of hope due to the various disincentives for book sellers and publishers, the need to have a community DRM key server of some type, plus fears of a single DRM-breaking program making everything available to pirates. But we don't know the future, and who knows what can be achieved if people are forced to work together.

I'm sure I've ruffled a few feathers by saying format support is of secondary importance to me in an e-book reader. So let me have it. Why do you agree or disagree?

11-27-2008, 01:15 PM	#1
Bob Russell Recovering Gadget Addict Posts: 5,381 Karma: 676161 Join Date: May 2004 Location: Pittsburgh, PA Device: iPad	Why supported formats don't matter to me (very much) When we think about comparing e-book devices, we care mostly about some basics: * Screen quality * Battery life * Size and ease of use * Supported e-book formats Sure, there are many other features like screen lights that people care about. And the price certainly matters when deciding whether or not to purchase. But I think this pretty much covers the basics. (I'm sure that if I left out something obvious, we'll see it pop up immediately in the comments!) Okay. Now let's focus for a moment on the issue of supported formats. First of all, I am going to surprise you by saying that I don't care what format the reader supports natively. As long as there is a way to easily and accurately create that native format (on Linux and Windows), it's okay. So you might think that lots of formats are very important, but I only care about the following two things: 1) The ability to convert HTML and PDF files for use on the device. 2) Support for my favorite DRM'd format The only reason I include #2 is obvious - there are always books out there that are only available in DRM'd formats, and I want to be able to purchase and read them. Conversion programs aren't going to do the job unless they strip out the DRM, which is a whole other discussion. So why don't I care about native text support, for example? Or any of the many other formats? It's simple. Because e-books represent a significant amount of time investment as I read them, I don't mind spending a little bit of time doing a format conversion beforehand. I rarely need to read something particular "by surprise" so I can plan ahead. As long as it's a popular non-DRM'd format, I feel confident that there will be simple ways to convert most files into a simple universal format like HTML, and then from there is can be converted to use on the device. The only reason I include PDF conversion in the picture is because there are documents that are not-text based, or require special layout. HTML isn't very good for that. Plus, one can grab a free PDF print driver and create a PDF file out of anything that is printable. There is one huge caveat, however. The software that puts HTML or PDF files on the device must actually work. All the time on every "reasonable" file without problems. It must come out looking good. And the software must be available and continue to be updated for a period of time, and support all popular platforms. Already, that is reason enough for some people to say "I must have native PDF/HTML format support, or the equivalent". Some people will also object because they don't want to have to do a conversion step at all. They want to pop in an SD card with an RTF file and just start reading. I agree. That is also a nice feature. For me, though, it's not essential. Just nice. And, finally, I should add one more comment with respect to the e-book format wars. You might think I don't care. Not true. Even though I don't care too much personally about formatting beyond what HTML gives us, there are two huge reasons I care a lot about a universal reflowable e-book format. Number one, I want to eliminate every concern about conversions entirely. If, for example, everyone creates and supports all e-books in ePub, then we all win in terms of reduced complexity and improved compatibility. Ideally, it would be like .txt or .html files, but with more features. Just the way HTML improves on text files, but retains the universality, so might a standard format like ePub if everyone uses it. And number two, formats matter because there is a feint hope for the holy grail of a common DRM scheme. Imagine every protected e-book using the same interchangeable protection scheme and the same interchangeable key mechanisms. Any e-book reader could read any DRM'd book if you have the right to read it. If you buy a new device, you can still read the same books that you bought. If a company goes out of business, it doesn't stop you from keeping usage of the books. I don't have a lot of hope due to the various disincentives for book sellers and publishers, the need to have a community DRM key server of some type, plus fears of a single DRM-breaking program making everything available to pirates. But we don't know the future, and who knows what can be achieved if people are forced to work together. I'm sure I've ruffled a few feathers by saying format support is of secondary importance to me in an e-book reader. So let me have it. Why do you agree or disagree?