<?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: Breaking lines in siunitx version 2</title>
	<atom:link href="http://www.texdev.net/2009/03/07/breaking-lines-in-siunitx-version-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.texdev.net/2009/03/07/breaking-lines-in-siunitx-version-2/</link>
	<description>Coding in the TeX world</description>
	<lastBuildDate>Tue, 07 Feb 2012 20:07:12 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Stefan Pinnow</title>
		<link>http://www.texdev.net/2009/03/07/breaking-lines-in-siunitx-version-2/#comment-223</link>
		<dc:creator>Stefan Pinnow</dc:creator>
		<pubDate>Sun, 08 Mar 2009 12:08:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.texdev.net/?p=219#comment-223</guid>
		<description>I also think, that the only &quot;good&quot; point to break the value-unit-combo (if there is one) is between these two and not in between a value or unit.
I also think that that normally is not needed. One possibility where this could be needed, is in articles where small columns are printed. There a long value with a long unit could lead to weird looking lines.</description>
		<content:encoded><![CDATA[<p>I also think, that the only &#8220;good&#8221; point to break the value-unit-combo (if there is one) is between these two and not in between a value or unit.<br />
I also think that that normally is not needed. One possibility where this could be needed, is in articles where small columns are printed. There a long value with a long unit could lead to weird looking lines.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joseph Wright</title>
		<link>http://www.texdev.net/2009/03/07/breaking-lines-in-siunitx-version-2/#comment-211</link>
		<dc:creator>Joseph Wright</dc:creator>
		<pubDate>Sat, 07 Mar 2009 18:35:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.texdev.net/?p=219#comment-211</guid>
		<description>Hello Will,

I&#039;ve basically come down as you suggest: breaks between numbers and units yes, but not within units.

I didn&#039;t actually say I prefer non-literal units (although I always use the macro versions: logical input). I was taking about how they are handled as a package author. If the input is given in macro form, then there are no possible surprises and siunitx can handle them any way I can think of/code. On the other hand, if the input contains literals then my preference is to limit processing to converting &quot;.&quot; and &quot;~&quot; to spaces or symbols (as in sistyle).  I&#039;m very reluctant to do anything else, which includes adding line breaks. (I was asked if I could arrange for &quot;N/m.s&quot; to convert into \frac{N}{m.s}, for example: I&#039;ve said &quot;probably not&quot;.)</description>
		<content:encoded><![CDATA[<p>Hello Will,</p>
<p>I&#8217;ve basically come down as you suggest: breaks between numbers and units yes, but not within units.</p>
<p>I didn&#8217;t actually say I prefer non-literal units (although I always use the macro versions: logical input). I was taking about how they are handled as a package author. If the input is given in macro form, then there are no possible surprises and siunitx can handle them any way I can think of/code. On the other hand, if the input contains literals then my preference is to limit processing to converting &#8220;.&#8221; and &#8220;~&#8221; to spaces or symbols (as in sistyle).  I&#8217;m very reluctant to do anything else, which includes adding line breaks. (I was asked if I could arrange for &#8220;N/m.s&#8221; to convert into \frac{N}{m.s}, for example: I&#8217;ve said &#8220;probably not&#8221;.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Will</title>
		<link>http://www.texdev.net/2009/03/07/breaking-lines-in-siunitx-version-2/#comment-210</link>
		<dc:creator>Will</dc:creator>
		<pubDate>Sat, 07 Mar 2009 18:17:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.texdev.net/?p=219#comment-210</guid>
		<description>I don&#039;t mind the *option* to break between numbers and units (although I&#039;d never use it myself), but line-breaking between separate units in a dimensioned number seems like a bad idea to me.

Would you like to elaborate why you prefer non-literal units? I actually much prefer writing &quot;\SI{2.3}{N.m}&quot;.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t mind the *option* to break between numbers and units (although I&#8217;d never use it myself), but line-breaking between separate units in a dimensioned number seems like a bad idea to me.</p>
<p>Would you like to elaborate why you prefer non-literal units? I actually much prefer writing &#8220;\SI{2.3}{N.m}&#8221;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

