## TeX Live on Windows

As I posted earlier, the upcoming releases of both MiKTeX and TeX Live have very similar sets of features on Windows. I’ve just stumbled upon something that points up the slight differences that exist, even though this one is a bit complicated.

To detect what system is being used, for things like shell escape tricks, there is a LaTeX package called ifplatform. However, this only works on Windows if MiKTeX is being used. The reason is that while TeX Live aims to be as similar as possible across platforms, MiKTeX can adopt a different approach and stick to Windows conventions. Most of the time, this is transparent but it shows up if you use the `-shell-escape` option for either system and try to do some testing. Inside ifplatform, you’ll find the lines:

```\edef\ip@sig{write18-test-\the\year\the\month\the\day\the\time}
\edef\ip@win{'\ip@sig'}
\immediate\write18{echo \ip@win >"\ip@file"}```

The idea is that the text written to the temporary file will be different on Windows to on a Unix-like system. MiKTeX will retain the single quotes around the test data:

`'write18-test-20098231074'`

whereas Unix-like systems will not:

`write18-test-20098231074`

But try using ifplatform with TeX Live on Windows and the test fails. First, no test file gets written at all: a bit of hacking leads to the change of the write line to

`\immediate\write18{echo \ip@win > \ip@file}`

and then at least the first step works. However, the test file now looks like a Unix one (with no quote marks), and ifplatform gets things wrong. So for the moment the only thing to do is create a stub package file and use it, something like:

```\ProvidesPackage{ifplatform}[2007/11/18 v0.2  Testing for the operating system]
\newif\ifshellescape\shellescapetrue
\newif\ifwindows\windowstrue
\newif\ifmacosx
\newif\iflinux```

I’ve reported the problem to Will Robertson, and hopefully a solution which really tests the OS rather than the TeX system can be found. However, it is a reminder that even with very general feature sets, the two major TeX distributions still act differently in some respects when used on Windows.

## LaTeX and Dalton Transactions

For once I have a post which combines TeX directly with my job. I’ve just received a copy of the proofs for an article in the chemistry journal Dalton Transactions (the article has DOI 10.1039/b907982c). At the top of each page I spotted

/usr/local/teTeX/share/texmf/tex/latex/techbooks/als/rsc/base2006/rsc2006v1.cls
(2004/07/27 v1.0 Standard LaTeX document class for RSC Journals)

The great irony is that although the journal (along with many others in chemistry) is typeset in LaTeX, they don’t accept LaTeX submissions! I’d love to get hold of that class file and have a look: pretty much no chance, unfortunately.

## TeXworks v0.1 release candidate

Jonathan Kew has posted new binaries for TeXworks, with the idea that these are a release candidate for version 0.1 (which will be in TeX Live 2009 on Windows). Over the past few builds, we’ve got an icon, installer and the ability to associate .tex files with TeXworks. So things already look pretty good to me. I’m not sure what exactly is planned for v0.2, but somewhere along the line the plan is to include scripting, so perhaps that’s the next big item to add. I’m already using TeXworks for my day-to-day work, so don’t be put off by the low version number.

## Cross-platform working

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’s all fine when it works, but I’ve recently had a bit of trouble making zips at my end. My favoured tool for doing that has tended to be 7-Zip. However, it was pointed out to me last week that the resulting zip files are not quite right. On Unix systems, the command `unzip -xa` 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!

I did a bit of hunting around, and found Info-ZIP, where after a bit of hunting about you can find `zip` and `unzip` 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.

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’ve reworked it quite a bit, to generalise everything and also add a few tweaks. For anyone interested, the file is available here. It’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.

```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 UNPACK=%PACKAGE%.dtx```

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 achemso package. Most are pretty obvious settings, but in case anyone wants to use the file for their own purposes:

• `AUXFILES` File types to delete after every run: throw away files.
• `CLEAN` File types deleted only if make clean is run: useful stuff.
• `DOCEXTRA` Inserted when creating documentation, can be anything. I don’t typeset the code for my packages in the release documents, hence the `\OnlyDescription` setting.
• `INDEXFILE` This is always `gglo` for documents using the `ltxdoc` class, but is `l3doc` if using the LaTeX3 class `l3doc`.
• `PACKAGE` Pretty obvious, the bundle name!
• `PDF` 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.
• `TDSROOT.` Almost always as given for a LaTeX package.
• `TEX` A list of .tex files to copy into the TDS archive: to avoid any testing files, not all .tex files are copied.
• `TXT` The names of text files to copy to the documentation directory
• `UNPACK` 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.

If the batch file proves useful to enough people, I might write some proper documentation and do a bit more generalisation.

With all of that in place, I can hopefully keep Unix-based LaTeX users happy without too much work!

## siunitx update

I’ve just sent a minor update of the release version of siunitx to CTAN. There was a clash with the fourier package, to do with maths fonts. This is all due to the lack of an upright μ in Computers Modern: a continued pain. For the moment, all is sorted again! One note: I’ve done the release here using TeX Live 2009, rather than my more usual MiKTeX 2.7. Everything seems to have worked, but any feedback is of course welcome!

## TUG 2009 Videos

For those of us who couldn’t make TUG 2009, the excellent people at River Valley Technologies have recorded the talks. They are appearing a few at a time, and to quote the site:

Talks will be uploaded as post-processing is completed. Please note that we had some technical problems on day 1, so they may take longer to prepare.

I’m sure we can wait a little while for them to appear: I’ll certainly be taking a look over the next few days at what’s on offer.

## Testing MiKTeX 2.8 and TeX Live 2009

Both MiKTeX and TeX Live have new versions in the offing. I’ve been testing out both MiKTeX 2.8 and TeX Live 2009, to keep up to date with what is happening. In the past, I’ve tended to stick with MiKTeX as it is designed for Windows, and so can make some platform-specific decisions and be more focussed. However, the TeX Live team have done a lot of work to make TeX Live usable across platforms, and there are advantages to that approach.

Looking through the feature lists, a lot of the new features are common to the two systems, for example:

• TeXworks installed as a distribution-maintained editor.
• XeTeX version 0.9995 (which includes the new primitives that the LaTeX3 team asked for).
• Some `\write18` functions enabled without turning on full `\write18` support: this is used to allow “safe” functions.

There are, of course, also differences. For example, only TeX Live includes LuaTeX at present. I also notice that MiKTeX 2.8 is adding the full path of files to the log, whereas in the past you got the relative path. I’m not so sure this is a good idea: it makes things rather wordy, and also the log will vary between systems: not so great. On the other hand, MiKTeX 2.8 does provide user-specific texmf directories. For multi-user systems, this is a real bonus: you can use the auto-install system without needing to be the Administrator.

As I said, I’ve tended to use MiKTeX to date as it’s been the best “fit” on Windows. The latest version of TeX Live makes this a pretty tight call, I think. If you are happy installing a full TeX system (which I do), then there is very little in it. MiKTeX still has the edge for small installations, as the auto-install system really pays off there.