🚀 go-pugleaf

Christopher D Audley writes
> > Why not have everyone put their documentation in troff??
> 
> Why not just use PostScript.  Authors of documentation can
> use any word processing/page layout program they want and
> save it as PostScript.  Its not like people are typically
> going to want to be able to modify documentation they receive.
> The original author can retain the document in whatever format
> he wishes for latter modification. 

> Every NeXTstep program has the ability to create PostScript
> files and every NeXT can read them.  Why does there seem to
> be resistence to using it as the standard format of documentation?

I think that the main problem with PostScript is that you can't drop  
the files into DL.

Edit .rtf and .rtfd files seem ideal for distributing docs, and  
everyone gets Edit.  The main constraint there is the lack of page  
breaks and page numbering (and perhaps, headers/footers).  This would  
seem to be fairly trivial to add to Edit, and shouldn't step on too  
many outside developers' toes, since the resulting app would still be  
pretty limited.  If NeXT can't find the time to do it itself, perhaps  
they could provide the source to somebody who would volunteer to do  
it as a public service?

--
-
Stefano Pagiola
Food Research Institute, Stanford University
spagiola@frinext.stanford.edu (NeXTMail encouraged)