Making an ASP proceedings volume from contributions. Before you start: My procedure is to process each contribution, which is a standalone TeX document, to make it into a fragment suitable for inclusion in a bigger document. The method I use for doing this assumes that all of the contributions, and all of their PostScript figure files, are in the same directory. If you have each contribution in a separate directory, you can either rearrange, or use links to provide this alternative arrangement. If you want to build the book in a different directory, then you will need the GNU version of make, so that files can depend on files in other directories. If you don't have GNU make, then you can just throw everything into one directory. The ASP will reduce your proofs down to the size of the final book. My procedure is to have latex work on pages approximately the same size as the ones in the book, and to use an option on the dvips program (Tom Rokicki's dvi to PostScript converter) to scale up the output to the size the ASP expects for proofs. This may create a demand for fonts that would not otherwise be on your system, so you should have your system set up so that dvips can automatically invoke metafont to build the new fonts that are required. In Makefile: Everything should work with whatever version of latex you may have, but there is a LATEX macro at the top of the Makefile in case you need to specify a different program name. Set VPATH to the directory containing all of the contributed TeX and PostScript figure files. VPATH is something that only GNU make understands, however. The DVIPS macro sets the options on the dvips program. The -x option scales up the output, as part of the overall scheme. The number after the x is the magnification -- in TeX parlance magnification 1000 means 100%. Magnification 1095 makes a 10pt font into a 11pt font. Rip this out, if you aren't going to use this part of the scheme. -Phplj4 just invokes a locak 600dpi printer definition. Substitute or omit as suits your installation. The PAPERS macro must contain an entry for each contribution, but with a .ltx extension instead of .tex. .ltx is the file extension used by the \paper macro for inclusion into the book. At the bottom of the Makefile is a .tex.ltx rule for building the .ltx file from the original contribution. What the rule does is to comment out the \documentstyle, \begin{document} and \end{document} lines. It also inserts a \label command containing the root name of the file -- this can be used to insert a cross reference to another paper in the same volume. For example, if Dr. Smith refers to a paper by Dr. Jones in this volume, and Dr. Jones' paper is in file jonesd.tex, then in the references section of Dr. Smith's .tex file you could say Jones, D., 1997, this volume, \pageref{jonesd} The FIGURES macro is there if you want the book to depend on the PostScript figure files. This would only be the case if you planned to actually edit them. And it does slow things down to check them all every time. You may want to comment out the dependence of book.dvi on $(FIGURES) once you are finished editing the figure files. The clean and realclean targets get rid of things that make can build for you again without any real (human) effort. In adass96.sty First of all, you probably want to rename this file. If you aren't letting LaTeX work on reduced size pages, you will want to take out the dimension setting commands near the top of the file. Search down for "psfigurepath". If you don't have all of the figures in the same directory as the book, you will have to specify where to find the PS figures. In my case it was "../figures". You will have to substitute whatever is appropriate for you, in three places. The style files defines some useful macros: \us for an underscore in \tt fonts \fortran FORTRAN in small caps \micro micro symbol for both text and math modes \kms kilometers per second for text and math modes \Sim ~ for text and math modes \PM plus/minus sign for text and math modes In book.tex: There are a number of documentstyle options listed here, and you may not need (or have) them all. The here option invokes here.sty, which defines an 'h' placement option on figures and tables that means right here. The html option invokes the html.sty that comes with latex2html. For ASP volumes you need the aspconf style to come before adass96. Psfig is for including PostScript figures -- you won't need it if your authors (or editors) didn't use it. Most of your work is to create a \paper entry for each contribution. The \paper macro has 4 arguments: the root part of the tex file containing the contribution, the author list for the table of contents, the author list for page headers, and title for page headers. If the author's title is too long to fit the page header, put a shorter one here. The \invited macro is the same, except that it puts "invited talk" after the title in the table of contents. Use \part to create dividers. In the contributions themselves: You will have to put in your own \index commands if you want an index. The author-supplied \keywords are ignored. Of course, making the right choice of topics is a hard job. You also have to put in \aindex commands if you want to make an author index. Make sure to follow some kind of rule so that all entries for a given author match exactly. You can put "|bb" after first authors to make the page number come out bold in the index. Depending on what you told your authors, they probably all labelled their first figure as \label{fig-1}. But to make the book, you'll have to change them so that they are unique. The first time you run latex on the whole book, it will tell you which labels are multiply defined. Look in the notes file for a list of other things you may want to worry about. In aspconf.sty: Near the bottom of this file, you will find a \newif command defining \if@finalstyle, followed by \@finalstylefalse. You have to change this to \@finalstyletrue to put the slug lines in.