cpsdecode



       cpsdecode - Extract shell scripts and data files from Com­
       plete PostScript (CPS) file


SYNOPSIS

       cpsdecode [ PostScript-file ] [ -n ] [ -v ]


DESCRIPTION

       cpsencode [and cpsdecode]  provide  a  convenient  way  of
       storing  a  UNIX script (or DOS batch file) and data files
       as part of the single PostScript plot the script  creates.
       Thus,  given  the resulting Complete PostScript (CPS) file
       one can recreate the original script and data at  a  later
       time.  cpsdecode reads a PostScript file (or stdin if none
       given) that previously has been augmented with output from
       cpsencode.   It will then extract the embedded data files,
       undoing any uuencoding and compression that was  performed
       by cpsencode.

       -n     Dryrun.  No files are extracted but we report which
              files would be decoded|decompressed  and  saved  to
              disk.

       -v     Verbose. Report the progress of decoding the script
              and any  data  files  referred  to  in  the  script
              [Default is silent].


EXAMPLES

       Let  us  say  you have a cshell script called Figure_8.csh
       which  creates  the  PostScript  file  Figure_8.ps.   Fig­
       ure_8.csh  operates on several data files in order to make
       the  plot.  You  turn  this  plot  file  into  a  Complete
       PostScript (CPS) file with the command

       cpsencode -v Figure_8.csh >> Figure_8.ps

       Alternatively,  let that be the last command in the script
       so that it is automatically done by the script itself.
       To unscramble the CPS file, simply say

       cpsdecode -v Figure_8.ps


BUGS

       cpsencode assumes good script etiquette so that any tempo­
       rary  files  created  by  your  script  are removed before
       cpsencode is called.  Otherwise they will take up unnecce­
       sary  space  in the Complete PostScript (CPS) file. cpsen­
       code will have trouble if you script  changes  directories
       with  the  cd  command  since filenames become relative to
       another directory. Using absolute  paths  name  for  files
       (starting  with  /,  ~/.  or ~user/) is bad practice since
       other users may not be able to access those files.

       Paul Wessel, Geology & Geophysics,  SOEST,  University  of
       Hawaii,  1680  East-West  Road,  Honolulu  HI  96822, USA.
       www.soest.hawaii.edu/wessel.


















































Man(1) output converted with man2html