<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Tangential Ramblings &#187; Grammar etc.</title>
	<atom:link href="http://blog.osirra.com/category/grammar/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.osirra.com</link>
	<description></description>
	<lastBuildDate>Sat, 04 Feb 2012 23:35:54 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Fucking Hobnobs</title>
		<link>http://blog.osirra.com/2011/11/18/fucking-hobnobs/</link>
		<comments>http://blog.osirra.com/2011/11/18/fucking-hobnobs/#comments</comments>
		<pubDate>Fri, 18 Nov 2011 20:57:15 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[Grammar etc.]]></category>
		<category><![CDATA[Life]]></category>

		<guid isPermaLink="false">http://blog.osirra.com/?p=4081</guid>
		<description><![CDATA[Earlier today, my friend Paul Clarke tweeted thus: There are few challenges that cannot be surmounted with the aid of a dark chocolate Hob Nob. I corrected him, suggesting that HobNob was one word, camel case. My source: Wikipedia. (Topical.) Discussion ensued, and I think it was settled that that the current standard is actually [...]]]></description>
			<content:encoded><![CDATA[<p>Earlier today, my friend Paul Clarke <a href="https://twitter.com/#!/paul_clarke/status/137481753433604097"  target="_blank">tweeted</a> thus:</p>
<blockquote><p>There are few challenges that cannot be surmounted with the aid of a dark chocolate Hob Nob.</p></blockquote>
<p>I corrected him, suggesting that HobNob was one word, <a href="http://en.wikipedia.org/wiki/CamelCase" title="Wikipedia: CamelCase"  target="_blank">camel case</a>. My source: Wikipedia. (<a href="http://www.xkcd.com/978/" title="XKCD: Citogenesis"  target="_blank">Topical.</a>) Discussion ensued, and I think it was settled that that the current standard is actually Hobnob—one word, no camel-casing.</p>
<p>The reason for the confusion was that the McVitie&#8217;s branding is inconsistent. It seems that it&#8217;s changed over the years, switching from <em>HobNob</em> to <em>Hobnob</em>. The<a href="http://www.mcvities.co.uk/product_range/5/hobnobs" title="McVitie's Hobnob range"  target="_blank"> current standard</a> is certainly <em>Hobnob</em>.</p>
<p>As such, I&#8217;ve spent part of my Friday evening updating the <a href="http://en.wikipedia.org/wiki/HobNob"  target="_blank">Hobnob Wikipedia page</a> to reflect the revised branding.</p>
<p>FML.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.osirra.com/2011/11/18/fucking-hobnobs/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The proof is in the pudding. Or some such</title>
		<link>http://blog.osirra.com/2011/11/17/the-proof-is-in-the-pudding-or-some-such/</link>
		<comments>http://blog.osirra.com/2011/11/17/the-proof-is-in-the-pudding-or-some-such/#comments</comments>
		<pubDate>Thu, 17 Nov 2011 22:00:55 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[Grammar etc.]]></category>
		<category><![CDATA[Life]]></category>

		<guid isPermaLink="false">http://blog.osirra.com/?p=4076</guid>
		<description><![CDATA[Among other things, I am a proofreader. And it&#8217;s a profession for which many elements might have been commoditised by the internet. If you&#8217;re unsure whether to use affect or effect (or indeed effect), then it&#8217;s easy to find out on the internet. Is it yours or your&#8217;s? (Ouch, that hurt.) Again, the internet is your friend. [...]]]></description>
			<content:encoded><![CDATA[<p>Among other things, I am a proofreader. And it&#8217;s a profession for which many elements might have been commoditised by the internet.</p>
<p>If you&#8217;re unsure whether to use <em>affect</em> or <em>effect</em> (or indeed <em>effect</em>), then it&#8217;s easy to find out on the internet. Is it yours or your&#8217;s? (Ouch, that hurt.) Again, the internet is your friend. Google will tell you.</p>
<p>But the issue is twofold. People don&#8217;t know what needs checking. And even if they did, many wouldn&#8217;t have the wherewithal to check it.</p>
<p>One day, proofreading will become a true commodity. Upload a document and download it in perfect English. (If the document itself is a crock of shit, this attribute will remain.) In the meantime, you know where I am.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.osirra.com/2011/11/17/the-proof-is-in-the-pudding-or-some-such/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Shop names: an idiot’s guide</title>
		<link>http://blog.osirra.com/2011/08/07/shop-names-an-idiot%e2%80%99s-guide/</link>
		<comments>http://blog.osirra.com/2011/08/07/shop-names-an-idiot%e2%80%99s-guide/#comments</comments>
		<pubDate>Sun, 07 Aug 2011 15:02:51 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[Grammar etc.]]></category>

		<guid isPermaLink="false">http://blog.osirra.com/2011/08/07/shop-names-an-idiot%e2%80%99s-guide/</guid>
		<description><![CDATA[Here’s a little advice for you, to make your lives more rewarding and mine less frustrating. It relates to how shop names should be said and written. Here goes. Asda and Tesco are singular. There is never a need to saying you’re going to Asdas, unless you’re going to Asdas up and down the country [...]]]></description>
			<content:encoded><![CDATA[<p>Here’s a little advice for you, to make your lives more rewarding and mine less frustrating. It relates to how shop names should be said and written. Here goes.</p>
<p>Asda and Tesco are singular. There is never a need to saying you’re going to Asdas, unless you’re going to Asdas up and down the country in search for the last remaining Pokemon on Christmas Eve. If you need to pluralise Tesco in such a way, it’s Tescos.</p>
<p>McDonald’s and Sainsbury’s should both be written and said such. I went to McDonald’s. While this is a lie, it’s at least grammatically correct. In writing, avoid at all costs using these with a possessive apostrophe, as this is how wormholes are created. Talk of the profits that McDonald’s made, not of McDonald’s’ profits, or however it might be written.</p>
<p>Marks and Spencer doesn’t have an S at the end. Feel free to abbreviate to Markses, but only if you want to go to Hell.</p>
<p>That is all.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.osirra.com/2011/08/07/shop-names-an-idiot%e2%80%99s-guide/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Language: if in doubt, blame the Americans</title>
		<link>http://blog.osirra.com/2011/07/21/language-if-in-doubt-blame-the-americans/</link>
		<comments>http://blog.osirra.com/2011/07/21/language-if-in-doubt-blame-the-americans/#comments</comments>
		<pubDate>Thu, 21 Jul 2011 22:10:49 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[Grammar etc.]]></category>

		<guid isPermaLink="false">http://blog.osirra.com/?p=3938</guid>
		<description><![CDATA[Yesterday, the BBC published an article titled &#8220;Americanisms: 50 of your most noted examples&#8220;. It included 50 &#8220;Americanisms&#8221; sent in by the ill-educated British public—together with 1,295 comments—before it closed the forum. Some highlights from the 50: Two-time and three-time (instead of double and triple), from D. Rochelle in Bath. My understanding is that this [...]]]></description>
			<content:encoded><![CDATA[<p>Yesterday, the BBC published an article titled &#8220;<a href="http://www.bbc.co.uk/news/magazine-14201796"  target="_blank">Americanisms: 50 of your most noted examples</a>&#8220;. It included 50 &#8220;Americanisms&#8221; sent in by the ill-educated British public—together with 1,295 comments—before it closed the forum. Some highlights from the 50:</p>
<ul>
<li>Two-time and three-time (instead of double and triple), from D. Rochelle in Bath. My understanding is that this relates to concurrency. &#8220;Double–silver medallist&#8221; suggests two in one competition, whereas two-time silver medallist suggests two silver medals won in their career</li>
<li>24/7 instead of 24 hours, 7 days a week, from Simon Ball in Worcester. If we&#8217;re being pedantic, the longhand should have read &#8220;24 hours <em>a day</em>, seven days a week&#8221;, with seven written as a word. And should we use <em>per</em> instead of <em>a</em>? But let&#8217;s not go there, Simon. If you can&#8217;t handle such an obvious abbreviation, then you don&#8217;t belong in 2011. Or should I say AD 2011. Get over yourself</li>
<li>The word &#8220;gotten&#8221; makes Julie Marrs in Warrington shudder, despite it being an 11th century English word</li>
<li>Chris Capewell from Queens [sic] Park should concentrate more on his apostrophes and not let his teeth be set on edge at the use of the term &#8220;train station&#8221;</li>
<li>Ami Grewal, a Brit in New York, does not like the term bi-weekly, preferring fortnightly. But the latter is not common parlance in the US, so it&#8217;s understandable that they use the former. The confusion that the British seem to have over the use of the prefixes <em>bi</em> and <em>semi</em> should really be of greater concern to you, Ami</li>
<li>Michael Zealey in London berates &#8220;You do the Math&#8221;. Maybe we Brits should abbreviate to Math&#8217;s, to indicate the removal of some letters</li>
<li>James in Somerset berates the use of Scotch-Irish. Me too, James, but only because you&#8217;ve used a hyphen instead of an en dash. Scotch, while in declining usage, is a 16th century adjective meaning &#8220;of or relating to Scotland&#8221;</li>
<li>Tabitha in London despairs at the phrase &#8220;that&#8217;ll learn you&#8221;. Me too, but I&#8217;ve found it far more prevalent in the UK than the US</li>
<li>Period or full stop, Stuart Oliver in Sunderland? Well Aristophanes of Byzantium (257 BC – c. 185–180 BC) preferred <em>periodos</em>, from which the former has evolved</li>
<li>D. Henderson in Edinburgh detests the use of the word <em>season</em> in relation to TV series. Quite literally, (s)he should get out more</li>
<li>John in Leicester doesn&#8217;t like people having issues, preferring them to have problems. There&#8217;s one right there</li>
<li>And for Helen, in Martock, Somerset, <em>medalling</em>, as a verb in competition, &#8220;sets [her] teeth on edge with a vengeance&#8221;. I find your turn of phrase far more grating, Helen</li>
</ul>
<div>
<p>Most of the people that commented, I expect, are British sticklers ill-at-ease with change, writing letters on a regular basis to the Telegraph and Points of View. (Apparently, it&#8217;s still on air! Who knew?) But many are ill-educated buffoons of the opinion that any phrase that grates must be down to the Yanks. In actual fact, a good number of the top 50 entries constitute either language changes through business use, or Olde English words that have fallen out of British English usage, but that still form part of the American lexicon.</p>
<p>So people: get over yourselves. Stop blaming the Americans for the beautiful enhancement of our shared language. British and American English should live together in harmony, each celebrating its quirks, but not disparaging the other for infiltrating its own with a phrase that has become common parlance. Oh, and <a href="http://www.osirra.com/2009/11/a-single-version-of-english/" title="osirra: A single version of English"  target="_blank">here&#8217;s my post</a> on developing a single written version of English.</p>
<p>End of.</p>
</div>
]]></content:encoded>
			<wfw:commentRss>http://blog.osirra.com/2011/07/21/language-if-in-doubt-blame-the-americans/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Single space: the final frontier</title>
		<link>http://blog.osirra.com/2011/01/14/single-space-the-final-frontier/</link>
		<comments>http://blog.osirra.com/2011/01/14/single-space-the-final-frontier/#comments</comments>
		<pubDate>Fri, 14 Jan 2011 13:21:44 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[Grammar etc.]]></category>
		<category><![CDATA[Life]]></category>

		<guid isPermaLink="false">http://blog.osirra.com/?p=3747</guid>
		<description><![CDATA[Right now, I am a troubled little soul. You see, I was taught at school that there should be much space in between sentences. Indeed my teacher at the time, in the days of yore before computers were standard issue, literally applied a rule of thumb: there should be a full thumb&#8217;s width between a [...]]]></description>
			<content:encoded><![CDATA[<p>Right now, I am a troubled little soul.</p>
<p>You see, I was taught at school that there should be much space in between sentences. Indeed my teacher at the time, in the days of yore before computers were standard issue, literally applied a rule of thumb: there should be a full thumb&#8217;s width between a full stop and the subsequent sentence. Even with my rather petite thumbs, this amounted to quite a hefty gap.</p>
<p>On the second day, God invented computers—PCs in the morning; Macs and handheld devices in the afternoon, I believe. To allow me to move beyond my first typed sentence, I subconsciously—if I don&#8217;t remember correctly—converted the SI unit of space measurement in the handwritten world (the thumb) into two spaces in the space age, for want of a better phrase. (I&#8217;m laughing at that one, even if you&#8217;re not.) And ever since the mid-1980s, sentences emanating from my fingers have been succeeded by a double-tap of my right thumb.</p>
<p>(I later discovered that my mum has ever used three spaces, a behaviour that I can only describe as deranged (in the loving sense, of course), similarly deranged to the way in which sticklers will no doubt describe my own double-space habit.)</p>
<p>I always thought it was a style thing, a view likely encouraged by my mum&#8217;s quirky behaviour on this front. But my behaviour has drawn an increasing number of frowns of late. Those in the world of publishing—both online and offline—have reliably informed me that such behaviour is not to be accepted, and that one space is the standard.</p>
<p>This is a revelation that I&#8217;m happy, nay eager, to embrace. But I expect it will be my equivalent of giving up smoking. Or putting your socks on in the opposite order to which you generally do it (my <em>modus operandi</em> is left, right, btw). It sounds easy. But it&#8217;s not. For the split second for which my right foot is besocked and my left one is bare, my world is in utter turmoil.</p>
<p>I will need a support mechanism to help me through the months ahead, to unlearn something that has been a subconscious action for well over half my life.</p>
<p>If you catch me using two spaces, please take me to one side and slap me gently across the face. I expect it will be a rough ride, but I&#8217;m hoping you can help me reach the other side a stronger and better person.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.osirra.com/2011/01/14/single-space-the-final-frontier/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
		<item>
		<title>Proofreaders: know your game</title>
		<link>http://blog.osirra.com/2010/02/24/proofreaders-know-your-game/</link>
		<comments>http://blog.osirra.com/2010/02/24/proofreaders-know-your-game/#comments</comments>
		<pubDate>Wed, 24 Feb 2010 20:40:39 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[Grammar etc.]]></category>
		<category><![CDATA[Life]]></category>

		<guid isPermaLink="false">http://blog.osirra.com/?p=3381</guid>
		<description><![CDATA[Proofreading is unique.  Unique in the sense that as well as your CV and cover letter/email containing all of the specifics of your career and experience, they also embody the quality of your work.  Before you&#8217;ve even been invited in for an interview, I&#8217;ve had a small taster for how good you are at submitting [...]]]></description>
			<content:encoded><![CDATA[<p>Proofreading is unique.  Unique in the sense that as well as your CV and cover letter/email containing all of the specifics of your career and experience, they also embody the quality of your work.  Before you&#8217;ve even been invited in for an interview, I&#8217;ve had a small taster for how good you are at submitting error-free documents.</p>
<p>Yet it&#8217;s frightening how many people have emailed me recently asking for work in this very area—my business specialises in document editing—only for their covering emails to be littered with errors.  Admittedly, if I&#8217;d received the emails from people outside the field, people not looking for related work, I would have let the mistakes pass me by.  But their context has meant that I&#8217;ve either responded with some heartfelt, cotton wool-lined guidance, or responded with a pleasantry only to confine the email to the <em>Never hire</em> folder.  (Actually, the latter step is a given.)</p>
<p>Paragraphs have lacked closing periods, <em>proofreader</em> has been written as two words (yet as a single word within the same email), the Oxford comma has been used whimsically, appearing in some places but not in others, hyphens have appeared instead of em dashes, and quotation marks have been used in instances where one might not even expect someone to sign them in a bar with their hands.</p>
<p>Some (all?) of these points might sound pedantic.  And they are.  But then proofreading is all about pedantry, and if you can&#8217;t get your covering email right, what hope do I have that you&#8217;ll fare any better with a client&#8217;s document?</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.osirra.com/2010/02/24/proofreaders-know-your-game/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>My name&#8217;s Dan and I read my own blog</title>
		<link>http://blog.osirra.com/2009/07/18/my-names-dan-and-i-read-my-own-blog/</link>
		<comments>http://blog.osirra.com/2009/07/18/my-names-dan-and-i-read-my-own-blog/#comments</comments>
		<pubDate>Sat, 18 Jul 2009 12:25:23 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[Grammar etc.]]></category>

		<guid isPermaLink="false">http://blog.osirra.com/?p=3185</guid>
		<description><![CDATA[It&#8217;s a bit sad, isn&#8217;t it? But I subscribe to my own blog in Google Reader. And I read most of the posts that appear there. Before publishing a post, I&#8217;ll preview it, allowing me to assess the prose before it is exposed to its audience, however small that audience may be. This gives me [...]]]></description>
			<content:encoded><![CDATA[<p>It&#8217;s a bit sad, isn&#8217;t it?  But I subscribe to my own blog in Google Reader.  And I read most of the posts that appear there.</p>
<p>Before publishing a post, I&#8217;ll preview it, allowing me to assess the prose before it is exposed to its audience, however small that audience may be.  This gives me the opportunity to correct any issues with flow, and any howlers I may have made along the way.</p>
<p>And some time after I&#8217;ve hit the <em>Publish</em> button, the post will pop up in Google Reader.  And invariably, I&#8217;ll read it in its entirety.  Occasionally, I&#8217;ll spot a mistake that slipped through the net—I find my own work the most difficult to proofread, as I&#8217;m too close to it—but more importantly, I&#8217;ll read it as an audience member, given the delay since having read it.</p>
<p>And I like little better than stumbling upon old posts from years back to see what I had to say.  I&#8217;m happy to say that my writing has improved over the last five years, as has <strike>by</strike> my grammar.  Notwithstanding, I enjoy the things I had to say back then.</p>
<p>I&#8217;d be interested as to whether others out there read their own work.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.osirra.com/2009/07/18/my-names-dan-and-i-read-my-own-blog/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Beautiful date formats</title>
		<link>http://blog.osirra.com/2009/06/02/beautiful-date-formats/</link>
		<comments>http://blog.osirra.com/2009/06/02/beautiful-date-formats/#comments</comments>
		<pubDate>Tue, 02 Jun 2009 21:57:03 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[Grammar etc.]]></category>

		<guid isPermaLink="false">http://www.osirra.com/?p=3060</guid>
		<description><![CDATA[I&#8217;ve struggled with date formats for some time now.  Formats for dates that don&#8217;t need to be interpreted by computers that is, those that appear in documents.  For the sake of example, we&#8217;ll use the sixth day of December last year. While in America, I did as the Americans.  Shorthand was 12/6 (or &#8220;twelve six&#8221; [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve struggled with date formats for some time now.  Formats for dates that don&#8217;t need to be interpreted by computers that is, those that appear in documents.  For the sake of example, we&#8217;ll use the sixth day of December last year.</p>
<p>While in America, I did as the Americans.  Shorthand was 12/6 (or &#8220;twelve six&#8221; when voiced).  Longhand, it was December 6, 2008.  When combined with the year, it always struck me as slightly odd that the specificity was inconsistent from left to right: first came the month, which was then made more specific with the day.  Yet at this stage, the reader doesn&#8217;t yet know the year.  In the UK&#8217;s DD/MM/YYYY format, specificity decreases from left to right.  Although arguably, what use is the day without first knowing the month?</p>
<p>The comma in the American longhand version was necessary to separate the two numbers.  At first, I was uncomfortable with the proximity of these two numbers.  But over time, I came to regard it as an attribute rather than a hindrance.  And I came to adore the longhand variant.</p>
<p>(The shorthand version continued to confuse me throughout my two years there, and mentally I had to deconstruct the two numbers bleated out to figure out what they represented, particularly for days in the first twelve of the month.  Not ideal, being a project manager.)</p>
<p>Now back in the UK, I&#8217;ve recently settled on a format that I&#8217;m comfortable with.  In Excel, we&#8217;d say <em>d mmmm, yyyy</em>.  In English: 6 December, 2008.  Where the year is redundant, I simply opt for 6 December.  Never should either be preceded with a jarring <em>the</em>.  (My word do I hate that?)  When talking of a month, I use December 2008, without the intervening comma—it&#8217;s too short to warrant one.</p>
<p>For the full variation, I like its simplicity.  I&#8217;ve never been a big fan of the superscripts that come into play with ordinal numbers—when I do use ordinals, I always reject MS Word&#8217;s auto-formatting, leaving them in standard font—6th.  And I feel that the comma is necessary to give some rhythm to the construct.  As for the months, I feel that our Gregorian legacy is sufficiently poetic and inspiring for the months not to be abbreviated.  Let&#8217;s save that crime for data files.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.osirra.com/2009/06/02/beautiful-date-formats/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Out of orifice emails</title>
		<link>http://blog.osirra.com/2009/05/21/out-of-orifice-email/</link>
		<comments>http://blog.osirra.com/2009/05/21/out-of-orifice-email/#comments</comments>
		<pubDate>Thu, 21 May 2009 21:29:31 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[Grammar etc.]]></category>

		<guid isPermaLink="false">http://www.osirra.com/?p=3025</guid>
		<description><![CDATA[The Outlook interface for creating and editing your out-of-office email response is dreadful. In Outlook 2007, it constitutes a text-box four lines high, maybe 350 pixels wide for entering raw, unformatted text. Keep typing and you&#8217;ll get a vertical scrollbar. And the interface does not allow for spell-checking. The dreadfully constrained interface and the lack [...]]]></description>
			<content:encoded><![CDATA[<p>The Outlook interface for creating and editing your out-of-office email response is dreadful.  In Outlook 2007, it constitutes a text-box four lines high, maybe 350 pixels wide for entering raw, unformatted text.  Keep typing and you&#8217;ll get a vertical scrollbar.</p>
<p>And the interface does not allow for spell-checking.</p>
<p>The dreadfully constrained interface and the lack of a spell-checker make for out-of-office emails littered with typos and grammatical heathenry, an email that is sent to way more people than any other.  I would estimate that over half of those I receive contain at least one error.</p>
<p>Today&#8217;s examples:</p>
<ul>
<li>I am out of the office until Friday 22nd May and will limited access my emails during this time</li>
<li>I am out of the office at a and will be back at work on the 26th May 2009</li>
</ul>
<p>Please.  Copy your email into Word.  Read it, check it and double-check it before turning your out of office on.  Thank you.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.osirra.com/2009/05/21/out-of-orifice-email/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Too high for Nate</title>
		<link>http://blog.osirra.com/2009/04/11/too-high-for-nate/</link>
		<comments>http://blog.osirra.com/2009/04/11/too-high-for-nate/#comments</comments>
		<pubDate>Sat, 11 Apr 2009 11:37:49 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[Grammar etc.]]></category>

		<guid isPermaLink="false">http://www.osirra.com/?p=2885</guid>
		<description><![CDATA[Lots of sites, both professional and otherwise, seem to be using a double-hyphen when they mean to use an em dash.  It&#8217;s as if they know that they need a long dash, but can&#8217;t be arsed to insert one. The double-hyphen looks hideous, but it&#8217;s as if I should give them credit for trying.  How [...]]]></description>
			<content:encoded><![CDATA[<p>Lots of sites, both professional and otherwise, seem to be using a double-hyphen when they mean to use an em dash.  It&#8217;s as if they know that they need a long dash, but can&#8217;t be arsed to insert one.</p>
<p>The double-hyphen looks hideous, but it&#8217;s as if I should give them credit for trying.  How about trying a bit harder and typing <em>ALT+0151</em> (on the number keypad, not the top row).  Or if you&#8217;re in WordPress (I am, don&#8217;t you know), hit the <em>Insert Custom Character</em> button sporting a <em>Ω</em> symbol, having hit the <em>Show/Hide Kitchen Sink</em> button).  The em dash can be found on the second row, fifth symbol from the right.</p>
<p>Here you&#8217;ll find more on <a title="Tangential Rambings: the hyphen, the en dash and the em dash" href="/2006/02/19/the-hyphen-the-en-dash-and-the-em-dash/" target="_self">the correct use of hyphens, en dashes and em dashes</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.osirra.com/2009/04/11/too-high-for-nate/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->
