Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!csus.edu!ucdavis!csusac!unify!longbow!ttank!tts
From: tts@ttank.ttank.com (Karl Bunch)
Newsgroups: comp.lang.postscript
Subject: Protecting one's code.
Message-ID: <1991Apr3.174645.15251@ttank.ttank.com>
Date: 3 Apr 91 17:46:45 GMT
Reply-To: karl@ttank.com
Organization: Think Tank Software, Norwalk, CA
Lines: 20

Our company has just recently gotten into PostScript programming from a
customer stand point. (We've already setup invoices etc. for our in-house
needs).  Now that we are starting to create all kinds of PostScript forms
logos etc. we are concerned about the basic "Source" form that we must
give to the customers.  So as to avoid priracy is there a way we can use
eexec or some such to encode the PostScript source?  It doesn't have to
be fullproof.  Just something that would stop the average PostScript
programmer because of the "Complexity" of having to decode it etc etc.

BTW to all the people that replied to my questions about "Curl" on our
HP LJIII, Thanks!  I'm armed with lots of good ideas.. Now all I need is
a little time to test them out. :-)

Thanks for any ideas,
Karl
-- 
% ----------------------------------------------------------------------------
% Karl Bunch                            ||| UUCP: ..!uunet!zardoz!ttank!karl
% Think Tank Software                   ||| INTERNET: karl@ttank.com
% "...you'd be suprised how far a hug will go with Geordi, even Worf!" -- Riker