<?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; CTAN</title>
	<atom:link href="http://www.texdev.net/tag/ctan/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>A new upload system for CTAN</title>
		<link>http://www.texdev.net/2010/09/20/a-new-upload-system-for-ctan/</link>
		<comments>http://www.texdev.net/2010/09/20/a-new-upload-system-for-ctan/#comments</comments>
		<pubDate>Mon, 20 Sep 2010 19:48:59 +0000</pubDate>
		<dc:creator>Joseph Wright</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[CTAN]]></category>

		<guid isPermaLink="false">http://www.texdev.net/?p=810</guid>
		<description><![CDATA[The CTAN Team are currently testing a new upload system. There are several things going on with this new approach. First, if your material has been uploaded before then you can find it on the list of known packages, so various pieces of information are automatically available. Secondly, you can see the meta-data about your [...]]]></description>
			<content:encoded><![CDATA[<p>The <a href="http://www.ctan.org/">CTAN</a> Team are currently testing a <a href="http://az.ctan.org/send/">new upload system</a>. There are several things going on with this new approach. First, if your material has been uploaded before then you can find it on the list of known packages, so various pieces of information are automatically available. Secondly, you can see the meta-data about your upload, for example the short README-like text you see in the CTAN database. That means you can correct/add to the entry, and hopefully makes Robin Fairbairns life a little less busy!</p>
<p>The default page for uploads includes a list of all of the packages that CTAN contains (more or less: I&#8217;ve not checked the entire list!). There&#8217;s also <a href="http://az.ctan.org/send/enter_pkg">a page</a> you can use if you know the package name for your upload. I like that one, perhaps as I know the names of all of my packages and the aforementioned list is rather long!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.texdev.net/2010/09/20/a-new-upload-system-for-ctan/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Cross-platform working</title>
		<link>http://www.texdev.net/2009/08/18/cross-platform-working/</link>
		<comments>http://www.texdev.net/2009/08/18/cross-platform-working/#comments</comments>
		<pubDate>Tue, 18 Aug 2009 19:49:12 +0000</pubDate>
		<dc:creator>Joseph Wright</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[7-Zip]]></category>
		<category><![CDATA[CTAN]]></category>
		<category><![CDATA[Info-Zip]]></category>
		<category><![CDATA[TDS]]></category>
		<category><![CDATA[Unix]]></category>
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://www.texdev.net/?p=382</guid>
		<description><![CDATA[As many people will know, the CTAN team have come up with the idea of having TDS-ready zip files for packages. The idea is that you can just download the zip into your local TeX directory, unzip it and run texhash, with no TeX-based unpacking or document compilation. That&#8217;s all fine when it works, but [...]]]></description>
			<content:encoded><![CDATA[<p>As many people will know, the <a title="The Comprehensive TeX Archive Network" href="http://www.ctan.org">CTAN</a> team have come up with the idea of having TDS-ready zip files for packages. The idea is that you can just download the zip into your local TeX directory, unzip it and run texhash, with no TeX-based unpacking or document compilation.</p>
<p>That&#8217;s all fine when it works, but I&#8217;ve recently had a bit of trouble making zips at my end. My favoured tool for doing that has tended to be <a title="7-Zip" href="http://www.7-zip.org">7-Zip</a>. However, it was pointed out to me last week that the resulting zip files are not quite right. On Unix systems, the command <code>unzip -xa</code> will convert line endings to the system convention (LF only), even if they come from Windows (LF-CR endings). However, this requires that the zip identifies text files, and 7-Zip marks everything as binary!</p>
<p>I did a bit of hunting around, and found <a title="Info-ZIP Homepage" href="http://www.info-zip.org">Info-ZIP</a>, where after a bit of hunting about you can find <code>zip</code> and <code>unzip</code> binaries for Windows. These give me Unix-like capabilities on Windows, so I can make the appropriate files, alter line endings on zipping/unzipping and check the results.</p>
<p>That led me to take another look at the batch file I use  each time I release something to CTAN: doing it by hand is an unreliable business!  I&#8217;ve reworked it quite a bit, to generalise everything and also add a few tweaks. For anyone interested, the file is <a href="http://www.texdev.net/wp-content/uploads/2009/08/make.bat">available here</a>. It&#8217;s called make, so that you get Unix-like abilities on Windows. The file has to be customised for each package I write, but most of this version is generalised, and can be altered using a few settings.</p>
<pre>set AUXFILES=aux cmds dvi glo gls hd idx ilg ind ist log los out tmp toc
set CLEAN=bib bst cls eps gz ins cfg pdf sty tex txt zip
set DOCEXTRA=\AtBeginDocument{\OnlyDescription}
set INDEXFILE=gglo
set PACKAGE=achemso
set PDF=%PACKAGE%
set TDSROOT=latex\%PACKAGE%
set TEX=achemso-demo
set TXT=README
set UNPACK=%PACKAGE%.dtx</pre>
<p>Anyone at all familiar with batch files will see that this is a block of environmental variables: in this case, these are the settings for my <a title=" 	Support for American Chemical Society journal submissions" href="http://tug.ctan.org/cgi-bin/ctanPackageInformation.py?id=achemso">achemso</a> package. Most are pretty obvious settings, but in case anyone wants to use the file for their own purposes:</p>
<ul>
<li><code>AUXFILES</code> File types to delete after every run: throw away files.</li>
<li><code>CLEAN</code> File types deleted only if make clean is run: useful stuff.</li>
<li><code>DOCEXTRA</code> Inserted when creating documentation, can be anything. I don&#8217;t typeset the code for my packages in the release documents, hence the <code>\OnlyDescription</code> setting.</li>
<li><code>INDEXFILE</code> This is always <code>gglo</code> for documents using the <code>ltxdoc</code> class, but is <code>l3doc</code> if using the LaTeX3 class <code>l3doc</code>.</li>
<li><code>PACKAGE</code> Pretty obvious, the bundle name!</li>
<li><code>PDF</code> The names of PDF files to add to the documentation part of a TDS zip. By having this as a setting, special effects (demo documents, for example) are possible.</li>
<li><code>TDSROOT.</code> Almost always as given for a LaTeX package.</li>
<li><code>TEX</code> A list of .tex files to copy into the TDS archive: to avoid any testing files, not all .tex files are copied.</li>
<li><code>TXT</code> The names of text files to copy to the documentation directory</li>
<li><code>UNPACK</code> The file(s) to run to unpack the package. I use .dtx files that are self-extracting, but the traditional method is to have a separate .ins file.</li>
</ul>
<p>If the batch file proves useful to enough people, I might write some proper documentation and do a bit more generalisation.</p>
<p>With all of that in place, I can hopefully keep Unix-based LaTeX users happy without too much work!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.texdev.net/2009/08/18/cross-platform-working/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
	</channel>
</rss>

