<?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>Plain Text &#187; Capitalisation</title>
	<atom:link href="http://www.plain-text.co.uk/tag/capitalisation/feed" rel="self" type="application/rss+xml" />
	<link>http://www.plain-text.co.uk</link>
	<description>Copywriting that means business</description>
	<lastBuildDate>Thu, 12 Jan 2012 17:20:22 +0000</lastBuildDate>
	
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Issue 9, November 2003</title>
		<link>http://www.plain-text.co.uk/issue-9-november-2003</link>
		<comments>http://www.plain-text.co.uk/issue-9-november-2003#comments</comments>
		<pubDate>Sun, 30 Nov 2003 22:27:24 +0000</pubDate>
		<dc:creator>timadmin</dc:creator>
				<category><![CDATA[Plain Text Gazette]]></category>
		<category><![CDATA[Capitalisation]]></category>

		<guid isPermaLink="false">http://www.plain-text.co.uk/wp_cms/?p=237</guid>
		<description><![CDATA[================================================
THE PLAIN TEXT GAZETTE &#8211; Issue 9, November 2003
================================================
Contents
&#8212;&#8212;&#8211;
* Editorial
* why oh Why Oh why can&#8217;t we get Capitalisation Right?
* Words We Hate: the list that could just go on for ever
Editorial
&#8212;&#8212;&#8212;
Welcome to the pre-festive season Plain Text Gazette. This time, we have *good news* for subscribers whose daily routine involves a forlorn search of [...]]]></description>
			<content:encoded><![CDATA[<p>================================================<br />
THE PLAIN TEXT GAZETTE &#8211; Issue 9, November 2003<br />
================================================</p>
<p>Contents<br />
&#8212;&#8212;&#8211;</p>
<p>* Editorial<br />
* why oh Why Oh why can&#8217;t we get Capitalisation Right?<br />
* Words We Hate: the list that could just go on for ever</p>
<p>Editorial<br />
&#8212;&#8212;&#8212;</p>
<p>Welcome to the pre-festive season Plain Text Gazette. This time, we have *good news* for subscribers whose daily routine involves a forlorn search of their in-tray for the printed &#8216;A-Z of Plain Text&#8217; we once promised to send you. At long last, it is printed. One free copy is reserved for each Gazette subscriber, so if you would like a rather attractive 36-page guide to best practice in business writing, please email us at enquiries@plain-text.co.uk with your name and address and we&#8217;ll send it out forthwith.</p>
<p>In this issue, we&#8217;re going to rant about capitalisation. It may not bother you, but it sure as hell bothers us. We&#8217;ll tell you why. And then we&#8217;ve got some more hated words to pillory.</p>
<p>Before either of these things, though, we thought the<a id="fog" name="fog"></a> &#8216;Fog Index&#8217; (which we&#8217;ve only just discovered) was worth a mention. Many Gazette subscribers are likely to be aware of this calculation, devised by Robert Gunning, author of &#8216;The Technique of Clear Writing&#8217;.</p>
<p>The Fog Index assesses how easy copy is to understand, using wordcount, the number of sentences, and the percentage of long words. We won&#8217;t detail the formula here, because we hate numbers and typing &#8216;fog index&#8217; into Google will lead you to many sites on the subject. The view on these sites seems to be that a score of anything above 14 is &#8216;difficult&#8217;. So broadsheet newspapers come in at around 14; Time magazine scores 12; and the Reader&#8217;s Digest (a prestigious Plain Text client) hits 8. One website says: &#8220;If you have a Fog Index of more than 12, you run a serious risk of not being understood &#8212; or even read&#8221;.</p>
<p>We&#8217;re pleased to announce that a couple of samples of our own website copy came in at around 10, which seems about right for copy that is intended to be readily comprehensible without &#8216;talking down&#8217; to business readers.</p>
<p>But oh what fun we had applying the Fog Index to some other business copy! A random press release from a major technology company hit 18, not far off the awesome 22.5 achieved by <a href="http://www.plain-text.co.uk/the-plain-text-gazette-issue-1-september-2001#press">our own fake press release from &#8216;Prolix&#8217;</a>.</p>
<p>Most entertaining of all, the UK government communication service&#8217;s description of itself also scores an incomprehensible 18.</p>
<p>Time for a &#8216;Fog Index Hall of Fame&#8217; on our website?</p>
<p>Enjoy this issue, and don&#8217;t forget to ask for your free copy of the &#8216;A-Z&#8217;.</p>
<p>Keep it plain,</p>
<p>The Editors</p>
<p>why oh Why Oh why can&#8217;t we get Capitalisation Right?<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;-</p>
<p>If I had a penny for every inappropriate capital letter I&#8217;ve edited, I&#8217;d be writing this newsletter from the tastefully appointed cabin of my 60-foot yacht. Admittedly, not everyone cares about capitals as much as writers do. We find all that pressing of the &#8217;shift&#8217; key tiring. But there are many occasions when the misuse of capitals makes text look silly.</p>
<p>The Economist Style Guide suggests that &#8220;the general rule is to dignify with capital letters organisations and institutions, but not people&#8221;. But it also quotes Emerson, reminding us that &#8220;a foolish consistency is the hobgoblin of little minds&#8221;.</p>
<p>So there&#8217;s no hard-and-fast rule book for capitalisation; but we have strong views on a few areas where a bit of consistency isn&#8217;t at all foolish.</p>
<p>1. The Extremely Arresting Powerpoint Slide Title</p>
<p>&#8216;How Our New Services Can Help You!&#8217; If you spoke like this, you&#8217;d sound like a Dalek. So *why* does initial letter capitalisation crop up so much in promotional materials and presentations? I guess it&#8217;s to do with trying to make words stand out. The Plain Text solution is predictable and simple: if the title isn&#8217;t interesting enough, capital letters won&#8217;t save it.</p>
<p>2. Very Important People and Departments</p>
<p>&#8216;Sales Manager John Smith and Marketing Director Jane Doe gave a presentation to the Board&#8217;. Even the pope gets lower case in correct usage. What did the sales manager do to deserve his caps? And why the big &#8216;B&#8217; on &#8216;board&#8217;? In both cases, the capital letters are for the glorification of individuals and are unnecessary.</p>
<p>3. Markets and concepts</p>
<p>&#8216;The market for Personal Information Managers (PIMs) has grown rapidly amongst Investment Banking professionals&#8217;. By all means use the TLA (once it&#8217;s been explained) to describe this deadly ten-syllable market. But there&#8217;s no need in this sentence to capitalise the market itself; nor the concept of investment banking. Otherwise the text risks becoming an indecipherable forest of different-sized letters. Which leads us neatly to&#8230;</p>
<p>4. Daft ComPany and ProDuct NameS</p>
<p>&#8216;ProDuct&#8217;. Geddit? We&#8217;re a lobbying group for drains! Right. Just like PowerPoint is something that helps you to point powerfully. We&#8217;re in the realm of personal preference here, because it is clear that random capitalisation is a good way to make your company or product more prominent. From DreamWorks to QinetiQ, weirdly capitalised names stand out on the page. All Plain Text would ask is: *please* find another way to do it. Those random capitals make us poor writers wince.</p>
<p>Words We Hate: the list that could just go on for ever<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;<br />
Vision, n (and shockingly v); meaning: &#8216;a pleasing imaginative<br />
- &#8211; - &#8211; plan for, or anticipation of, future events&#8217;.</p>
<p>The phrase &#8216;Our vision&#8217; is inevitably followed by a seemingly random combination of &#8216;usual suspect&#8217; positive words and phrases: &#8216;empower&#8217;, &#8216;achieve&#8217;, &#8216;best-in-class&#8217;. I could go on. But is a &#8216;vision&#8217; really necessary? And how does it really differ from a &#8216;mission&#8217;? (We&#8217;ll deal with that word one day). Corporate visions should be honest. If Plain Text had one, it would be: &#8220;We&#8217;d like a world where all businesses write well. But not in our lifetimes, please. We have bills to pay.&#8221;</p>
<p>Workflow, n; meaning: dunno.<br />
- &#8211; - -</p>
<p>And that&#8217;s the problem with &#8216;workflow&#8217;. It *probably* means &#8216;an interconnected series of professional activities largely facilitated by technology&#8217;; and as such, is pretty good shorthand. &#8216;Workflow&#8217; has two big problems, though: its definition is somewhat nebulous and difficult to grasp; and not everyone seems to agree precisely what it means. A word as slippery and, let&#8217;s face it, as ghastly as this should be avoided.</p>
<p>Architect, v; meaning: &#8216;to design software&#8217;.<br />
- &#8211; - &#8211; -</p>
<p>I have friends who are architects. But do they &#8216;architect&#8217; their buildings? Of course not. So why does the software industry need it as a verb? I suspect that the hairy-chested yet intellectual world of technology feels that &#8216;design&#8217; is just a little bit too namby-pamby and &#8216;build&#8217; a little too blue-collar. We say that you can &#8216;architect&#8217; something about as much as you can &#8216;dentist&#8217; or &#8216;lawyer&#8217; something. Time to think of another word. How about &#8216;Make&#8217;?</p>
<p>That&#8217;s about it for this issue. Before we forget, though: check out Whatbrandareyou.com (a publicity wheeze for a UK ad agency) whose spoof company name generator has generated amusement, website hits and column inches in equal measure.</p>
<p>Paul &amp; Paul</p>
<p>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;-oOo&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;-</p>
<p>© Plain Text Ltd 2003 all rights reserved</p>
]]></content:encoded>
			<wfw:commentRss>http://www.plain-text.co.uk/issue-9-november-2003/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

