Index of /~leavens/texmf/doc

 Name                    Last modified       Size  Description

 Parent Directory        15-Feb-2009 12:53      -  
 LICENSE.html            07-Jan-2009 09:52     1k  
 ul9-instructions.txt    17-Jun-2009 11:19     1k

README for tex-include LaTeX/BibTeX tree

Last Revised on $Date: 2008-12-26 21:20:21 -0500 (Fri, 26 Dec 2008) $

Configuration

To use the LaTeX macros, styles and bibliography styles and databases, you have to tell your TeX distribution about this tree. But often you can just use the command texconf conf and look in the "kpathsea variables" section for the variable TEXMFDBS. In this path there is usually some directory like /home/You/texmf that will be the logical place to put the root of this directory tree.

Mac OS/X with TeX Live

On an Apple Macintosh with OS/X I just put the root of this directory tree in $HOME/Library with the root named texmf, and the it finds everything.

Windows with Cygwin's TeTeX

On a Windows machine running TeTeX I just put the root of this directory tree in $HOME/ with the root named texmf, and the it finds everything.

Linux with TeTeX

On a Linux machine running TeTeX I just put the root of this directory tree in $HOME/ with the root named texmf, and the it finds everything.

This directory tree contains bibliography files, bibliography styles, latex macros and styles designed by our research group (with some input from collaborators, especially for bibliography items).

Bibliography Support

Bibliography Databases

In the directory bibtex/bib/misc/ there are several bibliography databases (.bib files). The main ones are the following:

Makefile, which has as its default target the production of a file, all.bib (the concatenation of the .bib files below), which is useful in Framemaker and other such tools.
journal-abbrevs.bib, which contains abbreviations for journal names; this is needed to use the other files.
datatypes.bib, which has references on type theory, abstract data types, subtyping, types in programming languages
old-datatypes.bib, which has 1970s and older references on datatypes, type theory, etc.
distrib.bib, which has references on distributed and parallel processing, except language definitions.
languages.bib, which has references on programming language issues, semantics, implementation, except types, distributed/parallel stuff, and aspect-oriented software development. All language definitions go here.
se.bib, which has references on software engineering, specification, verification.
etc.bib, which has references on math and general stuff that doesn't go elsewhere.
proceedings.bib, which has various proceedings used by cross-reference in the other bib files.

Bibtex Database Conventions

If you change the bibtex database files, don't change all.bib as that is automatically generated. Please instead change one of the other files that is used to create it (see the Makefile).

If you change add or change these bibliography files, please also follow our conventions. The main ones are as follows.

Categorize the contribution into the appropriate bibliography file as best you can.
For citation keys, use the full names of up to 3 authors, separated by hyphens, followed by the last two digits of the year. For example, Leavens-Baker-Ruby02. For more authors, use -etal after the first author's name, followed by the last two digits of the year.
If you have physically laid hands on the paper or checked the information from a publsher's site, such as the ACM Digital Library, then put in an Annote key with the number of references, e.g., Annote="23 references.". You can have more text in the annote entry, but put the number of references last. If there are hundreds of references, then you can just say something like Annote="Hundreds of references." instead of counting them.
Use single letters after the year if the same group of authors has more than one paper in the given year. For example, Clifton-Leavens02a.
Keep the bibliography files sorted.
Use 3 letter abbreviations of months, without quotes or brackets, for example nov or may. These are bibtex macros which are expanded or contracted by the style sheet; if you quote or bracket them they aren't macros anymore.
Don't put quote marks or brackets around numbers for years, and only put in quote marks or brackets around other numbers if needed.

If a paper's entry gets replaced by a better version, it's probably safest to make a new entry. However, for one of our own papers, it would be more usual to replace the entry with an entry for the published version, and to rename the technical report version. For example, change the technical report entry of Clifton-Leavens02 to have the key Clifton-Leavens02a when the publication appears, and put the publication under the key Clifton-Leavens02.

If you make an entry for a paper with Leavens as a coauthor, please also place a copy of the entry in the file leavens.bib. You are welcome to make your own personal bibliography file also.

LaTeX Styles

There are also many latex macro and style files in the directory tex/latex/misc/. All are unsupported, so use at your own risk.

Conventions for the Latex Macro Files

If you channge the latex macro files, please make any changes upward compatible, so that old papers still can be formatted. The easiest way is to always use new names. Usually we use upper case for macro names.

If the tex/latex/misc/ directory contains duplicates or old versions of files in the standard tex distributions in, then these should be removed.