home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!van-bc!cs.ubc.ca!destroyer!sol.ctr.columbia.edu!usc!wupost!crcnis1.unl.edu!moe.ksu.ksu.edu!ux1.cso.uiuc.edu!usenet.ucs.indiana.edu!master.cs.rose-hulman.edu!master.cs.rose-hulman.edu!news
- From: operjfw@NeXTwork.Rose-Hulman.Edu (Waldby)
- Newsgroups: talk.bizarre
- Subject: Re: rot(13) posting
- Date: 15 Nov 1992 23:42:32 GMT
- Organization: Computer Science Department at Rose-Hulman
- Lines: 30
- Message-ID: <1e6n98INNerp@master.cs.rose-hulman.edu>
- References: <U4bBrA2BBh107h@momad.UUCP>
- Reply-To: operjfw@nextwork.rose-hulman.edu
- NNTP-Posting-Host: o233-27.nextwork.rose-hulman.edu
-
- > >xyzzy@mertwig.UUCP (Daniel Drucker) writes:
- >
- > >>Is this the only way to post in rot(13)?
- > >>
- > >>heres what I do:
- > >>
- > >>1) post normally.
- > >>2) read my post
- > >>3) rot(13) it with x.
- > >>4) write it to a file
- > >>5) substitute that file in the appropriate directory
- > >>6) batch.
-
- Well, the way I'll do it, if I ever do is,
- I'll set up a file which shows the code changes
- You know something like this:
-
- abcdefghijklm
- nopqrstuvwxyz
-
- And then whenever I'm about to press a key,
- I reference my code encrypter.
-
- That's the only way I know. But I haven't
- given the matter much thought.
-
- --
- I'm a busy, busy man, so if you want me
- to see replies, please send to
- operjfw@nextwork.rose-hulman.edu
-