<?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>CommaTrauma &#187; Featured</title>
	<atom:link href="http://www.commatrauma.com/category/featured/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.commatrauma.com</link>
	<description>Every writer needs a good editor</description>
	<lastBuildDate>Thu, 31 Dec 2009 00:34:23 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>General Help with Chicago Footnotes</title>
		<link>http://www.commatrauma.com/2007/06/general-help-with-chicago-footnotes/</link>
		<comments>http://www.commatrauma.com/2007/06/general-help-with-chicago-footnotes/#comments</comments>
		<pubDate>Thu, 07 Jun 2007 04:39:25 +0000</pubDate>
		<dc:creator>Jenn</dc:creator>
				<category><![CDATA[Chicago]]></category>
		<category><![CDATA[Featured]]></category>

		<guid isPermaLink="false">http://www.commatrauma.com/2007/06/06/general-help-with-chicago-footnotes/</guid>
		<description><![CDATA[Simple answers on how to write a paper with footnotes in Chicago's 15th style. Includes brief discussions on how I reached my editorial decisions as well as a few brief grammar tips.]]></description>
			<content:encoded><![CDATA[<p><img class="size-full wp-image-79 alignright" title="Chicago Style 15th Edition" src="http://www.commatrauma.com/wp-content/uploads/2009/10/Chicago-15ed-temp.png" alt="Chicago Style 15th Edition" width="64" height="64" />Okay, since I have to write this stuff down anyway, I thought I&#8217;d include it here for easy reference. The paper I&#8217;m editing began with the following:</p>
<p><em>EDITOR: I guess this is a disclaimer. This is my first time working with Chicago-style footnotes—really the first for footnotes. I did my best, but there may be a lot of problems and errors that I created.</em></p>
<p>And it made me smile. I don&#8217;t know many people who do feel comfortable with Chicago citation styles (and those who do feel comfortable with it have considerable industry experience). It&#8217;s definitely confusing at the beginning. Even as an editor, I am still chained to my Chicago—but I&#8217;ve gotten pretty good at figuring out where to look.</p>
<p>So, while this is definitely tailored to the decisions I&#8217;m making for this one particular paper, here&#8217;s a sample Chicago-style style sheet. I&#8217;ll also include my thoughts, when pertinent.<span id="more-7"></span></p>
<p><em><strong>1. Choosing between (a) the notes and bibliography option or (b) the author-date option.</strong></em><br />
One of the nice things about Chicago is its flexibility (see 16.7). My paper&#8217;s publisher dictates that all source information should be cited parenthetically, (Last Name, Year of Publication, p#) as listed in the author-date system. However, the publisher also dictates that the sources should be listed in a &#8220;bibliography&#8221; at the end of the volume. Then the author has entitled the citations &#8220;For reference and further study,&#8221; pointing to an author-date style. Ultimately, I think I&#8217;m going to use the author-date style within the text and the bibliographic style for the reference list. I chose this for three reasons: (a) what the author has compiled most represents a &#8220;full bibliography&#8221; as mentioned in Chicago 16.74 and 75 because it includes additional relevant works, (b) in the author&#8217;s field of study—religious texts—the dates are much less important than in other fields, and (c) the list was already in the bibliography format—why make it more complicated than it has to be?</p>
<p><strong><em>2. Do works mentioned parenthetically need to be fully referenced in the bibliography?</em></strong><br />
Yes. Let&#8217;s make things easier for the truly interested readers and give them all the information they will need.</p>
<p><strong><em>3. What to do with citations within notes?</em></strong><br />
When any work is cited within the notes, it will be given the same citation as in the text (name date, pp) and then will be fully referenced in the bibliography.</p>
<p><strong><em>4. What to do with multiple sets of parentheses?</em></strong><br />
Chicago 6.103 says to avoid having back-to-back parentheses. However, the in-text citation format for scriptural references is enclosed in parentheses. So what do do with a situation like the following?</p>
<p>(see Heb. 13:8; Gen. 25:19–23)(Draper and Parry 1999, 122)</p>
<p>I haven&#8217;t decided what to do with this. I&#8217;ll post more when I figure it out.</p>
<p><strong>Update: </strong>After a week&#8217;s worth of deliberation, I can&#8217;t find any definite back-up in Chicago. Sorry. For what it&#8217;s worth, here&#8217;s what I found. In 15:41 I did find two sets of parentheses together:</p>
<p><em> anno mundi</em> (in the year of the world) (not to be confused with <em>ante meridiem</em>; see 15.44).</p>
<p>In 15.44, it has a case where two parentheses could have been used, but where one set was changed to square brackets:</p>
<p><em> meridies </em>(noon [rarely used]).</p>
<p>Note that in the first example, the parentheticals served two different and distinct purposes, one to define and another to clarify. In the second example, both parenthetical references were of equal weight, both giving additional descriptive information about the term. I think this is where it is significant. (Also, did you notice how my examples are not at all related to the parentheses question? This section is just where I happened to find examples. I figured if I found examples of use in Chicago, then I could apply those same principles to the section.)</p>
<p>At any rate, I&#8217;ve come to the format that I like best. I&#8217;m sticking with:</p>
<p>(Draper and Parry 1999, 122; see Heb. 13:8; Gen. 25:19–23).</p>
<p><strong><em>5. What to do with spaces around the slashes in the manuscript? </em></strong><br />
In Chicago 6.112 it says that normally there are no spaces between the options and the slash—except where one or more of the terms being compared by the slash is an open compound, then use a thin space around the slash. However, since the manuscript (MS) has many instances where it compares both single words and phrases, I think I will leave out the space around the slash. It&#8217;s better to be consistent and never use spaces around the slash rather than going back and forth. As long as it&#8217;s consistent, the reader will understand what is being compared because of the repetition.</p>
<p><strong><em>6. Standardizing capitalization</em></strong><br />
The MS is seriously lacking consistency in capitalization. Here&#8217;s my thoughts:</p>
<ul>
<li><em>Church/church: </em>Chicago 8.106 says that when used alone to denote organized Christianity as an institution, <em>the church</em> is usually lowercase. However, when used as a short-hand to represent the Church of Jesus Christ of Latter-day Saints, <em>the Church</em> is what is recommended on <a title="LDS Newsroom – Style Guide" href="http://www.lds.org/ldsnewsroom/v/index.jsp?vgnextoid=ca07ae4af9c7e010VgnVCM1000004e94610aRCRD">lds.org</a> and, therefore, is what will be used. The majority of capital churches here will be changed to lowercase.</li>
<li><em>Saints/saints: </em>Same idea as above. Lowercase <em>saints</em> when referring to early Christian church members and uppercase when referring to members of the Church of Jesus Christ of Latter-day Saints. (This fits with Chicago 8.100 and the &#8220;spirit&#8221; of 8.106).</li>
<li>Quorum of the Twelve</li>
<li>Revelation (I&#8217;ve never realized—in all my 24 years—that it didn&#8217;t have an <em>s</em>. Seriously&#8230;)</li>
<li>Jewish high priest: no caps on the title b/c it isn&#8217;t a specific person.</li>
<li>celestial kingdom: the Church refers to it in lowercase</li>
<li>home base with a space (Even though I think it should be one word. But I tend to like closed word forms. Not in an Orwellian goodspeak way, though.)</li>
<li>Christlike (no hyphen)</li>
<li>Mount (capitalized and spelled out; see 15.32)</li>
</ul>
<p><em><strong>7. Citing a note from another work</strong></em><br />
The abbreviation for <em>notes </em>is <em>n</em> (plural <em>nn</em>). So, for the author-date style, Chicago 16.109 shows that it should be (Author date, p#n#) So, for example, it would be (Magie 1959, 43n50). In 16.43, the bibliographical shortened note style shows it as (Author, Title, p# n. #), which would look like (Magie, <em>Roman Rule</em>, 43, n. 50). However, in 17.140 (the more traditional style) shows it as (Magie, Roman Rule, 43 n. 50). So 17.140 is the rule I&#8217;ll go with.</p>
<p><em><strong>8. Letters representing rhyme schemes or stanzas in poetry</strong></em><br />
Should not be separated by commas and should be italicized (<em>aabbccbbaa</em>).</p>
<p><em><strong>9. Collective nouns: Subject-verb agreement</strong></em><br />
I, personally, think that it should be &#8220;the group was&#8221; not &#8220;the group were&#8221;. However, the author is referring to the group as a collection of individuals; therefore, Webster&#8217;s English Usage dictionary dictates that the plural verb should be used. It doesn&#8217;t sound quite right to me, but it does make the rest of the paragraph easier to deal with.</p>
<p><em><strong>10. What to do with scriptural verse numbers when quoting blocks of scripture?</strong></em><br />
Chicago 6.127 and 28 give the best rendering of what to do, I think. Since the scriptures are to be shown as, essentially, vertical lists in a paragraph style. So it would be correct to render them how they appear in most church texts. Also, since the formatting requires that scripture verses be single-spaced, I added the indentation to the verses required by 6.128 and matching the Church&#8217;s style.</p>
<p><em><strong>11. Dates, dates, dates&#8230;</strong></em><br />
In Chicago 9.38, it tells us what to do about BC/AD, BCE/CE, etc. (It&#8217;s a matter of house and personal preference regarding the abbreviations used and whether or not to use small caps and periods—it&#8217;s all perfectly acceptable to them.) However, it is important to note that the Latin forms precede the year, where everything else comes after it. (For example, &#8220;Even though my brothers act like I was born in 500 BC, I was actually born in AD 1983.&#8221;)</p>
<p><em><strong>12. Chapters as chapters (pages as pages, etc.)</strong></em><br />
When a chapter, page number, volumes, etc., of a book is being discussed, *always* use a number. Also you can lowercase the word &#8220;chapter&#8221; or &#8220;page.&#8221; (It&#8217;s always &#8220;In chapter 2&#8243; not &#8220;In Chapter Two.&#8221;)</p>
<p><em><strong>13. What to do with the &#8220;See&#8221; and &#8220;See also&#8221; notes&#8230;</strong></em><br />
Should they be in the notes or included parenthetically in the text? It goes back-and-forth in the manuscript&#8230;. To be consistent, they should be all one way or all the other. I prefer to clean up the text by taking them out—it adds several more footnotes, but the manuscript will read cleaner, in my opinion.</p>
<p><em><strong>14. Lines before block quotes?</strong></em><br />
Chicago 11.11 says that  this question is usually decided by the publisher, so I&#8217;m leaving the text as it is. Easy.</p>
<p><em><strong>15. Writing out fractions</strong></em><br />
Chicago 5.92 dictates that the fraction retains the <em>s</em> when it is used as a phrasal adjective (two-thirds majority). It is also hyphenated (no en- or em-dash).</p>
]]></content:encoded>
			<wfw:commentRss>http://www.commatrauma.com/2007/06/general-help-with-chicago-footnotes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Errors and Elbows</title>
		<link>http://www.commatrauma.com/2006/12/hello-world/</link>
		<comments>http://www.commatrauma.com/2006/12/hello-world/#comments</comments>
		<pubDate>Tue, 05 Dec 2006 08:35:24 +0000</pubDate>
		<dc:creator>Jenn</dc:creator>
				<category><![CDATA[Featured]]></category>
		<category><![CDATA[Oops!]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[Really, the credit for this blog should go directly to the folks at Fiddler&#8217;s Elbow. Let me explain. A few weeks ago my coworkers and I went to Fiddler&#8217;s Elbow on our lunch break. As we drove into the back parking lot, I quickly became irritated by a row of crimson banners supporting the University [...]]]></description>
			<content:encoded><![CDATA[<p>Really, the credit for this blog should go directly to the folks at <a title="Fiddler's Elbow" target="_blank" href="http://fiddlerselbowslc.com/">Fiddler&#8217;s Elbow</a>.</p>
<p>Let me explain. A few weeks ago my coworkers and I went to Fiddler&#8217;s Elbow on our lunch break. As we drove into the back parking lot, I quickly became irritated by a row of crimson banners supporting the <a title="Boo!" target="_blank" href="http://www.utah.edu/">University of Utah</a>. And, no, this was not because I&#8217;m a huge backer of rival <a title="Yay!" href="http://www.byu.edu/">Brigham Young University</a>. No, what really bothered me was the content of several of the banners.</p>
<p>They read: &#8220;Go Ute&#8217;s.&#8221;</p>
<p>Go Ute&#8217;s? Go U-T-E-<em>apostrophe</em>-S?! There&#8217;s no apostrophe in a plural! How could any decent person (or group of people, for that matter) sleep at night after committing—in 200 point font—a <em>huge and glaring error in punctuation?!</em> Why didn&#8217;t anyone—the designer, editor, or printer—catch this before it was plastered all over the side of a completely innocent building? What kind of place was this?</p>
<p>I&#8217;ll admit it. I couldn&#8217;t think of anything else during lunch. When we went out into the parking lot, I went out of my way and looked at the sign yet again. Yep—still wrong. At this point, I could no longer suffer in silence and began venting my surprise to my coworkers. Shortly after my coworkers&#8217; eyes glazed over, I realized that perhaps there was a better forum for my frustration.</p>
<p>And thus, CommaTrauma was born.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.commatrauma.com/2006/12/hello-world/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
