X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f996b,5e20dd0eb81e05d7 X-Google-Attributes: gidf996b,public From: Veronica Karlsson Subject: Re: sigs (was Re: Minor change in the F.A.Q. Please read.) Date: 1997/11/29 Message-ID: <347FAD2D.4487EB71@on.spammer>#1/1 X-Deja-AN: 293592350 References: <347B24B4.A2B045E5@inspace.net> <347B5183.C6@slip.net> <347B5A20.6201DD56@on.spammer> <347B63AE.1025@mpq.mpg.de> <347B6C57.2C67412E@on.spammer> <347C372E.4ECB@mpq.mpg.de> <347CF32E.FF6D5DF@on.spammer> <347D3701.75DB@mpq.mpg.de> <347D8040.63DECDAD@on.spammer> <65npea$do8$9@usenet88.supernews.com> Organization: University of Lulea, Sweden Newsgroups: alt.ascii-art aardvarko wrote: > > Hmmmmm... that's a pretty good idea. Is that a standard newsreader > feature? And if so, what's the point? OE4 only lets you unscramble, not > scramble. > Yes, it's standard. I seem to remember reading somewhere that it could be used for text that contained something that might offend somebody, that way only those who want to read it can read it and nobody has to accidentally read something he/she doesn't want to read... The coding is just there to "blur" the text for the human eye... This little C program will "scramble"/"unscramble" text for you: #include #include main() { int ch; while ((ch = getchar()) != EOF) { if ((ch >= 65) && (ch <= 90)) { ch = 65 + ((ch - 65) + 13) % 26; } if ((ch >= 97) && (ch <= 122)) { ch = 97 + ((ch - 97) + 13) % 26; } printf("%c", ch); } } -- _ ____ _ _ _ _ _ _ __ _| |__/ __ \| |_ _ __| |__| | | |_ _| |_| |_ ___ ___ \ V / / / / _` | | || / _` / _` |_| | || | _| ' \ _(_-