% README -- PASP Conference Series LaTeX macro package This directory contains all the files needed by authors to prepare their manuscripts for their Conference Proceedings that will be published as part of the PASP Conference Series. These files are described briefly immediately below. Following the file descriptions are short installation instructions and a generic recipe for printing the user guide and samples. README This file. README.bioast99 File containing specific instructions for your Conference Proceedings - this file should be edited by the editors for each Proceedings. paspconf.doc Fully documented source for the "paspconf" substyle. Contains macro definitions + comments. paspconf.sty LaTeX input style file for the "paspconf" substyle. This is the .doc file stripped of comments and unnecessary whitespace. paspman.tex The user input guide for the package. psample1.tex Minimal sample paper. psample2.tex Sample paper with "typical" content and markup. All of these files are generic in the sense that they can be used *as is* for any Conference Proceedings, except for the README.bioas99 file. The README.bioas99 file should be edited by the editors for a particular proceedings to reflect any special instructions that they would like to convey to their authors - and the file name should be changed so that "bioas99" is a shortened proceedings title for their volume. It should not be necessary to edit any other files. Authors who wish a somewhat more comprehensive introduction to the markup defined in this package may wish to retrieve the AAS LaTeX package for journal articles and read its user input guide. The AAS guide contains more detail about the contents of the package(s), and has some introductory sections that discuss "good LaTeX habits". The AASTeX package is available via anonymous FTP from the AAS Executive Office; the URL is ftp://aas.org/pubs/aastex.tar.Z. % ftp aas.org # 192.102.234.112 Username: anonymous Password: your email address, please ftp> cd pubs/aastex ftp> get README ftp> get aastex.tex ftp> get aaspptwo.sty ftp> bye INSTALLING THE STYLE FILES The *.sty files must be "installed" so that LaTeX can read them. This simply means that they must be placed either in (1) the user's working directory containing the paper being processed [single-user installation], or (2) in the TeX/LaTeX system input directory [site-wide installation]. Individuals who obtain the files for their personal use should just put the files in the same directory that they usually use when preparing papers, memos, etc. with TeX. Sites that expect usage by several authors will probably find it preferable to install the files in the standard TeX inputs area. In the parlances of popular OS's, these areas are typically called /local/lib/tex/inputs Unix and variants SOME$DISK:[TEX.INPUTS] VMS/Files-11 specification C:\EMTEX\TEXINPUT DOS (emTeX) The *.doc files are not actually read by LaTeX. They are the "source code" files for the corresponding .sty files. The *.sty files are produced mechanically from the *.doc files; these .sty files are never edited. Most installations of LaTeX keep .doc and .sty files in the same directory so that they can be easily found. PRINTING THE GUIDE AND SAMPLES The User Guide should be printed out for best results in reading it. The Guide is written using the paspconf substyle from the PASP macro package, and is therefore a LaTeX document. It must be processed by LaTeX, resulting in a compiled, device-independent format (a .dvi file). The DVI file has to be translated through a program that knows about the specific printer you wish to print on; such a program is often called a "DVI driver". Suppose you wish to print on a PostScript laser printer, and that the DVI driver on your computer system is called "dvips". The generic steps to be followed to get hardcopy are prompt> latex paspman prompt> latex paspman [Run LaTeX a 2nd time to get correct figure/table numbers, etc.] prompt> dvips paspman prompt> print paspman.ps There are various system- and program-specific eccentricities which cannot be fully enumerated here. Some things to watch out for: 1. On some systems, TeX and LaTeX do not permit a filename extension (the .tex) on the input file specification; .tex is assumed. On other systems, it is optional. 2. Most DVI drivers do not require the .dvi extension on the input filename. The extension of the output file (the one destined for a specific printer) is variable, often a site-dependent configuration parameter. 3. The user interfaces for DVI drivers are quite inconsistent. Some operate in an interactive mode, asking the user about variable setup parameters, while some only accept control input on the command line. 4. On some systems, the DVI translation and printing are combined, so one would enter only one OS command after running LaTeX. There is no way to know details of your installation, so you must inquire of the system administrator responsible for TeX, or hope that someone has written the LaTeX "Local Guide" for your site. PREPARING YOUR PAPER The instructions given in the "PASP Conference Series - Instructions for Authors Using LaTeX Markup" guide (paspman.tex) are brief as regards the details of preparing a paper with LaTeX. Authors who are not familiar with LaTeX may want to read also the author instructions for the AASTeX package, which can also be acquired via anonymous FTP, as described above. The AAS instructions contain fuller explanations of the basics of manuscript preparation with an electronic typesetter, macros for "popular" symbols, e.g., \sun, \earth, and so forth. For that matter, even if you are a regular LaTeX user, a refresher would not hurt. This package is derived from the AAS aaspp style, and it is intended that the markup for both styles to be the same. (The *output* is what will be different.) If you are familiar with the AAS styles, you will find that the markup commands are *identical*. Some of the commands are disabled in the PASP conference style, while others are unadvertised. Here are some things that may confuse you as you try to assimilate both sets of instructions. Use the 11pt substyle so that 11-point type is used. You should refrain from using alternate affiliations (\altaffilmark, \altaffiltext) for authors; these are unspecified in the PASP instructions. Do not use \twocolumn output. Please try to think of a few important keywords and include them in the paper in a \keywords{KEYWORDS} command. No output is produced. Footnotes for tables (\tablenotemark, \tablenotetext) are supported. They are explained in the AAS instructions. Authors should be able to use either of the sample papers as a template for editing their own manuscripts. The shorter sample contains a minimal amount of markup and essentially no comments: the markup itself serves as adequate in-line documentation. The longer paper (psample2) has examples of most of the elements that might be used in a paper: figures, tables, mathematical equations, etc. It is hard to over-emphasize that it is important that authors not define macros of their own. One of the principle objectives of markup definitions like this one is to describe a common language that can be used to exchange "tagged text" information, and adherence to a standard or convention permits the interchange of documents more broadly. If you do not have LaTeX... Even if you don't have access to LaTeX software or a laser printer at your site, you can still prepare your paper following the instructions in the instruction manual. In such cases, the editors will process the file and make any necessary editorial adjustments. ADMINISTRATIVE DETAILS This package has been prepared by Chris Biemesderfer and Jeanette Barnes of the National Optical Astronomy Observatories in Tucson. Thanks are due to Liz Holloman of the BYU Press for helpful advice. REVISION HISTORY v1.0, Sep 1991 Original version written at NOAO in anticipation of proceedings for software conference at NOAO in Tucson. Derived from the AAS aasms v2.2 substyle. v1.1, 16 Oct 1991 Fixed caption typography to conform to PASP write-up. Reported by Bob Hanisch. v1.2, 11 Feb 1992 Fixed caption typography again to account for 2em offset when comparing boxsize with textwidth. Reported by Jeannette Barnes. v1.3, Sept 1992 Altered some typography for ADASS II: Running heads are mixed case, use oblique font. Title is mixed case, uses large bold font. Author names are mixed case. Affiliations are mixed case, use italic font. Abstract title is mixed case, uses bold font. Sections are numbered, heads are mixed case, bold font. Acknowledgments title is mixed case, uses bold font, text is run-in. Figure and table captions use mixed case, arabic numbers. The appearance is somewhat different from the original PASP style, which had its heritage obviously in the IBM Selectric. The newer typography takes advantage of the versatility of laser printers. The main impact of the changes on authors is that they should not enter uppercase titles, names, or section heads. Ensured nominal RevTeX compliance. Mar 1994 (jvb) Modifications made to text in paspman.tex and psample2.tex to make them more consistent with standards. Changed "Reprints" section in paspman.tex at request of ASP office at BYU - reprints are no longer available. New diskette of directory sent to ASP office at BYU.