<?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: The cost of bad writing</title>
	<atom:link href="http://www.badlanguage.net/the-cost-of-bad-writing/feed" rel="self" type="application/rss+xml" />
	<link>http://www.badlanguage.net/the-cost-of-bad-writing</link>
	<description>How to communicate</description>
	<pubDate>Wed, 20 Aug 2008 07:39:33 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Bad Language / How to budget for, plan and measure writing output</title>
		<link>http://www.badlanguage.net/the-cost-of-bad-writing#comment-435677</link>
		<dc:creator>Bad Language / How to budget for, plan and measure writing output</dc:creator>
		<pubDate>Tue, 15 Jul 2008 08:10:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.badlanguage.net/?p=59#comment-435677</guid>
		<description>[...] Agree a specification, a word count and a budget. See Better briefs for writers. In my experience, without a clear brief, proper research and a professional relationship on both sides, you&#8217;ll get bad copy. And bad copy costs big money. [...]</description>
		<content:encoded><![CDATA[<p>[...] Agree a specification, a word count and a budget. See Better briefs for writers. In my experience, without a clear brief, proper research and a professional relationship on both sides, you&#8217;ll get bad copy. And bad copy costs big money. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
