%%% README HQ98 - the readme file for preparing Proceedings (6 1/8 x 9 1/4) %%% using aipproc macros for HQ98. These files originally came from AIP obtainable directly from AIP at ftp://ftp.aip.org/ems/tex/macros/proceedings/6x9/ through their WEB page http://www.aip.org/catalog/publish.html However there were a few problems with their files and updated files are given in this HQ98 area. The following changes were made: README, readme.txt % This readme file has been updated to explain the changes made to the files and explain the inconsistencies between the instructions given in cp6x9.pdf for camera ready manuscripts and those given in aipproc.tex for LaTeX macros. samp0.tex,samp1.tex % Corrected so that table column heads use bold type as instructed by cp6x9.pdf. samp2.tex % Corrected for column heads and added "lscape" in the documentstyle to enable the longtable to LaTeX properly. v3.13 longtable.* files are included in case you need them. cp6x9.pdf,cp6x9.ps % Added into this area for easy access longtable.sty,etc. % Added v3.13 longtable files for easy access The following files are provided: README % this file readme.txt aipproc.cls % the cls file for running LaTeX2e in compatibility mode. aipproc.sty % macros for aipproc style. cp6x9.pdf % THE correct instructions on what the camera ready manuscript should look like in PDF format. You should follow these instructions for preparing your manuscript. cp6x9.ps % PostScript version of cp6x9.pdf, the instructions for preparing your camera ready manuscript samp0.tex % sample input file for one paper. Everyone should be able % to run this file. No special package is needed. samp1.tex % sample input file for one paper. LaTeX 2.09 users should % be able to run it provided the epsfig.sty file for their % version of LaTeX and epsf.tex are installed. LaTeX2e users % with the "graphics" package installed can run this file too. samp2.tex % sample input file of one paper for LaTeX2e users. It uses % epsfig, longtable, and lscape. In order to run it, one must % have both "graphics" and "tools" bundles installed. sampmain.tex % sample input file of the whole proceedings --- you need % to get p1.tex and p2.tex to run it. aipproc.tex % General guidelines for using aipproc macros to help you prepare your camera ready manuscript. Note that these instructions and the associated LaTeX macros have some minor inconsistencies compared to the instructions given in cp6x9.pdf. You should follow instructions in cp6x9.pdf where you can, however the output produced by these LaTeX macros are acceptable if you follow the guidelines contained in this document, see also the output from the sample input files. Known inconsistencies are as follows: 1) The LaTeX output text area is very slightly different in size and certain spaces are different as compared to those indicated in cp6x9.pdf. Differences are of order of 1-2 mm which is acceptable. 2) The Equation numbering for multi-line equations should be centered according to cp6x9.pdf. However the LaTeX output has, for example in a two line equation, the equation number level with the first line instead of between the two lines. This is acceptable. However please center the equation number when you can. 3) Table column heads should be in bold according to cp6x9.pdf. However the LaTeX output defaults to non-bold and the aipproc.tex does not mention this type setting. However you should use bold table column heads where you can as is done with the (updated) sample input files. 4) When referring to references, cp6x9.pdf says to use parenthesis like (1), however the LaTeX output actually use square brackets like [1]. This is acceptable. 5) No color figures are accepted for this proceeding. If your PS file is color, that is fine as long as you (or we) print it out in black and white for the camera ready manuscript. got.ps % a eps-format figure used in the sample tex files. epsf.tex % tex file needed for LaTeX 2.09 using epsfig. longtable.sty % v3.13 longtable files added here for easy access longtable.* in case you need them. (If you are not sure which version of longtable you have look in the samp2.log file after you LaTeX it. Refer to notes below on use of longtable. %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Please note the following: 1. aipproc macros run with both LaTeX2e and LaTeX 2.09. BUT IT DOES NOT WORK WITH THE RARE UNSUPPORTED COMBINATION OF NFSS and LaTeX 2.09. For infomation on downloading and installing LaTeX2e on your machin, please goto URL http://www.cogs.susx.ac.uk/cgi-bin/texfaq2html?introduction=yes and follow the link named "(La)TeX for different machines". 2. You should use compatibility mode, i.e., use \documentstyle{aipproc} or \documentstyle[FOO]{aipproc} RATHER THAN \documentclass{aipproc} or \usepackage{FOO}, where "FOO" is the options list you decide to use. For example, use \documentstyle[epsfig,longtable,lscape]{aipproc} NOTE: It's important that users have all the PROPER "sty" files FOR THEIR VERSION of LaTeX required by the the documentstyle options. (a) For LaTeX 2.09, one can usually get the needed "sty" files from ftp.aip.org in the directory /ems/tex/macros/latex209/sty/ (b) For LaTeX2e, one should get both "graphics" and "tools" bundles, i.e., ftp to ftp.aip.org first, 'cd /ems/tex/macros/latex2e/packages/tools/', get all files in that directory; then 'cd /ems/tex/macros/latex2e/packages/graphics/', get all files in that directory. At your site, do the following: latex (or latex2e) tools.ins latex (or latex2e) graphics.ins Then you will have basically every "sty" file needed. **** Note: Use logntable v3.13. Newer versions of longtable **** do not work with aipproc! You should get longtable v3.13 **** from ftp.aip.org: **** /ems/tex/macros/latex2e/packages/tools/longtable.* 3. An input file must be latex'ed at least twice to get the correct placement of tables, table captions, table notes, Table of Contents, List of Figures, and List of Tables. 4. The tabular environment. The *-form of the tabular environment (i.e., \begin{tabular*}{WIDTH}{...} ... \end{tabular*}) is supported. Of course, there must be rubber space between columns (such as @{extracolsep{\fill}) that can stretch/shrink to fill out the specified WIDTH. Normally, you should not use the 'tabular*' environment. \multicol and '|' are supported. However, you must use \hline (instead of \tableline) and must place the following line \noalign{\vspace{-8pt}} immediately after the \begin{tabular}{...} line IF '|' appers inside the argument of tabular. To open up more space between table rows, you can use \rule{0pt}{14pt}. Change 14pt to a proper value for your needs. You can also use \\[4pt] to have 4pt extra vertial space between this and next rows. \tablenotemark[NUM] and \tablenotetext[NUM]{...} are supported in both the 'table' and 'aiptable' environments. These commands are useful when you want several tablenotes in a table to share one common tanlenote mark. You can use \tabcolsep to change the half width of the default horizontal space between columns in a tabular environment. aipproc sets \tabcolsep at 6pt. See vbar_table.tex for example use of these commands for tables. 5. The normal (default) type size is set to 12pt by aipproc already and all font size options (such as 11pt, 12pt) are ignored. 6. Each paper should label its things distinctively to avoid problems when running all files together. For example, (a) When using the \label and \ref commands, try to create unique labels so that there will be no collisions of names when all paper are run together at the end. For example, using \label{table1} is likely to put your label in conflict with another author's use of the same label. Here is one scheme that has been used successfully: Use \label{X:Y:Z}, where X is the label type (S = section, T = table, F = figure, E = equation), Y is the author's first initial and last name, and Z is the number of the thing being labeled. For example, the first table in James Foo's paper would be labeled with \label{T:jfoo:1}, the first figure would be \label{F:jfoo:1}, the second figure would be \label{F:jfoo:2}, and so on. (b) Input the reference section as a normal LaTeX bibliography. This will be the correct way to input things. Use LaTeX's \cite to reference the bibitems. This makes it easier if things change in any way. Some sort of unique id in the bibitem label would be helpful to avoid collisions with names in other papers. For example, \bibitem{smith} is likely to come up more than once, while \bibitem{jfoo:smith94} is not. It is important that the references themselves follow the right style. The sample file samp0.tex shows examples of a variety of references; e.g., journal, book, etc. (c) File name conventions: the file name for the 1st EPS figure in, for example, James Foo's paper is better named jfoo.ps instead of f1.ps, since the latter is most likely not unique across papers, and so on. 7. It is very important for the editor to enforce a consistent scheme for labeling and naming things. Otherwise, when all papers are run together, you may find yourself in a disastrous situation where cross-references are wrong or wrong figures are included into a papaer because ten different papers used the same bibitem label or the same file name "fig1.ps". 8. The special symbols in AASTeX are supported. See samp0.tex.