General Information

	Eli: Translator Construction Made Easy
	Global Index
	Frequently Asked Questions
	Typical Eli Usage Errors

Tutorials

	Quick Reference Card
	Guide For new Eli Users
	Release Notes of Eli
	Tutorial on Name Analysis
	Tutorial on Scope Graphs
	Tutorial on Type Analysis
	Typical Eli Usage Errors

Reference Manuals

	User Interface
	Eli products and parameters
	LIDO Reference Manual
	Typical Eli Usage Errors

Libraries

	Eli library routines
	Specification Module Library

Translation Tasks

	Lexical analysis specification
	Syntactic Analysis Manual
	Computation in Trees

Tools

	LIGA Control Language
	Debugging Information for LIDO
	Graphical ORder TOol

FunnelWeb User's Manual

	Pattern-based Text Generator
	Property Definition Language
	Operator Identification Language
	Tree Grammar Specification Language
	Command Line Processing
	COLA Options Reference Manual

Generating Unparsing Code

Monitoring a Processor's Execution

Administration

System Administration Guide

New Features of Eli Version 4.4

Producing portable document files

Eli now uses pdftex and pdflatex to produce PDF files. The original source for the text may be TeX or LaTeX, FunnelWeb, or Texinfo.

A conversion from TeX, LaTeX, or Texinfo to PDF is obtained simply by requesting the :pdf product:

foo.tex :pdf
bar.tnf :pdf

FunnelWeb formatting is complicated by the typesetter option (see Typesetting Documentation with Eli of FunnelWeb). You must choose the correct weaver for the option and include it in the request. For example, suppose that your FunnelWeb file did not use the typesetter option. In that case, fwTex is the correct weaver:

MySpec.fw :fwTex :pdf

You will not be able to produce PDF files from FunnelWeb files that specify `@p typesetter = html'.

It is also possible to use a type-`specs' file to specify a collection of type-`tnf' files, all of which are to be formatted. Suppose that the collection is defined by `Doc.specs', that `ps' is the directory into which PostScript files are to be placed, and that `pdf' is the directory into which PDF files are to be placed. Here is a request that yields one PostScript file in directory `ps' for each type-`tnf' file whose name appears in `Doc.specs'. That PostScript file is formatted for two-sided printing, with each chapter starting on an odd-numbered page:

Doc.specs :ps >ps

Here is a request yielding one PDF file in directory `pdf' for each type-`tnf' file whose name appears in `Doc.specs'. The `+single' parameter means that the PDF file will be formatted for single-sided printing -- chapters are not forced to begin on odd pages:

Doc.specs +single :pdf >pdf

Unfortunately, the names of the files in the `ps' directory will have the suffix `.tnf.tnfps' and the files in the `pdf' directory will have names ending in `.tnf.tnfpdf'. These names can be changed by a simple Bourne shell script with commands like the following:

for f in `ls *.tnfpdf`
do mv $f `basename $f .tnf.tnfpdf`.pdf
done