<?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: Lawyer Type (4): Ragged Is Right</title>
	<atom:link href="http://www.slaw.ca/2010/01/21/lawyer-type-4-ragged-is-right/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.slaw.ca/2010/01/21/lawyer-type-4-ragged-is-right/</link>
	<description>Canada&#039;s online legal magazine</description>
	<lastBuildDate>Thu, 09 Feb 2012 19:41:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Richard Belthoff</title>
		<link>http://www.slaw.ca/2010/01/21/lawyer-type-4-ragged-is-right/comment-page-1/#comment-753911</link>
		<dc:creator>Richard Belthoff</dc:creator>
		<pubDate>Sun, 12 Dec 2010 13:09:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.slaw.ca/?p=16608#comment-753911</guid>
		<description>I just stumbled on this blog or I would have commented sooner. In any event, if you&#039;re using Microsoft Word and full justification, you should  turn on the option to fully justify as done in WordPerfect 6.x for Windows in addition to turning on hyphenation (in Word 2010, this can be found under File, Options, Advanced, Compatibility, Layout Options). This makes a page much more readable. Word stretches out words by default when using full justification. The WordPerfect option, on the other hand, compresses the words so that they are more readable. So, generally, if the default Word options are used, full justification can be atrocious, but if you configure Word properly, full justification can be as readable as ragged right.</description>
		<content:encoded><![CDATA[<p>I just stumbled on this blog or I would have commented sooner. In any event, if you&#039;re using Microsoft Word and full justification, you should  turn on the option to fully justify as done in WordPerfect 6.x for Windows in addition to turning on hyphenation (in Word 2010, this can be found under File, Options, Advanced, Compatibility, Layout Options). This makes a page much more readable. Word stretches out words by default when using full justification. The WordPerfect option, on the other hand, compresses the words so that they are more readable. So, generally, if the default Word options are used, full justification can be atrocious, but if you configure Word properly, full justification can be as readable as ragged right.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon Fodden</title>
		<link>http://www.slaw.ca/2010/01/21/lawyer-type-4-ragged-is-right/comment-page-1/#comment-716028</link>
		<dc:creator>Simon Fodden</dc:creator>
		<pubDate>Sun, 24 Jan 2010 17:31:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.slaw.ca/?p=16608#comment-716028</guid>
		<description>Thanks, Dick. I ought to have stressed hyphenation and left kerning alone: you&#039;re right. And I don&#039;t disagree that properly done justified type is easier to read; it&#039;s the properly done part that&#039;s the problem. Line width is an interesting issue in legal materials. Most make a line far too long, as you say. Some, principally in the US, will break text into narrower columns (though only in some judgments and texts), which makes it much easier to read quickly.</description>
		<content:encoded><![CDATA[<p>Thanks, Dick. I ought to have stressed hyphenation and left kerning alone: you&#039;re right. And I don&#039;t disagree that properly done justified type is easier to read; it&#039;s the properly done part that&#039;s the problem. Line width is an interesting issue in legal materials. Most make a line far too long, as you say. Some, principally in the US, will break text into narrower columns (though only in some judgments and texts), which makes it much easier to read quickly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dick Margulis</title>
		<link>http://www.slaw.ca/2010/01/21/lawyer-type-4-ragged-is-right/comment-page-1/#comment-716027</link>
		<dc:creator>Dick Margulis</dc:creator>
		<pubDate>Sun, 24 Jan 2010 16:38:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.slaw.ca/?p=16608#comment-716027</guid>
		<description>Your comment interface seems not to permit URLs. I had included the link for Colin Wheildon, Type and Layout, but it vanished. Here it is in a form readers should be able to decipher: http://www.amazon.com/Type-Layout-Communicating-Making-Pretty/dp/1875750223</description>
		<content:encoded><![CDATA[<p>Your comment interface seems not to permit URLs. I had included the link for Colin Wheildon, Type and Layout, but it vanished. Here it is in a form readers should be able to decipher: <a href="http://www.amazon.com/Type-Layout-Communicating-Making-Pretty/dp/1875750223">http://www.amazon.com/Type-Layout-Communicating-Making-Pretty/dp/1875750223</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dick Margulis</title>
		<link>http://www.slaw.ca/2010/01/21/lawyer-type-4-ragged-is-right/comment-page-1/#comment-716026</link>
		<dc:creator>Dick Margulis</dc:creator>
		<pubDate>Sun, 24 Jan 2010 16:35:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.slaw.ca/?p=16608#comment-716026</guid>
		<description>Oh dear, where to start.

Okay, yes, word processors (notably MS Word) do a poor job of justification. The reason, though, is that hyphenation (breaking words at the end of the line) is turned off by default. And when it is turned on, the default parameters (unlimited consecutive hyphens, as well as the numeric settings) are far from ideal. So you&#039;re correct that ragged right reads better in word processor text, but you&#039;re not correct about the reason. Good typesetting does not require adjusting letterspacing except on rare occasion. Proper hyphenation control is usually adequate.

There may be some requirement I&#039;m not aware of (not being a lawyer) that you shouldn&#039;t hyphenate legal documents. If that&#039;s the case, then carry on with your ragged right.

However, the ONLY properly designed readability study in print (Colin Wheildon, Type and Layout,  demonstrates that properly justified text is actually more readable than ragged text, resulting in better retention and comprehension on the part of the reader.

The larger problem with legal documents is that the line length is too long and the leading (line spacing) too tight to enable proper reading in the first place. While you chose to limit this post to a single issue, you can&#039;t really do that and still understand the problem as it presents in the real world.

That said, readers are divided into three groups:

• Readers with certain disabilities process text differently from normal readers, requiring accommodations that actually impair readability for normal readers. For the purpose of THIS discussion, I&#039;ll ignore that group.

• People who are sensitive to the way type is presented on the page.

• People who are not sensitive to the way type is presented on the page.

For the latter group, this whole conversation is meaningless. They process text as a string of abstract symbols, much the way a paper tape reader does. Many are excellent speed readers, and they typically do well in terms of comprehension, even if they can&#039;t recall particular phrases or sentences. This group is not hindered by good typography, but they&#039;re not particularly hampered by poor typography, either, as they are not cognizant of the shapes on the page. They are just channeling the writer&#039;s thoughts. I suspect most lawyers fall into this group in the end, even if they didn&#039;t start out in it, because of the massive quantity of text they have to get through.

For the former group, typography matters very much, even if they can&#039;t articulate anything about their reading experience. This is the group typographers design for.</description>
		<content:encoded><![CDATA[<p>Oh dear, where to start.</p>
<p>Okay, yes, word processors (notably MS Word) do a poor job of justification. The reason, though, is that hyphenation (breaking words at the end of the line) is turned off by default. And when it is turned on, the default parameters (unlimited consecutive hyphens, as well as the numeric settings) are far from ideal. So you&#039;re correct that ragged right reads better in word processor text, but you&#039;re not correct about the reason. Good typesetting does not require adjusting letterspacing except on rare occasion. Proper hyphenation control is usually adequate.</p>
<p>There may be some requirement I&#039;m not aware of (not being a lawyer) that you shouldn&#039;t hyphenate legal documents. If that&#039;s the case, then carry on with your ragged right.</p>
<p>However, the ONLY properly designed readability study in print (Colin Wheildon, Type and Layout,  demonstrates that properly justified text is actually more readable than ragged text, resulting in better retention and comprehension on the part of the reader.</p>
<p>The larger problem with legal documents is that the line length is too long and the leading (line spacing) too tight to enable proper reading in the first place. While you chose to limit this post to a single issue, you can&#039;t really do that and still understand the problem as it presents in the real world.</p>
<p>That said, readers are divided into three groups:</p>
<p>• Readers with certain disabilities process text differently from normal readers, requiring accommodations that actually impair readability for normal readers. For the purpose of THIS discussion, I&#039;ll ignore that group.</p>
<p>• People who are sensitive to the way type is presented on the page.</p>
<p>• People who are not sensitive to the way type is presented on the page.</p>
<p>For the latter group, this whole conversation is meaningless. They process text as a string of abstract symbols, much the way a paper tape reader does. Many are excellent speed readers, and they typically do well in terms of comprehension, even if they can&#039;t recall particular phrases or sentences. This group is not hindered by good typography, but they&#039;re not particularly hampered by poor typography, either, as they are not cognizant of the shapes on the page. They are just channeling the writer&#039;s thoughts. I suspect most lawyers fall into this group in the end, even if they didn&#039;t start out in it, because of the massive quantity of text they have to get through.</p>
<p>For the former group, typography matters very much, even if they can&#039;t articulate anything about their reading experience. This is the group typographers design for.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Cheifetz</title>
		<link>http://www.slaw.ca/2010/01/21/lawyer-type-4-ragged-is-right/comment-page-1/#comment-716006</link>
		<dc:creator>David Cheifetz</dc:creator>
		<pubDate>Sat, 23 Jan 2010 04:20:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.slaw.ca/?p=16608#comment-716006</guid>
		<description>For what it&#039;s worth, I find ragged right text harder to scan quickly than justified when I&#039;m scanning down a page to read quickly. In addition, so long as the sentence doesn&#039;t have too long a word, the proportional fonts seem to work quite well for me. I concede that longer words sometimes create a problem as do longer URLs. I have, on occasion, rewritten a sentence because I didn&#039;t like the way the spacing looked in the fully justified form, but that&#039;s extremely rare. I have a long and even longer article on my website accessible off my personal page. In one text and footnotes are fully justifed. In the other the footnotes are ragged right. That&#039;s the URL issue.</description>
		<content:encoded><![CDATA[<p>For what it&#039;s worth, I find ragged right text harder to scan quickly than justified when I&#039;m scanning down a page to read quickly. In addition, so long as the sentence doesn&#039;t have too long a word, the proportional fonts seem to work quite well for me. I concede that longer words sometimes create a problem as do longer URLs. I have, on occasion, rewritten a sentence because I didn&#039;t like the way the spacing looked in the fully justified form, but that&#039;s extremely rare. I have a long and even longer article on my website accessible off my personal page. In one text and footnotes are fully justifed. In the other the footnotes are ragged right. That&#039;s the URL issue.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John G</title>
		<link>http://www.slaw.ca/2010/01/21/lawyer-type-4-ragged-is-right/comment-page-1/#comment-716003</link>
		<dc:creator>John G</dc:creator>
		<pubDate>Sat, 23 Jan 2010 03:07:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.slaw.ca/?p=16608#comment-716003</guid>
		<description>Well, I was taught just about 50 years ago to leave two spaces after a period, and it may take me the same amount of time to stop. But the old Underwood I taught myself to type on did not justify the right edge (or the time it took me to learn, for that matter.)

Reading experts find (as I recall from when I used to teach legal writing, &lt;50 years ago) that ragged right type is easier to read than justified too. I forget why - I think it was independent of the spacing issues that Simon raises.</description>
		<content:encoded><![CDATA[<p>Well, I was taught just about 50 years ago to leave two spaces after a period, and it may take me the same amount of time to stop. But the old Underwood I taught myself to type on did not justify the right edge (or the time it took me to learn, for that matter.)</p>
<p>Reading experts find (as I recall from when I used to teach legal writing, &lt;50 years ago) that ragged right type is easier to read than justified too. I forget why &#8211; I think it was independent of the spacing issues that Simon raises.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Angela Swan</title>
		<link>http://www.slaw.ca/2010/01/21/lawyer-type-4-ragged-is-right/comment-page-1/#comment-715995</link>
		<dc:creator>Angela Swan</dc:creator>
		<pubDate>Fri, 22 Jan 2010 13:26:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.slaw.ca/?p=16608#comment-715995</guid>
		<description>Thank you, Simon. I have been making this point for years, with very little effect. Now, if we could just have a nice serif font for the text, I&#039;d be happy.</description>
		<content:encoded><![CDATA[<p>Thank you, Simon. I have been making this point for years, with very little effect. Now, if we could just have a nice serif font for the text, I&#039;d be happy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg</title>
		<link>http://www.slaw.ca/2010/01/21/lawyer-type-4-ragged-is-right/comment-page-1/#comment-715981</link>
		<dc:creator>Greg</dc:creator>
		<pubDate>Thu, 21 Jan 2010 20:05:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.slaw.ca/?p=16608#comment-715981</guid>
		<description>YES. Thank you. There&#039;s nothing more distracting when trying to follow the logic in a judgment than having to battle through triple spacing in words.

Eventually I&#039;m sure the justify tools in word processors will be smart enough to adjust kerning in a way that rivals most printers&#039; work, but until then, embrace the ragged right!</description>
		<content:encoded><![CDATA[<p>YES. Thank you. There&#039;s nothing more distracting when trying to follow the logic in a judgment than having to battle through triple spacing in words.</p>
<p>Eventually I&#039;m sure the justify tools in word processors will be smart enough to adjust kerning in a way that rivals most printers&#039; work, but until then, embrace the ragged right!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ted Tjaden</title>
		<link>http://www.slaw.ca/2010/01/21/lawyer-type-4-ragged-is-right/comment-page-1/#comment-715979</link>
		<dc:creator>Ted Tjaden</dc:creator>
		<pubDate>Thu, 21 Jan 2010 18:47:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.slaw.ca/?p=16608#comment-715979</guid>
		<description>Hear, hear!

Right-justified text and two spaces after a period gives me conniption fits.</description>
		<content:encoded><![CDATA[<p>Hear, hear!</p>
<p>Right-justified text and two spaces after a period gives me conniption fits.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- This Quick Cache file was built for (  www.slaw.ca/2010/01/21/lawyer-type-4-ragged-is-right/feed/ ) in 0.40805 seconds, on Feb 9th, 2012 at 7:54 pm UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on Feb 9th, 2012 at 8:54 pm UTC -->
