Preparing Your Text and Tables -- Using LaTeX

For quickest processing, we prefer to receive final manuscripts from authors in Word docx format. If you wish to submit your final manuscript files in LaTeX, please observe the guidelines on this page in setting up your paper. It is particularly important that these guidelines be followed for manuscripts in the revision (i.e., post-peer-review) stage, though we encourage authors preparing their initial submission to follow these general guidelines as well. The downloadable files listed below will help you set up your manuscript.

  1. Use LaTeX2e. Manuscripts should be marked up in LaTeX2e, not LaTeX 2.09 or any earlier release.
  2. Strive for legible output. For both initial submissions and revised manuscripts after peer review, authors should avoid use of Type 3 bitmapped fonts in PostScript or PDF files generated from their TeX/LaTeX source.
  3. Keep it simple. Our routine for converting LaTeX files to Word format relies on a DOS-based utility that converts to HTML as an intermediate format. This utility works best if the following procedures are observed:
    • Keep all filenames -- the base .tex file and associated .bib, .aux, and other files -- at eight characters or less (excluding extensions).
    • Keep your LaTeX files as simple as possible; do not use elaborate local macros or highly customized style files. Please use the simple scifile.tex template for formatting your paper. (This is actually a perfectly good template to use both for the review draft and the final, revised copy. The source document includes additional instructions on setting up your manuscript.)
    • Do not use external style files, except for those already called out in the scifile.tex template. External style files are not supported by our conversion routine. If you need additional macros, please keep them simple and include them in the actual .tex document preamble.
    • Source code should be set up so that all .sty and .bst files called by the main .tex file are in the same directory as the main .tex file.
    • Use the $ delimiter for in-line equations and the $$ delimiter or the {equation} environment for displayed equations. Avoid using LaTeX subenvironments such as {array}, {eqnarray}, and {tabular} within math environments. Instead, use plain TeX commands to the extent possible (e.g., for generating matrices, use the TeX \matrix command in preference to the LaTeX {array} environment).
    • Please do not use AMS-LaTeX or other specialized macros for generating math.
    • Simple (i.e., non-nested) tables can be generated using the {tabular} environment. For nested tables, you may want to generate the table using a word processor and send it as a separate file.
  4. References. The most trouble-free approach to referencing (from our perspective) is to enter the figure calls manually in the text, in Science style, i.e.

    ({\it 1, 2})

    and then set up the reference list at the end using a simple {itemize} environment:

    \subsection*{References and Notes}
    \begin{itemize}
    \item[1.]
    J. Wynckin, L. Blinckin, F. Nodd, {\it J. Geophys. Res.} {\bf 103}, 727 (1998).
    \item[2.]
    Of course, these people really don't exist.
    \end{itemize}


    Alternatively, generate your references using the {thebibliography} environment or BibTeX. In any event, the references must be in Science style. (BibTeX users might try the Science.bst style file available here.) If you use BibTeX for your revision manuscript (i.e., after peer review), be sure to include all relevant style and bibliography files, including files generated by the compilation, with your upload (see below).

    Important: Use only the generic \cite{} command for referencing in the text, not other commands built on special macros. Also, make sure that there is no space between reference keynames within the braces (i.e., \cite{refone,reftwo,refthree}, not\cite{refone, reftwo, refthree}). If these guidelines aren't followed, some reference calls could get lost in the translation to HTML.
  5. Figures. How to handle figures depends on whether your manuscript is an initial submission or submission of a revised version after peer review.
    • If the manuscript is an initial submission, you should include figures within the PDF or PostScript file that you upload (see "Your upload," below), preferably at the end of the text. You can accomplish this by simply appending the figures to the end of the PDF or PostScript file (using Acrobat or another utility) or by including commands in your source file to insert graphics (using, for example, the graphix package).
    • For the final, revised draft (i.e., after peer review), do not include commands in your source file to insert PostScript or other graphics. Instead, generate figure captions at the end of your LaTeX file as ordinary text (i.e., do not use the {figure} environment). Save your figures as separate files, using Science's guidelines for preparing figures, and upload the figures separately.
  6. Compilation. Compile your LaTeX as many times as necessary to get a clean compilation. For those not using BibTeX, two compiles should do the trick; those using BibTeX should run the standard LaTeX --> BibTeX --> LaTeX --> LaTeX sequence. Be sure to save the .aux and .bbl files generated by the compilation. After your compile, use dvips (or another driver) to convert your .dvi file to PostScript, and (if possible) distill the PostScript to PDF.
  7. Your upload.

    Important: The files that you should upload depend on whether your manuscript is an initial submission, or submission of a revision after peer review.
    • For an initial submission, you should upload only the PostScript or PDF version of your compiled file (including figures, tables, references, and most categories of supplementary materials).
    • For submission of a revision after peer review, your upload should include the following files (to avoid upload problems, we strongly recommend that these files be packaged as a single compressed archive [*.zip file]):
      • LaTeX source file.
      • Any additional style files referenced in the source code (please avoid using these if possible).
      • The .aux file generated from the compilation.
      • BibTeX users: The .bib and .bst files used in compilation, plus the .bbl file generated by compilation.
      • .dvi, PostScript, and PDF files generated from the compilation.
      • Figure files and supplementary materials files.

Please also see our additional notes on the upload process for initial submissions and revised manuscripts.

Good luck, and thanks for publishing in Science.

Downloadable files: