Eli   Documents Get Eli: Translator Construction Made Easy at SourceForge.net.
    Fast, secure and Free Open Source software downloads

General Information

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

Tutorials

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

Reference Manuals

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

Libraries

 o Eli library routines
 o Specification Module Library

Translation Tasks

 o Lexical analysis specification
 o Syntactic Analysis Manual
 o Computation in Trees

Tools

 o LIGA Control Language
 o Debugging Information for LIDO
 o Graphical ORder TOol

 o FunnelWeb User's Manual

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

 o Generating Unparsing Code

 o Monitoring a Processor's Execution

Administration

 o System Administration Guide

Mail Home

New Features of Eli Version 4.4

Previous Chapter Next Chapter Table of Contents


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


Previous Chapter Next Chapter Table of Contents