🚀 go-pugleaf

In article <1992Aug2.170104.1236@afs.com> greg@afs.com (Gregory H. Anderson)  
writes:
> So far the mail on the ASCII vs RTF issue is running strongly in favor of  
> RTF. However, two people have raised a valid concern: Their access to the  
> Net is not directly through their NeXT machine. (Sounds like a reasonable  
> definition of Hell to me.) I just don't know: Is there any way they can  
> get RTF in that situation?

It is possible to save the RTF news file, transfer it to your NeXT, and read it  
there.  In fact, I think NGservice was written for just such a purpose.

The RTF issue was a rather contentious one, as seen by the vote.  The nominal  
consensus, in the absence of an RTF group, seems to be:
- do it only when it really adds to the information
- don't post large things that would be better off in the archives
- make sure you indicate (RTF) in the subject line, so people with low-speed  
modems can skip it.
The other concern was that the large bandwith consumed by RTF posts might make  
sites drop comp.sys.next altogether.

You might wish to consider (since Edit can covert to ASCII now) whether you  
should just post the ASCII version, and leave the RTF version on the archives.
A lot of it depends on just how much extra information RTF provides, and how  
much additional space it consumes.

Oh, and have you discussed turf issues vis-a-vis the csn.announce FAQ?  I don't  
think there is a huge overlap, and they'd probably enjoy diminishing there  
responisibility, but you should make it clear to avoid confusing users. Ditto  
with the comp.lang.objective-c FAQ.

- Ernie 'RFD' Prabhakar
--
Ernest N. Prabhakar                  Caltech High Energy Physics
Member, League for Programming Freedom (league@prep.ai.mit.edu)
CaJUN President        NeXTMail:ernest@pundit.cithep.caltech.edu
"...and ourselves, your servants for Jesus sake." - II Cor 5:13a
#import <std/disclaimer.h>