<?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 for doingText</title>
	<atom:link href="http://blog.doingtext.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.doingtext.com</link>
	<description></description>
	<pubDate>Fri, 30 Jul 2010 11:09:39 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>Comment on Congratulations to Our Winners of the Celebrate-the-Launch-Contest by alex</title>
		<link>http://blog.doingtext.com/2009/04/congratulations-to-our-winners-of-the-celebrate-the-launch-contest/#comment-296</link>
		<dc:creator>alex</dc:creator>
		<pubDate>Wed, 29 Apr 2009 11:20:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.doingtext.com/?p=232#comment-296</guid>
		<description>Hi drikkes, just register for a free account and then send me an email with your username to support AT doingtext.com</description>
		<content:encoded><![CDATA[<p>Hi drikkes, just register for a free account and then send me an email with your username to support AT doingtext.com</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Congratulations to Our Winners of the Celebrate-the-Launch-Contest by Hendrik Spree</title>
		<link>http://blog.doingtext.com/2009/04/congratulations-to-our-winners-of-the-celebrate-the-launch-contest/#comment-293</link>
		<dc:creator>Hendrik Spree</dc:creator>
		<pubDate>Tue, 28 Apr 2009 17:46:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.doingtext.com/?p=232#comment-293</guid>
		<description>Yeah!

I don't have an account yet, so what should I do register for "free" or "medium"?

Thanks!
drikkes</description>
		<content:encoded><![CDATA[<p>Yeah!</p>
<p>I don&#8217;t have an account yet, so what should I do register for &#8220;free&#8221; or &#8220;medium&#8221;?</p>
<p>Thanks!<br />
drikkes</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The API is there. by Linkwertig: Spotify, doingText, Blockbuster, Wer-kennt-wen » netzwertig.com</title>
		<link>http://blog.doingtext.com/2009/04/the-api-is-there/#comment-277</link>
		<dc:creator>Linkwertig: Spotify, doingText, Blockbuster, Wer-kennt-wen » netzwertig.com</dc:creator>
		<pubDate>Thu, 09 Apr 2009 07:01:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.doingtext.com/?p=217#comment-277</guid>
		<description>[...] » The API is there. [...]</description>
		<content:encoded><![CDATA[<p>[...] » The API is there. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on On Writing: Proofreading Methods by katrin</title>
		<link>http://blog.doingtext.com/2009/02/on-writing-proofreading-methods/#comment-260</link>
		<dc:creator>katrin</dc:creator>
		<pubDate>Mon, 09 Mar 2009 08:06:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.doingtext.com/?p=189#comment-260</guid>
		<description>Tom, thanks very much for providing a those ideas. They are a great addition.</description>
		<content:encoded><![CDATA[<p>Tom, thanks very much for providing a those ideas. They are a great addition.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on On Writing: Proofreading Methods by Tom</title>
		<link>http://blog.doingtext.com/2009/02/on-writing-proofreading-methods/#comment-259</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Sun, 08 Mar 2009 14:20:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.doingtext.com/?p=189#comment-259</guid>
		<description>Great advice. I'd also add a couple more tips:
* Don't just print out your text before you proofread. Also, change the font and the font size. I find courier can be a great font for proofreading and for spotting those little errors that always get left in there somewhere. Changing the font size means that words are in different places, tricking the lazy eye. This helps you spot errors like double spaces too.
* Start making a list of the mistakes that you make regularly. Depending on what field you are in, this could be, say, writing millions when you mean billions. Or using American English Z's when you want British English S's. 
* Best advice? Write clean copy in the first place. It can save you a bunch of time!</description>
		<content:encoded><![CDATA[<p>Great advice. I&#8217;d also add a couple more tips:<br />
* Don&#8217;t just print out your text before you proofread. Also, change the font and the font size. I find courier can be a great font for proofreading and for spotting those little errors that always get left in there somewhere. Changing the font size means that words are in different places, tricking the lazy eye. This helps you spot errors like double spaces too.<br />
* Start making a list of the mistakes that you make regularly. Depending on what field you are in, this could be, say, writing millions when you mean billions. Or using American English Z&#8217;s when you want British English S&#8217;s.<br />
* Best advice? Write clean copy in the first place. It can save you a bunch of time!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Embedding texts to your website by How should I handle this like a grown up? &#124; Easy Magic Words</title>
		<link>http://blog.doingtext.com/2009/02/embedding-texts-to-your-website/#comment-252</link>
		<dc:creator>How should I handle this like a grown up? &#124; Easy Magic Words</dc:creator>
		<pubDate>Fri, 13 Feb 2009 03:56:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.doingtext.com/?p=192#comment-252</guid>
		<description>[...] Embedding texts to your website &#124; doingText [...]</description>
		<content:encoded><![CDATA[<p>[...] Embedding texts to your website | doingText [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Wanted: Your Top Reasons for Using doingText. by The Checklist</title>
		<link>http://blog.doingtext.com/2008/12/wanted-your-top-reasons-for-using-doingtext/#comment-251</link>
		<dc:creator>The Checklist</dc:creator>
		<pubDate>Thu, 05 Feb 2009 09:25:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.doingtext.com/?p=153#comment-251</guid>
		<description>&lt;strong&gt;DoingText. Elaborare testi online...&lt;/strong&gt;

Nessuno mi paga per scrivere sui servizi che presento su queste pagine. Li presento perché li ritengo utili per il nostro lavoro o la nostra vita in rete e io li uso regolarmente. In genere sono gratuiti o mettono a disposizione almeno una parte delle...</description>
		<content:encoded><![CDATA[<p><strong>DoingText. Elaborare testi online&#8230;</strong></p>
<p>Nessuno mi paga per scrivere sui servizi che presento su queste pagine. Li presento perché li ritengo utili per il nostro lavoro o la nostra vita in rete e io li uso regolarmente. In genere sono gratuiti o mettono a disposizione almeno una parte delle&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Deleting comments, auto-resizing of images, subscribing to RSS and login failure notifications. by alex</title>
		<link>http://blog.doingtext.com/2008/12/deleting-comments-auto-resizing-of-images-subscribing-to-rss-and-login-failure-notifications/#comment-215</link>
		<dc:creator>alex</dc:creator>
		<pubDate>Sun, 04 Jan 2009 18:49:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.doingtext.com/?p=130#comment-215</guid>
		<description>i actually agree. this whole text formatting thing is something that we created really quickly in order to get doingtext out, but that doesn't mean it's going to stay like this. stay tuned.</description>
		<content:encoded><![CDATA[<p>i actually agree. this whole text formatting thing is something that we created really quickly in order to get doingtext out, but that doesn&#8217;t mean it&#8217;s going to stay like this. stay tuned.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Deleting comments, auto-resizing of images, subscribing to RSS and login failure notifications. by eno</title>
		<link>http://blog.doingtext.com/2008/12/deleting-comments-auto-resizing-of-images-subscribing-to-rss-and-login-failure-notifications/#comment-214</link>
		<dc:creator>eno</dc:creator>
		<pubDate>Sun, 04 Jan 2009 18:24:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.doingtext.com/?p=130#comment-214</guid>
		<description>"First, add .textile to the discussion title up in the header. For example “Films of the Week.textile”" ? Sorry guys, that is just not good. Why would you want to put the text encoding - after all it comes down to it? - into the text name? Can I not just start a text with a name "This is a text that's name ends in .textile"? This is just awkward, and the only thing it saves you is one little control in your user interface.

I would be glad to get rid of all file extensions on my desktop machines. Having to use something on the web is just soooo... 80iesh.</description>
		<content:encoded><![CDATA[<p>&#8220;First, add .textile to the discussion title up in the header. For example “Films of the Week.textile”&#8221; ? Sorry guys, that is just not good. Why would you want to put the text encoding - after all it comes down to it? - into the text name? Can I not just start a text with a name &#8220;This is a text that&#8217;s name ends in .textile&#8221;? This is just awkward, and the only thing it saves you is one little control in your user interface.</p>
<p>I would be glad to get rid of all file extensions on my desktop machines. Having to use something on the web is just soooo&#8230; 80iesh.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Stay Up-to-date with Email Notifications by Improved Handling, Writing and Performance &#124; doingText</title>
		<link>http://blog.doingtext.com/2008/12/stay-up-to-date-with-email-notifications/#comment-205</link>
		<dc:creator>Improved Handling, Writing and Performance &#124; doingText</dc:creator>
		<pubDate>Fri, 02 Jan 2009 14:02:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.doingtext.com/?p=157#comment-205</guid>
		<description>[...] &#171; Stay Up-to-date with Email Notifications [...]</description>
		<content:encoded><![CDATA[<p>[...] &laquo; Stay Up-to-date with Email Notifications [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
