<?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: eCub freebie for creating ePub books: Try it and help the dev with bug reports!</title>
	<atom:link href="http://www.teleread.org/2009/01/13/ecub-try-it-and-help-the-dev-with-bug-reports/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.teleread.org/2009/01/13/ecub-try-it-and-help-the-dev-with-bug-reports/</link>
	<description>News &#38; views on e-books, libraries, publishing and related topics</description>
	<lastBuildDate>Sat, 21 Nov 2009 20:01:59 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dick Pearson</title>
		<link>http://www.teleread.org/2009/01/13/ecub-try-it-and-help-the-dev-with-bug-reports/comment-page-1/#comment-1009203</link>
		<dc:creator>Dick Pearson</dc:creator>
		<pubDate>Mon, 02 Feb 2009 18:14:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.org/blog/2009/01/13/ecub-try-it-and-help-the-dev-with-bug-reports/#comment-1009203</guid>
		<description>I think eCub is a super tool, but you DO also need a suitable set of web tools: I use Ace HTML and TopStyle Pro so I validate my XHTML and CSS long before creating the book.
I solved problems with books I created for my Sony reader by making sure that all my constituent html files were less that 100K.  Anything larger than 200 KB per file, and the Sony Reader gives up and sulks!  It doesn&#039;t seem to care about the overall size of the .epub file - for instance my copy of the Bible runs to 1.66 MB and works (slowly) without problem.</description>
		<content:encoded><![CDATA[<p>I think eCub is a super tool, but you DO also need a suitable set of web tools: I use Ace HTML and TopStyle Pro so I validate my XHTML and CSS long before creating the book.<br />
I solved problems with books I created for my Sony reader by making sure that all my constituent html files were less that 100K.  Anything larger than 200 KB per file, and the Sony Reader gives up and sulks!  It doesn&#8217;t seem to care about the overall size of the .epub file &#8211; for instance my copy of the Bible runs to 1.66 MB and works (slowly) without problem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Cane</title>
		<link>http://www.teleread.org/2009/01/13/ecub-try-it-and-help-the-dev-with-bug-reports/comment-page-1/#comment-1002847</link>
		<dc:creator>Mike Cane</dc:creator>
		<pubDate>Wed, 14 Jan 2009 16:49:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.org/blog/2009/01/13/ecub-try-it-and-help-the-dev-with-bug-reports/#comment-1002847</guid>
		<description>Uh-oh.  Just looked a PRE-alpha size of ePub.  It is 2.47MB.  That&#039;s not good, is it?</description>
		<content:encoded><![CDATA[<p>Uh-oh.  Just looked a PRE-alpha size of ePub.  It is 2.47MB.  That&#8217;s not good, is it?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Cane</title>
		<link>http://www.teleread.org/2009/01/13/ecub-try-it-and-help-the-dev-with-bug-reports/comment-page-1/#comment-1002845</link>
		<dc:creator>Mike Cane</dc:creator>
		<pubDate>Wed, 14 Jan 2009 16:47:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.org/blog/2009/01/13/ecub-try-it-and-help-the-dev-with-bug-reports/#comment-1002845</guid>
		<description>300K is not much!!  Especially with a book that has 27 chapters *and* about *70* photos!

I could always chop it into bits.  Horrors.</description>
		<content:encoded><![CDATA[<p>300K is not much!!  Especially with a book that has 27 chapters *and* about *70* photos!</p>
<p>I could always chop it into bits.  Horrors.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hadrien</title>
		<link>http://www.teleread.org/2009/01/13/ecub-try-it-and-help-the-dev-with-bug-reports/comment-page-1/#comment-1002808</link>
		<dc:creator>Hadrien</dc:creator>
		<pubDate>Wed, 14 Jan 2009 15:10:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.org/blog/2009/01/13/ecub-try-it-and-help-the-dev-with-bug-reports/#comment-1002808</guid>
		<description>I can think of several reasons why it could potentially fail: for example incorrect XHTML markup or if you have a flow that&#039;s larger than 300k on the Sony Reader.</description>
		<content:encoded><![CDATA[<p>I can think of several reasons why it could potentially fail: for example incorrect XHTML markup or if you have a flow that&#8217;s larger than 300k on the Sony Reader.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Rothman</title>
		<link>http://www.teleread.org/2009/01/13/ecub-try-it-and-help-the-dev-with-bug-reports/comment-page-1/#comment-1002583</link>
		<dc:creator>David Rothman</dc:creator>
		<pubDate>Wed, 14 Jan 2009 00:50:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.org/blog/2009/01/13/ecub-try-it-and-help-the-dev-with-bug-reports/#comment-1002583</guid>
		<description>Keep us posted, Mike, and best of luck with your own noble experiment with Abyss! - David</description>
		<content:encoded><![CDATA[<p>Keep us posted, Mike, and best of luck with your own noble experiment with Abyss! &#8211; David</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Cane</title>
		<link>http://www.teleread.org/2009/01/13/ecub-try-it-and-help-the-dev-with-bug-reports/comment-page-1/#comment-1002580</link>
		<dc:creator>Mike Cane</dc:creator>
		<pubDate>Wed, 14 Jan 2009 00:42:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.org/blog/2009/01/13/ecub-try-it-and-help-the-dev-with-bug-reports/#comment-1002580</guid>
		<description>See, I was afraid of that very thing.  That I&#039;d get Abyss into finished form finally, only for it to be unusable on a Sony Reader or iPhone.

There&#039;s a validation tool sorta link in eCub, but I&#039;ve never tried it.

I&#039;m not even in alpha shape for the entire eBook yet, so this can wait til the end.  There can&#039;t be anything *monstrously* wrong with the ePub file, can there?  It&#039;s all based on the HTML, after all.

I&#039;m also going to do a MobiPocket version just to view on my LifeDrive as a test (LifeDrive screen same size as iPhone, see? good for photo scaling!).  That one I will *not* distribute because I do NOT want to encourage people to use that obsolete and monopolistic file format.</description>
		<content:encoded><![CDATA[<p>See, I was afraid of that very thing.  That I&#8217;d get Abyss into finished form finally, only for it to be unusable on a Sony Reader or iPhone.</p>
<p>There&#8217;s a validation tool sorta link in eCub, but I&#8217;ve never tried it.</p>
<p>I&#8217;m not even in alpha shape for the entire eBook yet, so this can wait til the end.  There can&#8217;t be anything *monstrously* wrong with the ePub file, can there?  It&#8217;s all based on the HTML, after all.</p>
<p>I&#8217;m also going to do a MobiPocket version just to view on my LifeDrive as a test (LifeDrive screen same size as iPhone, see? good for photo scaling!).  That one I will *not* distribute because I do NOT want to encourage people to use that obsolete and monopolistic file format.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
