[comp.archives] [text] Re: Asterix - product info wanted

wjh+@andrew.cmu.edu (Fred Hansen) (04/11/91)

Archive-name: x11/andrew/andrew/1991-04-10
Archive: emsworth.andrew.cmu.edu:/andrew.009.tar.Z [128.2.30.62]
Original-posting-by: wjh+@andrew.cmu.edu (Fred Hansen)
Original-subject: Re: Asterix - product info wanted
Reposted-by: emv@msen.com (Edward Vielmetti, MSEN)

Excerpts from netnews.comp.text: 9-Apr-91 Asterix - product info wanted
Stephen Frede@suite.sw.o (1001)

> We are looking for a text formatting system to supplement
> our extensive use of troff. It needs to be WYSIWIG but have
> as much of the flexibility of troff as possible, so that
> naive users can create documents easily and quickly, but
> complex macros (or whatever the product calls them) are
> possible.

Another system to consider is the Andrew Toolkit (ATK), its ez editor,
and its suite of applications which share the same data formats and user
interfaces.

ATK generates troff code and documents may be augmented with embedded
troff code if you want.  It handles and displays various fonts, type
sizes and face variants, justification, centered and right flush, sub-
and superscript, indentation, explicit page breaks, footnotes....  The
major feature is the capability of embedding objects in text--rasters,
tables, equations, drawings, ...;  this is an open system so users can
create their own objects and embed them.  

For printing, ATK generates troff (with embedded postscript for rasters)
which is run through troff (and psdit) to print the document.  ATK is
WYSIWYG only to the extent of showing all typography and embedded
objects;  line breaks on the display are adjusted to the display width. 
Lineand page breaks for printing are deferred to troff with its
extensive knowledge of the exact fonts that will be used for printing,
but the printed form can be viewed before printing via the 'preview'
program.  (Looking at a preview image shows one reason why WYSIWYG is
not always a great idea; characters positioned on screen according to
their print widths look awful.)

NESS
    "Ness" is the extension language for ATK.  It is a general
    purpose language with an emphasis on extending the behavior of
    embedded objects.  String processing is especially well
    supported: fromrtf.n, a translator from RTF to ATK, is
    fully-functioned, and yet only 2600 lines long.  String values
    in Ness can contain all the typographic formatting and embedded
    objects supported by ATK.

The cost of ATK has an upside and a downside.  It is free, so the price
is reasonable.  But it is not a "product" so some features are not fully
implemented.  I find it satisfactory for my work and have written half a
dozen papers and thousands of lines of code using it over the past four
years.  (Among the ATK applications is the multi-media mail interface
with which I am writing this note.)

ATK is available on the X tape and from the various ftp sites that
provide X--under directory contrib/andrew.  Our own ftp site is
emsworth.andrew.cmu.edu (128.2.30.62).

For more information you can contact Susan Straub:
	susan+@andrew.cmu.edu

Fred Hansen