<?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: Rules to Type By</title>
	<atom:link href="http://drewd.com/2008/09/18/rules-to-type-by/feed" rel="self" type="application/rss+xml" />
	<link>http://drewd.com/2008/09/18/rules-to-type-by</link>
	<description>The Adventures of Carlos d'Avis</description>
	<lastBuildDate>Mon, 06 Feb 2012 08:57:06 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: drew</title>
		<link>http://drewd.com/2008/09/18/rules-to-type-by/comment-page-1#comment-18059</link>
		<dc:creator>drew</dc:creator>
		<pubDate>Mon, 20 Oct 2008 21:12:43 +0000</pubDate>
		<guid isPermaLink="false">http://drewd.com/?p=437#comment-18059</guid>
		<description>I should make you a guest blogger, Charlie—your comment on my post is somewhere around five times longer than the post itself. 

As a note to you, Charlie Ellis, and to less informed readers, the Charlie I mentioned in my blog post is Charlie Matlack, who asked me about font choice for résumé some weeks ago. Mr. Ellis and I have, nonetheless, discussed typography previously and I much appreciate his reaction. 

I believe I made the switch to single-spaced sentences nearly a decade ago for purely aesthetic reasons. I did not know the behavior was &quot;correct&quot; but I knew I disliked the way double-spaced sentences look when printed from a computer (or on the web). 

Would you speak to specific problems you have with his policies on punctuation? 

His focus is certainly on printed materials, as the legal field stills deals primarily in physical documents. I absolutely agree that more conservative, standard font choices are correct for on-screen communication. If a potential employer requests a résumé as a Word document, I cringe and then deliver a relatively unstyled version, without fear of errors in its display. I much prefer a carefully generated PDF for this class of documents. And I believe one can generate a PDF with embedded fonts and text selection and search capabilities. 

In the CSS3 specification, font-face embedding is allowed. In other words, the HTML document can specify a font file on the server that is downloaded to the user&#039;s computer for proper display of a typeface. The major issue in this behavior is font licensing infringement. The less significant but more widespread issue will be the rising prevalence of eye-assaulting web font choices. Check out &lt;a href=&quot;http://typographica.org/001112.php&quot; rel=&quot;nofollow&quot;&gt;Typographica&lt;/a&gt; and &lt;a href=&quot;http://www.alistapart.com/articles/cssatten&quot; rel=&quot;nofollow&quot;&gt;A List Apart&lt;/a&gt; for more discussion.  

As for e-mails and Word documents, I do not know of any means of embedding fonts.</description>
		<content:encoded><![CDATA[<p>I should make you a guest blogger, Charlie—your comment on my post is somewhere around five times longer than the post itself. </p>
<p>As a note to you, Charlie Ellis, and to less informed readers, the Charlie I mentioned in my blog post is Charlie Matlack, who asked me about font choice for résumé some weeks ago. Mr. Ellis and I have, nonetheless, discussed typography previously and I much appreciate his reaction. </p>
<p>I believe I made the switch to single-spaced sentences nearly a decade ago for purely aesthetic reasons. I did not know the behavior was "correct" but I knew I disliked the way double-spaced sentences look when printed from a computer (or on the web). </p>
<p>Would you speak to specific problems you have with his policies on punctuation? </p>
<p>His focus is certainly on printed materials, as the legal field stills deals primarily in physical documents. I absolutely agree that more conservative, standard font choices are correct for on-screen communication. If a potential employer requests a résumé as a Word document, I cringe and then deliver a relatively unstyled version, without fear of errors in its display. I much prefer a carefully generated PDF for this class of documents. And I believe one can generate a PDF with embedded fonts and text selection and search capabilities. </p>
<p>In the CSS3 specification, font-face embedding is allowed. In other words, the HTML document can specify a font file on the server that is downloaded to the user's computer for proper display of a typeface. The major issue in this behavior is font licensing infringement. The less significant but more widespread issue will be the rising prevalence of eye-assaulting web font choices. Check out <a href="http://typographica.org/001112.php" rel="nofollow">Typographica</a> and <a href="http://www.alistapart.com/articles/cssatten" rel="nofollow">A List Apart</a> for more discussion.  </p>
<p>As for e-mails and Word documents, I do not know of any means of embedding fonts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Charlie</title>
		<link>http://drewd.com/2008/09/18/rules-to-type-by/comment-page-1#comment-18002</link>
		<dc:creator>Charlie</dc:creator>
		<pubDate>Sat, 18 Oct 2008 05:57:37 +0000</pubDate>
		<guid isPermaLink="false">http://drewd.com/?p=437#comment-18002</guid>
		<description>Good read. Apparently I&#039;m running the risk of being boring in my website typography choices. I&#039;ve done worse things, but maybe I should play with the font there.

As someone who rarely worries much about shaving for work, let alone polishing my shoes, I find some of this stuff a bit over-the-top, but I like the ideas, guidelines, and generally agree with his taste. For example, I always used Garamond as the font for my resume, which made copious use of small caps. I liked, and still like, that it gave the document a lighter, livelier, somewhat willowy feel, while still appearing elegant and professional.

And, though his ideas on punctuation seem a bit off to me, I do hereby solemnly promise to try to stop double spacing my sentences (it may take my fingers a while to unlearn their habits).

Also, he doesn&#039;t talk much about online font choices, and most of the stuff I write, both at work and in personal life, is primarily intended for consumption on a computer screen and only occasionally printed. In such cases, doesn&#039;t a balance have to be struck between novelty (not making the default choice) and getting something that is on the system? It seems like picking something not on your readers&#039; systems is a disaster, since font substitution will kick in and the result is something that&#039;s not only standardized but also completely unanticipated.

In such circumstances, the choice of Verdana or even Calibri for email or a Word doc seems like an OK one to me. While I may want to avoid Helvetica or Palatino, is there some font-embedding technology that I don&#039;t know about that would let me pick something like Minion and be confident that it&#039;s available to all my readers.

What do you think, Drew?</description>
		<content:encoded><![CDATA[<p>Good read. Apparently I'm running the risk of being boring in my website typography choices. I've done worse things, but maybe I should play with the font there.</p>
<p>As someone who rarely worries much about shaving for work, let alone polishing my shoes, I find some of this stuff a bit over-the-top, but I like the ideas, guidelines, and generally agree with his taste. For example, I always used Garamond as the font for my resume, which made copious use of small caps. I liked, and still like, that it gave the document a lighter, livelier, somewhat willowy feel, while still appearing elegant and professional.</p>
<p>And, though his ideas on punctuation seem a bit off to me, I do hereby solemnly promise to try to stop double spacing my sentences (it may take my fingers a while to unlearn their habits).</p>
<p>Also, he doesn't talk much about online font choices, and most of the stuff I write, both at work and in personal life, is primarily intended for consumption on a computer screen and only occasionally printed. In such cases, doesn't a balance have to be struck between novelty (not making the default choice) and getting something that is on the system? It seems like picking something not on your readers' systems is a disaster, since font substitution will kick in and the result is something that's not only standardized but also completely unanticipated.</p>
<p>In such circumstances, the choice of Verdana or even Calibri for email or a Word doc seems like an OK one to me. While I may want to avoid Helvetica or Palatino, is there some font-embedding technology that I don't know about that would let me pick something like Minion and be confident that it's available to all my readers.</p>
<p>What do you think, Drew?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: laura</title>
		<link>http://drewd.com/2008/09/18/rules-to-type-by/comment-page-1#comment-17489</link>
		<dc:creator>laura</dc:creator>
		<pubDate>Sat, 27 Sep 2008 04:22:15 +0000</pubDate>
		<guid isPermaLink="false">http://drewd.com/?p=437#comment-17489</guid>
		<description>Very interesting read.  Inspired me to try out Big Calson in place of a Times for Word.  Sadly, all but the sidebar displayed in Times New Roman in my browser.</description>
		<content:encoded><![CDATA[<p>Very interesting read.  Inspired me to try out Big Calson in place of a Times for Word.  Sadly, all but the sidebar displayed in Times New Roman in my browser.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

