<?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: Chocolate Covered or Chocolate-Covered?</title>
	<atom:link href="http://www.dailywritingtips.com/chocolate-covered-or-chocolate-covered/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dailywritingtips.com/chocolate-covered-or-chocolate-covered/</link>
	<description></description>
	<lastBuildDate>Sat, 21 Nov 2009 02:00:10 -0600</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Sarah Turner</title>
		<link>http://www.dailywritingtips.com/chocolate-covered-or-chocolate-covered/comment-page-1/#comment-113285</link>
		<dc:creator>Sarah Turner</dc:creator>
		<pubDate>Thu, 23 Apr 2009 14:46:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailywritingtips.com/?p=1997#comment-113285</guid>
		<description>Email is more often than not written without the hyphen. At least in the UK. Although The Times still uses e-mail. Other electronic things haven&#039;t quite made the jump yet: e-newslettters or eNewsletters, e-shots, e-book or eBook. But I think in time they will. 

The Web and The Internet and now often seen without their caps: web and internet. And Web site is now only one word: website. It&#039;s progress I guess!</description>
		<content:encoded><![CDATA[<p>Email is more often than not written without the hyphen. At least in the UK. Although The Times still uses e-mail. Other electronic things haven&#8217;t quite made the jump yet: e-newslettters or eNewsletters, e-shots, e-book or eBook. But I think in time they will. </p>
<p>The Web and The Internet and now often seen without their caps: web and internet. And Web site is now only one word: website. It&#8217;s progress I guess!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mand</title>
		<link>http://www.dailywritingtips.com/chocolate-covered-or-chocolate-covered/comment-page-1/#comment-111803</link>
		<dc:creator>mand</dc:creator>
		<pubDate>Sun, 19 Apr 2009 15:09:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailywritingtips.com/?p=1997#comment-111803</guid>
		<description>@24. Miriam - Funny, i do write &lt;i&gt;tshirt&lt;/i&gt;!

@22. Gab - I think i agree with you overall. Of course &lt;i&gt;bumblebee&lt;/i&gt; has been around longer even than &lt;i&gt;mother-in-law&lt;/i&gt;, at least i&#039;d guess so.

The point about pronunciation of &lt;i&gt;e-book&lt;/i&gt;, with two stressed syllables, hadn&#039;t occurred to me and is a good one.   80)

I&#039;m sure this is an &#039;argument&#039; (of the least agressive kind) that no one will win.   ;0)</description>
		<content:encoded><![CDATA[<p>@24. Miriam &#8211; Funny, i do write <i>tshirt</i>!</p>
<p>@22. Gab &#8211; I think i agree with you overall. Of course <i>bumblebee</i> has been around longer even than <i>mother-in-law</i>, at least i&#8217;d guess so.</p>
<p>The point about pronunciation of <i>e-book</i>, with two stressed syllables, hadn&#8217;t occurred to me and is a good one.   80)</p>
<p>I&#8217;m sure this is an &#8216;argument&#8217; (of the least agressive kind) that no one will win.   ;0)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Miriam</title>
		<link>http://www.dailywritingtips.com/chocolate-covered-or-chocolate-covered/comment-page-1/#comment-111018</link>
		<dc:creator>Miriam</dc:creator>
		<pubDate>Fri, 17 Apr 2009 15:45:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailywritingtips.com/?p=1997#comment-111018</guid>
		<description>We write e-mail because that&#039;s how it&#039;s pronounced! We wouldn&#039;t write bmovie or tshirt.</description>
		<content:encoded><![CDATA[<p>We write e-mail because that&#8217;s how it&#8217;s pronounced! We wouldn&#8217;t write bmovie or tshirt.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PreciseEdit</title>
		<link>http://www.dailywritingtips.com/chocolate-covered-or-chocolate-covered/comment-page-1/#comment-111017</link>
		<dc:creator>PreciseEdit</dc:creator>
		<pubDate>Fri, 17 Apr 2009 15:43:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailywritingtips.com/?p=1997#comment-111017</guid>
		<description>Interesting. The double hyphen I typed was formatted as a dash. In any case, both occurrences should be en dashes.</description>
		<content:encoded><![CDATA[<p>Interesting. The double hyphen I typed was formatted as a dash. In any case, both occurrences should be en dashes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gab</title>
		<link>http://www.dailywritingtips.com/chocolate-covered-or-chocolate-covered/comment-page-1/#comment-110387</link>
		<dc:creator>Gab</dc:creator>
		<pubDate>Thu, 16 Apr 2009 03:54:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailywritingtips.com/?p=1997#comment-110387</guid>
		<description>My take on where to put the hyphens is that you generally need them when you&#039;re making up a new expression, but that it makes sense to take a more descriptive view when you&#039;re using an established expression, which means taking into account that some of these tend to be used with hyphens, some without and some either way!

An expression might be more established because it&#039;s an official term like &quot;mother-in-law&quot;, or because the expression created really derives a new noun rather than describes one referent of the noun . That&#039;s a clunky way to express it, forgive me, but what I mean is that &quot;bumblebee&quot; denotes a creature within a particular subclass of the category bees, whereas &quot;buzzing bee&quot; describes a creature from the category of bees that happens to be buzzing, it doesn&#039;t create a subclass.

I don&#039;t see any point in resisting this kind of language change - we wouldn&#039;t bother trying to separate expressions like &quot;farewell&quot; or &quot;welcome&quot;, so why try to re-insert hyphens when newer expressions become so common that we no longer need the hyphen to explain what the nouns are doing in that position in a sentence?

People have mentioned e-mail/email and e-book/ebook. Firstly, email has been around longer than e-books have, so perhaps people are more comfortable with &quot;email&quot; becoming a word in its own right by now, rather than a contraction. Secondly, the phonetics/phonology of &quot;email&quot; lends itself better to treating this as one word, whereas &quot;e-book&quot; tends to be pronounced with two stressed syllables, keeping them separate, so it seems less likely that the hyphen will be lost in this case.

My point is that it doesn&#039;t make sense to stick fanatically to one set of rules when the changes happen on a case-by-case basis, depending on all sorts of things about the expression involved. In the examples above, I&#039;m suggesting that semantic (bumblebee), contextual/usage (mother-in-law) and phonological factors (email/e-book), can all be important, but not necessarily for the same expressions.</description>
		<content:encoded><![CDATA[<p>My take on where to put the hyphens is that you generally need them when you&#8217;re making up a new expression, but that it makes sense to take a more descriptive view when you&#8217;re using an established expression, which means taking into account that some of these tend to be used with hyphens, some without and some either way!</p>
<p>An expression might be more established because it&#8217;s an official term like &#8220;mother-in-law&#8221;, or because the expression created really derives a new noun rather than describes one referent of the noun . That&#8217;s a clunky way to express it, forgive me, but what I mean is that &#8220;bumblebee&#8221; denotes a creature within a particular subclass of the category bees, whereas &#8220;buzzing bee&#8221; describes a creature from the category of bees that happens to be buzzing, it doesn&#8217;t create a subclass.</p>
<p>I don&#8217;t see any point in resisting this kind of language change &#8211; we wouldn&#8217;t bother trying to separate expressions like &#8220;farewell&#8221; or &#8220;welcome&#8221;, so why try to re-insert hyphens when newer expressions become so common that we no longer need the hyphen to explain what the nouns are doing in that position in a sentence?</p>
<p>People have mentioned e-mail/email and e-book/ebook. Firstly, email has been around longer than e-books have, so perhaps people are more comfortable with &#8220;email&#8221; becoming a word in its own right by now, rather than a contraction. Secondly, the phonetics/phonology of &#8220;email&#8221; lends itself better to treating this as one word, whereas &#8220;e-book&#8221; tends to be pronounced with two stressed syllables, keeping them separate, so it seems less likely that the hyphen will be lost in this case.</p>
<p>My point is that it doesn&#8217;t make sense to stick fanatically to one set of rules when the changes happen on a case-by-case basis, depending on all sorts of things about the expression involved. In the examples above, I&#8217;m suggesting that semantic (bumblebee), contextual/usage (mother-in-law) and phonological factors (email/e-book), can all be important, but not necessarily for the same expressions.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
