Developer Information


The contents of this page apply if you are interested in the internals of the DB2LaTeX XSL transformation stylesheets, or if you are interested in becoming an active developer and mantainer of the DB2LaTeX stylesheets, or just if you would like to be able to write your own XSL customization layers. Also, modification of the localisation files requires a developer-style DB2LaTeX source tree.

Getting the XSL stylesheets

In general, see our installation guide.

Anonymous CVS Access

Anonymous CVS read-only access is available for the DB2LaTeX project. Follow the following instructions:

baldrick(/opt/sgml/xsl)% cvs -z3
      login baldrick(/opt/sgml/xsl)% cvs -z3 co
      db2latex baldrick(/opt/sgml/xsl)% cvs -z3
      logout (Logging out of

Developer CVS Access

Developer (full) CVS access is available for the DB2LaTeX project upon request.

baldrick(/opt/sgml/xsl)% export CVS_RSH=ssh
      baldrick(/opt/sgml/xsl)% cvs -z3 co
      db2latex's password: xxxxxyxxxx
      cvs server: Updating db2latex...
[Important] Important

Do not forget to export (setenv in C-sh) the CVS_RSH variable. Otherwise, sourceforge will close the connection without further notice. (Yes, it happened to me too :)

Configuring and Building DB2LaTeX

A GNUmakefile is provided. It can build the DB2LaTeX documentation and packages. Within the admin, xsl/sample and contrib directories you will find further Makefiles. Some are accompanied by README files or help targets. There is also a top-level ./configure script that will set up Makefile.local files for you (currently, this is only known to work with xsltproc and Saxon). For regenerating the localisation files, you will need access to the Internet or gentext CVS checkouts.