<?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: Top four LaTeX mistakes</title>
	<atom:link href="http://www.johndcook.com/blog/2010/02/15/top-latex-mistakes/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.johndcook.com/blog/2010/02/15/top-latex-mistakes/</link>
	<description>The blog of John D. Cook</description>
	<lastBuildDate>Sat, 11 Feb 2012 01:10:06 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Andrew McLeod</title>
		<link>http://www.johndcook.com/blog/2010/02/15/top-latex-mistakes/comment-page-1/#comment-102331</link>
		<dc:creator>Andrew McLeod</dc:creator>
		<pubDate>Wed, 07 Sep 2011 16:23:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=3169#comment-102331</guid>
		<description>Also a symbol for a matrix should be bold italic.</description>
		<content:encoded><![CDATA[<p>Also a symbol for a matrix should be bold italic.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew McLeod</title>
		<link>http://www.johndcook.com/blog/2010/02/15/top-latex-mistakes/comment-page-1/#comment-102330</link>
		<dc:creator>Andrew McLeod</dc:creator>
		<pubDate>Wed, 07 Sep 2011 16:21:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=3169#comment-102330</guid>
		<description>Strictly speaking indeed,

There is an ISO standard relating to mathematics (although widely ignored?). The isomath package (&lt;a href=&quot;http://tug.ctan.org/tex-archive/macros/latex/contrib/isomath&quot; rel=&quot;nofollow&quot;&gt;http://tug.ctan.org/tex-archive/macros/latex/contrib/isomath&lt;/a&gt;) helps dramatically.

The differential operator should be roman, and care should be taken with spacing.
The constant &#039;e&#039; should be in roman, as should all constants (excluding those whose values are experimentally determined, and therefore subject to change).</description>
		<content:encoded><![CDATA[<p>Strictly speaking indeed,</p>
<p>There is an ISO standard relating to mathematics (although widely ignored?). The isomath package (<a href="http://tug.ctan.org/tex-archive/macros/latex/contrib/isomath" rel="nofollow">http://tug.ctan.org/tex-archive/macros/latex/contrib/isomath</a>) helps dramatically.</p>
<p>The differential operator should be roman, and care should be taken with spacing.<br />
The constant &#8216;e&#8217; should be in roman, as should all constants (excluding those whose values are experimentally determined, and therefore subject to change).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Rasmusen</title>
		<link>http://www.johndcook.com/blog/2010/02/15/top-latex-mistakes/comment-page-1/#comment-99111</link>
		<dc:creator>Eric Rasmusen</dc:creator>
		<pubDate>Thu, 18 Aug 2011 14:26:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=3169#comment-99111</guid>
		<description>I hate the need to use `` .  I use a plain editor to write my latex, and it looks ugly and unbalanced when you have ``quote is here&quot; on the page. Writing ``quote is here&#039; &#039;  has doubled the number of keystrokes. And if I&#039;m cutting and pasting, often I have &quot;quote is here&quot; and I have to go through and manually change all the left quotes. 

  Please, someone, write a package to fix this. Csquotes is not the solution, because it adds a huge number of necessary keystrokes and hurts readability of the raw latex code and doesn&#039;t solve the cut-and-paste problem.  All that is needed is something that goes through the latex document and whenever it finds the symbol &quot; (except if it&#039;s being used in HTML)  change it in the first instance to `` and in the second instance to &#039; &#039;  as one step in the process of turning the input code into ps or pdf.  I&#039;d do it myself but I don&#039;t know any programming languages.</description>
		<content:encoded><![CDATA[<p>I hate the need to use &#8220; .  I use a plain editor to write my latex, and it looks ugly and unbalanced when you have &#8220;quote is here&#8221; on the page. Writing &#8220;quote is here&#8217; &#8216;  has doubled the number of keystrokes. And if I&#8217;m cutting and pasting, often I have &#8220;quote is here&#8221; and I have to go through and manually change all the left quotes. </p>
<p>  Please, someone, write a package to fix this. Csquotes is not the solution, because it adds a huge number of necessary keystrokes and hurts readability of the raw latex code and doesn&#8217;t solve the cut-and-paste problem.  All that is needed is something that goes through the latex document and whenever it finds the symbol &#8221; (except if it&#8217;s being used in HTML)  change it in the first instance to &#8220; and in the second instance to &#8216; &#8216;  as one step in the process of turning the input code into ps or pdf.  I&#8217;d do it myself but I don&#8217;t know any programming languages.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Johannes</title>
		<link>http://www.johndcook.com/blog/2010/02/15/top-latex-mistakes/comment-page-1/#comment-93745</link>
		<dc:creator>Johannes</dc:creator>
		<pubDate>Wed, 20 Jul 2011 16:20:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=3169#comment-93745</guid>
		<description>Andrew: In the latter case, I guess. It gets noticable when you use text figures instead of lining figures (which should be reserved for headings and tables).</description>
		<content:encoded><![CDATA[<p>Andrew: In the latter case, I guess. It gets noticable when you use text figures instead of lining figures (which should be reserved for headings and tables).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://www.johndcook.com/blog/2010/02/15/top-latex-mistakes/comment-page-1/#comment-93635</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Tue, 19 Jul 2011 18:28:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=3169#comment-93635</guid>
		<description>When should I use math mode for isolated numerals?  Ever?

here?: &quot;There are 27 objects&quot;

here?: &quot;one of the objects has value 27&quot;</description>
		<content:encoded><![CDATA[<p>When should I use math mode for isolated numerals?  Ever?</p>
<p>here?: &#8220;There are 27 objects&#8221;</p>
<p>here?: &#8220;one of the objects has value 27&#8243;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Miguel</title>
		<link>http://www.johndcook.com/blog/2010/02/15/top-latex-mistakes/comment-page-1/#comment-93612</link>
		<dc:creator>Miguel</dc:creator>
		<pubDate>Tue, 19 Jul 2011 14:55:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=3169#comment-93612</guid>
		<description>Thanks for this post. I found it very useful.</description>
		<content:encoded><![CDATA[<p>Thanks for this post. I found it very useful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jaare</title>
		<link>http://www.johndcook.com/blog/2010/02/15/top-latex-mistakes/comment-page-1/#comment-71488</link>
		<dc:creator>jaare</dc:creator>
		<pubDate>Tue, 15 Mar 2011 15:25:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=3169#comment-71488</guid>
		<description>From item 4 I can conclude that differentials should be written as \mathrm{d}, as long d is not a variable.</description>
		<content:encoded><![CDATA[<p>From item 4 I can conclude that differentials should be written as \mathrm{d}, as long d is not a variable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Johannes Rössel</title>
		<link>http://www.johndcook.com/blog/2010/02/15/top-latex-mistakes/comment-page-1/#comment-54937</link>
		<dc:creator>Johannes Rössel</dc:creator>
		<pubDate>Sat, 11 Dec 2010 10:56:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=3169#comment-54937</guid>
		<description>Thanks for the overview. I was tempted once to write a similar article as nearly all of the above are glaring (at least to one who has a little interestin in typography). And many professors at our university, even those who wrote books, make at least a few of those errors. But I think asking a math professor to review her book for proper typography as an humble CS student is probably a bit ... misplaced :-)

Ian: That depends a little on regional typographic styles. I think in European countries it is commonly not italicized, in American typography it is, however.</description>
		<content:encoded><![CDATA[<p>Thanks for the overview. I was tempted once to write a similar article as nearly all of the above are glaring (at least to one who has a little interestin in typography). And many professors at our university, even those who wrote books, make at least a few of those errors. But I think asking a math professor to review her book for proper typography as an humble CS student is probably a bit &#8230; misplaced <img src='http://www.johndcook.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>Ian: That depends a little on regional typographic styles. I think in European countries it is commonly not italicized, in American typography it is, however.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian</title>
		<link>http://www.johndcook.com/blog/2010/02/15/top-latex-mistakes/comment-page-1/#comment-51665</link>
		<dc:creator>Ian</dc:creator>
		<pubDate>Fri, 12 Nov 2010 03:02:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=3169#comment-51665</guid>
		<description>Actually, the differential d should technically not be italics.  I usually actually make a macro so that I can use \mathrm{d} as \dif or something.  I have to say though, that sometimes I find it looks funny when it&#039;s not italics though.</description>
		<content:encoded><![CDATA[<p>Actually, the differential d should technically not be italics.  I usually actually make a macro so that I can use \mathrm{d} as \dif or something.  I have to say though, that sometimes I find it looks funny when it&#8217;s not italics though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George</title>
		<link>http://www.johndcook.com/blog/2010/02/15/top-latex-mistakes/comment-page-1/#comment-47937</link>
		<dc:creator>George</dc:creator>
		<pubDate>Tue, 05 Oct 2010 19:37:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=3169#comment-47937</guid>
		<description>Number 4 just saved my day!</description>
		<content:encoded><![CDATA[<p>Number 4 just saved my day!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob Carpenter</title>
		<link>http://www.johndcook.com/blog/2010/02/15/top-latex-mistakes/comment-page-1/#comment-41076</link>
		<dc:creator>Bob Carpenter</dc:creator>
		<pubDate>Thu, 01 Jul 2010 22:33:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=3169#comment-41076</guid>
		<description>My biggest peeve is when people use math mode for italics.   I&#039;m currently reading Robert and Casella&#039;s book&#039; Monte Carlo Methods in R, so I have to add using bit-mapped graphics (the graphics in that book are the worst I&#039;ve ever seen in a book I&#039;ve paid for).

When I wrote my first book in LaTeX (The Logic of Typed Feature Structures), the good folks at Cambridge University Press gave me a clinic on typesetting, with everything from kerning to laying out bottoms of spreads to be even.   Once you learn more about typesetting, almost everything out there looks terrible.  Especially egregious is all the wasted white space in most docs, especially vertically;  CUP&#039;s LaTeX cleanup crew actually reduced the length of my book substantially by tightening everything up.</description>
		<content:encoded><![CDATA[<p>My biggest peeve is when people use math mode for italics.   I&#8217;m currently reading Robert and Casella&#8217;s book&#8217; Monte Carlo Methods in R, so I have to add using bit-mapped graphics (the graphics in that book are the worst I&#8217;ve ever seen in a book I&#8217;ve paid for).</p>
<p>When I wrote my first book in LaTeX (The Logic of Typed Feature Structures), the good folks at Cambridge University Press gave me a clinic on typesetting, with everything from kerning to laying out bottoms of spreads to be even.   Once you learn more about typesetting, almost everything out there looks terrible.  Especially egregious is all the wasted white space in most docs, especially vertically;  CUP&#8217;s LaTeX cleanup crew actually reduced the length of my book substantially by tightening everything up.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://www.johndcook.com/blog/2010/02/15/top-latex-mistakes/comment-page-1/#comment-38383</link>
		<dc:creator>John</dc:creator>
		<pubDate>Thu, 13 May 2010 21:00:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=3169#comment-38383</guid>
		<description>Mario: One advantage of HTML over LaTeX in this context is that I assume browsers would render the HTML markup &lt;q&gt; for quotes differently depending on the user&#039;s locale.</description>
		<content:encoded><![CDATA[<p>Mario: One advantage of HTML over LaTeX in this context is that I assume browsers would render the HTML markup <q> for quotes differently depending on the user&#8217;s locale.</q></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mario</title>
		<link>http://www.johndcook.com/blog/2010/02/15/top-latex-mistakes/comment-page-1/#comment-38381</link>
		<dc:creator>Mario</dc:creator>
		<pubDate>Thu, 13 May 2010 19:42:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=3169#comment-38381</guid>
		<description>In my country we write quotes as ,,text&#039;&#039; (here I used double comma and double apostrofe).

Integrals should be written as &quot;\int_0^1f(x)\,\mathrm{d}x&quot; for the d to be not italics.</description>
		<content:encoded><![CDATA[<p>In my country we write quotes as ,,text&#8221; (here I used double comma and double apostrofe).</p>
<p>Integrals should be written as &#8220;\int_0^1f(x)\,\mathrm{d}x&#8221; for the d to be not italics.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Brown</title>
		<link>http://www.johndcook.com/blog/2010/02/15/top-latex-mistakes/comment-page-1/#comment-33137</link>
		<dc:creator>David Brown</dc:creator>
		<pubDate>Wed, 17 Feb 2010 18:43:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=3169#comment-33137</guid>
		<description>One of my latex pet peeves: \colon vs. : (e.g. $f:X \to Y$ vs. $f\colon X \to Y$; the second moves the colon slightly to the left).</description>
		<content:encoded><![CDATA[<p>One of my latex pet peeves: \colon vs. : (e.g. $f:X \to Y$ vs. $f\colon X \to Y$; the second moves the colon slightly to the left).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Richeson</title>
		<link>http://www.johndcook.com/blog/2010/02/15/top-latex-mistakes/comment-page-1/#comment-33133</link>
		<dc:creator>Dave Richeson</dc:creator>
		<pubDate>Wed, 17 Feb 2010 16:18:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=3169#comment-33133</guid>
		<description>Great list. 

I have my  students write in Latex all the time. If I had to come up with my own list of mistakes my students make all the time I would definitely have included (3) and (4). 

Two others that I would add are to use the letter x instead of \times, and the dual to your (4)—writing text in math mode. For example, \{x\in S: x&gt;2 and x&lt;4\} (the &quot;and&quot; should be plain text).</description>
		<content:encoded><![CDATA[<p>Great list. </p>
<p>I have my  students write in Latex all the time. If I had to come up with my own list of mistakes my students make all the time I would definitely have included (3) and (4). </p>
<p>Two others that I would add are to use the letter x instead of \times, and the dual to your (4)—writing text in math mode. For example, \{x\in S: x&gt;2 and x&lt;4\} (the &quot;and&quot; should be plain text).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthias</title>
		<link>http://www.johndcook.com/blog/2010/02/15/top-latex-mistakes/comment-page-1/#comment-33012</link>
		<dc:creator>Matthias</dc:creator>
		<pubDate>Tue, 16 Feb 2010 04:27:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=3169#comment-33012</guid>
		<description>The quotes problem can be solved by using the excellent package &quot;csquotes&quot; (see http://www.ctan.org/tex-archive/macros/latex/contrib/csquotes/ ). The basic command \enquote{text} typesets the correct quotation marks for the selected language automagically.</description>
		<content:encoded><![CDATA[<p>The quotes problem can be solved by using the excellent package &#8220;csquotes&#8221; (see <a href="http://www.ctan.org/tex-archive/macros/latex/contrib/csquotes/" rel="nofollow">http://www.ctan.org/tex-archive/macros/latex/contrib/csquotes/</a> ). The basic command \enquote{text} typesets the correct quotation marks for the selected language automagically.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Top four LaTeX mistakes &#124; Research tips</title>
		<link>http://www.johndcook.com/blog/2010/02/15/top-latex-mistakes/comment-page-1/#comment-32995</link>
		<dc:creator>Top four LaTeX mistakes &#124; Research tips</dc:creator>
		<pubDate>Mon, 15 Feb 2010 23:17:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=3169#comment-32995</guid>
		<description>[...] is a nice post today by John Cook on the top four LaTeX mistakes. I see these all the time in draft papers by my students and [...]</description>
		<content:encoded><![CDATA[<p>[...] is a nice post today by John Cook on the top four LaTeX mistakes. I see these all the time in draft papers by my students and [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Elton Carvalho</title>
		<link>http://www.johndcook.com/blog/2010/02/15/top-latex-mistakes/comment-page-1/#comment-32985</link>
		<dc:creator>Elton Carvalho</dc:creator>
		<pubDate>Mon, 15 Feb 2010 18:09:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=3169#comment-32985</guid>
		<description>The problem with putting &quot;the real&quot; curly quotes in a .tex source would be portability. Not all editors use UTF-8, you see?

About differentials, aside the \, spacing, I prefer to write the d uptight, so I usually define a \newcoomand{\ud}{\mathrm{d}} and use it whenever I need a differential.</description>
		<content:encoded><![CDATA[<p>The problem with putting &#8220;the real&#8221; curly quotes in a .tex source would be portability. Not all editors use UTF-8, you see?</p>
<p>About differentials, aside the \, spacing, I prefer to write the d uptight, so I usually define a \newcoomand{\ud}{\mathrm{d}} and use it whenever I need a differential.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MATLABician</title>
		<link>http://www.johndcook.com/blog/2010/02/15/top-latex-mistakes/comment-page-1/#comment-32982</link>
		<dc:creator>MATLABician</dc:creator>
		<pubDate>Mon, 15 Feb 2010 17:12:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=3169#comment-32982</guid>
		<description>A number of mistakes come to my mind---some common and some subtle---too many to mention in the comments. I&#039;ve put together some of them in a ``LaTeX niceties&#039;&#039; document here: &lt;a href=&quot;http://matlabician.wordpress.com/latex-niceties&quot; rel=&quot;nofollow&quot;&gt;http://matlabician.wordpress.com/latex-niceties&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>A number of mistakes come to my mind&#8212;some common and some subtle&#8212;too many to mention in the comments. I&#8217;ve put together some of them in a &#8220;LaTeX niceties&#8221; document here: <a href="http://matlabician.wordpress.com/latex-niceties" rel="nofollow">http://matlabician.wordpress.com/latex-niceties</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Panos Ipeirotis</title>
		<link>http://www.johndcook.com/blog/2010/02/15/top-latex-mistakes/comment-page-1/#comment-32978</link>
		<dc:creator>Panos Ipeirotis</dc:creator>
		<pubDate>Mon, 15 Feb 2010 15:52:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=3169#comment-32978</guid>
		<description>My own pet peeve is the incorrect use of the non-breaking space (the ~ character). I have seen countless times users putting a space before ~. For example, &#039;in Section ~\ref{sec:blah}, we see...&#039; instead of  &#039;in Section~\ref{sec:blah}, we see...&#039;. Or &#039;John Smith ~\cite{smith}&#039; instead of the correct &#039;John Smith~\cite{smith}&#039;.</description>
		<content:encoded><![CDATA[<p>My own pet peeve is the incorrect use of the non-breaking space (the ~ character). I have seen countless times users putting a space before ~. For example, &#8216;in Section ~\ref{sec:blah}, we see&#8230;&#8217; instead of  &#8216;in Section~\ref{sec:blah}, we see&#8230;&#8217;. Or &#8216;John Smith ~\cite{smith}&#8217; instead of the correct &#8216;John Smith~\cite{smith}&#8217;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Dyer</title>
		<link>http://www.johndcook.com/blog/2010/02/15/top-latex-mistakes/comment-page-1/#comment-32976</link>
		<dc:creator>Jason Dyer</dc:creator>
		<pubDate>Mon, 15 Feb 2010 15:20:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=3169#comment-32976</guid>
		<description>I&#039;m guilty of #2, but I wasn&#039;t writing a book or article either. Can you point me to a place to see this error &quot;in the wild&quot;?</description>
		<content:encoded><![CDATA[<p>I&#8217;m guilty of #2, but I wasn&#8217;t writing a book or article either. Can you point me to a place to see this error &#8220;in the wild&#8221;?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://www.johndcook.com/blog/2010/02/15/top-latex-mistakes/comment-page-1/#comment-32975</link>
		<dc:creator>John</dc:creator>
		<pubDate>Mon, 15 Feb 2010 14:51:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=3169#comment-32975</guid>
		<description>mjm: Certainly some TeX-authoring software will fix the quotes for you. My impression is that nearly all TeX software will do this for you. That doesn&#039;t mean the mistake isn&#039;t still common. Maybe people using a general-purpose text editor rather than software (or context-sensitive mode) specialized for TeX.</description>
		<content:encoded><![CDATA[<p>mjm: Certainly some TeX-authoring software will fix the quotes for you. My impression is that nearly all TeX software will do this for you. That doesn&#8217;t mean the mistake isn&#8217;t still common. Maybe people using a general-purpose text editor rather than software (or context-sensitive mode) specialized for TeX.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mjm</title>
		<link>http://www.johndcook.com/blog/2010/02/15/top-latex-mistakes/comment-page-1/#comment-32974</link>
		<dc:creator>mjm</dc:creator>
		<pubDate>Mon, 15 Feb 2010 14:45:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=3169#comment-32974</guid>
		<description>The ``double-backtick-double-apostrophe solution&#039;&#039; to (1) has always bothered me. It looks just as irritating and amateurish as the problem it ”solves”. It was fine for a time when curly quotes were exotic, but today it feels like a hack.

A better way is to use real curly quotes. On the mac US keyboard layout, they’re option-[ and option-shift=[ (single quotes are under ]). I haven’t used windows in a while but the US-International keyboard layout used to be almost as usable as the mac layout.

If you use Emacs, AUCTeX lets you use the inch-mark &quot; just as you would in word-processing software and contextually switches it to “ before text and ” after (&quot; with a second press if you are talking about inches). The config group tex-quote lets you configure this behavior and more. The csquotes package is helpful if you use different languages with different quoting habits – your source can contain “” and the result in French for example be typeset using «».

Is there any other TeX-authoring software that does this?</description>
		<content:encoded><![CDATA[<p>The &#8220;double-backtick-double-apostrophe solution&#8221; to (1) has always bothered me. It looks just as irritating and amateurish as the problem it ”solves”. It was fine for a time when curly quotes were exotic, but today it feels like a hack.</p>
<p>A better way is to use real curly quotes. On the mac US keyboard layout, they’re option-[ and option-shift=[ (single quotes are under ]). I haven’t used windows in a while but the US-International keyboard layout used to be almost as usable as the mac layout.</p>
<p>If you use Emacs, AUCTeX lets you use the inch-mark &#8221; just as you would in word-processing software and contextually switches it to “ before text and ” after (&#8221; with a second press if you are talking about inches). The config group tex-quote lets you configure this behavior and more. The csquotes package is helpful if you use different languages with different quoting habits – your source can contain “” and the result in French for example be typeset using «».</p>
<p>Is there any other TeX-authoring software that does this?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://www.johndcook.com/blog/2010/02/15/top-latex-mistakes/comment-page-1/#comment-32973</link>
		<dc:creator>John</dc:creator>
		<pubDate>Mon, 15 Feb 2010 14:43:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=3169#comment-32973</guid>
		<description>I recommend typing closing delimiters immediately after opening delimiters, then backing up to fill in the content in between. I almost always work this way, unless there is very little content between the delimiters. 

I also recommend &lt;a href=&quot;http://stackoverflow.com/questions/193298/best-practices-in-latex/218506#218506&quot; rel=&quot;nofollow&quot;&gt;aligning LaTeX delimiters&lt;/a&gt; vertically, the way one would when writing C code, especially for delimiters like &lt;code&gt;\left(&lt;/code&gt; and&lt;code&gt; \right)&lt;/code&gt; that might have a lot of content inside.</description>
		<content:encoded><![CDATA[<p>I recommend typing closing delimiters immediately after opening delimiters, then backing up to fill in the content in between. I almost always work this way, unless there is very little content between the delimiters. </p>
<p>I also recommend <a href="http://stackoverflow.com/questions/193298/best-practices-in-latex/218506#218506" rel="nofollow">aligning LaTeX delimiters</a> vertically, the way one would when writing C code, especially for delimiters like <code>\left(</code> and<code> \right)</code> that might have a lot of content inside.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Talbert</title>
		<link>http://www.johndcook.com/blog/2010/02/15/top-latex-mistakes/comment-page-1/#comment-32968</link>
		<dc:creator>Robert Talbert</dc:creator>
		<pubDate>Mon, 15 Feb 2010 14:27:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.johndcook.com/blog/?p=3169#comment-32968</guid>
		<description>I&#039;d have to say the #1 LaTeX mistake is none of the above, but simply mismatching delimiters -- whether it&#039;s failing to match a parenthesis or other delimiter altogether, or matching it with the wrong kind. Example: \frac{1}{x).  

I also am repeatedly guilty of forgetting to close off an environment properly, such as when I have nested enumerate environments (happens a lot to teachers who do this sort of thing for creating tests).</description>
		<content:encoded><![CDATA[<p>I&#8217;d have to say the #1 LaTeX mistake is none of the above, but simply mismatching delimiters &#8212; whether it&#8217;s failing to match a parenthesis or other delimiter altogether, or matching it with the wrong kind. Example: \frac{1}{x).  </p>
<p>I also am repeatedly guilty of forgetting to close off an environment properly, such as when I have nested enumerate environments (happens a lot to teachers who do this sort of thing for creating tests).</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.477 seconds -->

