<?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: January 1 Doesn&#8217;t Need an &#8220;st&#8221;</title>
	<atom:link href="http://www.dailywritingtips.com/january-1-doesnt-need-an-st/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dailywritingtips.com/january-1-doesnt-need-an-st/</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: Grace S.</title>
		<link>http://www.dailywritingtips.com/january-1-doesnt-need-an-st/comment-page-1/#comment-106950</link>
		<dc:creator>Grace S.</dc:creator>
		<pubDate>Tue, 07 Apr 2009 18:33:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailywritingtips.com/january-1-doesnt-need-an-st/#comment-106950</guid>
		<description>As a commercial print proofreader, I use The Gregg Reference Manual. It indicates that for dates the numeral should stand alone, but for ordinals (as, for example, in street names) the letters should be added. 

Gregg also has a general guideline for abbreviations (and it includes the ordinals in that category), to use the shortest form that can be used without sacrificing clarity of meaning. In the case of ordinals, they prefer to drop the &quot;r&quot; from &quot;rd&quot; (3d instead of 3rd) and the &quot;n&quot; from &quot;nd&quot; (2d instead of 2nd), although they indicate these are alternate forms. Other than in Gregg, I have never seen these numerals written this way, and do not edit out the &quot;r&quot; or &quot;n&quot; when I encounter them (in ordinals used correctly), because I believe it would look like a typo to customers and their audiences--at least in my part of the U.S.</description>
		<content:encoded><![CDATA[<p>As a commercial print proofreader, I use The Gregg Reference Manual. It indicates that for dates the numeral should stand alone, but for ordinals (as, for example, in street names) the letters should be added. </p>
<p>Gregg also has a general guideline for abbreviations (and it includes the ordinals in that category), to use the shortest form that can be used without sacrificing clarity of meaning. In the case of ordinals, they prefer to drop the &#8220;r&#8221; from &#8220;rd&#8221; (3d instead of 3rd) and the &#8220;n&#8221; from &#8220;nd&#8221; (2d instead of 2nd), although they indicate these are alternate forms. Other than in Gregg, I have never seen these numerals written this way, and do not edit out the &#8220;r&#8221; or &#8220;n&#8221; when I encounter them (in ordinals used correctly), because I believe it would look like a typo to customers and their audiences&#8211;at least in my part of the U.S.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott</title>
		<link>http://www.dailywritingtips.com/january-1-doesnt-need-an-st/comment-page-1/#comment-83153</link>
		<dc:creator>Scott</dc:creator>
		<pubDate>Sat, 14 Feb 2009 11:25:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailywritingtips.com/january-1-doesnt-need-an-st/#comment-83153</guid>
		<description>Yes, I like the date format for comments as well. I have to say, I personally love the Japanese date standard of YYYY.MM.DD (i.e. 2009.02.14 ). It leaves very little confusion and all of the dates sort beautifully on my computer.</description>
		<content:encoded><![CDATA[<p>Yes, I like the date format for comments as well. I have to say, I personally love the Japanese date standard of YYYY.MM.DD (i.e. 2009.02.14 ). It leaves very little confusion and all of the dates sort beautifully on my computer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Una</title>
		<link>http://www.dailywritingtips.com/january-1-doesnt-need-an-st/comment-page-1/#comment-77790</link>
		<dc:creator>Una</dc:creator>
		<pubDate>Sun, 01 Feb 2009 03:10:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailywritingtips.com/january-1-doesnt-need-an-st/#comment-77790</guid>
		<description>Did anyone else find it slightly hilarious that the line above the comments keeps stating
X on January the 12th, 13th etc?

:P</description>
		<content:encoded><![CDATA[<p>Did anyone else find it slightly hilarious that the line above the comments keeps stating<br />
X on January the 12th, 13th etc?</p>
<p> <img src='http://www.dailywritingtips.com/wp-includes/images/smilies/icon_razz.gif' alt=':P' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tami</title>
		<link>http://www.dailywritingtips.com/january-1-doesnt-need-an-st/comment-page-1/#comment-70831</link>
		<dc:creator>Tami</dc:creator>
		<pubDate>Tue, 13 Jan 2009 18:59:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailywritingtips.com/january-1-doesnt-need-an-st/#comment-70831</guid>
		<description>I&#039;m a public librarian and also do PR for a public library. I&#039;m constantly after other staff not to submit events using the suffixes after the dates. When I&#039;ve noticed this more and more frequently in writing everywhere including reputable news sites where one would have hoped the writers were trained properly (every academic and professional style source I&#039;ve found says NO NO NO to st, rd, th, etc. after dates). I blame word processing programs that automatically put such suffixes into superscript if you write them. &quot;If the program does this, then it must be correct.&quot; This and the constant misuse of the possessive Apostrophe S for plurals have become my top pet peeves. I&#039;ve also noticed that the dates for the comment posts on this web page use the suffixes.</description>
		<content:encoded><![CDATA[<p>I&#8217;m a public librarian and also do PR for a public library. I&#8217;m constantly after other staff not to submit events using the suffixes after the dates. When I&#8217;ve noticed this more and more frequently in writing everywhere including reputable news sites where one would have hoped the writers were trained properly (every academic and professional style source I&#8217;ve found says NO NO NO to st, rd, th, etc. after dates). I blame word processing programs that automatically put such suffixes into superscript if you write them. &#8220;If the program does this, then it must be correct.&#8221; This and the constant misuse of the possessive Apostrophe S for plurals have become my top pet peeves. I&#8217;ve also noticed that the dates for the comment posts on this web page use the suffixes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Maeve</title>
		<link>http://www.dailywritingtips.com/january-1-doesnt-need-an-st/comment-page-1/#comment-53180</link>
		<dc:creator>Maeve</dc:creator>
		<pubDate>Tue, 11 Nov 2008 13:58:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailywritingtips.com/january-1-doesnt-need-an-st/#comment-53180</guid>
		<description>Peter,
I read &quot;October 12&quot; as &quot;October twelfth.&quot;  I read &quot;Henry VIII&quot; as &quot;Henry the Eighth.&quot;  I read &quot;Xmas&quot; as &quot;Christmas.&quot;  There&#039;s such a thing as convention.</description>
		<content:encoded><![CDATA[<p>Peter,<br />
I read &#8220;October 12&#8243; as &#8220;October twelfth.&#8221;  I read &#8220;Henry VIII&#8221; as &#8220;Henry the Eighth.&#8221;  I read &#8220;Xmas&#8221; as &#8220;Christmas.&#8221;  There&#8217;s such a thing as convention.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
