Path: utzoo!attcan!uunet!mcvax!ukc!slxsys!ibmpcug!daven From: daven@ibmpcug.UUCP (David Newman) Newsgroups: comp.sys.ibm.pc Subject: Re: Sprint word processor Message-ID: <11200@ibmpcug.UUCP> Date: 12 Aug 89 20:52:12 GMT Organization: The IBM PC User Group, UK. Lines: 36 I used Sprint to produce the camera ready copy for a 435-page book of conference proceedings (published by Chapman and Hall), using its very good postscript driver, and its macro language to convert badly typed PC-Write files into the format needed for the book. I also use it as my main programming editor, since it has a C-like macro language, and can have 24 files open at once. I like word processors with a separate editor and formatter. If you want WYSIWYG, then Sprint is not for you. You mark areas as headings, tables, figures etc. These appear as, say "CHAPTER Introduction" in the text. On printing, the formatter combines these markers with a style sheet to produce the layout you want. So you can write formatting style sheets and macros for different printers, journals, readers and so on - but the document file remains the same. Since you don't see what you get (except in a crude preview mode), it is hard to judge exact table alignments. So you have to print it out. I would not use it again for DTP of tables - I would use Sprint as a preprocessor, printing out into a file format marked up for Ventura. For less complicated layout, Sprint is fine. It's much easier to use than Word Perfect. But it can get quite complex when you are using it for DTP or as a programmers editor, since it has 2 programming languages - one for editor macros, the other for formatting and printer drivers. As usual, the printer drivers it comes with (some 300) don't always make use of all the features of the printer - you can usually improve on them. Of course, I am writing this message in Sprint. Dave Newman. JANET: D.R.Newman@kingston.ac.uk Usenet: as above. GreenNet (Econet/Peacenet/WEB): gn:davenewman. -- Automatic Disclaimer: The views expressed above are those of the author alone and may not represent the views of the IBM PC User Group.