## News items

### Blahtex(ml) has moved to github

16 October 2013

In April, I decided to move blahtex(ml) to github. This decision was taken mainly because I don't have much time left to maintain blahtex(ml), and so it makes it easier for other contributors to fix bugs or bring improvements.

The history was preserved from the original blahtex 0.4.4 by David Harvey to the latest changes brought by Matt Rajca.

Please visit `https://github.com/gvanas/blahtexml`

.

### Blahtex used by Apple's iBook Author

16 October 2013

Apple's iBooks Author supports equations written in LaTeX or MathML, and it does so using blahtex.

### Blahtexml and multi-target document generation

16 October 2013

This article, published in the Zpravodaj Československého sdružení uživatelů TeXu, describes a particular use case of blahtexml, where the source of a scientific document is written in XML and can be the input for a variety of output formats, ranging from LaTeX articles to documents in OpenDocument format to web pages. We show that blahtexml can play a central role in such a context, where the author wishes to enter equations in the TeX syntax and yet enable his document for publication not only with TeX but also in MathML-based formats.

This comes with a working, yet simple, example of a multi-target generation system for scientific documents.

### Blahtexml 0.9 released

27 November 2010

The new **blahtexml 0.9** offers better support for inline vs block equations.

Inline equations are displayed in the text, while block (or "display") equations are displayed stand-alone. In the latter case, TeX adapts its rendering, such as moving the limits of sums below and above the sum symbol.

This translates into the following changes in blahtex and blahtexml. For blahtex, the `--displaymath`

option is now a general option, which causes the equation to be set in block mode, both for MathML and PNG outputs. For blahtexml (with `--xmlin`

), each equation can be given as inline or block. It now properly converts block equations in display style.

### Blahtexml 0.8 released

8 March 2010

In this release, **blahtexml 0.8** supports Xerces-C 3.0 in addition to version 2.8.

As added functionality, blahtexml can produce annotations with TeX and/or PNG outputs (options `--annotate-TeX`

and `--annotate-PNG`

), in parallel to the MathML code. This way, the XML output produced by blahtexml contains mathematical formulas in up to three different formats simultaneously: MathML, TeX and as PNG images. Subsequent filters or XML processors can take advantage of this to produce documents in different formats from the same source.

### Blahtexml packaged for Ubuntu

3 October 2009

Blahtexml is packaged for Ubuntu, thanks to Abhishek Dasgupta

### Blahtexml 0.7 released under the BSD license

10 August 2009

The main change in **blahtexml 0.7** is that the source code of blahtex and blahtexml has been released under the BSD license, in agreement with David Harvey. At the same time, the text of the manual is released under the Creative Commons Attribution license.

In addition, LaTeX code can be inserted before purified TeX equations (e.g., to change fonts) for PNG output (thanks to Mikkel Ricky), and support for the Ångström symbol has been added (thanks to Paul Dlug).

### Blahtexml 0.6 is out

27 July 2008

Besides some bug fixing, the only change in **blahtexml 0.6** since the last version is the possibility to render "display math" formulas in PNG, thanks to a patch by Ari Stern.

### Blahtexml 0.5 is out

16 May 2008

The main difference of **blahtexml 0.5** with version 0.4.4 is that both blahtex and blahtexml now accept Unicode mathematical symbols and Greek letters as input in math mode. These symbols are equivalent to their command counterparts. For instance, the following two lines are equivalent and will give the same output:

`<eq b:inline="\Phi \leq \Omega \approx \Gamma"/>`

`<eq b:inline="Φ≤Ω≈Γ"/>`

The first line uses the traditional TeX commands, while the second line uses the Unicode symbols directly. The full list of accepted symbols can be found in the manual.