home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!cs.utexas.edu!asuvax!asuacad!aubxg
- Organization: Arizona State University
- Date: Monday, 23 Nov 1992 18:51:12 MST
- From: Ben Goren <AUBXG@ASUACAD.BITNET>
- Message-ID: <92328.185112AUBXG@ASUACAD.BITNET>
- Newsgroups: comp.lang.postscript
- Subject: Re: A rough attempt to define comp.sources.postscript formally
- References: <1992Nov20.172051.7022@cs.brown.edu>
- Lines: 29
-
- I'd vote yes for c.s.ps moderated, no for c.s.ps.d, and suggest that
- anything that gets misposted either gets redirected to c.l.p or the
- original sender, at the moderator's discretion.
-
- It also might not be a bad idea for the moderator to have a copy of
- the FAQ on hand to send to those who ask FAQs.
-
- There should probably be a FAQ for the sources group which explains
- how to access the archives; it'd also be nice if it gets reposted
- whenever it expires. That'd likely cut down on the "could somebody
- please repost that xyz2eps program" request.
-
- And, on the content of the group: I wouldn't mind seeing an occasional
- source that generates PostScript if it does something novel or especially
- useful, but I see non-PS postings being the rare exception. And for the
- acceptable file formats? Straight ASCII, whenever possible; shell
- archives when not (as they're just ASCII files with some extra things that
- make it easy for Unix to extract and assemble). If compression is
- absolutely necessary, use the RLE built into PS Level 2, and let the printer
- deal with the compression. Sure, it might be slow and not everybody has
- a Level 2 device yet, but those with the high-speed connections who would
- actually download such a large file will probably have access to something
- with Level 2. As a bonus, anybody who posts such a file might want to
- include something which writes the uncompressed file to the standard
- output.
-
- All for now.
-
- b&
-