🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.sys.next.misc
Article #3809

Re: A Modest Proposal

#3809
From: Paul Marcos
Date: Tue, 06 Oct 1992 20:05
47 lines
3202 bytes
In article <y&#@byu.edu>, yackd@alaska.et.byu.edu (Don Yacktman) wrote:

> >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?
> 
> My guess is that this is twofold:  (1) someone would have to set up DL so
> that it can index PS files.  To my knowledge (which may not be complete...)
> right now, indexing PS doesn't work the way you would want it to.  Even so,
> you wouldn't be able to easily open the PS file to the page where the word
> you searched for appears...or, for that matter, find the next word.  So, it
> would seem to me that until DL and Preview get better, you lose a lot by
> going to PS format.  And, (2) PS files are very big compared to, say, a
> WriteNow document.  They can be stored compressed, but then you don't have
> access to the info inside.  (What would be great, though, is to set things
> up so that a ".psZ" file would be zcatted into Preview...hmmm...)  Those are
> the reasons that are most obvious to me; I'm sure others can add to the list.

PostScript wouldn't be too good of a choice.  The problem is that PS
doesn't necessarily save text as a "stream of letters".  Very often words
are broken up and painted as individual letters.  Take the case of text
along a circle.  More than likely the text is painted character by
character as opposed to a string.  This would make searching it virtually
impossible.   

If the text was kept as a string, it wouldn't be too hard to get to the
page that it's on but it would be tricky to highlight it.  There would have
to be some intelligence built into the viewer.  

If there was an easy way to do it NeXT probably would already have the
features available in DL and Preview. 

Paul

|---------------------------------------------------------------------|
|  Paul Marcos                        |     Anything that I say,      |
|  Adobe Systems, Inc.                |     I say on my own.          |
|  1545 Charleston RD, P.O. Box 7900  |     My views are not          |
|  Mountain View, CA  94039-7900      |     the views of my employer. |
|  Internet:  pmarcos@adobe.com       |                               |
|---------------------------------------------------------------------|
Technical Details
Message-ID: <pmarcos-061092130239@clive.mv.us.adobe.com>
Path: arc1-ca.pugleaf.net!sparky!uunet!olivea!decwrl!adobe!clive.mv.us.adobe.com!user
References: <tlm.718249912@scl1.al.iastate.edu> <1992Oct5.190630.26539@jhunix.hcf.jhu.edu> <y&#@byu.edu>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!olivea!decwrl!adobe!clive.mv.us.adobe.com!user
From: pmarcos@adobe.com (Paul Marcos)
Newsgroups: comp.sys.next.misc
Subject: Re: A Modest Proposal
Message-ID: <pmarcos-061092130239@clive.mv.us.adobe.com>
Date: 6 Oct 92 20:05:48 GMT
References: <tlm.718249912@scl1.al.iastate.edu> <1992Oct5.190630.26539@jhunix.hcf.jhu.edu> <y&#@byu.edu>
Sender: usenet@adobe.com (USENET NEWS)
Followup-To: comp.sys.next.misc
Organization: Adobe Systems, Inc.
Lines: 47