<?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"
	>
<channel>
	<title>Comments on: Yet another sign that the .epub standard is here to stay: An .epub blog</title>
	<atom:link href="http://www.teleread.org/blog/2008/04/12/yet-another-sign-that-the-epub-standard-is-here-to-stay-an-epub-blog/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.teleread.org/blog/2008/04/12/yet-another-sign-that-the-epub-standard-is-here-to-stay-an-epub-blog/</link>
	<description>News &#38; views on e-books, libraries, publishing and related topics</description>
	<pubDate>Mon, 06 Oct 2008 19:21:56 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Mike Cook</title>
		<link>http://www.teleread.org/blog/2008/04/12/yet-another-sign-that-the-epub-standard-is-here-to-stay-an-epub-blog/#comment-761887</link>
		<dc:creator>Mike Cook</dc:creator>
		<pubDate>Sun, 13 Apr 2008 10:21:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.org/blog/2008/04/12/yet-another-sign-that-the-epub-standard-is-here-to-stay-an-epub-blog/#comment-761887</guid>
		<description>Hi David, no connections with the IDPF here I'm afraid.

Like many people reading the TeleRead blog, I've been following the development of the epub format and I'm very keen for it to become the standard book format. However, I noticed there was a serious lack of community discussion - except for here of course - where are all the blogs, forums and mailing lists? Thus the reason I started this new blog.

Over the last year and a half I've been developing tools to convert Project Gutenberg Plain-Vanilla TXT files into TEI documents. Now once I've learned how to use XSL I want to transform these to the .epub format, along with PDF and some others. Starting a blog seemed a great way to pass along what I learn during this process.

@Joseph: The mystery was not intentional, I just didn't think this blog would surface for a good few months yet! I've now created a Contact page and opened the comments so you don't need to register.

Yes, at the moment the information is quite basic - I only registered the domain a couple of weeks ago! - but I'm hoping to expand on this over the coming months.

@everyone: The site is very new so please bear with me while I get it up to speed - heck, I don't even have a personalised template yet!

Blogs are only as good as the content they provide, I will do my best to make it so but if anyone has good information, guides, links or other ideas please don't hesitate to contact me.</description>
		<content:encoded><![CDATA[<p>Hi David, no connections with the IDPF here I&#8217;m afraid.</p>
<p>Like many people reading the TeleRead blog, I&#8217;ve been following the development of the epub format and I&#8217;m very keen for it to become the standard book format. However, I noticed there was a serious lack of community discussion - except for here of course - where are all the blogs, forums and mailing lists? Thus the reason I started this new blog.</p>
<p>Over the last year and a half I&#8217;ve been developing tools to convert Project Gutenberg Plain-Vanilla TXT files into TEI documents. Now once I&#8217;ve learned how to use XSL I want to transform these to the .epub format, along with PDF and some others. Starting a blog seemed a great way to pass along what I learn during this process.</p>
<p>@Joseph: The mystery was not intentional, I just didn&#8217;t think this blog would surface for a good few months yet! I&#8217;ve now created a Contact page and opened the comments so you don&#8217;t need to register.</p>
<p>Yes, at the moment the information is quite basic - I only registered the domain a couple of weeks ago! - but I&#8217;m hoping to expand on this over the coming months.</p>
<p>@everyone: The site is very new so please bear with me while I get it up to speed - heck, I don&#8217;t even have a personalised template yet!</p>
<p>Blogs are only as good as the content they provide, I will do my best to make it so but if anyone has good information, guides, links or other ideas please don&#8217;t hesitate to contact me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joseph Gray</title>
		<link>http://www.teleread.org/blog/2008/04/12/yet-another-sign-that-the-epub-standard-is-here-to-stay-an-epub-blog/#comment-761577</link>
		<dc:creator>Joseph Gray</dc:creator>
		<pubDate>Sat, 12 Apr 2008 23:18:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.teleread.org/blog/2008/04/12/yet-another-sign-that-the-epub-standard-is-here-to-stay-an-epub-blog/#comment-761577</guid>
		<description>I was just visiting that blog. It has some good, basic information. I wanted to contact the mystery blog author about some additional information, but there is no email address. The only other method of contact that I can see is to comment on a blog entry (not really what I had in mind), but this requires that I create a log-in account. Now, I already have dozens of log-ins that I have to keep track of for various web sites. I really don't want to create yet another, just to leave an occasional comment on some blog. Perhaps the mystery blogger will post an email address, or at least use a commenting method like the one used here at TeleRead.</description>
		<content:encoded><![CDATA[<p>I was just visiting that blog. It has some good, basic information. I wanted to contact the mystery blog author about some additional information, but there is no email address. The only other method of contact that I can see is to comment on a blog entry (not really what I had in mind), but this requires that I create a log-in account. Now, I already have dozens of log-ins that I have to keep track of for various web sites. I really don&#8217;t want to create yet another, just to leave an occasional comment on some blog. Perhaps the mystery blogger will post an email address, or at least use a commenting method like the one used here at TeleRead.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
