<?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 for Threepress Consulting blog</title>
	<atom:link href="http://blog.threepress.org/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.threepress.org</link>
	<description>Threepress creates software for publishers, educators and authors.</description>
	<lastBuildDate>Fri, 12 Mar 2010 09:22:18 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on New ePub Zen Garden style: Gibson by Adam Scott by devblog.feedmyereader.de &#187; Blog Archive &#187; Neuer Style im epubzengarden</title>
		<link>http://blog.threepress.org/2010/03/10/new-epub-zen-garden-style-gibson-by-adam-scott/comment-page-1/#comment-2320</link>
		<dc:creator>devblog.feedmyereader.de &#187; Blog Archive &#187; Neuer Style im epubzengarden</dc:creator>
		<pubDate>Fri, 12 Mar 2010 09:22:18 +0000</pubDate>
		<guid isPermaLink="false">http://blog.threepress.org/?p=1248#comment-2320</guid>
		<description>[...] http://blog.threepress.org/2010/03/10/new-epub-zen-garden-style-gibson-by-adam-scott/ [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://blog.threepress.org/2010/03/10/new-epub-zen-garden-style-gibson-by-adam-scott/" rel="nofollow">http://blog.threepress.org/2010/03/10/new-epub-zen-garden-style-gibson-by-adam-scott/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Using Flash video in ePub by Liza Daly</title>
		<link>http://blog.threepress.org/2009/11/14/using-flash-video-in-epub/comment-page-1/#comment-2317</link>
		<dc:creator>Liza Daly</dc:creator>
		<pubDate>Thu, 11 Mar 2010 17:55:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.threepress.org/?p=854#comment-2317</guid>
		<description>I first heard about the licensing issue here as part of the discussion about -- what else? -- video in HTML5: &lt;a href=&quot;http://diveintohtml5.org/video.html#licensing&quot; rel=&quot;nofollow&quot;&gt;Dive into HTML5&lt;/a&gt; by Mark Pilgrim.</description>
		<content:encoded><![CDATA[<p>I first heard about the licensing issue here as part of the discussion about &#8212; what else? &#8212; video in HTML5: <a href="http://diveintohtml5.org/video.html#licensing" rel="nofollow">Dive into HTML5</a> by Mark Pilgrim.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Using Flash video in ePub by Peter Collingridge</title>
		<link>http://blog.threepress.org/2009/11/14/using-flash-video-in-epub/comment-page-1/#comment-2316</link>
		<dc:creator>Peter Collingridge</dc:creator>
		<pubDate>Thu, 11 Mar 2010 17:42:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.threepress.org/?p=854#comment-2316</guid>
		<description>On licensing fees - it is my understanding that MP3 also comes with a license fee that has (at times) been recouped by the license holders. It may be ±2% of gross. That concern is one of the reasons we prefer to use AAC audio encoding in our Apps; AAC is an open format that also has the benefit of delivering higher quality audio at smaller file sizes. However, it is not (yet) as widely supported as MP3, but it is supported by Apple, which makes the decision a no-brainer for us.</description>
		<content:encoded><![CDATA[<p>On licensing fees &#8211; it is my understanding that MP3 also comes with a license fee that has (at times) been recouped by the license holders. It may be ±2% of gross. That concern is one of the reasons we prefer to use AAC audio encoding in our Apps; AAC is an open format that also has the benefit of delivering higher quality audio at smaller file sizes. However, it is not (yet) as widely supported as MP3, but it is supported by Apple, which makes the decision a no-brainer for us.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Using Flash video in ePub by Dave Thomas</title>
		<link>http://blog.threepress.org/2009/11/14/using-flash-video-in-epub/comment-page-1/#comment-2315</link>
		<dc:creator>Dave Thomas</dc:creator>
		<pubDate>Thu, 11 Mar 2010 17:30:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.threepress.org/?p=854#comment-2315</guid>
		<description>Be careful recommending H.264—you may be liable to pay royalties on paid content (and, starting next year, on free content) that includes H.264-encoded content. I&#039;m no expert on this, but I&#039;m scared by what I read. (http://www.streaminglearningcenter.com/articles/h264-royalties-what-you-need-to-know.html and http://www.streamingmedia.com/article.asp?id=11011&amp;page=1&amp;c=7 give some background)</description>
		<content:encoded><![CDATA[<p>Be careful recommending H.264—you may be liable to pay royalties on paid content (and, starting next year, on free content) that includes H.264-encoded content. I&#8217;m no expert on this, but I&#8217;m scared by what I read. (<a href="http://www.streaminglearningcenter.com/articles/h264-royalties-what-you-need-to-know.html" rel="nofollow">http://www.streaminglearningcenter.com/articles/h264-royalties-what-you-need-to-know.html</a> and <a href="http://www.streamingmedia.com/article.asp?id=11011&amp;page=1&amp;c=7" rel="nofollow">http://www.streamingmedia.com/article.asp?id=11011&amp;page=1&amp;c=7</a> give some background)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Using Flash video in ePub by Hamranhansenhansen</title>
		<link>http://blog.threepress.org/2009/11/14/using-flash-video-in-epub/comment-page-1/#comment-2313</link>
		<dc:creator>Hamranhansenhansen</dc:creator>
		<pubDate>Thu, 11 Mar 2010 05:04:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.threepress.org/?p=854#comment-2313</guid>
		<description>&gt; Flash
&gt; QuickTime

Neither of those are suitable, because they are proprietary to Adobe and Apple respectively, and so they are not supported on all platforms. In order to support either of those, a device maker has to license software from Adobe or Apple. Most video playing devices don&#039;t have the CPU power to run FlashPlayer or QuickTime Player, that is PC software.

There is a universal consumer video format called ISO MPEG-4 H.264/AAC. It succeeded the MPEG-2 found on the DVD and the MPEG-1 found on Video CD about 10 years ago. It&#039;s vendor neutral, any device maker can use it in their device or software player on equal terms with all other device makers.

ISO MPEG-4 plays not just in both FlashPlayer and QuickTime Player on Mac/PC, which would be remarkable in itself, but also on iPod and other media players, iPhone and other smartphones, iPad and other tablets, set top boxes, game consoles, Blu-Ray Disc, and so on and so on. Every video on YouTube is stored as MPEG-4, and every video ever sold from iTunes is MPEG-4. Also, if you shoot video with a Flip or iPod or iPhone camcorder, that is MPEG-4. In the same way a DVD Player always has an MPEG-2 decoder, all of the devices that succeed the DVD Player have MPEG-4 decoders.

A key thing to understand is that devices other than Mac and PC do not have large general purpose CPU&#039;s that can run any arbitrary codec as software. Instead, they have dedicated video decoder chips that can decode ISO MPEG-4 with high efficiency and very low battery use. That&#039;s why the iPad can play 10 hours of video, it&#039;s playing through a hardware device that is highly optimized, not through a software codec on a general purpose CPU, as it would on many PC&#039;s. (Macs have H.264 decoders in their GPU&#039;s.)

Another thing to consider is bandwidth. If you have a book with Flash video in it, and you replace that video with ISO MPEG-4 H.264, the weight of the video will be 20% of what it was. (And it still plays in FlashPlayer.) When you consider readers will be downloading your book over cellular connections, and there are limits in some cases where a fat book has to be downloaded over Wi-Fi, this is important.

As for quality, ISO MPEG-4 scales from YouTube to Blu-Ray HD. Flash video does not do HD.

So if you want universal playback, start with the universal video format. Include an image as fallback content for devices that can&#039;t play video, and text for devices that can&#039;t display images. But I would be very suspicious of doing any other audio video formats as that time is likely wasted, and likely doubles or triples the weight of your book for all readers for no good reason.

&gt; since the iPhone doesn’t support flash video

There are no mobiles that support Flash video (zero, none, nada), it is not just the iPhone that does not support it. Flash video only plays in Adobe FlashPlayer, which as I write this (2010-03-10) runs only on Mac and PC platforms and requires a desktop-class CPU equivalent to a P4 2GHz, which is many times the computational power of a mobile. A version of FlashPlayer for mobiles has been promised by Adobe for over 3 years now but has still not shipped. FlashPlayer is Mac/PC software. Authoring books for FlashPlayer is like shipping your book as a Word document or InDesign document. Movies don&#039;t ship in Final Cut, music doesn&#039;t ship in Logic format.

Video in books has to be universal because many books really benefit from it as essential content, not just an add-on frosting layer. For example, tech books: a frozen shot of a cursor hovering over Photoshop or a wrench hovering in mid-air is just not nearly as good as a short video showing the entire technique. Obviously books about movies should have movie clips illustrating the text. So books benefit from standardized consumer video as much as music and video players have benefited.</description>
		<content:encoded><![CDATA[<p>&gt; Flash<br />
&gt; QuickTime</p>
<p>Neither of those are suitable, because they are proprietary to Adobe and Apple respectively, and so they are not supported on all platforms. In order to support either of those, a device maker has to license software from Adobe or Apple. Most video playing devices don&#8217;t have the CPU power to run FlashPlayer or QuickTime Player, that is PC software.</p>
<p>There is a universal consumer video format called ISO MPEG-4 H.264/AAC. It succeeded the MPEG-2 found on the DVD and the MPEG-1 found on Video CD about 10 years ago. It&#8217;s vendor neutral, any device maker can use it in their device or software player on equal terms with all other device makers.</p>
<p>ISO MPEG-4 plays not just in both FlashPlayer and QuickTime Player on Mac/PC, which would be remarkable in itself, but also on iPod and other media players, iPhone and other smartphones, iPad and other tablets, set top boxes, game consoles, Blu-Ray Disc, and so on and so on. Every video on YouTube is stored as MPEG-4, and every video ever sold from iTunes is MPEG-4. Also, if you shoot video with a Flip or iPod or iPhone camcorder, that is MPEG-4. In the same way a DVD Player always has an MPEG-2 decoder, all of the devices that succeed the DVD Player have MPEG-4 decoders.</p>
<p>A key thing to understand is that devices other than Mac and PC do not have large general purpose CPU&#8217;s that can run any arbitrary codec as software. Instead, they have dedicated video decoder chips that can decode ISO MPEG-4 with high efficiency and very low battery use. That&#8217;s why the iPad can play 10 hours of video, it&#8217;s playing through a hardware device that is highly optimized, not through a software codec on a general purpose CPU, as it would on many PC&#8217;s. (Macs have H.264 decoders in their GPU&#8217;s.)</p>
<p>Another thing to consider is bandwidth. If you have a book with Flash video in it, and you replace that video with ISO MPEG-4 H.264, the weight of the video will be 20% of what it was. (And it still plays in FlashPlayer.) When you consider readers will be downloading your book over cellular connections, and there are limits in some cases where a fat book has to be downloaded over Wi-Fi, this is important.</p>
<p>As for quality, ISO MPEG-4 scales from YouTube to Blu-Ray HD. Flash video does not do HD.</p>
<p>So if you want universal playback, start with the universal video format. Include an image as fallback content for devices that can&#8217;t play video, and text for devices that can&#8217;t display images. But I would be very suspicious of doing any other audio video formats as that time is likely wasted, and likely doubles or triples the weight of your book for all readers for no good reason.</p>
<p>&gt; since the iPhone doesn’t support flash video</p>
<p>There are no mobiles that support Flash video (zero, none, nada), it is not just the iPhone that does not support it. Flash video only plays in Adobe FlashPlayer, which as I write this (2010-03-10) runs only on Mac and PC platforms and requires a desktop-class CPU equivalent to a P4 2GHz, which is many times the computational power of a mobile. A version of FlashPlayer for mobiles has been promised by Adobe for over 3 years now but has still not shipped. FlashPlayer is Mac/PC software. Authoring books for FlashPlayer is like shipping your book as a Word document or InDesign document. Movies don&#8217;t ship in Final Cut, music doesn&#8217;t ship in Logic format.</p>
<p>Video in books has to be universal because many books really benefit from it as essential content, not just an add-on frosting layer. For example, tech books: a frozen shot of a cursor hovering over Photoshop or a wrench hovering in mid-air is just not nearly as good as a short video showing the entire technique. Obviously books about movies should have movie clips illustrating the text. So books benefit from standardized consumer video as much as music and video players have benefited.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on CSS columns for ebook text by Liza Daly</title>
		<link>http://blog.threepress.org/2010/03/08/css-columns-for-ebook-text/comment-page-1/#comment-2312</link>
		<dc:creator>Liza Daly</dc:creator>
		<pubDate>Thu, 11 Mar 2010 00:32:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.threepress.org/?p=1239#comment-2312</guid>
		<description>Apparently getBoundingClientRect doesn&#039;t work on the iPhone anyway (I remember experimenting with it ages ago; this may have been why I gave up on it.) c.f. http://twitter.com/johnboxall/status/10291708368</description>
		<content:encoded><![CDATA[<p>Apparently getBoundingClientRect doesn&#8217;t work on the iPhone anyway (I remember experimenting with it ages ago; this may have been why I gave up on it.) c.f. <a href="http://twitter.com/johnboxall/status/10291708368" rel="nofollow">http://twitter.com/johnboxall/status/10291708368</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Three JavaScript ePub Readers by What We&#8217;re Reading - Open Blog - NYTimes.com</title>
		<link>http://blog.threepress.org/2010/02/06/three-javascript-epub-readers/comment-page-1/#comment-2311</link>
		<dc:creator>What We&#8217;re Reading - Open Blog - NYTimes.com</dc:creator>
		<pubDate>Wed, 10 Mar 2010 14:38:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.threepress.org/?p=1198#comment-2311</guid>
		<description>[...] Amazing JavaScript Who knew there were three JavaScript-based ePub readers out there? What&#8217;s more, you can use JavaScript to unzip files. [...]</description>
		<content:encoded><![CDATA[<p>[...] Amazing JavaScript Who knew there were three JavaScript-based ePub readers out there? What&#8217;s more, you can use JavaScript to unzip files. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on CSS columns for ebook text by Liza Daly</title>
		<link>http://blog.threepress.org/2010/03/08/css-columns-for-ebook-text/comment-page-1/#comment-2310</link>
		<dc:creator>Liza Daly</dc:creator>
		<pubDate>Wed, 10 Mar 2010 01:49:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.threepress.org/?p=1239#comment-2310</guid>
		<description>Oh no, I was experimenting with getBoundingClientRect based on finding it in your code (we only care about WebKit on the mobile devices).  So far it was meeting my needs (paired with document.elementFromPoint), but I hadn&#039;t experimented a ton.

element.scrollIntoView is an interesting idea too -- thanks!  (When I had a columns implementation it was basically the same as yours.)</description>
		<content:encoded><![CDATA[<p>Oh no, I was experimenting with getBoundingClientRect based on finding it in your code (we only care about WebKit on the mobile devices).  So far it was meeting my needs (paired with document.elementFromPoint), but I hadn&#8217;t experimented a ton.</p>
<p>element.scrollIntoView is an interesting idea too &#8212; thanks!  (When I had a columns implementation it was basically the same as yours.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on CSS columns for ebook text by Joseph</title>
		<link>http://blog.threepress.org/2010/03/08/css-columns-for-ebook-text/comment-page-1/#comment-2308</link>
		<dc:creator>Joseph</dc:creator>
		<pubDate>Wed, 10 Mar 2010 01:41:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.threepress.org/?p=1239#comment-2308</guid>
		<description>I agree — finding the real location of columned elements has been something of a frustration for Monocle too. GetClientRects is promising, but was still erroneous in the last testing I did (a few weeks ago).

My solution is probably peculiar to Monocle&#039;s column-width/scroll setup, but I found that using element.scrollIntoView then checking scrollLeft gave me at least a useful x coordinate. 

It&#039;s a hack I&#039;d love to dig out, though. Great news that it works in the latest nightly.</description>
		<content:encoded><![CDATA[<p>I agree — finding the real location of columned elements has been something of a frustration for Monocle too. GetClientRects is promising, but was still erroneous in the last testing I did (a few weeks ago).</p>
<p>My solution is probably peculiar to Monocle&#8217;s column-width/scroll setup, but I found that using element.scrollIntoView then checking scrollLeft gave me at least a useful x coordinate. </p>
<p>It&#8217;s a hack I&#8217;d love to dig out, though. Great news that it works in the latest nightly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Ibis Reader and BookServer by BookServer，电子书的未来架构支柱 &#124; 数字出版研究</title>
		<link>http://blog.threepress.org/2009/11/02/ibis-reader-and-bookserver/comment-page-1/#comment-2303</link>
		<dc:creator>BookServer，电子书的未来架构支柱 &#124; 数字出版研究</dc:creator>
		<pubDate>Tue, 09 Mar 2010 08:46:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.threepress.org/?p=631#comment-2303</guid>
		<description>[...] 目前的确如此…，毕竟是个全新开展的计划架构，尚未全然搞懂，不过有跟推的朋友大概看过之前发过的一篇：下一代的电子书系统架构 Ibis Reader and BookServer，几个月之内就会有实作出来了。 [...]</description>
		<content:encoded><![CDATA[<p>[...] 目前的确如此…，毕竟是个全新开展的计划架构，尚未全然搞懂，不过有跟推的朋友大概看过之前发过的一篇：下一代的电子书系统架构 Ibis Reader and BookServer，几个月之内就会有实作出来了。 [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
