Important files

The file initial.tex included at the head of this report is commented and gives several commands you may wish to employ. We suggest you latex and print this present document and then print off the two source files layout.tex and initial.tex and keep them handy while reading this text.

You should always include the file initial.tex at the beginning of your main text file by inserting the command \input{initial} (no .tex) as the first line of your text: this contains such details as page dimensions and other parameter settings, most of which you should not alter. Other information in this file can be altered or added to. Typically, you would alter only header and footer information to reflect the relevant details of your document (search for \pagefooter and \pageheader). Normally, you would edit only the 2nd and 3rd fields of the header (chapter heading or other string, and the relevant document number) and the 1st and 3rd fields of the footer (document status and date). You might also add abbreviated commands, acronyms etc. to the list in initial.tex, however please do not delete existing abbreviated commands.

Several files are automatically included by initial.tex, thus you should ensure these are available. They should have been distributed along with this file. You should not edit any of these style files. Table 2.1 summarises these automatically included files. The last three are included in the normal LaTeX distribution.

 

EAGLES declarations initial.tex
Headers and footers headerfo.sty
For processing EPSFs psfig.tex
HTML-related LaTeX commands html.sty
HTML-related LaTeX commands verbatim.sty
Arithmetic calculation calc.sty
Bibliographic references harvard.sty
Linguistic structures lingmacros.sty
Linguistic structures tree-dvips.sty
Required by tree-dvips.sty tree-dvips91.pro
Linguistic structures avm.sty
Not needed for LaTeX-ing, LaTeX2HTML use only heqn.sty
Times Roman times.sty
Index generation makeidx.sty
Graphics and figures graphics.sty
Table 2.1: Auto-included files 

In addition, the (path)name of any EPSF you include must be specified in your text. Other files may be necessary, e.g. to handle linguistic trees.

Editors' note: Please consult the Editorial Board if you plan to use any style files or complex user commands not mentioned here, as there are implications for conversion to HTML that must typically be taken into account.

For further general information, you should consult your local facility's LaTeX user manual, or invest in a copy of Lamport (1994). In this report, we largely assume that you know the basics of LaTeX already and how to run the system. However, there follows a synopsis of how to write in LaTeX.




ceditor@tnos.ilc.pi.cnr.it