<?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: &#8220;Pages&#8221; in ePub: Adobe&#8217;s page-map versus NCX pageList</title>
	<atom:link href="http://blog.threepress.org/2009/11/26/adobe-page-map-versus-ncx-pagelist/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.threepress.org/2009/11/26/adobe-page-map-versus-ncx-pagelist/</link>
	<description>Threepress creates software for publishers, educators and authors.</description>
	<lastBuildDate>Tue, 07 Feb 2012 13:57:55 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Irwin</title>
		<link>http://blog.threepress.org/2009/11/26/adobe-page-map-versus-ncx-pagelist/comment-page-1/#comment-1894</link>
		<dc:creator>Irwin</dc:creator>
		<pubDate>Wed, 23 Dec 2009 15:46:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.threepress.org/?p=790#comment-1894</guid>
		<description>(Sorry, Keith. Thought you were Liza.)</description>
		<content:encoded><![CDATA[<p>(Sorry, Keith. Thought you were Liza.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Irwin</title>
		<link>http://blog.threepress.org/2009/11/26/adobe-page-map-versus-ncx-pagelist/comment-page-1/#comment-1893</link>
		<dc:creator>Irwin</dc:creator>
		<pubDate>Wed, 23 Dec 2009 15:45:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.threepress.org/?p=790#comment-1893</guid>
		<description>The idea of a page is necessarily rooted in reference to the book as physical object. The same way the icon for email is still a paper envelope. Because we&#039;re at a transitional period, most people need the comfort of referring to a &quot;page&quot; rather than a &quot;location&quot; as Kindle puts it. But I would like to point out that Bible readers and scholars have been citing not pages but chapter:verse for a very long time. We just need to get used to applying the same system to all electronic reading material. 

I wish browsers (really the HTML spec) would give you granularity down to the character. I smell a jQuery plugin that needs to be written...

(BTW, I love your work, Liza. Keep it going!)</description>
		<content:encoded><![CDATA[<p>The idea of a page is necessarily rooted in reference to the book as physical object. The same way the icon for email is still a paper envelope. Because we&#8217;re at a transitional period, most people need the comfort of referring to a &#8220;page&#8221; rather than a &#8220;location&#8221; as Kindle puts it. But I would like to point out that Bible readers and scholars have been citing not pages but chapter:verse for a very long time. We just need to get used to applying the same system to all electronic reading material. </p>
<p>I wish browsers (really the HTML spec) would give you granularity down to the character. I smell a jQuery plugin that needs to be written&#8230;</p>
<p>(BTW, I love your work, Liza. Keep it going!)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Micah Bowers</title>
		<link>http://blog.threepress.org/2009/11/26/adobe-page-map-versus-ncx-pagelist/comment-page-1/#comment-1466</link>
		<dc:creator>Micah Bowers</dc:creator>
		<pubDate>Mon, 30 Nov 2009 16:42:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.threepress.org/?p=790#comment-1466</guid>
		<description>Yes, in DE the way the page number display works + the fact that you can&#039;t turn it off is very, very unfortunate (bugs).  I&#039;m looking forward to seeing that fixed. 

BTW, I respectfully disagree about  whether most books need a page map. How else could humans communicate about content locations in a reflowable document?  And, If publishers don&#039;t include it, the reading system has to generate it programatically - which is far less optimal.  Caveat is the lack of consistent implementation to a standard.  So it is a fair question about whether to go with the extension that at least works on Adobe SDK devices or with pagelist which may be supported in the future by some reading systems.</description>
		<content:encoded><![CDATA[<p>Yes, in DE the way the page number display works + the fact that you can&#8217;t turn it off is very, very unfortunate (bugs).  I&#8217;m looking forward to seeing that fixed. </p>
<p>BTW, I respectfully disagree about  whether most books need a page map. How else could humans communicate about content locations in a reflowable document?  And, If publishers don&#8217;t include it, the reading system has to generate it programatically &#8211; which is far less optimal.  Caveat is the lack of consistent implementation to a standard.  So it is a fair question about whether to go with the extension that at least works on Adobe SDK devices or with pagelist which may be supported in the future by some reading systems.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bowerbird</title>
		<link>http://blog.threepress.org/2009/11/26/adobe-page-map-versus-ncx-pagelist/comment-page-1/#comment-1404</link>
		<dc:creator>bowerbird</dc:creator>
		<pubDate>Sat, 28 Nov 2009 07:07:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.threepress.org/?p=790#comment-1404</guid>
		<description>it amazes me how far down this particular road
that you .epub people still need to travel...

i strongly encourage you to spend some more time
engaging in thought and discussion on the topic...

-bowerbird</description>
		<content:encoded><![CDATA[<p>it amazes me how far down this particular road<br />
that you .epub people still need to travel&#8230;</p>
<p>i strongly encourage you to spend some more time<br />
engaging in thought and discussion on the topic&#8230;</p>
<p>-bowerbird</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lindsey Thomas Martin</title>
		<link>http://blog.threepress.org/2009/11/26/adobe-page-map-versus-ncx-pagelist/comment-page-1/#comment-1376</link>
		<dc:creator>Lindsey Thomas Martin</dc:creator>
		<pubDate>Thu, 26 Nov 2009 18:19:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.threepress.org/?p=790#comment-1376</guid>
		<description>You wrote: 
&#039;My personal opinion is that this sort of print-centrism is unnecessary for the vast majority of titles&#039;. 

For the most part, I agree with you on this. There is, however, a precedent in scholarly publishing for this sort of &#039;page mapping&#039;, when it was useful to link editions of classical authors to a standard edition so passages could be compared easily. The Stephanus pagination used in editions of Plato is an example. Had the editions been digital and thus easily searched, such an expedient would have been less necessary, though it is still convenient in discussion to have a short-hand way to refer to passages from a corpus.</description>
		<content:encoded><![CDATA[<p>You wrote:<br />
&#8216;My personal opinion is that this sort of print-centrism is unnecessary for the vast majority of titles&#8217;. </p>
<p>For the most part, I agree with you on this. There is, however, a precedent in scholarly publishing for this sort of &#8216;page mapping&#8217;, when it was useful to link editions of classical authors to a standard edition so passages could be compared easily. The Stephanus pagination used in editions of Plato is an example. Had the editions been digital and thus easily searched, such an expedient would have been less necessary, though it is still convenient in discussion to have a short-hand way to refer to passages from a corpus.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

