Документ взят из кэша поисковой машины. Адрес оригинального документа : http://www.adass.org/adass/authors/LatexInfo.txt Дата изменения: Mon Oct 20 21:59:17 2003 Дата индексирования: Mon Oct 1 19:40:22 2012 Кодировка:

%LatexInfo.txt
This file describes some important points about Latex and the
ADASSCONF package.

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. The AASTeX package also
has a home page at URL: http://www.ferberts.com/AAS/aastex.html.

% 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 aas2pp4.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)


PRINTING THE GUIDE AND SAMPLES

Read UserGuide.ps for detailed instructions on preparing your manuscript.

The files sample1.tex and sample2.tex are Latex files which are
example manuscripts. Running one through latex will result 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 sample2
prompt> latex sample2 [Run LaTeX a 2nd time to get correct
figure/table numbers, etc.]
prompt> dvips sample2

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.

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 UserGuide.ps are brief as regards the
details of preparing your manuscript 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. Also,
LatexSummary.ps contains a 14 page list of Latex commands.

This package is derived from the AAS v3.0 aaspp style, and it was intended
that the markup for both styles to be the same, although there can be slight
differences with AASTeX v4.0. (The *output* is what will be different.) If
you are familiar with the AAS styles, you will find that the markup commands
are similar. Some of the commands are disabled in the ADASSCONF 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.

Do not use \twocolumn output.

Footnotes for tables (\tablenotemark, \tablenotetext) are supported.
They are explained in the AAS instructions.

Authors can use template.tex or either of the sample papers as a
template for editing their own manuscripts. The shorter sample
contains a minimal amount of markup. The longer paper (sample2) has
examples of most of the elements that might be used in a paper:
figures, tables, mathematical equations, etc.

We must 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.