<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: InDesign Files and Kindle Formats</title>
	<atom:link href="http://waltshiel.com/2009/11/12/indesign-files-and-kindle-formats/feed/" rel="self" type="application/rss+xml" />
	<link>http://waltshiel.com/2009/11/12/indesign-files-and-kindle-formats/</link>
	<description>Micro-Publisher Walt Shiel&#039;s publishing-related commentary</description>
	<lastBuildDate>Fri, 10 Sep 2010 16:16:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Walt Shiel</title>
		<link>http://waltshiel.com/2009/11/12/indesign-files-and-kindle-formats/#comment-1435</link>
		<dc:creator>Walt Shiel</dc:creator>
		<pubDate>Fri, 05 Feb 2010 21:27:23 +0000</pubDate>
		<guid isPermaLink="false">http://waltshiel.com/?p=902#comment-1435</guid>
		<description>Actually, you do have that option. Try:
  File
    Cross-Media Export
      XHTML/Digital Editions...

I can, however, almost guarantee that you won&#039;t get a well-done ePub file from that process. You&#039;ll have to dig into the ePub file and massage some of the XHTML files contained in it.

I also recommend you read my &lt;a href=&quot;http://waltshiel.com/2009/11/24/creating-epub-documents-from-indesign/&quot; rel=&quot;nofollow&quot;&gt;Creating ePub Documents from InDesign&lt;/a&gt; and check out the links I provide there.</description>
		<content:encoded><![CDATA[<p>Actually, you do have that option. Try:<br />
  File<br />
    Cross-Media Export<br />
      XHTML/Digital Editions&#8230;</p>
<p>I can, however, almost guarantee that you won&#8217;t get a well-done ePub file from that process. You&#8217;ll have to dig into the ePub file and massage some of the XHTML files contained in it.</p>
<p>I also recommend you read my <a href="http://waltshiel.com/2009/11/24/creating-epub-documents-from-indesign/" rel="nofollow">Creating ePub Documents from InDesign</a> and check out the links I provide there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TaniaL</title>
		<link>http://waltshiel.com/2009/11/12/indesign-files-and-kindle-formats/#comment-1433</link>
		<dc:creator>TaniaL</dc:creator>
		<pubDate>Fri, 05 Feb 2010 19:07:53 +0000</pubDate>
		<guid isPermaLink="false">http://waltshiel.com/?p=902#comment-1433</guid>
		<description>Thank you so much for this page, it has been very helpful in my experimentation with epublishing. However, I seem to still have one major problem with InDesign export that I&#039;m hoping you might be able to help me with. (I apologize in advance for bothering you with this very fundamental question!) I thought it was a CS3/CS4 issue, however you stated above that you are still using CS3 which makes me hopeful. I do not have an option in my CS3 to export as .epub (file menu-&gt;export=pdf/eps/xml/svg/ind-exchage is all I have in my program)- how do you export as an epub file from indesign CS3?</description>
		<content:encoded><![CDATA[<p>Thank you so much for this page, it has been very helpful in my experimentation with epublishing. However, I seem to still have one major problem with InDesign export that I&#8217;m hoping you might be able to help me with. (I apologize in advance for bothering you with this very fundamental question!) I thought it was a CS3/CS4 issue, however you stated above that you are still using CS3 which makes me hopeful. I do not have an option in my CS3 to export as .epub (file menu-&gt;export=pdf/eps/xml/svg/ind-exchage is all I have in my program)- how do you export as an epub file from indesign CS3?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Walt Shiel</title>
		<link>http://waltshiel.com/2009/11/12/indesign-files-and-kindle-formats/#comment-1240</link>
		<dc:creator>Walt Shiel</dc:creator>
		<pubDate>Wed, 25 Nov 2009 19:58:45 +0000</pubDate>
		<guid isPermaLink="false">http://waltshiel.com/?p=902#comment-1240</guid>
		<description>When exporting from ID to ePub, you need to add the necessary metadata to the file first by selecting &quot;File Info...&quot; on the File menu. I suspect that not all ereaders will use that data, but that&#039;s where they will get it (Title, Author, etc.). 

As for those page numbers in the margin, if they match the page numbers in the ID document then you probably have a &quot;page-map.xml&quot; file in the OEBPS folder within the ePub file itself that maps those page numbers. However, some readers (I don&#039;t know for sure if that includes Sony) will generate a synthetic page map. I know Adobe Digital Editions does this. If you find that &quot;page-map.xml&quot; file in your ePub file, you could probably modify it by using empty name attributes (or maybe just deleting the list of page cross-refs), which should cause nothing to be placed in those locations. You can find out more about that file in the Adobe &lt;a href=&quot;http://www.adobe.com/devnet/digitalpublishing/epubs/EPUBBestPractices-1_0_3.epub&quot; target=&quot;_blank&quot; rel=&quot;nofollow&quot;&gt;ePub Best Practices Guide&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>When exporting from ID to ePub, you need to add the necessary metadata to the file first by selecting &#8220;File Info&#8230;&#8221; on the File menu. I suspect that not all ereaders will use that data, but that&#8217;s where they will get it (Title, Author, etc.). </p>
<p>As for those page numbers in the margin, if they match the page numbers in the ID document then you probably have a &#8220;page-map.xml&#8221; file in the OEBPS folder within the ePub file itself that maps those page numbers. However, some readers (I don&#8217;t know for sure if that includes Sony) will generate a synthetic page map. I know Adobe Digital Editions does this. If you find that &#8220;page-map.xml&#8221; file in your ePub file, you could probably modify it by using empty name attributes (or maybe just deleting the list of page cross-refs), which should cause nothing to be placed in those locations. You can find out more about that file in the Adobe <a href="http://www.adobe.com/devnet/digitalpublishing/epubs/EPUBBestPractices-1_0_3.epub" target="_blank" rel="nofollow">ePub Best Practices Guide</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SheriG</title>
		<link>http://waltshiel.com/2009/11/12/indesign-files-and-kindle-formats/#comment-1239</link>
		<dc:creator>SheriG</dc:creator>
		<pubDate>Wed, 25 Nov 2009 17:01:15 +0000</pubDate>
		<guid isPermaLink="false">http://waltshiel.com/?p=902#comment-1239</guid>
		<description>I am wondering if you have any tips about master page headers? I work for a small press and we produce our books using InDesign .indb files. I&#039;ve gotten the ePub generation down pretty well now, except for the headers. We include a header at the top of each page of the print-book version that has the name of the book and the page number (done on the master page). However, after we convert to ePub, the title of the book drops off but the page numbers show up in the ePub document as a &quot;floating&quot; number along the right side of the screen. I&#039;ve purchased eBooks for my Sony eReader and they manage to include a header with the book name at the top of each page, and no residual page number from the print version leftover, either.

Any tips you&#039;d care to share?

Thanks!</description>
		<content:encoded><![CDATA[<p>I am wondering if you have any tips about master page headers? I work for a small press and we produce our books using InDesign .indb files. I&#8217;ve gotten the ePub generation down pretty well now, except for the headers. We include a header at the top of each page of the print-book version that has the name of the book and the page number (done on the master page). However, after we convert to ePub, the title of the book drops off but the page numbers show up in the ePub document as a &#8220;floating&#8221; number along the right side of the screen. I&#8217;ve purchased eBooks for my Sony eReader and they manage to include a header with the book name at the top of each page, and no residual page number from the print version leftover, either.</p>
<p>Any tips you&#8217;d care to share?</p>
<p>Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Walt Shiel</title>
		<link>http://waltshiel.com/2009/11/12/indesign-files-and-kindle-formats/#comment-1227</link>
		<dc:creator>Walt Shiel</dc:creator>
		<pubDate>Thu, 19 Nov 2009 20:16:17 +0000</pubDate>
		<guid isPermaLink="false">http://waltshiel.com/?p=902#comment-1227</guid>
		<description>We&#039;ve found that, often, it is easier to produce a good Kindle format and then use that to convert to ePub. 

I&#039;m still toying with the idea of coding all our in-house book with XML to make ePub conversion easier (at least in theory). The biggest problem is cost of good tools for doing the XML coding. And, for maximum benefit, we need to update our InDesign from CS3 but now figure we&#039;ll wait for CS5 next year.

The comments on providing an MS Word document was primarily aimed at the self-publishers and small indie publishers with whom we work through our &lt;a href=&quot;http://fiverainbows.com&quot; target=&quot;_blank&quot; rel=&quot;nofollow&quot;&gt;Five Rainbows Services&lt;/a&gt; subsidiary.

Walt</description>
		<content:encoded><![CDATA[<p>We&#8217;ve found that, often, it is easier to produce a good Kindle format and then use that to convert to ePub. </p>
<p>I&#8217;m still toying with the idea of coding all our in-house book with XML to make ePub conversion easier (at least in theory). The biggest problem is cost of good tools for doing the XML coding. And, for maximum benefit, we need to update our InDesign from CS3 but now figure we&#8217;ll wait for CS5 next year.</p>
<p>The comments on providing an MS Word document was primarily aimed at the self-publishers and small indie publishers with whom we work through our <a href="http://fiverainbows.com" target="_blank" rel="nofollow">Five Rainbows Services</a> subsidiary.</p>
<p>Walt</p>
]]></content:encoded>
	</item>
</channel>
</rss>
