Philip Newton
Tue, 27 Mar 2001 03:20:54 -0800
Matthew Byng-Maddick wrote: > The other possibility, I guess, given that it's london.pm is > to make it relate to buffy in some way.... :) That reminds me of an idea I had this morning on the way to work -- encode text using "Buffy" with uppercase and lowercase letters: uppercase letters stand for "0" bits and lowercase letters for "1" bits. (Or, if you prefer, bit 5 / 2**5 / 32 of each character represents the bit to be encoded.) Then you just have to chop the message into 5-bit chunks (adding 0 bits at the end if needed to pad to a 5-bit boundary) and translate. "London.pm"[1], in this method, turns into "BuFFy bUFFy bUffy bUffY bufFY buFFy BUFfy Buffy BufFy buFFY bUffy BUffy BUFFY buFfy BuFFY". See? Bears no resemblance to "London.pm" at all; all spies' attempts at figuring out the true meaning will be thwarted! Alernatively, there's the "beer" code, which has the advantage of mapping 4 bits handily to one nybble; "London.pm" then turns into "BeER beER BeeR beer BeeR beeR BeeR BeER BeeR beer BeeR beeR BEeR beeR Beer BEER BeeR beEr". Cheers, Philip [1] "London.pm" = 4c 6f 6e 64 6f 6e 2e 70 6d hex, or 01001100 01101111 01101110 01100100 01101111 01101110 00101110 01110000 01101101 binary, or 01001 10001 10111 10110 11100 11001 00011 01111 01101 11000 10111 00111 00000 11011 01+000 in 5-bit groups -- Philip Newton <[EMAIL PROTECTED]> All opinions are my own, not my employer's. If you're not part of the solution, you're part of the precipitate.