<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Include source code in Latex with &#8220;Listings&#8221;</title>
	<atom:link href="http://texblog.wordpress.com/2008/04/02/include-source-code-in-latex-with-listings/feed/" rel="self" type="application/rss+xml" />
	<link>http://texblog.wordpress.com/2008/04/02/include-source-code-in-latex-with-listings/</link>
	<description>Reporting without troubles</description>
	<lastBuildDate>Sun, 25 Oct 2009 15:55:04 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jon</title>
		<link>http://texblog.wordpress.com/2008/04/02/include-source-code-in-latex-with-listings/#comment-2225</link>
		<dc:creator>Jon</dc:creator>
		<pubDate>Thu, 26 Feb 2009 22:09:06 +0000</pubDate>
		<guid isPermaLink="false">http://texblog.wordpress.com/?p=52#comment-2225</guid>
		<description>Thanks for the post. It was useful for dumping code into latex and not worrying about escaping and formatting.</description>
		<content:encoded><![CDATA[<p>Thanks for the post. It was useful for dumping code into latex and not worrying about escaping and formatting.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: thurnherr</title>
		<link>http://texblog.wordpress.com/2008/04/02/include-source-code-in-latex-with-listings/#comment-2230</link>
		<dc:creator>thurnherr</dc:creator>
		<pubDate>Thu, 26 Feb 2009 19:00:36 +0000</pubDate>
		<guid isPermaLink="false">http://texblog.wordpress.com/?p=52#comment-2230</guid>
		<description>Hi Nadine,

You can use the following options to omit the frame and numbering:

frame=none, numbers=none

You can find the documentation of the listings package &lt;a href=&quot;http://www.pvv.ntnu.no/~berland/latex/docs/listings.pdf&quot; rel=&quot;nofollow&quot;&gt;here&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>Hi Nadine,</p>
<p>You can use the following options to omit the frame and numbering:</p>
<p>frame=none, numbers=none</p>
<p>You can find the documentation of the listings package <a href="http://www.pvv.ntnu.no/~berland/latex/docs/listings.pdf" rel="nofollow">here</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nadine</title>
		<link>http://texblog.wordpress.com/2008/04/02/include-source-code-in-latex-with-listings/#comment-2224</link>
		<dc:creator>Nadine</dc:creator>
		<pubDate>Thu, 26 Feb 2009 18:58:08 +0000</pubDate>
		<guid isPermaLink="false">http://texblog.wordpress.com/?p=52#comment-2224</guid>
		<description>Can we put the code without frame and without numbering?</description>
		<content:encoded><![CDATA[<p>Can we put the code without frame and without numbering?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nadine</title>
		<link>http://texblog.wordpress.com/2008/04/02/include-source-code-in-latex-with-listings/#comment-2223</link>
		<dc:creator>Nadine</dc:creator>
		<pubDate>Thu, 26 Feb 2009 17:15:26 +0000</pubDate>
		<guid isPermaLink="false">http://texblog.wordpress.com/?p=52#comment-2223</guid>
		<description>God mainly bless you for this page. It was a blessing for me to know how to put my SAS-Code into my latex document. So i just want to acknowledge and to thank you for it.</description>
		<content:encoded><![CDATA[<p>God mainly bless you for this page. It was a blessing for me to know how to put my SAS-Code into my latex document. So i just want to acknowledge and to thank you for it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Pyles</title>
		<link>http://texblog.wordpress.com/2008/04/02/include-source-code-in-latex-with-listings/#comment-2199</link>
		<dc:creator>James Pyles</dc:creator>
		<pubDate>Tue, 13 Jan 2009 22:42:00 +0000</pubDate>
		<guid isPermaLink="false">http://texblog.wordpress.com/?p=52#comment-2199</guid>
		<description>Thanks, Phillip. the \usepackage{upquote} solution was just was just what I was looking for.</description>
		<content:encoded><![CDATA[<p>Thanks, Phillip. the \usepackage{upquote} solution was just was just what I was looking for.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Philip Machanick</title>
		<link>http://texblog.wordpress.com/2008/04/02/include-source-code-in-latex-with-listings/#comment-2156</link>
		<dc:creator>Philip Machanick</dc:creator>
		<pubDate>Sun, 30 Nov 2008 23:14:56 +0000</pubDate>
		<guid isPermaLink="false">http://texblog.wordpress.com/?p=52#comment-2156</guid>
		<description>Answered my own question:

\usepackage{upquote}

after all other font specs will force typewriter font to Computer Modern Typewriter and make verbatim, verbatim*, verb, and verb*  leave ` and &#039; in their original state.

(&quot; is already set unchanged; I&#039;m not sure of the logic of curling &#039; and ` in a mode that otherwise leaves things unchanged. While it&#039;s true that the old ASCII character set didn&#039;t include encodings for these so it&#039;s useful to be able to create them in verbatim mode, not having an obvious escape to get back to raw apostrophes and grave accents seems to me an omission).

Not quote as fancy as the listings package but for simple scripts and one-liners, being able to get the various verbatim modes to behave is good. Unless you need the default behaviour for some other purpose in the same document ...</description>
		<content:encoded><![CDATA[<p>Answered my own question:</p>
<p>\usepackage{upquote}</p>
<p>after all other font specs will force typewriter font to Computer Modern Typewriter and make verbatim, verbatim*, verb, and verb*  leave ` and &#8216; in their original state.</p>
<p>(&#8221; is already set unchanged; I&#8217;m not sure of the logic of curling &#8216; and ` in a mode that otherwise leaves things unchanged. While it&#8217;s true that the old ASCII character set didn&#8217;t include encodings for these so it&#8217;s useful to be able to create them in verbatim mode, not having an obvious escape to get back to raw apostrophes and grave accents seems to me an omission).</p>
<p>Not quote as fancy as the listings package but for simple scripts and one-liners, being able to get the various verbatim modes to behave is good. Unless you need the default behaviour for some other purpose in the same document &#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Philip Machanick</title>
		<link>http://texblog.wordpress.com/2008/04/02/include-source-code-in-latex-with-listings/#comment-2155</link>
		<dc:creator>Philip Machanick</dc:creator>
		<pubDate>Fri, 28 Nov 2008 06:16:22 +0000</pubDate>
		<guid isPermaLink="false">http://texblog.wordpress.com/?p=52#comment-2155</guid>
		<description>The main problem I had with setting Awk scripts in verbatim mode is that single quotes are turned into curly apostrophes, making it awkward to copy and paste a typset example into a terminal or editor window to execute. Double quotes are OK in verbatim mode. Using lstlisting mode, ALL quotes are turned into curly quotes, one worse than verbatim.

Any ideas? The simplest thing to make a listing in any mode without curling quotes would be good. Thanks.</description>
		<content:encoded><![CDATA[<p>The main problem I had with setting Awk scripts in verbatim mode is that single quotes are turned into curly apostrophes, making it awkward to copy and paste a typset example into a terminal or editor window to execute. Double quotes are OK in verbatim mode. Using lstlisting mode, ALL quotes are turned into curly quotes, one worse than verbatim.</p>
<p>Any ideas? The simplest thing to make a listing in any mode without curling quotes would be good. Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nguyenminhhaivn</title>
		<link>http://texblog.wordpress.com/2008/04/02/include-source-code-in-latex-with-listings/#comment-2132</link>
		<dc:creator>nguyenminhhaivn</dc:creator>
		<pubDate>Wed, 12 Nov 2008 12:10:40 +0000</pubDate>
		<guid isPermaLink="false">http://texblog.wordpress.com/?p=52#comment-2132</guid>
		<description>@steven: You&#039;ve said &quot;The resulting text just looks ugly with incredibly bad spacing - the character kerning is completely messed up&quot;. I finally found out that the ``columns&#039;&#039; option can solve your problem. The complete command is \lstset{columns=fullflexible}.</description>
		<content:encoded><![CDATA[<p>@steven: You&#8217;ve said &#8220;The resulting text just looks ugly with incredibly bad spacing &#8211; the character kerning is completely messed up&#8221;. I finally found out that the &#8220;columns&#8221; option can solve your problem. The complete command is \lstset{columns=fullflexible}.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Python</title>
		<link>http://texblog.wordpress.com/2008/04/02/include-source-code-in-latex-with-listings/#comment-2060</link>
		<dc:creator>Joe Python</dc:creator>
		<pubDate>Tue, 28 Oct 2008 15:39:47 +0000</pubDate>
		<guid isPermaLink="false">http://texblog.wordpress.com/?p=52#comment-2060</guid>
		<description>If you have python distribution in your machine you can use &#039;pygmentize&#039;. Using pygmentize you can also generate syntax highlighted code in Word, html and pdf formats besides LateX.</description>
		<content:encoded><![CDATA[<p>If you have python distribution in your machine you can use &#8216;pygmentize&#8217;. Using pygmentize you can also generate syntax highlighted code in Word, html and pdf formats besides LateX.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2008-10-18 &#171; Iveney&#8217;s Weblog</title>
		<link>http://texblog.wordpress.com/2008/04/02/include-source-code-in-latex-with-listings/#comment-1988</link>
		<dc:creator>links for 2008-10-18 &#171; Iveney&#8217;s Weblog</dc:creator>
		<pubDate>Sat, 18 Oct 2008 15:02:35 +0000</pubDate>
		<guid isPermaLink="false">http://texblog.wordpress.com/?p=52#comment-1988</guid>
		<description>[...] Include source code in Latex with “Listings” « Blog on Latex Matters (tags: listings latex src) [...]</description>
		<content:encoded><![CDATA[<p>[...] Include source code in Latex with “Listings” « Blog on Latex Matters (tags: listings latex src) [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
