IMHO, the stuff related to parsing SCS should remain in the SCS
programs. Remember: SCS is not the only printer language that the
system supports. We'll want to support AFP, IPDS, USER-ASCII, etc in
the long run.
Plus, I think it's really handy for debugging and development to be able
to dump the SCS data to a file and be able to analyze that file, and run
it through other tools like scs2ascii or scs2pdf later on.
Can scs2pdf simply save the settings it needs into a file on disk?