<?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: IDPF e-book standards news: &#8216;Adobe InDesign CS3 Generation of OCF/OPS Content&#8217;</title>
	<atom:link href="http://www.teleread.org/2007/04/28/idpf-e-book-standards-news-adobe-indesign-cs3-generation-of-ocfops-content/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.teleread.org/2007/04/28/idpf-e-book-standards-news-adobe-indesign-cs3-generation-of-ocfops-content/</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: Paul Norton</title>
		<link>http://www.teleread.org/2007/04/28/idpf-e-book-standards-news-adobe-indesign-cs3-generation-of-ocfops-content/comment-page-1/#comment-392101</link>
		<dc:creator>Paul Norton</dc:creator>
		<pubDate>Thu, 31 May 2007 01:36:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.org/blog/?p=6500#comment-392101</guid>
		<description>@ Robert Nagle: It means you can create reflowable ebooks that support an open standard using Adobe InDesign. :) If you look at Digital Editions you&#039;ll find it supports both PDFs and the reflowable epubs.

@ Preston DuBose: It really works best with narrative content... if the look of the spread is important, you&#039;ll want to keep using PDF as the output format. 

@ David Rotham: If you grab the 1.0.1 version of the plug-in you should find that the generated .epub files are very close to the IDPF spec... the 1.0 came a bit before the latest draft of the OPS spec, and therefore, had some issues.</description>
		<content:encoded><![CDATA[<p>@ Robert Nagle: It means you can create reflowable ebooks that support an open standard using Adobe InDesign. <img src='http://www.teleread.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  If you look at Digital Editions you&#8217;ll find it supports both PDFs and the reflowable epubs.</p>
<p>@ Preston DuBose: It really works best with narrative content&#8230; if the look of the spread is important, you&#8217;ll want to keep using PDF as the output format. </p>
<p>@ David Rotham: If you grab the 1.0.1 version of the plug-in you should find that the generated .epub files are very close to the IDPF spec&#8230; the 1.0 came a bit before the latest draft of the OPS spec, and therefore, had some issues.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Nagle</title>
		<link>http://www.teleread.org/2007/04/28/idpf-e-book-standards-news-adobe-indesign-cs3-generation-of-ocfops-content/comment-page-1/#comment-348869</link>
		<dc:creator>Robert Nagle</dc:creator>
		<pubDate>Sat, 28 Apr 2007 21:29:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.org/blog/?p=6500#comment-348869</guid>
		<description>You know, although one can rag on adobe products for various reasons, i find the capabilities promised by their tools to be both interesting and forward-looking. (investigating on the website, it seems they have a server-client package for cs3 as well--it&#039;s some attempt at an end-to-end solution). 

Commercial solutions involve some degree of vendor lockin/commitment.  I wouldn&#039;t mind that so much if you could have the ability to separate code from presentation (if  for example I could import docbook/whatever files and then let adobe handle the presentation layer). We&#039;re dealing (it seems) with two different kinds of workflows, and I confess I know too little about the Indesign workflow to comment more.</description>
		<content:encoded><![CDATA[<p>You know, although one can rag on adobe products for various reasons, i find the capabilities promised by their tools to be both interesting and forward-looking. (investigating on the website, it seems they have a server-client package for cs3 as well&#8211;it&#8217;s some attempt at an end-to-end solution). </p>
<p>Commercial solutions involve some degree of vendor lockin/commitment.  I wouldn&#8217;t mind that so much if you could have the ability to separate code from presentation (if  for example I could import docbook/whatever files and then let adobe handle the presentation layer). We&#8217;re dealing (it seems) with two different kinds of workflows, and I confess I know too little about the Indesign workflow to comment more.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Rothman</title>
		<link>http://www.teleread.org/2007/04/28/idpf-e-book-standards-news-adobe-indesign-cs3-generation-of-ocfops-content/comment-page-1/#comment-348816</link>
		<dc:creator>David Rothman</dc:creator>
		<pubDate>Sat, 28 Apr 2007 20:08:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.org/blog/?p=6500#comment-348816</guid>
		<description>This bears investigating, of course---with the big question being: How fully compatible will this be with the IDPF standards? Will Adobe-specific stuff clutter things up? I&#039;d hope that if need be, you could set up the InDesign so that the results were viewable on a wide variety of IDPF-compliant readers.

But conversions into Mobipocket and the rest? Ferget it. Hey, Adobe is still Adobe.</description>
		<content:encoded><![CDATA[<p>This bears investigating, of course&#8212;with the big question being: How fully compatible will this be with the IDPF standards? Will Adobe-specific stuff clutter things up? I&#8217;d hope that if need be, you could set up the InDesign so that the results were viewable on a wide variety of IDPF-compliant readers.</p>
<p>But conversions into Mobipocket and the rest? Ferget it. Hey, Adobe is still Adobe.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Preston DuBose</title>
		<link>http://www.teleread.org/2007/04/28/idpf-e-book-standards-news-adobe-indesign-cs3-generation-of-ocfops-content/comment-page-1/#comment-348798</link>
		<dc:creator>Preston DuBose</dc:creator>
		<pubDate>Sat, 28 Apr 2007 19:24:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.org/blog/?p=6500#comment-348798</guid>
		<description>I&#039;m with Robert. I&#039;m not entirely sure what this means. I&#039;m glad it can export to xhtml, but at first glance it seems to be limited to something readable by Adobe Digital Editions. While there may be benefits to doing that over PDF, AFAIK we&#039;re still limited to Adobe products. Or am I missing something here? As Robert asks, what about other formats like MobiPocket and others?

I have some InDesign CS1 files I&#039;d love to try this out on, just to see the results. My documents include illustrations and data tables, so I&#039;m very curious to gauge the output.</description>
		<content:encoded><![CDATA[<p>I&#8217;m with Robert. I&#8217;m not entirely sure what this means. I&#8217;m glad it can export to xhtml, but at first glance it seems to be limited to something readable by Adobe Digital Editions. While there may be benefits to doing that over PDF, AFAIK we&#8217;re still limited to Adobe products. Or am I missing something here? As Robert asks, what about other formats like MobiPocket and others?</p>
<p>I have some InDesign CS1 files I&#8217;d love to try this out on, just to see the results. My documents include illustrations and data tables, so I&#8217;m very curious to gauge the output.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Nagle</title>
		<link>http://www.teleread.org/2007/04/28/idpf-e-book-standards-news-adobe-indesign-cs3-generation-of-ocfops-content/comment-page-1/#comment-348793</link>
		<dc:creator>Robert Nagle</dc:creator>
		<pubDate>Sat, 28 Apr 2007 19:08:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.org/blog/?p=6500#comment-348793</guid>
		<description>This sounds interesting, but I really don&#039;t know what  it means. 

My question becomes: If I can export as a reflowable xhtml ebook, how easy would it be to produce a mobipocket file or a fb2 file?  And what (if anything) is lost by the process?</description>
		<content:encoded><![CDATA[<p>This sounds interesting, but I really don&#8217;t know what  it means. </p>
<p>My question becomes: If I can export as a reflowable xhtml ebook, how easy would it be to produce a mobipocket file or a fb2 file?  And what (if anything) is lost by the process?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
