<?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>Kublog &#187; Stylebites</title>
	<atom:link href="http://www.adamkuban.com/kublog/category/language/stylebites/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.adamkuban.com/kublog</link>
	<description>my rest stop on the information superhighway</description>
	<lastBuildDate>Mon, 09 Aug 2010 04:00:17 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>adamkuban.com/stylebites now public</title>
		<link>http://www.adamkuban.com/kublog/2009/01/adamkubancomstylebites-now-public/</link>
		<comments>http://www.adamkuban.com/kublog/2009/01/adamkubancomstylebites-now-public/#comments</comments>
		<pubDate>Thu, 29 Jan 2009 14:30:23 +0000</pubDate>
		<dc:creator>Adam Kuban</dc:creator>
				<category><![CDATA[Copy-Editing]]></category>
		<category><![CDATA[Journalism]]></category>
		<category><![CDATA[Language]]></category>
		<category><![CDATA[Serious Eats]]></category>
		<category><![CDATA[Style and Grammar]]></category>
		<category><![CDATA[Stylebites]]></category>
		<category><![CDATA[blogging]]></category>
		<category><![CDATA[Style Bites]]></category>

		<guid isPermaLink="false">http://www.adamkuban.com/kublog/?p=964</guid>
		<description><![CDATA[For the past couple of weeks in Serious Eats Talk, I&#8217;ve been meddling with Talk topic titles, trying to help make them more precise and reflective of what&#8217;s being asked in the thread. In some cases, I truly think my meddling is helpful. For instance, &#8220;Need a butcher in Phoenix&#8221; is a better title than [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.adamkuban.com/stylebites"><img title="adamkuban-stylebites" class="noline" src="http://www.adamkuban.com/kublog/wp-content/uploads/2009/01/adamkuban-stylebites.jpg" alt="adamkuban-stylebites" width="500" height="293" /></a></p>
<p>For the past couple of weeks in <a href="http://www.seriouseats.com/talk">Serious Eats Talk</a>, I&#8217;ve been meddling with Talk topic titles, trying to help make them more precise and reflective of what&#8217;s being asked in the thread.</p>
<p>In some cases, I truly think my meddling is helpful. For instance, &#8220;Need a butcher in Phoenix&#8221; is a better title than &#8220;Need a butcher.&#8221;</p>
<p>Well, the Serious Eats community is sharp, and they&#8217;ve noticed. I&#8217;ve been called out a couple times now on it, the latest in <a href="http://www.seriouseats.com/talk/2009/01/winning-haiku-no-look-whos-talkin-last-week.html">this thread</a> that SE member <a href="http://www.seriouseats.com/user/profile/PerkyMac">PerkyMac</a> started early Tuesday morning.</p>
<p>I&#8217;ve been following the conversation and commenting there over the last two days and have realized that maybe a large part of my headline meddling had to do with some of the recent off-topicality in Talk. We&#8217;ve gotten more than a few emails in the last couple months about threads going off-topic and becoming too filled with chit chat. And now I&#8217;m wondering if my playing with Talk titles was a way to try to correct that and steer things in a more serious direction.</p>
<p>Anyway, I have more to say about it in <a href="http://www.seriouseats.com/talk/2009/01/winning-haiku-no-look-whos-talkin-last-week.html#259718">this comment</a> on that thread. What I&#8217;m blabbing about here is my <a href="http://www.adamkuban.com/stylebites"><strong>Style Bites</strong></a> site, which I&#8217;ve now taken out from behind its privacy wall.</p>
<p>SE member <a href="http://www.seriouseats.com/user/profile/dbcurrie">dbcurrie</a>, who works at a newspaper, brought up AP style in the abovementioned thread, and it reminded me that I had been keeping Style Bites to myself. I really love talking about copy-editing and blogging and writing for the web (which is also why that Talk topic has been so fun to participate in). And now that I&#8217;m sharing the Style Bites blog, I hope to do more of it on Kublog/Style Bites.<span id="more-964"></span></p>
<p>You may wonder if some of the stuff that goes on in SE Talk drives me batty as a copy editor. And I have to admit that, yes, yes, it does. When people don&#8217;t put spaces between sentences—or between a comma and the following word—it just burns my eyeballs to look at it. When people use five exclamation points where one will do. Or five question marks. Or ALL CAPS.</p>
<p>We&#8217;ve always corrected excessive punctuation in titles and have lowercased ALL CAPS, but I think I&#8217;ve gone overboard with setting Talk titles in <a href="http://en.wikipedia.org/wiki/Letter_case#Sentence_case_versus_title_case">title casing</a> and in changing them. But for the most part, I do try to leave the body of the Talk threads alone. I don&#8217;t expect that everyone has had the same copy-edit training that I have, so it&#8217;s sort of a live and let live thing. (Although if I do see obvious typos, I will fix them (&#8220;peal onions&#8221; to &#8220;pearl onions&#8221; in SE Talk is a recent example I can think of).</p>
<p>Anyway, for anyone not working for/with Serious Eats, Style Bites is more a behind-the-scenes look at what we do. For SE staff/contributors, it&#8217;s strongly suggested reading. And for other foodbloggers, it might be a helpful resource.</p>
<p>I&#8217;ll have to play around with the templates behind Style Bites to tweak some functionality, but I hope to add some more entries sooner rather than later.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.adamkuban.com/kublog/2009/01/adamkubancomstylebites-now-public/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Stylebites, 6/16/2008 &#8211; 7/01/2008</title>
		<link>http://www.adamkuban.com/kublog/2008/07/stylebites-6162008-7012008/</link>
		<comments>http://www.adamkuban.com/kublog/2008/07/stylebites-6162008-7012008/#comments</comments>
		<pubDate>Wed, 02 Jul 2008 04:30:00 +0000</pubDate>
		<dc:creator>Adam Kuban</dc:creator>
				<category><![CDATA[Stylebites]]></category>

		<guid isPermaLink="false">http://www.adamkuban.com/2008/07/stylebites-6162008-7012008/</guid>
		<description><![CDATA[STYLE MATTERS capitalization Watch your caps, folks. I&#8217;m seeing weird-ass shit that shouldn&#8217;t be capped. And I&#8217;m seeing things lowercased that should absolutely be capped. It&#8217;s driving me crazy because this is elementary school English. I&#8217;m not going to go over the basic rules of capitalization, because you learned that in third grade. Er, maybe [...]]]></description>
			<content:encoded><![CDATA[<p><b><font size="3">STYLE MATTERS</font></b></p>
<p><b>capitalization<br />
</b>Watch<br />
your caps, folks. I&#8217;m seeing weird-ass shit that shouldn&#8217;t be capped.<br />
And I&#8217;m seeing things lowercased that should absolutely be capped. It&#8217;s<br />
driving me crazy because this is elementary school English. I&#8217;m not<br />
going to go over the basic rules of capitalization, because you learned<br />
that in third grade. Er, maybe I will &#8230;</p>
<ul>
<li><b>Proper nouns (also called <i><a href="http://en.wikipedia.org/wiki/Proper_name" title="Proper name" target="_blank">proper names</a></i>):</b> Nouns representing unique entities (such as <i>London</i>, <i>Universe</i>, or <i>John</i>), as distinguished from &#8230;</li>
<li><b>Common nouns:</b> Nouns which describe a class of entities (such as <i>city</i>, <i>well</i>, or <i>person</i>).</li>
</ul>
<p><b><br /></b>Proper nouns are capitalized. Common nouns are not.</p>
<p><b>No:</b> <i>The best Hot Dogs in Chicago can be found at Hot Doug&#8217;s.</i><br /><b>Yes:</b> <i>The best hot dogs in Chicago can be found at Hot Doug&#8217;s.</i></p>
<p><b>No:</b> <i>Ed says he really likes the thai food at Won Dee Siam.</i><br />
<b>Yes:</b> <i>Ed says he really likes the Thai food at Won Dee Siam.</i></p>
<p><span id="more-11"></span><br />
<b>commas, with state and city names<br /></b>Please use commas after both the city name and the state name when namechecking a city/state in body copy.<br />
<b><br />No: </b><i>Washington D.C. hosts a respectable amount &#8230;</i><br /><b>Yes: </b><i>Washington, D.C., hosts a respectable amount &#8230;</i><br />
<b><br /></b><b>No:&nbsp;</b><i>Daniel Boulud got his start in Wichita Kansas as a line cook at Burger King.</i><br />
<b>No:&nbsp;</b><i>Daniel Boulud got his start in Wichita, Kansas as a line cook at Burger King.</i></p>
<p><b>Yes: </b><i>Daniel Boulud got his start in Wichita, Kansas, as a line cook at Burger King.</i></p>
<p><b></p>
<p></b><b>dates<br />
</b>Don&#8217;t use <a title="ordinals" href="http://en.wikipedia.org/wiki/Ordinal_number" target="_blank">ordinals</a> on dates.<br />
<b>No:</b> <i>The iPhone 3G comes out on July 11th.</i><br />
<b>Yes:</b> <i>The iPhone 3G comes out on July 11.</i><br />
<b></p>
<p>italics<br />
</b>PLEASE USE ITALICS for the following:</p>
<p>Titles of &#8230;</p>
<ul>
<li>newspapers</li>
<li>books</li>
<li>magazines</li>
<li>TV shows</li>
<li>movies</li>
<li>music albums</li>
<li>names of sea- and spacefaring vessels (You may laugh, but we have an instance <a title="here" href="http://www.seriouseats.com/required_eating/2008/07/in-videos-celebrating-the-4th-of-july-on-star-trek.html" target="_blank">here</a> )</li>
</ul>
<p>
LAY OFF THE ITALICS for trying to emphasize things in body copy. You can do that with the bolding schtick.</p>
<p><b><br />
quotation marks, in post titles and subheds</b><br /><span style="background-color: rgb(255, 255, 255);">DO NOT USE double quotes</span><span style="background-color: rgb(255, 255, 255);"> in headlines or post titles. USE SINGLE QUOTES.</span><br style="background-color: rgb(255, 255, 255);" /><br />
<span style="background-color: rgb(255, 255, 255);"><br />
[</span><i style="background-color: rgb(255, 255, 255);">This SB was previously covered in the 5/25/2008 and 6/1/2008 edition.</i><span style="background-color: rgb(255, 255, 255);">]</span><br style="background-color: rgb(255, 255, 255);" /><br />
<br /><b>No: </b><i>&#8220;Crazy Legs&#8221; Conti Eats a Hot Dog<br /></i><b>Yes: </b><i>&#8216;Crazy Legs&#8217; Conti Eats a Hot Dog</p>
<p></i><b>No: </b><i>Jersey &#8220;Food Court&#8221; Dispatch: Mitsuwa Marketplace<br /></i><b>Yes: </b><i>Jersey &#8216;Food Court&#8217; Dispatch: Mitsuwa Marketplace</p>
<p></i><b>No: </b><i>Australian Senate: Ramsay Fills TV with &#8220;Astounding Volume of Foul Language&#8221;<br /></i><b>Yes: </b><i>Australian Senate: Ramsay Fills TV with &#8216;Astounding Volume of Foul Language&#8217;</i></p>
<p>
<b>quotation marks, with commas and periods</b><br />
Commas and periods go <span style="background-color: rgb(255, 153, 0);">inside</span> the quotation marks. [<i>This SB was previously covered in the 6/1/2008 and 5/25/2008 editions.</i>]</p>
<p><i>&#8220;I eat like a pig,&#8221; Joey Chestnut said.</i> Not <i>&#8220;I eat like a pig&#8221;, Joey Chestnut said.</i></p>
<p><i>Joey Chestnut said, &#8220;I eat like a pig.&#8221;</i> Not <i>Joey Chestnut said, &#8220;I eat like a pig&#8221;.</i></p>
<p>
<b>serial commas<br /></b><i>I want those apples, oranges, and pears.<br />
I want mushrooms, onions, and sausage on my pizza.<br />
</i><br />
I want to see you all using the <a title="serial comma" href="http://en.wikipedia.org/wiki/Serial_comma" target="_blank">serial comma</a>. Your English teacher may have beaten into you that you drop the comma before the <i>and</i>. S/he wasn&#8217;t necessarily wrong. You can drop it or use it. I think it adds clarity to a sentence, and we should employ it.</p>
<p>
<b>tags<br />
</b>Use plurals. And make sure to capitalize proper nouns. <b>Ex.: </b><i>wedding cakes,</i> not <i>wedding cake</i>; <i>Japan,</i> not <i>japan.</i></p>
<p><b><font size="3"><br />WORDS TO WATCH</font></b></p>
<p><b>all-you-can-eat<br />
All-you-can-eat buffet</p>
<p>amid vs. amidst</b></p>
<p>Use <i>amid</i>. (Refrain from using longer words when shorter ones will do. Plus, it&#8217;s pretentious.)</p>
<p><b><br />
among vs. amongst</b><br />
Use <i>among.</i> (Refrain from using longer words when shorter ones will do. Plus, it&#8217;s pretentious.)</p>
<p><b>barbecue<br />
</b>Not <i>BBQ.</i> Not <i>bar-be-que.</i> Not <i>bar-b-que.</i><b> It is <span style="background-color: rgb(255, 153, 0);">always</span> <i>barbecue, </i></b>unless it is in the context of a restaurant name, in which case we should honor that spelling.<b></p>
<p>British spellings<br />
</b>Avoid. I don&#8217;t want to see <i>colour, flavour, favourite, </i><i>defence </i>or any other British spellings<i>&#8211;</i><a title="Unless you're British and have special permission." href="http://www.seriouseats.com/required_eating/2007/02/in-defence-of-british-food.html" target="_blank">unless you&#8217;re British and have special permission.</a> </p>
<p><b>chocolaty<br /></b>not <i>chocolately</i> or <i>chocolate-y</i></p>
<p><b>fancy-pants<br />
</b>Not <i>fancypants.</i></p>
<p><b><br />
</b><b>house-made<br />
</b>Not <i>housemade.</i><br />
<b><br />
&#8220;just [BLANK] enough&#8221;<br />
</b><i>Just salty enough, just sweet enough, just chewy enough, just crisp enough.</p>
<p></i>Enough! We&#8217;re overusing this phrase. Please find a way around this<br />
locution. It&#8217;s fine every once in a while, but it begins to lose its<br />
meaning after several iterations.<br />
<b><br />
non-<br />
</b>Most <i>non </i>words are closed up: <i>nonstop, nonrefundable.</i> Your inclination may be to hyphenate these. Fight that inclination. Check this out: <a title="http://www.merriam-webster.com/dictionary/non" href="http://www.merriam-webster.com/dictionary/non" target="_blank">http://www.merriam-webster.com<wbr>/dictionary/non</a> </p>
<p><b><br />
pre-<br />
</b>Most words beginning with the prefix <i>pre </i>are closed up: <i>prebake, prewash, precut.</i> Amazing, huh? Not really: <a title="http://www.merriam-webster.com/dictionary/pre" href="http://www.merriam-webster.com/dictionary/pre" target="_blank">http://www.merriam-webster.com<wbr>/dictionary/pre</a> <b></p>
<p></b><b>that</b></p>
<p>In many instances you can remove <i>that</i> from a sentence without changing the meaning <b>Ex.:</b> <i>He said <strike>that</strike> he wanted to go to Di Fara.</i> <i>She said <strike>that</strike> it was OK to eat the potato salad.</i></p>
<p><b>un-<br />
</b>Most words beginning with the prefix <i>un </i>are closed up: <i>unaffordable, uninspired, unapproved.<br />
</i>However: <i>un-American, un-English, un-European. </i>When used with a <a title="proper noun" href="http://en.wikipedia.org/wiki/Proper_name" target="_blank">proper noun</a>, they form hyphenated compounds.&nbsp;<a title="http://www.merriam-webster.com/dictionary/un-" href="http://www.merriam-webster.com/dictionary/un-" target="_blank">http://www.merriam-webster.com<wbr>/dictionary/un-</a> <b></p>
<p></b><br />
<b>very</b><br />
One of the first things you learn in Reporting 101 is that nine times out of ten, you can take the ax to <i>very</i><br />
without changing your sentence one bit. It&#8217;s a so-called intensifier<br />
that gets in the way of strong, direct writing. Often used by lazy<br />
writers. What&#8217;s the differencebetween  <i>The cake was very good </i>and <i>The cake was good</i>? Wasted keystrokes.</p>
<p><b><font size="3">PROTOCOL/SITE OPS</font></p>
<p></b><b>don&#8217;t space out</b><br />Watch your use of spaces within HTML coding.</p>
<p><b>No:</b> Eater &lt;a href=&#8221;URL&#8221;&gt;reports that<span style="background-color: rgb(0, 255, 0);"> </span>&lt;/a&gt;David Chang scratched his balls today.<br /><b>Yes:</b> Eater &lt;a href=&#8221;URL&#8221;&gt;reports that&lt;/a&gt; David Chang scratched his balls today.</p>
<p>In the case above, the errant space will yield a sloppy-looking link, leaving a little bit of underlining between <i>that </i>and <i>David:</p>
<p></i></p>
<div style="margin-left: 40px;">Eater <u style="color: rgb(0, 0, 255);">reports that </u>David Chang scratched his balls today.
</div>
<p>
I often see this with &lt;em&gt; and &lt;strong&gt; coding, too.<br />
Admittedly, it&#8217;s less critical in those instances, but you might was<br />
well watch your HTML there, too, as laziness in one area begets<br />
laziness in others.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.adamkuban.com/kublog/2008/07/stylebites-6162008-7012008/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Stylebites for the week of February 18</title>
		<link>http://www.adamkuban.com/kublog/2008/02/stylebites-for-the-week-of-february-18/</link>
		<comments>http://www.adamkuban.com/kublog/2008/02/stylebites-for-the-week-of-february-18/#comments</comments>
		<pubDate>Tue, 26 Feb 2008 04:16:55 +0000</pubDate>
		<dc:creator>Adam Kuban</dc:creator>
				<category><![CDATA[Stylebites]]></category>

		<guid isPermaLink="false">http://www.adamkuban.com/2008/02/stylebites-for-the-week-of-february-18/</guid>
		<description><![CDATA[Each week, I keep track of minor style points on Serious Eats and issue an end-of-week email to staff and contributors of things to watch out for. Call it a &#8220;post postmortem.&#8221; (Get it, &#8220;post&#8221; as in &#8220;blog post&#8221;? Groan.) I&#8217;m going to post them here on my personal blog for anyone (God help them) [...]]]></description>
			<content:encoded><![CDATA[<p>Each week, I keep track of minor style points on <a href="http://www.seriouseats.com/">Serious Eats</a> and issue an end-of-week email to staff and contributors of things to watch out for. Call it a &#8220;post postmortem.&#8221; (Get it, &#8220;post&#8221; as in &#8220;blog post&#8221;? <em>Groan.</em>) I&#8217;m going to post them here on my personal blog for anyone (God help them) looking for copy-editing advice as it relates to blogging. After the jump, the most recent installment of Stylebites.</p>
<p><span id="more-8"></span></p>
<p><strong>DATES</strong><br />
Spell out names of months. If citing an exact date with year, commas come after the date and the year (unless, of course, the date comes at the end of the sentence). Do not tack on an ordinal ending to the date (e.g., &#8220;st,&#8221; &#8220;nd,&#8221; &#8220;rd,&#8221; &#8220;th&#8221;).</p>
]]></content:encoded>
			<wfw:commentRss>http://www.adamkuban.com/kublog/2008/02/stylebites-for-the-week-of-february-18/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
