<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Threepress Consulting blog &#187; kindle</title>
	<atom:link href="http://blog.threepress.org/category/kindle/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.threepress.org</link>
	<description>Threepress creates software for publishers, educators and authors.</description>
	<lastBuildDate>Mon, 09 Jan 2012 13:02:39 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Quakebook: a community-sourced book benefiting Japan</title>
		<link>http://blog.threepress.org/2011/04/19/quakebook-a-community-sourced-book-benefiting-japan/</link>
		<comments>http://blog.threepress.org/2011/04/19/quakebook-a-community-sourced-book-benefiting-japan/#comments</comments>
		<pubDate>Tue, 19 Apr 2011 16:42:34 +0000</pubDate>
		<dc:creator>Liza Daly</dc:creator>
				<category><![CDATA[book design]]></category>
		<category><![CDATA[content]]></category>
		<category><![CDATA[digitization]]></category>
		<category><![CDATA[kindle]]></category>

		<guid isPermaLink="false">http://blog.threepress.org/?p=1904</guid>
		<description><![CDATA[We were very pleased to be able to work on the ebook version of this innovative project.

Quakebook is:
A Twitter-sourced charity book about how the Japanese Earthquake at 2:46 on March 11, 2011 affected us all. All revenues from the QuakeBook Book go to the Japan Red Cross.
Threepress took the print-ready InDesign file and converted it [...]]]></description>
			<content:encoded><![CDATA[<p>We were very pleased to be able to work on the ebook version of this innovative project.</p>
<p><a href="http://quakebook.org/"><img src="http://3press-blog.s3.amazonaws.com/sm-QuakeBook-cover_M1.jpg" alt="Quakebook cover" /></a></p>
<p><a href="http://quakebook.org/">Quakebook</a> is:</p>
<blockquote><p>A Twitter-sourced charity book about how the Japanese Earthquake at 2:46 on March 11, 2011 affected us all. All revenues from the QuakeBook Book go to the Japan Red Cross.</p></blockquote>
<p>Threepress took the print-ready InDesign file and converted it to EPUB (which was then provided to Amazon for conversion to Mobi).  It took a ridiculous amount of time given the length of the title &#8212; almost 20 man-hours, compressed into just a few calendar hours &#8212; typical of InDesign conversions that weren&#8217;t EPUB-optimized.  InDesign&#8217;s output really needs to be more fault-tolerant; it should not be a specialized skill to just create EPUB-friendly InDesign files.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.threepress.org/2011/04/19/quakebook-a-community-sourced-book-benefiting-japan/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Better single-source Mobi/EPUB files</title>
		<link>http://blog.threepress.org/2010/11/16/better-single-source-mobiepub-files/</link>
		<comments>http://blog.threepress.org/2010/11/16/better-single-source-mobiepub-files/#comments</comments>
		<pubDate>Tue, 16 Nov 2010 17:12:46 +0000</pubDate>
		<dc:creator>Liza Daly</dc:creator>
				<category><![CDATA[epub]]></category>
		<category><![CDATA[kindle]]></category>

		<guid isPermaLink="false">http://blog.threepress.org/?p=1708</guid>
		<description><![CDATA[Edited 3:15pm: Though the current epubcheck considers the sample below to be valid, the approach described in this post is likely not strictly valid according to EPUB 2.0.1. The XHTML TOC is not necessarily meant to be part of the EPUB publication as it is for Kindle consumption only, but it is included in the [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Edited 3:15pm:</strong> <em>Though the current epubcheck considers the sample below to be valid, the approach described in this post is likely not strictly valid according to EPUB 2.0.1. The XHTML TOC is not necessarily meant to be part of the EPUB publication as it is for Kindle consumption only, but it is included in the manifest. Proceed with caution.</em></p>
<p>Many publishers prefer to create only a single EPUB file that can be distributed both into EPUB reading system channels like iBooks and B&#038;N, but can also be distributed in the Kindle ecosystem after conversion by <a href="http://www.amazon.com/gp/feature.html?ie=UTF8&#038;docId=1000234621">kindlegen</a>, <a href="http://calibre-ebook.com/">Calibre</a> or Amazon&#8217;s internal systems. </p>
<p>There are a few problems with this. One is that Mobipocket&#8217;s primitive HTML support conflicts with the requirement that commercial EPUBs be valid XHTML 1.1.  There are some design elements that are difficult to do &#8220;right&#8221; in Mobipocket while still maintaining compliance with EPUB.  Our best recommendation in this case is to optimize the design for EPUB reading systems that are based on browser engines; that is clearly where the next generation of EPUB readers are going, and ebooks should be designed as much for future readers as for the state of the art today.  Designers who need fine control over the look of Kindle books should first buy <a href="http://kindleformatting.com/book/">Kindle Formatting</a> by Joshua Tallent, and then be prepared to produce two separate EPUB files: a Mobi-specific one and a valid one for distribution in the other channels.</p>
<p>If exact formatting isn&#8217;t critical, then the single-source approach can work, but there&#8217;s one other layout issue: Kindle requires both the EPUB NCX Table of Contents as well as a table of contents marked up in XHTML. This requirement is silly — an XHTML TOC should only be included if the creator really wanted custom layout — but there it is. </p>
<p>This leads to content creators including an XHTML TOC in their EPUB, which is unnecessary in EPUB readers, takes up valuable front-matter space, and impedes the flow of reading.</p>
<p>Here&#8217;s a quick trick to bundling an XHTML TOC and &#8220;hiding&#8221; it from an EPUB reader: <em>omit the XHTML TOC from the spine</em>.</p>
<p>Sample OPF:</p>
<pre class="brush: xml;">
&lt;?xml version=&quot;1.0&quot;?&gt;
&lt;package xmlns=&quot;http://www.idpf.org/2007/opf&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; unique-identifier=&quot;bookid&quot; version=&quot;2.0&quot;&gt;
  &lt;metadata&gt;
    &lt;dc:title&gt;Test demonstrating mobi TOC that does not appear in an EPUB&lt;/dc:title&gt;
    &lt;dc:creator&gt;Threepress Consulting Inc.&lt;/dc:creator&gt;
    &lt;dc:description&gt;A demonstration of including a Mobi-friendly XHTML TOC in an EPUB&lt;/dc:description&gt;
    &lt;dc:date&gt;2010&lt;/dc:date&gt;
    &lt;dc:rights&gt;Public domain&lt;/dc:rights&gt;
    &lt;dc:identifier id=&quot;bookid&quot;&gt;urn:uuid:AB7456FF-DDC7-4DB1-AEFB-153DDDBA9F9B&lt;/dc:identifier&gt;
    &lt;dc:language&gt;en&lt;/dc:language&gt;
  &lt;/metadata&gt;
  &lt;manifest&gt;
    &lt;item id=&quot;ncx&quot; href=&quot;toc.ncx&quot; media-type=&quot;application/x-dtbncx+xml&quot;/&gt;
    &lt;item id=&quot;untitled-5&quot; href=&quot;Untitled-5.xhtml&quot; media-type=&quot;application/xhtml+xml&quot;/&gt;
    &lt;item id=&quot;toc&quot; href=&quot;toc.xhtml&quot; media-type=&quot;application/xhtml+xml&quot;/&gt;
    &lt;item id=&quot;css&quot; href=&quot;template.css&quot; media-type=&quot;text/css&quot;/&gt;
  &lt;/manifest&gt;
  &lt;spine toc=&quot;ncx&quot;&gt;
    &lt;itemref idref=&quot;untitled-5&quot;/&gt;
  &lt;/spine&gt;
  &lt;guide&gt;
    &lt;reference href=&quot;toc.xhtml&quot; type=&quot;toc&quot; title=&quot;Table of Contents&quot;/&gt;
  &lt;/guide&gt;
&lt;/package&gt;
</pre>
<p>In this case, the <code>guide</code> entry tells Kindle where to find the XHTML TOC, but omitting it from the <code>spine</code> means that it is not added to the &#8220;linear reading order&#8221; of the book.  It&#8217;s simply not accessible to any EPUB reader.</p>
<p>Thus you have a Kindle-friendly EPUB file that does not burden its EPUB reader cousins with unnecessary cruft.</p>
<p><a href="http://3press-blog.s3.amazonaws.com/single_source_mobi_epub.epub">A complete EPUB sample is attached</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.threepress.org/2010/11/16/better-single-source-mobiepub-files/feed/</wfw:commentRss>
		<slash:comments>26</slash:comments>
		</item>
		<item>
		<title>Video posted for &#8216;Survey of Current E-Readers&#8217;</title>
		<link>http://blog.threepress.org/2009/04/22/video-posted-for-survey-of-current-e-readers/</link>
		<comments>http://blog.threepress.org/2009/04/22/video-posted-for-survey-of-current-e-readers/#comments</comments>
		<pubDate>Wed, 22 Apr 2009 13:08:27 +0000</pubDate>
		<dc:creator>Liza Daly</dc:creator>
				<category><![CDATA[ebooks]]></category>
		<category><![CDATA[kindle]]></category>
		<category><![CDATA[toc]]></category>
		<category><![CDATA[video]]></category>
		<category><![CDATA[epub]]></category>
		<category><![CDATA[ereader]]></category>
		<category><![CDATA[olpc]]></category>
		<category><![CDATA[plasticlogic]]></category>
		<category><![CDATA[sony reader]]></category>
		<category><![CDATA[wireless]]></category>
		<category><![CDATA[xo]]></category>

		<guid isPermaLink="false">http://blog.threepress.org/?p=435</guid>
		<description><![CDATA[O&#8217;Reilly has posted video from my session with Keith Fahlgren on e-reading devices.  
Please enjoy my despair at the beginning as all the wireless-enabled readers interfere with the microphone.
It might be useful to follow along with the slides in the latter half of my talk, when the camera doesn&#8217;t show them.
 
]]></description>
			<content:encoded><![CDATA[<p>O&#8217;Reilly has posted video from my session with Keith Fahlgren on e-reading devices.  </p>
<p>Please enjoy my despair at the beginning as all the wireless-enabled readers interfere with the microphone.</p>
<p>It might be useful to follow along with the <a href="http://blog.threepress.org/2009/02/17/slides-from-survey-of-current-e-readers/">slides</a> in the latter half of my talk, when the camera doesn&#8217;t show them.</p>
<p><embed src="http://blip.tv/play/AfrkRIa7aQ" type="application/x-shockwave-flash" width="475" height="275"  allowscriptaccess="always" allowfullscreen="true"></embed> </p>
]]></content:encoded>
			<wfw:commentRss>http://blog.threepress.org/2009/04/22/video-posted-for-survey-of-current-e-readers/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>On the contentious subject of ebook pricing</title>
		<link>http://blog.threepress.org/2009/02/14/on-the-contentious-subject-of-ebook-pricing/</link>
		<comments>http://blog.threepress.org/2009/02/14/on-the-contentious-subject-of-ebook-pricing/#comments</comments>
		<pubDate>Sat, 14 Feb 2009 17:45:38 +0000</pubDate>
		<dc:creator>Liza Daly</dc:creator>
				<category><![CDATA[devices]]></category>
		<category><![CDATA[ebooks]]></category>
		<category><![CDATA[kindle]]></category>
		<category><![CDATA[ebook]]></category>
		<category><![CDATA[pricing]]></category>

		<guid isPermaLink="false">http://blog.threepress.org/?p=330</guid>
		<description><![CDATA[I had meant to include this as a slide in my e-reader talk but didn&#8217;t have time. 
 I think we can all agree that this is a don&#8217;t.  
 
 
(There&#8217;s a free sample though!)
]]></description>
			<content:encoded><![CDATA[<p>I had meant to include this as a slide in my e-reader talk but didn&#8217;t have time. </p>
<p> I think we can all agree that this is a <strong>don&#8217;t</strong>.  </p>
<p><a href="http://www.amazon.com/Selected-Nuclear-Materials-Engineering-Systems/dp/B001QTVXAK/ref=sr_1_1?ie=UTF8&amp;s=digital-text&amp;qid=1234575412&amp;sr=1-1"><img src="http://ecx.images-amazon.com/images/I/51R4dZMM-0L._SL500_AA242_PIkin-dp-500,BottomRight,-18,38_AA280_SH20_OU01_.jpg" alt=""  align="center" /></a> </p>
<p><img class="aligncenter size-full wp-image-331" title="picture-69" src="http://blog.threepress.org/wp-content/uploads/2009/02/picture-69.png" alt="picture-69" /> </p>
<p>(There&#8217;s a free sample though!)</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.threepress.org/2009/02/14/on-the-contentious-subject-of-ebook-pricing/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

