<?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>osirra consulting</title>
	<atom:link href="http://www.osirra.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.osirra.com</link>
	<description>Precision, insight, delivery.</description>
	<lastBuildDate>Sun, 13 May 2012 09:42:01 +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>The change from read to red, with associated changes</title>
		<link>http://www.osirra.com/2012/05/the-change-from-read-to-red-with-associated-changes/</link>
		<comments>http://www.osirra.com/2012/05/the-change-from-read-to-red-with-associated-changes/#comments</comments>
		<pubDate>Sun, 13 May 2012 09:42:01 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[Rules]]></category>

		<guid isPermaLink="false">http://www.osirra.com/?p=449</guid>
		<description><![CDATA[Yesterday my friend Paul suggested evolving the English language to change the perfect tense of the verb &#8220;read&#8221; to &#8220;red&#8221;. This change has been endorsed by the Brit. Eng. language committee, and will come into effect, incorporated with the necessary and associated changes below, on 1 July 2012. Red: Despite possible confusion with the colour, [...]]]></description>
			<content:encoded><![CDATA[<p>Yesterday my friend Paul <a title="Twitter link" href="https://twitter.com/#!/paul_clarke/status/201208740811247616" target="_blank">suggested evolving the English language</a> to change the perfect tense of the verb &#8220;read&#8221; to &#8220;red&#8221;. This change has been endorsed by the Brit. Eng. language committee, and will come into effect, incorporated with the necessary and associated changes below, on 1 July 2012.</p>
<ul>
<li>Red: Despite possible confusion with the colour, the perfect tense of read will change to &#8220;red&#8221;. This brings it in line with the verb lead/led. &#8220;I am not going to read that book because I have red it already.&#8221;</li>
<li>Insted: To avoid people mispronouncing words ending in &#8220;ead&#8221; that rhyme with &#8220;red&#8221;, the &#8220;a&#8221; will be removed. These include, but are not limited to, insted (instead), sted (stead), ded (dead), hed (head), led (lead, as in the metal; leads for dogs will remain unchanged), bred (bread), tred (tread).</li>
<li>Mead and bead will remain unaffected by the change.</li>
<li>To avoid confusion, present-tense verbs containing &#8220;ed&#8221; will be changed to incorporate an &#8220;a&#8221;, their pronunciation changing accordingly. People will wead, but will have wed, and people will attend weadings. And the slang term for &#8220;bedding someone&#8221; will become &#8220;beading&#8221;.</li>
</ul>
<p>Full details of the change can be red by writing to the Hed of the British English society, or insted on their website.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.osirra.com/2012/05/the-change-from-read-to-red-with-associated-changes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Syllepsis</title>
		<link>http://www.osirra.com/2012/04/syllepsis/</link>
		<comments>http://www.osirra.com/2012/04/syllepsis/#comments</comments>
		<pubDate>Fri, 06 Apr 2012 21:02:04 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[Grammar]]></category>

		<guid isPermaLink="false">http://www.osirra.com/?p=444</guid>
		<description><![CDATA[I learnt a new word today: syllepsis. A syllepsis is a specific type of zeugma, which begs the question: what&#8217;s a zeugma. A zeugma is a figure of speech in which multiple parts of a sentence are joined with a single verb or noun. Family, religion, friendship. These are the three demons you must slay [...]]]></description>
			<content:encoded><![CDATA[<p>I learnt a new word today: <a href="http://en.wikipedia.org/wiki/Zeugma#Syllepsis" target="_blank">syllepsis</a>.</p>
<p>A syllepsis is a specific type of <a href="http://en.wikipedia.org/wiki/Zeugma" target="_blank">zeugma</a>, which begs the question: what&#8217;s a zeugma.</p>
<p>A zeugma is a figure of speech in which multiple parts of a sentence are joined with a single verb or noun.</p>
<blockquote><p>Family, religion, friendship. These are the three demons you must slay if you wish to succeed in business.</p></blockquote>
<p>The verb is operating on three objects, but means something subtly different in each case.</p>
<p>A syllepsis (also known as a semantic zeugma) is a zeugma in which the grammar becomes stilted, either because of a change in meaning or through a grammatical inconsistency.</p>
<blockquote><p>He carried a strobe light and the responsibility for the lives of his men.</p>
<p>She lowered her standards by raising her glass.</p>
<p>The sky—and my hopes—is falling.</p></blockquote>
<p>Syllepses are intended constructs. And I rather like them.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.osirra.com/2012/04/syllepsis/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Staff is vs. staff are</title>
		<link>http://www.osirra.com/2012/04/staff-is-vs-staff-are/</link>
		<comments>http://www.osirra.com/2012/04/staff-is-vs-staff-are/#comments</comments>
		<pubDate>Thu, 05 Apr 2012 15:58:59 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[Grammar]]></category>

		<guid isPermaLink="false">http://www.osirra.com/?p=441</guid>
		<description><![CDATA[A friend emailed yesterday asking why Microsoft tried to change &#8220;staff are&#8221; to &#8220;staffs are&#8221;. Here&#8217;s some background. Imagine the following sentence. The staff are going to go bananas when they find out. Now taking aside whether you&#8217;re happy about the word &#8220;bananas&#8221; in the above sentence, my understanding is that most Brits will find this sentence perfectly fine, while [...]]]></description>
			<content:encoded><![CDATA[<p>A friend emailed yesterday asking why Microsoft tried to change &#8220;staff are&#8221; to &#8220;staffs are&#8221;. Here&#8217;s some background.</p>
<p>Imagine the following sentence.</p>
<blockquote><p>The staff are going to go bananas when they find out.</p></blockquote>
<p>Now taking aside whether you&#8217;re happy about the word &#8220;bananas&#8221; in the above sentence, my understanding is that most Brits will find this sentence perfectly fine, while many Americans will smart at it. And here&#8217;s why.</p>
<p>Americans are much more loyal to the rule that a group noun must be treated as singular. In the main, they will treat family, team, staff as singular and the verb will obey this rule. So the England team is without a manager, my family is so dysfunctional, and the staff is going to go bananas when they find out.</p>
<p>Meanwhile, British people deem those sentences to read awkwardly. So in the main, we&#8217;ll tend towards adopting the plural form of the noun: the England team are going to struggle in Euro 2012, my family are going on holiday without me, and the staff are going to go bananas.</p>
<p>Microsoft Word, whether it&#8217;s set to UK or US English, underlines &#8220;staff are&#8221; in green, flagging it as a potential grammar violation. It suggests &#8220;staff is&#8221; or staffs are&#8221;. The former bows to the American English strictness for treating group nouns as singular; the latter suggests you may be writing about shepherds&#8217; staffs.</p>
<p>I expect that American English has its limits when it comes to the pluralisation of group nouns. &#8220;Number&#8221;, for example, is one that should strictly be singular, but I expect is treated as plural on both sides of the Pond. &#8220;A number of people is going out tonight&#8221; would, I expect, cause consternation regardless of nationality.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.osirra.com/2012/04/staff-is-vs-staff-are/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Eleven days; 119,754 words; 31,587 changes</title>
		<link>http://www.osirra.com/2012/02/eleven-days-119754-words-31587-changes/</link>
		<comments>http://www.osirra.com/2012/02/eleven-days-119754-words-31587-changes/#comments</comments>
		<pubDate>Mon, 27 Feb 2012 13:51:53 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[Life]]></category>

		<guid isPermaLink="false">http://www.osirra.com/?p=435</guid>
		<description><![CDATA[Last month, one of our biggest clients forewarned us of a proofreading project coming up in late February. At the time, they indicated it would be around 25,000 words, &#8220;with a few other documents in the mix&#8221;. Even when the documents started coming through a week last Thursday, we weren&#8217;t fully aware of the scale [...]]]></description>
			<content:encoded><![CDATA[<p>Last month, one of our biggest clients forewarned us of a proofreading project coming up in late February.</p>
<p>At the time, they indicated it would be around 25,000 words, &#8220;with a few other documents in the mix&#8221;.</p>
<p>Even when the documents started coming through a week last Thursday, we weren&#8217;t fully aware of the scale of this project, the deadline for which was today (eleven days in total).</p>
<p>All told, the client delivered 34 documents, with a total word count of 119,754.</p>
<p>Not knowing the full scale of the job meant that it was a difficult project to resource. I knew we&#8217;d need two people, and there was a possibility that we&#8217;d need a third.</p>
<p>In some respects, having it split into 34 documents makes a job like this easier. Having the work split up into bite-size chunks gives lower-level milestones against which progress can be measured, and more easily allows the work to be divided between different proofreaders. A single 120,000-word document might have been more daunting. But each document was written by a different set of authors, each with their own style, their own idiosyncrasies, their own types of mistake.</p>
<p>The last week has meant some very late nights for three people, myself included. But the last document was sent to the client on schedule this morning.</p>
<p>The highlight for me was spotting that the product number for an obscure piece of hardware was missing a letter. My hope is that this change alone will astound the client at the level of rigour we apply to the task. (Google means that anything and everything can be checked.) The lowlight was undoubtedly my overwriting a 2,000-word proofread document on the final evening. Huge thanks to Steve for stepping in to re-review it to save my addled brain, which was barely running on empty at the time.</p>
<p>It was a marvellous team effort. I&#8217;m hugely indebted to Steve and Paul for their extraordinary efforts on this one. They&#8217;ve been instrumental to the success of this project.</p>
<p>Now, hopefully some respite before the next big project arrives.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.osirra.com/2012/02/eleven-days-119754-words-31587-changes/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>The introduction of the asterisk</title>
		<link>http://www.osirra.com/2012/01/the-introduction-of-the-asterisk/</link>
		<comments>http://www.osirra.com/2012/01/the-introduction-of-the-asterisk/#comments</comments>
		<pubDate>Sat, 28 Jan 2012 23:13:43 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[Life]]></category>

		<guid isPermaLink="false">http://www.osirra.com/?p=429</guid>
		<description><![CDATA[As a proofreader, many would think that I&#8217;m averse to changes in language. But I&#8217;m not. I welcome change. While I&#8217;m not one to fully embrace txtspk, there are certain features that I enjoy and adopt. The asterisk is one such feature. I use it in two contexts. First, I use it to emphasise. To [...]]]></description>
			<content:encoded><![CDATA[<p>As a proofreader, many would think that I&#8217;m averse to changes in language. But I&#8217;m not. I welcome change. While I&#8217;m not one to fully embrace <a title="Wikipedia: txtspk" href="http://en.wikipedia.org/wiki/SMS_language" target="_blank">txtspk</a>, there are certain features that I enjoy and adopt.</p>
<p>The asterisk is one such feature. I use it in two contexts.</p>
<p>First, I use it to emphasise.</p>
<p>To quote Chandler in <em>Friends</em>, &#8220;could this *be* any more lame?&#8221; Underlining is now largely frowned upon given its use in hyperlinks; and bold is considered harsh. Italics has various other uses (see <em>Friends</em> earlier in this paragraph), and so the asterisks are a welcome addition.</p>
<p>I wouldn&#8217;t use them in an overly formal letter, but I regularly use them in relatively formal work-related emails. And I admit, part of me does so to invite question.</p>
<p>Second, I use it to indicate an action.</p>
<p>This one is used in online conversations to indicate what you&#8217;re doing, usually in a non-factual way. *puts kettle on* or *puts on loungin&#8217; pants*. It&#8217;s used to evoke a sense of what you might be doing in response to some preceding comment in the conversation.</p>
<p>Oddly, even though it&#8217;s a reference to the first person, yourself, it&#8217;s always phrased without the subject, yet in the third person. A bit like <a title="Wikipedia: The Jimmy" href="http://en.wikipedia.org/wiki/The_Jimmy" target="_blank">Jimmy</a> in Seinfeld.</p>
<p>I wouldn&#8217;t write this in work emails, except in an informal manner to people more savvy in Twitter and txtspk. In the main, I&#8217;d save this for a Facebook conversation or a Twitter retort.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.osirra.com/2012/01/the-introduction-of-the-asterisk/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Are you trying to write a letter?</title>
		<link>http://www.osirra.com/2012/01/are-you-trying-to-write-a-letter/</link>
		<comments>http://www.osirra.com/2012/01/are-you-trying-to-write-a-letter/#comments</comments>
		<pubDate>Sat, 28 Jan 2012 22:43:47 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[Rules]]></category>

		<guid isPermaLink="false">http://www.osirra.com/?p=427</guid>
		<description><![CDATA[At work the other day, someone was writing a letter. A traditional, formal letter on letterhead and everything. It was to a client, for audit purposes. Hence the formality. There was question about which valediction should be paired with &#8220;To whom it may concern&#8221;. (Yours faithfully.) And then discussion turned to questions of format: where [...]]]></description>
			<content:encoded><![CDATA[<p>At work the other day, someone was writing a letter. A traditional, formal letter on letterhead and everything. It was to a client, for audit purposes. Hence the formality.</p>
<p>There was question about which valediction should be paired with &#8220;To whom it may concern&#8221;. (Yours faithfully.) And then discussion turned to questions of format: where to put the date, how much space to leave before the sign-off name, how many spaces thereafter before any enclosures were listed etc.</p>
<p>My view is that in letters, most things are stylistic rather than formulaic. That is, how you structure things is your call. There are, however, a few things that are sacred.</p>
<ul>
<li>Your own address should either be part of the letterhead or should appear at the top, on the right-hand side</li>
<li>The recipient&#8217;s name and address should appear on the left, either beneath the letterhead or lower on the page than your own address details. Basically, it should be positioned to hit the window of a DL envelope when the A4 page is folded into three, even if a different delivery mechanism is being used</li>
<li>If there is a subject, this should appear directly beneath the salutation</li>
<li>The valediction should be in keeping with the salutation. <em>Dear Sir/Madam</em> or <em>To whom it may concern</em> should be paired with a <em>Yours faithfully</em>. Letters to a named individual can be paired with anything.</li>
</ul>
<p>To me, <em>Yours sincerely</em> is no longer necessary. A more friendly valediction can be used without causing offence. But <em>Yours faithfully</em> is still sacrosanct. I often simply use <em>Sincerely</em>, which softens the harshness of the traditional version, and puts emphasis on the sentiment (sincerity) rather than the formal construct.</p>
<p>Whether you put the date on the left or right is a decision of style, as is spacing.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.osirra.com/2012/01/are-you-trying-to-write-a-letter/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Grammatical renegades</title>
		<link>http://www.osirra.com/2012/01/grammatical-renegades/</link>
		<comments>http://www.osirra.com/2012/01/grammatical-renegades/#comments</comments>
		<pubDate>Sat, 21 Jan 2012 23:23:06 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[Life]]></category>

		<guid isPermaLink="false">http://www.osirra.com/?p=422</guid>
		<description><![CDATA[There are three types of shop. There are the grammatical stalwarts, clinging to the apostrophe in their Men&#8217;s, Women&#8217;s and Children&#8217;s departments, no doubt seething at the lacking punctuation in Menswear and the like. There are the grammatical heathens, with signs directing you to the Childrens&#8217; Department or the Womens&#8217; Toilets, but correctly to the [...]]]></description>
			<content:encoded><![CDATA[<p>There are three types of shop.</p>
<p>There are the grammatical stalwarts, clinging to the apostrophe in their Men&#8217;s, Women&#8217;s and Children&#8217;s departments, no doubt seething at the lacking punctuation in Menswear and the like.</p>
<p>There are the grammatical heathens, with signs directing you to the Childrens&#8217; Department or the Womens&#8217; Toilets, but correctly to the Men&#8217;s Shoes. Inconsistency abounds.</p>
<p>And finally, there are the grammatical renegades. These are the ones that have actively shunned the awkward apostrophe that sits within departments&#8217; signage, but that have done so consistently, resolutely and boldly.</p>
<p><em><a href="http://www.clarks.co.uk/" target="_blank">Clarks</a></em> is a good example of the latter. You won&#8217;t find a single apostrophe on their website. Their departments are Boys, Girls, Mens, Womens. It&#8217;s clear that they&#8217;ve made an active choice to shun it, possibly for SEO reasons, possibly for typographical beauty and neatness, likely a combination of the two.</p>
<p>And while it may grate at first, I have to respect them for the decision. The fact that it is an active decision makes it admirable. They know what they&#8217;re doing, and they know that it&#8217;s technically wrong, but they&#8217;re pushing forward regardless, on the basis that life without it will be easier than that with it. Just as <a title="Guardian: So, Waterstones – no apostrophe? Hey, no catastrophe" href="http://www.guardian.co.uk/commentisfree/2012/jan/12/waterstones-apostrophe-no-catastrophe" target="_blank">Waterstone&#8217;s announced last week</a>.</p>
<p>(The slight awkwardness comes when branding meets the written word. Their marketing emails talk of savings on men&#8217;s boots, with graphics advertising great savings on mens styles.)</p>
<p>Notwithstanding, as long as people know what they&#8217;re doing, I&#8217;m all for a bold move like this. It&#8217;s the grammatical heathens that you&#8217;ve got to worry about.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.osirra.com/2012/01/grammatical-renegades/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>That vs. which</title>
		<link>http://www.osirra.com/2012/01/that-vs-which/</link>
		<comments>http://www.osirra.com/2012/01/that-vs-which/#comments</comments>
		<pubDate>Sat, 14 Jan 2012 14:07:27 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[Rules]]></category>

		<guid isPermaLink="false">http://www.osirra.com/?p=419</guid>
		<description><![CDATA[That and which have become interchangeable in certain aspects of their use. Take the sentence below. We have overtaken the car that/which was holding us up. Either is fine. Traditionalists, and those over 60, will default to using which. But many style guides have moved to endorse that. My preferred style is to use that. [...]]]></description>
			<content:encoded><![CDATA[<p><em>That</em> and <em>which</em> have become interchangeable in certain aspects of their use. Take the sentence below.</p>
<blockquote><p>We have overtaken the car <em>that/which</em> was holding us up.</p></blockquote>
<p>Either is fine. Traditionalists, and those over 60, will default to using <em>which</em>. But many style guides have moved to endorse <em>that</em>.</p>
<p>My preferred style is to use <em>that</em>. My loose rule: <em>which</em> follows a comma, <em>that</em> does not. Take the two sentences below.</p>
<blockquote><p>We have overtaken the car that was holding us up.</p>
<p>We have overtaken the car, which was holding us up.</p></blockquote>
<p>While the two sentences are pretty similar in their sense and meaning, there&#8217;s an important distinction. In the former, the car that was holding us up is, in its entirety, the object of the sentence, modified by what&#8217;s known as a restrictive clause. In the latter, the car is the object, a subsequent clause (called non-restrictive) giving some further information about its annoying slowness.</p>
<p>My view is that while the comma distinguishes between the two sentences, further distinguishing them by using opposing pronouns can do nothing but good.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.osirra.com/2012/01/that-vs-which/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>How to apply for a proofreading post</title>
		<link>http://www.osirra.com/2012/01/how-to-apply-for-a-proofreading-post/</link>
		<comments>http://www.osirra.com/2012/01/how-to-apply-for-a-proofreading-post/#comments</comments>
		<pubDate>Sat, 07 Jan 2012 18:16:26 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[Life]]></category>

		<guid isPermaLink="false">http://www.osirra.com/?p=415</guid>
		<description><![CDATA[You’re no doubt reading this post because you&#8217;ve seen we&#8217;re always looking for new talent; fresh eyes to peruse the documents that we receive and polish them like they&#8217;ve never been polished before. You&#8217;re interested in what makes us tick, and which buttons to push to ensure that your own application makes its way to [...]]]></description>
			<content:encoded><![CDATA[<p>You’re no doubt reading this post because you&#8217;ve seen we&#8217;re always looking for new talent; fresh eyes to peruse the documents that we receive and polish them like they&#8217;ve never been polished before. You&#8217;re interested in what makes us tick, and which buttons to push to ensure that your own application makes its way to the top of the pile.</p>
<p>You&#8217;re in luck, because here’s some advice for those looking for work in this arena, specifically with osirra: mistakes in your application are not an option.</p>
<p>You see, we operate in a line of work where we correct mistakes. We correct mistakes in the written word. So if we at osirra stumble upon a CV or a covering letter that contains mistakes, we aren&#8217;t going to look upon it too favourably. In fact, we&#8217;ll probably think that if you make mistakes like this in your application, there&#8217;s nothing to stop you allowing similar mistakes through in reviewing our clients&#8217; work.</p>
<p>If you apply for a proof reading position, we&#8217;re likely to bin your application in favour of someone applying for a proofreading position. If your salutation is to Mr. Ossira, we&#8217;d much rather this was spelt with a solitary S and a couple of Rs, consistent with the logo at the top of our website. And if you sign that same application off with &#8220;Yours faithfully&#8221;, then please include your home address to allow us to hang, draw and quarter you.</p>
<p>If you were applying for a position as a bricklayer, then where/whether you put an apostrophe in the word &#8220;its&#8221; matters not one jot. (We&#8217;re not currently recruiting any bricklayers, by the way, but if that changes, you&#8217;ll be the first to know.)</p>
<p>But the people we work with are of a certain ilk. We have a passion for detail. We adore finding errant apostrophes; a customer compliant (where a complaint would be more logical); incorrectly-spelled hospital names in the Black Country; and even executives&#8217; names spelt incorrectly, something that the writer should rightly know better than we do.</p>
<p>We&#8217;re passionate about content. We&#8217;re passionate about researching where we&#8217;re not quite sure. And we&#8217;re passionate about getting things right.</p>
<p>Don&#8217;t get me wrong: we all make mistakes. I&#8217;ve sent emails that I&#8217;ve looked back on months after the event that contain howling typos that scream at you when read cold. But here&#8217;s the important thing: I&#8217;ve never done so when applying for a proofreading position. Such applications are unique in their self-referential quality.</p>
<p>So please, before you submit your CV or hit send on a covering email, stop. Read it again. And again. Send it to a similar-minded friend to proofread on your behalf. And read it again. Make sure it&#8217;s absolutely watertight before it reaches us. Because anything less simply won&#8217;t do.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.osirra.com/2012/01/how-to-apply-for-a-proofreading-post/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The apostrophe that few people get</title>
		<link>http://www.osirra.com/2011/12/the-apostrophe-that-few-people-get/</link>
		<comments>http://www.osirra.com/2011/12/the-apostrophe-that-few-people-get/#comments</comments>
		<pubDate>Wed, 21 Dec 2011 22:44:49 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[Grammar]]></category>

		<guid isPermaLink="false">http://www.osirra.com/?p=413</guid>
		<description><![CDATA[Most professionals get the apostrophe. They understand when to use it, when not to, what it signifies and most of the rules associated with it. They know that it&#8217;s important that its use is correct. And they&#8217;re confident in their ability to use them correctly. But there is one apostrophe use that always divides opinion [...]]]></description>
			<content:encoded><![CDATA[<p>Most professionals get the apostrophe. They understand when to use it, when not to, what it signifies and most of the rules associated with it. They know that it&#8217;s important that its use is correct. And they&#8217;re confident in their ability to use them correctly.</p>
<p>But there is one apostrophe use that always divides opinion and gets people debating, often vehemently. I have no idea what it&#8217;s called. But I know how to use it. Below is an example sentence.</p>
<blockquote><p>Please can you give me two hundred pounds&#8217; worth of dollars?</p></blockquote>
<p>From the discussions I&#8217;ve had about it, most people will not use an apostrophe. Nor will they think one&#8217;s necessary when prompted. But the apostrophe is necessary, and not using one is, technically, grammatically incorrect.</p>
<p>For a moment, consider its singular equivalent.</p>
<blockquote><p>Please can you give me a pound&#8217;s worth of gobstoppers?</p></blockquote>
<p>Now apart from swapping dollars for gobstoppers, mainly to lighten the mood, the only change is reducing the two hundred to one.</p>
<p>In this latter example, I don&#8217;t think any semi-educated person in their right mind would think of leaving the apostrophe out. But by pluralising the amount, suddenly it becomes confusing.</p>
<p>This apostrophe will be the first to disappear as English changes and grammatical correctness becomes compromised with time. And eventually, likely in my lifetime, it will become grammatically incorrect to use one.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.osirra.com/2011/12/the-apostrophe-that-few-people-get/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Grammar: Things I can&#8217;t abide</title>
		<link>http://www.osirra.com/2011/07/grammar-things-i-cant-abide/</link>
		<comments>http://www.osirra.com/2011/07/grammar-things-i-cant-abide/#comments</comments>
		<pubDate>Sat, 16 Jul 2011 20:51:24 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[Grammar]]></category>

		<guid isPermaLink="false">http://www.osirra.com/?p=408</guid>
		<description><![CDATA[As a professional proofreader, I look for everything that&#8217;s wrong with a piece of text. Sometimes even when not proofreading, I struggle to rise myself above the grammar. But there are certain things that I really can&#8217;t abide. Fortunately for you, my services will get rid of such things for you—as well as countless others. [...]]]></description>
			<content:encoded><![CDATA[<p>As a professional proofreader, I look for everything that&#8217;s wrong with a piece of text. Sometimes even when not proofreading, I struggle to rise myself above the grammar.</p>
<p>But there are certain things that I really can&#8217;t abide. Fortunately for you, my services will get rid of such things for you—as well as countless others. Below is a short list of the ones that drive me nuts:</p>
<ul>
<li>Inconsistent spacing between sentences. Sometimes one; sometimes two.</li>
<li>Faux ellipses. Three full stops/periods (&#8230;) instead of the ellipsis symbol (…).</li>
<li>Hyperlinks that underline a trailing space or punctuation mark as well as the words that form the link. (Note that if an entire sentence is being hyperlinked, the full stop/period at the end <em>should</em> be underlined.)</li>
<li>Italicised words or phrases that also have the leading or trailing space italicised. It&#8217;s not obvious to a lay-reader, but it kills me.</li>
<li>Inconsistent punctuation at the end of bullets.</li>
<li>Redundant spaces at the end of paragraphs. Yes, I know they&#8217;re not harming anyone, but they are doing untold damage to my sanity.</li>
</ul>
<p>Above are some of the reasons I&#8217;m a proofreader, and arguably no fun to be around.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.osirra.com/2011/07/grammar-things-i-cant-abide/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Carrying over a who</title>
		<link>http://www.osirra.com/2010/05/carrying-over-a-who/</link>
		<comments>http://www.osirra.com/2010/05/carrying-over-a-who/#comments</comments>
		<pubDate>Sun, 30 May 2010 20:09:11 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[Grammar]]></category>

		<guid isPermaLink="false">http://www.osirra.com/?p=392</guid>
		<description><![CDATA[I paused on reading the following sentence in a BBC News article recently. Inquiries also continue over the disappearance of Susan Rushworth, 43, who also worked as a prostitute and was last seen near her home in the Manningham area of Bradford on 22 June last year. In the latter half of the sentence, the [...]]]></description>
			<content:encoded><![CDATA[<p>I paused on reading the following sentence in a <a title="BBC News: Body parts found in river in Bradford woman search" href="http://news.bbc.co.uk/1/hi/england/bradford_and_west_yorkshire/10159300.stm" target="_blank">BBC News article</a> recently.</p>
<blockquote><p>Inquiries also continue over the disappearance of Susan Rushworth, 43, who also worked as a prostitute and was last seen near her home in the Manningham area of Bradford on 22 June last year.</p></blockquote>
<p>In the latter half of the sentence, the carry-over of the who is unacceptable.  The two constructs—&#8221;worked&#8221; and &#8220;was last seen&#8221;—are sufficiently different from one another to necessitate a second &#8220;who&#8221;.  I&#8217;m not sure whether the issue lies in the verbs being different in nature, or whether it&#8217;s because their context is so very different, but a second &#8220;who&#8221; is needed before the &#8220;was&#8221;.  If it had instead read:</p>
<blockquote><p>[…who also worked as a prostitute and attended Bradford University</p></blockquote>
<p>…then that would have been perfectly fine.</p>
<p>The two instances of the word &#8220;also&#8221; also grate.  Faux pas most definitely intended.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.osirra.com/2010/05/carrying-over-a-who/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Curry and Rice with FREE Popdomas £6</title>
		<link>http://www.osirra.com/2010/03/curry-and-rice-with-free-popdomas-6/</link>
		<comments>http://www.osirra.com/2010/03/curry-and-rice-with-free-popdomas-6/#comments</comments>
		<pubDate>Mon, 29 Mar 2010 16:41:54 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.osirra.com/2010/03/curry-and-rice-with-free-popdomas-6/</guid>
		<description><![CDATA[Such was the title of a recent marketing email to a friend. Now it’s either part of a Latin declension (popdoma, popdomas, popdomat, popdomamus, popdomatis, popdomant) or a heinous typo. I favour the latter, as the Mediterraneans weren’t big curry fans back then. On a related note, I genuinely believe there’s money to be made [...]]]></description>
			<content:encoded><![CDATA[<p>Such was the title of a recent marketing email to a friend. Now it’s either part of a Latin declension (popdoma, popdomas, popdomat, popdomamus, popdomatis, popdomant) or a heinous typo. I favour the latter, as the Mediterraneans weren’t big curry fans back then.</p>
<p>On a related note, I genuinely believe there’s money to be made in the proofreading of takeaway and restaurant menus. High volume, low margin—but there’s certainly a market there to be tapped.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.osirra.com/2010/03/curry-and-rice-with-free-popdomas-6/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Natural History Museum&#8217;s em dash faux pas</title>
		<link>http://www.osirra.com/2010/03/the-natural-history-museums-em-dash-faux-pas/</link>
		<comments>http://www.osirra.com/2010/03/the-natural-history-museums-em-dash-faux-pas/#comments</comments>
		<pubDate>Wed, 10 Mar 2010 22:31:23 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[Grammar]]></category>
		<category><![CDATA[Rules]]></category>

		<guid isPermaLink="false">http://www.osirra.com/?p=373</guid>
		<description><![CDATA[The Natural History Museum has followed Expedia&#8217;s bad example in their use of the dash to indicate date ranges.  Remember, kids: en dash for ranges, unless the latter date is not yet fixed (e.g. for living people), in which case use an em dash.]]></description>
			<content:encoded><![CDATA[<p>The Natural History Museum has followed <a title="osirra blog: Expedia.co.uk and the errant em dash" href="http://www.osirra.com/2006/11/expedia-co-uk-and-the-errant-em-dash/">Expedia&#8217;s bad example</a> in their use of the dash to indicate date ranges.  Remember, kids: en dash for ranges, unless the latter date is not yet fixed (e.g. for living people), in which case use an em dash.</p>
<p><a href="http://www.osirra.com/wp-content/uploads/2010/03/photo.jpg"><img class="size-medium wp-image-374 alignnone" title="photo" src="http://www.osirra.com/wp-content/uploads/2010/03/photo-300x225.jpg" alt="Decode: 8 December 2009 — 11 April 2010" width="300" height="225" /></a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.osirra.com/2010/03/the-natural-history-museums-em-dash-faux-pas/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Expedia.co.uk and the errant em dash</title>
		<link>http://www.osirra.com/2010/03/expedia-co-uk-and-the-errant-em-dash-2/</link>
		<comments>http://www.osirra.com/2010/03/expedia-co-uk-and-the-errant-em-dash-2/#comments</comments>
		<pubDate>Wed, 10 Mar 2010 22:24:52 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[Grammar]]></category>

		<guid isPermaLink="false">http://www.osirra.com/?p=368</guid>
		<description><![CDATA[When you search for flights on expedia.co.uk and click search, you are presented with a holding screen, informing you that: Expedia.co.uk is searching for flights on selected travel dates: Mon 23/11/2009 — Fri 27/11/2009 (Obviously the dates in question are those pertinent to your requested jaunt rather than mine.) The em dash (—) between the [...]]]></description>
			<content:encoded><![CDATA[<p>When you search for flights on expedia.co.uk and click search, you  are presented with a holding screen, informing you that:</p>
<blockquote>
<p style="text-align: center;">Expedia.co.uk is searching for<br />
flights on selected  travel dates:<br />
Mon 23/11/2009 — Fri 27/11/2009</p>
</blockquote>
<p>(Obviously the dates in question are those pertinent to your  requested jaunt rather than mine.)</p>
<p>The <a title="Wikipedia: em  dash" href="http://en.wikipedia.org/wiki/Dash#Em_dash" target="_blank">em dash</a> (—) between the dates should be an <a title="Wikipedia: en dash" href="http://en.wikipedia.org/wiki/Dash#En_dash" target="_blank">en dash</a> (–), and there  shouldn’t be any spaces.</p>
<p>It’s only a tiny point, but on a screen that all flight-bookers will  see, they should really get it right.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.osirra.com/2010/03/expedia-co-uk-and-the-errant-em-dash-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>I Gotta Feeling.  So very wrong</title>
		<link>http://www.osirra.com/2010/03/i-gotta-feeling-so-very-wrong/</link>
		<comments>http://www.osirra.com/2010/03/i-gotta-feeling-so-very-wrong/#comments</comments>
		<pubDate>Sun, 07 Mar 2010 12:40:08 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[Rules]]></category>

		<guid isPermaLink="false">http://www.osirra.com/?p=363</guid>
		<description><![CDATA[I embrace the evolution of the English language.  But I think that its rules and regulations differ from one medium to another.  Certain contractions (e.g. OMG, FTW, WTF, gotta) are acceptable in instant messenger conversations and text messages, but shouldn&#8217;t be used in more formal forms of communication. But if you&#8217;re going to use such [...]]]></description>
			<content:encoded><![CDATA[<p>I embrace the evolution of the English language.  But I think that its rules and regulations differ from one medium to another.  Certain contractions (e.g. OMG, FTW, WTF, gotta) are acceptable in instant messenger conversations and text messages, but shouldn&#8217;t be used in more formal forms of communication.</p>
<p>But if you&#8217;re going to use such contractions, use them properly.  <em>Gotta</em> is a contraction of <em>got to</em>; it&#8217;s not a contraction of <em>got a</em>.  And so it should be used.</p>
<blockquote><p>&#8220;I gotta go to the toilet&#8221; is fine.</p>
<p>&#8220;I Gotta Feeling&#8221; is not, Black Eyed Peas.</p></blockquote>
<p>That said, it didn&#8217;t seem to bother Joe Public, as it was the biggest selling track out of the first one billion downloaded from iTunes.  And I bought it, in spite of my grammatical disappointment.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.osirra.com/2010/03/i-gotta-feeling-so-very-wrong/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Time separators</title>
		<link>http://www.osirra.com/2010/03/time-separators/</link>
		<comments>http://www.osirra.com/2010/03/time-separators/#comments</comments>
		<pubDate>Mon, 01 Mar 2010 12:10:48 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[Rules]]></category>

		<guid isPermaLink="false">http://www.osirra.com/?p=344</guid>
		<description><![CDATA[I use colons, as opposed to periods, to separate time units. Periods are the same as decimal points, which can cause confusion. Periods should be used after the number of seconds to indicate the decimals thereafter. The couple met at 9:30am. He went to bed at 11:45pm. Schumacher&#8217;s 1:34.236 was the best lap time of [...]]]></description>
			<content:encoded><![CDATA[<p>I use colons, as opposed to periods, to separate time units.  Periods are the same as decimal points, which can cause confusion.  Periods should be used after the number of seconds to indicate the decimals thereafter.</p>
<blockquote><p>The couple met at 9:30am.<br />
He went to bed at 11:45pm.<br />
Schumacher&#8217;s 1:34.236 was the best lap time of the practice session.<br />
He ran the marathon in 3:25:23.</p></blockquote>
<p>As well as avoiding confusion, the above style is somewhat quaint.<br />
Update: when working in business, the 24-hour clock should be used exclusively, with no separator between the hours and the minutes.  (Thanks to Paul Clarke for highlighting this clarification.)</p>
<blockquote><p>The meeting will take place at 1330 GMT (0830 EST).</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://www.osirra.com/2010/03/time-separators/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Proofreading: pedantry is everything</title>
		<link>http://www.osirra.com/2010/02/proofreading-pedantry-is-everything/</link>
		<comments>http://www.osirra.com/2010/02/proofreading-pedantry-is-everything/#comments</comments>
		<pubDate>Sat, 06 Feb 2010 09:54:11 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[Life]]></category>

		<guid isPermaLink="false">http://www.osirra.com/?p=293</guid>
		<description><![CDATA[I advertise this site through the likes of Google AdWords. Most of the interest generated is for the services that we offer. But occasionally, someone will email me out of the blue asking whether we&#8217;re recruiting, either on a permanent or freelance basis, and offering their own services. Given the services we offer, I expect [...]]]></description>
			<content:encoded><![CDATA[<p>I advertise this site through the likes of Google AdWords.  Most of the interest generated is for the services that we offer.  But occasionally, someone will email me out of the blue asking whether we&#8217;re recruiting, either on a permanent or freelance basis, and offering their own services.</p>
<p>Given the services we offer, I expect these latter emails to be flawless—if you can&#8217;t get your own, short emails right, then what confidence do I have that you can do the same for one of our clients?</p>
<p>I recently received such a request, consisting of six lines of content, together with a salutation and valediction.  Below were the errors I picked up:</p>
<ul>
<li>The <em>Dear Sir/Madam</em> did not come with a corresponding <em>Yours faithfully</em>.  Harsh in today&#8217;s less formal world, but a tradition that should be upheld, for the time being, at least.</li>
<li><em>Proofreader</em> was sometimes hyphenated, sometimes not.</li>
<li>The Oxford comma was used in one instance, but not in another.</li>
<li>The lady used quotation marks around words not warranting them, much like an annoying person might sign visually in a bar conversation.  E.g. &#8220;[you] would, naturally, take a &#8216;cut&#8217;&#8221;.</li>
<li>A spaced, single hyphen had been used instead of an em dash before a separated clause.</li>
</ul>
<p>I politely pointed out some of these issues to the lady, that she might be more successful in looking for other work.  She refuted many of them, the worst defence being that her keyboard didn&#8217;t do em dashes.  (Yes it does: ALT+0151.)</p>
<p>Now some of the issues I raised may sound pedantic.  But given the subject matter, pedantry is essential.  Our reputation is founded on attention to detail, picking up issues that our clients don&#8217;t spot but which their clients may smart at.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.osirra.com/2010/02/proofreading-pedantry-is-everything/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A single version of English</title>
		<link>http://www.osirra.com/2009/11/a-single-version-of-english/</link>
		<comments>http://www.osirra.com/2009/11/a-single-version-of-english/#comments</comments>
		<pubDate>Sat, 21 Nov 2009 22:22:53 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[Grammar]]></category>
		<category><![CDATA[Thoughts]]></category>

		<guid isPermaLink="false">http://www.osirra.com/?p=287</guid>
		<description><![CDATA[Wouldn&#8217;t it be wonderful if there was an internationally-recognised standard for written English? If people saw the word color (or indeed colour) and didn&#8217;t recoil. If there was a widely acknowledged view as to whether The meeting Thursday or The meeting on Thursday was acceptable. I&#8217;m not asking us to can our respective versions of [...]]]></description>
			<content:encoded><![CDATA[<p>Wouldn&#8217;t it be wonderful if there was an internationally-recognised standard for written English?  If people saw the word <em>color</em> (or indeed <em>colour</em>) and didn&#8217;t recoil.  If there was a widely acknowledged view as to whether <em>The meeting Thursday</em> or <em>The meeting on Thursday</em> was acceptable.</p>
<p>I&#8217;m not asking us to can our respective versions of English—British, American, Australian, Canadian etc.  I&#8217;m instead suggesting that a new version of English is created that would, over time, supersede our respective versions, taking the loveliness from each and consolidating it into a single set of rules that people can abide by in certain media, predominantly the web at first.</p>
<p>And I&#8217;m not suggesting that any one of our beautiful set of idiosyncrasies overrules those of the other countries&#8217;.  There are some beautiful American constructs; and some equally beautiful British ones.  I&#8217;m sure the same is true of the other variants, although I&#8217;m less familiar with these.</p>
<p>To achieve the goal, I&#8217;m proposing we first brainstorm the inconsistencies.  And then we bring together five leading literary luminaries representing  each of the English variants to agree on which version is preferable, leaving aside their local bias.</p>
<p>The whole process would strengthen the language and bring closer the English-speaking world.</p>
<p>Thoughts?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.osirra.com/2009/11/a-single-version-of-english/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Should of vs. should have</title>
		<link>http://www.osirra.com/2009/11/should-of-vs-should-have/</link>
		<comments>http://www.osirra.com/2009/11/should-of-vs-should-have/#comments</comments>
		<pubDate>Wed, 04 Nov 2009 22:39:30 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[Grammar]]></category>
		<category><![CDATA[Life]]></category>

		<guid isPermaLink="false">http://www.osirra.com/?p=279</guid>
		<description><![CDATA[I have a couple of well-educated ex-colleagues who shall remain nameless who, in the written form, have started using the phrase should of, in the following context: Mum should of gone to Iceland. I must stress that this is not the actual phrase they used.  They used more business-like phrases.  But you get the picture. [...]]]></description>
			<content:encoded><![CDATA[<p>I have a couple of well-educated ex-colleagues who shall remain nameless who, in the written form, have started using the phrase <em>should of</em>, in the following context:</p>
<blockquote><p>Mum should of gone to Iceland.</p></blockquote>
<p>I must stress that this is not the actual phrase they used.  They used more business-like phrases.  But you get the picture.</p>
<p>Speech has always influenced the development of written language.  But the world we now live in is made up of people whose English education is often, at best, questionable—people who, even if educated appropriately to suspect a mistake, have neither the time nor the inclination to search for the truth.  This means that mistakes like that above will become increasingly prevalent with time, which is a shame.</p>
<p>The correct construct is:</p>
<blockquote><p>Mum should have gone to Iceland.</p></blockquote>
<p>Or indeed:</p>
<blockquote><p>Mum really shouldn&#8217;t have gone to Iceland.  Especially now that they&#8217;ve fired Kerry Katona.</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://www.osirra.com/2009/11/should-of-vs-should-have/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>

