<?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: On Editing: Style</title>
	<atom:link href="http://www.kimwerker.com/2008/07/13/on-editing-style/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.kimwerker.com/2008/07/13/on-editing-style/</link>
	<description>Think. Create. Write.</description>
	<lastBuildDate>Fri, 27 Jan 2012 20:36:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Amie</title>
		<link>http://www.kimwerker.com/2008/07/13/on-editing-style/comment-page-1/#comment-3542</link>
		<dc:creator>Amie</dc:creator>
		<pubDate>Fri, 25 Jul 2008 01:56:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.kimwerker.com/?p=184#comment-3542</guid>
		<description>To confuse things more for you (ha!), in the fine art of teaching Art, we only refer to it as free-form, as in, &quot;Picasso painted with organic, free-form shapes.&quot; So when I see it any other way, I just want to break out a pencil and start throwing in hyphens all over the place.</description>
		<content:encoded><![CDATA[<p>To confuse things more for you (ha!), in the fine art of teaching Art, we only refer to it as free-form, as in, &#8220;Picasso painted with organic, free-form shapes.&#8221; So when I see it any other way, I just want to break out a pencil and start throwing in hyphens all over the place.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Amie</title>
		<link>http://www.kimwerker.com/2008/07/13/on-editing-style/comment-page-1/#comment-7513</link>
		<dc:creator>Amie</dc:creator>
		<pubDate>Fri, 25 Jul 2008 01:56:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.kimwerker.com/?p=184#comment-7513</guid>
		<description>To confuse things more for you (ha!), in the fine art of teaching Art, we only refer to it as free-form, as in, &quot;Picasso painted with organic, free-form shapes.&quot; So when I see it any other way, I just want to break out a pencil and start throwing in hyphens all over the place.</description>
		<content:encoded><![CDATA[<p>To confuse things more for you (ha!), in the fine art of teaching Art, we only refer to it as free-form, as in, &#8220;Picasso painted with organic, free-form shapes.&#8221; So when I see it any other way, I just want to break out a pencil and start throwing in hyphens all over the place.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kim</title>
		<link>http://www.kimwerker.com/2008/07/13/on-editing-style/comment-page-1/#comment-3489</link>
		<dc:creator>Kim</dc:creator>
		<pubDate>Wed, 16 Jul 2008 18:22:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.kimwerker.com/?p=184#comment-3489</guid>
		<description>@&lt;a href=&quot;#comment-3481&quot; rel=&quot;nofollow&quot;&gt;Nina Piper&lt;/a&gt;: In blogging and writing email, I find I nest parentheticals oddly frequently.
@&lt;a href=&quot;#comment-3488&quot; rel=&quot;nofollow&quot;&gt;EL&lt;/a&gt;: As soon as we moved to Canada, I started automatically spelling like a Canadian. One more thing that makes the man think my being American was an accident of birth. Also, I find it hard to filter out Canadian spelling in my work for the magazine.
Also, @&lt;a href=&quot;#comment-3476&quot; rel=&quot;nofollow&quot;&gt;Kim&lt;/a&gt;: Interweave follows the Chicago Manual of Style, which supports use of the serial comma (so the man pointed out to me). As I said, I don&#039;t argue this one when it comes to the magazine. In my personal work, though, I use the serial comma as infrequently as possible.</description>
		<content:encoded><![CDATA[<p>@<a href="#comment-3481" rel="nofollow">Nina Piper</a>: In blogging and writing email, I find I nest parentheticals oddly frequently.<br />
@<a href="#comment-3488" rel="nofollow">EL</a>: As soon as we moved to Canada, I started automatically spelling like a Canadian. One more thing that makes the man think my being American was an accident of birth. Also, I find it hard to filter out Canadian spelling in my work for the magazine.<br />
Also, @<a href="#comment-3476" rel="nofollow">Kim</a>: Interweave follows the Chicago Manual of Style, which supports use of the serial comma (so the man pointed out to me). As I said, I don&#8217;t argue this one when it comes to the magazine. In my personal work, though, I use the serial comma as infrequently as possible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kim Werker</title>
		<link>http://www.kimwerker.com/2008/07/13/on-editing-style/comment-page-1/#comment-7510</link>
		<dc:creator>Kim Werker</dc:creator>
		<pubDate>Wed, 16 Jul 2008 18:22:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.kimwerker.com/?p=184#comment-7510</guid>
		<description>@&lt;a href=&quot;#comment-3481&quot; rel=&quot;nofollow&quot;&gt;Nina Piper&lt;/a&gt;: In blogging and writing email, I find I nest parentheticals oddly frequently.
@&lt;a href=&quot;#comment-3488&quot; rel=&quot;nofollow&quot;&gt;EL&lt;/a&gt;: As soon as we moved to Canada, I started automatically spelling like a Canadian. One more thing that makes the man think my being American was an accident of birth. Also, I find it hard to filter out Canadian spelling in my work for the magazine.
Also, @&lt;a href=&quot;#comment-3476&quot; rel=&quot;nofollow&quot;&gt;Kim&lt;/a&gt;: Interweave follows the Chicago Manual of Style, which supports use of the serial comma (so the man pointed out to me). As I said, I don&#039;t argue this one when it comes to the magazine. In my personal work, though, I use the serial comma as infrequently as possible.</description>
		<content:encoded><![CDATA[<p>@<a href="#comment-3481" rel="nofollow">Nina Piper</a>: In blogging and writing email, I find I nest parentheticals oddly frequently.<br />
@<a href="#comment-3488" rel="nofollow">EL</a>: As soon as we moved to Canada, I started automatically spelling like a Canadian. One more thing that makes the man think my being American was an accident of birth. Also, I find it hard to filter out Canadian spelling in my work for the magazine.<br />
Also, @<a href="#comment-3476" rel="nofollow">Kim</a>: Interweave follows the Chicago Manual of Style, which supports use of the serial comma (so the man pointed out to me). As I said, I don&#8217;t argue this one when it comes to the magazine. In my personal work, though, I use the serial comma as infrequently as possible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: EL</title>
		<link>http://www.kimwerker.com/2008/07/13/on-editing-style/comment-page-1/#comment-3488</link>
		<dc:creator>EL</dc:creator>
		<pubDate>Wed, 16 Jul 2008 17:43:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.kimwerker.com/?p=184#comment-3488</guid>
		<description>Yes, this is satisfying! Thank you for discussing it. Good copyediting makes the magazine look professional. Punctuation, used accurately, helps express the tone and even the body language. That&#039;s strange about &quot;ravel&quot;; the first definition in my dictionary says &quot;to separate or undo the texture of: UNRAVEL.&quot; Suggesting that &quot;unravel&quot; is preferable. ??  P.S. How did you adjust to Canadian (British) spelling?  ;-)</description>
		<content:encoded><![CDATA[<p>Yes, this is satisfying! Thank you for discussing it. Good copyediting makes the magazine look professional. Punctuation, used accurately, helps express the tone and even the body language. That&#8217;s strange about &#8220;ravel&#8221;; the first definition in my dictionary says &#8220;to separate or undo the texture of: UNRAVEL.&#8221; Suggesting that &#8220;unravel&#8221; is preferable. ??  P.S. How did you adjust to Canadian (British) spelling?  ;-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: EL</title>
		<link>http://www.kimwerker.com/2008/07/13/on-editing-style/comment-page-1/#comment-7511</link>
		<dc:creator>EL</dc:creator>
		<pubDate>Wed, 16 Jul 2008 17:43:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.kimwerker.com/?p=184#comment-7511</guid>
		<description>Yes, this is satisfying! Thank you for discussing it. Good copyediting makes the magazine look professional. Punctuation, used accurately, helps express the tone and even the body language. That&#039;s strange about &quot;ravel&quot;; the first definition in my dictionary says &quot;to separate or undo the texture of: UNRAVEL.&quot; Suggesting that &quot;unravel&quot; is preferable. ??  P.S. How did you adjust to Canadian (British) spelling?  ;-)</description>
		<content:encoded><![CDATA[<p>Yes, this is satisfying! Thank you for discussing it. Good copyediting makes the magazine look professional. Punctuation, used accurately, helps express the tone and even the body language. That&#8217;s strange about &#8220;ravel&#8221;; the first definition in my dictionary says &#8220;to separate or undo the texture of: UNRAVEL.&#8221; Suggesting that &#8220;unravel&#8221; is preferable. ??  P.S. How did you adjust to Canadian (British) spelling?  ;-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nina Piper</title>
		<link>http://www.kimwerker.com/2008/07/13/on-editing-style/comment-page-1/#comment-3481</link>
		<dc:creator>Nina Piper</dc:creator>
		<pubDate>Mon, 14 Jul 2008 20:05:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.kimwerker.com/?p=184#comment-3481</guid>
		<description>Commas are overused, but as you said, it&#039;s nice to have an indication that the reader should pause. I&#039;m also not a big fan of parenthetical statements, although obviously they&#039;re not as offensive in blogs and other personal writing created in a write-as-you-think style. I think freeform works best as one word, because it is a legitimate word. The hyphen extends the word by one character, but doesn&#039;t add any value to the sentence :)</description>
		<content:encoded><![CDATA[<p>Commas are overused, but as you said, it&#8217;s nice to have an indication that the reader should pause. I&#8217;m also not a big fan of parenthetical statements, although obviously they&#8217;re not as offensive in blogs and other personal writing created in a write-as-you-think style. I think freeform works best as one word, because it is a legitimate word. The hyphen extends the word by one character, but doesn&#8217;t add any value to the sentence :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nina Piper</title>
		<link>http://www.kimwerker.com/2008/07/13/on-editing-style/comment-page-1/#comment-7516</link>
		<dc:creator>Nina Piper</dc:creator>
		<pubDate>Mon, 14 Jul 2008 20:05:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.kimwerker.com/?p=184#comment-7516</guid>
		<description>Commas are overused, but as you said, it&#039;s nice to have an indication that the reader should pause. I&#039;m also not a big fan of parenthetical statements, although obviously they&#039;re not as offensive in blogs and other personal writing created in a write-as-you-think style. I think freeform works best as one word, because it is a legitimate word. The hyphen extends the word by one character, but doesn&#039;t add any value to the sentence :)</description>
		<content:encoded><![CDATA[<p>Commas are overused, but as you said, it&#8217;s nice to have an indication that the reader should pause. I&#8217;m also not a big fan of parenthetical statements, although obviously they&#8217;re not as offensive in blogs and other personal writing created in a write-as-you-think style. I think freeform works best as one word, because it is a legitimate word. The hyphen extends the word by one character, but doesn&#8217;t add any value to the sentence :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kim</title>
		<link>http://www.kimwerker.com/2008/07/13/on-editing-style/comment-page-1/#comment-3476</link>
		<dc:creator>Kim</dc:creator>
		<pubDate>Mon, 14 Jul 2008 15:31:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.kimwerker.com/?p=184#comment-3476</guid>
		<description>@&lt;a href=&quot;#comment-3475&quot; rel=&quot;nofollow&quot;&gt;Michelle&lt;/a&gt;: I knew &lt;a href=&quot;http://en.wikipedia.org/wiki/Serial_comma&quot; target=&quot;_blank&quot; title=&quot;serial comma&quot; rel=&quot;nofollow&quot;&gt;it&lt;/a&gt; would come up! I almost mentioned it in the post. What&#039;s your take on it?
At this moment I&#039;m not a fan of the serial comma, and my reasons are a preference for minimalism and a personal challenge. If the context indicates a list, the serial comma is pretty much just redundant decoration and should be nixed. If the context is a bit more vague or if the contents of the list require further indication of distinction or disambiguation, then I&#039;m all for using it. Also, a comma in any place is important for indicating &lt;a href=&quot;http://en.wikipedia.org/wiki/Prosody_(linguistics)&quot; target=&quot;_blank&quot; rel=&quot;nofollow&quot;&gt;prosody&lt;/a&gt; (such a good word; one I&#039;d forgotten about before skimming the article I linked to above). So if the pacing of a list needs a pause, give it a comma. My personal challenge is simply to try to use fewer commas. I realized a couple of years ago that I was using loads of commas, and think I&#039;ll improve my overall skill with language if I can manage to stop relying on them so much.
So, in sum: Not a fan of the serial comma unless it&#039;s there for good reason.
(I don&#039;t actually know Interweave&#039;s stance on the serial comma. It&#039;s not something I&#039;d push my chair back for.)</description>
		<content:encoded><![CDATA[<p>@<a href="#comment-3475" rel="nofollow">Michelle</a>: I knew <a href="http://en.wikipedia.org/wiki/Serial_comma" target="_blank" title="serial comma" rel="nofollow">it</a> would come up! I almost mentioned it in the post. What&#8217;s your take on it?<br />
At this moment I&#8217;m not a fan of the serial comma, and my reasons are a preference for minimalism and a personal challenge. If the context indicates a list, the serial comma is pretty much just redundant decoration and should be nixed. If the context is a bit more vague or if the contents of the list require further indication of distinction or disambiguation, then I&#8217;m all for using it. Also, a comma in any place is important for indicating <a href="http://en.wikipedia.org/wiki/Prosody_(linguistics)" target="_blank" rel="nofollow">prosody</a> (such a good word; one I&#8217;d forgotten about before skimming the article I linked to above). So if the pacing of a list needs a pause, give it a comma. My personal challenge is simply to try to use fewer commas. I realized a couple of years ago that I was using loads of commas, and think I&#8217;ll improve my overall skill with language if I can manage to stop relying on them so much.<br />
So, in sum: Not a fan of the serial comma unless it&#8217;s there for good reason.<br />
(I don&#8217;t actually know Interweave&#8217;s stance on the serial comma. It&#8217;s not something I&#8217;d push my chair back for.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kim Werker</title>
		<link>http://www.kimwerker.com/2008/07/13/on-editing-style/comment-page-1/#comment-7512</link>
		<dc:creator>Kim Werker</dc:creator>
		<pubDate>Mon, 14 Jul 2008 15:31:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.kimwerker.com/?p=184#comment-7512</guid>
		<description>@&lt;a href=&quot;#comment-3475&quot; rel=&quot;nofollow&quot;&gt;Michelle&lt;/a&gt;: I knew &lt;a href=&quot;http://en.wikipedia.org/wiki/Serial_comma&quot; title=&quot;serial comma&quot; rel=&quot;nofollow&quot;&gt;it&lt;/a&gt; would come up! I almost mentioned it in the post. What&#039;s your take on it?
At this moment I&#039;m not a fan of the serial comma, and my reasons are a preference for minimalism and a personal challenge. If the context indicates a list, the serial comma is pretty much just redundant decoration and should be nixed. If the context is a bit more vague or if the contents of the list require further indication of distinction or disambiguation, then I&#039;m all for using it. Also, a comma in any place is important for indicating &lt;a href=&quot;http://en.wikipedia.org/wiki/Prosody_(linguistics)&quot; rel=&quot;nofollow&quot;&gt;prosody&lt;/a&gt; (such a good word; one I&#039;d forgotten about before skimming the article I linked to above). So if the pacing of a list needs a pause, give it a comma. My personal challenge is simply to try to use fewer commas. I realized a couple of years ago that I was using loads of commas, and think I&#039;ll improve my overall skill with language if I can manage to stop relying on them so much.
So, in sum: Not a fan of the serial comma unless it&#039;s there for good reason.
(I don&#039;t actually know Interweave&#039;s stance on the serial comma. It&#039;s not something I&#039;d push my chair back for.)</description>
		<content:encoded><![CDATA[<p>@<a href="#comment-3475" rel="nofollow">Michelle</a>: I knew <a href="http://en.wikipedia.org/wiki/Serial_comma" title="serial comma" rel="nofollow">it</a> would come up! I almost mentioned it in the post. What&#8217;s your take on it?<br />
At this moment I&#8217;m not a fan of the serial comma, and my reasons are a preference for minimalism and a personal challenge. If the context indicates a list, the serial comma is pretty much just redundant decoration and should be nixed. If the context is a bit more vague or if the contents of the list require further indication of distinction or disambiguation, then I&#8217;m all for using it. Also, a comma in any place is important for indicating <a href="http://en.wikipedia.org/wiki/Prosody_(linguistics)" rel="nofollow">prosody</a> (such a good word; one I&#8217;d forgotten about before skimming the article I linked to above). So if the pacing of a list needs a pause, give it a comma. My personal challenge is simply to try to use fewer commas. I realized a couple of years ago that I was using loads of commas, and think I&#8217;ll improve my overall skill with language if I can manage to stop relying on them so much.<br />
So, in sum: Not a fan of the serial comma unless it&#8217;s there for good reason.<br />
(I don&#8217;t actually know Interweave&#8217;s stance on the serial comma. It&#8217;s not something I&#8217;d push my chair back for.)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

