Thread View: comp.sys.next.programmer
4 messages
4 total messages
Started by Gregory H. Anderson
Sun, 02 Aug 1992 17:01
FAQ issues: round 3
Author: Gregory H. Anderson
Date: Sun, 02 Aug 1992 17:01
Date: Sun, 02 Aug 1992 17:01
34 lines
2099 bytes
2099 bytes
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? Also, someone else mentioned the enormous amount of flamage earlier this year directed at people who post RTF, and pointed out that an attempt to create c.s.n.rtf failed. Should this bother us uber-programmers? I received several suggestions to include more stuff on OS functions and Mach. To me, only some OS issues, such as missing functions on NeXT that Sun programmers are used to, are relevant to c.s.n.programmer. I don't know about Mach and Unix generally. It seems to me that very few people actually write Loadable Kernel Servers. Besides, there's already a comp.os.mach and comp.os.unix newsgroup. Has NeXT really hacked up the standard Mach and BSD releases enough to include it here too? Subrata Sircar made the excellent suggestion to list the standard documentation sources and books, so people know where to go for further enlightenment. Several people suggested separate FAQs for each object class, but that seems excessive. Do we really want 100 small FAQ postings every month? Besides, in DL it doesn't really matter where the info lives. I find it more convenient to find multiple references within fewer titles, anyway. As usual, keep those cards and letters coming.... -- Gregory H. Anderson | "We're very tolerant around here, Benevolent Dictator-for-Life | being only amateurs ourselves." Anderson Financial Systems | - Tortoise (Godel, Escher, Bach) greg@afs.com (Nextmail OK) |
Re: FAQ issues: round 3
Author: Ernest Prabhakar
Date: Mon, 03 Aug 1992 02:42
Date: Mon, 03 Aug 1992 02:42
37 lines
2496 bytes
2496 bytes
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>
Re: FAQ issues: round 3
Author: Subrata Sircar
Date: Wed, 05 Aug 1992 22:34
Date: Wed, 05 Aug 1992 22:34
25 lines
1734 bytes
1734 bytes
greg@afs.com 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? RTF and NewsGrazer posts are slightly different; NewsGrazer has a plain-text version and an RTF version of the contents. Both can generally be transferred to a NeXT machine either electronically or physically (via floppy/OD) and then read with Edit/NGService. If we have either a lot of files, or large files, net.practice seems to be to post a pointer to the files and place the actual files on an FTP site. Nova is accessible by mail as well, so everyone should be able to get them from there. -- Subrata Sircar | ssircar@canon.com | Prophet & SPAMIT Charter Member Canon Information Systems and I do not speak for each other on all things. "I wish people wouldn't instantly assume that I am an idiot." (Valentine) "A restaurant is a whorehouse that does food instead of sex." (Roger Lustig)
Re: FAQ issues: round 3
Author: Andy Newman
Date: Fri, 07 Aug 1992 06:07
Date: Fri, 07 Aug 1992 06:07
14 lines
1124 bytes
1124 bytes
ssircar@canon.com (Subrata Sircar) writes: >greg@afs.com writes: >RTF and NewsGrazer posts are slightly different; NewsGrazer has a plain-text >version and an RTF version of the contents. Both can generally be transferred >to a NeXT machine either electronically or physically (via floppy/OD) and then >read with Edit/NGService. > The extra non-ASCII part is *not* RTF! It is a undocumented, NewsGrazer specific format. Firstly its uuencoded. If you uudecode the "noise" at the end of NewsGrazer articles it is plainly not RTF. It looks a bit like RTF but it isn't the same. -- Andy Newman (andy@research.canon.oz.au) "int - God's own type"
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads