Thread View: comp.sys.next.misc
4 messages
4 total messages
Started by Tim Pugh
Thu, 30 Jul 1992 11:34
Editing '.ps' files?
Author: Tim Pugh
Date: Thu, 30 Jul 1992 11:34
Date: Thu, 30 Jul 1992 11:34
13 lines
1070 bytes
1070 bytes
Please podon my ignorance but it would seem that PostScript is a great
output file format but not readily available as an input format. While
I am able to open a '.ps' file in Edit, all I see is "raw" PostScript".
WriteNow will not even show that a '.ps' file exists in it's open panel.
While Preview is great for display of a '.ps' file, how does one convert
it to an input format such as RTF or ASCII (without the PS commands)?
Thanks for you help,
Tim
--
Tim Pugh |MicroCALL Services
tim@aplcen.apl.JHU.EDU |8713 Briarcroft Lane
|Laurel, MD 20708-1355
------------------------------------------------------------------------------
Re: Editing '.ps' files?
Author: Eric P. Scott
Date: Fri, 31 Jul 1992 05:33
Date: Fri, 31 Jul 1992 05:33
25 lines
1783 bytes
1783 bytes
In article <1992Jul30.113455.13997@aplcen.apl.jhu.edu> tim@aplcen.apl.jhu.edu (Tim Pugh) writes: >Please podon my ignorance but it would seem that PostScript is a great >output file format but not readily available as an input format. While >I am able to open a '.ps' file in Edit, all I see is "raw" PostScript". >WriteNow will not even show that a '.ps' file exists in it's open panel. >While Preview is great for display of a '.ps' file, how does one convert >it to an input format such as RTF or ASCII (without the PS commands)? This is one of the most commonly asked questions in the newsgroup comp.lang.postscript. <-- blatant plug The general answer is, "you can't." PostScript is an honest-to- goodness programming language, and the ONLY way to make sense of arbitrary PostScript is to execute it. Except for rigid subsets (such as Adobe Illustrator format) that are basically data structures suitably contrived to pass for valid PostScript, it's impossible to do what you're asking for any but the most trivial files (which generally means no reencodings, no kerning, etc.). Sometimes you can get away with redefining a whole bunch of operators (ref. distill) and get something meaningful, especially if whatever generated the PostScript in the first place wasn't deliberately mean-spirited. -=EPS=-
Re: Editing '.ps' files?
Author: Dave Griffiths
Date: Tue, 04 Aug 1992 05:59
Date: Tue, 04 Aug 1992 05:59
35 lines
2323 bytes
2323 bytes
In article <1992Jul31.053336.6399@csus.edu> eps@cs.sfsu.edu writes: >In article <1992Jul30.113455.13997@aplcen.apl.jhu.edu> > tim@aplcen.apl.jhu.edu (Tim Pugh) writes: >>Please podon my ignorance but it would seem that PostScript is a great >>output file format but not readily available as an input format. While >>I am able to open a '.ps' file in Edit, all I see is "raw" PostScript". >>WriteNow will not even show that a '.ps' file exists in it's open panel. >>While Preview is great for display of a '.ps' file, how does one convert >>it to an input format such as RTF or ASCII (without the PS commands)? > >The general answer is, "you can't." PostScript is an honest-to- >goodness programming language, and the ONLY way to make sense of >arbitrary PostScript is to execute it. Except for rigid subsets >(such as Adobe Illustrator format) that are basically data >structures suitably contrived to pass for valid PostScript, it's >impossible to do what you're asking for any but the most trivial >files (which generally means no reencodings, no kerning, etc.). >Sometimes you can get away with redefining a whole bunch of >operators (ref. distill) and get something meaningful, especially >if whatever generated the PostScript in the first place wasn't >deliberately mean-spirited. > While it may be true that "we can't", surely it is true that NeXT *can*? In other words, it must be possible to add some functionality to the window server to say "give me the text in this rectangle"? (Maybe in RTF. Lets forget about the graphics for the time being.) Since the window server is interpreting the postscript, *it* must know where it is placing the text and what font is being used? Given the pervasiveness of postscript on the NeXT and the usefulness of being able to extract RTF from postscript for cutting and pasting purposes, I'm really surprised that no such ability exists. Dave Griffiths
Re: Editing '.ps' files?
Author: Tim Pugh
Date: Tue, 04 Aug 1992 16:45
Date: Tue, 04 Aug 1992 16:45
51 lines
3126 bytes
3126 bytes
prim!dave@germany.eu.net (Dave Griffiths) writes:
>In article <1992Jul31.053336.6399@csus.edu> eps@cs.sfsu.edu writes:
>>In article <1992Jul30.113455.13997@aplcen.apl.jhu.edu>
>> tim@aplcen.apl.jhu.edu (Tim Pugh) writes:
>>>Please podon my ignorance but it would seem that PostScript is a great
>>>output file format but not readily available as an input format. While
>>>I am able to open a '.ps' file in Edit, all I see is "raw" PostScript".
>>>WriteNow will not even show that a '.ps' file exists in it's open panel.
>>>While Preview is great for display of a '.ps' file, how does one convert
>>>it to an input format such as RTF or ASCII (without the PS commands)?
>>
>>The general answer is, "you can't." PostScript is an honest-to-
>>goodness programming language, and the ONLY way to make sense of
>>arbitrary PostScript is to execute it. Except for rigid subsets
>>(such as Adobe Illustrator format) that are basically data
>>structures suitably contrived to pass for valid PostScript, it's
>>impossible to do what you're asking for any but the most trivial
>>files (which generally means no reencodings, no kerning, etc.).
>>Sometimes you can get away with redefining a whole bunch of
>>operators (ref. distill) and get something meaningful, especially
>>if whatever generated the PostScript in the first place wasn't
>>deliberately mean-spirited.
>>
>While it may be true that "we can't", surely it is true that NeXT *can*?
>In other words, it must be possible to add some functionality to the
>window server to say "give me the text in this rectangle"? (Maybe in
>RTF. Lets forget about the graphics for the time being.) Since the window
>server is interpreting the postscript, *it* must know where it is placing
>the text and what font is being used?
>Given the pervasiveness of postscript on the NeXT and the usefulness of
>being able to extract RTF from postscript for cutting and pasting
>purposes, I'm really surprised that no such ability exists.
>Dave Griffiths
As the original poster of the query, finding there was no NeXT supplied
way to do the above, I tried the Create application. Since all I was
really trying to do was to fill in the blanks on a software license
for Andrew, I fould that Create does this job nicely. However, I agree
with Dave that it would be nice if NeXT supplied us with a tool to do
this, perhaps built into Preview.
Tim
--
Tim Pugh |MicroCALL Services
tim@aplcen.apl.JHU.EDU |8713 Briarcroft Lane
|Laurel, MD 20708-1355
------------------------------------------------------------------------------
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads