🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.lang.postscript
Article #3179

Re: UnPostscripter?

#3179
From: Woody Baker Eagle Signal
Date: Tue, 25 Sep 1990 04:09
20 lines
1424 bytes
> 
> I worry about the availability of such decoding tool in general,
> because my colleagues and I use postscript as a relatively secure
> method (secure from cut and paste plagiarism, at least) to prepublish
> scientific papers. Postscript was specifically chosen over TeX
> precisely for its ability to obscure the source text.


You gotta be kidding.  If I wanted to plagarize any prepublished papers,
I'd simply scan them in, and use OCR to get the text.  Now, if you are
sending the raw postscript file out, it seems likely that postscript
would indeed obscure the source text, but certainly if you are dealing
with sending or giving someone a copy to critique or review, you would
be giving them a final i.e. printed page, not the Postscript code.
I think it is harder to read TeX source files with all the embedded
junk in them (at least the last time I looked, TeX was a nightmare to
specify anything in.

Cheers
Woody
Technical Details
Message-ID: <1589@chinacat.Unicom.COM>
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!chinacat!woody
References: <1990Sep21.003615.7222@amd.com> <POLLACK.90Sep24130957@dendrite.cis.ohio-state.edu>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!chinacat!woody
From: woody@chinacat.Unicom.COM (Woody Baker @ Eagle Signal)
Newsgroups: comp.lang.postscript
Subject: Re: UnPostscripter?
Summary: you gotta be kidding!
Message-ID: <1589@chinacat.Unicom.COM>
Date: 25 Sep 90 04:09:36 GMT
References: <1990Sep21.003615.7222@amd.com> <POLLACK.90Sep24130957@dendrite.cis.ohio-state.edu>
Organization: a guest of Unicom Systems Development, Austin
Lines: 20