• Mapping to characters

    It is quite natural to think that separating a word up into individual characters is quite easy. It turns out that for the computer this isn’t really the case. If we look at a system that understands Unicode (like XeTeX or LuaTeX), most of the time one ‘character’ is stored as one codepoint. A codepoint is a single character entity for a Unicode programme. For example, if we take the input café, it is made up of four codepoints:
  • Math mode: $...$ vs \(...\)

    A topic that comes up for many LaTeX users is how best to mark up math mode in sentences: inline math mode. LaTeX offers three (!) official ways to do that
  • siunitx v3.1: complex values

    I mentioned recently that I’m working on features for siunitx v3.1. One area that I’ve now been able to commit is improvements to handling complex values.
  • siunitx v3.1 development

    I’ve now done 49 (!) minor releases of siunitx on the v3.0.x branch. These have addressed quite a few minor bugs: I expected to have to do a bit of work since the shift from v2 was quite major.
  • siunitx v3 successes

    The third major release of siunitx was out in May, after the TeX Live 2021 DVD. That means it’s been picked up primarily by more active users: people who install TeX between the ‘fixed’ DVD releases (or who use MiKTeX). It also didn’t initially appear on Overleaf, as they take a while to test TeX Live images before making them public.
  • A new theme

    I’ve been meaning for a little while to look properly at my Jeykll theme for the site and tidy it up: it was a bit basic. Prompted in part by Will Robertson, I decided that now is the moment.
  • Talking about units

    Usually, I keep my day job (as a university lecturer in chemistry) and my LaTeX work separate. Of course, I use LaTeX at work for things like lecture handouts, but most of the time the two areas don’t directly intersect.
  • Moving from siunitx v2 to v3

    With v3 of siunitx out, I am as expected getting quite a few questions about moving from v2. In the main, this is quite easy as there is a decent amount of compatibility code. Here, I’ll pick out a few cases where you might want some adjustments.
  • siunitx v3 beta 2

    Following up on the recent first beta for siunitx, I’ve now made a second beta available. There was only one issue picked up so far by testers, plus of course those I’ve spotted myself. In particular, I’ve allowed a way to set the text font manually if simply resetting back to the standard one doesn’t work. I’ve also sneaked in a late addition: the ability to parse and print uncertainties the way NIST seem to suggest they should appear.
  • siunitx v3 beta

    I’ve been talking about a new version of siunitx for ages. Progress has been slow but I’ve now put my back into it and got to a feature-complete version: I’m calling this v3.0.0-beta. As this is a beta release, it’s not ready for production just yet, but it is ready for proper testing. I’ve made the TDS-style zip file available here; if you know how to use this kind of file, please download and test!

Full post archive