Complete issue 10:1 as one pdf - TUG

More documents

Recommendations

Info

$E-m: Guidelines for Future TEX Extensions - TUG$

$TUG 2001: A TEX Odyssey PROGRAM$

$LATEX Sophisticated professional typesetting for business and ...$

$TEX and Scripting Languages - TUG$

$Geometric Diversions with TEX, METAFONT and METAPOST - TUG$

$Writing Gregg Shorthand with mEtaFoNt and LATEX - TUG$

$Generating LaTeX documents through Matlab - TUG$

16 The File TUGboat, Volume 10 (1989), No. 1
TUGboat, Volume 10 (1989), No. 1 Software News from the V O R Project ~ Michael A. Harrison* Computer Science Division University of California, Berkeley Introduction This is a report on the current state of the V i m project as it relates to the community. The project has been running for over three years. Our research funding has been extended, but we will be evolving in non w-compatible ways. We expect to publish traditional research papers on the novel aspects of our work. Cf. [7] for a summary of a number of issues underlying this work. Design issues are discussed in [6]. This brief summary will tell you what software we will have available for use by the research community; it can be licensed commercially as well. By the time you read this report, all of the systems discussed should be available. The original goal of the VOW project was to create an integrated document preparation environment capable of producing high quality technical documents which involve mathematics, text, and graphics. In V O ~ both , source and target representations of a document are maintained and presented. The source representation refers to a m document in its original unformatted form; the target representation presents its formatted result. The user can edit both representations using a text editor and what is called a proof editor, respectively. Our editor is an Emacs-like editor written in our own VLisp (Vom Lisp). Changes made to one representation propagate to the other version automatically. It is easy to support source modifications that cause the target representation to change. but a major challenge was the transformation from a target version back to the source version. The original design ideas are described in [6]. The system reformats a document and redisplays it on the screen incrementally. Only the part of the document or the subregion of the screen that is affected by recent changes is reprocessed. The document *Sponsored by the Defense Advanced Research Projects Agency (DoD), monitored by Space and Naval Warfare Systems Command, under Contract No. N00039-88-C-0292. Additional funding came from the California MICRO program (Grant 88-083 in conjunction with IBM). environment has support for automatic production of indexes for books [8], support for bibliographic material (31, spelling checkers, and other documentrelated utilities. Cf. [5]. Our current system uses workstations with bitmap displays running under the UNIX operating system and the X window system [12]. Some subsystems also support SUNVIEW. In order to provide device independent high quality graphics, we use Postscript [1,2] and have written a Postscript interpreter. We are developing methods to interpolate Postscript into our displays. Future research plans include supporting composite objects, symbolic mathematics, hypertext documents, audio, live video, etc. A key element will be access to a persistent object base which is important for many applications. The V O prototype ~ is running and did pass the traditional Trip test [lo], as well as the more demanding Trip* test required of incremental document processors [9]. Because the w processor is based on Pat Monardo's C-?'E)i. the system is fast. Some timing data are reported in [9]. The most challenging part of V O R is ~ the reverse mapping mechanism. To handle some of the semantic difficulties, functions in VLisp are used to implement reverse mapping. Only a few are implemented in the current prototype. The V O prototype ~ will be available on the distribution sometime in January 1989. As the system currently stands, it will require a great deal of work to make into an industrial-strength system. It served our purposes admirably because we found out what we did right (and wrong) and this will influence the design of its successor. We have produced another system called INCTEX, derived from V i m , which we think will be useful immediately to the community. INCTEX is an incremental w It is very fast and is more efficient in its use of memory than V m . It supports quiescence checking, convergence testing, etc. (cf. [9] for definitions). It creates a DVI file and checkpoints some state information for each page on the first run. On subsequent runs. only those parts of the document which have changed are reprocessed. When running I4?'E)i incrementally, no unnecessary passes are used. INW, unlike V-, is editor independent and is designed to avoid parts of the operating system which would hamper porting. INCTEX has not passed the Trip' test as of this writing, but works well enough to process many research papers and a 200-page dissertation. IIGTEX 'Any flavor of T@ you want, not just plain m.
Page 1 and 2: When problem solving is reduced to
Page 3 and 4: TUGboat, Volume 10 (1989), No. 1 No
Page 5 and 6: TUGboat, Volume 10 (1989), No. 1 Ge
Page 7 and 8: TUGboat, Volume 10 (1989), No. 1 7
Page 9: TUGboat, Volume 10 (1989), No. 1 SG
Page 13 and 14: TUGboat, Volume 10 (1989), No. 1 tr
Page 21 and 22: TUGboat, Volume 10 (1989): No. 1 21
Page 25 and 26: TUGboat, Volume 10 (1989)' No. 1 Th
Page 29 and 30: TUGboat, Volume 10 (1989), No. 1 &z
Page 39 and 40: TUGboat, Volume 10 (1989), No. 1 Fo
Page 41 and 42: TUGboat, Volume 10 (1989), No. 1 co
Page 43 and 44: TUGboat, Volume 10 (1989), No. 1 Th
Page 47 and 48: TUGboat, Volume 10 (1989), No. 1 pr
Page 51 and 52: Low-Resolution Printers on Multi-Us
Page 53 and 54: LOW-Resolution Printers on Microcom
Page 55 and 56: Typesetters Allied Linotype CRTroni
Page 57 and 58: TUGboat, Volume 10 (1989), No. 1 zi
Page 59 and 60: TUGboat, Volume 10 (1989), No. I Si
Page 61 and 62:
TUGboat, Volume 10 (1989), No. 1 di
Page 63 and 64:
TUGboat, Volume 10 (1989), No. 1 se
Page 65 and 66:
TUGboat, Volume 10 (1989), No. 1 Am
Page 67 and 68:
TUGboat, Volume 10 (1989), No. 1 On
Page 70 and 71:
70 TUGboat, Volume 10 (1989), No. 1
Page 72 and 73:
TUGboat, Volume 10 (1989), No. 1 \e
Page 74 and 75:
TUGboat, Volume 10 (1989), No. 1 If
Page 76 and 77:
TUGboat, Volbme 10 (1989), No. 1 \n
Page 78 and 79:
TUGboat, Volume 10 (1989), No. 1 \g
Page 80 and 81:
Page 82 and 83:
TUGboat, Volume 10 (1989), No. 1 Ex
Page 84 and 85:
TUGboat, Volume 10 (1989), No. 1 Su
Page 86 and 87:
TUGboat, Volume 10 (1989), No. 1 %
Page 88 and 89:
TUGboat, Volume 10 (1989), No. 1 %
Page 90 and 91:
Page 92 and 93:
TUGboat, Volume 10 (1989), No. 1 \c
Page 94 and 95:
TUGboat, Volume 10 (1989), No. 1 po
Page 96 and 97:
TUGboat, Volume 10 (1989), No. I %
Page 98 and 99:
TUGboat, Volume 10 (1989), No. 1 ho
Page 100 and 101:
TUGboat, Volume 10 (1989)' No. 1 ch
Page 102 and 103:
TUGboat, Volume 10 (1989), No. 1 ac
Page 104 and 105:
TUGboat, Volume 10 (1989), No. 1 th
Page 106 and 107:
TUGboat, Volume 10 (1989), No. 1 \p
Page 108 and 109:
TUGboat, Volume 10 (1989), No. 3 Ve
Page 110 and 111:
GEOID COMPUTATION The problems rela
Page 112 and 113:
PRESENTATION OF RESULTS The Oblique
Page 114 and 115:
TUGboat, Volume 10 (1989), No. 1 Re
Page 116 and 117:
TUGboat, Volume 10 (1989), No. 1 er
Page 118 and 119:
TUGboat, Volume 10 (1989), No. 1 GU
Page 120 and 121:
120 TUGboat, Volume 10 (1989), No.
Page 122 and 123:
122 TUGboat, Volume 10 (1989), No.
Page 124 and 125:
TUGboat, Volume 10 (1989), No. 1 Un
Page 126 and 127:
Integrated Computer Software, Inc S
Page 128 and 129:
TEX Distribution tapes: 'QjX Order
Page 130 and 131:
It doesn't have to be. End its Tfle
Page 132 and 133:
If you find yourself needing a Tani
Page 134 and 135:
Math and Technical B Publishers. If
Page 136 and 137:
Publishing Companion translates Wor
Page 138 and 139:
A Gourmet Guide to Typesetting with
Page 140 and 141:
We have it all. ArborText offers mo
Page 142 and 143:
TUGboat, Volume 10 (1989), No. 1 TE
Page 144 and 145:
Colophon for Computers & Typesettin
Page 146 and 147:
Page 4 : Bugs in Computers & Typese
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 10 : Bugs in Computers & Types
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Page 16 : Changes to the Programs a
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166:
Page 26: Changes to the Programs an
show all

Complete issue 10:1 as one pdf - TUG

Create successful ePaper yourself

Delete template?

Save as template?