The TeX Live inclusion policy

TeX Live takes almost all of the material it includes from CTAN, but not everything that goes to CTAN gets into TeX Live. That’s because CTAN will take anything TeX-related, but TeX Live is ‘free as in speech’ and that means that some things are not suitable for inclusion.

Packages are removed from time to time license reasons: they are not actually free, so can’t stay. However,  a few packages have been removed from TeX Live they did not fit in with the policy for inclusion in TeX Live for other reasons. That has caused a bit more surprise, and some questions have come up about it.So I thought it would be useful to summarise the TeX Live situation as I understand it.

The clearest case is material where the license is not ‘free’ (as defined by Debian): anything without a free license cannot go into TeX Live. Perhaps the next clearest case is support for commercial fonts. To use a font with pdfLaTeX, it’s necessary to have the correct support files. Quite often, these are sent to CTAN with a free license, but don’t go into TeX Live. Without the fonts themselves you can’t use the support material, so it’s only practically useful if you are happy to buy the non-free fonts.

Life is more complicated in the cases that have come up recently, where things are less clear cut. AS many readers will know, the PDF specification is nowadays an ISO standard, and there are several PDF viewer implementations with free licenses. However, there are two caveats to this. First, Adobe have published extensions to the ISO version of the PDF specification. Secondly, creating a PDF viewer does not mean that every possible PDF feature is implemented. Why is this relevant to TeX Live? Well, there are several packages on CTAN, for example media9, which use PDF features which are either not part of the ISO standard PDF specification or which are only available in Adobe Reader. These have been removed from TeX Live as the conclusion is that they only have real functionality along with a non-free product. (There seems to be some confusion as to whether any of the free viewers may support at least some of the necessary PDF features: I can’t find a definite answer.)

That judgement is complicated: this case is not the same as the font situation. The PDFs produced by for example media9 are still viewable with free readers, they just don’t have all of the bells and whistles available. It’s also the case that if we look back in time a little, PDFs were only viewable using Adobe Reader, but that did not stop the development of  pdfTeX, hyperref and so on. On the other hand, the TeX Live developers already do a great deal of hard work, and it’s not unreasonable for them to set a policy that they are comfortable with: after all, it’s a labour of love. I think that the policy is reasonably clear, although tracking what is practically implemented, as opposed to what is legally allowed, is rather likely to change over time.

 

WinEdt 7

The world seems to be full of LaTeX editors, particularly on Windows. One of the longest standing is WinEdt, a shareware editor that retains a strong following due to its powerful features. What has been missing in recent years is full Unicode support: not so much of an issue for me, but crucial for non-European users in particular. WinEdt 7 has now been released, and the big new feature is Unicode support in the editor. That can only be a good thing!

TeXworks roadmap

There has been some discussion over the past couple of weeks on the TeXworks mailing list about the future direction of the project. As regular readers will know, I like TeXworks, and use it as my day-to-day editor, so I’m very interested in what the developers are up to.

Two very useful things have now been added to the project website. First, there is a roadmap highlighting the key areas for development for v0.6 and v0.8. It looks like v0.6 is mainly about improving the PDF viewer, with editor improvements as the main target for v0.8.  For C++ coders, there is also a list of ideas to work on. That should let people with the right skills dip in to coding TeXworks in a self-contained way.

TeXworks is a great project, and I do hope that interested C++ programmers in particular see these new pieces of information as an opportunity to get involved. For those of us who don’t code C++, direct contribution is a bit more difficult, but spreading the word is something we can all do.