<?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: A Format For Online Fiction, Part 2</title>
	<atom:link href="http://www.novelr.com/2009/11/03/a-format-for-online-fiction-part-2/feed" rel="self" type="application/rss+xml" />
	<link>http://www.novelr.com/2009/11/03/a-format-for-online-fiction-part-2</link>
	<description>Hacking Publishing</description>
	<lastBuildDate>Sun, 29 Apr 2018 10:09:00 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=4.0.23</generator>
	<item>
		<title>By: Johny C.</title>
		<link>http://www.novelr.com/2009/11/03/a-format-for-online-fiction-part-2/comment-page-1#comment-7546</link>
		<dc:creator><![CDATA[Johny C.]]></dc:creator>
		<pubDate>Sat, 15 Oct 2011 22:13:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.novelr.com/?p=1226#comment-7546</guid>
		<description><![CDATA[Very nice post, I found it to be very interesting. I have bookmarked your page as I will show it to my friend.
You can also check out www.ecompareereaders.com for more information on all new ereaders of 2011.]]></description>
		<content:encoded><![CDATA[<p>Very nice post, I found it to be very interesting. I have bookmarked your page as I will show it to my friend.<br />
You can also check out <a href="http://www.ecompareereaders.com" rel="nofollow">http://www.ecompareereaders.com</a> for more information on all new ereaders of 2011.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MCM</title>
		<link>http://www.novelr.com/2009/11/03/a-format-for-online-fiction-part-2/comment-page-1#comment-4003</link>
		<dc:creator><![CDATA[MCM]]></dc:creator>
		<pubDate>Mon, 02 Nov 2009 20:29:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.novelr.com/?p=1226#comment-4003</guid>
		<description><![CDATA[ePub sucks like nobody&#039;s business, but the fundamental theory is good.  XML is good too, but it means you need to write custom interpreters, when we&#039;ve already got a bunch of lightweight rendering engines (WebKit, Gecko and Opera) already deployed on tons of devices.  All you need to do is make some simple HTML pages of your content with CSS in an included stylesheet, and you&#039;re good to go.  You embed a lot of &quot;invisible&quot; content in the package so it can be pulled if requested, but it&#039;s still fundamentally a standard ePub file.  Validates and everything.  The cheaper ePub readers ignore the fancy stuff, but anything web-based reads it all in.  ePub is already supported widely, so you&#039;re not introducing a new format into the mix.  It&#039;s sneaky, but it does the job :)]]></description>
		<content:encoded><![CDATA[<p>ePub sucks like nobody&#8217;s business, but the fundamental theory is good.  XML is good too, but it means you need to write custom interpreters, when we&#8217;ve already got a bunch of lightweight rendering engines (WebKit, Gecko and Opera) already deployed on tons of devices.  All you need to do is make some simple HTML pages of your content with CSS in an included stylesheet, and you&#8217;re good to go.  You embed a lot of &#8220;invisible&#8221; content in the package so it can be pulled if requested, but it&#8217;s still fundamentally a standard ePub file.  Validates and everything.  The cheaper ePub readers ignore the fancy stuff, but anything web-based reads it all in.  ePub is already supported widely, so you&#8217;re not introducing a new format into the mix.  It&#8217;s sneaky, but it does the job :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eli James</title>
		<link>http://www.novelr.com/2009/11/03/a-format-for-online-fiction-part-2/comment-page-1#comment-4002</link>
		<dc:creator><![CDATA[Eli James]]></dc:creator>
		<pubDate>Mon, 02 Nov 2009 20:19:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.novelr.com/?p=1226#comment-4002</guid>
		<description><![CDATA[I&#039;m surprised that ePub is that powerful, to be honest. I&#039;d have thought that if you want to build something that spans so many formats and mediums, XML would be a good choice. But I&#039;ll have to think about that - I must admit that I&#039;d completely forgotten about mobile devices and their importance to web fiction publishing.

Oh and thanks, MCM. For the compliment. =)]]></description>
		<content:encoded><![CDATA[<p>I&#8217;m surprised that ePub is that powerful, to be honest. I&#8217;d have thought that if you want to build something that spans so many formats and mediums, XML would be a good choice. But I&#8217;ll have to think about that &#8211; I must admit that I&#8217;d completely forgotten about mobile devices and their importance to web fiction publishing.</p>
<p>Oh and thanks, MCM. For the compliment. =)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MCM</title>
		<link>http://www.novelr.com/2009/11/03/a-format-for-online-fiction-part-2/comment-page-1#comment-4000</link>
		<dc:creator><![CDATA[MCM]]></dc:creator>
		<pubDate>Mon, 02 Nov 2009 20:00:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.novelr.com/?p=1226#comment-4000</guid>
		<description><![CDATA[Excellent, excellent post!  Not a huge surprise, but still.  It needs to be said.

One of the challenges of this format debate is portability.  If we remove interface from the equation (which I would argue it should be), you&#039;re left with a book — a presentation — which people will want to read on varying devices.  A common complaint during Typhoon was that it wasn&#039;t readable on mobile platforms.  The seamless conversion from one presentation technique to another should be a big part of the process.

My current theory is this: enhanced ePub files that are fully designed and formatted into whatever the author desires.  The reading software can be interchangeable, using whatever UI method you want.  Build the &quot;browse&quot; content into the book itself, so the packaging is complete.  I&#039;ve made this kind of thing recently, and it works perfectly.  Weaker ePub readers just do the text, but the advanced ones give the full effect.  And I have a few reader systems for websites that present the files seamlessly.

I&#039;m hoping to have a draft of this available in the next few weeks, and then everyone can see how it works.  I even have a handy Wordpress exporter plugin that will create such files for you almost instantly.  The software needs to be broken out from the content, but if we keep in mind the &quot;browse&quot; and &quot;read&quot; requirements, I think we&#039;ll be okay.]]></description>
		<content:encoded><![CDATA[<p>Excellent, excellent post!  Not a huge surprise, but still.  It needs to be said.</p>
<p>One of the challenges of this format debate is portability.  If we remove interface from the equation (which I would argue it should be), you&#8217;re left with a book — a presentation — which people will want to read on varying devices.  A common complaint during Typhoon was that it wasn&#8217;t readable on mobile platforms.  The seamless conversion from one presentation technique to another should be a big part of the process.</p>
<p>My current theory is this: enhanced ePub files that are fully designed and formatted into whatever the author desires.  The reading software can be interchangeable, using whatever UI method you want.  Build the &#8220;browse&#8221; content into the book itself, so the packaging is complete.  I&#8217;ve made this kind of thing recently, and it works perfectly.  Weaker ePub readers just do the text, but the advanced ones give the full effect.  And I have a few reader systems for websites that present the files seamlessly.</p>
<p>I&#8217;m hoping to have a draft of this available in the next few weeks, and then everyone can see how it works.  I even have a handy WordPress exporter plugin that will create such files for you almost instantly.  The software needs to be broken out from the content, but if we keep in mind the &#8220;browse&#8221; and &#8220;read&#8221; requirements, I think we&#8217;ll be okay.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
