<?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; siunitx</title>
	<atom:link href="http://www.texdev.net/category/latex/siunitx/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.texdev.net</link>
	<description>Coding in the TeX world</description>
	<lastBuildDate>Sun, 22 Jan 2012 10:34:39 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>siunitx v2.4 beta</title>
		<link>http://www.texdev.net/2011/11/09/siunitx-v2-4-beta/</link>
		<comments>http://www.texdev.net/2011/11/09/siunitx-v2-4-beta/#comments</comments>
		<pubDate>Wed, 09 Nov 2011 18:49:10 +0000</pubDate>
		<dc:creator>Joseph Wright</dc:creator>
				<category><![CDATA[siunitx]]></category>

		<guid isPermaLink="false">http://www.texdev.net/?p=1174</guid>
		<description><![CDATA[Development of the next release of siunitx has gone quite smoothly: I&#8217;ve added a few new features, and there is now nothing outstanding for v2.4. So it is time to ask for some volunteers to test the code. In terms of new features, I have added the a choice of rounding modes modes the ability [...]]]></description>
			<content:encoded><![CDATA[<p>Development of the next release of <a href="http://ctan.org/pg/siunitx">siunitx</a> has gone quite smoothly: I&#8217;ve added a few new features, and there is now nothing outstanding for v2.4. So it is time to ask for some volunteers to test the code.</p>
<p>In terms of new features, I have added the a <a href="https://bitbucket.org/josephwright/siunitx/issue/40/choice-of-methods-for-rounding-exactly">choice of rounding modes</a> modes the ability to <a href="https://bitbucket.org/josephwright/siunitx/issue/62/more-possibilities-for-the-sirange-and">compress down exponents in ranges and lists</a>, both long-standing feature requests. In response to a <a href="http://tex.stackexchange.com/q/32925/73">recent TeX.sx question</a>, siunitx can now also<a href="https://bitbucket.org/josephwright/siunitx/issue/173/convert-scientific-notation-to-si-prefix"> turn exponents into unit prefixes</a>. At a lower level, I&#8217;ve also altered some of the options internally so fewer of the assume math mode.</p>
<p>To test, please download the <a href="http://www.texdev.net/wp-content/uploads/2011/11/siunitx.tds_.zip">ready to install TDS-style .zip</a> file and install it locally. You should then be good to go. Feedback as a <a href="https://bitbucket.org/josephwright/siunitx/issues?status=new&amp;status=open">bug report</a> or <a href="mailto:joseph.wright@morningstar2.co.uk">by e-mail</a> welcome, as always. Assuming there are no problems, I&#8217;d expect to upload to <a href="http://www.ctan.org/">CTAN</a> by the end of the month.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.texdev.net/2011/11/09/siunitx-v2-4-beta/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Which siunitx options to set globally?</title>
		<link>http://www.texdev.net/2011/07/17/which-siunitx-options-to-set-globally/</link>
		<comments>http://www.texdev.net/2011/07/17/which-siunitx-options-to-set-globally/#comments</comments>
		<pubDate>Sun, 17 Jul 2011 15:08:14 +0000</pubDate>
		<dc:creator>Joseph Wright</dc:creator>
				<category><![CDATA[LaTeX]]></category>
		<category><![CDATA[siunitx]]></category>

		<guid isPermaLink="false">http://www.texdev.net/?p=1048</guid>
		<description><![CDATA[On the TeX.SX site recently, there was some discussion about locally over-riding the round-mode = places setting in my siunitx package. One thing this highlights for me is the need to think about which settings to apply globally. Some siunitx settings are about consistency of appearance, and seem to apply naturally to entire documents. A [...]]]></description>
			<content:encoded><![CDATA[<p>On the <a href="http://tex.stackexchange.com/">TeX.SX</a> site recently, there was some discussion about <a href="http://tex.stackexchange.com/q/23193/73">locally over-riding the <code>round-mode = places</code> setting</a> in my <a title="A comprehensive (SI) units package" href="http://ctan.org/pkg/siunitx">siunitx</a> package. One thing this highlights for me is the need to think about which settings to apply globally.</p>
<p>Some siunitx settings are about consistency of appearance, and seem to apply naturally to entire documents. A classic example would be <code>output-decimal-marker</code>: if you are using <code>,</code> as a decimal marker, it should apply everywhere!</p>
<p>However, this is not so clear-cut for many of the options related to number-manipulation. The rounding options in particular are really intended for the case where you have some auto-generated data (say a long list from an instrument), and the real accuracy is not as great as the apparent precision. Instruments are great at providing lots of numbers, but it takes a bit of human thought to decide how many of these are really relevant. So for these cases, setting an appropriate rounding scheme is perfectly sensible.</p>
<p>On the other hand, for a number you&#8217;ve typed in yourself I&#8217;d hope that you&#8217;ve done the thinking part when the number is typed, so rounding by the computer is not needed. That suggests to me that most of the time rounding should not be set as a global option.</p>
<p>Of course, it will depend on the exact nature of the document in question. If all of the data in a document is in tables, all of which need rounding, then there is a performance gain from setting the rounding once globally. So the best I can say, guidance-wise, is ‘think about <em>your</em> document’!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.texdev.net/2011/07/17/which-siunitx-options-to-set-globally/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>siunitx v2.3: consolidation</title>
		<link>http://www.texdev.net/2011/05/30/siunitx-v2-3-consolidation/</link>
		<comments>http://www.texdev.net/2011/05/30/siunitx-v2-3-consolidation/#comments</comments>
		<pubDate>Mon, 30 May 2011 17:36:49 +0000</pubDate>
		<dc:creator>Joseph Wright</dc:creator>
				<category><![CDATA[siunitx]]></category>

		<guid isPermaLink="false">http://www.texdev.net/?p=1025</guid>
		<description><![CDATA[I&#8217;m making a start on the next release of siunitx: v2.3. There are a number of issues in the database targeting this release, and these are mainly about dealing with things behind the scenes. Some options need revision, and I need to improve the table code somewhat. However, I doubt that there will be much [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m making a start on the next release of <a title="A comprehensive (SI) units package" href="http://ctan.org/pkg/siunitx">siunitx</a>: v2.3. There are a number of <a href="https://bitbucket.org/josephwright/siunitx/issues?milestone=v2.3">issues in the database</a> targeting this release, and these are mainly about dealing with things behind the scenes. Some options need revision, and I need to improve the table code somewhat. However, I doubt that there will be much to excite users. That&#8217;s not necessarily a bad thing: there seem to be a lot of siunitx users, and I don&#8217;t want to break the code! Of course, if there is a particular issue that needs addressing then the usual rule applies: <a href="mailto:joseph.wright@morningstar2.co.uk">make a case to me</a> and I&#8217;ll see what I can do.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.texdev.net/2011/05/30/siunitx-v2-3-consolidation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>siunitx v2.2 released</title>
		<link>http://www.texdev.net/2011/04/14/siunitx-v2-2-released/</link>
		<comments>http://www.texdev.net/2011/04/14/siunitx-v2-2-released/#comments</comments>
		<pubDate>Thu, 14 Apr 2011 07:24:54 +0000</pubDate>
		<dc:creator>Joseph Wright</dc:creator>
				<category><![CDATA[LaTeX]]></category>
		<category><![CDATA[siunitx]]></category>

		<guid isPermaLink="false">http://www.texdev.net/?p=1006</guid>
		<description><![CDATA[As I detailed a little while ago, I&#8217;ve been working on v2.2 of siunitx. I&#8217;ve now released the latest version, v2.2, to CTAN. There are a number of small changes, introducing new features, but I thought I would highlight a few. A long-standing feature request has been to be able to use the cancel package [...]]]></description>
			<content:encoded><![CDATA[<p>As I <a href="http://www.texdev.net/2011/03/20/sorting-issues-for-consideration-for-siunitx-v2-2/">detailed a little while ago</a>, I&#8217;ve been working on v2.2 of <a href="http://ctan.org/pkg/siunitx">siunitx</a>. I&#8217;ve now released the latest version, v2.2, to <a href="http://www.ctan.org/">CTAN</a>. There are a number of small changes, introducing new features, but I thought I would highlight a few.</p>
<p>A long-standing feature request has been to be able to use the <a href="http://ctan.org/pkg/cancel">cancel</a> package to show how units cancel out. This is useful for teaching, although it&#8217;s not of course part of the usual typesetting of units for publication. It turns out not to be too hard to allow this, so that you can now use input such as</p>
<pre>\si[per-mode = fraction]{\cancel\kg\m\per\s\cancel\kg}</pre>
<p>and have it come out properly. At the same time, I&#8217;ve made it possible to highlight particular units</p>
<pre>\si{\highlight{green}\square\metre\candela\second}</pre>
<p>again for teaching-related purposes.</p>
<p>A second long-standing request is to be able to parse uncertainties given in the form</p>
<pre>\num{1.23 +- 0.15}</pre>
<p>which was something more of challenge, but again is now working properly. So you can get the same output from the above and from</p>
<pre>\num{1.23(15)}.</pre>
<p>A final highlight is the new <code>\tablenum</code> macro. This is needed for aligning numbers inside <code>\multicolumn</code> and <code>\multirow</code>, which otherwise does not work. (At a technical level, both <code>\multicolumn</code> and <code>\mutirow</code> use the <code>\omit</code> primitive, and so the code inserted by the <code>S</code> column is not used. The <code>\tablenum</code> macro effectively makes the same approach available as a stand-alone function.)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.texdev.net/2011/04/14/siunitx-v2-2-released/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Sorting issues for consideration for siunitx v2.2</title>
		<link>http://www.texdev.net/2011/03/20/sorting-issues-for-consideration-for-siunitx-v2-2/</link>
		<comments>http://www.texdev.net/2011/03/20/sorting-issues-for-consideration-for-siunitx-v2-2/#comments</comments>
		<pubDate>Sun, 20 Mar 2011 10:57:17 +0000</pubDate>
		<dc:creator>Joseph Wright</dc:creator>
				<category><![CDATA[LaTeX]]></category>
		<category><![CDATA[siunitx]]></category>

		<guid isPermaLink="false">http://www.texdev.net/?p=962</guid>
		<description><![CDATA[I&#8217;ve been leaving siunitx alone for a while, concentrating on bug fixes in the v2.1 branch. The  list of issues has continued to grow, and I&#8217;m now getting some organisation done before starting on items for v2.2. Some of these are more likely to get tackled, some rather less likely, but it&#8217;s best to get [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve been leaving <a title="A comprehensive (SI) units package" href="http://ctan.org/pkg/siunitx"><code>siunitx</code></a> alone for a while, concentrating on bug fixes in the v2.1 branch. The  <a href="https://bitbucket.org/josephwright/siunitx/issues?status=new&amp;status=open">list of issues</a> has continued to grow, and I&#8217;m now getting some organisation done before starting on items for v2.2. Some of these are more likely to get tackled, some rather less likely, but it&#8217;s best to get everything logged! If you look at the <a href="https://bitbucket.org/josephwright/siunitx/issues?status=resolved&amp;status=invalid&amp;status=duplicate">closed issues</a>, you&#8217;ll see that part of getting organised is closing some bugs where I don&#8217;t feel that it is appropriate to take action. What I would say is that if you&#8217;ve got something you&#8217;d like considering, put it into the database. I do try to keep up with ideas by <a href="mailto:joseph.wright@morningstar2.co.uk">e-mail</a> or from forums, but do forget some.</p>
<p>On particular thing I want to think about is the naming is some options and macros. I&#8217;ve had some discussion with Marcus Foster from <a title="Commonwealth Scientific and Research Organisation" href="http://www.csiro.au/">CSIRO Information Management &amp; Technology</a> about <code>siunitx</code>, and he&#8217;s pointed out various errors on my part. Some of those, in the documentation, have been fixed. At the code level, he pointed out that what <code>\SI</code> prints are properly called quantities, and that units are separated by products. So I&#8217;m thinking of some reasonably radical renaming of <a href="https://bitbucket.org/josephwright/siunitx/issue/116/">macros</a> and <a href="https://bitbucket.org/josephwright/siunitx/issue/115/">options</a> (with the old ones retained, of course!). Feedback on these ideas would be welcome. At the same time, he&#8217;s not at all keen on the ‘qualifiers’ concept, but on that I think users would not be happy if I removed it!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.texdev.net/2011/03/20/sorting-issues-for-consideration-for-siunitx-v2-2/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Installing achemso and siunitx</title>
		<link>http://www.texdev.net/2010/12/27/installing-achemso-and-siunitx/</link>
		<comments>http://www.texdev.net/2010/12/27/installing-achemso-and-siunitx/#comments</comments>
		<pubDate>Mon, 27 Dec 2010 21:36:16 +0000</pubDate>
		<dc:creator>Joseph Wright</dc:creator>
				<category><![CDATA[achemso]]></category>
		<category><![CDATA[LaTeX]]></category>
		<category><![CDATA[siunitx]]></category>
		<category><![CDATA[installation]]></category>

		<guid isPermaLink="false">http://www.texdev.net/?p=856</guid>
		<description><![CDATA[A question that comes up from time to time is how to install one or other of my packages, usually either achemso or siunitx. While both are essentially standard LaTeX packages (no weird files or binaries needed), there are still soem stumbling blocks that cause issues. So I thought a few notes by be useful [...]]]></description>
			<content:encoded><![CDATA[<p>A question that comes up from time to time is how to install one or other of my packages, usually either <a title=" 	Support for American Chemical Society journal submissions" href="http://ctan.org/pkg/achemso">achemso</a> or <a title="A comprehensive (SI) units package" href="http://ctan.org/pkg/siunitx">siunitx</a>. While both are essentially standard LaTeX packages (no weird files or binaries needed), there are still soem stumbling blocks that cause issues. So I thought a few notes by be useful here.</p>
<h2>Installing as part of an up to date TeX system</h2>
<p>By far the easiest way to install my LaTeX packages is to get them as part an up to date TeX system. Both <a title="MiKTeX" href="http://www.miktex.org/">MikTeX 2.9</a> and <a title="TeX Live" href="http://www.tug.org/texlive">TeX Live 2010</a> include all of my general packages. MiKTeX is of course Windows-only, but TeX Live can be installed on Windows, Mac OS X and Linux. After installation, doing an on-line update should grab all of the latest packages from <a title="The Comprehensive TeX Archive Network" href="http://www.ctan.org/">CTAN</a>. Both MiKTeX and TeX Live include graphical update programs, so this is not such a difficult process nowadays.</p>
<p>Mac users may well prefer <a title="MacTeX" href="http://www.tug.org/mactex">MacTeX</a> over plain TeX Live, but MacTeX is built on top of TeX Live and so the same ideas apply. You can install either TeX Live or MacTeX and get the same basic functionality.</p>
<p>For Linux users, it&#8217;s worth noting that popular Linux distributions tend to include old versions of TeX Live (or even teTeX), rather than TeX Live 2010. So if you want an up-to-date TeX system you&#8217;ll be better off ignoring your Linux package manager and grabbing TeX Live directly.</p>
<p>One thing to do if you update your TeX system is to check any locally-installed files you might have (see the next section for more about local installation). These will be in <code>~/texmf</code> on Linux, <code>~/Library/texmf</code> on a Mac and (probably) <code>%USERPROFILE%\texmf</code> on Windows. One problem I see from time to time is that users of achemso have installed some of the BibTeX styles locally, then update the main package and all sorts of things go wrong. So do check carefully on any local files: they might be outdated by a new TeX system.</p>
<h2>Installing using the TDS zip files</h2>
<p>The method above is fine if you are happy installing an entirely new TeX system, but if all you need is access to one of my packages then it is probably over-kill. For these users, I provide ready-to-install zip files on CTAN. For achemso, you need <a href="http://www.ctan.org/cgi-bin/filenameSearch.py?filename=achemso.tds.zip&amp;Search=Search">achemso.tds.zip</a>, while for siunitx users you probably need</p>
<ul>
<li><a href="http://www.ctan.org/cgi-bin/filenameSearch.py?filename=siunitx.tds.zip&amp;Search=Search">siunitx.tds.zip</a></li>
<li><a href="http://www.ctan.org/cgi-bin/filenameSearch.py?filename=expl3.tds.zip&amp;Search=Search">expl3.tds.zip</a></li>
<li><a href="http://www.ctan.org/cgi-bin/filenameSearch.py?filename=xpackages.tds.zip&amp;Search=Search">xpackages.tds.zip</a></li>
</ul>
<p>The idea with these files is that I have set them up with documentation, ready to use LaTeX styles and all of the support files. All that needs to happen with them is to unzip them inside your local TeX directory and tell TeX about them.</p>
<p>Where the files should go depends a little on your operating system. The local directory (folder) is usually <code>~/texmf</code> on Linux, <code>~/Library/texmf</code> on a Mac and (probably) <code>%USERPROFILE%\texmf</code> on Windows. Here, <code>~</code> and <code>%USERPROFILE%</code> represent your home directory (folder). So on my Windows 7 PC, I have a folder</p>
<pre>C:\Users\joseph\texmf</pre>
<p>while on my Mac there is one at</p>
<pre>/Users/joseph/Library/texmf</pre>
<p>Whichever system you use, copy the appropriate zip files there and unzip. The result should be a structure which looks like</p>
<pre>texmf/tex/latex/achemso/achemso.sty
...
texmf/tex/latex/siunitx/siunitx.sty</pre>
<p>and so on. Of course, the exact structure will depend on which packages you install! What is important for installing siunitx is to also install expl3 and xpackages. If the versions do not match then trouble will not be far away.</p>
<p>To tell TeX about the new files, you need to run the program <code>texhash</code>. There is a graphical interface for this in both MiKTeX (<em>Update File Name Database</em>) and TeX Live. I find it easiest just to start a Command Prompt/Terminal and type</p>
<pre>texhash</pre>
<p>[For users with recent versions of TeX Live (2009 and 2010, I think), running <code>texhash</code> is actually not needed. However, it will not do any harm so you may as well run it.)</p>
<h2>Installing from the dtx file</h2>
<p>The traditional method to install a package is to unpack it from the dtx source. I&#8217;ve got to say that I only recommend this for experienced LaTeX users. While both achemso and siunitx are designed to be easy to unpack, life is more complex for expl3 and xpackages. So I&#8217;d strongly recommed using the TDS zip files unless you know a bit more about LaTeX!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.texdev.net/2010/12/27/installing-achemso-and-siunitx/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>siunitx: testing for v2.1 release</title>
		<link>http://www.texdev.net/2010/10/27/siunitx-testing-for-v2-1-release/</link>
		<comments>http://www.texdev.net/2010/10/27/siunitx-testing-for-v2-1-release/#comments</comments>
		<pubDate>Wed, 27 Oct 2010 17:45:34 +0000</pubDate>
		<dc:creator>Joseph Wright</dc:creator>
				<category><![CDATA[LaTeX]]></category>
		<category><![CDATA[siunitx]]></category>

		<guid isPermaLink="false">http://www.texdev.net/?p=835</guid>
		<description><![CDATA[Anyone who follows the BitBucket repository for siunitx will have seen that I&#8217;ve made a lot of commits over recent days. If you look at the list of open issues, you&#8217;ll also see that it&#8217;s got smaller and that some have been moved from targeting v2.1 to targeting v2.2. I&#8217;ve been aiming to get v2.1 [...]]]></description>
			<content:encoded><![CDATA[<p>Anyone who follows the <a href="http://bitbucket.org/josephwright/siunitx/">BitBucket repository</a> for <a title="A comprehensive (SI) units package" href="http://ctan.org/pkg/siunitx">siunitx</a> will have seen that I&#8217;ve made a lot of <a href="http://bitbucket.org/josephwright/siunitx/changesets">commits</a> over recent days. If you look at the list of <a href="http://bitbucket.org/josephwright/siunitx/issues?status=new&amp;status=open">open issues</a>, you&#8217;ll also see that it&#8217;s got smaller and that some have been moved from targeting v2.1 to <a href="http://bitbucket.org/josephwright/siunitx/issues?status=new&amp;status=open&amp;milestone=v2.2">targeting v2.2</a>. I&#8217;ve been aiming to get v2.1 finished this month, and I&#8217;ve been working out what I can and can&#8217;t do in that time frame.</p>
<p>The result is that the <a href="http://bitbucket.org/josephwright/siunitx/src/tip/siunitx.dtx">code on BitBucket now</a> is what I&#8217;ll release as v2.1, baring any remaining bug fixes. The idea is to have some new features, but not so many that I&#8217;ll have introduced lots of new bugs. I hope that I&#8217;ve got the balance about right, and that there has been enough time for testing the new additions to the package. If all looks okay by the weekend I will be updating CTAN at the weekend. If you&#8217;d like to test it before then, either grab the code from BitBucket or, if you use TeX Live, try the <a href="http://tlcontrib.metatex.org/">TLcontrib</a> installation method.</p>
<p>I&#8217;m hoping to work on v2.2 for a release early in the new year, probably late January. There are already a <a href="http://bitbucket.org/josephwright/siunitx/issues?status=new&amp;status=open&amp;milestone=v2.2">few issues on the list for v2.2</a>, but that may alter if there is a good case made for something else. Of course, I&#8217;ll also have to avoid breaking anything!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.texdev.net/2010/10/27/siunitx-testing-for-v2-1-release/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Testing versions of siunitx v2.1 on TLcontrib</title>
		<link>http://www.texdev.net/2010/10/12/testing-versions-of-siunitx-v2-1-on-tlcontrib/</link>
		<comments>http://www.texdev.net/2010/10/12/testing-versions-of-siunitx-v2-1-on-tlcontrib/#comments</comments>
		<pubDate>Tue, 12 Oct 2010 18:41:02 +0000</pubDate>
		<dc:creator>Joseph Wright</dc:creator>
				<category><![CDATA[siunitx]]></category>
		<category><![CDATA[TLcontrib]]></category>

		<guid isPermaLink="false">http://www.texdev.net/?p=826</guid>
		<description><![CDATA[I&#8217;m working on the list of issues for siunitx v2.1. As I do, I hope that the code is staying usable at all times! The list is getting shorter (finally), so I&#8217;m hoping to get something released around the end of the month.  One thing that I need for that is testing. My recent post [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m working on the <a href="http://bitbucket.org/josephwright/siunitx/issues?status=new&amp;status=open&amp;milestone=v2.1">list of issues</a> for <a title="A comprehensvie (SI) units package" href="http://ctan.org/pkg/siunitx">siunitx</a> v2.1. As I do, I hope that the code is staying usable at all times! The list is getting shorter (finally), so I&#8217;m hoping to get something released around the end of the month.  One thing that I need for that is testing. My <a title="TeX Live packaging expands" href="http://www.texdev.net/2010/10/09/tex-live-packaging-expands/">recent post about TLcontrib</a> mentioned this as a route for testing packages prior to release. So I&#8217;m taking advantage, and sending snapshots of siunitx to TLcontrib each time I add a new feature. So if you want to help to test things out, then you can run</p>
<pre>tlmgr --repository http://tlcontrib.metatex.org/2010 update siunitx</pre>
<p>from your command prompt/terminal. Let me know about any new issues!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.texdev.net/2010/10/12/testing-versions-of-siunitx-v2-1-on-tlcontrib/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Time to take a look at the issues for siunitx v2.1</title>
		<link>http://www.texdev.net/2010/10/01/time-to-take-a-look-at-the-issues-for-siunitx-v2-1/</link>
		<comments>http://www.texdev.net/2010/10/01/time-to-take-a-look-at-the-issues-for-siunitx-v2-1/#comments</comments>
		<pubDate>Fri, 01 Oct 2010 20:30:28 +0000</pubDate>
		<dc:creator>Joseph Wright</dc:creator>
				<category><![CDATA[LaTeX]]></category>
		<category><![CDATA[siunitx]]></category>

		<guid isPermaLink="false">http://www.texdev.net/?p=815</guid>
		<description><![CDATA[The list of issues for siunitx has been growing for a while. I&#8217;ve been holding off work on the bigger issues while bugs in v2.0 have come up, as I&#8217;d prefer to have something that works for most people now rather than try to add more new features too soon. At the same time, I&#8217;m [...]]]></description>
			<content:encoded><![CDATA[<p>The <a href="http://bitbucket.org/josephwright/siunitx/issues?status=new&amp;status=open">list of issues</a> for <a href="http://ctan.org/pkg/siunitx">siunitx</a> has been growing for a while. I&#8217;ve been holding off work on the bigger issues while bugs in v2.0 have come up, as I&#8217;d prefer to have something that works for most people now rather than try to add more new features too soon. At the same time, I&#8217;m also busy working on <a href="http://www.latex-project.org/latex3.html">other things</a>. However, I&#8217;ve been prodded by a few users to make a start on some of the feature requests. I do aim to please, so I&#8217;m going to make a start on the list.</p>
<p>Of course, just because I look at something does not mean I&#8217;ll do it. I decided to start simple, and took a look at <a href="http://bitbucket.org/josephwright/siunitx/issue/71/kerning-of-femto-prefix">issue 71</a>. The question here was about automatically adding kerning for things like <code>\femto\farad</code>, as the kerning in Computer Modern is not good here. I did write some code, but looking at it decided that this is too close to the font choice for me. So I&#8217;ve closed the issue as &#8216;WONTFIX&#8217;. I&#8217;ll see whether this sticks or whether there is a lot of demand for such a feature.</p>
<p>The plan is to get on with adding features and fixing more complex issues over the next few weeks. I never leave the code unusable (I use the development version as my day-to-day workhorse), so you can grab the .dtx file and try things out if you like. I&#8217;ll post again if there are any particular new features or changes that need a try out.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.texdev.net/2010/10/01/time-to-take-a-look-at-the-issues-for-siunitx-v2-1/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The trouble with getting things right</title>
		<link>http://www.texdev.net/2010/06/25/the-trouble-with-getting-things-right/</link>
		<comments>http://www.texdev.net/2010/06/25/the-trouble-with-getting-things-right/#comments</comments>
		<pubDate>Fri, 25 Jun 2010 07:33:36 +0000</pubDate>
		<dc:creator>Joseph Wright</dc:creator>
				<category><![CDATA[LaTeX]]></category>
		<category><![CDATA[siunitx]]></category>

		<guid isPermaLink="false">http://www.texdev.net/?p=752</guid>
		<description><![CDATA[I work hard on my LaTeX packages, and try to get things to work well for the user with clear interfaces. However, there is a down side to this: I get asked to do more things! For example, I&#8217;ve recently released version 2 of siunitx. This builds on the work from version 1, which itself [...]]]></description>
			<content:encoded><![CDATA[<p>I work hard on my LaTeX packages, and try to get things to work well for the user with clear interfaces. However, there is a down side to this: I get asked to do more things! For example, I&#8217;ve recently released version 2 of <a title="A comprehensive (SI) units package" href="http://tug.ctan.org/pkg/siunitx">siunitx</a>. This builds on the work from version 1, which itself was designed as an improvement to various earlier unit packages for LaTeX. I did remove a few features when I moved from version 1 to version 2, but in the main each new version of siunitx has added ‘more stuff’ to the package. However, I&#8217;ve also got organised with tracking bugs and feature requests using <a href="http://www.bitbucket.org/josephwright/">BitBucket</a>. The resulting <a href="http://www.bitbucket.org/josephwright/siunitx/issues?status=new&amp;status=open">list of open issues</a> is already quite frightening (at least for me). I&#8217;ve been keeping up with the bugs in the new release (I try to deal with them within a few days of being reported), so the list is all made up of feature requests, and almost all of those are new things. So the package being successful results in more work for me, not less. I&#8217;m not complaining: I want things to work. It&#8217;s just worth bearing in mind!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.texdev.net/2010/06/25/the-trouble-with-getting-things-right/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

