<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Libris eBook Reader coming to iPhone, via Java Virtual Machine?</title>
	<atom:link href="http://www.teleread.org/2008/03/10/libris-ebook-reader-coming-to-iphone-via-java-virtual-machine/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.teleread.org/2008/03/10/libris-ebook-reader-coming-to-iphone-via-java-virtual-machine/</link>
	<description>News &#38; views on e-books, libraries, publishing and related topics</description>
	<lastBuildDate>Sun, 08 Nov 2009 03:38:33 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: David</title>
		<link>http://www.teleread.org/2008/03/10/libris-ebook-reader-coming-to-iphone-via-java-virtual-machine/comment-page-1/#comment-774880</link>
		<dc:creator>David</dc:creator>
		<pubDate>Thu, 24 Apr 2008 17:59:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.org/blog/2008/03/10/libris-ebook-reader-coming-to-iphone-via-java-virtual-machine/#comment-774880</guid>
		<description>Give reader a try.  http://reader.dbelement.com  It&#039;s perfect for eBooks and it has all features  you would expect from a high quality eBook reader (One touch scrolling, font-size manipulation, section skipping, live bookmarking, and tons more.  )  not to mention it looks better than any other eBook reader out there.

iphoneappreviews.blogspot.com/</description>
		<content:encoded><![CDATA[<p>Give reader a try.  <a href="http://reader.dbelement.com" rel="nofollow">http://reader.dbelement.com</a>  It&#8217;s perfect for eBooks and it has all features  you would expect from a high quality eBook reader (One touch scrolling, font-size manipulation, section skipping, live bookmarking, and tons more.  )  not to mention it looks better than any other eBook reader out there.</p>
<p>iphoneappreviews.blogspot.com/</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Cane</title>
		<link>http://www.teleread.org/2008/03/10/libris-ebook-reader-coming-to-iphone-via-java-virtual-machine/comment-page-1/#comment-733135</link>
		<dc:creator>Mike Cane</dc:creator>
		<pubDate>Mon, 10 Mar 2008 22:13:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.org/blog/2008/03/10/libris-ebook-reader-coming-to-iphone-via-java-virtual-machine/#comment-733135</guid>
		<description>eBabel may be with us a long, long time.

Someone pointed out to me that, in effect, iSDKed iPhone apps will be able to address their own files (like the &quot;iPod app&quot; on the iPhone does).

But here&#039;s where it gets hairy, eBabelish, and no fun:

Let&#039;s say you are a madman (ie, David Rothman!) and install all the book apps that come down the pike onto your iPhone.

Let&#039;s say you have 3 of these apps that can read the same ebook format.

Well, guess what?

Each of those three will require *its own copy* of an ebook.  All three can *not* dip into a shared storage area to, say, pull up an ebook in, say, I don&#039;t know, Palm DOC format (or whatever).  Each app will need *its own copy*, even though all three apps can read the same file format.

This is my understanding of how things work (with the beta iSDK of today).

Something for you to investigate, David!</description>
		<content:encoded><![CDATA[<p>eBabel may be with us a long, long time.</p>
<p>Someone pointed out to me that, in effect, iSDKed iPhone apps will be able to address their own files (like the &#8220;iPod app&#8221; on the iPhone does).</p>
<p>But here&#8217;s where it gets hairy, eBabelish, and no fun:</p>
<p>Let&#8217;s say you are a madman (ie, David Rothman!) and install all the book apps that come down the pike onto your iPhone.</p>
<p>Let&#8217;s say you have 3 of these apps that can read the same ebook format.</p>
<p>Well, guess what?</p>
<p>Each of those three will require *its own copy* of an ebook.  All three can *not* dip into a shared storage area to, say, pull up an ebook in, say, I don&#8217;t know, Palm DOC format (or whatever).  Each app will need *its own copy*, even though all three apps can read the same file format.</p>
<p>This is my understanding of how things work (with the beta iSDK of today).</p>
<p>Something for you to investigate, David!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
