Archive for the ‘biblatex’ tag
Biber now in TeX Live 2010
Many readers will be familiar with the Biber program, a replacement for BibTeX which works with the biblatex package. Binaries for common platforms have been available from TLcontrib for a while, but have now been added to the main TeX Live 2010 system. So you can install Biber on the ‘common’ platforms using the TeX Live Manager (or tlmgr from the command line). Yet another reason to move on from BibTeX and switch to biblatex, if you’ve not already!
biblatex reaches version 1.0
Reading through some TeX-related material today, I spotted that the very popular biblatex package has finally reached version 1. Accompanying this release is a version step for the biber BibTeX-replacement program, which reaches version 0.6. Both are now considered non-beta, and the biblatex release in particular is a big story to me. I’ll be checking on my own biblatex-related packages over the weekend and making sure that they are working with the new release, and if all goes well will move them to v1.0 as well.
A quick look through the documentation for both biblatex and biber shows that the new versions are mainly about stability. There are not a lot of changes listed from the previous testing releases: they’ve proved to be pretty stable and so the time for an official move to release status has obviously arrived.
biber without building from TLContrib
I’ve written in the past about the biber program, a replacement for BibTeX when using the biblatex system for citations in LaTeX. The biggest stumbling block to using biber to date has been the need to build it from the source. On Windows, that also means getting a working Perl installation, which is a non-standard item on that operating system. However, there is now an alternative approach, at least for people using TeX Live 2010. The new TLContrib system for additions to TeX Live now includes a biber package for Windows, Mac OS X (64 bit) and Linux.
To get biber installed, you’ll need to use the Command Prompt or Terminal. On Windows, you probably need to run the Command Prompt as the Administrator, while on the Mac or Linux you will probably want to sudo the following. To get biber installed, all you need to type is
tlmgr --repository http://tlcontrib.metatex.org/2010 install biber
The system will then get on with installing biber, which you can then use as a replacement for BibTeX. I’d then add biber to my graphical editor’s list of programs to make it easy to use: the detail of course depends on which editor you use.
What is particularly interesting here is that it has been possible to build a stand-alone biber. This should mean that at some stage both TeX Live and MiKTeX can integer ate it directly. This will really make biber a viable choice for most people using biblatex: building from the source is not most people’s idea of ‘easy to use’!
Building biblatex-biber on Windows
I’ve just reinstalled my Strawberry Perl system on Windows, and so had the opportunity to try a clean build of biblatex-biber. I’ve posted before about building this on various platforms, and it now is almost asstraight-forward on Windows as on Linux.
As before, I’ll assume you’ve grabbed the source code, unzipped it and have a Command Prompt running as the Administrator, in the directory where biblatex-biber is unzipped. First, you need to install one support Perl module using
cpan Config::AutoConf
You can then do
perl Build.PL build installdeps build build test build install
That’s it! I’m not quite sure why you have to install Config::AutoConf ‘by hand’, but if you don’t then Text::BibTeX still fails to work. However, that is almost as easy as on Linux or MacOS 10.6, so everyone should be able to use biblatex-biber now.
Building biblatex-biber
The biblatex-biber project provides probably the best way for biblatex users to switch to pure UTF-8 bibliography information. However, getting it to build can cause problems: biblatex-biber is a Perl programme, and needs various downloads from CPAN. I thought it would therefore be useful to put some simple recipes here, explaining what I’ve done to get a working biblatex-biber on Windows, Ubuntu and Mac OS X. I’m assuming that the latest biblatex-biber release has been downloaded and unzipped somewhere, and that the Command Prompt/Terminal/Shell is open in that directory (folder).
Mac OS X 10.6 (Snow Leopard)
Mac OS X comes with Perl installed, so life is relatively easy. At the Terminal, you need to run the cpan script as root:
sudo cpan
The cpan script has its own prompt, but this is very similar to the Terminal one. First, I updated cpan itself and installed a helper module with
install CPAN reload cpan install YAML
That done, the various requirements for biblatex-biber can be installed, using the single call
install Data::Dump List::AllUtils Readonly Text::BibTeX Readonly::XS
For the more cautious person (such as me), each install instruction can be given on a separate line: this keeps things a bit more controlled. I accepted the standard settings, except when asked about installing items that were only needed for testing, where I said no.
Once cpan has done all of the installing, you can leave it by typing
exit
So now back at the Terminal prompt, a few simple instructions
perl Build.PL ./Build sudo ./Build install
That put biblatex-biber onto the path for all users: everything then worked correctly.
Ubuntu 9.10
Once again, Perl is installed as standard in Linux distributions: I’m using Ubuntu as a representative system. Before starting cpan, there is an additional step, which is to install an extra Ubuntu package. So at the Terminal, you need to do
sudo apt-get install libxml2-dev
This is needed as otherwise you get some very odd errors in a bit. Now, essentially the same recipe works as for the Mac. First run cpan running and update and install YAML. Then there is a long list of items to install
install Data::Dump List::AllUtils Readonly Text::BibTeX Readonly::XS XML::Writer XML::LibXML File::Slurp
which can again be done one at a time, for the more cautious.
After exiting cpan, the same three lines at the Terminal should work as in the Mac section.
perl Build.PL ./Build sudo ./Build install
Windows (XP, Vista and 7)
To date, my attempts to build biblatex-biber on Windows (using Strawberry Perl) have failed as I can’t get the Perl module Text::BibTeX to install. This is supposed to be optional, but without it biblatex-biber does not seem to work, although I do get it to build. Luckily, there is a self-contained binary for Windows available from the project site. This includes its own Perl system, so there is no need to get Perl set up before trying it. Everything seems to work for me with this version. Any ideas on what is necessary would be helpful!
biblatex-chem again
Another day, another biblatex-chem update. I’ve added the ability to only use the first page of a range to all of the styles. Some journals require this, and I’d prefer to keep the total number of styles down with appropriate options. This is such a trivial variation it seems to be the best way to me.
biblatex-chem update
I’ve just spotted a bug in biblatex-chem, and a fix is on the way to CTAN. It looks like changes in the biblatex core have made the comma after journal titles when using the chem-rsc style disappear. This was working earlier: I’ve retested an old version and it is not due to anything I’ve done.
On another matter, I’ve been asked to look at turning page ranges into single pages in biblatex-chem. I need to add the appropriate functions to biblatex, so there may be a delay (I have lots on at the moment). It is definitely on my list to do. Why do this? Well, some journals insist on first-page only, but in a database both pages will be present. So the code needs to handle things. There should be another update once I sort this: a few days.
Coding in public
I see that the biblatex package has been updated to version 0.8c, and that there is now a SourceForge page for the package. The later is just holding bug and feature tracking for the package, and no actual code. Placing development code in a public place means that your commits (or lack of them) are there for all to see, so I can see why keeping things private is attractive. Of course, just because nothing happens in public doesn’t mean nothing is happening, and in any case these things are done as a “hobby”.