<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: &#8220;Bylaws&#8221; or &#8220;By-laws&#8221;?</title>
	<atom:link href="http://www.adamsdrafting.com/2008/02/23/bylaws/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.adamsdrafting.com/2008/02/23/bylaws/</link>
	<description></description>
	<lastBuildDate>Thu, 18 Mar 2010 12:12:39 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Peter Gulia</title>
		<link>http://www.adamsdrafting.com/2008/02/23/bylaws/comment-page-1/#comment-43702</link>
		<dc:creator>Peter Gulia</dc:creator>
		<pubDate>Mon, 25 Feb 2008 18:14:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2008/02/23/bylaws/#comment-43702</guid>
		<description>Here’s a style rule that I often apply to resolve a choice of spellings.  If the writing uses a word in the same sense that the relevant statute uses it, spell it the way the statute does.

For example, in a writing that refers to an SEC-registered investment adviser, I spell it “adviser” (not “advisor”) because that’s how the U.S. statute spells it.  

Using a rule of this kind sometimes results in a spelling that’s now out of favor.  But there’s a little value in falling in with the statute.  And if a writing includes goes back and forth between original text and quotations, using one spelling might avoid an unnecessary distraction.</description>
		<content:encoded><![CDATA[<p>Here’s a style rule that I often apply to resolve a choice of spellings.  If the writing uses a word in the same sense that the relevant statute uses it, spell it the way the statute does.</p>
<p>For example, in a writing that refers to an SEC-registered investment adviser, I spell it “adviser” (not “advisor”) because that’s how the U.S. statute spells it.  </p>
<p>Using a rule of this kind sometimes results in a spelling that’s now out of favor.  But there’s a little value in falling in with the statute.  And if a writing includes goes back and forth between original text and quotations, using one spelling might avoid an unnecessary distraction.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Adams</title>
		<link>http://www.adamsdrafting.com/2008/02/23/bylaws/comment-page-1/#comment-43693</link>
		<dc:creator>Ken Adams</dc:creator>
		<pubDate>Mon, 25 Feb 2008 15:34:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2008/02/23/bylaws/#comment-43693</guid>
		<description>Steve: You make an interesting point that requires two answers.

First, as a general matter don&#039;t capitalize textual references to &lt;em&gt;bylaws&lt;/em&gt;—they&#039;re simply a kind of document, not a title. See &lt;em&gt;MSCD&lt;/em&gt; 13.31.

Second, if you were stating &lt;em&gt;by-laws&lt;/em&gt; (with a hyphen) in a title, according to the &lt;em&gt;Chicago Manual of Style&lt;/em&gt; you shouldn&#039;t capitalize the &lt;em&gt;l&lt;/em&gt; in &lt;em&gt;laws&lt;/em&gt;. See &lt;em&gt;CMOS&lt;/em&gt; 8.168–170. For one thing, the &lt;em&gt;by&lt;/em&gt; is a prefix that couldn&#039;t stand by itself as a word. But more to the point, I wouldn&#039;t use the hyphen.

Ken</description>
		<content:encoded><![CDATA[<p>Steve: You make an interesting point that requires two answers.</p>
<p>First, as a general matter don&#8217;t capitalize textual references to <em>bylaws</em>—they&#8217;re simply a kind of document, not a title. See <em>MSCD</em> 13.31.</p>
<p>Second, if you were stating <em>by-laws</em> (with a hyphen) in a title, according to the <em>Chicago Manual of Style</em> you shouldn&#8217;t capitalize the <em>l</em> in <em>laws</em>. See <em>CMOS</em> 8.168–170. For one thing, the <em>by</em> is a prefix that couldn&#8217;t stand by itself as a word. But more to the point, I wouldn&#8217;t use the hyphen.</p>
<p>Ken</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: steven pappas</title>
		<link>http://www.adamsdrafting.com/2008/02/23/bylaws/comment-page-1/#comment-43692</link>
		<dc:creator>steven pappas</dc:creator>
		<pubDate>Mon, 25 Feb 2008 14:58:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2008/02/23/bylaws/#comment-43692</guid>
		<description>Ken: I often see &lt;em&gt;By-Laws&lt;/em&gt;, with a capital &lt;em&gt;L&lt;/em&gt; after the hyphen. Is there any support for that usage? I would dare say that the majority of drafters capitalize &lt;em&gt;laws&lt;/em&gt; when they use the hypen approach but I have never understood why. Steve</description>
		<content:encoded><![CDATA[<p>Ken: I often see <em>By-Laws</em>, with a capital <em>L</em> after the hyphen. Is there any support for that usage? I would dare say that the majority of drafters capitalize <em>laws</em> when they use the hypen approach but I have never understood why. Steve</p>
]]></content:encoded>
	</item>
</channel>
</rss>
