tqft's Introduction

The TQFT Package

This is the official home of the development repository for the tqft library for LaTeX. This package is for drawing cobordism diagrams, as typified in topological quantum field theory (tqft).

The current published version can be found on CTAN and the documentation is there as a PDF.

To use the most recent version, download the file tqft.dtx. To generate the library files, run tex tqft.dtx. To generate the documentation, run pdflatex tqft_doc.dtx.

Versions

The TQFT package has two main versions:

Version 1: the original version defined the diagrams using nodes. To use this version, use \usepackage{tqft} in your preamble. This version will not get new features, but I'll fix bugs (if I can).
Version 2: the most recent version defines the diagrams using pics. To use this version, use \usetikzlibrary{tqft} in your preamble. This is the recommended version and the one that is maintained.

tqft's People

Contributors

Stargazers

Watchers

tqft's Issues

Add a node for the genus holes

It would be useful to have a node located at the holes for drawing purposes. Or at least, some coordinates scattered around it.

Fix node label inconsistencies

Reported via email:

I noticed that the documentation mentions an anchor named between first and last incoming, but the code names this anchor as between first incoming and last incoming.
Meanwhile, the dual anchor (between first and last outgoing) works as intended.
The other "incorrect" anchor, between first outgoing and last outgoing, doesn't exist.
I think you get why that can be confusing!

Would you mind making two aliases, so that both versions are correct, and in that way we have both consistency and backwards compatibility?
That is, making between first and last incoming an alias for between first incoming and last incoming, and making between first outgoing and last outgoing an alias for between first and last outgoing.
I don't know much about the inner workings of tikz, but I assume this is an easy fix.

If you cannot for whatever reason, a small update to the documentation to inform users of this pitfall (without changing any of the code or breaking existing documents) would be nice.