<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Some TeX Developments &#187; graphicx</title>
	<atom:link href="http://www.texdev.net/tag/graphicx/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.texdev.net</link>
	<description>Coding in the TeX world</description>
	<lastBuildDate>Thu, 26 Aug 2010 17:47:37 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
		<item>
		<title>Change for the better</title>
		<link>http://www.texdev.net/2009/03/05/change-for-the-better/</link>
		<comments>http://www.texdev.net/2009/03/05/change-for-the-better/#comments</comments>
		<pubDate>Thu, 05 Mar 2009 19:50:43 +0000</pubDate>
		<dc:creator>Joseph Wright</dc:creator>
				<category><![CDATA[LaTeX]]></category>
		<category><![CDATA[BibTeX]]></category>
		<category><![CDATA[graphicx]]></category>
		<category><![CDATA[LaTeX community]]></category>
		<category><![CDATA[natbib]]></category>

		<guid isPermaLink="false">http://www.texdev.net/?p=215</guid>
		<description><![CDATA[There have been a couple of discussions recently, both concerned with “change for the better”. The first, on the LaTeX-L list, is about adding the ability to convert EPS graphics to PDF “on the fly”. The suggestion is to have the graphicx package load epstopdf automatically, and to arrange a limited version of \write18 that [...]]]></description>
			<content:encoded><![CDATA[<p>There have been a couple of discussions recently, both concerned with “change for the better”. The first, on the<a title="LaTeX3 Mailing list" href="http://news.gmane.org/gmane.comp.tex.latex.latex3/"> LaTeX-L list</a>, is about adding the ability to convert EPS graphics to PDF “on the fly”.  The suggestion is to have the graphicx package load epstopdf automatically, and to arrange a limited version of <code>\write18</code> that will only allow known commands to be run. That should let ordinary users include EPS files with pdfLaTeX without needing to worry about the detail.  A good thing, but it does raise one issue.  People who use updated versions of LaTeX will have this feature, but if they send their files to others who don&#8217;t, things won&#8217;t “just work”.  This can&#8217;t really be avoided: if you add a new feature, then people without the update get a different result from those who do have it. Not much you can do, if you want any change at all!</p>
<p>The second change has come up on the <a title="LaTeX Community" href="http://www.latex-community.org/">LaTeX Community</a> and <a title="(La)TeX Usenet group, via Google" href="http://groups.google.com/group/comp.text.tex/topics">comp.text.tex</a>. The latest version of <a title="Flexible bibliography support" href="http://www.ctan.org/pkg/natbib">natbib</a> is rather more careful than earlier versions about the BibTeX style file used. This means that the latest version gives an error, where older versions silently change settings to “mind-read” what the user wants. This has lead to a lot of confusion, and some people recommending replacing the newer version with the old one! In the end, the change here is also for the better: the error that is causing problems (where the BibTeX style needs the “numbers” option, and it&#8217;s not been given) is perfectly sensible. But it also shows the dangers of mending or improving things: people get used to the sub-optimal behaviour, and think something is wrong when it is sorted out!</p>
<p>Conclusion: make change for the better, but be ready for complaints.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.texdev.net/2009/03/05/change-for-the-better/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
