<?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: On Using a Two-Column Format</title>
	<atom:link href="http://www.adamsdrafting.com/2006/07/30/on-using-a-two-column-format/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.adamsdrafting.com/2006/07/30/on-using-a-two-column-format/</link>
	<description></description>
	<lastBuildDate>Tue, 31 Jan 2012 01:23:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
	<item>
		<title>By: AJ</title>
		<link>http://www.adamsdrafting.com/2006/07/30/on-using-a-two-column-format/comment-page-1/#comment-92629</link>
		<dc:creator>AJ</dc:creator>
		<pubDate>Mon, 06 Jul 2009 14:06:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2006/07/30/on-using-a-two-column-format/#comment-92629</guid>
		<description>Hi,
I waa referring to FIDIC conditions of Contract and was interested in applying the same formating i.e. the headings should be freely flowing in LHS column and the all the texts are similialy limited to RHS column - both texts flowing freely (as in a table).
I am avoiding table for the obvious reasons of it not giving the freedom of desired formatting. Is there any way to make the columns take such texts.</description>
		<content:encoded><![CDATA[<p>Hi,<br />
I waa referring to FIDIC conditions of Contract and was interested in applying the same formating i.e. the headings should be freely flowing in LHS column and the all the texts are similialy limited to RHS column &#8211; both texts flowing freely (as in a table).<br />
I am avoiding table for the obvious reasons of it not giving the freedom of desired formatting. Is there any way to make the columns take such texts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gregory S. Marsiglia</title>
		<link>http://www.adamsdrafting.com/2006/07/30/on-using-a-two-column-format/comment-page-1/#comment-31330</link>
		<dc:creator>Gregory S. Marsiglia</dc:creator>
		<pubDate>Sat, 19 Jan 2008 01:38:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2006/07/30/on-using-a-two-column-format/#comment-31330</guid>
		<description>The same text printed in two columns requires fewer pages than if printed in one.</description>
		<content:encoded><![CDATA[<p>The same text printed in two columns requires fewer pages than if printed in one.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AdamsDrafting &#187; Blog Archive &#187; It&#8217;s Time for a Typeface Change</title>
		<link>http://www.adamsdrafting.com/2006/07/30/on-using-a-two-column-format/comment-page-1/#comment-24757</link>
		<dc:creator>AdamsDrafting &#187; Blog Archive &#187; It&#8217;s Time for a Typeface Change</dc:creator>
		<pubDate>Thu, 20 Dec 2007 23:35:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2006/07/30/on-using-a-two-column-format/#comment-24757</guid>
		<description>[...] Of the two sample pages that I link to above, the version with Times New Roman squeezes three more lines on the one page than does the Calibri version. That&#8217;s because, in typographer speak, Calibri has a slightly larger x-height, wider letter-spacing, and more in-built interline spacing (also known as leading). But I&#8217;m don&#8217;t make a fetish of variations of a page or two in the page count. If it&#8217;s something you&#8217;re concerned about, you could use 11.5 point size or, gulp, a two-column format. [...]</description>
		<content:encoded><![CDATA[<p>[...] Of the two sample pages that I link to above, the version with Times New Roman squeezes three more lines on the one page than does the Calibri version. That&#8217;s because, in typographer speak, Calibri has a slightly larger x-height, wider letter-spacing, and more in-built interline spacing (also known as leading). But I&#8217;m don&#8217;t make a fetish of variations of a page or two in the page count. If it&#8217;s something you&#8217;re concerned about, you could use 11.5 point size or, gulp, a two-column format. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Adams</title>
		<link>http://www.adamsdrafting.com/2006/07/30/on-using-a-two-column-format/comment-page-1/#comment-8637</link>
		<dc:creator>Ken Adams</dc:creator>
		<pubDate>Tue, 11 Sep 2007 20:45:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2006/07/30/on-using-a-two-column-format/#comment-8637</guid>
		<description>I&#039;ve just uploaded a new PDF of the one-page examples. In the two-column version, I halved the tab settings. Ken</description>
		<content:encoded><![CDATA[<p>I&#8217;ve just uploaded a new PDF of the one-page examples. In the two-column version, I halved the tab settings. Ken</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Celia C. Elwell</title>
		<link>http://www.adamsdrafting.com/2006/07/30/on-using-a-two-column-format/comment-page-1/#comment-103</link>
		<dc:creator>Celia C. Elwell</dc:creator>
		<pubDate>Fri, 11 Aug 2006 17:21:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2006/07/30/on-using-a-two-column-format/#comment-103</guid>
		<description>The columns don&#039;t bother me much, but the idea of long contract language sentences and paragraphs in 8 point font does.  That&#039;s just too small and too crammed together, unless making it hard to read is the goal.</description>
		<content:encoded><![CDATA[<p>The columns don&#8217;t bother me much, but the idea of long contract language sentences and paragraphs in 8 point font does.  That&#8217;s just too small and too crammed together, unless making it hard to read is the goal.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Goldman</title>
		<link>http://www.adamsdrafting.com/2006/07/30/on-using-a-two-column-format/comment-page-1/#comment-94</link>
		<dc:creator>Eric Goldman</dc:creator>
		<pubDate>Thu, 03 Aug 2006 15:10:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2006/07/30/on-using-a-two-column-format/#comment-94</guid>
		<description>Agreed.  But even if a commercial contract escapes negotiation 95% of the time, that other 5% of the time can be a pain for the reviewers.  And, if a dual-column contract hits my desk, it&#039;s because we&#039;re one of the exceptions, yet I still have to deal with the dual columns.  I&#039;ll also add that, in the pursuit of faux brevity, I&#039;ve gotten commercial contracts from the other side in dual columns that I know most/all of their customers negotiate.  Eric.</description>
		<content:encoded><![CDATA[<p>Agreed.  But even if a commercial contract escapes negotiation 95% of the time, that other 5% of the time can be a pain for the reviewers.  And, if a dual-column contract hits my desk, it&#8217;s because we&#8217;re one of the exceptions, yet I still have to deal with the dual columns.  I&#8217;ll also add that, in the pursuit of faux brevity, I&#8217;ve gotten commercial contracts from the other side in dual columns that I know most/all of their customers negotiate.  Eric.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Adams</title>
		<link>http://www.adamsdrafting.com/2006/07/30/on-using-a-two-column-format/comment-page-1/#comment-91</link>
		<dc:creator>Ken Adams</dc:creator>
		<pubDate>Thu, 03 Aug 2006 14:08:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2006/07/30/on-using-a-two-column-format/#comment-91</guid>
		<description>Eric: No argument that 8 point is borderline (although the two-column format offsets somewhat the small font size).

But my principal feeling regarding the two-column format is not that it&#039;s somehow an improvement on one-column formats--it isn&#039;t--but rather that I&#039;m pleasantly surprised that I was able to come up with a two-column format that I can live with, if necessary, rather than simply rejecting the notion out of hand, which is what I have been doing.

In the context of commercial agreements that essentially aren&#039;t subject to negotiation, businesspeople will sometimes insist on a two-column format--anything to make the document shorter. When a document is to be negotiated, I certainly wouldn&#039;t use two-columns, and I&#039;d be peeved if someone sent me a two-column draft.</description>
		<content:encoded><![CDATA[<p>Eric: No argument that 8 point is borderline (although the two-column format offsets somewhat the small font size).</p>
<p>But my principal feeling regarding the two-column format is not that it&#8217;s somehow an improvement on one-column formats&#8211;it isn&#8217;t&#8211;but rather that I&#8217;m pleasantly surprised that I was able to come up with a two-column format that I can live with, if necessary, rather than simply rejecting the notion out of hand, which is what I have been doing.</p>
<p>In the context of commercial agreements that essentially aren&#8217;t subject to negotiation, businesspeople will sometimes insist on a two-column format&#8211;anything to make the document shorter. When a document is to be negotiated, I certainly wouldn&#8217;t use two-columns, and I&#8217;d be peeved if someone sent me a two-column draft.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Goldman</title>
		<link>http://www.adamsdrafting.com/2006/07/30/on-using-a-two-column-format/comment-page-1/#comment-90</link>
		<dc:creator>Eric Goldman</dc:creator>
		<pubDate>Thu, 03 Aug 2006 01:07:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2006/07/30/on-using-a-two-column-format/#comment-90</guid>
		<description>I&#039;m not sure if the negotiation deterrent effect is due to dual columns or small type.  I find that the smaller the type, the less negotiable the contract feels.  

I always view formatting tricks like dual columns, small fonts and (worst of all) reduced margins as a shell game--a way to move words around without reducing the substance.  My goal has always been to use the fewest number of words possible, i.e., to legitimately reduce the document&#039;s length.  I find that short documents just make everything go faster, so I fight for every word in advance.  If my client decides to engage in formatting games after that, it&#039;s their choice.  

On the other side, when I get a Word document in small font, I just increase the font size myself before I review it (and sometimes in the return document).  Where I can, I get rid of dual columns too, but this can screw up the formatting.  I do get ticked when I&#039;m asked to review a PDF document with small font and dual columns.  Arial 8 is borderline, but I wouldn&#039;t be too upset to get your mock document so long as the margins were wide enough for writing comments.

Eric.</description>
		<content:encoded><![CDATA[<p>I&#8217;m not sure if the negotiation deterrent effect is due to dual columns or small type.  I find that the smaller the type, the less negotiable the contract feels.  </p>
<p>I always view formatting tricks like dual columns, small fonts and (worst of all) reduced margins as a shell game&#8211;a way to move words around without reducing the substance.  My goal has always been to use the fewest number of words possible, i.e., to legitimately reduce the document&#8217;s length.  I find that short documents just make everything go faster, so I fight for every word in advance.  If my client decides to engage in formatting games after that, it&#8217;s their choice.  </p>
<p>On the other side, when I get a Word document in small font, I just increase the font size myself before I review it (and sometimes in the return document).  Where I can, I get rid of dual columns too, but this can screw up the formatting.  I do get ticked when I&#8217;m asked to review a PDF document with small font and dual columns.  Arial 8 is borderline, but I wouldn&#8217;t be too upset to get your mock document so long as the margins were wide enough for writing comments.</p>
<p>Eric.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mary</title>
		<link>http://www.adamsdrafting.com/2006/07/30/on-using-a-two-column-format/comment-page-1/#comment-88</link>
		<dc:creator>Mary</dc:creator>
		<pubDate>Tue, 01 Aug 2006 02:11:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2006/07/30/on-using-a-two-column-format/#comment-88</guid>
		<description>Ken,

Some things have been well known (or assumed) in document design:

1) Shorter line lengths improve readability, making two column formats easier to read.

2)On paper, in smaller sizes, serif fonts (such as Times) are easier to read than sans-serif fonts (such as Arial). Arial is best on screens and for headings.

3) Two columns does give the appearance of being &quot;boiler plate&quot;. For most documents the boiler plate is less likely to be custom written and more difficult to modify.

Although MS Word makes two column format easy to produce, few people use it. Therefore the &quot;this isn&#039;t going to be changed&quot; impression remains common. However, it can also gives the impression that the document is a form and not necessarily appropriate for the particular circumstances.

I don&#039;t work with contracts as often as I work with standards, specifications, and other documents. However, I expect the above observations apply to contracts as well as to the other documents.</description>
		<content:encoded><![CDATA[<p>Ken,</p>
<p>Some things have been well known (or assumed) in document design:</p>
<p>1) Shorter line lengths improve readability, making two column formats easier to read.</p>
<p>2)On paper, in smaller sizes, serif fonts (such as Times) are easier to read than sans-serif fonts (such as Arial). Arial is best on screens and for headings.</p>
<p>3) Two columns does give the appearance of being &#8220;boiler plate&#8221;. For most documents the boiler plate is less likely to be custom written and more difficult to modify.</p>
<p>Although MS Word makes two column format easy to produce, few people use it. Therefore the &#8220;this isn&#8217;t going to be changed&#8221; impression remains common. However, it can also gives the impression that the document is a form and not necessarily appropriate for the particular circumstances.</p>
<p>I don&#8217;t work with contracts as often as I work with standards, specifications, and other documents. However, I expect the above observations apply to contracts as well as to the other documents.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Adams</title>
		<link>http://www.adamsdrafting.com/2006/07/30/on-using-a-two-column-format/comment-page-1/#comment-83</link>
		<dc:creator>Ken Adams</dc:creator>
		<pubDate>Sun, 30 Jul 2006 18:25:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2006/07/30/on-using-a-two-column-format/#comment-83</guid>
		<description>Michael: I believe that you&#039;re correct that a two-column format is used when the drafter hopes or expects that the parties will be doing little or no negotiating.

In the case of commercial agreements I&#039;ve been working on recently, the client&#039;s intent in using a two-column format wasn&#039;t to dissuade the other side from commenting on a given draft, but rather to downplay somehow its significance by shrinking the number of pages it occupied. But the effect is the same.</description>
		<content:encoded><![CDATA[<p>Michael: I believe that you&#8217;re correct that a two-column format is used when the drafter hopes or expects that the parties will be doing little or no negotiating.</p>
<p>In the case of commercial agreements I&#8217;ve been working on recently, the client&#8217;s intent in using a two-column format wasn&#8217;t to dissuade the other side from commenting on a given draft, but rather to downplay somehow its significance by shrinking the number of pages it occupied. But the effect is the same.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

